Summary: | app-portage/ufed adds -* when it shouldn't. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Kevin Korb <gentoobugs> |
Component: | Tools | Assignee: | Sven Eden <sven.eden> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | axiator, boxcars, brian, bruce, che, holger, kensington, kripton, mgorny, mmw, ms, proxy-maint, qa, redblade7, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kevin Korb
2018-03-02 23:30:47 UTC
If only we had responsible developers in tools-portage, this bug report would save some users from catastrophic system destruction. I'm going to apply an emergency mask. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0b107e42c5d349e08c33f7113283a8321e68d4c5 commit 0b107e42c5d349e08c33f7113283a8321e68d4c5 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-05-01 06:41:21 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-05-01 06:41:21 +0000 package.mask: [QA] Mask app-portage/ufed for breakage Bug: https://bugs.gentoo.org/649416 Signed-off-by: Michał Górny <mgorny@gentoo.org> profiles/package.mask | 5 +++++ 1 file changed, 5 insertions(+) I ran into this exact same issue a week ago. I finally found -* in my make.conf, but I had no idea how it got there. I've been a long time user of ufed and use it semi-frequently. (In reply to George Cox from comment #3) > I ran into this exact same issue a week ago. I finally found -* in my > make.conf, but I had no idea how it got there. I've been a long time user of > ufed and use it semi-frequently. I ran into this too but the workaround is not too bad. You just select - for "-*" field in ufed and then it works fine. With respect, masking based on a 2+ year old report - when no others have complained or reported an issue in the intervening time - seems a bit much. I use this semi-regularly and don't see the problem; as Andrius said, simply set '-*' to '-' and all is well. Perhaps a post-installation note is a better approach? Given the potential for major breakage Michał Górny made the right call. A better question is what was this package doing in portage for two years with this outstanding bug? I also noticed this behavior a couple of months ago. I'm surprised that it's been around since 2018! It hit me just now reading the first post by Kevin Korb why it suddenly triggered for me: It must be because I've recently been trying to get rid of python 2.7 so I have added -* somewhere in there! see also https://bugs.gentoo.org/549042 It looks as the bug is since 2015. (In reply to jospezial from comment #8) > see also https://bugs.gentoo.org/549042 > > It looks as the bug is since 2015. Thank you. This is a duplicate of bug 549042, and the patch in attachment 402928 [details, diff] appears to fix it. *** This bug has been marked as a duplicate of bug 549042 *** I don't know why, but this bug report totally got past me. Just now I have tried it out: 1) Add any package with "-*" to any file in /etc/portage/package.use 2) Start ufed 3) -* is ticked That's bad, but I will continue in the other report. |