Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 876505 - app-portage/eix: /usr/bin/eix-layman fails with: line 166: $1: unbound variable
Summary: app-portage/eix: /usr/bin/eix-layman fails with: line 166: $1: unbound variable
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Michał Górny
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-10 13:52 UTC by tt_1
Modified: 2023-05-23 14:55 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
output from emerge --info (emerge-info,8.13 KB, text/plain)
2022-10-10 13:52 UTC, tt_1
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tt_1 2022-10-10 13:52:08 UTC
my version of app-portage/eix is 0.36.5, I emerged with: 

$ emerge -pv eix

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] app-portage/eix-0.36.5::gentoo  USE="nls sqlite -debug -doc" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB



I just wanted to make use of eix-layman, and all I got was this output: 

/usr/bin/eix-layman: line 166: $1: unbound variable

the eix-layman file is not a symlink to eix, and I clearly don't understand how its compiled or generated during compile, let alone from which files it is compiled.
Comment 1 tt_1 2022-10-10 13:52:56 UTC
Created attachment 823465 [details]
output from emerge --info
Comment 2 Martin Väth 2022-10-11 04:57:16 UTC
Thanks for reporting.
eix-layman requires an argument ("add" or "remove").
You can display the help text with "eix-layman help" or "eix-layman -h".

I agree that eix-layman should better display the help text as well if no argument is given instead of just displaying an unclear error message.

Will be fixed in 0.36.6, but release will probably wait for further changes.
Comment 3 Jack 2023-05-23 14:50:08 UTC
Should this be marked as resolved?
Comment 4 tt_1 2023-05-23 14:55:23 UTC
ah yes, it has been fixed in 0.36.6

thanks for the hint, and the fix of course