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 template is slightly different to the one
currently in debian/watch, perhaps it will find 0.2.5.

FWIW, the uscan v4 template for github packages only manages to find the
stripped source package, but the attached one does the trick.

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 some old
and some new qualms that could/should be investigated. Please also find
attached the sbuild output.

Cheers,
Flo

Hello Anders,

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

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

Cheers,
Flo

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.
free to pick up the parts you like - if any - for any eventual libyaml
update.

The changelog currently reads
| libyaml (0.2.5-0.1) UNRELEASED; urgency=medium
|
|   [ Debian Janitor ]
|   * Use secure copyright file specification URI.
|   * Set debhelper-compat version in Build-Depends.
|   * Set upstream metadata fields: Bug-Database, Bug-Submit (from ./configure),
|     Repository, Repository-Browse.
|   * Drop transition for old debug package migration.
|   * Update standards version to 4.6.0, no changes needed.
|
|   [ Florian Ernst ]
|   * Non-maintainer upload.
|   * [de63dcd] debian/watch: update as per latest uscan recommendations.
|     This allows detecting new upstream releases again and also migrates
|     to the actual upstream source tarballs not containing any pre-built
|     stuff like documentation, saving a bunch of lintian errors/warnings.
|   * [1b08058] New upstream version 0.2.5 (Closes: #987895)
|   * [dfbe297] debian/copyright: update years according to most recent changes
|   * [183f9d4] upgrade to recommended debhelper-compat (= 13)
|     But ignore libtool library during installation and simplify debian/rules
|   * [982974f] debian/rules: enable hardening=+all
|   * [1f7cabe] debian/libyaml-0-2.symbols: add Build-Depends-Package
|     meta-information
|   * [1104826] debian/control: declare Rules-Requires-Root: no
|   * [8f2e2e6] debian/tests/: add upstream tests as autopkgtest

i.e. it incorporates the Janitor MR from
<https://salsa.debian.org/andersk/libyaml/-/merge_requests/1>,
changes the upstream tarball and brings the packaging up-to-speed with
respect to recent best practices.

All packaging, including the autopkgtest, has been checked: the Salsa
pipeline at
<https://salsa.debian.org/florian/libyaml/-/pipelines/363041> for
building and static checks, and I successfully rebuilt all direct
reverse build-depends against the updated package (well, all that are
currently able to build, that is, as some are rather broken at the
moment). Full logs are available, of course.

You can find my state of packaging in a fork of your repo at
<https://salsa.debian.org/florian/libyaml>.

Cheers,
Flo

Hello Anders,

Could you please comment on <https://bugs.debian.org/987895>?

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
<https://wiki.debian.org/PackageSalvaging>, so please speak up.

Kind regards,
Flo

It would be very nice to get this package updated.
So I hope the NMU or package salvaging process will be started soon.

Greetings,

JFTR, I now started the salvaging process in
<https://bugs.debian.org/1012344>.

Kind regards,
Flo

We believe that the bug you reported is fixed in the latest version of
libyaml, 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 987895@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 libyaml 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: Wed, 06 Jul 2022 16:45:09 +0200
Source: libyaml
Architecture: source
Version: 0.2.5-1
Distribution: unstable
Urgency: medium
Maintainer: Florian Ernst <florian@debian.org>
Changed-By: Florian Ernst <florian@debian.org>
Closes: 987895 1012344
Changes:
 libyaml (0.2.5-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure copyright file specification URI.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit (from ./configure),
     Repository, Repository-Browse.
   * Drop transition for old debug package migration.
   * Update standards version to 4.6.0, no changes needed.
 .
   [ Florian Ernst ]
   * [de63dcd] debian/watch: update as per latest uscan recommendations.
     This allows detecting new upstream releases again and also migrates
     to the actual upstream source tarballs not containing any pre-built
     stuff like documentation, saving a bunch of lintian errors/warnings.
   * [1b08058] New upstream version 0.2.5 (Closes: #987895)
   * [dfbe297] debian/copyright: update years according to most recent changes
   * [183f9d4] upgrade to recommended debhelper-compat (= 13)
     But ignore libtool library during installation and simplify debian/rules
   * [982974f] debian/rules: enable hardening=+all
   * [1f7cabe] debian/libyaml-0-2.symbols: add Build-Depends-Package
     meta-information
   * [1104826] debian/control: declare Rules-Requires-Root: no
   * [8f2e2e6] debian/tests/: add upstream tests as autopkgtest
   * [f5e5378] Add Salsa pipeline via debian/salsa-ci.yml file
   * [88cfa12] salvaging the package and moving to Debian group on Salsa
     (Closes: #1012344)
   * [da1b78b] debian/control: Standards-Version: 4.6.1.0 (no further changes
     required)
Checksums-Sha1:
 dbf88ef7db7667d2e3f39e0c0d12b5d52be024dd 2071 libyaml_0.2.5-1.dsc
 db474288fde305468602e051d963c6936ef5a9ae 85055 libyaml_0.2.5.orig.tar.gz
 de733ba5904f1da6e24f017a44f2128d2e8635b7 5324 libyaml_0.2.5-1.debian.tar.xz
 b99aa5bd697dc6f5e37aaa7eeae5fcdeea1baed1 7089 libyaml_0.2.5-1_amd64.buildinfo
Checksums-Sha256:
 1edbf86e5cd76937ff62892ba6c2537456d645d834d4cd4a82430b8be7051bf4 2071 libyaml_0.2.5-1.dsc
 fa240dbf262be053f3898006d502d514936c818e422afdcf33921c63bed9bf2e 85055 libyaml_0.2.5.orig.tar.gz
 8730e0510129e516c3c7c1cda7428e02a0a122699e57ed203f835a338a686d1f 5324 libyaml_0.2.5-1.debian.tar.xz
 cfe9bba074dc5be91bf0e43ea37881a9a136efef754a86060d23bbfe635d57c2 7089 libyaml_0.2.5-1_amd64.buildinfo
Files:
 97f5e2a9bb0c6899898545bb861f66f9 2071 libs optional libyaml_0.2.5-1.dsc
 163fc1e22153d3e2cebfe5cbb43a1769 85055 libs optional libyaml_0.2.5.orig.tar.gz
 b85c86c592b17615c9669618fc151c4d 5324 libs optional libyaml_0.2.5-1.debian.tar.xz
 66c4d3ce012696155d60cc46d843279f 7089 libs optional libyaml_0.2.5-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEBn03XtJwVyplJ26xBjdBuvXdHs4FAmLFoTwACgkQBjdBuvXd
Hs7J+w//d2Zgj8r+FRB8tPf3t9B3x///lo0yZgreWbZY1uWccgGXkQ2Bo4mbXZCF
LrEG2eW7O4NYzuBTivxRJrrWZZ7iBnROpSG4EJTFjnDWGhjOXZ9/disW6e+r+Cgf
EcF/NkG65MwPqdue8FwQV15FAGRXkBizKYcGCG3fafj/YL3hAE43/pyeQWAhOvLM
q9XPSVuCU3NkDE2fK3xL8UVip2UIOAiMAb+aIqZeVgaCFJNZHjE0WNVCKyG9dkFi
Weavai7CjzspdTwabQ1GhhWBwE6N7y/dEBLRyHbnJyz9ZvuCBrD5aU1r57x3Fotc
HuUhsWxncMNaZzxLulGbiS3dWzWaymg+71NifrI3+cp+SrK6t8a2R/2glTlwCUF9
S0PGNr4SfSCzQLpxjgeaa7g8Vmn17q2Ksr77rD7G925yOUr6mPKkAqIGPyJaTOK0
ZZHz7ldslWyDrbeW0LfEQfodCQRDxHfCM36Y1mhvT8I58EfEFVbunmknhuvvN8Go
SPXtxTvt0UaznjyD4A/sQRuNZFKB7IDz0vvyKwcKok4XsDeImExZQjHBvDVEXdiN
aCwvWqugmO2qpJTwpw8KZbemyaP7a6Kux+9Cw4yV62o5smKAag39iP7fQXEvm2lk
6urAo3dcdI9rNDTWzyV8jfbv/dY5dvrGigynW2wdQiBL8FTK6BQ=
=0Huv
-----END PGP SIGNATURE-----