X-Debbugs-CC: Paul Gevers <elb...@debian.org> On Sat, Aug 13, 2022 at 11:07:12PM +0200, Paul Gevers wrote: > Can we have this fix in unstable too please? bctoolbox is a key package. > Please fix RC bugs in unstable/bookworm too.
I'll look into it, but need some clarification: If I make a new version 4.4.13-4 for unstable, it will then contain the very changes that led to the creation of 5.0.37-2 for experimental (thus rendering it redundant), and the latter will also not have 4.4.13-4 as a predecessor in its changelog. In a nutshell, shouldn't any new upload to unstable automatically nuke any newer version already in experimental as otherwise it becomes impossible for the experimental package to migrate to unstable without introducing changelog inconsistencies in the form of missing entries? I presume to handle this correctly that I'd have to do something like rebase all 5.0.37-* releases onto 4.4.13-4, then create 5.0.37-3 with no changes except its changelog rewritten to explain which changes were backported to unstable and which releases were obviated as a result. Is there an established way to express this? Regards, Dennis