public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: <isar-users@googlegroups.com>
Cc: <ubely@ilbers.de>, <jan.kiszka@siemens.com>,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 00/19] ubely/sbuild: rework handling of DSC files
Date: Mon, 14 Mar 2022 15:59:45 +0100	[thread overview]
Message-ID: <20220314145946.1254164-1-felix.moessbauer@siemens.com> (raw)

This is an addition to the ubely/sbuild branch.
It makes the generation of the DSC file used for the sbuild more robust.

Note: I'm just sending the additional patch.

Best regards,
Felix

Anton Mikanovich (1):
  dpkg: Build packages with sbuild

Felix Moessbauer (1):
  fix: support build of packages with epoch version

Uladzimir Bely (17):
  dpkg-gbp: Use separate command to export tarball
  dpkg-gbp: Use host tools for dsc preparation
  sbuild: Add recipes for host and target rootfs to run sbuild
  sbuild: Introduce a class for another build method
  sbuild: support of DEB_BUILD_PROFILES
  sbuild: support of shell exports from dpkg_runbuild_prepend
  dpkg: Remove builddeps install task.
  sbuild: add ccache support
  dpkg-base: Switch devshell to use schroot
  dpkg-base: Switch apt_fetch and apt_unpack to use schroot
  doc: Add sbuild-related documentation
  sbuild: Use .dsc file instead of source directory.
  sbuild: rework DEB_BUILD_PROFILES
  sbuild: fix proxy support
  sbuild: Fix repro_test fail
  sbuild: Protect sbuild ccache setup by lock
  Run only repro test with leaving build results

 doc/user_manual.md                            |  22 +-
 meta/classes/dpkg-base.bbclass                |  78 +++----
 meta/classes/dpkg-gbp.bbclass                 |  26 +--
 meta/classes/dpkg.bbclass                     | 102 ++++++---
 meta/classes/sbuild.bbclass                   | 202 ++++++++++++++++++
 meta/conf/bitbake.conf                        |   2 +
 .../sbuild-chroot/sbuild-chroot-host.bb       |  13 ++
 .../sbuild-chroot/sbuild-chroot-target.bb     |  10 +
 .../sbuild-chroot/sbuild-chroot.inc           |  39 ++++
 scripts/ci_build.sh                           |   2 +-
 testsuite/build_test/cibase.py                |   2 +-
 11 files changed, 415 insertions(+), 83 deletions(-)
 create mode 100644 meta/classes/sbuild.bbclass
 create mode 100644 meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
 create mode 100644 meta/recipes-devtools/sbuild-chroot/sbuild-chroot-target.bb
 create mode 100644 meta/recipes-devtools/sbuild-chroot/sbuild-chroot.inc

-- 
2.30.2


             reply	other threads:[~2022-03-14 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 14:59 Felix Moessbauer [this message]
2022-03-14 14:59 ` [PATCH 19/19] fix: support build of packages with epoch version Felix Moessbauer

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=20220314145946.1254164-1-felix.moessbauer@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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