Hi there!
To be clear, I'm in Athens atm and I don't really have time now to look
better at this, but:

On Tue, Dec 01, 2015 at 02:13:07PM -0800, Vagrant Cascadian wrote:
> Hey, I think all of the second builds on armhf are failing to set up the
> build environment:
>   https://reproducible.debian.net/logs/unstable/armhf/gb_0.3.2-1.build2.log.gz
>   I: Installing the build-deps
>   I: user script 
> /srv/workspace/pbuilder/5651/tmp/hooks/D01_modify_environment starting
>   FATAL: kernel too old

This must me some toolchain stuff.  That menas something inside the hook
failed, and thanks to `set -e` (luckily) the whole script failed, so did
the build.  The head of that script is:

    set -e
    # exit if we are in the same UTS namespace as init ( != 2nd build )
    [ "$(readlink /proc/1/ns/uts)" = "$(readlink /proc/self/ns/uts)" ] && exit 0
    echo "I: Changing host+domainname to test build reproducibility" >&2

Given that I don't the text on that echo, I've got to assume it fails
eariler, but I can't even think how...

> Also saw this message on an amd64/experimental build, although much
> later in the build environment setup:
> https://reproducible.debian.net/logs/experimental/amd64/python-letsencrypt_0.0.0.dev20151123-1.build2.log.gz
>   Traitement des actions différées (« triggers ») pour libc-bin (2.21-1)...
>   FATAL: kernel too old
>   Segmentation fault
>   FATAL: kernel too old
>   Segmentation fault
>   dpkg: erreur de traitement du paquet libc-bin (--unpack)
> Hrm.

Just looking at the error triggers no ideas to me... boooh

                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  http://mapreri.org                              : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature

Reproducible-builds mailing list

Reply via email to