Hi! On Fri, 2022-08-05 at 22:13:15 +0200, Simon Josefsson wrote: > Guillem Jover <guil...@debian.org> writes: > > Sure. As per the plan on debian-devel, whenever you have some time, could > > you prepare the netkit-telnet update targeting experimental, which > > renames the binary packages to be prefixed with netkit-*? Then once these > > get ACCEPTED from NEW, we can coordinate the upload of netkit-telnet and > > inetutils into unstable. > > Hi! Great. I have uploaded it now, and my main problem is thinking > about upgrades. In git, I have renamed telnet(d) to netkit-telnet(d) > now, and added Replaces/Breaks on the old versions. How do we test > upgrade paths? It is not clear to me what should happen in all cases > (e.g., system with telnet+inetutils-telnet installed, alternatives > pointing to netkit, do we want that to upgrade both packages and change > alternative?).
And it seems it was ACCEPTed yesterday! I've prepared the following changes inetutils: https://git.hadrons.org/cgit/debian/pkgs/inetutils.git/log/?h=pu/default it seems to handle the upgrade correctly. For telnetd we need to remove the inetd entry otherwise update-inetd will prompt, for telnet we should remove the alternative otherwise there are warnings about disappearing implementations for the alternative. I've tested this by installing the telnet/telnetd package and then just running the equivalent of «apt install ./inetutils-telnet*.deb ./telnet*.deb». If you can have a peek that would be nice, then once we are satisfied we can decide on a day, where I upload inetutils to sid first, to take over the telnet/telnetd, then once that's accepted you could upload the netkit from experimental to sid. Thanks, Guillem
