Bug#617982: release-notes: Before beginning the upgrade remove old debconf files

[Karl O. Pinc]

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

[Debian Bug Tracking System]

tags -1 moreinfo

Bug #617982 [release-notes] release-notes: Before beginning the upgrade remove old debconf files
Added tag(s) moreinfo.
--
617982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617982
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems

[David Prévot]

Control: tags -1 moreinfo

Hi,

Post by Karl O. Pinc
Package: release-notes
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 hardly see any benefit to advise anyone to loose history just to avoid
confusion (timestamp can help to that regards). I may be missing your
point here, but if I’m not, I believe this issue is not relevant, and
advise the RN wizard to close it (I may do so myself next time I come
across this bug report unless more information is provided).

Regards

David

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #683698,
regarding [wheezy] mention SSD TRIM support
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #708135,
regarding release-notes: Should mention change of aptitude config "Apt::AutoRemove::Suggests-Important [wheezy]
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #769388,
regarding setting up a headless system
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #770533,
regarding release-notes: [jessie]: add note about removal of lire (once Bug#770532 has been dealt with)
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #706610,
regarding no migration from isdn4linux to mISDN possible: there is no userland
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #713914,
regarding squeeze->wheezy: reminder that kernel should be >= 2.6.32 before 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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #803356,
regarding release-notes: cryptdisks conflicts with documentation, and is cryptic to use [jessie]
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #699754,
regarding grub core.img too large when using lvm+md
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #783235,
regarding Installation Guide link in 3.1.2. Automated installation points to Wheezy documentation
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #769388,
regarding 'PermitRootLogin without-password' in new installations breaks some use cases
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #762026,
regarding php5-cgi + libapache2-mod-fcgid wheezy upgrade problem not documented well
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #783232,
regarding release-notes: two comments about the security section [jessie]
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #706217,
regarding release-notes: mention manual upgrade path for dovecot
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sun, 3 Mar 2019 20:35:55 +0100
with message-id <7b603213-96c5-8056-b6d3-***@debian.org>
and subject line close release-notes bugs for releases before stretch
has caused the Debian Bug report #774563,
regarding release-notes: Document improved AppArmor support in Jessie
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 ***@bugs.debian.org
immediately.)

[Harald Dunkel]

Sorry to reopen this bug report. The issue is still unresolved.
And its not a documentation issue, either.

Its not reasonable to install and activate an ssh service at
debootstrap time, and then disable it for the only available
login because ssh password-based login is vulnerable to a brute
force attack. Why was ssh installed in the first place?


Regards
Harri

[Paul Gevers]

Hi Harald,

Post by Harald Dunkel
Sorry to reopen this bug report. The issue is still unresolved.
And its not a documentation issue, either.

As this isn't (as you say) a documentation issue, could you please
assign it to the right package then? Currently it is assigned to the
release-notes; your issue will not be resolved by the people caring for
those.

Post by Harald Dunkel
Its not reasonable to install and activate an ssh service at
debootstrap time, and then disable it for the only available
login because ssh password-based login is vulnerable to a brute
force attack. Why was ssh installed in the first place?

As I am not involved in that area, I have no clue. This is the wrong
place to discuss this.

Paul