Hi, On Fri, Apr 15, 2022 at 05:12:38PM +0300, Michael Tokarev wrote: > * switch from weird ~deb11uN to the usual +deb11uN release numbering scheme > since a more recent upstream version is available in testing now > > It is not really a change per se, just an indication that the versioning > scheme is finally back to normal.
I'm not speaking autoritatively here, but please do not do that. It changes the semantics and meaning what's happening and doe not sort anymore before the 2:4.13.13+dfsg-1. ~deb11u1 described that the update was build upon the unstable upload and was basically a rebuild for bullseye(-security). Subsequent updates added patches on top, so numbered ~deb11u1. Would the update have been a fresh import of upstream on top of the packaging then it would have been intially 2:4.13.13+dfsg-*0*+deb11u1, and subsequent uploads with patches on top (note the 0 in the Debian revision). (expections in how this is handled exists, especially e.g. in src:linux where stable series are followed separately). This is done to have at any time, the sorting correctly to an upload to the upper suite, even if testing now has a higher version, 2:4.13.13+dfsg-1 did exist for real in the archive history. Thus Z~debXuY can be perfectly valid, depending on what the upload wants to express. Exceptions exists always. but I would not change the versioning here in the mid. In particular because it was on purpose not choosen :4.13.13+dfsg-*1*+deb11u1. Regards, Salvatore