Hi Vagrant,
On Sat, 08 Apr 2023 20:23:29 -0700, Vagrant Cascadian wrote:
> On 2023-04-08, Wouter Verhelst wrote:
> > This behavior is on purpose. The build system is used for the one on
> > salsa too, and there we *want* the name "testing" (as well as the name
> > "stable") to resolve to "whatever is current".
> >
> > The build is reused for the package, because we want to make 100% sure
> > that the contents of the package (at the time of the package build, at
> > least) is the same as what would be served on the website.
>
> This is probably because I am not understanding something, but how would
> you perform a security update or update for a stable point release?
The package contains metadata for external repositories. If the package
is updated, it is a good thing that the metadata is made more recent; it
makes no sense to provide metadata for repositories that are no longer
accessible.
I have not yet considered whether we want to provide common updates to
stable. Perhaps I should talk to the SRMs about that...
At any rate, the purpose of this package is to provide an alternative to
the online version of the same data that can be downloaded through a
pages.debian.net URL. Thus it should be as similar as possible to that
one.
> The package ends up shipping entirely different repository information
> based on when you happen to build the package.
Which in the context of extrepo-data is a feature, not a bug.
> In the case of the tests.reproducible-builds.org, we are building a
> little over a year in the future, and I guess DistroInfo is
> hard-coding when it expects future distributions to become testing?
Possibly, I don't know what the reasoning behind all that is :)
> > Looking at the source of Debian::DistroInfo, there does not currently
> > appear to be a way to ask for information at a given date, but that
> > sounds like a reasonable wishlist for Debian::DistroInfo to provide.
> >
> > Once that's available, updating extrpo-offline-data to use that to build
> > on a source epoch in the past seems like a reasonable course of action
> > to fix this bug.
>
> Yes, this sounds like that a better way to fix the issue overall!
Indeed.
--
w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}
I will have a Tin-Actinium-Potassium mixture, thanks.
