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

Bug#617982: marked as done (release-notes: Before beginning the upgrade remove old debconf files)

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 #617982,
regarding release-notes: Before beginning the upgrade remove old debconf files
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.)


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

Hi,

It makes sense to cleanup from the last upgrade before
starting a new one.  The files that debconf leaves
when packages are upgraded should be found and
removed by the admin so that there is no possiblity
of confusion after upgrade as to what changes
were made to the config files.

I.e.  debconf (iirc) leaves old config
files 'foo.dpkg-old' laying about when
the admin decides to install the package
maintiner's new version of a config file
rather than keep what's on the system.
I'm sure there's a different name for
when the admin decides to keep the old
file.

-- System Information:
Debian Release: 5.0.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- 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: