Bug 449024 – app-portage/ufed-0.40.2-r1 fails when FEATURES contains unknown value

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Marcin Mirosław 2012-12-28 11:43:07 UTC]

# grep "^FEATURES" /etc/make.conf
FEATURES="inv"

# ufed
Couldn't read FEATURES variable contains unknown value(s): inv
/var/db/pkg
Compilation failed in require at /usr/sbin/ufed line 9.
BEGIN failed--compilation aborted at /usr/sbin/ufed line 9.


Reproducible: Always

[Comment 1 Jeroen Roovers (RETIRED) 2012-12-28 15:06:15 UTC]

Is this a bug or a feature? :)

[Comment 2 Sven Eden 2013-01-07 12:09:52 UTC]

(In reply to comment #1)
> Is this a bug or a feature? :)

I think this is a bug, because portage displays such a message, too, but does not break on it. ufed should load after displaying the error message without further ado.
-> on my todo list.

[Comment 3 Sven Eden 2013-01-16 13:46:18 UTC]

I have just pushed a commit to git (please test via app-portage/ufed-9999) that changes the determination of the EPREFIX value.
As this value is determined asking portageq, its output is filtered to display warnings that do not endanger the wanted task.

To test I have put an invalid value in my mak.conf, and the result is now that ufed works as expected, but after exiting I can see:

-----

 # ufed
FEATURES variable contains unknown value(s): this_is_no_valid_feature
Cancelled, not saving changes.

-----

Please test and report whether this bug is fixed with the latest change.

[Comment 4 Marcin Mirosław 2013-01-16 14:46:52 UTC]

Works like a charm, thanks!

[Comment 5 Paul Varner (RETIRED) 2013-03-26 18:09:01 UTC]

Released in ufed-0.90_rc1

[Comment 6 Marcin Mirosław 2013-03-27 11:19:32 UTC]

Thanks for your hard work. Now I have to learn ufed again;)