From: "Andreas K. Hüttel" <dilfridge@gentoo.org> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/catalyst:master commit in: catalyst/targets/ Date: Sat, 3 Aug 2024 09:06:51 +0000 (UTC) [thread overview] Message-ID: <1722675989.31d975c10785f4de73cd788285ccf2408aa54a30.dilfridge@gentoo> (raw) commit: 31d975c10785f4de73cd788285ccf2408aa54a30 Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org> AuthorDate: Sat Aug 3 09:06:29 2024 +0000 Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org> CommitDate: Sat Aug 3 09:06:29 2024 +0000 URL: https://gitweb.gentoo.org/proj/catalyst.git/commit/?id=31d975c1 stage1: make sure we bind-mount within the chroot dir, try 3, now with pathlib Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org> catalyst/targets/stage1.py | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/catalyst/targets/stage1.py b/catalyst/targets/stage1.py index ba42d9b8..ae27cd0a 100644 --- a/catalyst/targets/stage1.py +++ b/catalyst/targets/stage1.py @@ -31,14 +31,18 @@ class stage1(StageBase): # otherwise we may end up trying to mount the same squashfs twice instead # of a bind mount # * take the directory inside the chroot as source, not the host directory + # In the meantime we fixed make.profile to point outside ROOT, so this may not + # be necessary at the moment anymore. Having it can prevent future surprises + # though. self.set_chroot_path() for path, name, _ in self.repos: name = get_repo_name(path) mount_id = f'root_repo_{name}' + repo_loc = self.get_repo_location(name) self.mount[mount_id] = { 'enable': True, - 'source': self.settings['chroot_path'] / self.get_repo_location(name), - 'target': normpath("/tmp/stage1root") / self.get_repo_location(name) + 'source': self.settings['chroot_path'] / repo_loc.relative_to('/'), + 'target': normpath("/tmp/stage1root") / repo_loc.relative_to('/') } def set_root_path(self):
WARNING: multiple messages have this Message-ID (diff)
From: "Andreas K. Hüttel" <dilfridge@gentoo.org> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/catalyst:dilfridge/qcow2 commit in: catalyst/targets/ Date: Fri, 9 Aug 2024 19:34:08 +0000 (UTC) [thread overview] Message-ID: <1722675989.31d975c10785f4de73cd788285ccf2408aa54a30.dilfridge@gentoo> (raw) Message-ID: <20240809193408.Mibtpmo_n0LjGo41-LW0xsH-EF3Sup7AR4DfUudsKPQ@z> (raw) commit: 31d975c10785f4de73cd788285ccf2408aa54a30 Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org> AuthorDate: Sat Aug 3 09:06:29 2024 +0000 Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org> CommitDate: Sat Aug 3 09:06:29 2024 +0000 URL: https://gitweb.gentoo.org/proj/catalyst.git/commit/?id=31d975c1 stage1: make sure we bind-mount within the chroot dir, try 3, now with pathlib Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org> catalyst/targets/stage1.py | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/catalyst/targets/stage1.py b/catalyst/targets/stage1.py index ba42d9b8..ae27cd0a 100644 --- a/catalyst/targets/stage1.py +++ b/catalyst/targets/stage1.py @@ -31,14 +31,18 @@ class stage1(StageBase): # otherwise we may end up trying to mount the same squashfs twice instead # of a bind mount # * take the directory inside the chroot as source, not the host directory + # In the meantime we fixed make.profile to point outside ROOT, so this may not + # be necessary at the moment anymore. Having it can prevent future surprises + # though. self.set_chroot_path() for path, name, _ in self.repos: name = get_repo_name(path) mount_id = f'root_repo_{name}' + repo_loc = self.get_repo_location(name) self.mount[mount_id] = { 'enable': True, - 'source': self.settings['chroot_path'] / self.get_repo_location(name), - 'target': normpath("/tmp/stage1root") / self.get_repo_location(name) + 'source': self.settings['chroot_path'] / repo_loc.relative_to('/'), + 'target': normpath("/tmp/stage1root") / repo_loc.relative_to('/') } def set_root_path(self):
next reply other threads:[~2024-08-03 9:06 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-08-03 9:06 Andreas K. Hüttel [this message] 2024-08-09 19:34 ` [gentoo-commits] proj/catalyst:dilfridge/qcow2 commit in: catalyst/targets/ Andreas K. Hüttel -- strict thread matches above, loose matches on Subject: below -- 2024-10-13 20:33 [gentoo-commits] proj/catalyst:master " Andreas K. Hüttel 2024-10-13 20:33 Andreas K. Hüttel 2024-08-03 11:01 Andreas K. Hüttel 2024-07-30 15:29 Andreas K. Hüttel 2024-07-30 15:28 Andreas K. Hüttel 2024-07-30 14:54 Andreas K. Hüttel 2024-07-30 14:45 Andreas K. Hüttel 2024-07-30 11:06 Andreas K. Hüttel 2024-07-30 11:06 Andreas K. Hüttel 2022-11-20 0:21 [gentoo-commits] proj/catalyst:wip/mattst88 " Matt Turner 2022-04-02 23:50 ` [gentoo-commits] proj/catalyst:master " Matt Turner 2021-02-21 2:05 Matt Turner 2021-01-18 19:53 [gentoo-commits] proj/catalyst:pending/mattst88 " Matt Turner 2020-12-27 23:15 ` [gentoo-commits] proj/catalyst:master " Matt Turner 2020-10-29 21:00 [gentoo-commits] proj/catalyst:wip/mattst88 " Matt Turner 2020-10-24 22:07 ` [gentoo-commits] proj/catalyst:master " Matt Turner 2020-10-24 22:07 Matt Turner 2020-10-23 4:36 [gentoo-commits] proj/catalyst:pending/mattst88 " Matt Turner 2020-10-24 22:07 ` [gentoo-commits] proj/catalyst:master " Matt Turner 2020-06-05 21:13 Matt Turner 2020-06-05 21:13 Matt Turner 2020-05-20 3:39 [gentoo-commits] proj/catalyst:pending/mattst88 " Matt Turner 2020-05-17 22:54 ` [gentoo-commits] proj/catalyst:master " Matt Turner 2020-05-16 6:43 Matt Turner 2020-05-16 6:43 Matt Turner 2019-10-11 16:02 Ben Kohler 2019-07-01 15:35 Rick Farina 2018-10-01 16:30 Brian Dolbec 2018-07-21 18:54 Brian Dolbec 2018-04-05 18:21 Richard Farina 2018-01-04 19:09 Brian Dolbec 2017-12-18 16:57 Richard Farina 2017-11-29 17:20 Brian Dolbec 2016-03-21 5:09 Mike Frysinger 2015-12-23 4:30 Brian Dolbec 2015-12-15 17:13 Brian Dolbec 2015-12-15 17:13 Brian Dolbec 2015-12-15 17:13 Brian Dolbec 2015-12-15 17:13 Brian Dolbec 2015-12-15 17:13 Brian Dolbec 2015-11-12 16:24 Brian Dolbec 2015-10-11 17:26 Mike Frysinger 2015-10-11 17:26 Mike Frysinger 2015-10-11 17:26 Mike Frysinger 2015-10-11 17:26 Mike Frysinger 2015-10-11 17:26 Mike Frysinger 2015-10-11 17:26 Mike Frysinger 2015-10-09 21:06 Mike Frysinger 2015-10-08 22:09 Mike Frysinger 2015-10-08 3:53 Mike Frysinger 2015-10-06 15:31 Mike Frysinger 2015-09-15 21:48 Richard Farina 2015-09-09 17:42 Brian Dolbec 2015-02-26 20:12 Brian Dolbec 2015-02-26 19:25 [gentoo-commits] proj/catalyst:pending " Brian Dolbec 2015-02-26 20:12 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec 2015-01-01 5:59 [gentoo-commits] proj/catalyst:pending " Brian Dolbec 2015-02-26 20:12 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec 2015-01-01 5:59 [gentoo-commits] proj/catalyst:pending " Brian Dolbec 2015-02-26 4:12 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec 2014-05-05 19:17 Brian Dolbec 2014-04-02 20:09 [gentoo-commits] proj/catalyst:pending " Brian Dolbec 2014-04-02 20:09 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec 2014-04-02 20:09 [gentoo-commits] proj/catalyst:pending " Brian Dolbec 2014-04-02 20:09 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec 2014-04-02 20:09 [gentoo-commits] proj/catalyst:pending " Brian Dolbec 2014-04-02 20:09 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec
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=1722675989.31d975c10785f4de73cd788285ccf2408aa54a30.dilfridge@gentoo \ --to=dilfridge@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: linkBe 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