You are not logged in.
Hi!
When using extra-*-build, how should it be handled when "One or more PGP signatures could not be verified"?
I could of course chroot into it and import the key manually or change the settings to not require those checks... but wouldn't that be kind of counterproductive, since I'm using extra-*-build to make sure it builds fine on a "fresh" system in the first place?
Am I forgetting about anything that needs to be added to the PKGBUILD (the key is in validpgpkeys; what else)? Anything I should check for?
Last edited by whoops (2017-01-02 11:31:20)
Offline
The keys need to be in the keyring of the user calling the build script (or that user needs auto-key-retrieve enabled).
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Doesn't extra-*-build (/ makechrootpkg) delete & recreate the whole build user and directory every time it starts?
edit: not sure, don't understand the whole script... but this looks suspicious:
grep "builduser" -n1 $(which makechrootpkg) | grep "passwd" -n1
7-398- # an x86_64 host).
8:399: sed -e '/^builduser:/d' -i "$copydir"/etc/{passwd,group}
9-400: printf >>"$copydir/etc/group" 'builduser:x:%d:\n' $builduser_gid
10:401: printf >>"$copydir/etc/passwd" 'builduser:x:%d:%d:builduser:/build:/bin/bash\n' $builduser_uid $builduser_gid
Last edited by whoops (2017-01-02 12:44:50)
Offline