So, fixed in Natty (and Maverick too).
Closing.
** Changed in: git-buildpackage (Ubuntu)
Status: Fix Committed => Fix Released
--
heuristic to determine compression-format from HEAD of upstream branch can lead
to incorrect result when upstream is not merged to master
https://bugs.launchp
** Tags added: patch
--
heuristic to determine compression-format from HEAD of upstream branch can lead
to incorrect result when upstream is not merged to master
https://bugs.launchpad.net/bugs/615212
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: git-buildpackage (Ubuntu)
Status: New => Fix Committed
--
heuristic to determine compression-format from HEAD of upstream branch can lead
to incorrect result when upstream is not merged to master
https://bugs.launchpad.net/bugs/615212
You received this bug notification beca
** Summary changed:
- gbp misses bz2 support
+ heuristic to determine compression-format from HEAD of upstream branch can
lead to incorrect result when upstream is not merged to master
** Attachment removed: "graph.txt"
https://bugs.launchpad.net/ubuntu/+source/git-buildpackage/+bug/615212/
I just noticed the issue after sending the last mail. The heuristic is
to look at pristine-tar not upstream (basically since pristine-tar only
supports a single branch) so we have to look at the commit messages.
--
heuristic to determine compression-format from HEAD of upstream branch can lead
t
yes, you are absolutely right. compression-format ought to be
determined from pristine-tar branch. Currently, gbp always look at HEAD
of that branch. What I meant to say is how to determine where in
pristine-tar gbp should look. commit messages is another way, I guess.
--
heuristic to determi
On Tue, Sep 14, 2010 at 10:41:25AM +0200, Guido Günther wrote:
> Attached (very lightly tested patch) fixes the issue for me.
The fix for this is shipped in 0.5.9.
Cheers,
-- Guido
--
heuristic to determine compression-format from HEAD of upstream branch can lead
to incorrect result when upstre
On Tue, Sep 14, 2010 at 10:41:25AM +0200, Guido Günther wrote:
> Attached (very lightly tested patch) fixes the issue for me.
The fix for this is shipped in 0.5.9.
Cheers,
-- Guido
--
heuristic to determine compression-format from HEAD of upstream branch can lead
to incorrect result when upstr
Attached (very lightly tested patch) fixes the issue for me.
-- Guido
** Patch added: "0001-Improve-compression-format-detection.patch"
https://bugs.launchpad.net/bugs/615212/+attachment/1582015/+files/0001-Improve-compression-format-detection.patch
--
heuristic to determine compression-fo