[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted debputy 0.1.40 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 30 Jun 2024 12:43:55 +0000
Source: debputy
Architecture: source
Version: 0.1.40
Distribution: unstable
Urgency: medium
Maintainer: Debputy Maintainers <debputy@packages.debian.org>
Changed-By: Niels Thykier <niels@thykier.net>
Changes:
 debputy (0.1.40) unstable; urgency=medium
 .
   * Manifest changes:
     - The manifest parser now validates the used features against the
       integration mode. This causes some invalid manifests to be
       detected at parse time (`debputy manifest`) rather than at
       build time for `dh-sequence-zz-debputy-rrr`).
 .
   * LSP/Lint:
     - Use `dh_assistant` to determine inactive commands. This improves
       the check to cover commands that `debhelper` knows are inactive.
       However, the functionality now requires `debhelper (>= 13.15~)`.
     - Apply sequences from `debian/control` when analyzing `debian/rules`.
       Note for LSP: Depending on your editor, you may have to save
       `debian/control` first and then trigger a change in `debian/rules`
       for it to be visible. (Known issue, see debputy#103 and debputy#108)
     - Provide inlay hints for inherited fields in `debian/control`.
     - Provide integration mode level checks for most features. The
       capabilities on `path-metadata` is a known and notable case where
       the LSP/Lint side is silent where `debputy check-manifest` would
       complain.
     - Provide a warning for unknown capabilities (that `cap_from_text`
       does not recognize). Previously, this would only appear in
       `debputy check-manifest` or during builds.
     - Validate boolean and enum-like values for attributes of the
       manifest. These would previously only be caught by
       `debputy check-manifest` or during builds.
 .
   * debputy: Remove internal `--integration-mode=rrr` option.
   * dh_debputy: Remove internal `--integration-mode=rrr` option.
Checksums-Sha1:
 008d3c34eff2f6dfc34cca2bd7849a6e76eb4df4 2067 debputy_0.1.40.dsc
 4de70fcebe6feac59df26afdb6968d4784d4f465 434696 debputy_0.1.40.tar.xz
Checksums-Sha256:
 0e28959a9ba251f48e4fef346987dcff8ec13a275b56576e73265a08640e017e 2067 debputy_0.1.40.dsc
 462756297a6d06d7860a5b680b67be9f74530a4acbbbc425628671b59a3f32b9 434696 debputy_0.1.40.tar.xz
Files:
 a5fdd334e2ba76058eae7cad89cca1dc 2067 devel optional debputy_0.1.40.dsc
 e0e841312947f07713252a57a7edcae3 434696 devel optional debputy_0.1.40.tar.xz

-----BEGIN PGP SIGNATURE-----

iQFGBAEBCgAwFiEE9ecZmu9eXGflVYc/dA1oiINl0okFAmaBVR4SHG5pZWxzQHRo
eWtpZXIubmV0AAoJEHQNaIiDZdKJJGMH/2xPAqKd1di0liLuUnTnAjmtgY4R9Xfq
sKRQqH+5drE97Dj4FVe8MzNN3babopcbU0UEbecGE7R+Qsv0Ficgm9HO1AkMcts8
I4VhpsjRsrwOzRmvY1tyjWwGb5XowCbGSCZNqZ6/oUv65k7qGwS0ud55aEPK3GIk
HSYvVK/k2VCGi8c6IqjnJzCCi+fdLOjI8iEUIz3eUH6NGyML8WxbyZgRbydEuj5U
EaCZMzfJAF+DiMbFgw5iNldiSsdvctMbWfuM4RRwVWLb5Bix7DSNIIXHHco2ylZ1
eB8BlehO4eEheEVj45KqYYsIED7F3RYLV34KnazZXysbVNGEeX9L3qY=
=yEHc
-----END PGP SIGNATURE-----

Attachment: pgp_bU1gAq8W0.pgp
Description: PGP signature


Reply to: