catalyst-3.0.22-r2 fails to create a /etc/catalyst/*, resulting in catalyst failing to run. Additionally, if upgrading from a previous version, /etc/catalyst/* no longer exists. /etc/catalyst/* should be preserved to prevent users from losing config files. Reproducible: Always Steps to Reproduce: 1. Have working catalyst-3.0.22-r1 or earlier 2. Upgrade to catalyst-3.0.22-r2 3. Run catalyst stage1.* Actual Results: 12 Jul 2023 06:35:29 EDT: NOTICE : Loading configuration file: /etc/catalyst/catalyst.conf 12 Jul 2023 06:35:29 EDT: ERROR : CatalystError: Could not open file /etc/catalyst/catalyst.conf Traceback (most recent call last): File "/usr/lib/python3.11/site-packages/catalyst/config.py", line 31, in parse_file with open(filename, "r") as myf: ^^^^^^^^^^^^^^^^^^^ FileNotFoundError: [Errno 2] No such file or directory: '/etc/catalyst/catalyst.conf' Expected Results: Catalyst finds catalyst.conf.
I don't see how you'd lose your existing one with CONFIG_PROTECT. Anyway, probably the PEP517 conversion.
Sorry about that, will fix shortly. We lost man pages too. But I believe you'd only lose your existing copies in /etc if they were unmodified... so no crucial custom config was lost, but it does make catalyst unable to run.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8cb5483f0ef5ea115748f8db5545a77aca4fcdcf commit 8cb5483f0ef5ea115748f8db5545a77aca4fcdcf Author: Ben Kohler <bkohler@gentoo.org> AuthorDate: 2023-07-12 16:12:50 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2023-07-12 16:16:54 +0000 dev-util/catalyst: restore missing configs & man from PEP517 conversion Closes: https://bugs.gentoo.org/910261 Signed-off-by: Ben Kohler <bkohler@gentoo.org> .../{catalyst-3.0.22-r2.ebuild => catalyst-3.0.22-r3.ebuild} | 8 ++++++++ dev-util/catalyst/catalyst-9999.ebuild | 4 ++++ 2 files changed, 12 insertions(+)
