From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2] dpkg-base: Fix and improve handling of multiple apt sources per package
Date: Mon, 29 Jan 2024 13:49:05 +0300 [thread overview]
Message-ID: <7247b399cd44720143f840b74549f117887e4c75.camel@ilbers.de> (raw)
In-Reply-To: <20240127075617.26804-1-ubely@ilbers.de>
On Sat, 2024-01-27 at 08:56 +0100, Uladzimir Bely wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Due to overeager quoting, multiple entries in SRC_APT would have led
> to
> build errors, rather than mulitple invocations of the fetching and
> unpacking steps.
>
> While fixing that, also avoid pointless re-entries into the schroot
> by
> simply pulling the loop into it.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> Reviewed-by: Uladzimir Bely <ubely@ilbers.de>
> ---
>
Applied to next, thanks.
prev parent reply other threads:[~2024-01-29 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 7:56 Uladzimir Bely
2024-01-29 10:49 ` Uladzimir Bely [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=7247b399cd44720143f840b74549f117887e4c75.camel@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