Giter VIP home page Giter VIP logo

Comments (7)

samoht avatar samoht commented on May 27, 2024

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

from opam-repository.

avsm avatar avsm commented on May 27, 2024

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 [email protected] 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.

from opam-repository.

lefessan avatar lefessan commented on May 27, 2024

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)

from opam-repository.

samoht avatar samoht commented on May 27, 2024

forbidden by what ?

from opam-repository.

lefessan avatar lefessan commented on May 27, 2024

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

from opam-repository.

samoht avatar samoht commented on May 27, 2024

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.

from opam-repository.

samoht avatar samoht commented on May 27, 2024

This is now tracked by OCamlPro/opam#548

from opam-repository.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.