From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by c5ff346549e7 (Postfix) with ESMTPS id 602E35D6 for ; Thu, 8 Aug 2019 19:03:39 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.64,362,1559512800"; d="scan'208,217";a="394887158" Received: from sympa.inria.fr ([193.51.193.213]) by mail2-relais-roc.national.inria.fr with ESMTP; 08 Aug 2019 21:03:38 +0200 Received: by sympa.inria.fr (Postfix, from userid 20132) id 63BC07ED24; Thu, 8 Aug 2019 21:03:38 +0200 (CEST) Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 077E97EC74 for ; Thu, 8 Aug 2019 21:03:30 +0200 (CEST) Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=josh@berdine.net; spf=Pass smtp.mailfrom=josh@berdine.net; spf=Pass smtp.helo=postmaster@out5-smtp.messagingengine.com IronPort-PHdr: =?us-ascii?q?9a23=3AwWlE7RQIAe6G9Ci1BKaaVBOwptpsv+yvbD5Q0YIu?= =?us-ascii?q?jvd0So/mwa67ZBeFt8tkgFKBZ4jH8fUM07OQ7/m6HzVZvN3Y6i1KWacPfidNsd?= =?us-ascii?q?8RkQ0kDZzNImzAB9muURYHGt9fXkRu5XCxPBsdMs//Y1rPvi/6tmZKSV3wOgVv?= =?us-ascii?q?O+v6BJPZgdip2OCu4Z3TZBhDiCagbb9oIxi6sBvdutMLjYd/Kqs9xQbFrmVIdu?= =?us-ascii?q?9L2W5mOFWfkgrm6Myt5pBj6SNQu/wg985ET6r3erkzQKJbAjo7LW07/dXnuhbf?= =?us-ascii?q?QwSB4HscSXgWnQFTAwfZ9hH6X4z+vTX8u+FgxSSVJ8z2TbQzWTS/86dmTQLjhS?= =?us-ascii?q?kbOzIl9mzcl9d9h7xHrh2/uxN/wpbUYICLO/p4YqPdZs4RSW5YUspMSyBNHoaw?= =?us-ascii?q?Yo0IAOQcIOZYtJH9qEUSohuiCwesA+bvxSVJhn/wwKY21+ssHAXD0AEmAtkAsm?= =?us-ascii?q?nbrM/tOakST+670afGwzLAYfxU1zfy55THfws7rv2QWLJ9a9DcxVUtGg7Dk16e?= =?us-ascii?q?qZblPzSQ1ukVvWSV6+1gVfmvi2U6tgx+vCKvydotionPmI0ZxE3P+CJ7wIYyPt?= =?us-ascii?q?24SFV2bsW6H5tKqi6aNo12Td04T2Fupik61qQLtJimdyYEz5QnwgTQa/2Bc4WQ?= =?us-ascii?q?+hLsTvqRITdiiHJhf7Kwmwy98Uy4xuLgUcm01VNKoTBDktbRrHwN0xvT5dSdRf?= =?us-ascii?q?t55kuuxzCP1x7K5uFKIEA0kbTUJ4Qlwr43ipUcq0DDEjfzmEXxi6+WcV8o9fSv?= =?us-ascii?q?6+TiernmoYKcN5NsigHjLqQig8K/AeU8MgcQRWSb/eO826H58k39WLlKj+E2k6?= =?us-ascii?q?jDvJDeIsQUurS2AwtT340+6Bi/Fy+r3dUZkHUdMV5JZQ+Lg5LmNl3UPvz1Ce+z?= =?us-ascii?q?j0monTpv3fzKIKHtDojXInXCkbrtZ6px5khBwwQp199f/YhbCrQZLfLzREDxsN?= =?us-ascii?q?vYAwc+Mwyp3+bqCMxx1pgbWWKTGq+VKqbSvkGT5uI0OeaMa44VuDDyK/c74f7u?= =?us-ascii?q?gn45mVkDcqWzwZQXb3W4EuxnI0Wff3Xsns8MHGYLswYkUeDmlUCOXSRcanqoQa?= =?us-ascii?q?4x4ik3CIe8AofCQoCtjqaB3CC+HpBOZGBGDUuMEXfzeoqfRfgMcj+dIs5nkjMa?= =?us-ascii?q?T7ShTZEu1Q22uA/g17VnNvbU+jEftZ/7yNd6/ejTlRUr+TxwDsSdyH2NQnpvnm?= =?us-ascii?q?IIQj82xLpwrVZ8yleFy6h4guZXGcZd5/NTVAoxKIDRz+hnC9DpRgLOYM2JRkun?= =?us-ascii?q?QtSnHz48Vs49kJcyZBM3PN6rixSL+iOrB74TmPSvBYcouOqI1HH0I4N5ym3a/K?= =?us-ascii?q?gnlVgvBMVVYz6InKl6okLxAJXJ22+Ujaqrc6lWlHrP83yD5WCDpk1ZVgM2V6jZ?= =?us-ascii?q?CyNMLnDKpMj0sxuRB4SlDq4qZ04ckJfTeJsPUcXgiBB9fNmmPd3fZ2yrnGLpXk?= =?us-ascii?q?SCy6mAbYznPWMQwHeEURRWo0Uo5X+DcDMGKGK5uWuHV25kGEjjYkXht+9ztCHj?= =?us-ascii?q?FxJm/0Sxd0RkkoGN1FsViPibEKpB2a8Y5WI6rilsWlOwxMnfBNuGqAdnc6RabJ?= =?us-ascii?q?U251IVjG8=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BaHgDicExdhx0Eb0JmHQEBBQEHBQGBZ?= =?us-ascii?q?4FpgRwDTwExKoQeiHyGJ4FqJYNnlyIJAQMBDBsUAQGEPwKCVhwGAQQ0EwEEAQE?= =?us-ascii?q?EAQEEAQMHARMBAQEKCwkIKYUuDII6KYJnAQEBAQIBIx0BASwMBAsJAhgqAgJXB?= =?us-ascii?q?hODIgGBew+QIJp7cYEygnoBAQWCSIR1CYE0i2QXgX+BEScME4JMPodPMoImjC+?= =?us-ascii?q?KF5R4CQKCHWIBhXyNZYIwbYZCg1kUimqlcYE9KoF5ewo7KgGCQQmCORqDV4RZg?= =?us-ascii?q?XiEAz4BATGNEwEB?= X-IPAS-Result: =?us-ascii?q?A0BaHgDicExdhx0Eb0JmHQEBBQEHBQGBZ4FpgRwDTwExKoQ?= =?us-ascii?q?eiHyGJ4FqJYNnlyIJAQMBDBsUAQGEPwKCVhwGAQQ0EwEEAQEEAQEEAQMHARMBA?= =?us-ascii?q?QEKCwkIKYUuDII6KYJnAQEBAQIBIx0BASwMBAsJAhgqAgJXBhODIgGBew+QIJp?= =?us-ascii?q?7cYEygnoBAQWCSIR1CYE0i2QXgX+BEScME4JMPodPMoImjC+KF5R4CQKCHWIBh?= =?us-ascii?q?XyNZYIwbYZCg1kUimqlcYE9KoF5ewo7KgGCQQmCORqDV4RZgXiEAz4BATGNEwE?= =?us-ascii?q?B?= X-IronPort-AV: E=Sophos;i="5.64,362,1559512800"; d="scan'208,217";a="315961039" X-MGA-submission: =?us-ascii?q?MDHFesDiBxu1azaqWAJKxbpPAN53WG2k+NEfzy?= =?us-ascii?q?AZ5OtE20W7Bq9TAFKWpy1YlQ8Imcz8Kf9RfrDan3mVGFgLGzjw7tTwTu?= =?us-ascii?q?tijHMxUOKNCemlhbxvPZmRvz58dE+4oPI3BD+ujFJlMeJAkwvMpOyyNi?= =?us-ascii?q?XUmKxBSZ1ZGTOGnAU74Q+L1g=3D=3D?= Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Aug 2019 21:03:28 +0200 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8AE7120A34 for ; Thu, 8 Aug 2019 15:03:25 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 08 Aug 2019 15:03:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berdine.net; h= from:to:subject:date:message-id:in-reply-to:references :mime-version:content-type; s=fm3; bh=q0e9Jav3tdqint58i7Q9Xl14HB A3pNtn9MuNBzZtVfQ=; b=lyDVivVVTe8Ne6w+GUO4jYPkFK5CppGhcNsaTig7YO Rao6cz+wcbGkoX7GFk72bKaWM85lJ40ZfmMie9UPgUWFYOCx3mglfKdIckrdS0Bp 1SNxeUUm87oOHxOPO0nS3RDM4yYskG1+HrhXk55bY2uASwDaFYgbltsIrgo9YP85 W8CXGGw9qNYBP5ZVV0kYqFIXwfLSo0EOhQIywOHjMvv7gWbpm6J6E0roJ/1gPYUb FiOnCULl3aj+oAKcgthVvrRAGwi/e/OTKf/z5OuxDSYw2qD97cdyhsuMzgF2N0QQ 0qzCztE2Qm85HdEy3EjroFuGeof02MmtoeOnf14pPMZA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=q0e9Ja v3tdqint58i7Q9Xl14HBA3pNtn9MuNBzZtVfQ=; b=t75xgHZKJzd8/bWIU9sieN j0rc7IRwb7BwEP4dsmf/Dr+wLROpwxSJ/P1v8zEIQ0Soxn54bGAD+kM2ex+Ol5te bpGnjx886vTDyATIZ1VfWvWt9agjc+r4mhvoRR93KsK3WiQ74LKY2Vd36Hj6UvUB +ebZy/OuN0ywgxGuY6wiutuyYckCEC5aTNQLN5EOOrG43T7utf9BIJYPM8nq3fJ3 B/OEQ/6dMPXcmVIbmdX2aSn2QRT+nd7pi8jpcZHpj3KQOv5BYloBoSiXb/ZQv1CV VFg5aFNloFruJDzafgF37uFrRJSkbe3yH+f5mCge7C/gY4Qs9zlel+/Sj0bx88oA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudduhedguddvhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enogfuuhhsphgvtghtffhomhgrihhnucdlgeelmdenucfjughrpefhvffufffokfgjfhgg tgesrgdtmherredtjeenucfhrhhomhepfdflohhshhcuuegvrhguihhnvgdfuceojhhosh hhsegsvghrughinhgvrdhnvghtqeenucffohhmrghinhepphgrthhhrdhlohgtrghlpdgt ohhmmhgrnhgurdhlohgtrghlpdgvnhhvqdhfihhlvgdrlhhotggrlhdpmhhoohhordgtoh hmpdhouhhtphhuthdqfhhilhgvrdhlohgtrghlpdhithiirdhlohgtrghlnecukfhppedu leelrddvtddurdeiiedrtdenucfrrghrrghmpehmrghilhhfrhhomhepjhhoshhhsegsvg hrughinhgvrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from [172.16.16.231] (unknown [199.201.66.0]) by mail.messagingengine.com (Postfix) with ESMTPA id 993FC380089 for ; Thu, 8 Aug 2019 15:03:24 -0400 (EDT) From: "Josh Berdine" To: "Ocaml Mailing List" Date: Thu, 08 Aug 2019 20:03:22 +0100 X-Mailer: MailMate (1.12.5r5635) Message-ID: In-Reply-To: References: <20190731211816.x5vj472m34cshifj@matica.foolinux.mooo.com> <20190806184710.7zlxt2amae2tsg3w@matica.foolinux.mooo.com> <20190807203214.6jkj2ygi5vcad4to@matica.foolinux.mooo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_MailMate_2DE949B2-3515-4364-BF92-391955EFB0BC_=" Embedded-HTML: [{"HTML":[1150,3722],"plain":[785,2790],"uuid":"7B2D899F-C497-42C6-A4BA-88F46584BB6D"}] Subject: Re: [Caml-list] opam and dune [Was: How to use -map] Reply-To: "Josh Berdine" X-Loop: caml-list@inria.fr X-Sequence: 17747 Errors-to: caml-list-owner@inria.fr Precedence: list Precedence: bulk Sender: caml-list-request@inria.fr X-no-archive: yes List-Id: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --=_MailMate_2DE949B2-3515-4364-BF92-391955EFB0BC_= Content-Type: text/plain; format=flowed FWIW, there is a very similar stumbling block when working on a pinned package that has an opam file in the opam repo but not in the package's own source repo. In this case the problem does not have anything to do with whether the opam file is generated or not, and is independent of dune. This situation arises if e.g. you `opam pin --dev` (or pin a local git clone of) such a package, and then make source changes that also require changes to the opam file. At that point, opam uses the opam file from the opam repo whether or not there is a local one (that is not in source control). Perhaps this situation is too uncommon to warrant the time to address it, but I have hit it and don't know a satisfactory work-around. Cheers, Josh On 8 Aug 2019, at 19:05, Yawar Amin wrote: > Checking in generated build system files is fairly common practice > now. > Lots of build systems/package managers have 'lockfiles' that are > generated > to help with reproducible builds. These need to be checked in. In fact > I > think opam has two different ways of generating 'lockfiles'. > > Regards, > > Yawar > > On Wed, Aug 7, 2019 at 4:32 PM Ian Zimmerman > wrote: > >> On 2019-08-06 11:47, Ian Zimmerman wrote: >> >>> So, for now, I'm sticking with Makefiles. :-P >> >> I decided to give dune a try, mostly to give myself an excuse to >> procrastinate with other projects. After some rough going but being >> able to figure it out, I hit what seems like an impassable strait. >> >> dune generates the $package.opam file, therefore that file should not >> be >> on version control. _But_ then "opam pin ." insists on getting that >> very file from the version control repo, instead of using the local >> one: >> >> matica!179 aaa$ opam pin . >> [NOTE] Package aaa is already pinned to >> git+file:///home/itz/git/aaa#master (version 0.0.8~dev). >> [aaa.0.0.8~dev] no changes from git+file:///home/itz/git/aaa#master >> [WARNING] aaa's opam file has uncommitted changes, using the >> versioned one >> aaa is now pinned to git+file:///home/itz/git/aaa#master (version >> 0.0.8~dev) >> The following actions will be performed: >> - install aaa 0.0.8~dev* >> Do you want to continue? [Y/n] y >> [aaa.0.0.8~dev] synchronised from git+file:///home/itz/git/aaa#master >> >> <><> Processing actions >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> [ERROR] The compilation of aaa failed at >> "/home/itz/.local/packages/opam/opam-init/hooks/sandbox.sh build dune >> subst". >> >> #=== ERROR while compiling aaa.0.0.8~dev >> ======================================# >> # context 2.0.4 | linux/x86_64 | ocaml-base-compiler.4.07.1 | >> pinned(git+file:///home/itz/git/aaa#master#193ad3bd) >> # path >> ~/.local/packages/opam/default/.opam-switch/build/aaa.0.0.8~dev >> # command ~/.local/packages/opam/opam-init/hooks/sandbox.sh build >> dune >> subst >> # exit-code 1 >> # env-file ~/.local/packages/opam/log/aaa-10257-b76d46.env >> # output-file ~/.local/packages/opam/log/aaa-10257-b76d46.out >> ### output ### >> # Error: No .opam files found. >> >> >> >> <><> Error report >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> +- The following actions failed >> | - build aaa 0.0.8~dev >> +- >> - No changes have been performed >> >> So how do you get around this? >> >> -- >> Please don't Cc: me privately on mailing lists and Usenet, >> if you also post the followup to the list or newsgroup. >> To reply privately _only_ on Usenet and on broken lists >> which rewrite From, fetch the TXT record for no-use.mooo.com. >> --=_MailMate_2DE949B2-3515-4364-BF92-391955EFB0BC_= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
<= p dir=3D"auto">FWIW, there is a very similar stumbling block when working= on a pinned package that has an opam file in the opam repo but not in th= e package's own source repo. In this case the problem does not have anyth= ing to do with whether the opam file is generated or not, and is independ= ent of dune.

This situation arises if e.g. you `opam pin --dev` (or pi= n a local git clone of) such a package, and then make source changes that= also require changes to the opam file. At that point, opam uses the opam= file from the opam repo whether or not there is a local one (that is not= in source control).

Perhaps this situation is too uncommon to warrant the tim= e to address it, but I have hit it and don't know a satisfactory work-aro= und.

Cheers, Josh

On 8 Aug 2019, at 19:05, Yawar Amin wrote:

Checking in generated build system files is fairly common = practice now. Lots of build systems/package managers have 'lockfiles&= #39; that are generated to help with reproducible builds. These need to b= e checked in. In fact I think opam has two different ways of generating &= #39;lockfiles'.

Regards,

= Yawar

On Wed, Aug 7, 2019 at 4:32 PM Ian Zimmerman <itz@very.loosely.org> wrote:
On 2019-08-06 11:47,= Ian Zimmerman wrote:

> So, for now, I'm sticking with Makefiles. :-P

I decided to give dune a try, mostly to give myself an excuse to
procrastinate with other projects.=C2=A0 After some rough going but being=
able to figure it out, I hit what seems like an impassable strait.

dune generates the $package.opam file, therefore that file should not be<= br> on version control.=C2=A0 _But_ then "opam pin ." insists on ge= tting that
very file from the version control repo, instead of using the local one:<= br>
=C2=A0matica!179 aaa$ opam pin .
[NOTE] Package aaa is already pinned to git+file:///home/itz/git/aaa#mast= er (version 0.0.8~dev).
[aaa.0.0.8~dev] no changes from git+file:///home/itz/git/aaa#master
[WARNING] aaa's opam file has uncommitted changes, using the versione= d one
aaa is now pinned to git+file:///home/itz/git/aaa#master (version 0.0.8~d= ev)
The following actions will be performed:
=C2=A0 - install aaa 0.0.8~dev*
Do you want to continue? [Y/n] y
[aaa.0.0.8~dev] synchronised from git+file:///home/itz/git/aaa#master
=
<><> Processing actions <><><><><&= gt;<><><><><><><><><&g= t;<><><><><><><><><>= ;<><><><><>
[ERROR] The compilation of aaa failed at "/home/itz/.local/packages/= opam/opam-init/hooks/sandbox.sh build dune
=C2=A0 =C2=A0 =C2=A0 =C2=A0 subst".

#=3D=3D=3D ERROR while compiling aaa.0.0.8~dev =3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D#
# context=C2=A0 =C2=A0 =C2=A02.0.4 | linux/x86_64 | ocaml-base-compiler.4= =2E07.1 | pinned(git+file:///home/itz/git/aaa#master#193ad3bd)
# path=C2=A0 =C2=A0 =C2=A0 =C2=A0 ~/.local/packages/opam/default/.opam-sw= itch/build/aaa.0.0.8~dev
# command=C2=A0 =C2=A0 =C2=A0~/.local/packages/opam/opam-init/hooks/sandb= ox.sh build dune subst
# exit-code=C2=A0 =C2=A01
# env-file=C2=A0 =C2=A0 ~/.local/packages/opam/log/aaa-10257-b76d46.env # output-file ~/.local/packages/opam/log/aaa-10257-b76d46.out
### output ###
# Error: No <package>.opam files found.



<><> Error report <><><><><><= ;><><><><><><><><><= ><><><><><><><><><&= gt;<><><><><><><>
+- The following actions failed
| - build aaa 0.0.8~dev
+-
- No changes have been performed

So how do you get around this?

--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.
--=_MailMate_2DE949B2-3515-4364-BF92-391955EFB0BC_=--