Hello ,
Packages not signed in F24 are breaking copr builds , but I need copr to test packages for F24 ...
What should we do ? to workaround this problem.
Thanks,
On 03/08/2016 12:20 PM, Sérgio Basto wrote:
Hello ,
Packages not signed in F24 are breaking copr builds , but I need copr to test packages for F24 ...
What should we do ? to workaround this problem.
Thanks,
Wait for tomorrow. The packages should be signed starting today, as it is the bodhi activation point.
It was asked many times here and around during last few days. Here [1], here [2] and may be more.
[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/... [2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
On Ter, 2016-03-08 at 14:49 +0100, Jakub Jelen wrote:
On 03/08/2016 12:20 PM, Sérgio Basto wrote:
Hello ,
Packages not signed in F24 are breaking copr builds , but I need copr to test packages for F24 ...
What should we do ? to workaround this problem.
Thanks,
Wait for tomorrow. The packages should be signed starting today, as it is the bodhi activation point.
Meanwhile , can't we hack copr , with gpgcheck=0 in Fedora 24 repos. It will be much less stressful.
It was asked many times here and around during last few days. Here [1], here [2] and may be more.
I can't see any workaround to manage builds on copr and this is broken for a few days ...
[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproje ct.org/thread/A7VQ45QJW6CM5UW3PJKC5S2V7GIC32AH/ [2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproje ct.org/thread/V5B6J4UNMOJIPC5J7O5VRW7PLGPCLGR3/
On Wed, 09 Mar 2016 16:35:17 +0000 Sérgio Basto sergio@serjux.com wrote:
Meanwhile , can't we hack copr , with gpgcheck=0 in Fedora 24 repos. It will be much less stressful.
There was talk last cycle about adjusting fedora-repos for nogpg check until bodhi enablement, but it means another fedora-repos update.
It was asked many times here and around during last few days. Here [1], here [2] and may be more.
I can't see any workaround to manage builds on copr and this is broken for a few days ...
It will be fixed as soon as the branched compose lands today. As lots of people have mentioned.
kevin
On Qua, 2016-03-09 at 09:59 -0700, Kevin Fenzi wrote:
On Wed, 09 Mar 2016 16:35:17 +0000 Sérgio Basto sergio@serjux.com wrote:
Meanwhile , can't we hack copr , with gpgcheck=0 in Fedora 24 repos. It will be much less stressful.
There was talk last cycle about adjusting fedora-repos for nogpg check until bodhi enablement, but it means another fedora-repos update.
It was asked many times here and around during last few days. Here [1], here [2] and may be more.
I can't see any workaround to manage builds on copr and this is broken for a few days ...
It will be fixed as soon as the branched compose lands today. As lots of people have mentioned.
Build of (...) for fedora-24-x86_64 finished with 'success', is working again as you wrote .
Thanks.
kevin
On Ter, 2016-03-08 at 14:49 +0100, Jakub Jelen wrote: Meanwhile , can't we hack copr , with gpgcheck=0 in Fedora 24 repos. It will be much less stressful.
Please don't. Having unchecked code shipped and installed is a risk we don't need to take. How about signing every package instead, including rawhide/F24 at split time?
On Wed, 09 Mar 2016 21:10:14 -0000 "Christian Stadelmann" genodeftest@fedoraproject.org wrote:
On Ter, 2016-03-08 at 14:49 +0100, Jakub Jelen wrote: Meanwhile , can't we hack copr , with gpgcheck=0 in Fedora 24 repos. It will be much less stressful.
Please don't. Having unchecked code shipped and installed is a risk we don't need to take. How about signing every package instead, including rawhide/F24 at split time?
ok, one more time (I have lost count of how many times I have explained this, so perhaps I can just point to this mail from now. ;)
When we branch a new release off, but before bodhi is enabled, ie, the two weeks between
Branch Fedora 24 from Rawhide (Rawhide becomes future F25)
and
Bodhi activation point.
There is no gating in the branched release, it composes via cron every night (just as rawhide always does). We have a process that autosigns things (hurray!) but without a gate, there is no way we can be 100% sure that all packages are signed in each nights compose.
Lets take an example. Say the cron fires off at 5:15 UTC. The autosigner signs everything and we are 100% signed at 5:10 UTC. Then a texlive build finishes and is tagged into the repo. The autosigner starts signing it's 5000+ packages (including it's 1.xGB src.rpm that takes about 30min to sign). There's no way it can finish before the compose kicks off.
So, the only way we can ensure this is to gate things. We have talked about doing that for rawhide in the past, but just haven't done it yet. I suppose once we do we could use the same setup for branched for these two weeks. Until then, sorry.
kevin