I believe the correct answer is as follows: You can't simply remove the updated package from the unstable archive, once it's in it's in. Package version numbering must always increase in order that package upgrading does not get confused. There are two solutions to a situation like yours:
a) The version numbering rules provide for a '1:' prefix to be used to deal with version numbering mistakes. A version number starting with '1:' counts as higher than any without such a prefix; a '2:' counts as higher than '1:', etc. So you could re-upload 2.10.08+ds-1 with version number '1:2.10.08+ds-1' to supplant 2.11.01+ds-3. However the downside to this approach is that you're forevermore committed to having that prefix in the version numbering. b) Re-upload 2.10.08+ds-1 with a version number like '2.11.01+ds-3- really2.10.08+ds-1', such that it will count as a higher version number than the mistaken upload of 2.11.01+ds-3 and thus replace it in package upgrades. You'd then continue with this pattern for 2.10.x updates until the eventual proper migration of 2.11 to unstable, at which point you can simplify the version numbering back to '2'11.x'. I'm sure you'll agree that option B would probably be preferable. On Wed, 2024-02-28 at 23:59 +0100, Preuße, Hilmar wrote: > Hello, > > dumb question: in an error I uploaded luametatex 2.11.01+ds-2 to > Debian > unstable. This was a mistake, it should have been uploaded to > experimental, as it is part of the upcoming TL 2024. Is it possible > to > downgrade the Debian archive (unstable) to 2.10.08+ds-1 and upload > the > 2.11.01+ds-3 to experimental? > > Thanks, > Hilmar > -- > sigfault >
