public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: adriaan.schmidt@siemens.com, Uladzimir Bely <ubely@ilbers.de>
Subject: [PATCH v10 01/19] dpkg-gbp: Use separate command to export tarball
Date: Thu,  5 May 2022 17:39:16 +0300	[thread overview]
Message-ID: <20220505143934.16096-2-amikan@ilbers.de> (raw)
In-Reply-To: <20220505143934.16096-1-amikan@ilbers.de>

From: Uladzimir Bely <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 d956e8c..6129d73 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.17.1


  reply	other threads:[~2022-05-05 14:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 14:39 [PATCH v10 00/19] Sbuild/Schroot migration Anton Mikanovich
2022-05-05 14:39 ` Anton Mikanovich [this message]
2022-05-05 14:39 ` [PATCH v10 02/19] dpkg-gbp: Use host tools for dsc preparation Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 03/19] sbuild: Add recipes for host and target rootfs to run sbuild Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 04/19] sbuild: Introduce a class for another build method Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 05/19] dpkg: Build packages with sbuild Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 06/19] sbuild: Support of DEB_BUILD_PROFILES Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 07/19] sbuild: Support of shell exports from dpkg_runbuild_prepend Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 08/19] dpkg: Remove builddeps install task Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 09/19] sbuild: Add ccache support Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 10/19] dpkg-base: Switch devshell to use schroot Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 11/19] dpkg-base: Switch apt_fetch and apt_unpack " Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 12/19] doc: Add sbuild-related documentation Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 13/19] sbuild: Use .dsc file instead of source directory Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 14/19] sbuild: Fixed proxy support Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 15/19] sbuild: Fix debsrc_download for packages dependencies Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 16/19] fix: support build of packages with epoch version Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 17/19] always create apt-cache dirs in deb_dl_dir_import Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 18/19] avoid absolute SCHROOT_* paths to improve caching Anton Mikanovich
2022-05-05 14:39 ` [PATCH v10 19/19] dpkg-base: Cleanup on schroot fail Anton Mikanovich
2022-05-12 12:54 ` [PATCH v10 00/19] Sbuild/Schroot migration Anton Mikanovich
2022-05-12 15:55   ` Moessbauer, Felix
2022-05-18 16:20     ` Baurzhan Ismagulov

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=20220505143934.16096-2-amikan@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=adriaan.schmidt@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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