Accepted gitpkg 0.13 (source all)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sun, 15 Nov 2009 06:04:26 +1030
Source: gitpkg
Binary: gitpkg
Architecture: source all
Version: 0.13
Distribution: unstable
Urgency: low
Maintainer: Ron Lee <ron@debian.org>
Changed-By: Ron Lee <ron@debian.org>
Description:
gitpkg - tools for maintaining Debian packages with git
Closes: 544210 554519
Changes:
gitpkg (0.13) unstable; urgency=low
.
* Lucky for some.
* Don't hardcode .gitignore removal here, people should use gitattributes(5)
for that sort of thing instead.
* Move all configuration options to use git-config(1). There is no sense in
reinventing a(nother) config file hierarchy and format ourselves. Existing
config should continue working for now, and gitpkg itself will hint to you
about how to migrate.
* Pass the contents of gitpkg.dpkg-source options verbatim to dpkg-source.
Closes: #554519
* Support being invoked from a subdir of the repo to export.
* Pander to "format 3.0" which can't build orig tarballs itself anymore and
gags on the dpkg-source options that specify how the source is presented.
* Drop the .orig suffix from paths in the orig tarballs.
* Make the hardcoded rule to call the debian/rules clean target prior to
building the package more flexible. Not all packages need this, and some
may have some other special rule they'd rather call instead.
* Rehash the user hook handling entirely (though any existing hooks should
still work for now too). We now provide support for multiple distinct
hooks that are run at key times and places during the build process, and
a more complete set of environment variables are guaranteed to be available
to them. Closes: #544210
* Add /usr/share/gitpkg/hooks initially populated with simple off the shelf
support for cowpoke, dpkg-buildpackage, and pristine-tar.
* Now with 30% less typing! That's right, you only need to pass the second
treeish if you actually do need gitpkg to export a new orig tarball.
This isn't really a "new feature", but it's now safe to formalise that it
isn't just an accident. The second tag was always ignored previously if
a suitable orig tarball already existed, but now we give you more choice
over what should actually happen in that case, and make it explicit that
you don't need to pass the second treeish if you already have an orig.
Checksums-Sha1:
90313e0796630f47a7fe89e53eddbd0491532488 783 gitpkg_0.13.dsc
e23a73a3788fb5c9849280bb9a3df4443c9d8597 24336 gitpkg_0.13.tar.gz
cbe930a6a1a2adda057af11c4be10ce08b738e7d 27726 gitpkg_0.13_all.deb
Checksums-Sha256:
2a2608c79c1371deba3167551c9b1ffde2a0f4032b9c99561e041403113eb8bc 783 gitpkg_0.13.dsc
64fef7f1503caf7aebd8db01ffe7cdeb7cc9505438a7d00d05c245bd9e2ac01a 24336 gitpkg_0.13.tar.gz
e95b652b98f81ea3f33c98335aa1dd346c1e5a173529083fa66c47fa90149c7d 27726 gitpkg_0.13_all.deb
Files:
20fc54ff3ae4fffc3b6cc954a92cf251 783 vcs optional gitpkg_0.13.dsc
d6d86835c9df2ed852f60ddc13088682 24336 vcs optional gitpkg_0.13.tar.gz
fd53449a0d0d94d1ba8f8a3502c1b2c6 27726 vcs optional gitpkg_0.13_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFLEQK2p4BCHGgCHOQRAiMzAJ0bXNGAQotjTlFdf5xOVMYYHWLgsgCdERmq
j7MCTnFypXsfX+kBGjfDnxo=
=UG0V
-----END PGP SIGNATURE-----
Accepted:
gitpkg_0.13.dsc
to main/g/gitpkg/gitpkg_0.13.dsc
gitpkg_0.13.tar.gz
to main/g/gitpkg/gitpkg_0.13.tar.gz
gitpkg_0.13_all.deb
to main/g/gitpkg/gitpkg_0.13_all.deb
Reply to: