Your message dated Wed, 01 Jan 2014 00:10:20 +0100
with message-id <52c34edc.6020...@debian.org>
and subject line Re: Bug#713212: ocaml-deriving-ocsigen: FTBFS: cp: cannot stat
'debian/tmp//usr/lib/ocaml/deriving-ocsigen/pa_deriving_tc.cma': No such file
or directory
has caused the Debian Bug report #713212,
regarding ocaml-deriving-ocsigen: FTBFS: cp: cannot stat
'debian/tmp//usr/lib/ocaml/deriving-ocsigen/pa_deriving_tc.cma': 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 ow...@bugs.debian.org
immediately.)
--
713212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-deriving-ocsigen
Version: 0.3c-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_install --fail-missing
> cp: cannot stat
> 'debian/tmp//usr/lib/ocaml/deriving-ocsigen/pa_deriving_tc.cma': No such file
> or directory
> dh_install: cp -a
> debian/tmp//usr/lib/ocaml/deriving-ocsigen/pa_deriving_tc.cma
> debian/libderiving-ocsigen-ocaml-dev///usr/lib/ocaml/deriving-ocsigen/
> returned exit code 1
> make[1]: *** [override_dh_install] Error 2
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/ocaml-deriving-ocsigen_0.3c-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: 0.3c-3
Le 22/06/2013 14:11, Lucas Nussbaum a écrit :
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> [...]
This has been fixed a while ago...
--
Stéphane
--- End Message ---
