Your message dated Mon, 03 Oct 2016 04:27:29 +0000
with message-id <[email protected]>
and subject line Bug#839182: fixed in postgis 2.3.0+dfsg-2
has caused the Debian Bug report #839182,
regarding postgresql-9.4-postgis-2.2 and postgresql-9.4-postgis-2.1 cannot be
installed simultaneously
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 [email protected]
immediately.)
--
839182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839182
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-9.4-postgis-2.2
Version: 2.2.2+dfsg-5.pgdg+1
Severity: normal
Hello,
I work for Heroku Postgres, a service provider for postgres. We make
available postgis to our customers, some of whom are using 2.0, 2.1 and 2.2
versions of postgis on major versions of postgres including 9.2, 9.3, 9.4
and 9.5.
A situation we have seen is where a user has a 9.4 database with postgis
2.1 that would like to run pg_upgrade to 9.5. The upgrade fails, as no
postgis 2.1 package or binaries exist for 9.5.
To allow this upgrade to succeed, we must install
postgresql-9.4-postgis-2.2 alongside postgresql-9.4-postgis-2.1, which
allows ALTER EXTENSION postgis UPDATE to work, which clears the way for
pg_upgrade to 9.5 to work as expected.
With the latest release of postgis 2.3, however, these packages are no
longer able to be installed:
> # apt-get install postgresql-9.4-postgis-2.2 postgresql-9.4-postgis-2.1
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
> postgresql-9.4-postgis-2.2 : Depends: postgresql-9.4-postgis-2.2-scripts
but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
This appears to be from postgresql-9.4-postgis-2.1 depending on
postgresql-9.4-postgis-scripts, which depends on
postgresql-9.4-postgis-2.3-scripts, which conflicts with
postgresql-9.4-postgis-2.2-scripts:
> # apt-cache depends postgresql-9.4-postgis-2.1
> postgresql-9.4-postgis-2.1
> Depends: libc6
> Depends: libgdal1h
> Depends: libgeos-c1
> Depends: liblwgeom-2.1.8
> Depends: libproj0
> Depends: libxml2
> Depends: postgresql-9.4
> Depends: postgresql-9.4-postgis-scripts
> Suggests: postgis
> Recommends: postgresql-contrib-9.4
> Breaks: postgis
> # apt-cache depends postgresql-9.4-postgis-scripts
> postgresql-9.4-postgis-scripts
> Depends: postgresql-9.4-postgis-2.3-scripts
> # apt-cache depends postgresql-9.4-postgis-2.3-scripts
> postgresql-9.4-postgis-2.3-scripts
> Recommends: postgresql-9.4-postgis-2.3
> Conflicts: postgresql-9.4-postgis-2.2-scripts
> Breaks: postgresql-9.4-postgis-scripts
> Replaces: postgresql-9.4-postgis-scripts
This is surprising, as we have been successfully installing and using
postgis 2.0, 2.1 and 2.2 packages with the latest postgis-scripts package
satisfying dependencies for all versions for some time.
Is each version of postgis-scripts incompatible with other versions of
postgis? Is postgis-2.3-scripts not backwards compatible with postgis-2.2?
I have found https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837294 and
am not sure of the reasoning behind "We're using Conflicts instead of
Breaks/Replaces because the source packages is also used in PGDG where
multiple versions are provided." as it breaks the multiple version use case
that pgdg allows.
Thanks,
Greg
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.15-moby (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
--- End Message ---
--- Begin Message ---
Source: postgis
Source-Version: 2.3.0+dfsg-2
We believe that the bug you reported is fixed in the latest version of
postgis, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Markus Wanner <[email protected]> (supplier of updated postgis 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 30 Sep 2016 16:36:08 +0200
Source: postgis
Binary: postgis postgis-gui postgis-doc liblwgeom-2.3-0 liblwgeom-dev
postgresql-9.6-postgis-2.3 postgresql-9.6-postgis-2.3-scripts
postgresql-9.6-postgis-scripts
Architecture: source all
Version: 2.3.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project <[email protected]>
Changed-By: Markus Wanner <[email protected]>
Description:
liblwgeom-2.3-0 - PostGIS "Lightweight Geometry" library
liblwgeom-dev - PostGIS "Lightweight Geometry" library - Development files
postgis - Geographic objects support for PostgreSQL
postgis-doc - Geographic objects support for PostgreSQL -- documentation
postgis-gui - Geographic objects support for PostgreSQL -- GUI programs
postgresql-9.6-postgis-2.3 - Geographic objects support for PostgreSQL 9.6
postgresql-9.6-postgis-2.3-scripts - Geographic objects support for PostgreSQL
9.6 -- scripts
postgresql-9.6-postgis-scripts - transitional dummy package
Closes: 839182
Changes:
postgis (2.3.0+dfsg-2) unstable; urgency=medium
.
* Update pgversions to require PostgreSQL 9.2 or newer.
* Run tests against all supported PostgreSQL versions.
* Downgrade the dependency from the extension package to the
scripts package to a recommendation, so the former becomes
co-installable with older versions, again. Closes: #839182.
Checksums-Sha1:
926548645ca8f27ccf874a119ae6aaa32ecfbd00 3661 postgis_2.3.0+dfsg-2.dsc
9e6ae6960890772c2807389a0ad8bcb41ddbd562 38348
postgis_2.3.0+dfsg-2.debian.tar.xz
2b751229a2bd044aa253fd8f3737d0761549e8e8 3363466
postgis-doc_2.3.0+dfsg-2_all.deb
de6b3f6bbbe5eb130ba677dbb46113804460c692 1215332
postgresql-9.6-postgis-2.3-scripts_2.3.0+dfsg-2_all.deb
b016f1ec1e66cb5ee47ad88af16b69591c5bf4d1 466290
postgresql-9.6-postgis-scripts_2.3.0+dfsg-2_all.deb
Checksums-Sha256:
e2ce16b2afff34472280782fbcd84041cb7b6058f08339ee41ed710dc57cb771 3661
postgis_2.3.0+dfsg-2.dsc
1140700a57a0003f2514dae154e72cdd765de589d16bc2c8aa57466f6c136b6f 38348
postgis_2.3.0+dfsg-2.debian.tar.xz
0359dd81f76d44d46ea2eba61db0ffea6bd9bf4a3582ebc9a8141c1d1c22e764 3363466
postgis-doc_2.3.0+dfsg-2_all.deb
1c87b39d23fd7828b6cfa8f6c4ecc5b6b50b85e393fe1c6ad620ede608c3e7d5 1215332
postgresql-9.6-postgis-2.3-scripts_2.3.0+dfsg-2_all.deb
8ae6126fe1ac2693295eeb4ac979699a06c02e998dcdeb499f17fc518af6aa83 466290
postgresql-9.6-postgis-scripts_2.3.0+dfsg-2_all.deb
Files:
ff5adeade5870ef2617824ff1054d36f 3661 misc optional postgis_2.3.0+dfsg-2.dsc
b3ce3d456fd0ed17249d71374fccc800 38348 misc optional
postgis_2.3.0+dfsg-2.debian.tar.xz
6fcbc9f72c8cfda8a6ce26e127f5064e 3363466 doc optional
postgis-doc_2.3.0+dfsg-2_all.deb
4898bb66a1b8ee5ebfd02fae2a629a7e 1215332 misc optional
postgresql-9.6-postgis-2.3-scripts_2.3.0+dfsg-2_all.deb
fb6b681f3492bc213ccbd5908c6f4eb0 466290 oldlibs extra
postgresql-9.6-postgis-scripts_2.3.0+dfsg-2_all.deb
-----BEGIN PGP SIGNATURE-----
iQQcBAEBCgAGBQJX8dxkAAoJEOhoLRs/MemzU6kf/28xnrWGiNqpe/mRoub66BRK
wSgVIseTfLX8b9WjJshAnoSJK5fkN9C5nIu5IBnyfogGqkBsW48UkrglXP5g+bMe
cISuYXrOiEeB/m5xWWn6T8gMmy2CnfyXZtxXdccbtSNMy23fpRyGUWr12P3k4rs8
ABI1tdpsQsXDmI9YWpQ+5d/r751pfEAjSLlurM7cjFZMyUYS0z+TzoCIyv/Ff6CE
8E1grohmrk+aiWv3wFZnHfzMgEbSYmZG72BB44MmuijuyJj1d17g9SYG4ub/G4WN
m9lp4Ia+CZ3puVWwt0br/mCXI7Dbx55F+yo5etArJfER3oZxRTWOPMqU5IMm+Lgi
gVtRZbrndNbqvgjf3OsqC6vO5EIdiVSnFjfwjMzQLyieVgOn06pgtTjX5BDpRX3/
Bnr+60ZSFkS+9ZtS8sPxJDdXHYo6GVJW3K9NkalgL0C6CDv8zyvKBAw//rxWepbj
dBopwaAIvKVMUtcqo5onoK3irletY4+E41DWCgwnIwBNZQpuGhLiO29rzNMEMY5+
ueRcrZ5SYLLKGnJ6vOrU2XQqwmBpKkKC0NzJFBjhDD5+KTfKiyjMQsTKfqPYbGxo
iKj8a8WwsvXbzRcAxonxbr9cR9/qGf7Gv+28pdSSzybw3RN+DOWKMzXAHvDTGr3m
hphTMsedl8WnXDDgz6y1I+JXYjCfIdf7QTk5MwLi8qC4N1n0LcbCltpp7RsTRFNi
OT38pBfn17NJeZn4N7ZUiCqjqqFO4EbTAeqkwNFmdDRyVHcXpOzkiWqyotC6FFo5
dpf550X94CbviRLniWv2GmYWAefEGMDQ06TNiPEqGFEXlN+9MkttM2E2Lmappb7n
PyUZOt1uW++9xuNko7CUIjByoINAp8VhTv6KK3YqkoW+S69tQaCYU+pwtOWjoU0A
9NY/SOK3BLPbT2VMOET+Gcga7z7pU2y+wxiq9jdmp+o1K5OD1E/J2PTHd2KfkIC+
g4P8Khzd0Apk6Yj1Qll88rln5i0rif57NL3pn6KKnO93F9gWhs+IKTbUzyyLFVF7
ixl7Ny/vyaeUnw0MYMCxuAN5vml2/j2PSeQxclkWTIOscT8Bj0nbqnMKzoAkDcbu
kO5/N+2pXURlao2x25tT2QahVJM2FUzdLj4p8R0MfzaGHvq+hjOnVbhNQmGqgBvc
Hz5jCcxrUYPOpnjxSZvPA7HWvQ2jR7QXZa5pKpzpJBpXQ8VV7632TkID5KZJ0lMP
jm9BmaglBH2PiaY6Sm+Q8VEr0tD4rdlpO9fMb+TcJiJaSIwJYWPOgdMRru2zomRw
Ki2ID4x3QIgbl2n4w+mI/J73PF1wKDGqvoR5kz0PiPrJgSwR82Axhr9jU8yKJ6U=
=bQHJ
-----END PGP SIGNATURE-----
--- End Message ---
