Your message dated Sat, 10 Jan 2026 11:52:34 +0000
with message-id <[email protected]>
and subject line Released with 13.3
has caused the Debian Bug report #1110915,
regarding trixie-pu: package extrepo-data/1.0.6~deb13u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1110915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110915
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: trixie
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:extrepo-data
User: [email protected]
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.
--- End Message ---
--- Begin Message ---
Package: release.debian.org\nVersion: 13.3\n\nThis update has been released as
part of Debian 13.3.
--- End Message ---
