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

Bug#724215: marked as done (eliom: FTBFS: make[1]: *** No rule to make target `Makefile.config'. Stop.)



Your message dated Fri, 13 Dec 2013 09:13:28 +0100
with message-id <52AAC1A8.3060404@debian.org>
and subject line Re: Bug#724215: eliom: FTBFS: make[1]: *** No rule to make target `Makefile.config'.  Stop.
has caused the Debian Bug report #724215,
regarding eliom: FTBFS: make[1]: *** No rule to make target `Makefile.config'.  Stop.
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.)


-- 
724215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724215
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: eliom
Version: 3.0.3-1
Severity: serious
Tags: jessie sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20130922 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
>    dh_auto_clean
> make[1]: Entering directory `/«PKGBUILDDIR»'
> Makefile:1: Makefile.config: No such file or directory
> make[1]: *** No rule to make target `Makefile.config'.  Stop.
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> dh_auto_clean: make -j1 distclean returned exit code 2
> make: *** [clean] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/09/22/eliom_3.0.3-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 ---
Version: 3.0.3-2

Le 22/09/2013 19:58, David Suárez a écrit :
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> [...]

This is obviously fixed...

-- 
Stéphane

--- End Message ---

Reply to: