lilypond-devel
[Top][All Lists]
Advanced

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

Re: 2.20 plans.


From: David Kastrup
Subject: Re: 2.20 plans.
Date: Tue, 16 Oct 2018 22:11:46 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

"Phil Holmes" <address@hidden> writes:

> I've been trying a GUB build today.  It's failed rather strangely.  At
> first I got:
>
> Command barfed: cd /home/gub/NewGub/gub/downloads/lilypond/git && git
> fetch git://git.sv.gnu.org/lilypond.git
> stable/2.20:refs/heads/git.sv.gnu.org/lilypond.git/stable/2.20
>
> Tail of log/gub.log >>>>>>>>
> *** Stage: download (lilypond, darwin-x86)
> invoking cd /home/gub/NewGub/gub/downloads/lilypond/git && git fetch
> git://git.sv.gnu.org/lilypond.git
> stable/2.20:refs/heads/git.sv.gnu.org/lilypond.git/stable/2.20
> fatal: Unable to look up git.sv.gnu.org (port 9418) (Name or service
> not known)
> Command barfed: cd /home/gub/NewGub/gub/downloads/lilypond/git && git
> fetch git://git.sv.gnu.org/lilypond.git
> stable/2.20:refs/heads/git.sv.gnu.org/lilypond.git/stable/2.20
>
>
> I thought that might be down to a network problem, so I tried the
> network and it looked OK so I ran the make again and this time I got:
>
>
> Tail of target/freebsd-x86/log/lilypond.log >>>>>>>>
> building package: freebsd-x86::lilypond
> *** Stage: download (lilypond, freebsd-x86)
> *** Stage: untar (lilypond, freebsd-x86)
> invoking cd /home/gub/NewGub/gub/downloads/lilypond/git && git fetch
> git://git.sv.gnu.org/lilypond.git
> stable/2.20:refs/heads/git.sv.gnu.org/lilypond.git/stable/2.20
> <<<<<<<< Tail of target/freebsd-x86/log/lilypond.log
>
> Traceback (most recent call last):
> File "bin/gub", line 233, in exceptional_build
> build (settings, options, files)
> File "bin/gub", line 229, 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 48, in execute
> buildspec.source.update_workdir (buildspec.expand ('%(srcdir)s'))
> File "bin/../gub/repository.py", line 699, in update_workdir
> self._update_workdir_shallow (destdir)
> File "bin/../gub/repository.py", line 707, in _update_workdir_shallow
> barf
> NameError: global name 'barf' is not defined
>
>
> Any thoughts of where to go from here?

"barf" sounds like an intentionally undefined function, "called" in
order to get a backtrace.

When I learnt programming, long long ago in the time of punch cards, my
mentor used "CALL HUGO" for this purpose.  Indeed this triggered a
_runtime_ error on the Fortran 77 compiler of the Cyber 175.

I guess this is the same trick, just for Python.  So now we have a
backtrace.  We just need to figure out what reason "barf" is getting
called for.  What's in line 707 of repository.py ?

-- 
David Kastrup



reply via email to

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