From: Hendrik Boom <hendrik@topoi.pooq.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] [rfc] deprecating opam 1.2.0
Date: Fri, 2 Jun 2017 08:16:30 -0400 [thread overview]
Message-ID: <20170602121630.GA30172@topoi.pooq.com> (raw)
In-Reply-To: <810984CC-EA48-49A7-A00C-7127E824B9DA@recoil.org>
On Fri, Jun 02, 2017 at 11:09:37AM +0100, 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 higher.
>
> ### Why deprecate opam 1.2.0
>
> OPAM 1.2.0 was released in October 2014, and saw rapid uptake from the community. We did some rapid bugfixing to solve common problems, and OPAM 1.2.2 was released in April 2015. Since then, 1.2.2 has been a very solid release and has been the stable version in use to date.
>
> Unfortunately, part of the bugfixes in the 1.2.2 series resulted in an `opam` file format that is not fully backwards compatible with the 1.2.0 syntax, and the net effect is that users of 1.2.0 now see a broken package repository. Our CI tests for new packages regularly fail on 1.2.0, even if they succeed on 1.2.2 and higher.
>
> As we prepare the plan for [1.2.2 -> 2.0 migration](https://github.com/ocaml/opam/issues/2918), it is clear that we need a "one-in one-out" policy on releases in order to preserve the overall health of the package repository -- maintaining three separate releases and formats of the repository is not practical. Therefore the 1.2.0 release needs to be actively deprecated, and we could use some help from the community to make this happen.
>
> ### Who is still using opam 1.2.0?
>
> I found that the Debian Jessie (stable) release includes 1.2.0, and this is probably the last major distribution including it. The [Debian Stretch](https://wiki.debian.org/DebianStretch) is due to become the stable release on the 17th June 2017, and so at that point there will hopefully be no distributions actively sending opam 1.2.0 out.
>
> Is there anyone else that is still packaging 1.2.0? Please comment here if so, and we should move them away.
Yes. There's Devuan stable. It is Debian without systemd, and it
will take a while for it to catch up when Debian relabels their
releases.
I'll ask about it on the devuan mailing list. Perhaps they can
accelerate the opam-related packages. I don't know whether that will
be compatible with their automated workflow.
-- hendrik
next prev parent reply other threads:[~2017-06-02 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 10:09 Anil Madhavapeddy
2017-06-02 12:16 ` Hendrik Boom [this message]
2017-06-02 13:31 ` Anil Madhavapeddy
2017-06-03 14:48 ` Evgeny Roubinchtein
2017-06-03 15:04 ` David Allsopp
2017-06-05 7:29 ` Hannes Mehnert
2017-06-11 18:27 ` Anil Madhavapeddy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170602121630.GA30172@topoi.pooq.com \
--to=hendrik@topoi.pooq.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox