On Tuesday, May 20, 2025 12:42:38 PM Mountain Standard Time Hilmar Preuße
wrote:
> Yes, do exactly this. Re-uploading the same version again won't work.
>
> > And in any of these cases is there an automated removal mechanism for
> > the redundant package left behind in experimental?
> >
>
> Yes, there is.
"As part of their archive maintenance role, the ftp-master team periodically
(daily, cron-job) run a tool which searches for packages that should be
removed. This tool used to be known as "rene" (and is still often referred to
as such) but has now become the "cruft-report" sub-command of dak. In the
cases handled by this tool, there is no need to request that your package be
removed, they are handled in batches from times to times (apart from the
"Architecture Not Allowed In Source" case, which still need a removal
request).”
"Packages in experimental for which a higher numbered version of the package
exists in unstable ("NVIU" - "newer version in unstable”)”
https://wiki.debian.org/ftpmaster_Removals
--
Soren Stoutner
soren@debian.orgAttachment:
signature.asc
Description: This is a digitally signed message part.