public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v8 01/15] dpkg-gbp: Use separate command to export tarball
Date: Wed, 16 Mar 2022 08:25:53 +0100	[thread overview]
Message-ID: <20220316072607.20518-2-ubely@ilbers.de> (raw)
In-Reply-To: <20220316072607.20518-1-ubely@ilbers.de>

We don't actually build the package with gbp, but only prepare it for
the building with external dpkg-buildpackage command. In case there is
no need in real build we can perform only export which will produce
upstream tarball to pass for later building.
This allows to use any build tool for later processing.

Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
 meta/classes/dpkg-gbp.bbclass | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/meta/classes/dpkg-gbp.bbclass b/meta/classes/dpkg-gbp.bbclass
index d956e8c3..6129d734 100644
--- a/meta/classes/dpkg-gbp.bbclass
+++ b/meta/classes/dpkg-gbp.bbclass
@@ -30,5 +30,9 @@ do_install_builddeps_append() {
 }
 
 dpkg_runbuild_prepend() {
-    export GBP_PREFIX="gbp buildpackage --git-ignore-new ${GBP_EXTRA_OPTIONS} --git-builder="
+    sudo -E chroot --userspec=$( id -u ):$( id -g ) ${BUILDCHROOT_DIR} \
+        sh -c "cd ${PP}/${PPS} && gbp buildpackage --git-ignore-new --git-builder=/bin/true ${GBP_EXTRA_OPTIONS}"
+    # NOTE: `buildpackage --git-builder=/bin/true --git-pristine-tar` is used
+    # for compatibility with gbp version froms debian-stretch. In newer distros
+    # it's possible to use a subcommand `export-orig --pristine-tar`
 }
-- 
2.20.1


  reply	other threads:[~2022-03-16  7:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16  7:25 [PATCH v8 00/15] Sbuild/Schroot migration Uladzimir Bely
2022-03-16  7:25 ` Uladzimir Bely [this message]
2022-03-16  7:25 ` [PATCH v8 02/15] dpkg-gbp: Use host tools for dsc preparation Uladzimir Bely
2022-03-16  7:25 ` [PATCH v8 03/15] sbuild: Add recipes for host and target rootfs to run sbuild Uladzimir Bely
2022-03-16  7:25 ` [PATCH v8 04/15] sbuild: Introduce a class for another build method Uladzimir Bely
2022-03-16  7:25 ` [PATCH v8 05/15] dpkg: Build packages with sbuild Uladzimir Bely
2022-03-16  7:25 ` [PATCH v8 06/15] sbuild: Support of DEB_BUILD_PROFILES Uladzimir Bely
2022-03-16  7:25 ` [PATCH v8 07/15] sbuild: Support of shell exports from dpkg_runbuild_prepend Uladzimir Bely
2022-03-16  7:26 ` [PATCH v8 08/15] dpkg: Remove builddeps install task Uladzimir Bely
2022-03-16  7:26 ` [PATCH v8 09/15] sbuild: Add ccache support Uladzimir Bely
2022-03-16  7:26 ` [PATCH v8 10/15] dpkg-base: Switch devshell to use schroot Uladzimir Bely
2022-03-16  7:26 ` [PATCH v8 11/15] dpkg-base: Switch apt_fetch and apt_unpack " Uladzimir Bely
2022-03-16  7:26 ` [PATCH v8 12/15] doc: Add sbuild-related documentation Uladzimir Bely
2022-03-16  7:26 ` [PATCH v8 13/15] sbuild: Use .dsc file instead of source directory Uladzimir Bely
2022-03-16  7:26 ` [PATCH v8 14/15] sbuild: Fixed proxy support Uladzimir Bely
2022-03-16  7:26 ` [PATCH v8 15/15] sbuild: Fix debsrc_download for packages dependencies Uladzimir Bely
2022-03-16  7:50 ` [PATCH v8 00/15] Sbuild/Schroot migration Uladzimir Bely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220316072607.20518-2-ubely@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox