Package: git-buildpackage Version: 0.2.24 Severity: wishlist Some upstreams will eventually release "a.b.c-d" versions, e.g., on patchlevel. This can be terribly confusing with the simple way git-buildpackage is dealing with tags right now.
Please use different format strings to tag upstream and debian releases, as done by cvs-buildpackage. Actually, it would be best to just make tag format strings configurable for all branches using a regexp=format notation, or somesuch. That way you can address nmu, upstream, releases, backports, etc. Suggested defaults are: upstream/<foo> debian/<foo> (yes, that does mean placing the tags on subdirs. cvs-buildpackage placed these things on different namespaces for a reason!). -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.38-debian13+bluesmoke+lm85 Locale: LANG=pt_BR.ISO-8859-1, LC_CTYPE=pt_BR.ISO-8859-1 (charmap=ISO-8859-1) Versions of packages git-buildpackage depends on: ii devscripts 2.9.27 Scripts to make the life of a Debi ii git-core 1:1.4.4.4-1 content addressable filesystem ii git-load-dirs 1.0.35 Import upstream archives into git ii python 2.4.4-2 An interactive high-level object-o ii python-support 0.5.6 automated rebuilding support for p git-buildpackage recommends no packages. -- no debconf information -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
