Skip to content
Release debputy/0.1.3

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

Format: 1.8
Date: Sun, 23 Jul 2023 07:52:46 +0000
Source: debputy
Architecture: source
Version: 0.1.3
Distribution: experimental
Urgency: medium
Maintainer: Debhelper Maintainers <debhelper@packages.debian.org>
Changed-By: Niels Thykier <niels@thykier.net>
Changes:
 debputy (0.1.3) experimental; urgency=medium
 .
   * debputy.pm: Breaking change: The debputy dh sequence now removes the
     following debhelper tools from the sequence:
     - dh_lintian
     - dh_bugfiles
     - dh_compress (note: hardlinks are not supported correctly)
   * Create a basic plugin API infrastructure and move some of the
     debputy into a plugin. Plugins can currently register packager
     provided files (`d/pkg.foo -> usr/.../pkg[.conf]`) and detection
     (and generation) of maintscript snippets, substvars and triggers.
     However, plugins cannot alter the contents of the data.tar.
     Additionally, the plugins are not loaded deterministically during
     builds (unclean chroot can load too many plugins), so they are not
     ready for prime time yet.
   * Fixed a bug in debputy's handling of icon-cache generation
     (dh_icons).
   * Detect kernel modules under /usr in addition to /lib.
   * debputy.py: When migrating from dh, detect use of `=>` in
     debhelper config files and report it as unsupported. The migrator
     would not generate the correct code for these lines. Currently,
     none of the debhelper tools where you can use `=>` would be migrated,
     so this is just future proofing.
   * debputy.py: Provide a `plugin` subcommand to interact with the
     plugins.  Currently, it can only list plugins and a bit of the
     content they provide.
   * all frontends: Show colorized error and warning messages similar to
     debhelper.
   * all frontends: Provide a `--version` that prints the version of
     debputy.
   * debputy.py: Detect `/usr/local` paths and abort as they are unhandled.
     Note that `dh_usrlocal` would normally be run and clean up these
     directories, so this is only an issue if you bypass `dh_usrlocal` or
     ask debputy to create content in `/usr/local`.
Checksums-Sha1:
 c6809cc5a03f0cc9a61c93350410bc5192670c73 1758 debputy_0.1.3.dsc
 21241030c5ffa083494084e54efe8fd3432ef857 115852 debputy_0.1.3.tar.xz
 beeb532bb380cceefc5d4ae06bf99ebcde542023 6657 debputy_0.1.3_source.buildinfo
Checksums-Sha256:
 e2d3fa522ea63e04b3d27ea187b01637fd978a134942cc3b256742e88ceebe7d 1758 debputy_0.1.3.dsc
 13692b3e7065c01a1ea4e927b72a51072d2054610b36b9b921672806c5edd0f1 115852 debputy_0.1.3.tar.xz
 825fa455cba2430ffa254ff722ed026ae8baaca8ffb57a0580f91af05f6fa5b3 6657 debputy_0.1.3_source.buildinfo
Files:
 5de0ae538a2e43396a3a45ca2df5cbd2 1758 devel optional debputy_0.1.3.dsc
 2cde317c70d0c5f596c0c8d109185126 115852 devel optional debputy_0.1.3.tar.xz
 b533069b6ffaf13f2c75e13a7e2ac638 6657 devel optional debputy_0.1.3_source.buildinfo