From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: ubely@ilbers.de
Cc: isar-users@googlegroups.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH(sbuild) 0/1] Fix issues on rebuild with empty DL_DIR
Date: Fri, 8 Apr 2022 11:23:49 +0200 [thread overview]
Message-ID: <20220408092350.2220280-1-felix.moessbauer@siemens.com> (raw)
Hi,
this is an addition to the sbuild-v8 patch series.
It fixes the discussed issue when re-building with sstate,
but without a persistent DL_DIR.
By that, the DL_DIR was empty, hence the deb_dl_dir_import function
did not find any files and also did not create the directories.
Note, that this is technically unrelated to sstate-cache,
but was only observed when using sstate, as the DL_DIR otherwise
always contained at least one package.
Best regards,
Felix
Felix Moessbauer (1):
always create apt-cache dirs in deb_dl_dir_import
meta/classes/deb-dl-dir.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.30.2
next reply other threads:[~2022-04-08 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 9:23 Felix Moessbauer [this message]
2022-04-08 9:23 ` [PATCH(sbuild) 1/1] always create apt-cache dirs in deb_dl_dir_import Felix Moessbauer
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=20220408092350.2220280-1-felix.moessbauer@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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