From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] fix(apt-fetcher): drop isar apt entries before fetching on unshare
Date: Fri, 31 Jul 2026 10:34:30 +0200 [thread overview]
Message-ID: <1817c348-ce12-4b98-94b9-13824c413220@ilbers.de> (raw)
In-Reply-To: <20260729111518.3667086-1-felix.moessbauer@siemens.com>
Applied to next, thanks.
Zhihang
On 7/29/26 13:15, 'Felix Moessbauer' via isar-users wrote:
> The apt-fetcher must only fetch from upstream (but not from isar-apt),
> as otherwise the altered files are ingressed on the next fetch. This is
> already correctly implemented for the schroot backend, but was missed
> for unshare.
>
> Fixes: f2644cd7 ("apt-fetcher: implement support for unshare ...")
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> meta/lib/aptsrc_fetcher.py | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/lib/aptsrc_fetcher.py b/meta/lib/aptsrc_fetcher.py
> index 49f12075..fe8f1cd3 100644
> --- a/meta/lib/aptsrc_fetcher.py
> +++ b/meta/lib/aptsrc_fetcher.py
> @@ -108,6 +108,8 @@ class AptSrcUnshare(AptSrc):
> mkdir -p {rootfsdir}
> tar -xf {sbuild_chroot} -C {rootfsdir}
> cp /etc/resolv.conf {os.path.join(rootfsdir, 'etc/resolv.conf')}
> + rm -f {rootfsdir}/etc/apt/sources.list.d/isar-apt.list \
> + {rootfsdir}/etc/apt/preferences.d/isar-apt
> EOF
> ''', d)
> logger.info(f'rootfs extracted to: {rootfsdir}')
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/1817c348-ce12-4b98-94b9-13824c413220%40ilbers.de.
prev parent reply other threads:[~2026-07-31 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 11:15 'Felix Moessbauer' via isar-users
2026-07-31 8:34 ` Zhihang Wei [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=1817c348-ce12-4b98-94b9-13824c413220@ilbers.de \
--to=wzh@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--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