Add some more info to the 'Cannot chown a lockfile' message, since
authorZac Medico <zmedico@gentoo.org>
Sun, 15 Aug 2010 07:41:08 +0000 (00:41 -0700)
committerZac Medico <zmedico@gentoo.org>
Sun, 15 Aug 2010 07:41:08 +0000 (00:41 -0700)
it's being triggered on the buildbot.

pym/portage/locks.py

index 3685d8041be9b2100d5304ebee48166f647863db..4a86e5acbde1d9e7094d3f41190d8ee2957ab3e6 100644 (file)
@@ -88,9 +88,13 @@ def lockfile(mypath, wantnewlockfile=0, unlinkfile=0,
                                                        unlinkfile=unlinkfile, waiting_msg=waiting_msg,
                                                        flags=flags)
                                        else:
+                                               writemsg("%s: chown('%s', -1, %d)\n" % \
+                                                       (e, lockfilename, portage_gid), noiselevel=-1)
                                                writemsg(_("Cannot chown a lockfile: '%s'\n") % \
                                                        lockfilename, noiselevel=-1)
-
+                                               writemsg(_("Group IDs of current user: %s\n") % \
+                                                       " ".join(str(n) for n in os.getgroups()),
+                                                       noiselevel=-1)
                finally:
                        os.umask(old_mask)