public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [RFC 0/2] Fixes for dpkg-gdb packages rebuild
Date: Thu, 12 Aug 2021 11:01:04 +0200	[thread overview]
Message-ID: <c1a1a941-b1d0-c3cc-0c63-480e874a9c20@siemens.com> (raw)
In-Reply-To: <20210812081030.4505-1-ubely@ilbers.de>

On 12.08.21 10:10, Uladzimir Bely wrote:
> Second isar build can cause some packages rebuild due to configuration
> changes and some of thems (like cowsay) fail due to broken git tree
> and/or already being applied.
> 
> Uladzimir Bely (2):
>   dpkg-base: Add new git alternates record instead of replace old one
>   dpkg-gdb: Reset git to SRCREV revision before patching
> 
>  meta/classes/dpkg-base.bbclass |  2 +-
>  meta/classes/dpkg-gbp.bbclass  | 10 ++++++++++
>  2 files changed, 11 insertions(+), 1 deletion(-)
> 

I've fixed this locally, enabling alternates both inside and outside the
buildchroot without switching it.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

      parent reply	other threads:[~2021-08-12  9:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12  8:10 Uladzimir Bely
2021-08-12  8:10 ` [RFC 1/2] dpkg-base: Add new git alternates record instead of replace old one Uladzimir Bely
2021-08-12  9:00   ` Jan Kiszka
2021-08-12  9:18     ` Uladzimir Bely
2021-08-12  9:24       ` Jan Kiszka
2021-08-12  8:10 ` [RFC 2/2] dpkg-gdb: Reset git to SRCREV revision before patching Uladzimir Bely
2021-08-12  9:01 ` Jan Kiszka [this message]

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=c1a1a941-b1d0-c3cc-0c63-480e874a9c20@siemens.com \
    --to=jan.kiszka@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