Hi Marco, First off, thanks very much, genuinely, for all the work you do as the maintainer for the netbase package. I can understand that one of the unfortunate things about being a Debian developer is that you probably almost never hear from users unless they have bugs to report. So please do know that you have my sincere appreciation and respect and admiration for your work.
Along with that, I do want to add a couple of comments about bug 560238, as replies to comments that Salvo and Paul posted earlier. Salvo Tomaselli <tipos...@tiscali.it>, 2009-12-10 09:25 +0100: > You should modify the package to introduce a postinst script that shows some > dialog, that tells the user what is going on, why is this change happening, > give some links on where to find further informations, how to revert the > change and most of all put a "YES/NO" to let the user decide if he wants to > do > the change, after he is aware that the change might break his system. FWIW, I agree with that. I think the package upgrade should at least do the apt-listchanges thing where it puts up a message on the console and/or mails a copy to an admin address. Paul Seelig <psee...@debian.org>, 2009-12-10 15:54 +0100: > While the functionality was broken, it was not even possible to connect > a local session to localhost, when it was connected under either its IP, > or via 127.0.0.1, or its very own hostname. I ran into the same issue, and at first had no idea at all what the cause was. It took me a significant amount of time to get it figured out -- tried at first using netstat and lsof, etc., and not seeing any problems and just completely baffled as to what was going on. Paul Seelig <psee...@debian.org>, 2009-12-10 01:45 +0100: > It took me much more time i could currently afford to find out > what the breakage was caused by. That's the core concern here, I think. It's that unless/until the package is updated to emit some kind of user notification about the net.ipv6.bindv6only=1 change, you are risking to end up with a significant number of frustrated users -- because you're going to have N different users getting bitten by it when they run into problems on upgrade, and each of them needing to take probably at least something like 30 minutes or an hour go through the process of first probably thinking they must have done something wrong themselves, then checking their environment, tweaking other config options in their environment and finding that they have no effect, then (hopefully) resorting to using a search engine and finding out that it's a known issue and what the fix is. Yeah, the first step for users when something like this happens probably should be to try the search engine first, but for whatever reason, it often doesn't seem to be the first thing that people try. Again, thanks for your work on this package, and please just consider my comments for what they're worth to you. Regards, --Mike -- Michael(tm) Smith http://people.w3.org/mike/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
