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

Bug#750576: marked as done (ITP: debdry -- Semi-assisted automatic Debian packaging)

Your message dated Fri, 05 Sep 2014 13:00:06 +0000
with message-id <E1XPt7W-0008FG-LV@franck.debian.org>
and subject line Bug#750576: fixed in debdry 0.1-1
has caused the Debian Bug report #750576,
regarding ITP: debdry -- Semi-assisted automatic Debian packaging
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.)


-- 
750576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750576
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Enrico Zini <enrico@debian.org>

* Package name    : debdry
  Version         : 0.1
  Upstream Author : Enrico Zini <enrico@enricozini.org>
* URL             : http://anonscm.debian.org/gitweb/?p=collab-maint/debdry.git
* License         : GPL3
  Programming Lang: Python 3
  Description     : Semi-assisted automatic Debian packaging

debdry is for debian/ directories what debhelper7 is for debian/rules.

It applies the Don't Repeat Yourself idea to packaging, attempting to reuse as
much as possible of upstream's metadata and standard packaging practices.

debdry runs an appropriate auto-debianisation tool for a given source
directory, then applies manual overrides from a debian.in directory.

 - - -

I'm generally fond of the DRY principle (http://c2.com/cgi/wiki?DontRepeatYourself)
but every time I package software for Debian I feel WET (Write
Everything Twice) instead.

Many upstream ecosystems have started including enough metadata in their
upstream packaging to significantly overlap with debian/. Think
short/long descriptions, upstream URLs, licenses, dependencies.

When the upstream packaging is well made, there is usually not much else
to add to a dh-make-equivalent initial boilerplate code, besides testing
and taking responsibility for it. Maintaining software in Debian should
be about testing and taking responsibility for it, not about retyping
things that upstream has already typed.

What if upstream got it wrong? It often happens. In that case, we can
patch their sources, and send them the patch. That way, instead of
having our own private work-arounds, we make the packaging better for
everyone, even those who do not use Debian.

The idea of debdry is to regenerate the debian/ directory every time a
new version of the software is packaged, using the dh-make-equivalent
for the given package type. It then takes manually maintained data from
the debian.in/ directory and uses it to complete the packaging.

At each new version there is a chance for the debianisation to be
updated: the Python team switches from dh_pysupport to dh_python2? Your
package will automatically follow (provided python-stdeb is updated
accordingly, but that is another story).

I like how with debhelper7 we are writing debian/rules files that only
describe how the package diverges from a standard. I want to do exactly
the same for the whole debian/ directory. Ideally, the debian.in/
directory used by debdry should only describe how the upstream packaging
diverges from a standard in a way that cannot be fixed by patching it.

I have no intention of having debdry replace hand-writing debian/
directories, nor have it handle all possible corner cases. I aim at it
being useful in the general case. I want to address the ordinary,
routine, boring work, and leave the rest as it is.

This is also a proof of concept for an idea. We can discuss it in more
detail here, or at DebConf.

In the meantime I'd like to use it for my packages, because frankly,
I'm bored of writing everything twice.

Ciao,

Enrico

--- End Message ---
--- Begin Message --- 
Source: debdry
Source-Version: 0.1-1

We believe that the bug you reported is fixed in the latest version of
debdry, 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 750576@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Enrico Zini <enrico@debian.org> (supplier of updated debdry 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: SHA256

Format: 1.8
Date: Sat, 30 Aug 2014 19:07:50 -0700
Source: debdry
Binary: python3-debdry
Architecture: source all
Version: 0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Enrico Zini <enrico@debian.org>
Changed-By: Enrico Zini <enrico@debian.org>
Description:
 python3-debdry - Semi-assisted automatic Debian packaging
Closes: 750576
Changes:
 debdry (0.1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #750576)
Checksums-Sha1:
 d02a0777643068b6338311b9fddaabe671c5cd39 1671 debdry_0.1-1.dsc
 270859c9643980b93db1505d2c361da3093f5a4a 24735 debdry_0.1.orig.tar.gz
 4bd1b166c75571102a733b201af488a44ef4a416 1540 debdry_0.1-1.debian.tar.xz
 3c0ff3fffe509f3c6771b5d5e306bc40d5a79ff5 9154 python3-debdry_0.1-1_all.deb
Checksums-Sha256:
 14988db1be383924b992e5fbffb37fc5de89dd2d65389cd6ee53646c58130c18 1671 debdry_0.1-1.dsc
 ffbd346242f31169cdb49146260bb3e52ba648eddf768539c1ab16d38c4e2489 24735 debdry_0.1.orig.tar.gz
 eb7fed1b37d9bb9cce104117aa6759bae5c1965365c200955ecea90c94206e10 1540 debdry_0.1-1.debian.tar.xz
 d9250f5ee401e362874e209e4f275e134e24dcbb3d5c34f8134d5a21c02dcb9c 9154 python3-debdry_0.1-1_all.deb
Files:
 fb0914f824720faad758f597546f856e 9154 devel optional python3-debdry_0.1-1_all.deb
 b2071cdbe103754e9ce48fc97774412f 1671 devel optional debdry_0.1-1.dsc
 f698f0499f61dd143f7bbbd060b09c25 24735 devel optional debdry_0.1.orig.tar.gz
 fa93ccd5c5068ff3337f4aa683369304 1540 devel optional debdry_0.1-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJUAoQxAAoJEAPWVoyDcnWp22sP/23NofbCM6KeINVBfFGMHmIm
SBXkTwOfTxbRkrQ8/1ppwIyu9YAnFuiuL+6izFpP2h+H0zIrfKPkf73X7BRzjyMN
pTNMfDqbhxBnoawAL7Swn7c1PYCayHdMASGIzbXDuFLO5jn7xnZata15A6VsCNIT
ZMcjV8qYA9r07fHNF83GW+yOWnBjp37Ot9X+6ClWPNGu0x8rtrHracmNwQ0EIHSz
HYEHYY8QEXNZaBCKjxA5fuR7CDz0YV+7qTfZtbCQHsQQd6VbIM2Uzy98srfRQ4bz
d41zRID5yBByieJSbb461XqLSGE94P/JcU+2rFpu8yHFiGXQGpRpPS9nn0mljg+3
rVSTJeXdRjAcjXhu5GnGEoIetmZ/qrCo16ZL0Rq9YNWESnN4z4AzB/V9NdMBDvYH
gp0jVtoukRv7h9xe+HFBSFgLosMzg41yTqyChH8JDStoM4YSRe6BJrEH/V2zihUM
TO3mpYvIUtOKGJV7BACK3vNyiLiW7R0MGOJovt1G3vjEa7xVa+GJsJoY+a9LwLLR
QYjaIqAEZbxxMQRA8OdTw+oiGco3CNftTqW8DN/CFjVjVljPOhdmYvCtjmRX5WGF
3Zvt7T7Gapo2CqMbJvoea+A9hTOPzqAM24Cgy0ELgvcrFrgfBZoJB6Skq9j4L88+
g6f3D8ROE2iG6tCrbOaJ
=vW96
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: