Closed yminsky closed 12 years ago
This is fixed in releases >= 7.3. @avsm could you please update the brew version ?
I upgraded the Homebrew OPAM to 0.7.3 a few days ago in https://github.com/mirage/homebrew-ocaml/commit/23916853b91112b9e188f9fc15ee7e721d7de09f
I think we need the auto-update check in #166 really (although it might be annoying if it is displayed all the time)
This problem is that old versions of opam sometime can't read the repository to know there is a new version available.
that's why you want to add this feature early! i was thinking it could just check a single file with an opam-repository version before doing anything else. Repositories should probably be versioned independently from the clients (e.g. when a new substitution variable is added), but the same file could also contain the latest client version too...
Repositories should probably be versioned independently from the clients (e.g. when a new substitution variable is added), but the same file could also contain the latest client version too...
yes, I was starting looking at something along these lines. I guess we should just put the oldest compatible client version in that file, and regularly warn the user he has an outdated client version on update.
There's also an opam in the regular brew setup (rather than the mirage version.) Can we get the default brew setup upgraded as well? (I'm trying to run bog-standard stuff, so I can more effectively fix bugs that others will run into.)
y
On Wed, Oct 3, 2012 at 10:25 AM, Anil Madhavapeddy <notifications@github.com
wrote:
I upgraded the Homebrew OPAM to 0.7.3 a few days ago in mirage/homebrew-ocaml@mirage/homebrew-ocaml@2391685https://github.com/mirage/homebrew-ocaml/commit/23916853b91112b9e188f9fc15ee7e721d7de09f
I think we need the auto-update check in #166https://github.com/OCamlPro/opam/issues/166really (although it might be annoying if it is displayed all the time)
— Reply to this email directly or view it on GitHubhttps://github.com/OCamlPro/opam/issues/205#issuecomment-9107932.
That's annoying; I hadn't submitted it upstream so we could do quick updates on our tap until it is more stable. Now we have to wait for them to merge versions upstream...I'll open a ticket shortly.
On 3 Oct 2012, at 08:26, Yaron Minsky notifications@github.com wrote:
There's also an opam in the regular brew setup (rather than the mirage version.) Can we get the default brew setup upgraded as well? (I'm trying to run bog-standard stuff, so I can more effectively fix bugs that others will run into.)
y
On Wed, Oct 3, 2012 at 10:25 AM, Anil Madhavapeddy <notifications@github.com
wrote:
I upgraded the Homebrew OPAM to 0.7.3 a few days ago in mirage/homebrew-ocaml@mirage/homebrew-ocaml@2391685https://github.com/mirage/homebrew-ocaml/commit/23916853b91112b9e188f9fc15ee7e721d7de09f
I think we need the auto-update check in #166https://github.com/OCamlPro/opam/issues/166really (although it might be annoying if it is displayed all the time)
— Reply to this email directly or view it on GitHubhttps://github.com/OCamlPro/opam/issues/205#issuecomment-9107932.
— Reply to this email directly or view it on GitHub.
I've opened a Homebrew update request to the latest OPAM at mxcl/homebrew#15279
That was fast! They've merged it. I'll send a note to the Mirage list to deprecate my tap. Everyone should just use the mainline Homebrew version now...
Ok, as homebrew is updated and as I've implemented #166, I'm closing this issue.
When I do an "opam update" on the latest version from brew (0.7.2), I get the following error:
~ $ opam update Fetching git://github.com/mirage/opam-repo-dev ... Synchronizing with http://opam.ocamlpro.com ... Package wdialog depends on the unknown package ocaml-inifiles Package why depends on the unknown package frama-c 'opam update' failed
~ $