Bug#959007: liblognorm: Please provide new upstream release (2.0.6)

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 signature.asc Description: PGP signature

Bug#959007: liblognorm: Please provide new upstream release (2.0.6)

Hello Pierre, On Fri, Feb 18, 2022 at 10:20:20PM +0100, Florian Ernst wrote: > 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" >

Bug#959007: liblognorm: Please provide new upstream release (2.0.6)

On Sat, Jan 29, 2022 at 08:54:16PM +0100, Florian Ernst wrote: > JFTR, the Changelog at > reads as > follows: FWIW, I can confirm that when you apply the current packaging to upstream 2.0.6 it still manages to build its packages (albeit

Bug#959007: liblognorm: Please provide new upstream release (2.0.6)

On Mon, Apr 27, 2020 at 09:37:49PM -0400, Boyuan Yang wrote: > 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

Bug#959007: liblognorm: Please provide new upstream release (2.0.6)

Source: liblognorm Version: 2.0.5-1.1 Severity: normal 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? -- Thanks, Boyuan Yang signature.asc