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

Bug#1029645: marked as done (ITP: debputy -- Manifest style debian package builder)

Your message dated Tue, 06 Jun 2023 18:00:10 +0000
with message-id <E1q6ayY-00AIdG-Il@fasolo.debian.org>
and subject line Bug#1029645: fixed in debputy 0.1.1
has caused the Debian Bug report #1029645,
regarding ITP: debputy -- Manifest style debian package builder
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1029645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029645
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Niels Thykier <niels@thykier.net>
X-Debbugs-Cc: debian-devel@lists.debian.org, niels@thykier.net

* Package name    : debputy
  Version         : 0.1.1
  Upstream Contact: Niels Thykier <niels@thykier.net>
* URL             : https://salsa.debian.org/debian/debputy/
* License         : GPL-2+
  Programming Lang: Python
  Description     : Manifest style debian package builder


Binary package being dh-debputy:
  Package builder that provides a declarative manifest for building
  debian packages.

  This version integrates with the debhelper sequencer dh and will
  replace several of debhelper's tools that are covered by debputy.

  The debputy package builder aims to reduce cognitive load for the
  packager and provide better introspection to better support to
  packagers, linters and the Debian janitor.
The early versions will integrate into the debhelper sequencer dh and will replace several of debhelper's tools that are covered by debputy. However, the goal is that debputy will be a standalone tool capable of packaging work from start to end.
In the early phase, I plan to keep debputy in experimental to allow for more aggressive prototyping. 

Rationale:
==========
My work on debputy is aimed at exploring an alternative packaging format that focuses on a single manifest (think Kubernetes helm charts or docker compose files). A key goal is introspection and, for errors, a clear link to the part of the configuration that was involved or triggered the error. 


Maintenance:
============
I am looking for people, who are interested in exploring this area with me and are: 

  1) Interested in trying the prototype, or/and
  2) Interested in helping me design the manifest format, or/and
  3) Interested in helping me develop the tool, or/and
  4) Interested in integrating with the tool.
     - Whether third-party plug-in (a la dh add-ons) or linters/fixers
As some concrete suggestions for what a contributor might be helping me with. The list is not exhaustive and you are welcome to help regardless of whether your interest is mentioned above. :) 

Trying out debputy:
===================
There is a getting started guide at https://salsa.debian.org/debian/debputy/-/blob/main/GETTING-STARTED-WITH-dh-debputy.md. 

If you do not use any overrides/hook targets, it is question of running:

 # (Remove --no-act to actually perform the change)
 $ debputy migrate-from-dh --no-act
And then add `dh-sequence-zz-debputy` to Build-Depends (the `zz-` is a hack for ordering debputy after other addons). 

Key features:
-------------
Some high lighted features in debputy that are currently not available in other Debian packaging tools that might be interesting for you :) 

 1) debputy supports setting static ownerships inside the debs without
    relying on fakeroot.  This means that packages never need fakeroot
    for the Debian packaging side (i.e., you should always be able to
    use `Rules-Requires-Root: no` as long as the upstream build system
    behaves).

    This feature is mentioned in the GETTING-STARTED-WITH-dh-debputy.md
    document, so you can see how to use it / try it out.

 2) If a binary package does not have a Multi-Arch field, debputy will
    automatically deduce if it is safe to set "Multi-Arch" to "same".
    The mechanics are based on rules by Helmut Grohne, who proposed this
    feature on IRC.  In the rare cases, that debputy is wrong here,
    you can explicitly set "Multi-Arch: no"
On the flip side, there are tons of features *not* supported by debputy at the moment. 

Thanks,
~Niels

--- End Message ---
--- Begin Message --- 
Source: debputy
Source-Version: 0.1.1
Done: Niels Thykier <niels@thykier.net>

We believe that the bug you reported is fixed in the latest version of
debputy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1029645@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Niels Thykier <niels@thykier.net> (supplier of updated debputy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Sun, 05 Feb 2023 18:27:25 +0000
Source: debputy
Binary: dh-debputy
Architecture: source all
Version: 0.1.1
Distribution: experimental
Urgency: medium
Maintainer: Debhelper Maintainers <debhelper@packages.debian.org>
Changed-By: Niels Thykier <niels@thykier.net>
Description:
 dh-debputy - Manifest style debian package builder (debhelper integration)
Closes: 1029645
Changes:
 debputy (0.1.1) experimental; urgency=medium
 .
   * Initial release.  (Closes: #1029645)
Checksums-Sha1:
 9c518a87e02ad6b39a33033279599462034822ba 1734 debputy_0.1.1.dsc
 78f7ff5344ff3d1ba791c07af4d5f6ad7999f72f 3282740 debputy_0.1.1.tar.xz
 4a576ae32061b290cce73e1a74832e793a7b3eb1 6658 debputy_0.1.1_amd64.buildinfo
 afb6b8937a3602a57b459df7a2282c6668b3c1cf 74712 dh-debputy_0.1.1_all.deb
Checksums-Sha256:
 fa49d59e9580f3d16e81e43e7d10176f72f8bcac52d398914ac65228a4b4e445 1734 debputy_0.1.1.dsc
 c1262b9dd0bd9fac2c753b46773111da3fa65ef230a64a2d244bcd6bfd7fd612 3282740 debputy_0.1.1.tar.xz
 51375d1018bf1dab937dc20b50cc0de3d31374626b6978ddebd7ec94a96705a6 6658 debputy_0.1.1_amd64.buildinfo
 bb58bdaaecc014ba49477d09ca848c96a6ac7be42ffed9900a66d7d1a2a38ba2 74712 dh-debputy_0.1.1_all.deb
Files:
 0b34197ad61e234dc2f5983271adec19 1734 devel optional debputy_0.1.1.dsc
 afd93d81872a25a8574890eeabf6e8ef 3282740 devel optional debputy_0.1.1.tar.xz
 bebd4460970cf118967b6cc7974b493a 6658 devel optional debputy_0.1.1_amd64.buildinfo
 f2467fe4c5825f113bf29f740632d2fa 74712 devel optional dh-debputy_0.1.1_all.deb

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

iQJGBAEBCgAwFiEE8f9dDX4ALfD+VfsMplt42+Z8eqwFAmPf9UgSHG5pZWxzQHRo
eWtpZXIubmV0AAoJEKZbeNvmfHqsQHMP/j6BPP1krPeh4RszNoq2x9exCIXV4gnn
cnGjmjETtxEX87s4hPBGk5J1ulgHGFflsXiVwrh74/dxL1XW+sm1UXlSJVHbTWqx
Bj9mPcw6b7Hde0opAOOvEOlum2scXBUB0mF32a1toJS/YDEhRT/x+aTFwQ+tO+HV
a4hCACZMqh/XC6sjw90rfzG3tEvKE0tg7CSpFMfazg+CZDOmEoZMxID1U1TDD1ma
mrI/mRvoz3iLfqCwuXqeDqcpVSssrkAkTpjwSkS7X2UzHIgRdAQziDl+ccR4Mevn
q4He9ozhl9Eb6LKnJo03+ZtpH9OqWagrxrrsAiHpTK41Nk4JGeO3FhQAR/PkBDYI
o0H2e18C3xL59GUivHcyiCpCd7CK3IBEYWfR5SR4TziDZPul6vi5XyHwp25JvRCA
e8AqBzM5mcg5bu6pp2jBvhzi/ceEPgDM3eGvDaeGu8kl2GV0CnD1tEeArf8xKHaM
LyMonTtpeIx/uH/9jobyTZANYNzIM0vJTup30Z96iJdGPSAf1lEwCTb6LICyUkyW
srOyeolGgtoJhhLwO9i6ao+WjZYe4+dwAMXVit+YPJ6ooYY2L8DnG88V6PrCRZif
fgQHPYiOGOtrXnM+mtUy5zPHnnME021o1uh80diBB5RM2yuU+gsUizLo0F9EJx6N
xakmvbBpByMt
=/pmN
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: