On Mon, Jan 10, 2005 at 05:42:17PM +0200, Teemu Ikonen wrote:
> Hi all,
> Occasionally, upgrading a Debian unstable (or testing) system results in
> breakage. Sometimes the bugs are not immediately detected, or they are not
> easily located to a single package, especially if the upgrade in question
On Mon, 2005-01-10 at 18:40 +0100, Petter Reinholdtsen wrote:
> [Otavio Salvador]
> > No because some applications doesn't depends only of configuration
> > files but data-files. When you purge then, all data files will be
> > removed together (in major of times). Another problem is how you can
>
[Andrew Suffield]
> Seems like a poor reimplementation of a backup system to me. It's
> independently useful, and gains nothing from being embedded into the
> package manager, so why stuff it into the package manager?
I recommend reading the article, to gain some insight into the problem
it is try
|| On Mon, 10 Jan 2005 18:08:02 +
|| Andrew Suffield <[EMAIL PROTECTED]> wrote:
>> Such feature would be nice to have in Debian as well. If you have a
>> very short upgrade window, where one will have to abort and roll back
>> if the upgrade fail, it would be helpful if dpkg would allow you
|| On Mon, 10 Jan 2005 18:40:39 +0100
|| Petter Reinholdtsen <[EMAIL PROTECTED]> wrote:
pr> [Otavio Salvador]
>> No because some applications doesn't depends only of configuration
>> files but data-files. When you purge then, all data files will be
>> removed together (in major of times). Another
On Mon, Jan 10, 2005 at 06:40:39PM +0100, Petter Reinholdtsen wrote:
> [Otavio Salvador]
> > No because some applications doesn't depends only of configuration
> > files but data-files. When you purge then, all data files will be
> > removed together (in major of times). Another problem is how you
[Otavio Salvador]
> No because some applications doesn't depends only of configuration
> files but data-files. When you purge then, all data files will be
> removed together (in major of times). Another problem is how you can
> revert upgrade processes in database files and like?
RPM have a featur
|| On Mon, 10 Jan 2005 18:44:14 +0200
|| Teemu Ikonen <[EMAIL PROTECTED]> wrote:
ti> On 10/01/05 14:32, Otavio Salvador wrote:
>> || On Mon, 10 Jan 2005 17:42:17 +0200
>> || Teemu Ikonen <[EMAIL PROTECTED]> wrote:
>>
ti> I've been playing with putting the /etc directory plus a list of currently
On Mon, Jan 10, 2005 at 06:44:14PM +0200, Teemu Ikonen wrote:
> Maybe (and probably) some packages modify their data (which is not part of
> the package) so that downgrade is not possible, but I'd guess this kind of
> packages are not that common.
Anything that is linked to libdb is your biggest p
On 10/01/05 14:32, Otavio Salvador wrote:
> || On Mon, 10 Jan 2005 17:42:17 +0200
> || Teemu Ikonen <[EMAIL PROTECTED]> wrote:
>
> ti> I've been playing with putting the /etc directory plus a list of currently
> ti> installed packages and their versions under version control. In principle,
> ti>
[Teemu Ikonen]
> Thus it would be useful to know what has changed in a past upgrade,
> or when a certain package was last upgraded. Unfortunately, apt and
> dpkg do not have built-in logging (see #134694).
I tell apt-listchanges to email me a list of changes on every upgrade,
and can thus use the
|| On Mon, 10 Jan 2005 17:42:17 +0200
|| Teemu Ikonen <[EMAIL PROTECTED]> wrote:
ti> I've been playing with putting the /etc directory plus a list of currently
ti> installed packages and their versions under version control. In principle,
ti> a "rollback" to any previous system state would be pos
Hi all,
Occasionally, upgrading a Debian unstable (or testing) system results in
breakage. Sometimes the bugs are not immediately detected, or they are not
easily located to a single package, especially if the upgrade in question
contained many libraries or other shared code. Thus it would be usef
13 matches
Mail list logo
