Bug#411206: git-buildpackage: Please allow use of an external .orig.tar.gz
Package: git-buildpackage Version: 0.2.25 Severity: wishlist Hello, I'd like to make use of pre-existing .orig.tar.gz's. I have a large of these lying around for more stable parts of xorg, and I'd like to just have git-buildpackage use them rather than import them in to the repository. I think this is the last issue that's keeping me from using git-buildpackage for managing the xorg packages for Debian. Thank you and keep up the great work! - David Nusinow -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) 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-dirs1.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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#411206: git-buildpackage: Please allow use of an external .orig.tar.gz
Hi David, On Fri, Feb 16, 2007 at 10:24:54PM -0500, David Nusinow wrote: >I'd like to make use of pre-existing .orig.tar.gz's. I have a large > of these lying around for more stable parts of xorg, and I'd like to just > have git-buildpackage use them rather than import them in to the > repository. I think this is the last issue that's keeping me from using So you only want to maintain debian/ in the git-repository? This is certainly doable but git is so space efficient (git-repack -a, git-prune-packed) that you won't gain much by this - are there other reasons for keeping the upstream sources out of the archive? Cheers, -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#411206: git-buildpackage: Please allow use of an external .orig.tar.gz
Guido Guenther wrote: > Hi David, > On Fri, Feb 16, 2007 at 10:24:54PM -0500, David Nusinow wrote: > >>I'd like to make use of pre-existing .orig.tar.gz's. I have a large >> of these lying around for more stable parts of xorg, and I'd like to just >> have git-buildpackage use them rather than import them in to the >> repository. I think this is the last issue that's keeping me from using >> > So you only want to maintain debian/ in the git-repository? This is > certainly doable but git is so space efficient (git-repack -a, > git-prune-packed) that you won't gain much by this - are there other > reasons for keeping the upstream sources out of the archive? > Cheers, > I guess David wanted to try git-buildpackage for X packages and I just had a look at this too. For clarification, Xorg upstream also uses git, so we have the upstream code in a branch (upstream-unstable or upstream-experimental) and upstream+debianpackaging in another branch (debian-unstable or debian-experimental). And we would basically build packages for unstable using: git-buildpackage --git-upstream-branch=upstream-unstable --git-debian-branch=debian-unstable However, being able to use the actual tarball that upstream ships might be good, instead of recreating it from our upstream-unstable branch. So I second David's request for something like a --git-orig-targz foo.tar.gz (or bz2) option. In the end, thinking about all this, I am not sure git-buildpackage is really useful for X packages since upstream uses git. Why does it buy us? Avoiding -i.git? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#411206: git-buildpackage: Please allow use of an external .orig.tar.gz
Hi Brice, thanks for the clarification. On Tue, May 22, 2007 at 10:13:06PM +0200, Brice Goglin wrote: > I guess David wanted to try git-buildpackage for X packages and I just > had a look at this too. For clarification, Xorg upstream also uses git, > so we have the upstream code in a branch (upstream-unstable or > upstream-experimental) and upstream+debianpackaging in another branch > (debian-unstable or debian-experimental). And we would basically build > packages for unstable using: > git-buildpackage --git-upstream-branch=upstream-unstable > --git-debian-branch=debian-unstable or specify this in gbp.conf > However, being able to use the actual tarball that upstream ships might > be good, instead of recreating it from our upstream-unstable branch. So > I second David's request for something like a --git-orig-targz > foo.tar.gz (or bz2) option. Well, git-buildpackage doesn't create a orig.tar.gz at all, if it finds one. Do you want to be able to give a different name that is then copied over to .orig.tar.gz? > In the end, thinking about all this, I am not sure git-buildpackage is > really useful for X packages since upstream uses git. Why does it buy > us? Avoiding -i.git? * making sure you have everything committed nicely * automatic tags (to your own gusto) after a successful build * automatic push outs to altioth after a successful build+tag * automatic signed tags (via gbp.conf) This might not be of any actual use for xorg packaging though. Cheers, -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
