Package: crm114
Version: 20090423-1
Severity: critical
Justification: causes serious data loss
Changes (again...) in .css files just made me lose about one full day of
mail...
All non whitelisted mails were apparently just trashed after the line, in my
.procmailrc, where they're piped to crm114.
> "CP" == Christian Perrier 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
d
Le jeudi 21 mai 2009 à 08:36 +0200, Milan Zamazal a écrit :
> > "CP" == Christian Perrier 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.
> "JM" == Josselin Mouette writes:
JM> Simple: if there is no reasonable upgrade path, you need to
JM> change the binary package name. And of course, to do that in a
JM> way that does not install the new version automatically.
This may be a good idea. Do you know about packages
Quoting Milan Zamazal (p...@debian.org):
> > "CP" == Christian Perrier 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 t
On 0, Milan Zamazal wrote:
>
> This may be a good idea. Do you know about packages with similar
> properties (i.e. changing their data formats incompatibly) so that I
> don't invent my own binary package naming scheme?
>
Unison maintainer did that for some period because of protocol
changes. Th
> "CP" == Christian Perrier writes:
CP> The duty of the Debian maintainer is to smooth down impacts from
CP> upstream changes. One of the recognized qualities of Debian is
CP> such stability. So, we need to prepare our stable releases to
CP> avoid such breakages.
CP> Anot
> "MD" == Mehdi Dogguy writes:
MD> Unison maintainer did that for some period because of protocol
MD> changes. There have been unison and unison2.13.16 installable
MD> and usable together in the same system, thank to
MD> alternatives. The latter was kept for compatibility reas
Quoting Milan Zamazal (p...@debian.org):
> CP> At the very minimum, a critical priority debconf note displayed
> CP> when upgrading from a pre-20090423 version would be a good way
> CP> to try your best preventing the problem to appear. Debconf notes
> CP> are discouraged but I thi
[Better late than never.]
The discussion with upstream has lead to no better solution than already
proposed, i.e. prompting the users on upgrade. Future crm114 versions
may provide .css incompatibilities again (e.g. the recently released
beta version does).
So I've uploaded new package version t
Quoting Milan Zamazal (p...@debian.org):
> So I've uploaded new package version today that implements debconf
> prompting. I tried to be as aggressive with the prompting as possible:
Seems fair.
> Would you please review `preinst' script and debconf `templates' in
> crm114 20090423-2 to check
11 matches
Mail list logo
