Bug #15618

Build fails if `config/chroot_local-packages` contains packages

Added by segfault 2018-05-24 15:38:29 . Updated 2018-05-25 10:18:39 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2018-05-24
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

I tried this once with the packages I built for VeraCrypt (Feature #15521), and then again with an existing Debian package (https://packages.debian.org/stretch/amd64/vim/download). In both cases the build fails with:

P: Configuring file /etc/apt/sources.list
gpg: WARNING: unsafe permissions on homedir '/root/.gnupg'
gpg: keybox '/root/.gnupg/pubring.kbx' created
gpg: agent_genkey failed: Inappropriate ioctl for device
gpg: key generation failed: Inappropriate ioctl for device
cp: cannot create regular file 'cache/': Not a directory
P: Begin unmounting filesystems...

Subtasks


History

#1 Updated by segfault 2018-05-24 15:39:27

  • blocks Feature #14481: Release Beta for VeraCrypt support in Tails added

#2 Updated by segfault 2018-05-24 15:41:00

intrigeri, do you have any idea what’s the issue here or where I should start investigating?

#3 Updated by segfault 2018-05-24 16:52:02

  • blocked by deleted (Feature #14481: Release Beta for VeraCrypt support in Tails)

#4 Updated by intrigeri 2018-05-25 06:31:11

> intrigeri, do you have any idea what’s the issue here

No, sorry :/

> or where I should start investigating?

You could find a way to run live-build in debug mode to get more details but at first glance:

It may be that our live-build 2.x fork does not support GnuPG 2.x. I believe what breaks is the key generation in scripts/build/lb_chroot_sources and then cp chroot/root/local-package-keyring.* cache/. I would look at how this code looks like in current live-build versions: perhaps there are some fixes for GnuPG 2.x (or some other Stretch change) that we could backport to our live-build 2.x fork.

#5 Updated by intrigeri 2018-05-25 10:18:39

… but IMO don’t bother for now: focus on Feature #14481 without this feature.