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

Bug#841542: marked as done (parmap: FTBFS: ocamlfind: Cannot mkdir /usr/local/lib/ocaml/4.02.3/parmap: Permission denied)

Your message dated Thu, 3 Nov 2016 15:39:55 +0100
with message-id <[🔎] CAK0OdpzScGxdnmastWDmGDO7ft6+NYBfZ6UDr1SYu+_NuhXWdg@mail.gmail.com>
and subject line Re: Bug#837674: parmap: FTBFS with bindnow and PIE enabled
has caused the Debian Bug report #837674,
regarding parmap: FTBFS: ocamlfind: Cannot mkdir /usr/local/lib/ocaml/4.02.3/parmap: Permission denied
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.)


-- 
837674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837674
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: parmap
Version: 1.0~rc7-1
Severity: serious
Tags: stretch sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> ocamlfind ocamlopt -shared -o parmap.cmxs bytearray_stubs.o setcore_stubs.o bytearray.cmx parmap_utils.cmx parmap.cmx
> ocamlfind remove parmap
> ocamlfind: [WARNING] No such directory: /usr/local/lib/ocaml/4.02.3/parmap
> ocamlfind install parmap META bytearray.cmi parmap_utils.cmi parmap.cmi setcore.cmi parmap.cma parmap.cmxa parmap.cmxs *.a *.mli bytearray_stubs.o setcore_stubs.o *.so
> ocamlfind: Cannot mkdir /usr/local/lib/ocaml/4.02.3/parmap: Permission denied
> Makefile:34: recipe for target 'install' failed
> make[2]: *** [install] Error 2

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/parmap_1.0~rc7-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 --- 
Hi,

2016-11-03 1:07 GMT+01:00 Mehdi Dogguy <mehdi@dogguy.org>:
> Hi,
>
> On 13/09/2016 14:12, Balint Reczey wrote:
>> During a rebuild of all packages in sid, your package failed to build on
>> amd64 with patched GCC and dpkg.
>>
>> The rebuild tested if packages are ready for a transition
>> enabling PIE and bindnow for amd64.
>>
>
> FWIW, I've tried to rebuild parmap in a clean Sid chroot and I am unable
> to reproduce the build failure. You can find attached my build log.
>
> Does it still fail for you?

No, it does build for me now.

Cheers,
Balint

>
> Regards,
>
> --
> Mehdi

--- End Message ---
Reply to: