Your message dated Mon, 21 Jun 2021 14:20:29 +0000
with message-id <e1lvkmr-000fn3...@fasolo.debian.org>
and subject line Bug#989731: fixed in postgresql-q3c 2.0.0-5
has caused the Debian Bug report #989731,
regarding postgresql-13-q3c: drop Conflicts+Replaces: postgresql-q3c
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 ow...@bugs.debian.org
immediately.)
--
989731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-13-pgsphere
Version: 1.1.1+2020-10-20-1
Severity: serious
Control: clone -1 -2
Control: reassign -2 postgresql-13-q3c 2.0.0-4
Control: retitle -1 postgresql-13-q3c: drop Conflicts+Replaces: postgresql-q3c
In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984555#44
Markus Demleitner <msdem...@ari.uni-heidelberg.de> wrote:
> One thing that needs to be
> ensured, though, is that on upgrades, the old pgsphere packages do
> not get removed until the operator asks dpkg to explicitly. Perhaps
> stating the obvious, here's what needs to happen when upgrading from,
> say pg 11 to 13:
>
> (1) normal dist-upgrade pulls in (hopefully) postgres-13, keeps
> postgres-11 running as normal (hence, pgsphere-11 must still be
> there).
> (2) operator runs pg_upgrade (for which both pg-13 and pg-11 must be
> present with all necessary extensions)
> (3) the last step of pg_upgrade is to make pg-13 the default db server,
> and pg-11 isn't started any more
> (4) the operator can now purge postgres-11 together with the
> version 11 extensions.
This is currently not possible, since postgresql-13-pgsphere has
Conflicts+Replaces: postgresql-pgsphere (<< 1.1.1+2020)
(and C+R: postgresql-q3c (<< 2.0.0-2) for postgresql-13-q3c).
I do not know if other extension packages have the same bug.
(gavodachs2-server seems to be one of the few packages actually needing
some extensions (pgsphere and q3c) and thus exhibiting upgrade errors.)
I think these Conflicts+Replaces can be safely dropped, since all files
in these packages are in versioned (/13/) paths and therefore cannot
cause file conflicts with the unversioned package in buster that ships
everything (but documentation) in versioned (/11/) paths.
But I may be overlooking something ...
Andreas
--- End Message ---
--- Begin Message ---
Source: postgresql-q3c
Source-Version: 2.0.0-5
Done: Ole Streicher <oleb...@debian.org>
We believe that the bug you reported is fixed in the latest version of
postgresql-q3c, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 989...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher <oleb...@debian.org> (supplier of updated postgresql-q3c package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 21 Jun 2021 15:37:28 +0200
Source: postgresql-q3c
Architecture: source
Version: 2.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers <team+postgre...@tracker.debian.org>
Changed-By: Ole Streicher <oleb...@debian.org>
Closes: 989731
Changes:
postgresql-q3c (2.0.0-5) unstable; urgency=medium
.
* Remove Conflitcs+Replaces: postgresql-pgsphere (Closes: #989731)
Checksums-Sha1:
59b35bd8386b734499d8fd32f12f23f4ebb2dac6 2193 postgresql-q3c_2.0.0-5.dsc
436880605a49959817044f187d8d7ff0e6527bf3 4556
postgresql-q3c_2.0.0-5.debian.tar.xz
Checksums-Sha256:
2644ffbd9170f49d8e2a2c7708d7538078e4d06d821b773c3001a84aa6bcbc7b 2193
postgresql-q3c_2.0.0-5.dsc
c26c28b477c212e410f8fab77191997c9fa470464e6eaa8bbc65d514917982ce 4556
postgresql-q3c_2.0.0-5.debian.tar.xz
Files:
1b0e8f76e815af988dc892d7bd96ec3e 2193 database optional
postgresql-q3c_2.0.0-5.dsc
79b38e64cb4aec02c9cde98b5ce91bcf 4556 database optional
postgresql-q3c_2.0.0-5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmDQlq8ACgkQcRWv0HcQ
3PcEDw//XfFFPGUf+u2S72nQtqNz7TnpAgcmYJb5tXGeJjtfMSRoC37qZndPDTNa
7NhSgCDELMAmrVbdeHWUU7ipDvqzsmZwshxYTWuh0TmPxEA1Zh/MU2ZBmO5+Olhh
DdqJ9yxtBSBbvbnSYaJZtWl8uC6W++IPKrZC7f9cZPdSxdRcTYu4uD8n27tlnNQ7
FKoOxclBMUayoEJGJpuP22uGfGKnwBv0w4uTnpHdPnOZKmdZKLx9arRpgB2rEv+b
gJjgRivCz2G3L7LS5iIr06L/M6Mk5ynA1HtPyAeHJOmtxRWJ8L/xCYdffZ7vZfoT
9RcwbkGPKMPk2xOTbz4P1MjSdXgxdgyPU5uXMGXDRwr+3wzvRWPvQQKJRix/Lgz1
o2gJNduo+0yEDw1j2kuBAt0jOxoQdDOpHJ55h/yKiKzuxys9BX2qjg0KeauFSjDI
CsrZBjKAjDcIyAwlHD1Ab2X824YuCmjWwlh4a9py6rbPM177bMChG65TY/2k9mND
iquQus2mrX6+du62iqB/TUzD8RZfWtUcGulDH8Ksqp0pC1OLSo+ECuspDNizHMFv
xMEimqa3dEOueG7oMtqk6aipU5+G+CKACc0pU4bhgEZrrtWUiU9gVcvHaRfvaKlV
BUvrYS1Sh0tdeifign8vE2/5jvbkktldbAXg0s4zsksD5hbhAWo=
=XYQR
-----END PGP SIGNATURE-----
--- End Message ---
