Re: [git-buildpackage] Would it be possible for pristine-tar to not be an absolute path?

On 12.01.2018 [09:26:11 +0100], Guido Günther wrote: > Hi, > On Thu, Jan 11, 2018 at 02:57:03PM -0800, Nish Aravamudan wrote: > > On Sun, Jan 7, 2018 at 11:09 AM, Guido Günther <a...@sigxcpu.org> wrote: > > > Hi, > > > On Fri, Jan 05, 2018 at 09:55:30PM -08

Re: [git-buildpackage] gbp and git-worktrees

On Thu, Jan 11, 2018 at 1:24 PM, Nish Aravamudan <nish.aravamu...@canonical.com> wrote: > Hi Guido, > > Sorry for all the noise lately! Have another question for you: Doubly sorry for the noise! I think I tracked this down to having GIT_WORK_TREE set which is conflicting withe

[git-buildpackage] gbp and git-worktrees

Hi Guido, Sorry for all the noise lately! Have another question for you: In git-ubuntu, we are starting to heavily use git-worktrees, so that we can have temporary locations that checkout different commits/trees/etc than HEAD. This is very useful for us, e.g., when linting arbitrary commits

Re: [git-buildpackage] could gbp.config.GbpOptionParser.get_config_files handle GBP_CONF_FILES=''

On 11.01.2018 [18:04:08 +0100], Guido Günther wrote: > Hi, > On Thu, Jan 11, 2018 at 08:22:13AM -0800, Nish Aravamudan wrote: > > On 11.01.2018 [08:39:10 +0100], Guido Günther wrote: > > > Hi Nish, > > > On Wed, Jan 10, 2018 at 02:21:52P

[git-buildpackage] could gbp.config.GbpOptionParser.get_config_files handle GBP_CONF_FILES=''

For the reproducibility/debuggability of the git-ubuntu snap, we want to ensure that everyone will end up running certain commands (e.g., quilt, gbp) the same, no matter what their local configuration is. This is especially true for the importer itself, but is also true for other subcommands in

Re: [git-buildpackage] Would it be possible for pristine-tar to not be an absolute path?

On Jan 7, 2018 12:51, "Guido Günther" <a...@sigxcpu.org> wrote: Hi, On Sun, Jan 07, 2018 at 11:31:07AM -0800, Nish Aravamudan wrote: [..snip..] > gbp export-orig should > support exporting any version given a debian revision: > > gbp export-ori

Re: [git-buildpackage] Would it be possible for pristine-tar to not be an absolute path?

Hi Guido, On Wed, Aug 30, 2017 at 12:47 PM, Guido Günther wrote: >> To be clear, we only use gbp for orig tarball handling currently (we >> import-orig the tarballs published for Debian & Ubuntu, and use >> buildpackage (eventually export-orig, once it's available) to get

Re: [git-buildpackage] setting author on command line for gbp dch

On Dec 18, 2017 13:40, "Gijs Molenaar" wrote: 2017-12-18 9:35 GMT+02:00 Gijs Molenaar : > Hi Guido, > > Thanks for your reply, and sorry for the delay. > > 2017-11-27 15:30 GMT+02:00 Guido Günther : > >> [...] >> >> This works

[git-buildpackage] ~ in debian/changelog breaks setup.py

The current version in setup.py is derived from debian/changelog. I believe this makes it impossible to actually build from setup.py (I get eventual errors: Could not find a version that satisfies the requirement gbp (from versions: 0.9.0-exp6) I think the ~ gets translated to - automatically

Re: [git-buildpackage] Would it be possible for pristine-tar to not be an absolute path?

On 30.08.2017 [21:47:08 +0200], Guido Günther wrote: > Hi, > On Wed, Aug 30, 2017 at 10:18:10AM -0700, Nish Aravamudan wrote: > > On 30.08.2017 [19:02:20 +0200], Guido Günther wrote: > > > Hi, > > > On Wed, Aug 30, 2017 at 09:37:28AM -0700, Nish Aravamudan wrote: >

Re: [git-buildpackage] Would it be possible for pristine-tar to not be an absolute path?

On 30.08.2017 [21:47:08 +0200], Guido Günther wrote: > Hi, > On Wed, Aug 30, 2017 at 10:18:10AM -0700, Nish Aravamudan wrote: > > On 30.08.2017 [19:02:20 +0200], Guido Günther wrote: > > > Hi, > > > On Wed, Aug 30, 2017 at 09:37:28AM -0700, Nish Aravamudan wrote: >

Re: [git-buildpackage] Would it be possible for pristine-tar to not be an absolute path?

On 30.08.2017 [19:02:20 +0200], Guido Günther wrote: > Hi, > On Wed, Aug 30, 2017 at 09:37:28AM -0700, Nish Aravamudan wrote: > > Hello, > > > > I am currently using gbp in a snap for `git-ubuntu`, a tool similar to > > dgit for doing Ubuntu source package work. The

[git-buildpackage] Would it be possible for pristine-tar to not be an absolute path?

Hello, I am currently using gbp in a snap for `git-ubuntu`, a tool similar to dgit for doing Ubuntu source package work. The snap contains all its dependencies, including pristine-tar at paths within the snap (which I ensure are in PATH when my tool runs), but gbp has a hard-coded path to

Re: [git-buildpackage] [ANNOUNCE] git-buildpackage 0.9.0~exp4

Hi Guido, On Sun, Aug 27, 2017 at 12:39 PM, Guido Günther wrote: > Hi, > I'm happy to announce the relesae of git-buildpackage 0.9.0~exp4: > > https://git.sigxcpu.org/cgit/git-buildpackage/tag/?id=debian/0.9.0~exp4 FYI, this is actually

Re: [git-buildpackage] `gbp import-orig --pristine-tar` with component tarballs

On Thu, Jun 29, 2017 at 5:59 PM, Nish Aravamudan <nish.aravamu...@canonical.com> wrote: > Hello, > > I *think* I may have found a bug in `gbp import-orig --pristine-tar` with > multiple component tarballs, but I'm not 100% :) I think I can TL;DR my previous e-mail a bit, hope

[git-buildpackage] `gbp import-orig --pristine-tar` with component tarballs

Hello, I *think* I may have found a bug in `gbp import-orig --pristine-tar` with multiple component tarballs, but I'm not 100% :) I'm specifically looking (as a test example) src:gosa, e.g., 2.7.4+reloaded2-13. The behavior I'm seeing is that while the machine that does the pristine-tar import