Hi,
On 10/25/18 3:17 PM, David Lamparter wrote:
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "frr"
* Package name : frr
Version : 6.0.1-1
Upstream Author : FRRouting-dev <d...@lists.frrouting.org>
* URL : https://frrouting.org/
* License : GPLv2 and LGPLv2.1
Section : net
This replaces the "quagga" package, which FRRouting is a fork of.
It builds those binary packages:
frr - BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon forked from Quagga
frr-dbg - BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (debug symbols)
frr-doc - BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (documentation)
frr-pythontools - BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (Python
Tools)
frr-rpki-rtrlib - FRRouting RTRlib RPKI support
frr-snmp - FRRouting SNMP support
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/frr
Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/f/frr/frr_6.0.1-1.dsc
More information about frr can be obtained from https://frrouting.org
Changes since the last upload is not applicable since this is the first
upload.
I expect there still is feedback that I need to address in regards to
the Debian packaging on this and I will likely be uploading further
revisions in the coming days.
I did not build the package. My comment:
There are many lintian info warnings that can be fixed easily:
I no-symbols-control-file
usr/lib/x86_64-linux-gnu/libfrrospfapiclient.so.0.0.0
usr/lib/x86_64-linux-gnu/libfrr.so.0.0.0
https://wiki.debian.org/UsingSymbolsFiles
I possible-documentation-but-no-doc-base-registration
I spelling-error-in-binary # a lot
I spelling-error-in-manpage # a lot
I systemd-service-file-missing-documentation-key
lib/systemd/system/frr.service
O package-name-doesnt-match-sonames
libfrr0 libfrrospfapiclient0 (override comment: libfrr* are for
internal use only and do not provide a stable API or ABI. soname / library
versioning is irrelevant and they must always be shipped exact-matching to the
daemons compiled against it)
It is a package name. That's all.
The lib can not be trusted?
O systemd-service-file-refers-to-unusual-wantedby-target
lib/systemd/system/frr.service network-online.target (override comment:
we're a bit special since we provide network connectivity by starting up
routing protocols.)
X duplicate-files
usr/share/doc/frr/examples/pbrd.conf.sample
usr/share/doc/frr/examples/staticd.conf.sample
frr-rpki-rtrlib
I extended-description-is-probably-too-short
I hardening-no-fortify-functions
usr/lib/x86_64-linux-gnu/frr/modules/bgpd_rpki.so
frr source
I debian-control-has-obsolete-dbg-package
frr-dbg
I duplicate-long-description
frr-doc frr-pythontools
I ored-build-depends-on-obsolete-package
build-depends: dh-systemd <!pkg.frr.nosystemd> => use debhelper (>=
9.20160709)
P debian-watch-does-not-check-gpg-signature
P package-uses-old-debhelper-compat-version
9
There is a problem with version 11?
O alternatively-build-depends-on-python-sphinx-and-python3-sphinx
(override comment: these are for build-compatibility on older distros
(e.g. Ubuntu 14.04))
It is a new package. It is preferable to not upload Python 2
X upstream-metadata-file-is-missing
Regards,
Herbert
