On Tuesday, January 18, 2022 3:17:31 AM EST Neil Williams wrote: > On Mon, 17 Jan 2022 12:47:44 -0500 > > Louis-Philippe VĂ©ronneau <po...@debian.org> wrote: > > Hey folks, > > > > I'm following up on bug #1001677 [1] on the DPT's list to try to reach > > consensus, as I think the Lintian tags that were created to fix this > > bug are not recommending the proper thing. > > > > As a TL;DR for those of you who don't want to read the whole BTS > > thread, jdg saw that a bunch of packages were using `py3versions -r` > > in autopkgtests, and this fails when there's no X-Python3-Version > > variable in d/control. > > > > The fix that Lintian now proposes for packages that use `py3versions > > -r` in autopkgtests is to set X-Python3-Version. > > > > I think the proper fix would be to ask people to move away from > > `py3versions -r` if there is no X-Python3-Version, and use`py3versions > > -s` instead. > > Just as a general point, can I ask that - especially in a TL;DR - that > long option names are used or the context of each option is included as > the difference between -r and -s is not obvious from this email & not > everyone on the list uses py3versions routinely.
TIL py3versions has long option names ... -d, --default print the default python3 version -s, --supported print the supported python3 versions -r, --requested print the python3 versions requested by a build; the argument is either the name of a control file or the value of the X-Python3-Version attribute -i, --installed print the installed supported python3 versions Scott K
signature.asc
Description: This is a digitally signed message part.