#748478 git-import-orig: Honour tarball-dir for orig symlink

Package:
git-buildpackage
Source:
git-buildpackage
Submitter:
Maximiliano Curia
Date:
2026-09-10 06:59:02 UTC
Severity:
wishlist
Tags:
#748478#5
Date:
2014-05-17 16:07:59 UTC
From:
To:
Package: git-buildpackage
Version: 0.6.13
Severity: normal
Tags: patch

Hi,

The current behavior in import-orig is to create an orig symlink in ../ even if
the user configures tarball-dir. The attached patch adds the argument
--tarball-dir so the user can override the symlink location.

Please consider applying this patch.

I added the option to import_group, if you would prefer for it to be in a
different group, please let me know.

Thanks
#748478#10
Date:
2014-05-17 20:18:46 UTC
From:
To:
Hi,

Thanks for your patch but why would I want to create the symlink in
tarball-dir. gbp buildpackage will then create the symlink in ../
anyways so dpkg-source etc see the correct tarball.
  -- Guido
#748478#17
Date:
2014-05-17 21:47:51 UTC
From:
To:
¡Hola Guido!

El 2014-05-17 a las 22:18 +0200, Guido Günther escribió:
in the tarball_dir, and symlinks that into the export_dir (not in '..')

If you are checking the code, keep in mind that output_dir is export_dir or '..'

Later dpkg-source finds the orig inside the export_dir.

This is not a perfect solution, as for multi orig packages the user needs to
manualy add the symlinks in the export_dir, so dpkg-source find the orig*, but
it works most of the time.

Just to be clear, the specific setup I use for KDE packages is:
* git repo with a master branch that only contains debian/, no pristine-tar
  branch, upstream branch is only local
* tarball_dir is set to one directory where all the origs are downloaded
* export_dir is a temporary directory, pruned after packages are uploaded
#748478#22
Date:
2026-09-10 06:57:56 UTC
From:
To:
Hello,

Any news about this bug?

gbp import-orig is still doing the same thing and it pollutes ../ while
it could write everything in ../tarballs

Kind regards,
Laurent Bigonville