Package: git-buildpackage
Version: 0.4.33
Severity: important
For example, upstream tree looks as follows,
A****B****C****D*****(tag v1.2)****E*****F
now, the debian uses the v1.2 as release point and doesn't follow the
development branch so,
/---A'---A"---(tag v.1.2-1)
A****B****C****D*****(tag v1.2)****E*****F
Now, I tag master as the upstream and deb. as the debian branch. This
works, but when git-buildpackage builds the tarball, it creates the
orig from the (F) or HEAD of the upstream branch and then applies
patches to the v.1.2-1. Instead, it should have used the base v1.2
tag, the base of the current checkout in the deb branch, as the source
of the orig.tar.gz.
- Adam
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (900, 'unstable'), (100, 'testing'), (5, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages git-buildpackage depends on:
ii devscripts 2.10.28 scripts to make the life of a Debi
ii git-core 1:1.5.6-1 fast, scalable, distributed revisi
ii python 2.5.2-1 An interactive high-level object-o
ii python-dateutil 1.4-1 powerful extensions to the standar
ii python-support 0.8.1 automated rebuilding support for P
git-buildpackage recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
