Your message dated Sat, 18 Jan 2025 16:45:39 +0100
with message-id <[email protected]>
and subject line Re: Bug#1002819: autopkgtest: --pin-packages assumes that the
release has a "Suite" name
has caused the Debian Bug report #1002819,
regarding autopkgtest: --pin-packages assumes that the release has a "Suite"
name
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.)
--
1002819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002819
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: autopkgtest
Version: 5.19
Severity: normal
User: [email protected]
Usertags: origin-kali
X-Debbugs-Cc: [email protected]
Usage of --pin-packages=kali-dev=src:foo results in a file like this
in /etc/apt/preferences.d/autopkgtest-kali-dev
Package: foo
Pin: release a=kali-dev
Pin-Priority: 995
Unfortunately the "a=kali-dev" only matches on the "Suite" or "Archive"
field in the Release file, and not on the "Codename" field (which in my
caces was the only field available).
I noticed that /etc/apt/preferences.d/autopkgtest-default-release uses
another syntax that seems to cover more cases:
Package: *
Pin: release kali-rolling
Pin-Priority: 990
However that syntax doesn't seem to be documented in apt_preferences.
If it's correct and allows to check on either of the 3 fields, then
we should likely use the same syntax in both files.
Otherwise I would like to suggest to create two entries, one with
"Pin: release a=foo" and one with "Pin: release n=foo" so that
we are sure to match on any of the 3 fields.
Cheers,
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'oldoldstable'), (500,
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.15.0-2-amd64 (SMP w/16 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages autopkgtest depends on:
ii apt-utils 2.3.13
ii libdpkg-perl 1.21.1
ii procps 2:3.3.17-5
ii python3 3.9.8-1
ii python3-debian 0.1.42
Versions of packages autopkgtest recommends:
ii autodep8 0.25
Versions of packages autopkgtest suggests:
pn fakemachine <none>
pn lxc <none>
pn lxd <none>
ii ovmf 2021.11-1
pn ovmf-ia32 <none>
pn qemu-efi-aarch64 <none>
pn qemu-efi-arm <none>
pn qemu-system <none>
ii qemu-utils 1:6.1+dfsg-8+b2
ii schroot 1.6.10-12
ii vmdb2 0.24-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Raphael,
On Wed, 11 Sep 2024 13:47:49 +0200 Paride Legovini <[email protected]>
wrote:
I think I accidentally fixed this bug in this MR:
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/425
This has been release a while back. I'm closing the issue assuming
Paride was right. Please reopen if you still experience this issue.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
