From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:catalyst-3.0-stable commit in: catalyst/base/
Date: Sun, 30 Jan 2022 21:02:31 +0000 (UTC) [thread overview]
Message-ID: <1643576365.5f563e551d7cb99edd3af4427186cc250a811f04.mattst88@gentoo> (raw)
commit: 5f563e551d7cb99edd3af4427186cc250a811f04
Author: Matt Turner <mattst88 <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 30 20:59:25 2022 +0000
Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Sun Jan 30 20:59:25 2022 +0000
URL: https://gitweb.gentoo.org/proj/catalyst.git/commit/?id=5f563e55
catalyst: Create snapcache directory
Apparently the snakeoil locking mechanisms implicitly created the
directory for us.
Closes: https://bugs.gentoo.org/806229
Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>
catalyst/base/stagebase.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/catalyst/base/stagebase.py b/catalyst/base/stagebase.py
index 28c4ee23..0cb43033 100644
--- a/catalyst/base/stagebase.py
+++ b/catalyst/base/stagebase.py
@@ -879,6 +879,7 @@ class StageBase(TargetBase, ClearBase, GenBase):
unpack = False
if unpack:
+ ensure_dirs(self.settings['snapshot_cache_path'])
if os.path.exists(target_portdir):
log.info('%s', cleanup_msg)
clear_dir(target_portdir)
next reply other threads:[~2022-01-30 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 21:02 Matt Turner [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-06 22:13 [gentoo-commits] proj/catalyst:catalyst-3.0-stable commit in: catalyst/base/ Matt Turner
2021-06-06 22:38 Matt Turner
2020-10-14 17:50 Matt Turner
2020-09-17 21:13 [gentoo-commits] proj/catalyst:dilfridge/image " Andreas K. Hüttel
2020-09-05 18:33 ` [gentoo-commits] proj/catalyst:catalyst-3.0-stable " Andreas K. Hüttel
2020-07-24 20:33 Andreas K. Hüttel
2020-07-20 0:25 Andreas K. Hüttel
2020-05-17 3:54 Matt Turner
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=1643576365.5f563e551d7cb99edd3af4427186cc250a811f04.mattst88@gentoo \
--to=mattst88@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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