Bug 819233 - Broken fedora-4-*-epel.cfg symlinks in /etc/mock
Summary: Broken fedora-4-*-epel.cfg symlinks in /etc/mock
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mock
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Clark Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-05 20:02 UTC by Ville Skyttä
Modified: 2012-08-02 00:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-02 00:36:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Ville Skyttä 2012-05-05 20:02:45 UTC 
The following symlinks in /etc/mock point to no longer existing epel-4-*.cfg targets:

fedora-4-i386-epel.cfg -> epel-4-i386.cfg
fedora-4-ppc-epel.cfg -> epel-4-ppc.cfg
fedora-4-x86_64-epel.cfg -> epel-4-x86_64.cfg

Should be an easy fix:

--- a/mock.spec
+++ b/mock.spec
@@ -53,5 +53,2 @@ install -m 644 %{SOURCE2} $RPM_BUILD_ROOT%{_sysconfdir}/mock/
 pushd $RPM_BUILD_ROOT/etc/mock
-ln -s epel-4-i386.cfg   fedora-4-i386-epel.cfg
-ln -s epel-4-ppc.cfg    fedora-4-ppc-epel.cfg
-ln -s epel-4-x86_64.cfg fedora-4-x86_64-epel.cfg
 ln -s epel-5-i386.cfg   fedora-5-i386-epel.cfg
Comment 1 Clark Williams 2012-06-07 20:48:51 UTC 
This got fixed in 1.1.21 and I missed putting the BZ into bohdi
Comment 2 Ville Skyttä 2012-06-08 14:50:10 UTC 
It's not fixed in 1.1.22-2.1.fc17.


$ rpm -qvlp mock-1.1.22-2.1.fc17.noarch.rpm | grep -P 'fedora-4|epel-4'
lrw-r--r--    1 root    mock                       15 May  8 14:27 /etc/mock/fedora-4-i386-epel.cfg -> epel-4-i386.cfg
lrw-r--r--    1 root    mock                       14 May  8 14:27 /etc/mock/fedora-4-ppc-epel.cfg -> epel-4-ppc.cfg
lrw-r--r--    1 root    mock                       17 May  8 14:27 /etc/mock/fedora-4-x86_64-epel.cfg -> epel-4-x86_64.cfg
Comment 3 Clark Williams 2012-08-02 00:36:12 UTC 
Got it in 1.1.23
Note You need to log in before you can comment on or make changes to this bug.