Your message dated Wed, 29 Sep 2010 20:45:15 +0200
with message-id <[email protected]>
and subject line Re: Bug#598530: /usr/bin/git-buildpackage: support
svn-buildpackage's mergeWithUpstream behavior whenever there is no upstream/
branch
has caused the Debian Bug report #598530,
regarding /usr/bin/git-buildpackage: support svn-buildpackage's
mergeWithUpstream behavior whenever there is no upstream/ branch
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 [email protected]
immediately.)
--
598530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598530
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-buildpackage
Version: 0.5.10
Severity: wishlist
File: /usr/bin/git-buildpackage
Primary reason:
I would like to co-maintain some packages, packaging of which is kept under SVN
with mergeWithUpstream flag. Sure thing I would like to use GIT and
git-buildpackage ;) Ideally I should be able to go with *.orig.tar.gz and
debian/ (under git), the same way as svn-buildpackage does.
Unfortunately it is not supported (or broken) as of now in gbp. In both
scenarios -- I have no upstream/ branch at all, or just empty upstream/ branch
-- target build directory lacks any upstream sources (and there is a
scream from dpkg-source I guess about deletion of all upstream files).
I have tried to google up either it was ever suggested or implemented,
but only found "is not supported", or statement that it works [1], which is,
unfortunately, not true (per described above).
[1] http://www.mail-archive.com/[email protected]/msg63336.html
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (901, 'unstable'), (900, 'testing'), (300, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, 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.67 scripts to make the life of a Debi
ii git [git-core] 1:1.7.1-1.1 fast, scalable, distributed revisi
ii git-core 1:1.7.1-1.1 fast, scalable, distributed revisi
ii python 2.6.5-13 interactive high-level object-orie
ii python-dateutil 1.4.1-3 powerful extensions to the standar
ii python-support 1.0.9 automated rebuilding support for P
Versions of packages git-buildpackage recommends:
ii cowbuilder 0.62 pbuilder running on cowdancer
ii pristine-tar 1.03 regenerate pristine tarballs
Versions of packages git-buildpackage suggests:
ii git-load-dirs 1.1.8 Import upstream archives into git
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Sep 29, 2010 at 02:33:44PM -0400, Yaroslav Halchenko wrote:
> Package: git-buildpackage
> Version: 0.5.10
> Severity: wishlist
> File: /usr/bin/git-buildpackage
>
>
> Primary reason:
>
> I would like to co-maintain some packages, packaging of which is kept under
> SVN
> with mergeWithUpstream flag. Sure thing I would like to use GIT and
> git-buildpackage ;) Ideally I should be able to go with *.orig.tar.gz and
> debian/ (under git), the same way as svn-buildpackage does.
>
> Unfortunately it is not supported (or broken) as of now in gbp. In both
> scenarios -- I have no upstream/ branch at all, or just empty upstream/ branch
> -- target build directory lacks any upstream sources (and there is a
> scream from dpkg-source I guess about deletion of all upstream files).
>
> I have tried to google up either it was ever suggested or implemented,
> but only found "is not supported", or statement that it works [1], which is,
> unfortunately, not true (per described above).
>
> [1] http://www.mail-archive.com/[email protected]/msg63336.html
It is supported quiet o.k (if I understand your request correctly) and I
documented recently how I'm using it:
http://honk.sigxcpu.org/con/Using_git_svn_and_git_buildpackage_to_build_packages_maintained_in_Subversion.html
Let me know if anything is missng.
Cheers,
-- Guido
--- End Message ---
