Your message dated Fri, 15 Mar 2024 11:43:39 +0100
with message-id <[email protected]>
and subject line Re: piuparts: breaks some salsa-ci tests
has caused the Debian Bug report #1064350,
regarding piuparts: breaks some salsa-ci tests
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1064350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064350
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: piuparts
Version: 1.3
Severity: serious
Hi,
I'm not sure whether this is caused by piuparts itself or by the way how
salsa-ci uses piuparts, but recently some piuparts tests run by salsa-ci
started to fail. So far I've only noticed this if salsa-ci.yml contains
SALSA_CI_COMPONENTS: 'main contrib non-free'
e.g. in this failure
https://salsa.debian.org/nvidia-team/bumblebee/-/jobs/5333059
...
0m0.2s DEBUG: sources.list:
deb http://deb.debian.org/debian sid main
deb http://deb.debian.org/debian sid contrib
deb http://deb.debian.org/debian sid non-free
...
0m0.2s DEBUG: Starting command: ['chroot', '/tmp/tmpz130bkq5', 'eatmydata',
'apt-get', 'update']
0m0.9s DUMP:
Hit:1 http://deb.debian.org/debian sid InRelease
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Sub-process apt-key returned an error code (29)Err:1
http://deb.debian.org/debian sid InRelease
gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Reading package lists...
W: An error occurred during the signature verification. The repository is not
updated and the previous index files will be used. GPG error:
http://deb.debian.org/debian sid InRelease: gpgv, gpgv2 or gpgv1 required for
verification, but neither seems installed
W: Failed to fetch http://deb.debian.org/debian/dists/sid/InRelease gpgv,
gpgv2 or gpgv1 required for verification, but neither seems installed
W: Some index files failed to download. They have been ignored, or old ones
used instead.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times
in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/debian.sources:1
W: Target Packages (main/binary-all/Packages) is configured multiple times in
/etc/apt/sources.list:1 and /etc/apt/sources.list.d/debian.sources:1
0m0.9s DEBUG: Command ok: ['chroot', '/tmp/tmpz130bkq5', 'eatmydata',
'apt-get', 'update']
...
apt-get update did not fail, but Packages for not-main are not loaded
resulting in subsequent installation failures of contrib or non-free
packages.
Another example where the test still succeeded 3 months ago:
https://salsa.debian.org/nvidia-team/python-pycuda/-/jobs/4920273
but fails today:
https://salsa.debian.org/nvidia-team/python-pycuda/-/jobs/5275149
Andreas
--- End Message ---
--- Begin Message ---
Version: 1.4
Hi Andreas,
On Tue, 20 Feb 2024 17:41:25 +0100 Andreas Beckmann <[email protected]> wrote:
> Package: piuparts
> Version: 1.3
> Severity: serious
>
> Hi,
>
> I'm not sure whether this is caused by piuparts itself or by the way how
> salsa-ci uses piuparts, but recently some piuparts tests run by salsa-ci
> started to fail. So far I've only noticed this if salsa-ci.yml contains
> SALSA_CI_COMPONENTS: 'main contrib non-free'
> e.g. in this failure
>
> https://salsa.debian.org/nvidia-team/bumblebee/-/jobs/5333059
>
> ...
> 0m0.2s DEBUG: sources.list:
> deb http://deb.debian.org/debian sid main
> deb http://deb.debian.org/debian sid contrib
> deb http://deb.debian.org/debian sid non-free
> ...
> 0m0.2s DEBUG: Starting command: ['chroot', '/tmp/tmpz130bkq5', 'eatmydata',
> 'apt-get', 'update']
> 0m0.9s DUMP:
> Hit:1 http://deb.debian.org/debian sid InRelease
> /usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
> /usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
> /usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
This seems like the same symptom as what was reported by Stefano in #1064842:
we used to ignore umask when creating the devices, but the changes uploaded in
1.3 ended up making piuparts honor umask, making the devices inaccessible under
some circumstances.
1.4, which I've just uploaded to fix the merged-/usr sync diversion, should
also fix this.
Cheers,
--
Nicolas Dandrimont
--- End Message ---
