[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: patch for

From: Dmitry Borodaenko
Subject: Re: patch for
Date: Sun, 6 May 2007 13:32:30 +0100

On 5/5/07, boud <address@hidden> wrote:
i didn't mean to auto-generate the config file in the debian package.
i rather meant just to give a warning to the sysadmin who is updating
interactively. The only option s/he will have is to click OK ;) - i'm
not sure offhand which packages have this type of messages, but i know
that some do - it can even be: "Warning: there are some important changes
in version 0.6.0-20070501 - your installation will probably fail unless
you follow the recommendations in /usr/share/doc/samizdat/NEWS.Debian."

Ah, you're right, I should put a warning using debconf. Probably not
as critical for experimental, but definitely should be done before
uploading this version to unstable.

> automated way will always work. And yes, you are supposed to read
> NEWS.Debian when upgrading a package, even if it doesn't break
> immediately after upgrade.
Even when an upgrade gives 10-20 packages modified?  Well, i guess
there's a difference between stable and testing/unstable and experimental.

Don't take my word on this, some DDs may disagree with me :)

I am upgrading from unstable daily, so I'm kind of used to checking
NEWS and changelogs when something breaks. Although I have to admin it
doesn't happen all that often, and it's not supposed to happen at all
when you upgrade from stable.

On a related topic, what are the plans for getting samizdat from unstable
into the full unstable -> testing cycle, so that in 18-24 months' time
samizdat will get into stable?

Version 0.6.0 is already in testing:

I hope that in 18-24 months time it will be at least 0.6.1 there :)

>> BUG: language_list was missing :(((, and language_list gave an old style
>> URL member.rb?set_lang= which fails

Version (soon to appear in experimental) will include
this and a bunch of other fixes, including weird database deadlocks
caused by CSRF protection. I hope the fix to keep action tokens in
cache instead of database will not cause cache deadlocks instead ;-)

Dmitry Borodaenko

reply via email to

[Prev in Thread] Current Thread [Next in Thread]