Bug 1065447 - ocaml-ounit clash with ocaml 4.01.0 stdlib
Summary: ocaml-ounit clash with ocaml 4.01.0 stdlib
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ocaml-ounit
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-14 16:44 UTC by Jerry James
Modified: 2014-02-16 04:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-16 04:45:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jerry James 2014-02-14 16:44:56 UTC
Description of problem:
While trying to do a review (bug 1055398), a build attempt in a Rawhide mock environment failed like so:

File "_none_", line 1:
Error: Files /usr/lib64/ocaml/oUnit/oUnit.cmxa
       and /usr/lib64/ocaml/stdlib.cmxa
       make inconsistent assumptions over implementation Arg
Command exited with code 2.
make[2]: *** [ocaml] Error 10

Version-Release number of selected component (if applicable):
ocaml-ounit-1.1.2-7.fc21.x86_64

How reproducible:
Always

Steps to Reproduce:
1. fedora-review -b 1055398 -m fedora-rawhide-x86_64
2.
3.

Actual results:
The build fails due to an inconsistency between ocaml-ounit and the ocaml stdlib.

Expected results:
Successful build.

Additional info:

Comment 1 Richard W.M. Jones 2014-02-14 17:49:55 UTC
I think this happens because I patched the Arg module in
our OCaml with a not-quite-upstream patch:

http://caml.inria.fr/mantis/view.php?id=5197

This may have changed the md5 hash of the module (although my
intention was *not* to do that ...).  And more to the point,
why didn't the automatic dependency stuff pick that up?

In any case, a simple rebuild of ocaml-ounit should fix it:

http://koji.fedoraproject.org/koji/taskinfo?taskID=6531165

Comment 2 Michel Lind 2014-02-16 04:45:14 UTC
Works in Rawhide now, thanks!


Note You need to log in before you can comment on or make changes to this bug.