Unable to compile systemd in a clean chroot [solved]

graysky · 2017-07-03 11:33:14

I pulled down our systemd package to build locally but am hitting errors when I try building... why It works if I comment out the call to _validate_tag in prepare().

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
 there is nothing to do
==> Making package: systemd 233-6 (Mon Jul  3 07:31:05 EDT 2017)
==> Retrieving sources...
  -> Cloning systemd git repo...
Cloning into bare repository '/scratch/systemd/trunk/systemd'...
remote: Counting objects: 214035, done.
remote: Compressing objects: 100% (211/211), done.
remote: Total 214035 (delta 141), reused 33 (delta 16), pack-reused 213808
Receiving objects: 100% (214035/214035), 74.90 MiB | 10.41 MiB/s, done.
Resolving deltas: 100% (163406/163406), done.
  -> Found initcpio-hook-udev
  -> Found initcpio-install-systemd
  -> Found initcpio-install-udev
  -> Found arch.conf
  -> Found loader.conf
  -> Found splash-arch.bmp
  -> Found systemd-user.pam
  -> Found systemd-hwdb.hook
  -> Found systemd-sysusers.hook
  -> Found systemd-tmpfiles.hook
  -> Found systemd-update.hook
==> Validating source files with sha512sums...
    systemd ... Skipped
    initcpio-hook-udev ... Passed
    initcpio-install-systemd ... Passed
    initcpio-install-udev ... Passed
    arch.conf ... Passed
    loader.conf ... Passed
    splash-arch.bmp ... Passed
    systemd-user.pam ... Passed
    systemd-hwdb.hook ... Passed
    systemd-sysusers.hook ... Passed
    systemd-tmpfiles.hook ... Passed
    systemd-update.hook ... Passed
==> Making package: systemd 233-6 (Mon Jul  3 07:31:17 EDT 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found initcpio-hook-udev
  -> Found initcpio-install-systemd
  -> Found initcpio-install-udev
  -> Found arch.conf
  -> Found loader.conf
  -> Found splash-arch.bmp
  -> Found systemd-user.pam
  -> Found systemd-hwdb.hook
  -> Found systemd-sysusers.hook
  -> Found systemd-tmpfiles.hook
  -> Found systemd-update.hook
==> Validating source files with sha512sums...
    systemd ... Skipped
    initcpio-hook-udev ... Passed
    initcpio-install-systemd ... Passed
    initcpio-install-udev ... Passed
    arch.conf ... Passed
    loader.conf ... Passed
    splash-arch.bmp ... Passed
    systemd-user.pam ... Passed
    systemd-hwdb.hook ... Passed
    systemd-sysusers.hook ... Passed
    systemd-tmpfiles.hook ... Passed
    systemd-update.hook ... Passed
==> Extracting sources...
  -> Creating working copy of systemd git repo...
Cloning into 'systemd'...
done.
Switched to a new branch 'makepkg'
==> Starting prepare()...
==> ERROR: failed to validate tag v233

==> ERROR: A failure occurred in prepare().
    Aborting...

Last edited by graysky (2017-07-09 16:32:44)

WorMzy · 2017-07-06 13:22:23

No problems here. What does cd-ing to the checked out repository and running 'git verify-tag --raw "v233"' manually return?

For comparison:

/var/lib/archbuild/extra-x86_64/wormzy/build/systemd/src/systemd> git verify-tag --raw "v233"
[GNUPG:] NEWSIG
[GNUPG:] KEY_CONSIDERED 63CDA1E5D3FC22B998D20DD6327F26951A015CC4 0
[GNUPG:] SIG_ID mULO8AbbxaZE+t81YrkN3zvvY3o 2017-03-01 1488405946
[GNUPG:] KEY_CONSIDERED 63CDA1E5D3FC22B998D20DD6327F26951A015CC4 0
[GNUPG:] GOODSIG B63B21879C3485B0 Lennart Poettering <lennart@poettering.net>
[GNUPG:] VALIDSIG 16B1C4EEC0BC021AC777F681B63B21879C3485B0 2017-03-01 1488405946 0 4 0 1 2 00 63CDA1E5D3FC22B998D20DD6327F26951A015CC4
[GNUPG:] KEY_CONSIDERED 63CDA1E5D3FC22B998D20DD6327F26951A015CC4 0
[GNUPG:] TRUST_UNDEFINED 0 pgp

eschwartz · 2017-07-07 01:57:22

The error seems blatantly obvious. You failed to verify the tag, just as the "==> ERROR: failed to validate tag v233" said.

As with all packages that contain GPG signatures, have you imported the key listed in validpgpkeys?

graysky · 2017-07-09 16:32:32

@Eschwartz - Thank you, that was the problem. In the past I recall makepkg erroring out on the singing step if a key was omitted. Since this error wasn't so verbose, I didn't consider it.

eschwartz · 2017-07-09 17:23:29

Well, the difference is that makepkg itself handles failures on GPG-signed *files*, but doesn't -- yet -- implement support for GPG-signed git repositories.

As soon as pacman 5.1 is released, makepkg will support sources like "git+https://example.com/foo.git#tag=${pkgver}?signed" and the same logic that is used for files with an accompanying .asc/.sig/.sign will also do the GPG checks on the referenced tag or commit or branch HEAD (still commit).
In the meantime, the systemd package reimplemented that check in prepare(), although it seems it doesn't implement checks for status=missingkey

See the last three commits here for details: pacman.git: log for commit 37a89e2fac704babbe3badf0d9df0d41ec622f6f

Last edited by eschwartz (2017-07-09 17:24:19)

Arch Linux

#1 2017-07-03 11:33:14

Unable to compile systemd in a clean chroot [solved]

#2 2017-07-06 13:22:23

Re: Unable to compile systemd in a clean chroot [solved]

#3 2017-07-07 01:57:22

Re: Unable to compile systemd in a clean chroot [solved]

#4 2017-07-09 16:32:32

Re: Unable to compile systemd in a clean chroot [solved]

#5 2017-07-09 17:23:29

Re: Unable to compile systemd in a clean chroot [solved]

Board footer