Bug#987895: libyaml: 0.2.5 released upstream, not detected by watch file

Greetings, On Sun, May 01, 2022 at 03:06:12PM +0200, Florian Ernst wrote: > Could you please comment on ? > > To me it feels like the libyaml package might be in need of salvaging as > per Developer's Reference (5.12) and the Debian Wiki >

Bug#987895: libyaml: 0.2.5 released upstream, not detected by watch file

Hello Anders, On Wed, Mar 30, 2022 at 05:54:52PM +0200, Florian Ernst wrote: > I saw that you had been active in Debian recently, which is a relief as > I was wondering whether the libyaml package might be in need of > salvaging, given the apparent lack of activity over the last years. Could you

Bug#987895: libyaml: 0.2.5 released upstream, not detected by watch file

Hello Anders, I saw that you had been active in Debian recently, which is a relief as I was wondering whether the libyaml package might be in need of salvaging, given the apparent lack of activity over the last years. Please share your thoughts on the topics below. On Sat, Mar 05, 2022 at

Bug#987895: libyaml: 0.2.5 released upstream, not detected by watch file

Hello Anders, On Sat, Feb 19, 2022 at 10:48:37AM +0100, Florian Ernst wrote: > [...] > Just as a heads-up, with the new upstream source the current packaging > still manages to build new packages, even though there seems to be some > doc-base weirdness now. The debdiff looks OK, and lintian has

Bug#987895: libyaml: 0.2.5 released upstream, not detected by watch file

Source: libyaml Version: 0.2.2-1 Severity: normal libyaml 0.2.5 was released upstream, probably useful to package it post-bullseye. The current debian/watch file does not detect it, it only finds 0.2.4. The uscan man page provides a template for github packages with uscan version=4. The latest