When syncing an overlay with layman 1.0.8 to a server that was going slow, I ctrl+c out of it but it claimed success. Here is the output: * Running command "/usr/bin/svn update "/usr/portage/local/layman/initng""... svn: PROPFIND request failed on '/portage/gentoo' svn: PROPFIND of '/portage/gentoo': could not connect to server (https://svn.initng.org) * * Success: * ------ * * Successfully synchronized overlay "initng". Perhaps layman does not check the return status of SVN?
*** Bug 159052 has been marked as a duplicate of this bug. ***
If I'm reading the code correct, layman doesn't seem to check the return code of any call to sync(), even though the return code is sent back by overlay.cmd()'s call to os.system(). Patches are welcome ;)
Yep. I see that on line 182 of db.py in /usr/lib/python2.4/site-packages/layman. I don't know python but let me read a tutorial and see if i can solve this.
Created attachment 104712 [details, diff] Patch to check return codes of sync Very small patch to db.py in /usr/lib/python2.4/site-packages/layman/. All it does is check the return code and if its non 0. I looked and all, svn, rsync, and cvs code all use the cmd to execute their sync command, so it should work for all of them. I patched mine and its working fine.
Fixed in layman-1.0.9. The new version was added to my overlay (http://overlays.gentoo.org/dev/wrobel) and will be moved to the overlay soon. Thanks for the patch.
