01.01.2019 23:14, Laurent Bigonville wrote:
On Mon, 24 Dec 2018 09:34:16 +0300 Michael Tokarev <m...@tls.msk.ru> wrote:
> it doesn't really break the package in question. All these > packages will be of the same version anwyway, upgraded in > one go, at the very max there will be some docs missing > for a (short) while, until the next apt run. > > More, it's just one version which were like that during the > buster development cycle. > > Besides, *this* bug is fixed, it does declare a replacement :) The usual way is to declare a Breaks/Replace when a file is moved between packages to prevent the file to be overwritten in case an older version of the package is installed.
I know the usual way, I just didn't think this is needed in this particular case, as I explained before. At the very least, it is a very minor issue, definitely not release critical.
> I don't think this bug needs to be acted upon more. At least > I don't plan a new upload at least before it is migrated to > testing, as time is already too short and this very bug, a > stupid mistake, already took more time than necessary. Well this bug has been reopened that mean that the package will never migrate
That's sort of unfortunate... Thanks, /mjt
