On 2024-09-06 13:50, Simon McVittie wrote:
> According to debian/README.source (which was written when Ubuntu 22.04
> was current), our policy is:
> 
>> If it's straightforward to avoid a newer dependency without too much
>> extra code, we can consider extending [the supported host system] to:
>>
>> - previous Debian stable
>> - previous Ubuntu LTS
>>
>> As of mid 2023, this means Debian 11, Ubuntu 20.04 and Python 3.8.
> 
> Now that Ubuntu 24.04 is current, I'd like to officially increase the
> recommended host system to Debian 12 or Ubuntu 24.04, and increase the
> minimum to Debian 11 or Ubuntu 22.04. That would mean we can rely on
> Python 3.9:
> 
> - replace List[Set[str]] with list[set[str]], etc.
> - dict1 | dict2
> - str.removeprefix, str.removesuffix
> - pathlib.Path.readlink
> - stderr is line-buffered
> 
> Please check whether any Ubuntu infrastructure is relying on being able
> to run a current version of autopkgtest on a 20.04 host system.

This _is_ the case, however I believe autopkgtest development should not
stop because of this. It's up to us Ubuntu people to upgrade the
infrastructure, and the "previous Ubuntu LTS" commitment we make in in
d/README.source is more than reasonable.

> We could also consider changing the policy from "previous Debian stable"
> to "previous Debian stable, if still supported outside LTS", which
> would mean we can drop Debian 11 support now that it has moved to LTS,
> and rely on Debian 12 or Ubuntu 22.04, with Python 3.10:

I think this is reasonable.

> Note that this is about the supported host OS version (host for VMs,
> containers, etc.). For the the testbed (the system under test, inside VMs,
> containers, etc.) we continue to allow very old versions, although this
> is "at risk" until/unless someone from Debian (E)LTS or Ubuntu ESM can
> fix #1078445.

(OT: speaking of #1078445, I replied there some time ago, basically
saying that it does not look like a bug to me. I'll check again in case
I overlooked anything, but please check my comment on the culprit maybe
being your apt-cacher-ng.)

Reply via email to