7:41 a.m.
dustymabe reported a new issue against the project: `releng` that you are following:
``
packages aren't signed in f26 tag which means our compose fails:
https://kojipkgs.fedoraproject.org/compose/branched/Fedora-26-20170610.n....
list of packages here:
<!!image>
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6833
4:46 p.m.
parasense added a new comment to an issue you are following:
``
So I signed those things.
Here is the list of packages I parsed out of your pungi logs:
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/aarch64/owncloud-client-2.3.2-1.fc26.aarch64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/aarch64/owncloud-client-caja-2.3.2-1.fc26.aarch64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/aarch64/owncloud-client-debuginfo-2.3.2-1.fc26.aarch64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/aarch64/owncloud-client-devel-2.3.2-1.fc26.aarch64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/aarch64/owncloud-client-dolphin-2.3.2-1.fc26.aarch64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/aarch64/owncloud-client-libs-2.3.2-1.fc26.aarch64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/aarch64/owncloud-client-nautilus-2.3.2-1.fc26.aarch64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/aarch64/owncloud-client-nemo-2.3.2-1.fc26.aarch64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/armv7hl/owncloud-client-2.3.2-1.fc26.armv7hl.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/armv7hl/owncloud-client-caja-2.3.2-1.fc26.armv7hl.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/armv7hl/owncloud-client-debuginfo-2.3.2-1.fc26.armv7hl.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/armv7hl/owncloud-client-devel-2.3.2-1.fc26.armv7hl.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/armv7hl/owncloud-client-dolphin-2.3.2-1.fc26.armv7hl.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/armv7hl/owncloud-client-libs-2.3.2-1.fc26.armv7hl.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/armv7hl/owncloud-client-nautilus-2.3.2-1.fc26.armv7hl.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/armv7hl/owncloud-client-nemo-2.3.2-1.fc26.armv7hl.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/i686/owncloud-client-2.3.2-1.fc26.i686.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/i686/owncloud-client-caja-2.3.2-1.fc26.i686.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/i686/owncloud-client-debuginfo-2.3.2-1.fc26.i686.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/i686/owncloud-client-devel-2.3.2-1.fc26.i686.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/i686/owncloud-client-dolphin-2.3.2-1.fc26.i686.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/i686/owncloud-client-libs-2.3.2-1.fc26.i686.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/i686/owncloud-client-nautilus-2.3.2-1.fc26.i686.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/i686/owncloud-client-nemo-2.3.2-1.fc26.i686.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64le/owncloud-client-2.3.2-1.fc26.ppc64le.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64le/owncloud-client-caja-2.3.2-1.fc26.ppc64le.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64le/owncloud-client-debuginfo-2.3.2-1.fc26.ppc64le.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64le/owncloud-client-devel-2.3.2-1.fc26.ppc64le.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64le/owncloud-client-dolphin-2.3.2-1.fc26.ppc64le.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64le/owncloud-client-libs-2.3.2-1.fc26.ppc64le.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64le/owncloud-client-nautilus-2.3.2-1.fc26.ppc64le.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64le/owncloud-client-nemo-2.3.2-1.fc26.ppc64le.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64/owncloud-client-2.3.2-1.fc26.ppc64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64/owncloud-client-caja-2.3.2-1.fc26.ppc64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64/owncloud-client-debuginfo-2.3.2-1.fc26.ppc64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64/owncloud-client-devel-2.3.2-1.fc26.ppc64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64/owncloud-client-dolphin-2.3.2-1.fc26.ppc64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64/owncloud-client-libs-2.3.2-1.fc26.ppc64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64/owncloud-client-nautilus-2.3.2-1.fc26.ppc64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/ppc64/owncloud-client-nemo-2.3.2-1.fc26.ppc64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/x86_64/owncloud-client-2.3.2-1.fc26.x86_64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/x86_64/owncloud-client-caja-2.3.2-1.fc26.x86_64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/x86_64/owncloud-client-debuginfo-2.3.2-1.fc26.x86_64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/x86_64/owncloud-client-devel-2.3.2-1.fc26.x86_64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/x86_64/owncloud-client-dolphin-2.3.2-1.fc26.x86_64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/x86_64/owncloud-client-libs-2.3.2-1.fc26.x86_64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/x86_64/owncloud-client-nautilus-2.3.2-1.fc26.x86_64.rpm
/mnt/koji/packages/owncloud-client/2.3.2/1.fc26/data/signed/64dab85d/x86_64/owncloud-client-nemo-2.3.2-1.fc26.x86_64.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/aarch64/powertop-2.9-1.fc26.aarch64.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/aarch64/powertop-debuginfo-2.9-1.fc26.aarch64.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/armv7hl/powertop-2.9-1.fc26.armv7hl.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/armv7hl/powertop-debuginfo-2.9-1.fc26.armv7hl.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/i686/powertop-2.9-1.fc26.i686.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/i686/powertop-debuginfo-2.9-1.fc26.i686.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/ppc64le/powertop-2.9-1.fc26.ppc64le.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/ppc64le/powertop-debuginfo-2.9-1.fc26.ppc64le.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/ppc64/powertop-2.9-1.fc26.ppc64.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/ppc64/powertop-debuginfo-2.9-1.fc26.ppc64.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/x86_64/powertop-2.9-1.fc26.x86_64.rpm
/mnt/koji/packages/powertop/2.9/1.fc26/data/signed/64dab85d/x86_64/powertop-debuginfo-2.9-1.fc26.x86_64.rpm
I've no idea what the back story is on this topic, I see owncloud-client was pushed to
stable like ~yesterday so that tells me it WAS signed yesterday.
I happen to mirror fedora-encilada on a nightly basis, so I looked in my personal
mirror.
$ rpm -qp --qf='%{NAME}-%{VERSION}-%{RELEASE} %{SIGPGP:pgpsig}
%{SIGGPG:pgpsig}\n' owncloud-client-2.2.4-6.fc26.x86_64.rpm
warning: owncloud-client-2.2.4-6.fc26.x86_64.rpm: Header V3 RSA/SHA256 Signature, key
ID 64dab85d: NOKEY
owncloud-client-2.2.4-6.fc26 RSA/SHA256, Sun 12 Feb 2017 07:34:20 AM CST, Key ID
812a6b4b64dab85d (none)
So it appears that is was signed with the right key 64dab85d (the last 8 chars of the key
ID.
This would make for an interesting root cause analysis.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6833
4:47 p.m.
The issue: `some rpms in f26 tag aren't signed - compose fails` of project: `releng`
has been assigned to `parasense` by parasense.
https://pagure.io/releng/issue/6833
5:47 p.m.
dustymabe added a new comment to an issue you are following:
``
@parasense - so you're saying that they 'were signed' and now they are
'not signed' ?
This is another thing I thought was interesting:
```
[dustymabe@media Renewal_2017-06 (master %)]$ koji latest-build f26 powertop
Build Tag Built by
---------------------------------------- -------------------- ----------------
powertop-2.9-1.fc26 f26 jskarvad
+[dustymabe@media Renewal_2017-06 (master %)]$ koji latest-build f26-updates-testing
powertop
Build Tag Built by
---------------------------------------- -------------------- ----------------
powertop-2.8-5.fc26 f26-updates-testing releng
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6833
10:40 a.m.
kevin added a new comment to an issue you are following:
``
These are all caused I think by corner cases in obsoletion in bodhi.
If a new update is submitted while an old one exists that has different packages, or is
locked or is submitted for stable already the new update will not obsolete it and they
will both exist. Then when we push all the updates, whatever one that happens to be tagged
last gets in stable updates, and the other one(s) do not. Many (all?) of these were
packages in the python mini-mass rebuild update... so that was there with it's 112
packages and then maintainers submitted newer builds as updates.
The signing issue happened this time because this freeze was so long, packages that were
not tagged had their signed copies garbage collected.
To fix this right now: we need to make sure that the newer version of each of those
packages is tagged into f26 (or untagged and retagged).
To fix this long term: https://github.com/fedora-infra/bodhi/issues/1266
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6833
11:09 a.m.
kevin added a new comment to an issue you are following:
``
I fixed those 4 packages and restarted a f26 compose...
I think @limb might have a script to check for more cases of these?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6833
11:59 a.m.
dustymabe added a new comment to an issue you are following:
``
I fixed those 4 packages and restarted a f26 compose...
Were there only 4 packages that had a problem? The log i linked to had a lot of packages
that it said were unsigned.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6833
12:17 p.m.
kevin added a new comment to an issue you are following:
``
Ah yeah, there were 2 more... I just fixed them.
There were only 6 source packages... with all their various binary packages in the various
arches/etc.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6833
12:39 p.m.
limb added a new comment to an issue you are following:
``
I fixed those 4 packages and restarted a f26 compose...
I think @limb might have a script to check for more cases of these?
Sort of. I have a script that checks my local yum repo against a folder in my mailbox,
and I don't have f26 there yet. I think @pingou has something better.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6833
7:43 a.m.
mohanboddu added a new comment to an issue you are following:
``
Closing this ticket since we got a working compose.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6833
7:43 a.m.
The status of the issue: `some rpms in f26 tag aren't signed - compose fails` of
project: `releng` has been updated to: Closed as Fixed by mohanboddu.
https://pagure.io/releng/issue/6833
2512
days inactive
2518
days old
rel-eng@lists.fedoraproject.org
10 comments
5 participants
participants (5)
-
Dusty Mabe -
Jon Ciesla
-
Jon Disnard
-
Kevin Fenzi
-
Mohan Boddu