Please backport git-buildpackage 0.4.33 from Intrepid to Hardy

[LaserJock]

The git-buildpackage version in Intrepid has some nice new features (pristine-tar support in import-orig is one I want) and lots of fixes. I can verify that it builds, installs, and runs (at least for my needs) fine.

[Brian Fallik (bfallik)]

I agree.

I was unable to get git-import-orig to work at all from Hardy. The traceback when run on a xxx.orig.tar.gz file was:
Traceback (most recent call last):
  File "/usr/bin/git-import-orig", line 211, in <module>
    sys.exit(main(sys.argv))
  File "/usr/bin/git-import-orig", line 181, in main
    import_source_tree(repo, orig_dir, version, options.filter, verbose=not is_empty)
  File "/usr/bin/git-import-orig", line 56, in import_source_tree
    old = set(repo.index_files())
  File "/var/lib/python-support/python2.5/gbp/git_utils.py", line 84, in index_files
    files = [ file for file in out[0].split('\0') if file ]
IndexError: list index out of range

My workaround was to use a very big hammer. I created an Intrepid chroot and used get-import-orig from there.

[Michael Casadevall (mcasadevall)]

As this appears to require rather large changes to backport, I'm marking this Incomplete.

[Brian Fallik (bfallik)]

Michael,

Can you clarify the "rather large changes to backport?"

Also, I don't see the value in setting this bug to Incomplete. Are you soliciting more information from us? https://wiki.ubuntu.com/Bugs/Status suggests Won't Fix is more appropriate if this bug is to be ignored for Hardy. I'm setting it back to New for now and the Bug Contact (who is that, anyway?) can mark it as Won't Fix.

Thanks,
brian

[Michael Casadevall (mcasadevall)]

Incomplete on backports means that the package need source level porting or requires build-deps not available in backports yet.

Since we're currently experiencing a massive backlog of backports, I'm trying to simply get the ones through that will not require changes, and then come back to the ones that will. Your backport request is a valid one, but it will require some work before it can be released to hardy-backports. If your willing to do the work to make git-buildpackage build and be usable on Hardy, I'll be willing to test the patch and confirm it.

[Michael Casadevall (mcasadevall)]

As a futher clarificaiton, the specific issue is the resulting package builds, but is not installable:

 git-buildpackage depends on devscripts (>= 2.10.26); however:
  Version of devscripts on system is 2.10.11ubuntu5.

devscripts needs to be backported (unlikely to happen), or git-buildpackage will need to be tweaked, and confirmed to work right with the older devscripts.

[Brian Fallik (bfallik)]

Michael,

Thanks for the clarification. I wasn't away that backport requests used the Status field differently. I wonder if it makes sense to note this in the wiki somewhere?

I understand the increased complexity of source level porting. Unfortunately I don't think I'll have any cycles to work on this, esp. considering the Intrepid chroot workaround I mentioned earlier.

Feel free to switch this bug back to Incomplete if that makes the most sense.

Thanks,
brian

[LaserJock (laserjock)]

Do we still need this bug?

[Brian Fallik (bfallik)]

I do not.

On Mon, Sep 14, 2009 at 9:19 PM, Jordan Mantha
<email address hidden> wrote:
> Do we still need this bug?
>
> --
> Please backport git-buildpackage 0.4.33 from Intrepid to Hardy
> https://bugs.launchpad.net/bugs/246493
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Evan Broder (broder)]

It looks like this bug requests a backport from Ubuntu 8.10 (Intrepid
Ibex). However, as Intrepid is no longer supported, such a backport is
no longer possible.

This bug is being set to "Won't Fix". If you would still like to move
forward with this backport request, please re-open the bug and adjust
it to request a backport from a current release.

(This change is being made by an automated bot run by Evan Broder, who
is now subscribed to the bug; if you think the change was made in
error, please feel free to re-open the bug)