| Summary: | ufed produces an error message, quits | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Tim Redman <tim> |
| Component: | Tools | Assignee: | Portage Tools Team <tools-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | davidgrant, k, tsdh |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Tim Redman
2004-11-08 04:57:30 UTC
It's almost certainly a change to your profile that did this, not a change of portage version. ufed 0.35 and earlier don't support stacked profiles. 0.35-r1 (not yet marked stable) does. Upgrading doesn't help. -(/home/david:$)-> ufed ESC pressed, changes not saved ufed crashes and produces the message above, no ncurses dialog comes up at all. > ESC pressed, changes not saved
That's not related to this bug report. The fact that it's even trying to show the dialog means it's able to read the files on your system to find out which flags you currently have enabled, while the "couldn't open use.defaults" message means ufed stopped even before that. It would probably be a good idea to report this as a new bug. If you do this, could you include the output of emerge --info on your system, as well as the version of dialog installed on your system?
Ok, I've filed a new bug report. See #70776. Regards, Tassilo Yes, the error looks different. It is due to the fact that the first reporter's profile's child-most directory had a make.defaults. The issue is still the same. *** This bug has been marked as a duplicate of 70345 *** can we mark ufed >= 0.35 stable ? |