Re: 2.20 plans.

[David Kastrup]

Federico Bruni <address@hidden> writes:

> Il giorno mar 16 ott 2018 alle 22:11, David Kastrup <address@hidden> ha
> scritto:
>> "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 ?
>>
>
> git head is invalid?
>
>    def _update_workdir_shallow (self, destdir):
>        branch = self.branch # branch is empty?
>        branch = 'master'
>        HEAD = self.checksum ()
>        if HEAD == 'invalid':
>            barf
>
> from https://github.com/gperciva/gub/blob/master/gub/repository.py#L702

Ok, so where do we go from here?  This sounds like Phil has set
something up wrong.  Missing environment variables or something?

-- 
David Kastrup