Your message dated Thu, 3 May 2018 08:05:50 +0200
with message-id <20180503060550.dnteo37co3wvi...@xanadu.blop.info>
and subject line Re: Bug#897455: geos: FTBFS: configure: error: Could not find 
ruby interpreter.
has caused the Debian Bug report #897455,
regarding geos: FTBFS: configure: error: Could not find ruby interpreter.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
897455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geos
Version: 3.6.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> checking for swig... /usr/bin/swig
> checking for SWIG version... 3.0.12
> configure: SWIG executable is '/usr/bin/swig'
> configure: SWIG library directory is '/usr/share/swig3.0'
> checking for ruby... no
> configure: error: Could not find ruby interpreter.
>       tail -v -n \+0 config.log

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/geos_3.6.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
On 03/05/18 at 07:28 +0200, Sebastiaan Couwenberg wrote:
> Control: tags -1 unreproducible moreinfo
> 
> Hi Lucas,
> 
> Thanks for reporting this issue.
> 
> Unfortunately I cannot reproduce it in an up-to-date unstable chroot.
> 
> Can you still reproduce this issue?

Strange, maybe one of the dependencies changed to depend on 'ruby'
(which wasn't installed in my build). I'm closing the bug.

Lucas

--- End Message ---

Reply via email to