Re: Does a temporarily dropped binary package have to re-enter via NEW?

["Adam D. Barratt" <adam@adam-barratt.org.uk>]

On Thu, 2025-11-13 at 13:34 -0700, Soren Stoutner wrote:
> On Thursday, November 13, 2025 1:12:23 PM Mountain Standard Time
> Christian 
> Kastner wrote:
> > Hi,
> > 
> > I have a package that provides multiple compute backends, all
> > shipped as
> > separate binary packages.
> > 
> > One of these backends requires a toolchain that, because of
> > transitions
> > and dependencies on transitions, will not be able to migrate to
> > testing
> > for what I believe will be a longer period. So it's holding back
> > the
> > rest of my package.
> > 
> > If I temporarily drop the binary package of this backend from my
> > source
> > package, will it have re-enter via NEW when I activate it again at
> > some
> > point in the future (say, 3 months from now)?
> 
> I believe the answer to that question is “yes”.  I think the check
> for new packages for an upload to unstable is against the version
> currently in unstable.

unstable and experimental share overrides - hence the preference for
NEW uploads for transitions to be made to experimental - so keeping a
version in experimental that still builds the dropped package would
avoid the NEW trip.

That does also require ensuring that the package in experimental
doesn't get removed for being older than the version in unstable, so
whether it's practicable and worth the effort is something you'd need
to consider.

Regards,

Adam