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

Bug#610194: marked as done (Suggest to purge removed packages with init scripts before squeeze upgrade)



Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-7b2c7a62a7f6@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #610194,
regarding Suggest to purge removed packages with init scripts before squeeze upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
610194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610194
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: wishlist


On Sat, 15 Jan 2011 18:02:06 -0800, Russ Allbery wrote:

> > I find this strange, since every system that has ever been etch will
> > have at least libdevmapper1.02 which stops insserv from migrating.
> Judging from further discussion, it looks like the reason why I've never
> seen this is that I routinely purge deinstalled packages on all my
> systems and most of the problems are with packages that have been
> deinstalled but not purged and have obsolete init scripts.  I wonder if we
> should suggest people consider doing that before the upgrade if they don't
> have any old configuration files around that they care about.

Now that Adam mentioned it I remember that I at least met this
removed-but-configured libdevmapper1.02 on each machine which tried
to convert to dependency based init scripts. (I think most other
issues I had came from home-grown init scripts without LSB headers.
-- And I also tend to purge removed packages; but not packages that
were both installed and removed automatically ...)

Suggesting to purge libdevmapper1.02 and maybe other
removed/configured packages in the release notes' "preparation"
section might indeed be helpful.

Cheers,
gregor, cc'ing the BTS 
 
-- 
 .''`.   http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4
 : :' :  Debian GNU/Linux user, admin, & developer - http://www.debian.org/
 `. `'   Member of VIBE!AT & SPI, fellow of Free Software Foundation Europe
   `-    NP: Simply Red: Holding Back The Years

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Hi,

We are sorry that we were not able to handle your contribution or
suggestion for changes to the release-notes. I am going over old bugs
and I am closing all the items that were suggested for the release-notes
of Debian releases before stretch. On the good side, some even appear to
have been applied, without the bug being closed.

Please don't hesitate to open a new bug if you think your suggestion is
still valuable for the release-notes of buster. If you do that, we'd
appreciate it when you try to summarize the issue properly when the
closed bug was more than a couple of messages.

Paul


Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply to: