Dear Debian liblognorm maintainer,

The liglognorm upstream has been providing new upstream release 2.0.6 since
2018. Is there any possibility to have this version packaged and provided in
Debian?

JFTR, the Changelog at
<https://www.liblognorm.com/news/liblognorm-2-0-6-released/> reads as
follows:

| Version 2.0.6, 2018-11-06
|
| - implement Checkpoint LEA transfer format
|   … at least if we guess right that this is the format name. This
|   type of format seems to be seen in syslog message. Checkpoint does
|   not provide a spec, so everything is guesswork… 🙁
|   closes https://github.com/rsyslog/liblognorm/issues/309
| - made build on AIX
|   Thanks to Philippe Duveau for the patch.
| - fixes and improvements in bash scripting
|   mostly based on shellcheck recommandations (via CodeFactor.com)
| - string parser: add “lazy” matching mode
|   This introduces paramter “matching.lazy”. See doc for details.
| - bugfix: suppress invalid param error for field name “-”
|   Suppress invalid param error for name for hexnumber, float, number,
|   date-rfc3164 and date-rfc5424. It will just check if name is “-” to
|   make sure that we only suppress the error message in case we do not
|   want to capture something.
|   Thanks to Sol Huebner for the patch.
|   closes https://github.com/rsyslog/liblognorm/issues/270
| - bugfix: cisco-interface-spec did not succeed when at end of line
|   Thanks to Sol Huebner for the patch.
|   closes https://github.com/rsyslog/liblognorm/issues/229

The bugfixes and the Checkpoint LEA transfer format seems to make this
worthwhile. Pierre, do you maybe need some support in packaging this?

Cheers,
Flo

FWIW, I can confirm that when you apply the current packaging to upstream
2.0.6 it still manages to build its packages (albeit not entirely
lintian clean and missing two new symbols "ln_constructCheckpointLEA"
and "ln_destructCheckpointLEA").

Cheers,
Flo

Hello Pierre,

Could you please comment on whether you have any plans for liblognorm
packaging? Thanks.

As written before there are updates available, and I am willing to help.

Cheers,
Flo

Hello Pierre,

could you please comment on this, as I am wondering by now whether
liblognorm might be in need of salvaging.

Best regards,
Flo

Greetings,

To fix the issues with this package, I've prepared a salvaging upload
for liblognorm (versioned as 2.0.6-1), debdiff attached. An upload to
DELAYED/11 will follow shortly. Please feel free to tell me if I should
delay it longer or even cancel it.

If this upload will be accepted I'm planning to fix
<https://bugs.debian.org/930599> in a separate upload. This fix is not
part of the current upload as it requires a roundtrip through NEW, and I
preferred to first have the new upstream release in place.

Kind regards,
Flo

We believe that the bug you reported is fixed in the latest version of
liblognorm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959007@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Florian Ernst <florian@debian.org> (supplier of updated liblognorm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 05 Jun 2022 07:51:00 +0200
Source: liblognorm
Architecture: source
Version: 2.0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Florian Ernst <florian@debian.org>
Changed-By: Florian Ernst <florian@debian.org>
Closes: 959007 1010433
Changes:
 liblognorm (2.0.6-1) unstable; urgency=medium
 .
   * New maintainer (Closes: #1010433)
     - update packaging to match current best practices
       + debhelper-compat (= 13)
       + all hardening options
       + Vcs-* fields and metadata
   * New upstream release (Closes: #959007)
     - update liblognorm5.symbols accordingly
     - add debian/patches/spelling.patch
Checksums-Sha1:
 c4373c3145d33e2839ae7822442a1e0d871ca121 2042 liblognorm_2.0.6-1.dsc
 61c72b58f511924ab80401b0719803963872c73d 666712 liblognorm_2.0.6.orig.tar.gz
 021f9320335b7345a5bb97888d83293e7e9c9775 16100 liblognorm_2.0.6-1.debian.tar.xz
 8b4d0cacb9d916706749b5d0c7c63908085d3a3f 9048 liblognorm_2.0.6-1_amd64.buildinfo
Checksums-Sha256:
 c466dc4998a4c18cdd986d8c6900d91a8b8f7c96ea03597da250452dcbe81665 2042 liblognorm_2.0.6-1.dsc
 cff057e85c22038992f9ed12eb8d4e63c45adf53a5a51faaa3279f605809f6f2 666712 liblognorm_2.0.6.orig.tar.gz
 127734bc043024ac92c003d5dd971dde20b42c8f0fbe5ca33005751c8e75702a 16100 liblognorm_2.0.6-1.debian.tar.xz
 1a5013edeaec1e73198b35d1366af20326da5184bfd84b73b3cee11baeec3cab 9048 liblognorm_2.0.6-1_amd64.buildinfo
Files:
 6da85e42f3a08f5c8c2b0348b1fafb2b 2042 libs optional liblognorm_2.0.6-1.dsc
 9b6b6b5f76fafbc853c65aad69d5d33b 666712 libs optional liblognorm_2.0.6.orig.tar.gz
 530d5c48c2bac97ef3c28839952ec789 16100 libs optional liblognorm_2.0.6-1.debian.tar.xz
 f738380c8ef3efa7411f5161bbc64032 9048 libs optional liblognorm_2.0.6-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEBn03XtJwVyplJ26xBjdBuvXdHs4FAmKcRWYACgkQBjdBuvXd
Hs6fvA/+JhOwm2kSF45WwtRj8pg9ck8cQ9lYNXNxauegvMNqvMenVU4IK5t2C3Y9
CbWpuUR0ytTaqER3XlAccSYr7653cjTw+7pxORyDBfpiuKrxHkbFSVTcWdFByiQJ
sbe9NILPR4XS7pf4U2IH/114zoCJmvRvciy87PdhSUaRAtQwZLjgNxsG2dBo+Mcr
IuO9jkoWn+NDLLdImIACGe4PxPyiQvkTQT93bjjVQAhA3fTJ4ah+PNPipdwXgFWa
AmCJ7Y+HKp16DXqHodY+CAYVNFdgm9LptSKAAIBXt99jX2jm2LTxBWirGGtXYNM9
M1U4XqIMbvX3IHnhPDNFpB6PzRs0UT9zq32xGvS/6XAkdMJZdVfMP0osS61v/WLA
T6k/BrNRaU/Hr9ZcI9WgxRCG/AVQU0x/D3EkrbX/fqnTFvx1aHNSgjyFb3fPldGQ
r74KRfq/DEV7fmejF2I0X5vj4JgvPT5kroWeI/1zuKniBeWhvuiVt4N0dMNpndLU
zrOUdptSX4b1yCnOXxl3NyLJx2bRe6BnTcQKL+whpTX01Z8aReW+EMw1AvhWSIPW
lYEEo+eKolp3ntwdf6CshqsRPLdppQjrXynTSv1KFLnl/ztaLDbu4HutoUrfcHWf
AnjgDAhKB5MFmcstlp/jnmgyi+T1xC8QGkhuQGs6rJlxw6ZJmfc=
=3EMn
-----END PGP SIGNATURE-----