Your message dated Wed, 4 Sep 2019 12:48:54 +0200
with message-id <[email protected]>
and subject line Re: Bug#939384: qgis-providers: proj_create: crs not found
has caused the Debian Bug report #939384,
regarding qgis-providers: proj_create: crs not found
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.)
--
939384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939384
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qgis-providers
Version: 3.4.11+dfsg-1
Severity: normal
Hi,
while upgrading my bullseye system:
workrave (1.10.34-2+b1) wird eingerichtet ...
qgis-providers (3.4.11+dfsg-1) wird eingerichtet ...
proj_create: crs not found
proj_create: crs not found
proj_create: crs not found
proj_create: crs not found
... a lot more of those ...
proj_create: crs not found
proj_create: crs not found
proj_create: crs not found
libqgis-customwidgets (3.4.11+dfsg-1) wird eingerichtet ...
python3-qgis-common (3.4.11+dfsg-1) wird eingerichtet ...
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (700, 'testing'), (600, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8),
LANGUAGE=de:en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages qgis-providers depends on:
ii dpkg 1.19.7
ii libc6 2.28-10
ii libexpat1 2.2.7-1
ii libgcc1 1:9.2.1-4
ii libgdal20 2.4.2+dfsg-1+b2
ii libhdf5-103 1.10.4+repack-10
ii libnetcdf13 1:4.6.2-1+b1
ii libpq5 12~beta3-1.pgdg+1
ii libqca-qt5-2 2.2.1-2
ii libqca-qt5-2-plugins 2.2.1-2
ii libqgis-core3.4.11 3.4.11+dfsg-1
ii libqgis-gui3.4.11 3.4.11+dfsg-1
ii libqscintilla2-qt5-13 2.10.4+dfsg-2.1
ii libqt5core5a [qtbase-abi-5-11-3] 5.11.3+dfsg1-4
ii libqt5gui5 5.11.3+dfsg1-4
ii libqt5network5 5.11.3+dfsg1-4
ii libqt5sql5 5.11.3+dfsg1-4
ii libqt5sql5-sqlite 5.11.3+dfsg1-4
ii libqt5widgets5 5.11.3+dfsg1-4
ii libqt5xml5 5.11.3+dfsg1-4
ii libspatialite7 4.3.0a-6+b1
ii libsqlite3-0 3.29.0-2
ii libstdc++6 9.2.1-4
ii qgis-providers-common 3.4.11+dfsg-1
qgis-providers recommends no packages.
qgis-providers suggests no packages.
-- no debconf information
Christoph
--- End Message ---
--- Begin Message ---
tags 939384 wontfix
thanks
Hi Christoph,
On 9/4/19 12:18 PM, Christoph Berg wrote:
> while upgrading my bullseye system:
>
> workrave (1.10.34-2+b1) wird eingerichtet ...
> qgis-providers (3.4.11+dfsg-1) wird eingerichtet ...
> proj_create: crs not found
> ... a lot more of those ...
> proj_create: crs not found
> libqgis-customwidgets (3.4.11+dfsg-1) wird eingerichtet ...
> python3-qgis-common (3.4.11+dfsg-1) wird eingerichtet ...
Not much we can do about this. PROJ 6 just migrated to testing and we'll
need to update a lot more of the stack to get them to support it fully.
QGIS 3.4 has partial support for PROJ 6, 3.8 has full support. But
before we get to that we need to update GDAL to 3.x for its PROJ 6 support.
This is just output from crssync which is unable to sync some projection
definitions from GDAL/PROJ to the QGIS srs.db, and can be safely ignored.
There may be changes for PROJ 6 in upcoming QGIS 3.4.x releases, but
full support will take some time until we upgrade to the 3.10 LTR in
early 2020.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
