Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#54687 - [debian-archive-keyring] build fails due to signature error

Attached to Project: Community Packages
Opened by Erich Eckner (deepthought) - Tuesday, 04 July 2017, 10:07 GMT
Last edited by Felix Yan (felixonmars) - Wednesday, 13 December 2017, 09:35 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

the build failes:
...
gpg: WARNING: unsafe permissions on homedir '/build/.gnupg'
gpg: Signature made Thu 25 May 2017 08:30:03 PM CEST
gpg: using RSA key C5CE5DC2C542CD59
gpg: BAD signature from "Adam D. Barratt <adam@adam-barratt.org.uk>" [unknown]
make: *** [Makefile:17: verify-results] Error 1
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/staging-x86_64/erich/build

Additional info:
* package version(s)
pkgname=debian-archive-keyring
pkgver=2017.5
pkgrel=1
* config and/or log files etc.
full log attached

Steps to reproduce:
> git clone 'https://git.archlinux.org/svntogit/community.git/'
> cd community.git
> git checkout 672d6ab8b321c46d5dc2d54feb1a1b9108302b1b
> cd debian-archive-keyring/trunk
> staging-x86_64-build

Is this an upstream bug or is some auto-key retrieval yet to be activated somewhere (it is activated in /build/.gnupg/gpg.conf)?

Cheers,
deep42thought
   log (11.4 KiB)
This task depends upon

Closed by  Felix Yan (felixonmars)
Wednesday, 13 December 2017, 09:35 GMT
Reason for closing:  None
Comment by Felix Yan (felixonmars) - Tuesday, 04 July 2017, 14:44 GMT
Unfortunately this is due to mismatch versions of GnuPG. You can retrieve one that matches the Debian version from our Package Archive and build with it.
Comment by Erich Eckner (deepthought) - Tuesday, 04 July 2017, 15:46 GMT
Thanks for the info.
btw.: I'm trying to build it for the archlinux32 project.

How do I find out what version of gnupg I need for that?
Will it (probably) be the same in the future?
Comment by Felix Yan (felixonmars) - Tuesday, 04 July 2017, 16:24 GMT
You can find that on the Debian package info page:

https://packages.debian.org/sid/gnupg

It could be the same as Arch in the future, but there's no promise.
Comment by Erich Eckner (deepthought) - Wednesday, 05 July 2017, 09:20 GMT
Maybe you could add a version in the dependencies?

something like

gnupg=2.1.18

or more elaborate:

gnupg=$(
curl 'https://packages.debian.org/sid/gnupg' 2> /dev/null | \
sed -n '
/Package:\sgnupg/{
s/^.*(\([^-]\+\)-.*$/\1/
p
}
'
)
Comment by Erich Eckner (deepthought) - Wednesday, 05 July 2017, 12:00 GMT
If I do a 'pacman -U gnupg-2.1.18-2.pkg.tar.xz', it still does not build (same error).
Comment by Erich Eckner (deepthought) - Sunday, 09 July 2017, 19:06 GMT
ah, sry, my bad: I installed gnupg 2.1.18-2 _outside_ of the chroot :-/
It works with gnupg=2.1.18 inside. You can close the bug (and maybe add the version to the dependency?).

Cheers,
deep42thought
Comment by Balló György (City-busz) - Monday, 10 July 2017, 07:59 GMT
I think we should remove this package from the [community] repository if we can't ensure that it builds with GnuPG from [core].
Comment by Felix Yan (felixonmars) - Wednesday, 13 December 2017, 09:34 GMT
The current 2017.6-1 version builds fine now. I'll patch the build script if it breaks in the future.

Loading...