[Pkg-ltsp-devel] Bug#831409: Bug#831409: ltsp-client lacks gnupg / gnupg2 for apt-key to work

[Vagrant Cascadian]

On 2016-07-15, Wolfgang Schweer <wschweer at arcor.de> wrote:
> while testing Debian Edu stretch I noticed that the LTSP chroot failed 
> to build.
>
> This is most probably caused by a recent change to apt, see: #830696
>
> I faced this error too:
> Error: gnupg or gnupg2 do not seem to be installed,
> Error: but apt-key requires gnupg or gnupg2 for this operation.

Thanks for the report!


> Adding gnupg or gnupg2 to the early packages list was to no avail.
> But after commenting out the apt-key call the chroot was built.
>
> Not quite sure, but I guess gnupg2 | gnupg might be needed as 
> Pre-Depends of ltsp-client.

No, ltsp-build-client on the server calls apt-keys within the chroot
before installing ltsp-client* (during the same pass that early-packages
is installed), so this needs to happen earlier.

I *think* it needs to be added to debootstrap's --include= to ensure it
is installed early enough (or setting DEBOOTSTRAP_INCLDUE=gnupg or
DEBOOTSTRAP_INCLUDE=gnupg2).

Alternately, maybe dropping the appropriate keys into
/etc/apt/trusted.gpg.d/ would work without requiring installing
additional software (need to verify that it doesn't downgrade to
accepting unsigned repositories in this case); though that will likely
break support for older releases.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ltsp-devel/attachments/20160717/ce559387/attachment.sig>