I have to put at the head of every command LOCAL_LAYMAN=/var/lib/layman. eix-remote update * $LOCAL_LAYMAN must not be empty Layman version is 1.3.2-r2.
The layman.config module now misinterprets "python -c ..." as "layman -c ..." A workaround is in eix svn trunk (>=eix-0.20.3).
(In reply to comment #1) > The layman.config module now misinterprets "python -c ..." as "layman -c ..." > A workaround is in eix svn trunk (>=eix-0.20.3). I don't get a word. Anything I need to fix in layman? If so please open a new bug for it.
(In reply to comment #2) > > Anything I need to fix in layman? If so please open a new bug for it. I am not sure whether it is a bug in layman or python or just a (somewhere documented) change in behavior: eix-remote (and also eix-layman) received layman configuration data using commands like python -c "from layman.config import Config print Config()['storage']" (or 'make_conf' instead of 'storage'). For some reason, the (python) option -c is now considered by the module as a passed option which was not the case in earlier python/layman versions. As a workaround, I avoid now any options, i.e. next version of eix uses instead printf '%s\n%s\n' 'from layman.config import Config' \ "print(Config()['storage'])" | python -- I suppose that this will work with all versions of python/layman, so it is probably not necessary to change something in layman.
*** Bug 311111 has been marked as a duplicate of this bug. ***
0.20.3 is in the tree.