DevHeads.net

a rawhide build not tagged into f27-build

Hi,

My build of updated poppler in Rawhide was not tagged into f27-build
automatically, as it used to be in the past:

$ koji wait-repo --build=`fedpkg verrel` f27-build
Warning: nvr poppler-0.53.0-1.fc27 is not current in tag f27-build
latest build in f27-build is poppler-0.52.0-1.fc26

I had to tag it manually to be able to proceed with rebuilds of
depending packages. Is that a misconfiguration in koji? Or is it an
expected behavior now?

D.

Comments

Re: a rawhide build not tagged into f27-build

By Peter Robinson at 03/28/2017 - 09:51

Nothing has ever got tagged into f27-build. The builds for that get
inherited from f27. All builds now go via f27-pending (as has been
advertised on this list and announce etc) where they currently just
get signed but eventually there will also be CI run at this point, but
they will then automatically go to f27 once signing is done. This did
happen in the case of your poppler NVR but you just didn't wait long
enough.

I have untagged poppler-0.53.0-1.fc27 from f27-build as that's not
where it's meant to go.

Re: a rawhide build not tagged into f27-build

By David Tardon at 03/30/2017 - 07:04

Hi,

On Tue, Mar 28, 2017 at 03:51:48PM +0100, Peter Robinson wrote:
So how long is this supposed to take? texlive-2016-34.20160520.fc27
finished during the night and it's still only in f27-pending more than
12 hours later.

D.

Re: a rawhide build not tagged into f27-build

By =?ISO-8859-1?Q?... at 03/30/2017 - 07:44

Dne 30.3.2017 v 14:04 David Tardon napsal(a):
It is ~million packages, so it takes some time. But it is definitely
annoying that it is not possible to see the status if the signing still
goes on or it is stuck somewhere ....

Vít

Re: a rawhide build not tagged into f27-build

By Kevin Fenzi at 03/30/2017 - 14:42

On 03/30/2017 06:44 AM, Vít Ondruch wrote:
Normally texlive takes 2-3hours I think. But it shouldn't take 12 for
sure. I'm manually finishing the signing on it and will get it tagged in
as soon as thats done.

After alpha is out we are going to rebuild the sign bridge with a bigger
disk. It might be that it's hitting that capacity because currently the
autosigner does a batch of all rpms in a package (so for texlive ~5000
or more). Additionally, we are going to implement a backoff where if it
tires to sign all rpms in a package and fails, it retries with a small
batch size.
Well, you can see the signing fedmsgs... so you can tell if it's still
signing or not and what package(s) it's on.

kevin

Re: a rawhide build not tagged into f27-build

By David Tardon at 03/28/2017 - 13:02

Hi,

On Tue, Mar 28, 2017 at 03:51:48PM +0100, Peter Robinson wrote:
Thanks for the explanation. It seems I missed this announcement or
didn't pay enough attention to it. And I am unable to find it now...

D.