Bug#1110915: trixie-pu: package extrepo-data/1.0.6~deb13u1

[Wouter Verhelst <wouter@debian.org>]

Package: release.debian.org
Severity: normal
Tags: trixie
X-Debbugs-Cc: extrepo-data@packages.debian.org
Control: affects -1 + src:extrepo-data
User: release.debian.org@packages.debian.org
Usertags: pu

extrepo-offline-data contains metadata of external repositories, meant
(mostly) for people using proxies (and the --mirror option for extrepo)
and airgapped systems.

Now that trixie is out, I expect a lot of repositories to update their
build systems to include trixie in their repositories.

I would like to upload an updated version of extrepo-offline-data to
unstable in a few weeks (which would be given the number 1.0.6), and
then (once that has migrated to forky) provide an update for trixie.

Would that be agreeable to the release team?

If so, which timeline should we keep in mind if we don't want to miss
any relevant deadlines for trixie's first point release?

Risk/impact: the risk should be low, as this package only contains
metadata for external repositories, nothing else.

The impact of refusing this will be that people on airgapped systems are
more likely to get incorrect or incomplete data.

Thanks.