From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id D49AD80143 for ; Sat, 3 Jun 2017 16:48:38 +0200 (CEST) Authentication-Results: mail2-smtp-roc.national.inria.fr; spf=None smtp.pra=zhenya1007@gmail.com; spf=Pass smtp.mailfrom=zhenya1007@gmail.com; spf=None smtp.helo=postmaster@mail-yb0-f195.google.com Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of zhenya1007@gmail.com) identity=pra; client-ip=209.85.213.195; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="zhenya1007@gmail.com"; x-sender="zhenya1007@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of zhenya1007@gmail.com designates 209.85.213.195 as permitted sender) identity=mailfrom; client-ip=209.85.213.195; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="zhenya1007@gmail.com"; x-sender="zhenya1007@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-yb0-f195.google.com) identity=helo; client-ip=209.85.213.195; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="zhenya1007@gmail.com"; x-sender="postmaster@mail-yb0-f195.google.com"; x-conformance=sidf_compatible IronPort-PHdr: =?us-ascii?q?9a23=3A71ZCJRNhVQ2c8mMyWs4l6mtUPXoX/o7sNwtQ0KIM?= =?us-ascii?q?zox0K/z6o8bcNUDSrc9gkEXOFd2CrakV1ayL7OigATVGusfe9ihaMdRlbFwst4?= =?us-ascii?q?Y/p08aPIa9E0r1LfrnPWQRPf9pcxtbxUy9KlVfA83kZlff8TWY5D8WHQjjZ0Iu?= =?us-ascii?q?frymUoHdgN6q2O+s5pbdfxtHhCanYbN1MR66sRjdutMYjIZmK6s90BvEr3lVcO?= =?us-ascii?q?hS2W9kOEifkhj468qy5pJv7zhct/c8/MNcTKv2eLg1QrNfADk6KW4549Hluwfe?= =?us-ascii?q?RgWV/HscVWsWkhtMAwfb6RzxQ4n8vCjnuOdjwSeWJcL5Q6w6VjSk9KdrVQTniD?= =?us-ascii?q?wbOD4j8WHYkdJ/gaRGqx+8vRN/worUYIaINPpie67WYN0XSXZdUstXSidMGZ23?= =?us-ascii?q?YZcRAOUdPOZYt4j9qEUIrRuiHgmnGefjxiZVinPqwaE21uIsHgbb0gw9BNIOqG?= =?us-ascii?q?rbo8npNKkcVuC1ybPHzTTFb/hL3Tvw54zFfhUnrPqRX7x/bNDRxFEtGAPLjlue?= =?us-ascii?q?p4/rMS6L2OsRqGWU9fZsWPi1hmI7tw18oD6izdoshInTgYIVz0jJ+ypnwIY6O9?= =?us-ascii?q?K4Tk56asO4HptXqiGVLIp2QsU+TGFopCY11LwGuZimdyUNyZUnxwDQa/qHcoeS?= =?us-ascii?q?/x7vSPqdLDVjiXJqfbKwnRey8Uy6xuLgUcm01U9HoyxYmdfCsXAN0gbc6smBSv?= =?us-ascii?q?Zl8EehwyiA2B7I5eFfPE84j63bK4QuwrIokZocrV7MHirymEnsi6+WbEok9vCp?= =?us-ascii?q?6+TheLXmp4WTO5V6igHkKqgulc2/Afg4MggTRGeX4/iz1Lrm/UHhQLRFlP02kq?= =?us-ascii?q?7esJzAOcsboau5DxdI3Yk98Bm/Di2p0NICkXkANlJFdxSKhJXqNVHWOP30E+uz?= =?us-ascii?q?jlC2nDpox/3KJKPtDojDI3TZjbvsebZw5khBwwQp199f/YhbCrQZLfLzREDxsN?= =?us-ascii?q?vYAwc8MwOuwubnDMxx14MFVm6TG6OZPr7evFuI6+41LOmMY4gVuDn5K/c7/fLh?= =?us-ascii?q?kXg5mVoFcamo25sYdmy4E+x4L0mFZXfgmNQMHGcQsgYgUeDnhkeOXSNXanuyR6?= =?us-ascii?q?484ys0CIOiDYfNXICth7mB0T+6H51WeG9GDFCNHm31e4mYR/sBajmfIsBkkjMe?= =?us-ascii?q?VLihT5Ut2g2ptA//07ZnNPbb+jUEtZL/09h4//Hcmgs39TxwFsid12CNT3ponm?= =?us-ascii?q?4TXD833KV/oVRnxVuZ0Kh4heZYFd1J6P9TXAc6L82U8+svItbzXkrkd9uJQUiv?= =?us-ascii?q?WtiqDSB5Gts3wtsmeUt2HNSmyBfZ0Hz5LaUSkummGpM59LOU5X/sLcd7wHba2a?= =?us-ascii?q?gnxw00QsZJJGT/3vYg3wfWDo/N1U6ekvD5JuwnwCfR+TLbniK1t0ZCXVs1DPzI?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DBBAAFyzJZdMPVVdFcGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBFgEBAQMBAQEJAQEBg1A0C4ENB4NsgTaIY5BPAQEBAQaBKHKBTYZahDW?= =?us-ascii?q?FBYMqghAshB6BWgKCdQc/GAEBAQEBAQEBAQEBEgEKCwwHJjGCMySCQgEEASMEG?= =?us-ascii?q?QEbEgYFAQMBCwYFCxodAgIiAREBBQEKEgYTEgKJfQEDCAUIEKB8P4pUEYEigWw?= =?us-ascii?q?YBQEcgwoFg2IKGScDClaCeQEBAQEGAQEBAQEBGgIGEoYJgiaCazSDJoFxgmWCY?= =?us-ascii?q?QEEgSwBAQGGOwyWIxAIAQGBRAmFVYM3gzGFI4IGGTyEaYo4kxcUH4EVDxCBQnR?= =?us-ascii?q?bGVqDWioPHIIAJDYBiWwBAQE?= X-IPAS-Result: =?us-ascii?q?A0DBBAAFyzJZdMPVVdFcGgEBAQECAQEBAQgBAQEBFgEBAQM?= =?us-ascii?q?BAQEJAQEBg1A0C4ENB4NsgTaIY5BPAQEBAQaBKHKBTYZahDWFBYMqghAshB6BW?= =?us-ascii?q?gKCdQc/GAEBAQEBAQEBAQEBEgEKCwwHJjGCMySCQgEEASMEGQEbEgYFAQMBCwY?= =?us-ascii?q?FCxodAgIiAREBBQEKEgYTEgKJfQEDCAUIEKB8P4pUEYEigWwYBQEcgwoFg2IKG?= =?us-ascii?q?ScDClaCeQEBAQEGAQEBAQEBGgIGEoYJgiaCazSDJoFxgmWCYQEEgSwBAQGGOwy?= =?us-ascii?q?WIxAIAQGBRAmFVYM3gzGFI4IGGTyEaYo4kxcUH4EVDxCBQnRbGVqDWioPHIIAJ?= =?us-ascii?q?DYBiWwBAQE?= X-IronPort-AV: E=Sophos;i="5.39,290,1493676000"; d="scan'208,217";a="277215227" Received: from mail-yb0-f195.google.com ([209.85.213.195]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 03 Jun 2017 16:48:37 +0200 Received: by mail-yb0-f195.google.com with SMTP id 202so3458639ybd.0 for ; Sat, 03 Jun 2017 07:48:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NylIAfqAWQrWWQcgoqrOOkSaKgU3mPxao10qwH3Hp5Y=; b=I3XZS7Ip5mCH8ReRkc1HufFtvAtacF6r8vm/zYmie9/x/V9nYleKzyaT//Yjy/MqDO PQ2UY9glDhctOCa2PTSju1RbLUEQ4k59sqHfVzbDlClyotSyAUJa1Ob4bZJSo3ryX7NS HoIjgFFmaq9JW7/4BGOSjb/uzmmnHejuingE6/xqCBytdlo1cGhGN/sVwYPAIn+ljw60 AirjcHxNa899wqwo2Z3TgG8f+S47h9BXlv+fq5bljnRYD2wXG4X3+7d5ew5jEZkPaYiq vHHsryKxVGxKhCUbg18ZEx0cVoGjrofArCb2lPrdqKFJdRoS+oXe6B84ep193axvGxxD Y5yQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NylIAfqAWQrWWQcgoqrOOkSaKgU3mPxao10qwH3Hp5Y=; b=QrpabckL5ji8hi0XqgmR/YN2CE8kGZ0AEJP+jvhG1+6wmVTTTYSDa1FbajD8jBRF7C 3FhxBUSBBu4oKuqQ6EMtmdtgsXGrNfLwDxI+8gZBljkT79MdAKylmKbI2J1bO3lXEePI lEVZlLXmxwECTP2813iDFM2TOR10YFOavPfgmD8DnXq9PlBJD8FuGsZ7opgDE3YX+x2E pq0xYlv2E3nLZ78M5JOEdPXe0ND6kpz0iltj2Hg48+fWAhFCydK9DCo1xdDefYCWTkWr 3EZijWGK0b3v7lqhuKym52ph1J32uoflfcRifA/D4ksbFJkhVV97KktITyU75AP2zXaz 2JyQ== X-Gm-Message-State: AODbwcBlkbYvvv53K7MuwgI2dX7xM3/Ijq5Vb/drnohzIUKNB7cg5xG7 LNyW2dwvQPITeALAq9GoLYJIBYHTyUIj X-Received: by 10.37.183.143 with SMTP id n15mr3738117ybh.125.1496501316103; Sat, 03 Jun 2017 07:48:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.218.13 with HTTP; Sat, 3 Jun 2017 07:48:35 -0700 (PDT) In-Reply-To: <810984CC-EA48-49A7-A00C-7127E824B9DA@recoil.org> References: <810984CC-EA48-49A7-A00C-7127E824B9DA@recoil.org> From: Evgeny Roubinchtein Date: Sat, 3 Jun 2017 10:48:35 -0400 Message-ID: To: Anil Madhavapeddy Cc: caml users , opam-devel Content-Type: multipart/alternative; boundary="089e08230b505a333605510f5d37" Subject: Re: [Caml-list] [rfc] deprecating opam 1.2.0 --089e08230b505a333605510f5d37 Content-Type: text/plain; charset="UTF-8" > Is there anyone else that is still packaging 1.2.0? Please comment here if so, and we should move them away. FreeBSD ports still only has opam 1.2.0: https://www.freebsd.org/cgi/ports.cgi?query=opam&stype=all. DragonFly may be in the same boat, since, IIRC the ports collection is shared between the two. Also, what about pkgsrc? The opam-2.x/master's "cold" target "just worked" for me when I tried it on FreeBSD (after a tiny patch that has already been merged), so I am optimistic that producing an updated port for FreeBSD is mostly a matter of going through the motions. One annoyance is that well-behaved ports are only supposed to access network during the "fetch" stage, so one would need to replicate in the FreeBSD port's Makefile the targets from the opam source tree that download various things during opam's build (I think it's mostly things in src_ext). That isn't an insurmountable obstacle, by any means, but just a bit of work that needs to be done. -- Best, Zhenya On Fri, Jun 2, 2017 at 6:09 AM, 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. > > ### How do we deprecate it? > > Due to the format changes happening in a minor version, it's a bit > difficult to give opam 1.2.0 users a smooth transition experience, to my > knowledge (Louis Gesbert or Thomas Gazagnaire may correct me here). I > would propose: > > - putting a notice on opam.ocaml.org that 1.2.2 is the only supported > stable release. > - can we somehow put in a request to debian-stable to add a > post-installation message that the upstream package will no longer work > since the repository? > > If there are any users of opam 1.2.0, particularly industrial ones, please > do speak up now. By performing an active deprecation of an older release, I > hope we can focus our efforts on ensuring the opam users have a good > out-of-the-box experience with opam 1.2.2 and the forthcoming opam 2.0 :-) > > regards, > Anil > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs --089e08230b505a333605510f5d37 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> Is there anyone else that is still pac= kaging 1.2.0?=C2=A0 Please comment here if so, and we should move them away= .

FreeBSD ports still only has opam 1.2.0: https://www.fre= ebsd.org/cgi/ports.cgi?query=3Dopam&stype=3Dall.=C2=A0 DragonFly ma= y be in the same boat, since, IIRC the ports collection is shared between t= he two.=C2=A0=C2=A0 Also, what about pkgsrc?=C2=A0=C2=A0

The opam-2= .x/master's "cold" target "just worked" for me when= I tried it on FreeBSD (after a tiny patch that has already been merged), s= o I am optimistic that producing an updated port for FreeBSD is mostly a ma= tter of going through the motions.=C2=A0 One annoyance is that well-behaved= ports are only supposed to access network during the "fetch" sta= ge, so one would need to replicate in the FreeBSD port's Makefile the t= argets from the opam source tree that download various things during opam&#= 39;s build (I think it's mostly things in src_ext).=C2=A0 That isn'= t an insurmountable obstacle, by any means, but just a bit of work that nee= ds to be done.

--
Best,
Zhenya

On Fri, Jun= 2, 2017 at 6:09 AM, Anil Madhavapeddy <anil@recoil.org> 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 comm= unity.=C2=A0 We did some rapid bugfixing to solve common problems, and OPAM= 1.2.2 was released in April 2015.=C2=A0 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 `opa= m` 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 reposi= tory.=C2=A0 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](http= s://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 ove= rall health of the package repository -- maintaining three separate release= s and formats of the repository is not practical.=C2=A0 Therefore the 1.2.0= release needs to be actively deprecated, and we could use some help from t= he 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.=C2=A0 The [Debian Stret= ch](https://wiki.debian.org/DebianStretch) is due to b= ecome 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?=C2=A0 Please comment he= re if so, and we should move them away.

### How do we deprecate it?

Due to the format changes happening in a minor version, it's a bit diff= icult to give opam 1.2.0 users a smooth transition experience, to my knowle= dge (Louis Gesbert or Thomas Gazagnaire may correct me here).=C2=A0 I would= propose:

- putting a notice on opam.ocaml.org that 1.2.2 is the only supported stabl= e release.
- can we somehow put in a request to debian-stable to add a post-installati= on message that the upstream package will no longer work since the reposito= ry?

If there are any users of opam 1.2.0, particularly industrial ones, please = do speak up now. By performing an active deprecation of an older release, I= hope we can focus our efforts on ensuring the opam users have a good out-o= f-the-box experience with opam 1.2.2 and the forthcoming opam 2.0 :-)

regards,
Anil

--
Caml-list mailing list.=C2=A0 Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs

--089e08230b505a333605510f5d37--