Bug 14925 - missing ocaml-deriving-ocsigen for install ocaml-deriving-ocsigen-devel
Summary: missing ocaml-deriving-ocsigen for install ocaml-deriving-ocsigen-devel
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker normal
Target Milestone: ---
Assignee: Malo Deniélou
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-01 13:33 CET by David GEIGER
Modified: 2015-02-03 22:47 CET (History)
2 users (show)

See Also:
Source RPM: ocaml-deriving-ocsigen
CVE:
Status comment:


Attachments

Description David GEIGER 2015-01-01 13:33:11 CET
Hi,

First one:

It seems that ocaml-deriving-ocsigen package was replaced by ocaml-deriving but there is always ocaml-deriving-ocsigen-devel present in repos Cauldron.

Try:

# LC_ALL=C urpmi ocaml-deriving-ocsigen-devel
A requested package cannot be installed:
ocaml-deriving-ocsigen-devel-0.5-4.mga5.x86_64 (due to unsatisfied ocaml-deriving-ocsigen[== 0.5-4.mga5])
Continue installation anyway? (Y/n) n
#


------------------------------------------------------------------------------
Second one:

Other problem is that ocalm-eliom need it to build properly and ocaml-eliom is still a part of packages that didn't build during mass rebuilds.




Reproducible: 

Steps to Reproduce:
Sander Lepik 2015-01-01 13:36:49 CET

CC: (none) => mageia
Assignee: bugsquad => pmdenielou

Comment 1 Sander Lepik 2015-01-01 14:06:54 CET
Marking as release blocker as it shows up on dependencies global report: http://check.mageia.org/cauldron/dependencies.html

Priority: Normal => release_blocker

Comment 2 Rémi Verschelde 2015-02-03 22:47:45 CET
Sander fixed this bug with http://svnweb.mageia.org/packages?view=revision&revision=813233 though that was as bogus as the bug itself IMO.
I've now pushed and submitted http://svnweb.mageia.org/packages?view=revision&revision=813279 which fixes the issue in a clean way, and makes sure the upgrade path is preserved.

For ocaml-eliom, I had a quick look but our very is very old, it's probably not compatible with the current ocaml stack. And I don't intend to try to update it to version 4.1 since I don't even know what ocaml is :-)

Status: NEW => RESOLVED
CC: (none) => remi
Resolution: (none) => FIXED


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