Hi Adam, Adam D. Barratt <a...@adam-barratt.org.uk> (2024-08-14): > choose-mirror is the d-i component responsible for presenting users > with a list of available mirrors from which packages can be installed. > The list it provides is periodically updated based on the "masterlist" > maintained by the Mirrors Team. > > I'd like to suggest that we get in the habit of updating the choose- > mirror package more often, in order to provide a more current mirror > list to d-i users. Most changes to the package consist of updates to > the mirror list, or to translations of the included Debconf templates. > > Assuming that people are happy with the idea, a few questions on how we > go about it: > - Would it be preferred that updates follow the usual path of an upload > to unstable followed by backports to stable and (when supported) > oldstable? I've presumed that d-i won't have any issues with ~debXuY > versions for udeb packages. > - From the Release Team side, would people want p-u bugs filing each > time, or could choose-mirror be considered to have a semi-permanent > exception?
I'm not sure which version to start from (current version in stable or an initial backport from unstable — unless there's a compelling reason for the latter, I'd rather go for the former, having had 0 looks at all at this point), but it seems to me we could just increment the version in stable, independently from what's happening (or not) in unstable? That'd just follow what we do for src:debian-installer itself (minus prop-up fun, as we already have some newer package in unstable). If we were to do that, skipping paperwork would have my preference. But it seems I'm regularly at odds with the rest of the release team so who knows… > Opinions / objections / octopuses welcome. I'd like an octopus too, please. Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
