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 05:45:59PM +0100, Florian Ernst wrote: > 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 some old > > and some new qualms that could/should be investigated. Please also find > > attached the sbuild output. > > 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. So I just took some time and prepared a more exhaustive update. Feel 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
signature.asc
Description: PGP signature
