Le jeudi 21 mai 2009 à 08:36 +0200, Milan Zamazal a écrit : > >>>>> "CP" == Christian Perrier <bubu...@debian.org> writes: > > CP> Oh, I certainly got warned by mail as there is a NEWS.Debian > CP> entry about this...and I ust apt-listchanges. "Unfortunately", > CP> that mail got trashed just like others. > > If you want to prevent such problems, configure apt-listchanges to > display information before installation and to ask for confirmation.
Sorry, but the existence of apt-listchanges is not an excuse for completely breaking existing setups. It can be an excuse for some more or less important glitches, but not for losing data. > This has nothing to do with Debian. Of course it has to do with Debian, it’s a Debian package. If you don’t want it to be a Debian problem, maintain the package in your own repository. > I don't understand. Recreating the .css files with mailreaver is > relatively easy and may even clean up and improve the .css files. The problem is not whether this is easy or not. The problem is that you broke existing setups in a way that leads to serious data loss. > I can understand your rage but as I've explained above I can't see in > your report what I should fix in the Debian package. Simple: if there is no reasonable upgrade path, you need to change the binary package name. And of course, to do that in a way that does not install the new version automatically. Bonus points go for changing the binary names as well, so that both versions can be installed at once on the system. Cheers, -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
