On 2025-05-30 19:49:54 +0800, xiao sheng wen(肖盛文) wrote: > Hi, > > 在 2025/5/30 15:51, Sebastian Ramacher 写道: > > On 2025-05-30 15:04:50 +0800, xiao sheng wen(肖盛文) wrote: > >> Control: reopen -1 > >> > >> Hi, > >> > >> 在 2025/5/30 13:37, Paul Gevers 写道: > >>> Hi, > >>> > >>> On 09-05-2025 09:28, Sebastian Ramacher wrote: > >>>> Benjamin, what is your take on this? Without explicit coordination, I'd > >>>> think it's too late for trixie and this should be revisited for forky. > >>> > >>> > >>> Explicit coordination didn't happen and we're 20 days further in the > >>> freeze process. Let's revisit this in forky. > >>> > >>> Paul > >>> > >> apt-mirror2 is a new package, although it has almost the same usage with > >> old package apt-mirror, > >> but apt-mirror2 can co-exist with apt-mirror in the same machine now. > >> > >> Install apt-mirror2 will *not* break apt-mirror! > >> > >> Why need to coordination with Benjamin in trixie? > > > > Because as new source package it was too late for trixie. It missed the > > deadline. If there had been coordination with apt-mirror we could have > > looked at replacing apt-mirror with apt-mirror2 in trixie and traded one > > source package for another. > > IMHO, apt-mirror2 would keep co-exist with apt-mirror for a long time. > As apt-mirror had very long time in Debian and apt-mirror2 is very new. > > Perhaps we have some communicate mismatch. > I just intend to unblock apt-mirror2, let it in trixie; > but I don't intend that apt-mirror2 replacement of apt-mirror in trixie. > > apt-mirror2 had set: > > Provides: apt-mirror > > It's benefit for user smooth switch to apt-mirror2. > > We don't need to traded one source package for another in trixie, > only let apt-mirror2 into trixie is enough. > > It's not a good time to replacement of apt-mirror now.
In that case it's too late. The dealine for new source packages to be part of trixie was 2025-04-15. See https://release.debian.org/testing/freeze_policy.html#soft Cheers -- Sebastian Ramacher
