Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
This commit breaks dozens of opam build instructions, because OASISFormat 0.2 and 0.1 are not longer supported.
Kind of expected (unfortunately).
Now I think OPAM packages should be fixed because I will not continue to support 0.1 and 0.2 forever.
@fdopen can you list precisely the packages that need to be fixed and add a link to the "weather channel" to check everything is ok ?
Also the test dependencies are incorrect:
The nocrypto problem is a bug: look like the propagation of the of the
I have no tests covering this case.
Can you open a bug on the forge to report that ? (so that you'll get a
You can quickly fix it, in the meantime, by adding a constraint like (oasis
Reporting this kind of bug will be extremely useful to me, because I can
Le mer. 24 août 2016 à 23:36, Thomas Gazagnaire firstname.lastname@example.org
I have done a short review of the various packages that were broken with 0.4.7:
E: OASIS format version '0.2' is not supported.
E: OASIS format version '0.1' is not supported.
I need to go through all of the build logs to check all possible bugs, but it seems that most of the bugs are related to the new parser rather than dropping support for OASISFormat 0.1 and 0.2.
I went through the full list on:
Here are the list of errors:
I plan to submit a patch to make them conflict with oasis 0.4.7, that will make them buildable.