Hi Santiago, Santiago Vila wrote:
> > Oddly enough, a copy of uw-imap (thus mlock) ship with Alpine source but > > are not compiled as part of the package. > > > But mlock is compiled as part of the alpine package, under the name > alpine-mlock. I missed this due to the renaming of the binary, and thus assumed it wasn't included. It could be the alpine package I examined was the older (unpatched) version. > Do you miss mlock because you are still using it, > or only because you believed alpine still needed it? The latter. > If it's the second, I think this bug could be closed. If it's > the first, I think mlock as a standalone package is very unlikely > to come back, because no other package is using it. Am I wrong for thinking there should have been an apt-listchanges NEWS bulletin about this? FWIW I did due diligence before opening this bug, somehow I missed the new binary when running strings on alpine. Was the renaming to avert any package conflict? The first I realized something was wrong when I saw mlock in the list of packages to be removed, with no replacement identified. While I agree there is no bug, maybe there is a bug in the documentation? If two packages are being merged, the change should have been publicized better unless I'm overlooking something. I can't be the only one that will have this concern post-upgrade.
