From: Tim Orling <ticotimo@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Tim Orling <tim.orling@konsulko.com>
Subject: [PATCH 0/3] Fix distro_check when a distro list cannot be fetched
Date: Sat, 14 Nov 2026 12:08:07 -0800 [thread overview]
Message-ID: <20261114200810.31078-1-tim.orling@konsulko.com> (raw)
create_distro_packages_list() in meta/lib/oe/distro_check.py writes no
package lists at all at the moment: the Debian list always fails, and
any failed distro then crashes the loop with UnboundLocalError.
1: Skip a distro whose package list can't be fetched.
2: ftp.debian.org no longer has dists/stable-proposed-updates. Read
Debian updates from stable-updates instead, which is only published
as Sources.xz.
3: Offline oe-selftest tests (oelib.distro_check) for both.
Nothing in OE-Core has used oe.distro_check since distrodata.bbclass
was removed in 2018, but the Recipe Reporting System on the layer
index still does (rrs_distros.py), to show which distros package each
recipe, and it has been broken by this.
[YOCTO #16503]
Tim Orling (3):
lib/oe/distro_check: skip a distro whose package list can't be fetched
lib/oe/distro_check: fetch Debian updates from stable-updates
oeqa/selftest/oelib: add tests for oe.distro_check
meta/lib/oe/distro_check.py | 9 ++-
.../oeqa/selftest/cases/oelib/distro_check.py | 59 +++++++++++++++++++
2 files changed, 65 insertions(+), 3 deletions(-)
create mode 100644 meta/lib/oeqa/selftest/cases/oelib/distro_check.py
--
2.56.1
next reply other threads:[~2026-11-14 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 20:08 Tim Orling [this message]
2026-11-14 20:08 ` [PATCH 1/3] lib/oe/distro_check: skip a distro whose package list can't be fetched Tim Orling
2026-11-14 20:08 ` [PATCH 2/3] lib/oe/distro_check: fetch Debian updates from stable-updates Tim Orling
2026-11-14 20:08 ` [PATCH 3/3] oeqa/selftest/oelib: add tests for oe.distro_check Tim Orling
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=20261114200810.31078-1-tim.orling@konsulko.com \
--to=ticotimo@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tim.orling@konsulko.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