Re: [opam-devel] More useful tags for Docker images

Apologies for the delayed reply to this suggestion. I'm currently reworking the opam2-based images and may actually remove the point releases entirely from the tag name in the new images. The reasoning is that we only ever test the latest point release of a given major release. In the new sch

[opam-devel] GitHub PR compiler switches now have their own remote

Dear all, I would like to draw your attention to a rearrangement of the opam-repository to streamline the number of compiler variants that are available by default: https://discuss.ocaml.org/t/opam-compiler-prs-are-migrating-to-their-own-remote/905 If you were using the "opam switch 4.06.0+pr9

Re: [opam-devel] [Caml-list] [rfc] deprecating opam 1.2.0

On 2 Jun 2017, at 11:09, Anil Madhavapeddy wrote: > > [ this is cross-posted from > https://discuss.ocaml.org/t/rfc-deprecating-opam-1-2-0/332 ] > > This is all for remaining users of OPAM 1.2.0, to see if it can be actively > deprecated in favour of OPAM 1.2.2 and hig

[opam-devel] [rfc] deprecating opam 1.2.0

[ this is cross-posted from https://discuss.ocaml.org/t/rfc-deprecating-opam-1-2-0/332 ] This is all for remaining users of OPAM 1.2.0, to see if it can be actively deprecated in favour of OPAM 1.2.2 and higher. ### Why deprecate opam 1.2.0 OPAM 1.2.0 was released in October 2014, and saw rap

[opam-devel] Fwd: [MirageOS-devel] opam-tagger

fyi > Begin forwarded message: > > From: Anil Madhavapeddy > Subject: [MirageOS-devel] opam-tagger > Date: 13 January 2017 at 14:30:24 GMT > To: mirageos-devel > > In the spirit of Mindy's upperbound-constrainer, I have published a simple > command line

Re: [opam-devel] ocamlbuild 0.10.1 missing from opam-repo?

Dear Daniel, Thanks, I'll revert the binary ocamlbuild 0.10.1 package for now. regards Anil > On 6 Jan 2017, at 15:33, Daniel Bünzli wrote: > > Both 10.0 and 10.1 were retracted. > > https://github.com/ocaml/opam-repository/pull/8157 > https://github.com/ocaml/opam-repository/pull/8156 > > B

[opam-devel] ocamlbuild 0.10.1 missing from opam-repo?

Dear all (but particularly Gabriel), Is there a reason that ocamlbuild.0.10.1 is missing from ocaml/opam-repository? I've just pulled up Alpine 3.5's ocamlbuild to that version, but installation is failing since there is no corresponding package in the OPAM repo for the preinstalled version. I

Re: [opam-devel] opam getting compiler version wrong

You can run "opam admin upgrade-format" to upgrade the repository, but I'm not sure of how to convert individual `opam` files. This seems like it would be useful in order to upgrade working repositories for pinning purposes... Anil > On 7 Dec 2016, at 21:52, Ashish Agarwal wrote: > > Seems t

Re: [opam-devel] [ocaml-infra] expiration SSL certificate

On 13 Sep 2016, at 10:31, Michael Grünewald wrote: > > >> On 13 Sep 2016, at 11:26, Anil Madhavapeddy wrote: >> >> On 13 Sep 2016, at 10:15, Daniel Bünzli wrote: >>> >>> Had a look at this. It seems rather toyish at the moment and makes me &

Re: [opam-devel] [ocaml-infra] expiration SSL certificate

On 13 Sep 2016, at 10:15, Daniel Bünzli wrote: > > On Tuesday 13 September 2016 at 10:51, Anil Madhavapeddy wrote: > >> There is an ocaml-acme client under development at: >> https://github.com/mmaker/ocaml-acme > > Had a look at this. It seems rather toyish at the

Re: [opam-devel] [ocaml-infra] expiration SSL certificate

On 10 Sep 2016, at 15:42, Xavier Leroy wrote: > > On 09/07/2016 04:21 PM, Ashish Agarwal wrote: >> IIRC, this was particularly relevant for the opam sub-domain, so cc-ing the >> opam-devel list. Can any opam dev please confirm. If it is still needed, we >> should act quick to update this. > > I'

Re: [opam-devel] deprecating opam 1.2.0

(not had time to investigate). -a > On 7 Jul 2016, at 11:15, Anil Madhavapeddy wrote: > > CCing Stephane Glondu -- would it be possible to request a backport of 1.2.2 > to Debian Stable? It's the last major distro distributing the older version > of OPAM, and it's

Re: [opam-devel] deprecating opam 1.2.0

CCing Stephane Glondu -- would it be possible to request a backport of 1.2.2 to Debian Stable? It's the last major distro distributing the older version of OPAM, and it's an increasingly difficult maintenance burden for us. regards, Anil > On 7 Jul 2016, at 07:50, Sylvain Le Gall wrote: > >

Re: [opam-devel] opam 2 containers/building toplevel

> On 1 Jun 2016, at 15:29, David Allsopp wrote: > > Anil Madhavapeddy wrote: >>> On 31 May 2016, at 14:36, Louis Gesbert >> wrote: > > > >>> The issue with `make lib-ext` may be that `opam-admin.top` can't find >>> the proper

Re: [opam-devel] opam 2 containers/building toplevel

> On 31 May 2016, at 14:36, Louis Gesbert wrote: > > Le mardi 31 mai 2016, 14:03:30 Anil Madhavapeddy a écrit : >> I'm just building Docker containers for the OPAM 2 master tree to sit >> alongside the existing 1.x containers. The build currently uses the >>

[opam-devel] opam 2 containers/building toplevel

I'm just building Docker containers for the OPAM 2 master tree to sit alongside the existing 1.x containers. The build currently uses the builtin libraries (make lib-ext), but this does not build the admin scripts for some reason. The admin scripts are needed for transitioning the 1.x repo to

Re: [opam-devel] [RFC] OPAM files as *the* OCaml package metadata format

On 13 Apr 2016, at 15:27, Daniel Bünzli wrote: > > Hello, > > A lot of the things I envision for the gradual simplification of the OCaml > build and package eco-system involves using OPAM files as the pivotal package > metadata file format (Louis, I really need these x- fields for playing w

Re: [opam-devel] docker hub update?

> On 11 Apr 2016, at 13:19, Grégoire Henry wrote: > > Hi Anil, > >> To fix this and address every usecase, I'd like to break up the container >> layers to be more fine-grained: >> >> - ocaml/ocaml - remains as it is right now >> - ocaml/opam-base - provides an installed OPAM binary, but _not_

Re: [opam-devel] docker hub update?

On 8 Apr 2016, at 16:51, Török Edwin wrote: > > Hi, > > How often are the ocaml/opam docker containers rebuilt and what determines > the build order? Hi Edwin, The Docker packages up on ocaml/opam are still somewhat experimental, so please do bear with me as I rearrange things around to make

Re: [opam-devel] more committers needed ?

On 30 Mar 2016, at 12:15, Hannes Mehnert wrote: > > uhm, this is very much into dreamland right now (since the first step, > of signing integration isn't done yet)... it's useful to figure out the workflow for people such that it'll actually get adoption... >

Re: [opam-devel] more committers needed ?

That actually sounds like the perfect workflow for signing... if there was some way to sign it (perhaps keybase.io via JavaScript) without a CLI, it would be much more widely adopted. -anil > On 30 Mar 2016, at 12:02, Louis Gesbert wrote: > > Note that it would become more complicated with ou

Re: [opam-devel] more committers needed ?

Hi Cheng, The OPAM tool indeed supports this model, but the automation infrastructure isn't fully written and deployed yet. There are various tools in-flight that do portions of this, but none exist that poll the --dev repository (e.g. for a new GitHub release) and autocreate a PR. I think th

[opam-devel] Fwd: [MirageOS-devel] ounit dependency failing for mirage-xen package

Does anyone have time to check the forge distfiles to see if they've been altered maliciously? I see this in some builds: /home/opam/.opam/packages.dev/ounit.2.0.0/ounit-2.0.0.tar.gz: - 2e0a24648c55005978d4923eb4925b28 [expected result] - 0f4f7cf8741d98cb419e45cc69962

Re: [opam-devel] build bot monitoring the opam-repository

On 23 Mar 2016, at 11:06, Fabrice Le Fessant wrote: > > Hi Anil, > > On Wed, Mar 23, 2016 at 11:53 AM Anil Madhavapeddy <mailto:a...@recoil.org>> wrote: > The build bot looks like it could also benefit from the container > infrastructure, since that takes care

Re: [opam-devel] build bot monitoring the opam-repository

Hi Fabrice, Thanks for releasing this; it looks very useful! The build bot looks like it could also benefit from the container infrastructure, since that takes care of depexts for a number of distributions. Before I look further at this, I just wanted to confirm that the licensing of the buil

Re: [opam-devel] IRILL cloud solver down?

On 24 Feb 2016, at 16:06, Grégoire Henry wrote: > >> Thanks, it seems to be back up again, so I'm restarting the CI jobs. >> Is the configuration of the server available so I can set it up as a >> local Docker container alongside the CI runs? We can spin up around >> 3000 containers simultaneous

Re: [opam-devel] IRILL cloud solver down?

On 24 Feb 2016, at 15:44, Grégoire Henry wrote: > > Hi Anil, > > The service only answers to POST request, hence the 404 you hit. Good point! > Otherwise, the server seems up and running. > > Our logs report some network instability though. Thanks, it seems to be back up again, so I'm res

[opam-devel] IRILL cloud solver down?

Good afternoon, Who maintains the IRILL cloud solver service? It appears to be giving a 404 now, which is disabling a lot of OPAM installs on distributions without a native port (OpenBSD, RedHat, CentOS, Alpine and Fedora among others). ~ $ curl -vv http://cudf-solvers.irill.org/cudf.bz2?crite

Re: [opam-devel] OPAM Dockerfiles set OPAMSWITCH

On 23 Feb 2016, at 15:00, David Sheets wrote: > > On Tue, Feb 23, 2016 at 12:33 PM, Anil Madhavapeddy wrote: >> On 23 Feb 2016, at 12:28, David Sheets wrote: >>> >>> The Docker containers described by >>> https://github.com/ocaml/opam-dockerfiles som

Re: [opam-devel] OPAM Dockerfiles set OPAMSWITCH

On 23 Feb 2016, at 12:28, David Sheets wrote: > > The Docker containers described by > https://github.com/ocaml/opam-dockerfiles somehow set the OPAMSWITCH > environment variable. I haven't been able to find where or why this > variable has been set and it causes many opam commands to be more > h

Re: [opam-devel] Please don't DoS the opam-repository

It's the free service, and so it's rate throttled by "reasonable use". In general we should avoid spamming the repository with a ton of requests to avoid causing Travis a surge. However, the model that you used is the right one, since it triggers an individual installation of each package rath

Re: [opam-devel] current opam-repository policy : who can modify a package description

On 22 Feb 2016, at 16:39, Hannes Mehnert wrote: > > On 02/22/16 05:31 PM, Anil Madhavapeddy wrote: >> Interesting idea -- so this would mean that OPAM has to remap >> upstream versions into something that is a semantic version. >> >> Does Elm eliminate this by m

Re: [opam-devel] current opam-repository policy : who can modify a package description

On 22 Feb 2016, at 16:23, Hannes Mehnert wrote: > > When a new release of any dependency is issued, this might be > incompatible with earlier versions (unfortunately we don't enforce > semantic versioning, afaik elm does this and opam should adapt). Interesting idea -- so this would mean that OP

Re: [opam-devel] current opam-repository policy : who can modify a package description

On 22 Feb 2016, at 15:42, Gabriel Scherer wrote: > > For ocamlbuild, I have written in the release How-to (the description > of things that have to be done when creating a new release) that the > upstream opam file of the last existing release should be checked for > packaging-policy changes: >

Re: [opam-devel] mailing liste for opam-repo maintainers

On 22 Feb 2016, at 15:41, David Allsopp wrote: > > No they would not – getting people on the conversation thread of a PR is > vastly superior; it groups the information and discussion in the place where > it’s merged and archives it there. I have certainly had to bisect > opam-repository befor

[opam-devel] Diplomat: NSDI paper on project community repositories

https://isis.poly.edu/~jcappos/papers/kuppusamy_nsdi_16.pdf Mentions the work that Hannes and Louis did on the TUF/OPAM design, and also rounds up the lessons from the other language communities as well. -Anil ___ opam-devel mailing list opam-devel@lis

Re: [opam-devel] more committers needed ?

On 17 Feb 2016, at 15:12, Thomas Gazagnaire wrote: > > Hi, > >>If there is some need to help managing PRs to the opam-repository, >> Grégoire Henry (OCamlPro-Henry on Github) and myself (lefessan on Github) >> are volunteers to spend some time doing it. > > I think that's a great idea! Th

Re: [opam-devel] [opam-dockerfiles] Bytecode only switches

On 8 Feb 2016, at 22:07, Daniel Bünzli wrote: > > Having seen a worrying trend of people submitting package with ad-hoc > installers made out of Makefile targets that will fail in various fashions on > more constrained switches, I think it would be good to have at least one > distribution with

Re: [opam-devel] odd error with aspcud on alpine linux

203 maybe related? > > hannes > > On 02/ 1/16 12:01 PM, Anil Madhavapeddy wrote: >> I've been porting OPAM to Alpine Linux, and have some very odd errors with >> Aspcud that I was hoping someone could help with. The solver pieces are all >> compiled

[opam-devel] odd error with aspcud on alpine linux

I've been porting OPAM to Alpine Linux, and have some very odd errors with Aspcud that I was hoping someone could help with. The solver pieces are all compiled and should have the right versions, but fail with an inconsistency error. To reproduce it, you need Docker and: $ docker run -ti ocam

Re: [opam-devel] Using binaries

On 22 Jan 2016, at 05:47, Louis Gesbert wrote: > > Le vendredi 22 janvier 2016, 08:34:34 Gabriel Scherer a écrit : >> I would be interested in some more information on this. This seems very >> simple as you say it, but I had not thought about the fact that OPAM >> already has the capacities to ac

Re: [opam-devel] Opam license bug

ompiler tools for commercial closed source use, and extending it to cover OPAM is the only route I see to getting a commercially friendly OPAM license for industrial users in the short term. -Anil > > Mark > >> On 19 January 2016 at 14:27, Anil Madhavapeddy wrote: >> On 19

Re: [opam-devel] Opam license bug

On 19 Jan 2016, at 14:17, Fabrice Le Fessant wrote: > > On Tue, Jan 19, 2016 at 9:47 AM Daniel Bünzli > wrote: > 3. I'm perfectly fine if opam stays with the LGPL. I'm not however fine with > the added CLA. > > I must repeat at this point that, as written i

Re: [opam-devel] [ANN] opam-fmt 1.0

{>= "1.3.1"} >>> # Included from _opam file >>> "conf-gsl" >>> ] >> >> I don't know what this comment means. >> >> packages/lz4/lz4.1.0.0/opam: >>> depexts: [ >>> [["debian"] ["lib

Re: [opam-devel] [ANN] opam-fmt 1.0

Thanks for this Gabriel! Quick notes: - I would really like opam-fmt to be lossless, so preserving comments seems like an extension that we should implement. Ideally everyone can just call it on their packages without thinking about it. - Having a bot regularly go through and reformat the en

Re: [opam-devel] OPAM for ubuntu 15.10

uis A. wrote: > > Hi Anil, > > I'm sorry, i should have checked that before writing. Thank you! > > Regards, > > Luis > > 2015-11-10 16:07 GMT+00:00 Anil Madhavapeddy <mailto:a...@recoil.org>>: > Hi Luis (+CC OPAM/Mirage lists as FYI), > >

Re: [opam-devel] OPAM for ubuntu 15.10

Hi Luis (+CC OPAM/Mirage lists as FYI), I've uploaded OCaml 4.02.3 and OPAM 1.2.2 PPA builds for Wily to Launchpad, where they're building in the experimental repository. Once that's completed (which takes a while due to the ARM builds), I will move them over to the stable PPAs. Note that OPA

Re: [opam-devel] opam does not uninstall menhir properly

Thanks -- the uninstall can be fixed in the already-released versions (by adding the `rm` lines into the `remove` field in the `opam` file), and ideally the upstream would fix the actual Makefile problem. I'm CCing the author, Francois Pottier to this mail. Anil > On 20 Oct 2015, at 23:54, Sé

Re: [opam-devel] distfiles for ocaml.janestreet.com need an SSL upgrade

> On 5 Oct 2015, at 01:50, Louis Gesbert wrote: > >> Louis, this manifests as a hard-to-debug error, since the curl command line >> doesn't seem to get output anywhere (even when using OPAMDEBUG=1). Is there >> some other way than modifying the OPAM source code to see all the commands >> that a

Re: [opam-devel] depexts homebrew taps

command. It could be possible to > install the dev version as a one-shot, without pinning, but I don't think > that would be a good idea, since opam will likely want to downgrade it on any > later upgrade or if needing recompilation... > >> - Anil Madhavapeddy, 04/10/2015

Re: [opam-devel] depexts homebrew taps

On 3 Oct 2015, at 11:53, Daniel Bünzli wrote: > > Le jeudi, 1 octobre 2015 à 17:59, Anil Madhavapeddy a écrit : >> [ ["osx" "homebrew"] ["tap/package"] ] >> >> In fact, would that just work as-is? > For the record, yes it does. It seem

[opam-devel] distfiles for ocaml.janestreet.com need an SSL upgrade

(x-posting to opam-devel as an fyi in case anyone else runs into this) Using OSX 10.11 results in an SSLv3 error from the upstream distfile server on ocaml.janestreet.com. Could it please be reconfigured to use TLS 1.0 or higher? Workaround is to "brew install wget", which is less secure out of

Re: [opam-devel] depexts homebrew taps

On 1 Oct 2015, at 17:20, Daniel Bünzli wrote: > > Hello, > > Is it possible to specify packages living in homebrew taps in the depext > field of an opam package ? Not taps, just the main Homebrew. However, this should be easy enough to add by doing a bit of parsing of the package name I g

Re: [opam-devel] [MirageOS-devel] Managing $PKG_CONFIG_PATH in opam

On 15 Sep 2015, at 12:50, Tim Cuthbertson wrote: > > On Tue, Sep 15, 2015 at 12:08 PM, Louis Gesbert > wrote: >> >>> I think we could definitely use an answer to pkg-config management, >>> but not one that's entwined into the core of OPAM itself. If something >>> could be figured out that fits

Re: [opam-devel] [MirageOS-devel] Managing $PKG_CONFIG_PATH in opam

> On 14 Sep 2015, at 15:05, Thomas Leonard wrote: > > On 14 September 2015 at 14:36, Anil Madhavapeddy wrote: >> On 13 Sep 2015, at 14:07, Thomas Leonard wrote: >>> >>> On 12 September 2015 at 08:49, Tim Cuthbertson wrote: >>>> On the MirageOS

Re: [opam-devel] [MirageOS-devel] Managing $PKG_CONFIG_PATH in opam

On 13 Sep 2015, at 14:07, Thomas Leonard wrote: > > On 12 September 2015 at 08:49, Tim Cuthbertson wrote: >> On the MirageOS mailing list, I submitted some patches[0] to make some >> mirage libraries build without assuming a strict `opam` destination >> directory layout. Mainly this was about th

Re: [opam-devel] What context do install an remove run in?

On 6 Sep 2015, at 19:49, Malcolm Matalka wrote: > > This is unclear to be from the documentation, but what context to the > commands `install` and `remove` sections of an opam file run in? I > would assume `install` runs in the directory of the built source, but > does `remove` have that same gu

Re: [opam-devel] Container based Travis CI service

Thanks for posting this to the list, Michael. We definitely need to do something about Travis, since the legacy infrastructure is failing regularly with network timeouts. If I understand it right, it won't be suitable for completely replacing depexts, since they specify OS dependencies for binary

Re: [opam-devel] opam publish package name

On 27 Aug 2015, at 05:57, Louis Gesbert wrote: > >> - Anil Madhavapeddy, 26/08/2015 18:49 - >> One thing I noticed is that the automatic plugin installation doesn't >> play well with non-interactivity (e.g. -y), btw. > > It should work with `OPAMYES=1` ; it'

Re: [opam-devel] opam publish package name

On 19 Aug 2015, at 11:04, Fabrice Le Fessant wrote: > > On Wed, Aug 19, 2015 at 11:56 AM, Louis Gesbert > wrote: >>> package, preventing "opam-cache", etc.), either to reserve names for >>> possible plugins ("search", "file", "git", etc). >> >> "search" is already an opam command :) > > Is it

Re: [opam-devel] opam publish package name

Yeah, after some thought I agree with you and Fabrice. Even though it'll take a few years to percolate through, having the right semantics in the core tool is more important than a transitionary period. It wont cost much to maintain two copies of important plugins. One thing I noticed is that th

Re: [opam-devel] user-setup

; > > On Wed, Aug 26, 2015, 10:49 AM Anil Madhavapeddy <mailto:a...@recoil.org>> wrote: > I didn't quite understand this last point, as a non-Emacser. What sort of > breakage to existing packages cause these Emacs errors? What tests would > make sense as part of a

Re: [opam-devel] user-setup

I didn't quite understand this last point, as a non-Emacser. What sort of breakage to existing packages cause these Emacs errors? What tests would make sense as part of a pull request to detect these? -anil > On 24 Aug 2015, at 16:25, Yaron Minsky wrote: > > Great. > > In addition, I wonde

Re: [opam-devel] opam publish package name

> On 18 Aug 2015, at 06:09, Fabrice Le Fessant > wrote: > > On Mon, Aug 17, 2015 at 6:34 PM, Anil Madhavapeddy wrote: >> Sounds fine to me. It's too late to enforce the "opam-" prefix in the >> package name unfortunately. > > Why is it too la

Re: [opam-devel] opam publish package name

publish.0.3.1 > - make publish conflict with earlier opam-publish versions > > This way an `opam upgrade` can pick up the name change. > > We can also, of course, keep an alias. > >> - Anil Madhavapeddy, 05/08/2015 16:43 - >> I notice that "opam publish" does

Re: [opam-devel] openbsd ocaml 4.02.3 + opam 1.2.2 upgrade

On 14 Aug 2015, at 15:40, Anil Madhavapeddy wrote: > > On 3 Aug 2015, at 18:58, Anil Madhavapeddy wrote: >> >> This rather large ports diff does an update of the OCaml ports to 4.02.3: >> http://www.recoil.org/~avsm/openbsd-patches/ocaml-4.02.3.patch.txt >> >&

Re: [opam-devel] openbsd ocaml 4.02.3 + opam 1.2.2 upgrade

On 3 Aug 2015, at 18:58, Anil Madhavapeddy wrote: > > This rather large ports diff does an update of the OCaml ports to 4.02.3: > http://www.recoil.org/~avsm/openbsd-patches/ocaml-4.02.3.patch.txt > > It bumps the REVISION of most of the untouched OCaml ports since binary

Re: [opam-devel] updating the ocaml ppa to 4.02.3

On 11 Aug 2015, at 09:40, Thomas Gazagnaire wrote: > >> >> In order to properly fix this, I've started to merge the scripts we use in >> opam-repository and the ones in ocaml-travisci-skeleton. See >> https://github.com/ocaml/ocaml-travisci-skeleton/pull/61 >> >> Comments are welcome. > > T

Re: [opam-devel] updating the ocaml ppa to 4.02.3

On 10 Aug 2015, at 14:16, Thomas Gazagnaire wrote: > >>> >>> I think you forgot to update camlp4 on the ppa, so the Travis CI scripts >>> trying to compile 4.02 are broken: >>> >>> https://travis-ci.org/mirage/ocaml-git/jobs/74897466 >> >> Not forgotten -- there's no way to do an atomic upgra

Re: [opam-devel] updating the ocaml ppa to 4.02.3

On 10 Aug 2015, at 14:01, Thomas Gazagnaire wrote: > >> I've updated the Ubuntu OCaml PPA in the ppa-opam-experimental tree to OCaml >> 4.02.3, Camlp4 4.02+6 and OPAM 1.2.2 built against this. I'll be rolling >> this out to the OCaml 4.02.x branches soon, so Travis will start picking it >> up

Re: [opam-devel] freebsd opam port update

Thanks Joris, much appreciated! We should be able to hook up FreeBSD bulk building into the OPAM repository test bots soon. -anil > On 7 Aug 2015, at 04:55, Joris Giovannangeli wrote: > > Hi Anil, > > thank you for your suggestions, i've submitted a problem report to the > port tracker : > ht

[opam-devel] freebsd opam port update

Hi Joris, Would it be possible to modify the FreeBSD OPAM 1.2.2 port's dependencies? - ocaml-camlp4 should be included by default, since it's necessary for the correct operation of the system compiler. - aspcud should also be on by default, since it's the recommended solver. The internal one is

[opam-devel] opam publish package name

I notice that "opam publish" doesn't autoinstall the plugin (as occurs with depext). This is because the OPAM package name is "opam-publish" instead of simply "publish". Should we rename it, or duplicate the package metadata so that the autoinstallation works? -anil __

[opam-devel] openbsd ocaml 4.02.3 + opam 1.2.2 upgrade

This rather large ports diff does an update of the OCaml ports to 4.02.3: http://www.recoil.org/~avsm/openbsd-patches/ocaml-4.02.3.patch.txt It bumps the REVISION of most of the untouched OCaml ports since binary compat is not preserved across OCaml revisions. Any tests on non-x86 would be appre

[opam-devel] updating the ocaml ppa to 4.02.3

I've updated the Ubuntu OCaml PPA in the ppa-opam-experimental tree to OCaml 4.02.3, Camlp4 4.02+6 and OPAM 1.2.2 built against this. I'll be rolling this out to the OCaml 4.02.x branches soon, so Travis will start picking it up by default once that rebuild happens. This means that we won't ha

[opam-devel] fwd: Cron job update-opam failed on opam.ocaml.org

Looks like recent opam-lib may have broken the cron jobs. > Begin forwarded message: > > ocamlfind ocamlopt -package > unix,extlib,re,re.emacs,re.str,re.perl,re.pcre,re.glob,cmdliner,ocamlgraph,cudf,dose3,jsonm > -c -g -w +a-4-9-32-41-44-45-48 -I core -I solver -I repositories -I client > -I c

Re: [opam-devel] opam.ocaml.org

n 2015, at 01:27, Louis Gesbert wrote: > > No issue that I can think of on my part! > > Thanks! > >> - Anil Madhavapeddy, 19/06/2015 16:43 - >> Any objections if I upgrade the opam.ocaml.org VM to Debian Jessie from >> Wheezy? I've taken a snapshot of

[opam-devel] opam.ocaml.org

Any objections if I upgrade the opam.ocaml.org VM to Debian Jessie from Wheezy? I've taken a snapshot of the current setup in Rackspace. We need a newer Nginx to support gzip_static, which in turn is needed since we've already hit the 256GB limit for the /builds logs. -anil ___

Re: [opam-devel] release scripts

On 11 Jun 2015, at 17:44, Thomas Gazagnaire wrote: > >> Does this also do a GitHub release, or just create the tag upstream? > > It just create the tag. Creating the GitHub release would imply dealing with > diffs in CHANGES files and will require talking to the GitHub API, which is > not tota

Re: [opam-devel] release scripts

On 11 Jun 2015, at 09:25, Thomas Gazagnaire wrote: > > I've tried to "clean-up" some of my release scripts, that I published on > GitHub. It is a mix between opam-publish and my own conventions, so I'm not > sure it very useful to someone else than me. Feel free to clone and to adapt > to your

Re: [opam-devel] regular bulk builds: now with HTML output!

On 30 May 2015, at 19:19, Thomas Gazagnaire wrote: > >> On 01/08/2015 07:52 PM, Anil Madhavapeddy wrote: >>> http://www.recoil.org/~avsm/opam-bulk/ (temporary URL) >> >> This is very nice and useful ! How can we contribute to opam-bulk project ? > > This

Re: [opam-devel] [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

On 20 May 2015, at 11:43, Martin Lucina wrote: > > On Wednesday, 20.05.2015 at 12:02, Martin Lucina wrote: >> Getting further through the list of Mirage dependencies, trying to get >> sexplib building for rumprun hits another different problem with OASIS: > > *facepalm* Ok, sorry, this was cause

Re: [opam-devel] Using the new travis containers

> On 14 May 2015, at 16:42, Thomas Gazagnaire wrote: > >>> opam pin add hdhcp >>> opam install -e ubuntu hdhcp > > opam list -e ubuntu dhcp --short But how do I get it recursively? $ opam list -e ubuntu hdhcp --short --rec $ opam list -e ubuntu ctypes-foreign libffi-dev An

Re: [opam-devel] Using the new travis containers

On 14 May 2015, at 13:30, Thomas Leonard wrote: > > Travis is currently migrating over to using containers for builds. > These start much faster than the old full VMs, but they don't give you > root access. This means that you can't use sudo to install packages > and should instead list them in y

Re: [opam-devel] ANNOUNCE: OWS, the Opam Wheather Service

Yes, this is excellent! I'm not entirely sure how to interpret the data as a package maintainer yet, but this much testing cannot be a bad thing :-) Is the data available as a JSON or other structured feed? It would make it easier to consume rather than clicking through the web page. Just curio

[opam-devel] opam 1.2.2rc2 -> release?

I've gone ahead somewhat optimistically and uploaded rc2 as OPAM-1.2.2 release to the Ubuntu PPA experimental archive. Louis, if you can give me the green light, I'll move it over to the stable repositories. -anil ___ opam-devel mailing list opam-devel

Re: [opam-devel] opam2{rpm,deb}

On 20 Mar 2015, at 23:22, Török Edwin wrote: > > Hi, > > [On Anil's suggestion I'm moving the discussion to opam-devel. > TL;DR: I am about to start writing opam2{rpm,deb} for my package and its > dependencies. Does anyone else need such a tool or want to help?] Apologies for the delay replyin

Re: [opam-devel] Problem with ocaml.janestreet.com TLS cert?

This is a broken `curl` command on base OSX. Try switching to wget with: export OPAMFETCH=wget CCing Yaron Minsky and Jeremie Diminio about the Jane Street setup -- this is likely a result of disabling SSLv3 due to the POODLE attack. -anil > On 18 Apr 2015, at 16:32, Richard Mortier > wr

Re: [opam-devel] OPAM 1.2.2~rc is out

CCing Thomas Leonard in case he's not on this list -- could you confirm if the new OPAMEXTERNALSOLVER is sufficient for 0install packaging now? (it should just take a path). https://github.com/ocaml/opam/issues/2085 -anil > On 16 Apr 2015, at 09:41, Louis Gesbert wrote: > > This is mostly a bu

Re: [opam-devel] opam bulk builds linked in experimentally to opam.ocaml.org

On 6 Apr 2015, at 17:19, Christophe Troestler wrote: > >> On Fri, 3 Apr 2015 14:35:20 +0100, Anil Madhavapeddy wrote: >> >> I've left the OPAM bulk builder rsyncing to a new logging volume on >> opam.ocaml.org (separate volume so if it gets full, it

Re: [opam-devel] opam bulk builds linked in experimentally to opam.ocaml.org

On 3 Apr 2015, at 15:06, Török Edwin wrote: > > On 04/03/2015 04:35 PM, Anil Madhavapeddy wrote: >> I've left the OPAM bulk builder rsyncing to a new logging volume on >> opam.ocaml.org (separate volume so if it gets full, it wont affect the rest >>

Re: [opam-devel] opam bulk builds linked in experimentally to opam.ocaml.org

On 3 Apr 2015, at 14:48, Daniel Bünzli wrote: > > Le vendredi, 3 avril 2015 à 15:35, Anil Madhavapeddy a écrit : >> I've left the OPAM bulk builder rsyncing to a new logging volume on >> opam.ocaml.org (http://opam.ocaml.org) (separate volume so if it gets full, >&g

[opam-devel] opam bulk builds linked in experimentally to opam.ocaml.org

I've left the OPAM bulk builder rsyncing to a new logging volume on opam.ocaml.org (separate volume so if it gets full, it wont affect the rest of the infrastructure at all): http://opam.ocaml.org/builds/ The jobs are currently run on a 48-core machine on a looping cron, so I'm just going

Re: [opam-devel] OPAM on a Raspberry Pi 2

On 2 Apr 2015, at 10:52, Dario Teixeira wrote: > > Hi, > > >> This sounds like the key problem. OPAM+aspcud should work fine >> on ARM (we use it regularly like this in MirageOS with a Cubieboard2). >> >> Could you please file a bug report with the version of aspcud and >> OPAM and the output?

Re: [opam-devel] OPAM on a Raspberry Pi 2

> On 31 Mar 2015, at 13:43, Dario Teixeira wrote: > > Hi, > > I'm trying to use OPAM 1.2.1 on a Raspberry Pi 2 running Raspbian. > At first glance everything seems fine. However, I'm running into > problems when attempting to install some packages with complex > dependencies. OPAM complains t

Re: [opam-devel] Travis is broken

Just disable the OSX build again if it's an issue. I trimmed back the number of Linux combinations already. -anil > On 24 Mar 2015, at 12:09, Thomas Gazagnaire wrote: > > We start to have the same issue again. > > Travis CI kindly allocates us 3 linux and 1 OSX builders per PR. As we are > t

Re: [opam-devel] Finding dependencies of a specific OPAM package

2. > > If you want all packages in the reverse dependency cone of cohttp _that are > also > coinstallable with it_, then you need to actually call the solver on each of > them. > > -- > Roberto > > On Mon, Mar 23, 2015 at 04:27:47PM +, Anil Madhavapeddy wrote:

[opam-devel] Finding dependencies of a specific OPAM package

I'm trying to find all the reverse dependency of a particular version of Cohttp. I can do: opam list --depends-on cohttp --rec to get all of the dependencies for all versions. Unfortunately trying: opam list --depends-on cohttp.0.15.2 --rec gives the same results (including packages

Re: [opam-devel] 1.2.1 final

On 18 Mar 2015, at 14:58, Louis Gesbert wrote: > > And -- thanks a lot for the packagings! > >> How about we swap over the OPAM repository tests to have a single >> OCaml 4.02.1+OPAM 1.2.0 test, with all the rest being OPAM 1.2.1? > > Indeed, it's vital to keep a 1.2.0 test in case packagers in

Re: [opam-devel] 1.2.1 final

On 18 Mar 2015, at 09:43, Thomas Leonard wrote: > > On 18 March 2015 at 03:57, Louis Gesbert wrote: >> Hi all, >> >> 1.2.1 is finally out, with no changes from RC2. Enjoy! >> >> Announcement to the platform blog and the caml-list coming soon. > > Great! I've updated the 0install feed (source,

  1   2   >