caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Hendrik Boom <hendrik@topoi.pooq.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [rfc] deprecating opam 1.2.0
Date: Fri, 2 Jun 2017 14:31:01 +0100	[thread overview]
Message-ID: <307A8D8C-0840-4C7D-9722-15748B71D4CF@recoil.org> (raw)
In-Reply-To: <20170602121630.GA30172@topoi.pooq.com>

On 2 Jun 2017, at 13:16, Hendrik Boom <hendrik@topoi.pooq.com> wrote:
> 
> On Fri, Jun 02, 2017 at 11:09:37AM +0100, Anil Madhavapeddy wrote:
>> 
>> ### 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.

Thanks for checking, Hendrik.  It may be worth mentioning to them that
OPAM 1.2.0 is already broken in practical terms (unless the repository
it defaults to is rolled back), and so we encourage backports to 1.2.2
in this case.

regards,
Anil

  reply	other threads:[~2017-06-02 13:31 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
2017-06-02 13:31   ` Anil Madhavapeddy [this message]
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=307A8D8C-0840-4C7D-9722-15748B71D4CF@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=hendrik@topoi.pooq.com \
    /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;
as well as URLs for NNTP newsgroup(s).