Bug#969952: provide a way to export the source tree (without building)

2020-09-10 Thread Santiago R.R. 
El 09/09/20 a las 13:25, Guido Günther escribió:
> Hi,
> On Wed, Sep 09, 2020 at 01:14:07PM +0200, Santiago R.R. wrote:
> > El 09/09/20 a las 11:11, Guido Günther escribió:
> > > Hi,
> > > On Wed, Sep 09, 2020 at 10:49:27AM +0200, Santiago R.R. wrote:
...
> > ACK. Sadly I don't have currently enough free cycles, so I cannot
> > promise I'll be able to do it myself.
> 
> Same here but maybe this helps a little
> 
>
> https://git.sigxcpu.org/cgit/git-buildpackage/commit/?id=c02938fd87042429d6d6102ba55e2b7eee9712f8

Great, thanks!

Forgot to say that would be also useful to have an argument to name the
directory where the debianized source would be extracted, other than
package-name-version.

Cheers,

 -- Santiago


signature.asc
Description: PGP signature

Bug#969952: provide a way to export the source tree (without building)

2020-09-09 Thread Guido Günther 
Hi,
On Wed, Sep 09, 2020 at 01:14:07PM +0200, Santiago R.R. wrote:
> El 09/09/20 a las 11:11, Guido Günther escribió:
> > Hi,
> > On Wed, Sep 09, 2020 at 10:49:27AM +0200, Santiago R.R. wrote:
> > > Source: git-buildpackage
> > > Version: 0.9.20
> > > Severity: wishlist
> > > 
> > > Dear Guido,
> > > 
> > > If I am not wrong, gbp doesn't have a simple method to just export the
> > > source tree (upstream orig + debian/), without building the packcage.
> > > 
> > > It would be nice to have something like:
> > > 
> > > gbp export-source-tree DIR
> > > 
> > > The simplest hack that I've found is (thanks folks in #debian-devel)
> > > somthing like this:
> > > 
> > > gbp buildpackage \
> > > --git-ignore-branch \
> > > --git-ignore-new \
> > > --git-export-dir=${SOURCE_DIR} \
> > > --git-no-purge \
> > > --git-builder="dpkg-buildpackage" \
> > > -S -d -nc -us -uc
> > > 
> > > but it needs to build the source package.
> > > 
> > > Could you please consider this new feature?
> > 
> > As noted on irc you can just use `/bin/true/` as builder:
> > 
> > gbp buildpackage --git-export-dir=/tmp/foo --git-builder=/bin/true 
> > --git-no-pbuilder --git-no-hooks
> 
> For completeness:
> 
>  gbp buildpackage --git-export-dir=/tmp/foo --git-builder=/bin/true 
> --git-no-pbuilder --git-no-hooks --git-no-purge   
> 
> Thanks! I've already tried `--git-builder=/bin/true`, but I was missing
> `--git-no-pbuilder --git-no-hooks`.
> 
> > 
> > but if somebody comes up with a patch that moves that common code into a
> > `export_source` command (including manpage) that would be nice too.
> 
> ACK. Sadly I don't have currently enough free cycles, so I cannot
> promise I'll be able to do it myself.

Same here but maybe this helps a little

   
https://git.sigxcpu.org/cgit/git-buildpackage/commit/?id=c02938fd87042429d6d6102ba55e2b7eee9712f8

Cheers,
 -- Guido

> 
> Thanks,
> 
>  -- Santiago

Bug#969952: provide a way to export the source tree (without building)

2020-09-09 Thread Santiago R.R. 
El 09/09/20 a las 11:11, Guido Günther escribió:
> Hi,
> On Wed, Sep 09, 2020 at 10:49:27AM +0200, Santiago R.R. wrote:
> > Source: git-buildpackage
> > Version: 0.9.20
> > Severity: wishlist
> > 
> > Dear Guido,
> > 
> > If I am not wrong, gbp doesn't have a simple method to just export the
> > source tree (upstream orig + debian/), without building the packcage.
> > 
> > It would be nice to have something like:
> > 
> > gbp export-source-tree DIR
> > 
> > The simplest hack that I've found is (thanks folks in #debian-devel)
> > somthing like this:
> > 
> > gbp buildpackage \
> > --git-ignore-branch \
> > --git-ignore-new \
> > --git-export-dir=${SOURCE_DIR} \
> > --git-no-purge \
> > --git-builder="dpkg-buildpackage" \
> > -S -d -nc -us -uc
> > 
> > but it needs to build the source package.
> > 
> > Could you please consider this new feature?
> 
> As noted on irc you can just use `/bin/true/` as builder:
> 
> gbp buildpackage --git-export-dir=/tmp/foo --git-builder=/bin/true 
> --git-no-pbuilder --git-no-hooks

For completeness:

 gbp buildpackage --git-export-dir=/tmp/foo --git-builder=/bin/true 
--git-no-pbuilder --git-no-hooks --git-no-purge

Thanks! I've already tried `--git-builder=/bin/true`, but I was missing
`--git-no-pbuilder --git-no-hooks`.

> 
> but if somebody comes up with a patch that moves that common code into a
> `export_source` command (including manpage) that would be nice too.

ACK. Sadly I don't have currently enough free cycles, so I cannot
promise I'll be able to do it myself.

Thanks,

 -- Santiago


signature.asc
Description: PGP signature

Bug#969952: provide a way to export the source tree (without building)

2020-09-09 Thread Guido Günther 
Hi,
On Wed, Sep 09, 2020 at 10:49:27AM +0200, Santiago R.R. wrote:
> Source: git-buildpackage
> Version: 0.9.20
> Severity: wishlist
> 
> Dear Guido,
> 
> If I am not wrong, gbp doesn't have a simple method to just export the
> source tree (upstream orig + debian/), without building the packcage.
> 
> It would be nice to have something like:
> 
> gbp export-source-tree DIR
> 
> The simplest hack that I've found is (thanks folks in #debian-devel)
> somthing like this:
> 
> gbp buildpackage \
> --git-ignore-branch \
> --git-ignore-new \
> --git-export-dir=${SOURCE_DIR} \
> --git-no-purge \
> --git-builder="dpkg-buildpackage" \
> -S -d -nc -us -uc
> 
> but it needs to build the source package.
> 
> Could you please consider this new feature?

As noted on irc you can just use `/bin/true/` as builder:

gbp buildpackage --git-export-dir=/tmp/foo --git-builder=/bin/true 
--git-no-pbuilder --git-no-hooks

but if somebody comes up with a patch that moves that common code into a
`export_source` command (including manpage) that would be nice too.
Cheers,
 -- Guido

> 
> Cheers,
> 
>  -- Santiago
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
> 'oldstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU threads)
> Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> -- no debconf information

Bug#969952: provide a way to export the source tree (without building)

2020-09-09 Thread Santiago R.R. 
Source: git-buildpackage
Version: 0.9.20
Severity: wishlist

Dear Guido,

If I am not wrong, gbp doesn't have a simple method to just export the
source tree (upstream orig + debian/), without building the packcage.

It would be nice to have something like:

gbp export-source-tree DIR

The simplest hack that I've found is (thanks folks in #debian-devel)
somthing like this:

gbp buildpackage \
--git-ignore-branch \
--git-ignore-new \
--git-export-dir=${SOURCE_DIR} \
--git-no-purge \
--git-builder="dpkg-buildpackage" \
-S -d -nc -us -uc

but it needs to build the source package.

Could you please consider this new feature?

Cheers,

 -- Santiago

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information


signature.asc
Description: PGP signature