RE : RE : SAGE in Debian status page
Good morning,
Yes now it works, but I have plenty of lintian warning or errors.
can you fix them all and explain also the name of the library package ?
thanks
Frederic
N: Using profile debian/main.
N: Setting up lab in /tmp/temp-lintian-lab-yHq5dzKbx6 ...
N: ----
N: Processing changes file polybori (version 0.8.2-0, arch source all i386) ...
N: ----
N: Processing source package polybori (version 0.8.2-0, arch source) ...
W: polybori source: dh_pycentral-is-obsolete line 71
N:
N: This package calls dh_pycentral in its debian/rules file. dh_pycentral
N: is deprecated and has been replaced by dh_python2.
N:
N: dh_python2 is available in Squeeze; if backporting the package to a
N: Lenny or older system, please ignore this warning.
N:
N: Refer to http://wiki.debian.org/Python/PyCentral2DhPython2 for details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: debhelper, Type: source
N:
W: polybori source: dh_pycentral-is-obsolete line 103
W: polybori source: debhelper-but-no-misc-depends polybori-doc
N:
N: The source package uses debhelper, but it does not include
N: ${misc:Depends} in the given binary package's debian/control entry. Any
N: debhelper command may add dependencies to ${misc:Depends} that are
N: required for the work that it does, so recommended best practice is to
N: always add ${misc:Depends} to the dependencies of each binary package if
N: debhelper is in use.
N:
N: Refer to the debhelper(7) manual page for details.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: debhelper, Type: source
N:
E: polybori source: debian-revision-should-not-be-zero 0.8.2-0
N:
N: The debian version part (the part after the -) should start with one,
N: not with zero. This is to ensure that a correctly-done Maintainer Upload
N: will always have a higher version number than a Non-Maintainer upload: a
N: NMU could have been prepared which introduces this upstream version with
N: Debian-revision -0.1
N:
N: Refer to Debian Developer's Reference section 5.11.2 (NMUs and
N: debian/changelog) for details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: fields, Type: binary, udeb, source
N:
W: polybori source: debian-rules-missing-recommended-target build-arch
N:
N: The debian/rules file for this package does not provide one of the
N: recommended targets. All of build-arch and build-indep should be
N: provided, even if they don't do anything for this package. If this
N: package does not currently split building of architecture dependent and
N: independent packages, the following rules may be added to fall back to
N: the build target:
N:
N: build-arch: build
N: build-indep: build
N:
N: Note that the following form is recommended however:
N:
N: build: build-arch build-indep
N: build-arch: build-stamp
N: build-indep: build-stamp
N: build-stamp:
N: build here
N:
N: These targets will be required by policy in the future, so should be
N: added to prevent future breakage.
N:
N: Refer to Debian Policy Manual section 4.9 (Main building script:
N: debian/rules) for details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: rules, Type: source
N:
W: polybori source: debian-rules-missing-recommended-target build-indep
W: polybori source: package-would-benefit-from-build-arch-targets
N:
N: The source package does not have both a build-arch and a build-indep
N: target. Furthermore it is part of the selected set of packages to be
N: fixed for Wheezy.
N:
N: Please consider adding both the build-arch and build-indep targets.
N:
N: Refer to http://bugs.debian.org/629385 and
N: https://wiki.debian.org/ReleaseGoals/BuildArchTarget for details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: rules, Type: source
N:
W: polybori source: ancient-standards-version 3.8.0 (current is 3.9.4)
N:
N: The source package refers to a Standards-Version that has been obsolete
N: for more than two years. Please update your package to latest Policy and
N: set this control field appropriately.
N:
N: If the package is already compliant with the current standards, you
N: don't have to re-upload the package just to adjust the Standards-Version
N: control field. However, please remember to update this field next time
N: you upload the package.
N:
N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the
N: debian-policy package for a summary of changes in newer versions of
N: Policy.
N:
N: Refer to http://www.debian.org/doc/debian-policy/upgrading-checklist for
N: details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: standards-version, Type: source
N:
N: ----
N: Processing binary package polybori-doc (version 0.8.2-0, arch all) ...
E: polybori-doc: debian-revision-should-not-be-zero 0.8.2-0
N: ----
N: Processing binary package libpolybori-dev (version 0.8.2-0, arch i386) ...
E: libpolybori-dev: debian-revision-should-not-be-zero 0.8.2-0
N: ----
N: Processing binary package python-polybori (version 0.8.2-0, arch i386) ...
W: python-polybori: hardening-no-relro usr/lib/python2.6/dist-packages/polybori/dynamic/PyPolyBoRi.so
N:
N: This package provides an ELF binary that lacks the "read-only
N: relocation" link flag. This package was likely not built with the
N: default Debian compiler flags defined by dpkg-buildflags. If built using
N: dpkg-buildflags directly, be sure to import LDFLAGS.
N:
N: Refer to http://wiki.debian.org/Hardening for details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: binaries, Type: binary, udeb
N:
W: python-polybori: hardening-no-fortify-functions usr/lib/python2.6/dist-packages/polybori/dynamic/PyPolyBoRi.so
N:
N: This package provides an ELF binary that lacks the use of fortified libc
N: functions. Either there are no potentially unfortified functions called
N: by any routines, all unfortified calls have already been fully validated
N: at compile-time, or the package was not built with the default Debian
N: compiler flags defined by dpkg-buildflags. If built using
N: dpkg-buildflags directly, be sure to import CPPFLAGS.
N:
N: NB: Due to false-positives, Lintian ignores some unprotected functions
N: (e.g. memcpy).
N:
N: Refer to http://wiki.debian.org/Hardening and
N: http://bugs.debian.org/673112 for details.
N:
N: Severity: normal, Certainty: possible
N:
N: Check: binaries, Type: binary, udeb
N:
W: python-polybori: hardening-no-relro usr/lib/python2.7/dist-packages/polybori/dynamic/PyPolyBoRi.so
W: python-polybori: hardening-no-fortify-functions usr/lib/python2.7/dist-packages/polybori/dynamic/PyPolyBoRi.so
E: python-polybori: debian-revision-should-not-be-zero 0.8.2-0
W: python-polybori: image-file-in-usr-lib usr/lib/polybori/gui/polybori.png
N:
N: This package installs a pixmap or a bitmap within /usr/lib. According to
N: the Filesystem Hierarchy Standard, architecture-independent files need
N: to be placed within /usr/share instead.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: files, Type: binary, udeb
N:
N: ----
N: Processing binary package libpolybori-0.8.2-0 (version 0.8.2-0, arch i386) ...
W: libpolybori-0.8.2-0: hardening-no-relro usr/lib/libpolybori-0.8.2.so.0.0.0
W: libpolybori-0.8.2-0: hardening-no-fortify-functions usr/lib/libpolybori-0.8.2.so.0.0.0
W: libpolybori-0.8.2-0: hardening-no-relro usr/lib/libpolybori_groebner-0.8.2.so.0.0.0
W: libpolybori-0.8.2-0: hardening-no-fortify-functions usr/lib/libpolybori_groebner-0.8.2.so.0.0.0
E: libpolybori-0.8.2-0: debian-revision-should-not-be-zero 0.8.2-0
Reply to: