lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Latest GUB error


From: Jonas Hahnfeld
Subject: Re: Latest GUB error
Date: Tue, 07 Apr 2020 16:55:17 +0200
User-agent: Evolution 3.36.1

Am Dienstag, den 07.04.2020, 15:18 +0100 schrieb Phil Holmes:
> We're getting further now.  Again, thanks for all your help so far.  This 
> time I get:
> 
> Traceback (most recent call last):
> File 
> "/home/gub/NewGub/gub/target/linux-64/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/scripts/build/out/install",
>  
> line 77, in <module>
> shutil.copy2 (f, dest)
> File "/home/gub/NewGub/gub/target/tools/root/usr/lib/python3.7/shutil.py", 
> line 266, in copy2
> copyfile(src, dst, follow_symlinks=follow_symlinks)
> File "/home/gub/NewGub/gub/target/tools/root/usr/lib/python3.7/shutil.py", 
> line 120, in copyfile
> with open(src, 'rb') as fsrc:
> FileNotFoundError: [Errno 2] No such file or directory: 'book_base.py'
> make[1]: *** [local-install-outfiles] Error 1
> make: *** [install] Error 2
> Command barfed: cd 
> /home/gub/NewGub/gub/target/linux-64/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable
>  
> && make TARGET_PYTHON=/usr/bin/python3 
> DESTDIR=/home/gub/NewGub/gub/target/linux-64/install/lilypond-2.21.0-root 
> install
> Traceback (most recent call last):
> File "bin/gub", line 231, in exceptional_build
> build (settings, options, files)
> File "bin/gub", line 227, in build
> b.build_source_packages (names)
> File "bin/../gub/buildrunner.py", line 334, in build_source_packages
> self.spec_build (spec_name)
> File "bin/../gub/buildrunner.py", line 262, in spec_build
> deferred_runner.execute_deferred_commands ()
> File "bin/../gub/runner.py", line 167, in execute_deferred_commands
> cmd.execute (self.logger)
> File "bin/../gub/commands.py", line 75, in execute
> ignore_errors=self.ignore_errors)
> File "bin/../gub/loggedos.py", line 93, in system
> raise misc.SystemFailed (m)
> SystemFailed: Command barfed: cd 
> /home/gub/NewGub/gub/target/linux-64/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable
>  
> && make TARGET_PYTHON=/usr/bin/python3 
> DESTDIR=/home/gub/NewGub/gub/target/linux-64/install/lilypond-2.21.0-root 
> install

Okay, so this is finally the foreseen problem in current master and
release/unstable when installing from a separate directory. This needs
a fix in LilyPond.
I think we can either revert the "offending" commit (which has
conflicts, see other thread on lilypond-devel) or take a minimum of 
https://codereview.appspot.com/549810043. I'd prefer the latter, but
that would require a rather quick consensus and pushing outside of the
usual review cycle.

Jonas

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]