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

Bug#706217: marked as done (release-notes: mention manual upgrade path for dovecot)

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 #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 owner@bugs.debian.org
immediately.)


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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

The dovecot packages have a new major release in wheezy (Dovecot 1 vs.
Dovecot 2). Almost nothing remained the same - the maintainer as wel as
upstream have chosesn to make the two versions heavily incompatible.

AN automated upgrade from the squeeze package to the wheezy package is
not possible (right now, the wheezy dovecot package fails in postinst
when upgrading from squeeze and also on a fresh installation, but this
is another issue). The upgrade needs a lot of manual work to convert the
configuration to the new format and also parameters for integration with
MTAs changed.

If the release team wants to add a section about that in the release
notes, please notify me and I will happily create one.

- -- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.7-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQJOBAEBCAA4BQJReoxxMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pajyRAAgzqR0yB9buFxAyLTAQ3q
r/lgRycjBA57ha5O7hAHPp/iJgnwUMk/0IT5ZXgo27VGNPb2o32tEqwLgu9xhAn7
4+TcFBQvZMtufFjKeN3BxobyIj1zGRpstgRk0bvjcgBgzg4aiAAR2wNmMlNNTUJx
AMv0G/Xr13bgWImkrhsC5F4qYzbOkV5EHecrd64tLofqY7vHxaBsjaqzuGxzpb73
O1Lt4QzAX/3NbZCNkVAWdIBeOeoemkbJqq/HOwkgv+8q1AwyWTH4ceWNXK+f+OW6
yEBat4RwphgxO3szeM1rZGwE+EOV8ii7z05ZLhSD04kXl5Vo5JlLcAIM4jGgEAnL
pxQf5GwnixKgz4VqdCc6fA+0jLAj634nuGUsg814kyF0JGUm1ZgSRc9n09PLL/g3
D53VpHuXVd3Yrsa4euM19+BeF3RZA/1CJR9DmpFEzCmFIdMKyK3I8/rGKGNovLFU
+hXLmNYK9ztrmZkcnbXkAqzUMd5/A2kF5+3kQOSwbwxjQCRihBikK+PPFaxJqsUR
AsBmfaW9etENUBi+aidgqZ/xhfeh0HmWLRlzn7yTO4yyWAxs1v/dUURR/gDOS5ko
c9qh7f62pDCYYCemX9uYpWEolwCEcOAnK+DSR0J10ZznhSLLneOx59XN82QiAjdh
/IcfehIvdItxbAJsycClQ40=
=f7P5
-----END PGP 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: