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

Bug#790819: marked as done (FTBFS: cannot stat 'debian/tmp//usr/lib/ocaml/netcamlbox': No such file or directory)



Your message dated Fri, 10 Jul 2015 15:43:14 +0200
with message-id <559FCBF2.7040602@debian.org>
and subject line Re: Bug#790819: FTBFS: cannot stat 'debian/tmp//usr/lib/ocaml/netcamlbox': No such file or directory
has caused the Debian Bug report #790819,
regarding FTBFS: cannot stat 'debian/tmp//usr/lib/ocaml/netcamlbox': 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.)


-- 
790819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790819
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: ocamlnet
Version: 3.7.3-4
Severity: serious

ocamlnet fails to build in unstable:

> sbuild (Debian sbuild) 0.64.1 (13 Oct 2013) on m400-c5n1.hlinux.usa.hp.com
...
>    debian/rules override_dh_install
> make[1]: Entering directory '/«PKGBUILDDIR»'
> dh_install --fail-missing -X.so.owner -Xmod_netcgi_apache.so
> cp: cannot stat 'debian/tmp//usr/lib/ocaml/netcamlbox': No such file or directory
> dh_install: cp --reflink=auto -a debian/tmp//usr/lib/ocaml/netcamlbox debian/libocamlnet-ocaml-dev//usr/lib/ocaml/ returned exit code 1
> make[1]: *** [override_dh_install] Error 2
> debian/rules:54: recipe for target 'override_dh_install' failed
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> debian/rules:25: recipe for target 'binary' failed
> make: *** [binary] Error 2

-- 
Martin Michlmayr
Linux for HP Helion OpenStack, Hewlett-Packard

--- End Message ---
--- Begin Message ---
Le 10/07/2015 15:05, Martin Michlmayr a écrit :
>>> Might it be the way the chroot was setup?
>>
>> Maybe. Are all virtual filesystems (in particular /dev/shm) mounted in
>> your chroot?
> 
> Sorry, that was not mounted (only /proc and /dev/pts) so feel free to
> close.

OK

-- 
Stéphane

--- End Message ---

Reply to: