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

Accepted debputy 0.1.68 (source) into experimental



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

Format: 1.8
Date: Tue, 15 Jul 2025 05:21:31 +0000
Source: debputy
Architecture: source
Version: 0.1.68
Distribution: experimental
Urgency: medium
Maintainer: Debputy Maintainers <debputy@packages.debian.org>
Changed-By: Niels Thykier <niels@thykier.net>
Changes:
 debputy (0.1.68) experimental; urgency=medium
 .
   * LSP/Reformat:
     - The `black` style now rewrites field names to use the canonical
       spelling of fields for fields where `debputy` knows the canonical
       name. Unknown fields remain in their current case/spelling.
 .
   * LSP/Lint:
     - Improve performance of semantic tokens request (LSP only), diagnostics
       (both LSP and `debputy lint` side), and inlay hints (LSP only).
     - Add more sematic tokens for relationship fields
     - Conditionally use `TextDocumentEdit` if the LSP client supports them.
       (bring us one step closer to supporting quick fixes that renames files)
     - Use plugin data for known packaging files to prevent false-positive
       prevention. This also avoids double maintenance of known packaging
       files.
     - Fix crash on typo of key in YAML based files
     - Recognize `.rst` and `.config` as non-typo extensions for files in
       the `debian/` directory.
     - Fix problem where raw type was shown instead of real type in the
       hover docs.
     - Improve YAML value validation to cover more cases. There are still
       constructs where the validation should catch errors but where the
       diagnostic code does not yet have a case for it.
     - Fix quick fix for `manifest-version` value not being quoted. That is,
       using the quick fix caused a diagnostic error. To add insult to injury,
       said error would have a quick fix that did not fix the error.
     - Hide integration mode text from hover docs in d/upstream/metadata
     - Fix crash/exception on completion in completely empty YAML files
     - Make it configurable if syntactical comments are spellchecked
       (Closes: debputy#125)
     - Provide completion suggestions in more cases for YAML based formats
     - Suggest dpkg makefiles as completion in d/rules after `include`
     - Support plugin provided manifest variables in completion + hover in
       `debputy.manifest`.
     - Tweak diagnostic message for using hook targets for inactive dh
       commands.
     - Define two more known substvars in `d/control` by providing hover
       docs and completion suggestions for them.
     - Add `vim-debian` ID for `debian/tests/control` after they added the
       support for it this week in the mainline. Relevant editor config
       snippet examples have been updated.
     - Add more checks of the sign-off line in `d/changelog`
     - Improve completion of variables in `debputy.manifest`. Notably,
       it is now possible to complete them inside an incomplete quote
       (which is a common case for them, since they require quoting).
 .
   * Manifest:
     - All `debputy` provided build systems now accept a `test-rule`
       attribute. It can be used to control when tests should be run
       or when tests should be non-fatal.
     - The definition of the `not` conditional has been corrected.
       It previously allowed an invalid form as well as the intended.
       The invalid form has now been removed.
     - The `for` attributes in build systems now support basic package
       selectors like `arch:all` in addition to plain package names.
 .
   * Plugin API:
     - Add new preferred way for Python plugins to initialize
 .
   * Add `debian/lrc.config` as a known Debian packaging file,
     which also means it is no longer a false positive for the typo
     detection of packaging files in the `debian/` directory.
     (Closes: debputy#135)
   * debputy: Provide clearer error on some types of invalid plugins
   * MANIFEST-FORMAT.md: Create a section on type mappings including
     a full listing of all type mappings provided by `debputy`.
   * Ensure generated MANIFEST-FORMAT.md always ends with a newline
   * MANIFEST-FORMAT.md: Use literal markup for "enum"-like values
   * Set HOME and XDG_RUNTIME_DIR during build similar to `debhelper`.
   * Refactor to ensure dest_dirs from build systems are computed in build env.
     This did not matter for any `debputy` provided build system, but will
     likely be relevant for some third party build systems down the line.
   * Build system: Cache output of `dpkg-buildflags` calls with same `DEB_*`
     env.
   * Fix problem where raw type was shown instead of real type in the static
     docs and in the CLI output for showing docs.
   * debputy: Be more lenient when parsing the LSP/lint config file
   * Support building basic LSP/lint-only version of `debputy` via hatchling
   * Bump Standards-Versions to 4.7.2
   * Enable support for `debian/package.udev` files again
   * migrate-from-dh: Recognise `zz-debputy-rrr` as known
   * debputy: Add a `Commands` field to `.deb` packages (but not `.udeb`)
     for packages that contains binaries in path to `command-not-found`
     (see #638517).
   * debputy: Work around `debhelper` or old `libjson-pp-perl` bug. This
     could cause `debputy` emit false positives for most of the files
     in the `debian/` directory. The problem can be avoided by installing
     either this version of `debputy`, `debhelper/13.25`, or
     `libjson-pp-perl/4.16000-1`. The `trixie` version of `perl` comes
     with the relevant version of `libjson-pp-perl` implied, which is
     why this problem was not reproducible in `trixie`.
Checksums-Sha1:
 2c4655ff9f334d60525e8c8e368a88dae0410ca4 2654 debputy_0.1.68.dsc
 031002c6b315a3017489e4eab72b85f297b1e29e 697284 debputy_0.1.68.tar.xz
 1c182ee87811deee7b4d06ab81c671fbdd4f15b7 1211876 debputy_0.1.68.git.tar.xz
 9b6bdddcdf8eade07ee7711bc0686e1efdefc9c5 18032 debputy_0.1.68_source.buildinfo
Checksums-Sha256:
 68e00c3af668503e1ce05ce10ebf9cfb58d718b504d89a6a493df96d70b255ee 2654 debputy_0.1.68.dsc
 c967be50bc65fc413b6cf727a3a8bdcf7476de14be4db97e98c0e3311bbae9ab 697284 debputy_0.1.68.tar.xz
 f562e5b625f0f2c6683b45e4ca19c7c64eb06933c3d539e15debcdd365028a2a 1211876 debputy_0.1.68.git.tar.xz
 75ee2dde7bcf08e1e32b9cd73404993702d8b2a772b6e538f4704291f85fc45a 18032 debputy_0.1.68_source.buildinfo
Files:
 fdf8e171f2cc89a7bc343e5c67685f59 2654 devel optional debputy_0.1.68.dsc
 77aba6fa6c80923fb7d4bbd1170eb00e 697284 devel optional debputy_0.1.68.tar.xz
 105f1f017a8602aecfd6adf84d4fdf25 1211876 devel optional debputy_0.1.68.git.tar.xz
 5a2edd0cd73c0c7e6eae47bc3c4d0ebe 18032 devel optional debputy_0.1.68_source.buildinfo
Git-Tag-Info: tag=a3247e7e874617feca02bceacd16d5f13344ea61 fp=f5e7199aef5e5c67e555873f740d68888365d289
Git-Tag-Tagger: Niels Thykier <niels@thykier.net>

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

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmh15rUACgkQYG0ITkaD
wHkF4Q/+M28kxQOcA9lonB2ALCziLCJt/Jj10ocGVLyflBHbF3W80MNarX40TjVN
PG5i/2bm4rs/z3bA1O/TALb6GOJrla79kyly/g/0swZ2G95p6e36nBnQChPd0Y7o
8RSeQ5lwbjx3So0DMzFfBK2x+9iJ0zF3Ewe/5x034wLoHdPK0EZVwGJOTvBo8HRj
yd5Qq8zQ4N/zOG4w9ISxYe15Fe4AGZCglvtLzDOlqEgJQmxwhvKa78Z4DRE1M47F
mcA84Q3zRULjeTM+N4obgZtdFPmTK/gsSl75vi3unfx0Kxcdwy7GtKy+9TUAVJ9d
CSZ3gLY5siDmuJdHinWs0hXnYUXWnNiKbw8DGa+FrljHO4nwc91JbcSjdtB/StoL
KSdZdZuG2IW3GSWv1eZ8RY4FmLulCTOqEGT6EM7kVkelVJloyx4h2PgOQJJGM7Bd
tZMXIlD6PNQRGmCT+fzabMYWRHXzVzn6AvtNXxDNdzhozHH5mJ1OkTg3EjGUwwoz
dnmSgsrhODXY4ym8JEc7H4Qz9O2Gny5rfzFpSSGYQ4zOQ33UsUD/csZk3Yr3/v2e
6XZ83VBA8ndQYeE3jjdidVrmEay/7eGZ2VYHSrSz0Y1aWlpGye1kFFrme00GKglU
QAtfYf7+V0ko3EGc9C08FOVilgFw0KpT+CEyTDljNijAVwPgP4I=
=7pop
-----END PGP SIGNATURE-----

Attachment: pgpoqoTkM71Fr.pgp
Description: PGP signature


Reply to: