#5870: rawhide signing
------------------------------+-----------------------
Reporter: kevin | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Final | Component: koji
Resolution: | Keywords: meeting
Blocked By: | Blocking:
------------------------------+-----------------------
Comment (by quickbooks):
Replying to [comment:12 kevin]:
So, we could easily make something that listens on fedmsg for builds
and
takes action on them. However, we need work to integrate that with sigul.
We need someone(s) to work on that integration...
In the mean time to move this forward, perhaps we can do a 'best effort'
version manually. Either:
a) Some packages not yet signed go out unsigned in rawhide composes.
b) we make rawhide build into f21-pending and only move them to f21 (and
push out
in compose) after signing.
a means some packages will simply not be signed at all.
b means some packages may be delayed getting out in composes if releng
folks
haven't signed them yet.
So now there will be 2 repositories right?
The first one will be called ''Rawhide Signed'' and the second
''Rawhide
Unsigned'', similar to how there is ''Updates'' and
''Updates Testing''
for F20?
--
Ticket URL: <
https://fedorahosted.org/rel-eng/ticket/5870#comment:13>
Fedora Release Engineering <
http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project