Created attachment 271363 [details] emerge --info # layman --sync ALL * * Errors: * ------ * * Failed to sync overlay "gnome". * Error was: can only concatenate list (not "str") to list * * Failed to sync overlay "marduk". * Error was: run_command() takes exactly 2 arguments (5 given) This doesn't happen when downgrading to 1.4.1.
i can confirm this bug too.
This error didn't occur with 1.4.2 either.
*** This bug has been confirmed by popular vote. ***
Seems I forgot to run etc-update. After running etc-update, all fixed now. Leaving open for the time being.
Argh, I take that back. I was confused about which version of layman I had installed. The problem persists. Leaving open.
Commenting out the python compatibility patch gets layman working again.
I confirm. BTW, layman's error messages should give more details about failure - names of module and function, line number etc.
Sorry everyone, It was a communication error on our part. It turned out the compatibility patch pushed to the tree only contained my last commit. But it needed both of the last 2 commits for it to be complete and work correctly. Honest I tested it first before committing! I'm preparing a corrected patch and will post it here/get the tree updated asap. And I agree that the error messages suck. I only recently took over development/maintenance of layman. I did not do any development for the current codebase up to and including 1.4.2. Only the python2.5 compatibility fixes/breakage (oops) :(. For the current live ebuild I have been working on an extensive cleanout/re-write of the api. The error reporting is already much better. It is also faster and more flexible in it's potential use...
Created attachment 271407 [details, diff] corrected patch
+*layman-1.4.2-r2 (28 Apr 2011) + + 28 Apr 2011; Jeremy Olexa <darkside@gentoo.org> -layman-1.4.2-r1.ebuild, + +layman-1.4.2-r2.ebuild, files/layman-1.4.2-python-compatbility-fix.patch: + Revision bump to fix broken sync function, bug 365123. New patch by Brian + Dolbec Close the bug when you see fit :)
patch seems to work fine now. this report can be close as resolved. thanks to @ll
Thanks guys!