Source: liblognorm
Version: 2.0.5-1.1
Severity: important
X-Debbugs-Cc: Pierre Chifflier <pol...@debian.org>, Michael Biebl 
<bi...@debian.org>

Greetings,

hereby I declare my intention to salvage the "liblognorm" package using
the procedure described in the Developer's Reference (5.12) and the
Debian Wiki <https://wiki.debian.org/PackageSalvaging>.

Criteria are met as follows:

* The package is in clear need of some love and care:
  * There is an upstream release missing, cf.
    <https://bugs.debian.org/959007>, filed 28 Apr 2020.
  * There is work needed from a quality-assurance perspective as the
    packaging uses outdated / deprecated standards, cf.
    <https://lintian.debian.org/sources/liblognorm>, and it FTCBFS, cf.
    <https://bugs.debian.org/930599>

    AND

* An upload is needed to fix this.

    AND

* At least one to the following applies (non-applicable omitted):
  * There is no visible activity regarding the package for six months.
    Attempting to elicit a maintainer response failed, cf.
    <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959007#10> ff.
  * The last upload was an NMU and there was no maintainer upload within
    one year.
    Last maintainer upload was on 2018-04-29, last NMU (and package
    update) on 2020-03-15.

My objective is to have this package in Debian, and in good shape. So
if you (maintainer) want to resume taking care of it, please do. And in
case you object or already have other plans, just let me know.

As this package is a direct dependency of rsyslog and is also coming
from the same upstream I'm CC'ing the rsyslog maintainer who might have
something to say on this.

Kind regards,
Flo

Attachment: signature.asc
Description: PGP signature

Reply via email to