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

Bug#474604: RoQA: Please remove qgis

Package: ftp.debian.org
Severity: normal

In the middle of a BSP, looking to fix #456064 (failure to build with
g++ 4.3). The more I look into the package, the more bugs I find. In
the existing packages, lintian complains:

E: libqgis1: arch-dependent-file-in-usr-share ./usr/share/qgis/python/qgis/core.so
E: libqgis1: arch-dependent-file-in-usr-share ./usr/share/qgis/python/qgis/gui.so
E: libqgis1: no-shlibs-control-file usr/lib/libqgis_core.so
E: libqgis1: no-shlibs-control-file usr/lib/libqgis_gui.so
E: libqgis1: postinst-must-call-ldconfig usr/lib/libqgis_core.so
E: qgis-plugin-grass: missing-dependency-on-libc needed by ./usr/lib/libqgisgrass.so and 2 others
E: qgis-plugin-grass: no-shlibs-control-file usr/lib/libqgisgrass.so
E: qgis-plugin-grass: postinst-must-call-ldconfig usr/lib/libqgisgrass.so
W: libqgis1-dev: copyright-without-copyright-notice
W: libqgis1-dev: dev-package-should-be-section-libdevel libqgis1-dev
W: libqgis1: copyright-without-copyright-notice
W: libqgis1: package-name-doesnt-match-sonames libqgis-core libqgis-gui
W: qgis-plugin-grass: copyright-without-copyright-notice
W: qgis-plugin-grass: package-name-doesnt-match-sonames libqgisgrass
W: qgis: binary-or-shlib-defines-rpath ./usr/bin/qgis /usr/lib:/usr/lib/python2.4/config
W: qgis: binary-without-manpage usr/bin/msexport
W: qgis: binary-without-manpage usr/bin/qgis
W: qgis: binary-without-manpage usr/bin/qgis_help
W: qgis: copyright-without-copyright-notice
W: qgis: package-contains-upstream-install-documentation usr/share/doc/qgis/INSTALL.gz

There are other outstanding bugs (#425384, #423566). After fixing the
FTBFS bug ready for an NMU, I can see that also:

 * it fails to cleanly rebuild, leaving crap all over the place after
   a first build
 * the shared libraries it installs into /usr/lib don't have sonames
   (it just installs .so files directly)

The package is a mess and needs lots of cleanup love, much more than
it's going to get in an NMU. Please remove it from testing and
unstable ASAP.

Steve McIntyre, Cambridge, UK.                                steve@einval.com
Is there anybody out there?

Reply to: