[opam-devel] opam repository problems

Richard Mortier Richard.Mortier at nottingham.ac.uk
Sun Dec 8 14:07:54 GMT 2013


On 8 Dec 2013, at 14:02, Anil Madhavapeddy wrote:

> On 8 Dec 2013, at 13:31, Richard Mortier <Richard.Mortier at nottingham.ac.uk> wrote:
> 
>> is anyone else noticing anything?  from what i can currently observe, 
>> 
>> + opam.ocamlpro.org is quite out of date (seems to still give me omd.0.6.0 rather than omd.0.8.2 for example)
>> 
>> + opam.ocaml.org is fine for opam.1.1.0 but has a broken repository for opam.1.0.0
> 
...
> So the summary of all this is that you should be using OPAM 1.1, and only with opam.ocaml.org.  OPAM 1.0 is now deprecated.  I don't think we've done a particularly good job of communicating this on the OPAM website though, so I'd quite like to clarify that.  In particular, if someone was using opam.ocamlpro.com via a non-HTTP remote (e.g. git), then the repo redirect will not kick in.

don't think it's anything to do with non-http remotes. ok-- just to be clear then:

+ we're only interested in opam.1.1.0 *not* in opam.1.0.0

+ the correct default opam repo to use is http://opam.ocaml.org

?

in which case i'm fine, things build under those conditions. but i'll strip out the needless tests from the .travis.yml in at least a few repos; and could you update your ppa sometime so that the default opam remote is opam.ocaml.org rather than opam.ocamlpro.org please?

> Which packages are you blocked on atm?  Sylvain just fixed forge.ocamlcore.org, which also went down last night and broke some packages.

patches to ocaml-cow to support omd (requires omd >= 0.8 or so), required by patches to cowabloga and (soon perhaps) mirage-www (and right now, my new website though noone else need care about that :)

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.






More information about the opam-devel mailing list