From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Question about base-apt: Usage of BASE_DISTRO instead of DISTRO
Date: Wed, 22 May 2019 10:24:01 +0200 [thread overview]
Message-ID: <54843fa8-16ea-195c-4ffa-8ec10fa9246c@siemens.com> (raw)
Hi,
I am currently investigating a CI issue, and some input would be nice to
have, since it touches code I am not that familiar with.
This is the log:
ERROR: mc:qemuarm-buster:isar-image-base-debian-buster-qemuarm
do_cache_base_repo: Function failed: do_cache_base_repo (log file is
located at
/workspace/build/isar_claudius_ilbers_fast_ci/26/build/tmp/work/debian-buster-armhf/isar-image-base-debian-buster-qemuarm/temp/log.do_cache_base_repo.14542)
ERROR: Logfile of failure stored in:
/workspace/build/isar_claudius_ilbers_fast_ci/26/build/tmp/work/debian-buster-armhf/isar-image-base-debian-buster-qemuarm/temp/log.do_cache_base_repo.14542
Log data follows:
| dpkg: warning: failed to open configuration file '/root/.dpkg.cfg' for
reading: Permission denied
| DEBUG: Executing shell function do_cache_base_repo
| Cannot find definition of distribution 'buster'!
| There have been errors!
| WARNING: exit code 249 from a shell command.
| ERROR: Function failed: do_cache_base_repo (log file is located at
/workspace/build/isar_claudius_ilbers_fast_ci/26/build/tmp/work/debian-buster-armhf/isar-image-base-debian-buster-qemuarm/temp/log.do_cache_base_repo.14542)
NOTE: recipe isar-image-base-debian-buster-qemuarm: task
do_cache_base_repo: Failed
ERROR: Task
(multiconfig:qemuarm-buster:/workspace/build/isar_claudius_ilbers_fast_ci/26/meta-isar/recipes-core/images/isar-image-base.bb:do_cache_base_repo)
failed with exit code '1'
That happens because 'buster' was not added to the repository configuration:
build/downloads/base-apt/apt/debian/conf/distributions:
Codename: stretch
Architectures: i386 armhf arm64 amd64 source
Components: main
The reason for that is that base-apt does not add a distribution entry,
if there is already a configuration file in place.
meta/recipes-devtools/base-apt/base-apt.bb:
[...]
CACHE_CONF_DIR = "${REPO_BASE_DIR}/${BASE_DISTRO}/conf"
[...]
if [ ! -e "${CACHE_CONF_DIR}/distributions" ]; then
sed -e "s#{CODENAME}#"${BASE_DISTRO_CODENAME}"#g" \
${WORKDIR}/distributions.in > ${CACHE_CONF_DIR}/distributions
if [ "${BASE_REPO_KEY}" ] ; then
# To generate Release.gpg
echo "SignWith: yes" >> ${CACHE_CONF_DIR}/distributions
fi
fi
[...]
What I currently don't understand is why the path to the repositories
contains BASE_DISTRO instead of DISTRO and is causing this kind of conflict?
I would now just rename the mentions of BASE_DISTRO to use DISTRO, but I
don't know if that is possible breaking the design here. To me that
looks a bit too deliberate to be just a bug.
My question is if the base-apt repository is meant to hold repositories
for different codenames and `base-apt` simply sets it wrong, or if we
want to have different repositories for each codename to avoid any
conflicts.
regards,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
reply other threads:[~2019-05-22 8:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54843fa8-16ea-195c-4ffa-8ec10fa9246c@siemens.com \
--to=claudius.heine.ext@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