Bug 785776

Summary:	fedpkg doesn't use ~/.koji/config anymore
Product:	[Fedora] Fedora	Reporter:	Karsten Hopp <karsten>
Component:	fedpkg	Assignee:	David Cantrell <dcantrell>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	high
Version:	16	CC:	dcantrell
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	fedpkg-1.9-1.fc17	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-31 02:57:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Karsten Hopp 2012-01-30 15:41:10 UTC

Description of problem:
older versions of fedpkg honored  ~/.koji/config which allowed me to overwrite the global config with p.e. secondary arch settings by linking ~/.koji/ppc-config to ~/.koji/config

Nowadays fedpkg has /etc/koji.conf hardcoded and secondary arch maintainers need to replace  /etc/koji.conf with custom configs as 'fedpkg --arches ppc ppc64' doesn't work either


Steps to Reproduce:
1. ln -s ~/.koji/ppc-config ~/.koji/config
2. cd to a fedora package checkout directory (p.e. fedpkg clone ed )
3. fedpkg build --scratch --target f17     -> package gets built on the primary archs
4. fedpkg build --scratch --archs ppc ppc64 --target f17   -> some weird error about your home directory not being a repository

Comment 1 Karsten Hopp 2012-01-30 15:44:50 UTC

4. the weird error happens only if you also have --srpm some-valid-srpm on the commandline, if you've changed into a package checkout directory, the package gets built on the primary archs again instead of ppc

Comment 2 Jesse Keating 2012-03-03 00:06:46 UTC

Two bugs here.  Bug 1 (not reading ~/.koji/config) is a rpkg bug, fixed in commit fba6396a959a03453856e2ef306116c344bb874d

Bug 2 (the error about not being in a repository) is a fedpkg bug, part of the routine that checks to see if the user has processed the branch renames yet in their checkout.  I've fixed it to pass if there is no repo in question, commit 467a8d218dcf29e2dff571abca5b2b652ffb8e1b

Comment 3 Fedora Update System 2012-03-12 23:56:05 UTC

rpkg-1.14-1.fc16,fedpkg-1.9-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/rpkg-1.14-1.fc16,fedpkg-1.9-1.fc16

Comment 4 Fedora Update System 2012-03-12 23:56:41 UTC

fedpkg-1.9-1.fc15,rpkg-1.14-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/fedpkg-1.9-1.fc15,rpkg-1.14-1.fc15

Comment 5 Fedora Update System 2012-03-12 23:57:11 UTC

fedpkg-1.9-1.fc17,rpkg-1.14-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/fedpkg-1.9-1.fc17,rpkg-1.14-1.fc17

Comment 6 Fedora Update System 2012-03-13 17:10:28 UTC

Package fedpkg-1.9-1.fc17, rpkg-1.14-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fedpkg-1.9-1.fc17 rpkg-1.14-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-3682/fedpkg-1.9-1.fc17,rpkg-1.14-1.fc17
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2012-03-31 02:57:30 UTC

fedpkg-1.9-1.fc15, rpkg-1.15-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2012-03-31 03:20:44 UTC

fedpkg-1.9-1.fc16, rpkg-1.15-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2012-04-12 02:06:23 UTC

fedpkg-1.9-1.fc17, rpkg-1.15-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.