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

Bug#718155: marked as done (ocaml-config-file: FTBFS: Makefile:29: master.Makefile: No such file or directory)

Your message dated Sat, 18 Jan 2014 04:34:24 +0100
with message-id <2585065.PqgY6RZFtG@sephirot>
and subject line Builds ok
has caused the Debian Bug report #718155,
regarding ocaml-config-file: FTBFS: Makefile:29: master.Makefile: No such file or directory
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 owner@bugs.debian.org
immediately.)


-- 
718155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718155
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: ocaml-config-file
Version: 1.1-1
Severity: serious
Tags: jessie sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20130726 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):
>  fakeroot debian/rules clean
> dh clean --with ocaml
>    dh_testdir
>    debian/rules override_dh_auto_clean
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_auto_clean
> make[2]: Entering directory `/«PKGBUILDDIR»'
> Makefile:29: master.Makefile: No such file or directory
> ./config.status --recheck
> make[2]: ./config.status: Command not found
> make[2]: *** [config.status] Error 127

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/07/26/ocaml-config-file_1.1-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 --- 
Now builds ok, closing it.

--- End Message ---
Reply to: