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

Accepted debputy 0.1.46~bpo12+1 (source) into stable-backports



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

Format: 1.8
Date: Tue, 13 Aug 2024 12:57:25 +0000
Source: debputy
Architecture: source
Version: 0.1.46~bpo12+1
Distribution: bookworm-backports
Urgency: medium
Maintainer: Debputy Maintainers <debputy@packages.debian.org>
Changed-By: Niels Thykier <niels@thykier.net>
Closes: 1076346 1078448
Changes:
 debputy (0.1.46~bpo12+1) bookworm-backports; urgency=medium
 .
   * Rebuild for bookworm-backports.
 .
 debputy (0.1.46) unstable; urgency=medium
 .
   * LSP:
     - Improve wording of and fix typo in hover docs.
     - Fix a typo of `hyphen-` that would distrupt "name to section"
       checks for `hyphen-` packages.
 .
   [ Niels Thykier ]
   * LSP: Fix typo of `hyphen-` and improve wording `Multi-Arch` field
   * debputy: Hoist `nocheck` and `nodoc` into `DEB_BUILD_OPTIONS`
     Thanks to Chris Hofstaedtler <zeha@debian.org>
   * Skip `debian/foo.1` for packager provided files typo checks.
     Thanks to Chris Hofstaedtler <zeha@debian.org>
   * Set `PKG_CONFIG` ENV var for  `perl-makemaker`
   * Fix bug in initialization of `EnvironmentModification` (only affects
     packages in `full` integration mode).
   * Fix bug in escape_util and have it use more readable output by default
   * Fix bug where pre-compressed manpage would be corrupted.
     Thanks to Andrey Rakhmatullin <wrar@debian.org> (Closes: #1078448)
 .
   [ Guillem Jover ]
   * LSP: Fix typos in several descriptions
 .
 debputy (0.1.45) unstable; urgency=medium
 .
   * Manifest:
     - Add new `default-build-environment`, `build-environments` and `build-rules`
       for the new `full` integration mode where `debhelper` is no longer driving
       the build.
     - Port all `debhelper` provided build systems to have an native `debputy`
       counter part with a few tweaks.
 .
 .
   * LSP/Lint:
     - Add `xpm` as a known extension for packager files
     - Add `Build-Driver` as a known field for `debian/control`.
     - Add `Files-Excluded` and `Files-Included` as known fields for DEP-5
     - Quote values in completation items for the manifest. This means that
       the value for `manifest-version` is now properly YAML quoted.
 .
   * debputy: Remove `--spellcheck` from "random" subcommands
   * debputy: Fix missing warning with `--debug` (it was supposed to be omitted,
     but never was due to exception flow).
   * debputy reformat: Fix bug where orphaned packages would have a style by default
   * doc: Document decision on plugin module import vs. initialization design
   * LSP/Lint: Fix crash with certain field being duplicated
   * MANIFEST-FORMAT.md: Fix wording
   * Add initial minimal `Build-Driver` support meaning that `debputy` can now use
     `dpkg-buildpackage`'s new `Build-Driver` support to drive the build without
     relying on `dh`. This requires bleeding edge features in `dpkg-buildpackage`
     and `debputy`.
   * Avoid stacktrace for CTRL + C during `run_command`
   * Improve error tracking related to plugins
   * Add remark about `env:` manifest variables sometimes respecting
     `build-environment`.
 .
 debputy (0.1.44) unstable; urgency=medium
 .
   * LSP:
     - Provide hover docs for packages in relationship fields. Due to
       implementation limitations, OR relations (`foo | bar`) do not
       work. The hover doc relies on the system's APT cache with all
       the limitations from that (like the data not matching the target
       distribution)
     - Fix wording in the synopsis hover doc
 .
   * debputy reformat: If possible provide the reformatting tool when the
     style cannot be applied.
   * debputy: Remove `printf` debug when log level is changed
   * debputy: Prefer using line numbers in error messages when available
   * editor-config: Improve the LSP config for `eglot`
   * debputy: Improve mode correction for `*.pm` files.
     Thanks to Russ Allbery <rra@debian.org> (Closes: #1076346)
 .
 debputy (0.1.43) unstable; urgency=medium
 .
   * debputy: Only warn about missing `-dev` SO symlinks for libraries
     in common lib paths (such as usr/lib/${MA})
   * debputy: Fix bug where `DH_VERBOSE` would fail to print all
     commands
   * debputy: Distinguish between `--debug` and `DH_VERBOSE` in terms
     of verbosity.
   * debputy: Restore `Multi-Arch: same` field in dbgsym packages.
     Thanks to Russ Allbery <rra@debian.org>
 .
 debputy (0.1.42) unstable; urgency=medium
 .
   * LSP/Lint:
     - Fix exception on some syntax errors
     - Add `X?-Ruby-Versions` as a known (obsolete) field
     - Include the final line of context (`debputy lint`-only)
     - Syntax check dependency relation fields
     - Detect incorrect version operators in `Provides`
     - Fix crash on package stanzas without `Package` field
     - Flag usage of `|` in relationship fields that does not
       support it
     - Fix invalid ranges for some checks when using field comments
 .
 debputy (0.1.41) unstable; urgency=medium
 .
   * LSP/Lint:
     - Fix typo in diagnostic message
     - Reduce the number of false positive pkgfile typo warnings.
       Thanks to Otto Kekäläinen <otto@debian.org> (Closes: debputy#109)
     - Avoid recommending name segment for packaging files that do not
       support that.  Note all `debhelper` files currently "support"
       name segments as far as `debputy` can tell, since `dh_assistant`
       does not track this feature.
   * debputy reformat: Fix error in instructions
   * debputy-documentation.json: Add `debian/lintian-brush.conf` as
     known file.
 .
 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:
 8090ec6d2baa492ce268516bec7ed566d77cb5db 1924 debputy_0.1.46~bpo12+1.dsc
 32929e7dd1c8a46b5eaf9cecd32d87239366233b 470944 debputy_0.1.46~bpo12+1.tar.xz
Checksums-Sha256:
 64fa567dcb37c4c43e151d52dd01f60625f9685662c9977e368791c4947f9256 1924 debputy_0.1.46~bpo12+1.dsc
 6d12469573e3b0facde453165da2ac853fb29506b60d64479a07a5e3def2f789 470944 debputy_0.1.46~bpo12+1.tar.xz
Files:
 13026173378a4a841f737e8ac18b8a48 1924 devel optional debputy_0.1.46~bpo12+1.dsc
 53a034ac239ce8dd18c0ee32bdb7384a 470944 devel optional debputy_0.1.46~bpo12+1.tar.xz

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

iQFGBAEBCgAwFiEE9ecZmu9eXGflVYc/dA1oiINl0okFAma7WO0SHG5pZWxzQHRo
eWtpZXIubmV0AAoJEHQNaIiDZdKJBMIH/1GqKiErwq6kKQ94kNhEN+3oardB0vz9
pQN/iN33LqqhVPxHQQdXxD/afwy+YaQ3XmMPYJC7ItPlsdKobbMae/YgUeoi3tMR
ZsCApIhXePDckMGBihc453yjKHUitOx2BXtOz+jmpPFaQOGbgBRlN5wTgJmrSOsv
ij2DIYHQ2fMQGqa3EX28tSEjM3Gc/+MOpmkUy4XKrGSh4yZH2XTo9xrdj7Ndtw3/
PQodL9YUixdlbIDWXdN8Np0AV3aDs+EPexlgo/uJYe1HrFY4ywhNCclxvyjUW4z7
yqhgtTPaqPvVoTkeX8SqfcOuWi6YXCgtuAbgiQa255piv7U4YXhq3KI=
=BAa4
-----END PGP SIGNATURE-----

Attachment: pgpZXmwJFMi6p.pgp
Description: PGP signature


Reply to: