Re: [Lilypond-auto] Issue 2885 in lilypond: GUB currently fails to create tarballs

[lilypond]

Comment #2 on issue 2885 by address@hidden: GUB currently fails to  
create tarballs
http://code.google.com/p/lilypond/issues/detail?id=2885

OK, so it's definitely this commit:

https://github.com/gperciva/gub/commit/dd2f4077f5f818a6f689b0f4a795bacb92dcb8ae

The old command would have been:

python gub/with-lock.py --skip  
/home/gub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable.lock  
make -f lilypond.make cached-dist-check

and the new one after the commit above is:

PATH=/home/gub/gub/target/tools/root/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin  
python  
gub/with-lock.py --skip  
/home/gub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable.lock  
make -f lilypond.make cached-dist-check

Can anyone with build/python/unix understanding suggest why the latter  
command fails because of a failed import of a module (misc) which is in the  
same directory as the running module (logging.py) whereas the earlier one  
doesn't.  Suggested fix, anyone?