[elbe-devel] ELBE 12.1: pbuilder project creation fails

[Yegor Yefremov]

On Fri, Jan 10, 2020 at 11:38 AM Yegor Yefremov
<yegorslists at googlemail.com> wrote:
>
> I have successfully created a Debian 10 initvm. But when I try to
> create a pbuilder project I get this error message:
>
> I: debootstrap finished
> I: copying local configuration
> W: No local /etc/mailname to copy, relying on
> /var/cache/pbuilder/build/14516/etc/mailname to be correct
> I: Installing apt-lines
> I: Copy  /var/cache/elbe/327aa298-e401-4a9a-8182-92febada79ee/aptconfdir/apt.conf.d
>  to chroot
> I: user script /var/cache/pbuilder/build/14516/tmp/hooks/G10elbe_apt_sources
> starting
> W: --force-yes is deprecated, use one of the options starting with
> --allow instead.

What should be done with these warnings? Just remove this part in
elbepack/pbuilder.py?

# Make apt-get use --force-yes which is not specified by
# pbuilder-satisfy-depends
fp.write('APT::Get::force-yes "true";\n')

> W: --force-yes is deprecated, use one of the options starting with
> --allow instead.
> W: --force-yes is deprecated, use one of the options starting with
> --allow instead.
> W: --force-yes is deprecated, use one of the options starting with
> --allow instead.
> W: --force-yes is deprecated, use one of the options starting with
> --allow instead.
> W: --force-yes is deprecated, use one of the options starting with
> --allow instead.
> W: --force-yes is deprecated, use one of the options starting with
> --allow instead.
> Warning: apt-key output should not be parsed (stdout is not a terminal)
> W: --force-yes is deprecated, use one of the options starting with
> --allow instead.
> gpg: can't connect to the agent: IPC connect call failed
> Hit:1 http://ftp.debian.org//debian buster InRelease
> Get:2 http://127.0.0.1:8080/var/cache/elbe/327aa298-e401-4a9a-8182-92febada79ee/repo
> buster InRelease [2645 B]
> Get:3 http://ftp.debian.org/debian buster-backports InRelease [46.7 kB]
> Get:5 http://192.168.1.36/freight buster InRelease [2030 B]
> Get:4 http://security-cdn.debian.org buster/updates InRelease [65.4 kB]
> Err:2 http://127.0.0.1:8080/var/cache/elbe/327aa298-e401-4a9a-8182-92febada79ee/repo
> buster InRelease
>   The following signatures couldn't be verified because the public key
> is not available: NO_PUBKEY 8F5559AED64D8F15
> Get:6 http://ftp.debian.org/debian buster-backports/contrib armhf
> Packages [3812 B]
> Get:7 http://ftp.debian.org/debian buster-backports/non-free armhf
> Packages [6040 B]
> Get:8 http://ftp.debian.org/debian buster-backports/main armhf Packages [160 kB]
> Ign:5 http://192.168.1.36/freight buster InRelease
> Get:9 http://192.168.1.36/freight buster/main armhf Packages [2403 B]
> Get:10 http://security-cdn.debian.org buster/updates/main armhf
> Packages [167 kB]
> Reading package lists...
> W: --force-yes is deprecated, use one of the options starting with
> --allow instead.
> W: GPG error: http://127.0.0.1:8080/var/cache/elbe/327aa298-e401-4a9a-8182-92febada79ee/repo
> buster InRelease: The following signatures couldn't be verified
> because the public key is not available: NO_PUBKEY 8F5559AED64D8F15
> E: The repository
> 'http://127.0.0.1:8080/var/cache/elbe/327aa298-e401-4a9a-8182-92febada79ee/repo
> buster InRelease' is not signed.
> W: GPG error: http://192.168.1.36/freight buster InRelease: The
> following signatures couldn't be verified because the public key is
> not available: NO_PUBKEY 3053DFAD36C3FCD9
> W: Aborting with an error
> I: cleaning the build env
> I: removing directory /var/cache/pbuilder/build/14516 and its subdirectories
> [ERROR] Pbuilder failed
> Traceback (most recent call last):
>   File "/var/cache/elbe/devel/elbepack/asyncworker.py", line 252, in execute
>     self.project.create_pbuilder()
>   File "/var/cache/elbe/devel/elbepack/elbeproject.py", line 733, in
> create_pbuilder
>     os.path.join(self.builddir, "aptconfdir")))
>   File "/var/cache/elbe/devel/elbepack/shellhelper.py", line 115, in do
>     raise CommandError(cmd, p.returncode)
> CommandError
> Project build was not successful, current status: build_failed
> elbe control wait_busy Failed
> Giving up
>
> This is how the files are organized on the server. Btw during the SD
> card image creation, ELBE could get the packages from this local repo
> without problems:
>
> dists/           2019-07-08 11:10 -
> keyring.gpg  2019-07-08 11:10 3.0K
> pool/            2019-07-08 11:09 -
> pubkey.gpg  2019-07-08 11:10 4.0K
>
> Project definition in our xml file:
>
>         <project>
>                 <name>onrisc-baltos</name>
>                 <version>1.0</version>
>                 <description>
>                         debian buster rootfs for OnRISC devices
>                 </description>
>                 <buildtype>armhf</buildtype>
>                 <mirror>
>                         <primary_host>ftp.debian.org</primary_host>
>                         <primary_path>/debian</primary_path>
>                         <primary_proto>http</primary_proto>
>                         <url-list>
>                                 <url>
>
> <binary>http://192.168.1.36/freight buster main</binary>
>                                 </url>
>                                 <url>
>
> <binary>http://ftp.debian.org/debian buster-backports main non-free
> contrib</binary>
>
> <source>http://ftp.debian.org/debian buster-backports main non-free
> contrib</source>
>                                 </url>
>                                 <url>
>
> <binary>http://security.debian.org/ buster/updates main contrib
> non-free</binary>
>
> <source>http://security.debian.org/ buster/updates main contrib
> non-free</source>
>                                 </url>
>                         </url-list>
>                 </mirror>
>                 <noauth/>
>                 <suite>buster</suite>
>         </project>
>
> Any idea?
>
> ELBE version output: elbe v 12.1 Ubuntu 18.04
>
> Regards,
> Yegor