Hi, > I think you are right. > You might already done so but do the followings fix > the problem? > > dpkg-divert --remove --rename --divert /usr/bin/lynx.nossl /usr/bin/lynx > dpkg-divert --remove --rename --divert /usr/share/man/man1/lynx.nossl.1.gz > /usr/share/man/man1/lynx.1.gz
I do have a methusalem installation (prior to 1997 I believe), and I did have the /usr/bin/lynx.nossl diversion, and doing these two suggestions (followed by purge of lynx and lynx-cur) was the part that finally fixed an apt-get install lynx run. Probably the only thing that's left to wonder now is whether there's something useful to be done about this upgrade issue programmatically, or whether this bug report's content is sufficient documentation for this ancient fact. Thank you for your input! Andreas Mohr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org