From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "Gylstorff, Quirin" <quirin.gylstorff@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/1] deduplicate apt sources.list based on filenames
Date: Thu, 27 Jul 2023 03:26:26 +0000 [thread overview]
Message-ID: <15630e37d0cd4deab9e9167619e205dedd53820d.camel@siemens.com> (raw)
In-Reply-To: <6f839d5b-4316-6523-368d-e1b3e450c35e@siemens.com>
On Wed, 2023-07-26 at 10:59 +0200, 'Gylstorff Quirin' via isar-users
wrote:
>
>
> On 7/26/23 08:14, 'Felix Moessbauer' via isar-users wrote:
> > When combining layers, it can happen that the same
> > DISTRO_APT_SOURCES
> > entry is added multiple times. This creates duplicate entries in
> > the
> > bootstrap.list, which is considered invalid by apt. To solve this,
> > we
> > deduplicate the values in the [HOST_]DISTRO_APT_SOURCES variable.
> > In addition, this also avoids adding the same SRC_URI entry twice.
> >
> > Note, that this only solves the trivial case that the duplicate
> > entries
> > come from the same file. However in case duplicate entries are
> > added
> > from multiple files with different names, the :remove syntax can be
> > used to remove these for the affected targets.
> >
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > ---
> > meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 13 ++++++--
> > -----
> > 1 file changed, 6 insertions(+), 7 deletions(-)
> >
> > diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> > b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> > index b94ae0bd..8af73a9b 100644
> > --- a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> > +++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> > @@ -59,8 +59,8 @@ python () {
> > filename = os.path.relpath(fetcher.localpath(key),
> > topdir)
> > d.appendVar("THIRD_PARTY_APT_KEYFILES", " ${TOPDIR}/%s" %
> > filename)
> >
> > - distro_apt_sources = d.getVar(d.getVar("DISTRO_VARS_PREFIX") +
> > "DISTRO_APT_SOURCES") or ""
> > - for file in distro_apt_sources.split():
> > + distro_apt_sources = get_aptsources_list(d)
> > + for file in distro_apt_sources:
> > d.appendVar("SRC_URI", " file://%s" % file)
> >
> > distro_apt_preferences =
> > d.getVar(d.getVar("DISTRO_VARS_PREFIX") + "DISTRO_APT_PREFERENCES")
> > or ""
> > @@ -149,10 +149,11 @@ def aggregate_aptsources_list(d, file_list,
> > file_out):
> >
> > def get_aptsources_list(d):
> > import errno
> > + from collections import OrderedDict
> > apt_sources_var = d.getVar("DISTRO_VARS_PREFIX") +
> > "DISTRO_APT_SOURCES"
> > - list = (d.getVar(apt_sources_var) or "").split()
> > + apt_sources_list =
> > list(OrderedDict.fromkeys((d.getVar(apt_sources_var) or
> > "").split()))
> Why not use `set()` if the goal is to remove all duplicates?
The set() does not preserve the order of the entries. However, the
order might be relevant as it influences the order of the entries in
the apt sources list. With the OrderedDict approach, the order is
preserved.
Felix
>
> Quirin
> > ret = []
> > - for p in list:
> > + for p in apt_sources_list:
> > try:
> > f = bb.parse.resolve_file(p, d)
> > ret.append(f)
> > @@ -251,9 +252,7 @@ python do_apt_config_prepare() {
> >
> > apt_sources_out = d.getVar("APTSRCS")
> > apt_sources_init_out = d.getVar("APTSRCS_INIT")
> > - apt_sources_list = (
> > - d.getVar(d.getVar("DISTRO_VARS_PREFIX") +
> > "DISTRO_APT_SOURCES") or ""
> > - ).split()
> > + apt_sources_list = get_aptsources_list(d)
> >
> > aggregate_files(d, apt_sources_list, apt_sources_init_out)
> > aggregate_aptsources_list(d, apt_sources_list,
> > apt_sources_out)
>
next prev parent reply other threads:[~2023-07-27 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 6:14 Felix Moessbauer
2023-07-26 8:59 ` Gylstorff Quirin
2023-07-27 3:26 ` MOESSBAUER, Felix [this message]
2023-07-27 9:51 ` Gylstorff Quirin
2023-08-02 21:30 ` Uladzimir Bely
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=15630e37d0cd4deab9e9167619e205dedd53820d.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=quirin.gylstorff@siemens.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