ocamlnet 3.6.0 is broken

[lefessan]

Hi,

With github version of opam (cadbcde0d242440478f8d172a51b6178af0c3681), I get:

=-=-= ocamlnet.3.6.0 =-=-=
The archive for ocamlnet.3.6.0 is in the local cache.
Extracting /home/lefessan/.opam/archives/ocamlnet.3.6.0+opam.tar.gz ...
Applying ocamlnet-ocaml4.diff
Cannot find /home/lefessan/.opam/4.00.0/build/ocamlnet.3.6.0/ocamlnet-ocaml4.diff

Due to some errors while processing ocamlnet.3.6.0, the following actions will NOT be proceeded:

• install weberizer.0.7.1
  [ERROR] while installing ocamlnet.3.6.0
  OpamGlobals.Exit(66)
  Raised at file "src/opamGlobals.ml", line 70, characters 10-19
  Called from file "src/opamSystem.ml", line 461, characters 6-51
  Called from file "src/opamSystem.ml", line 118, characters 12-17
  Re-raised at file "src/opamSystem.ml", line 123, characters 10-11
  Called from file "list.ml", line 75, characters 12-15
  Called from file "src/opamClient.ml", line 1553, characters 2-312
  Called from file "src/opamParallel.ml", line 244, characters 18-25

  'opam install weberizer' failed

zsh: exit 2 opam install weberizer

using a local clone repository of opam-repository. Looks like some patch on ocamlnet is not downloaded somewhere ?

[samoht]

seems you have an old archive which does contain the patch file. You need to either:

• regenerate it by running opam-mk-repo at the root of your repository, this will update all the archives (opam-mk-repo ocamlnet to regenerate only ocamlnet one)
• deleted archives/* and download all the archive upstream

[avsm]

I think the naming of *-opam.tar.gz archives could be improved post-1.0, to reflect their actual contents. For example, could it be *-opam-MD5.tar.gz, where the MD5 is the hash of all the additional contents?

-anil

On 16 Oct 2012, at 05:28, Thomas Gazagnaire notifications@github.com wrote:

seems you have an old archive which does contain the patch file. You need to either:

• regenerate it by running opam-mk-repo at the root of your repository, this will update all the archives (opam-mk-repo ocamlnet to regenerate only ocamlnet one)
• deleted archives/* and download all the archive upstream
—
Reply to this email directly or view it on GitHub.

[lefessan]

From a discussion with Debian maintainers, it is just forbidden to keep the same version number when the package is updated. This way, you cannot have this kind of problems. In particular, in their version scheme, you just add "-0" to indicate a minor change: ocamlnet.3.6.0+opam modified would become ocamlnet.3.6.0-0+opam, etc. (of course, you can just increase the new version number if you are the official opam maintainer of the package)

[samoht]

forbidden by what ?

[lefessan]

You cannot upload a package that has the same version number as an older one, it is just rejected automatically, I think.

[samoht]

well, technically, we do not upload a new package with the same version, we are just changing the cached archive (ie the upstream archive haven't changed, only the patches). I reckon we should just mirror the upstream archive anyway and not worry about the additional files and patches.

[samoht]

This is now tracked by OCamlPro/opam#548