Bug 281501 - New canonical location for Certs
Summary: New canonical location for Certs
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: koji
Version: 7
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-06 21:42 UTC by Mike McGrath
Modified: 2008-02-08 05:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-08 05:50:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mike McGrath 2007-09-06 21:42:38 UTC
There is a new location for the certs that fedora-packager-setup.sh should pull
from:

https://admin.fedoraproject.org/accounts/fedora-upload-ca.cert
and
https://admin.fedoraproject.org/accounts/fedora-server-ca.cert

Comment 1 Till Maas 2007-09-06 22:01:01 UTC
Please remove the attachments at
http://fedoraproject.org/wiki/PackageMaintainers/BuildSystemClientSetup?action=AttachFile
 once the updated koji package was pushed to stable.

Comment 2 Jesse Keating 2007-11-15 17:28:38 UTC
Dennis, is there an upstream location for the fedora-packager-setup.sh script? 
If not, we can chuck it in rel-eng git or something.  I'd like to get this
processed today as part of the overall buildsystem refresh.

Comment 3 Jesse Keating 2007-11-15 21:02:38 UTC
I've committed the change to the scripts in devel/ F-8/ and F-7/ koji modules. 
These will take effect next time we do a koji update, which there should be one
coming soon.

Dennis has no current upstream for these files, but is working on getting a
project page for these plus other Fedora developer related tools

Comment 4 Dennis Gilmore 2007-11-16 06:27:44 UTC
there is now an upstream for fedora-packager-setup.sh 
https://hosted.fedoraproject.org/projects/fedora-packager/  I neeed to get the 
pieces in quickly and  get the package in for review



Comment 5 Dennis Gilmore 2008-02-08 05:50:58 UTC
this is fixed now


Note You need to log in before you can comment on or make changes to this bug.