-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 10 Aug 2025 06:55:29 +0000
Source: debputy
Architecture: source
Version: 0.1.71
Distribution: unstable
Urgency: medium
Maintainer: Debputy Maintainers <debputy@packages.debian.org>
Changed-By: Niels Thykier <niels@thykier.net>
Changes:
debputy (0.1.71) unstable; urgency=medium
.
* Upload to unstable.
.
debputy (0.1.70) experimental; urgency=medium
.
* LSP/Lint+Reformat:
- More strict deb822 checks before activating features
.
* LSP/Lint:
- Initial support for version 5 `debian/watch` files
- The `Priority` field now defaults to `optional`
.
* LSP/Reformat:
- Fix a limitation that prevented some automatic
rewrites of fields into their canonical form.
It was previously only observed with
`XC-Package-Type` but it is more apparent with
with the new `debian/watch` support.
.
* debputy reformat: Accept `--write-style` option
* debputy lsp server: Work around KDE#506664 to reduce
the noise in LSP output.
.
debputy (0.1.69) experimental; urgency=medium
.
* LSP/Reformat:
- Fix bug that could eat field comments when the
field was reformatted.
Thanks to Chris Hofstaedtler <zeha@debian.org>
(Closes: debputy#140)
- Fix crash bug caused by overlapping edits. The
bug that caused overlapping edits was introduced
in 0.1.68.
.
* Fix LSP feature check for `spellchecking`. It checked
the wrong import was present and therefore the answer
did not reflect reality.
* Disable `dwz` to match `debhelper`. The migration of
`arch:any` packages now assumes compat 14 semantics
for this reason.
.
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:
b6dddcf4b9f3955cef67b97f9dc466fc42b36c81 2654 debputy_0.1.71.dsc
7e958c601c0e0b92d05504856cbd2e5e9c14d01d 719708 debputy_0.1.71.tar.xz
2e05720444f32f5f9ce8637ecee3759bc2475a1a 1253764 debputy_0.1.71.git.tar.xz
48520df03f0b3915053d5daccbfe540e8c9069fb 18050 debputy_0.1.71_source.buildinfo
Checksums-Sha256:
7660a1fd5311d25025e983be6065b359b559d91ee0b78a4e1bb2f4c9b2b41612 2654 debputy_0.1.71.dsc
097b3b12ff8690660815b27ca226b6b7a1bd88beb2c4f29ab95823a305c93d72 719708 debputy_0.1.71.tar.xz
9a41e821afa11d2fe0575b1a032f2489bf4f74b383be30bf47356a5e7d9ed623 1253764 debputy_0.1.71.git.tar.xz
6b98dcc14d4e39819f6e1dd984bd90b4c65169b588ab49fc2a19ac30c4d597eb 18050 debputy_0.1.71_source.buildinfo
Files:
d1a57eaf8d91a6de1488dfbf4b4cf068 2654 devel optional debputy_0.1.71.dsc
63a80ce947f1d8fd06dea5bc71470dd0 719708 devel optional debputy_0.1.71.tar.xz
656b7d844cfef12d62b749c56979358c 1253764 devel optional debputy_0.1.71.git.tar.xz
4bbb806530ab2f17a1a04ad09fa60896 18050 devel optional debputy_0.1.71_source.buildinfo
Git-Tag-Info: tag=f432069707092da150451ea2b68aee382da04741 fp=f5e7199aef5e5c67e555873f740d68888365d289
Git-Tag-Tagger: Niels Thykier <niels@thykier.net>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmiYazIACgkQYG0ITkaD
wHltSRAAjBpbKZaiARROJQxCdNDVgwGmRELfy00E6DyRZh+73S2nt1RtAy8nAsk3
Fhk9nLg6NjDN4y1Z4kYkOq7RFiRkXR+AL6Bev/NoKXLFHgEssAl4wRd32wLStWLE
Ts0wGkE5jvAN5HIEK65BpkRI7UgqnuZZHPz7DFB8yzBACQZKweqwoUeEgbuCpljr
jRQ84hx+t/RrVDODC+UxaXoRxiinPilzBPaXxvB5CI3CjxcwvrE5wECYsleyvVwh
UbUkDvxyUYo/EbVS51pcONHMv6aNT3ws+nD/mq4/jwsH7CWEzO9uSeJSmOen8mpH
DzQCZhgM3Oyb0kDcShz8tlon72aeCZ4Ua4yWFS9ppb9QlufudiG66xtK6umI78Pp
URyp/3IeBWaeZAWpYASKFVGCg73FgPKgv7Flaf7DbaaOQdCGYcz5bWO8ghNYWQTM
xCA19NwDILLBzlvsZp54aEVvpD5B7TWosNp0PL65puRKtXQd8ZusxOG7kboxJFWc
fVcZ8uxE6mTQ1XIBrL4ZOLG3z7f4bWvj2Q/UpmwSiTLWFYt6gw2Fv8+VCUFzXKvj
So6JawsHg860qHjLHlvrpO8OfIsYNz1qznib6i0iaUfAggT8xIgu9EDRH3bV+a2c
uvqajndbAxGIT+7mE4D+IlQeUEt2rMXxxmvuRDfTE6RLdOuO2dU=
=qyIJ
-----END PGP SIGNATURE-----
