Bug#1002819: autopkgtest: --pin-packages assumes that the release has a "Suite" name

2023-02-02 Thread Raphael Hertzog
(Adding Colin Watson as he might have feedback on Ubuntu's uses of the various Release fields and on the likeliness to fix/change them) Hello, On Wed, 01 Feb 2023, Paul Gevers wrote: > > I fear I've probably forgotten most of these details, so please pardon > > me for this response… Wasn't the

Bug#1002819: autopkgtest: --pin-packages assumes that the release has a "Suite" name

2023-02-01 Thread Paul Gevers
Hi, Sorry it took so long. On 02-01-2022 01:43, Iain Lane wrote: On Sat, Jan 01, 2022 at 10:05:21PM +0100, Paul Gevers wrote: Hi Raphael, On 01-01-2022 21:37, Raphael Hertzog wrote: On Fri, 31 Dec 2021, Paul Gevers wrote: Otherwise I would like to suggest to create two entries, one with

Bug#1002819: autopkgtest: --pin-packages assumes that the release has a "Suite" name

2022-01-01 Thread Iain Lane
Hey Paul, Raphael, happy new year to you, On Sat, Jan 01, 2022 at 10:05:21PM +0100, Paul Gevers wrote: > Hi Raphael, > > On 01-01-2022 21:37, Raphael Hertzog wrote: > > On Fri, 31 Dec 2021, Paul Gevers wrote: > > > > Otherwise I would like to suggest to create two entries, one with > > > > "Pin:

Bug#1002819: autopkgtest: --pin-packages assumes that the release has a "Suite" name

2022-01-01 Thread Paul Gevers
Hi Raphael, On 01-01-2022 21:37, Raphael Hertzog wrote: On Fri, 31 Dec 2021, Paul Gevers wrote: 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. I'll have to check and

Bug#1002819: autopkgtest: --pin-packages assumes that the release has a "Suite" name

2022-01-01 Thread Raphael Hertzog
Hi, On Fri, 31 Dec 2021, Paul Gevers wrote: > > 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. > > I'll have to check and think about this. I remember that I had

Bug#1002819: autopkgtest: --pin-packages assumes that the release has a "Suite" name

2021-12-31 Thread Paul Gevers
Hi Raphaël, Thanks for reporting. On 29-12-2021 11:44, Raphaël Hertzog wrote: 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

Bug#1002819: autopkgtest: --pin-packages assumes that the release has a "Suite" name

2021-12-29 Thread Raphael Hertzog
Control: tags -1 + patch Control: user de...@kali.org Control: usertag -1 + kali-patch On Wed, 29 Dec 2021, Raphaël Hertzog wrote: > I noticed that /etc/apt/preferences.d/autopkgtest-default-release uses > another syntax that seems to cover more cases: > > Package: * > Pin: release kali-rolling

Bug#1002819: autopkgtest: --pin-packages assumes that the release has a "Suite" name

2021-12-29 Thread Raphaël Hertzog
Package: autopkgtest Version: 5.19 Severity: normal User: de...@kali.org Usertags: origin-kali X-Debbugs-Cc: hert...@debian.org 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: