From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id oEq2IoPeNWNfeQAAbAwnHQ (envelope-from ) for ; Thu, 29 Sep 2022 20:05:55 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id 0O+uIoPeNWONKAAA9RJhRA (envelope-from ) for ; Thu, 29 Sep 2022 20:05:55 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 427A4EFB6 for ; Thu, 29 Sep 2022 20:05:55 +0200 (CEST) Received: from localhost ([::1]:35300 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1odxv0-0001iZ-BX for larch@yhetil.org; Thu, 29 Sep 2022 14:05:54 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:57890) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odxVz-0006GX-59 for guix-patches@gnu.org; Thu, 29 Sep 2022 13:40:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:40451) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1odxVy-0006rG-FH for guix-patches@gnu.org; Thu, 29 Sep 2022 13:40:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1odxVx-0003h8-WF for guix-patches@gnu.org; Thu, 29 Sep 2022 13:40:02 -0400 X-Loop: help-debbugs@gnu.org Subject: [bug#57540] [PATCH] Please rebase (was: Add ocaml-elpi (a dependency of coq-mathcomp-analysis)) Resent-From: Julien Lepiller Original-Sender: "Debbugs-submit" Resent-CC: guix-patches@gnu.org Resent-Date: Thu, 29 Sep 2022 17:40:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57540 X-GNU-PR-Package: guix-patches X-GNU-PR-Keywords: patch To: Garek Dyszel , zimoun Cc: 57540@debbugs.gnu.org Received: via spool by 57540-submit@debbugs.gnu.org id=B57540.166447318114152 (code B ref 57540); Thu, 29 Sep 2022 17:40:01 +0000 Received: (at 57540) by debbugs.gnu.org; 29 Sep 2022 17:39:41 +0000 Received: from localhost ([127.0.0.1]:39526 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1odxVc-0003gB-6f for submit@debbugs.gnu.org; Thu, 29 Sep 2022 13:39:40 -0400 Received: from lepiller.eu ([89.234.186.109]:55724) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1odxVZ-0003fz-Fn for 57540@debbugs.gnu.org; Thu, 29 Sep 2022 13:39:38 -0400 Received: from lepiller.eu (localhost [127.0.0.1]) by lepiller.eu (OpenSMTPD) with ESMTP id 0f687568; Thu, 29 Sep 2022 17:39:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lepiller.eu; h=date:from :to:cc:subject:in-reply-to:references:message-id:mime-version :content-type:content-transfer-encoding; s=dkim; bh=2qBJKhvW/O9d W88qcYJHhL0/iAQeYrsrY7rqpo5Mm2Q=; b=G8376cL9UKZUAIin3a+sIz5oTc1s 2tp79RgdQ0w8NvlXPdHm6iqVlUctsx6BEWZGCgHQjeWfX3X4HSWLudGeaRbaZo1i JHS9484IHw8H23Hw/x/LnbiDTTcaZTVCo2WoOPXUYbMSEGKtkPdhfdjhpWpLT1R4 ykeH26EN3eC+CFGepOsbNLVnzLEn5A4KrysURbaiNDdPevKwFcffDwKrRdA3YIdh DXp4F10MGStL4kL0kU0giP4VXfeiutfw23GNRgoQLP6KvwLXcdbF8mhHw8LrzSaK 0Frmza2fmfz2y0uprbqLpLZE2qCKSRxdBFzxdomEdjemb0MkJCsRrS08Vw== Received: by lepiller.eu (OpenSMTPD) with ESMTPSA id c7679dcd (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Thu, 29 Sep 2022 17:39:35 +0000 (UTC) Date: Thu, 29 Sep 2022 19:39:22 +0200 From: Julien Lepiller User-Agent: K-9 Mail for Android In-Reply-To: <871qru5cju.fsf@disroot.org> References: <79d544f7d8ba64b631a6f0f1d2ef0b08@disroot.org> <87sfl3vxws.fsf@disroot.org> <86sfkew017.fsf_-_@gmail.com> <87a66l9dem.fsf@disroot.org> <871qru5cju.fsf@disroot.org> Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----UE8W40XHUKL44TRR6YGB7H5U5FMOPC Content-Transfer-Encoding: 7bit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: guix-patches@gnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+larch=yhetil.org@gnu.org Sender: "Guix-patches" X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1664474755; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:resent-cc: resent-from:resent-sender:resent-message-id:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=Hk6vZJd23MgoylDADRGOZ9ciGIXadhu2UoOEnE528SU=; b=ipC5uX6B2nd4tCqbjlV1dzv6UFzgBbTnQQNK4+i2YOqwWZcZzKKE21QMoH8NeVgF5o/4yP lxfcxgviJgF4pAAfmzwb6WRTGsHRO26yLiZJlCrBNYvozqT6pP25X6a/8NB7sqsIRin7Er avBN9BMTsweVeSsLQDtZelCccW3C8/9x513u5TVg4vTVKSz5HXU+1Y4ZLV1qxBWZ1kVACL 9Wb272cwK/ZhEtArnvXivqrgaALqIyxm93wMVABUbfejXIwoUlBFd2cGU1OcOJNo+rYpCl cqZtalFU5KgRd4GiJiNmlcbOuCk62cbFuCgIJo+IiRmThu8xhc6xSJQwqtCsaw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1664474755; a=rsa-sha256; cv=none; b=nGNcPpkgWkorrhKg6FcrpWjALWp+YArzME6UPtX7Ui06QykC6Ds+3IzXcPvp2WlEpx9DAv xN1npyy++UewFZDQiavZI0lR+Cxst+R0qyRic1x71BwsGGZSd9b/OA/J1W4uF4uuSKzntJ YpiyffQLWRtxzZWzH4kC/1EjUGtsBNSUbpIEwsMnkAf6bCPWA82Z2V86zgfJR6dI1Vm6xJ BuMULym83+mHYl58yj1Cfy3iKJ3dXX/xIY2IWhWsQ8Aw6d4NsQy6QAwoYfPpr4ymZAq8zQ bzgB5fdbixXAfgD+c0paS+J3GiooNvLImbipkFlgIVRsYsHWCohhIjx0nbetlQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=lepiller.eu header.s=dkim header.b=G8376cL9; dmarc=fail reason="SPF not aligned (relaxed)" header.from=lepiller.eu (policy=none); spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: 7.36 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=lepiller.eu header.s=dkim header.b=G8376cL9; dmarc=fail reason="SPF not aligned (relaxed)" header.from=lepiller.eu (policy=none); spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 427A4EFB6 X-Spam-Score: 7.36 X-Migadu-Scanner: scn0.migadu.com X-TUID: 1S+wC0FFKS9y ------UE8W40XHUKL44TRR6YGB7H5U5FMOPC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable You can close by sending a reply to nnnnn-close@debbugs=2Egnu=2Eorg, where = nnnnn is the bug number=2E If it's easier for you, let's focus on ocaml-elp= i first :) If you have any question or need help, don't hesitate to ask! Le 29 septembre 2022 19:13:25 GMT+02:00, Garek Dyszel a =C3=A9crit=C2=A0: >Hi again, > >It looks like Coq has been updated to 8=2E16 now, which means the two >packages required by coq-mathcomp-hierarchy-builder in this patchset are >now out of date=2E The build processes have completely changed for >ocaml-elpi and coq-elpi=2E > >The new ocaml-elpi build system got rather confusing and will likely >take me much longer than I originally expected=2E Maybe we could close >this issue? I think it might be easier if I were to send in ocaml-elpi >on its own, for example=2E > >Let me know=2E > >Thanks! >Garek > >At 09:04 2022-09-27 UTC-0400, Garek Dyszel wr= ote: >> Hi Julien and simon, >> >> I planned to write back yesterday but had to run out the door >> unexpectedly=2E >> >> At 18:52 2022-09-26 UTC+0200, zimoun wro= te: >>> For instance the series reads, =2E=2E=2E where the logic about the ord= er is >>> not obvious >> >> The logic was essentially adding dependencies in reverse order=2E I >> started with the package that I wanted to build (coq-mathcomp-analysis)= , >> and added the dependencies as I found they were needed=2E >> >> I'll stick with committing dependencies in forward order (committing >> dependencies before packages) from now on=2E >> >>> I have tried to clean the mess but I give up for now=2E :-) It would b= e >>> much easier if the series provides, >>> >>> 1=2E the Git commit against which revision these patches apply (see t= he >>> option --base of git-format-patch) >>> >>> 2=2E the correct dependency order of the patches >> >> Probably it would also be easier to start over from the new master >> branch and recommit the remaining packages in the proper order=2E >> >> If I don't have another major interruption, I will send out a new set o= f >> commits, in the correct order, formatted with --base, before or by >> Friday=2E Excluding those packages which were already pushed to master,= of >> course :) >> >> At 20:39 2022-09-24 UTC+0200, Julien Lepiller wr= ote: >>> No need to repeat the license here=2E Also, this means that the licens= e >>> should be lgpl2=2E1+, instead of plain lgpl2=2E1=2E >> >> Ah, seems like I was getting lost in package-ception there and didn't >> check over the descriptions too rigorously=2E I'll keep this in mind wh= en >> preparing the next patchset for this thread=2E >> >>> For python packages, I see you add python to the inputs=2E Why is that= ? >>> The python-build-system already provides python=2E >> >> I had been getting errors of the form "python3 was not found on the >> PATH" during the 'configure' phase of some python packages, even though >> the python-build-system was being used=2E I added python to everything = to >> avoid such errors, but forgot to remove it for packages where it was no= t >> really needed=2E >> >> If I can find the first package that produced that error, I'll submit a >> bug report for it with the precise error quoted=2E=20 >> >>> It looks like python-jsonschema-next (4=2E5=2E1) does not have any >>> dependent, so updating this package instead might be better than >>> adding a new one, wdyt? >> >> I found evidence to the contrary, I think=2E With graphviz installed, I >> ran >> >> $ guix graph python-jsonschema > /tmp/py-js-deps=2Edot >> $ gc -n /tmp/py-js-deps=2Edot >> >> which says that there are 186 nodes, or (186 - 1) =3D 185 packages >> dependent on python-jsonschema-next=2E If you prefer viewing it as an >> image, >> >> $ dot /tmp/py-js-deps=2Edot > /tmp/py-js-deps=2Epng >> $ feh /tmp/py-js-deps=2Epng >> >> shows all 185 packages originating from the node named >> "python-jsonschema@4=2E5=2E1"=2E >> >> Maybe for now we could add this transitional python-jsonschema-4=2E15 t= o >> build coq-mathcomp-analysis, and remove it in a subsequent patchset? I >> don't want to tie this patch up unnecessarily=2E >> >> If I have malformed patches now with only 20 packages,=2E=2E=2E well, l= et's >> just say I don't know if I want to see the results just yet, if I'll >> need to rebuild 185 :) >> >> -- Garek ------UE8W40XHUKL44TRR6YGB7H5U5FMOPC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable You can close by sending a reply to nnnnn-close@de= bbugs=2Egnu=2Eorg, where nnnnn is the bug number=2E If it's easier for you,= let's focus on ocaml-elpi first :)

If you have any question or need= help, don't hesitate to ask!

Le 29 septe= mbre 2022 19:13:25 GMT+02:00, Garek Dyszel <garekdyszel@disroot=2Eorg>= ; a =C3=A9crit=C2=A0:
Hi again,

It looks like Coq has =
been updated to 8=2E16 now, which means the two
packages required by coq=
-mathcomp-hierarchy-builder in this patchset are
now out of date=2E The =
build processes have completely changed for
ocaml-elpi and coq-elpi=2E
The new ocaml-elpi build system got rather confusing and will likely<=
br>take me much longer than I originally expected=2E Maybe we could closethis issue? I think it might be easier if I were to send in ocaml-elpion its own, for example=2E

Let me know=2E

Thanks!
Garek
At 09:04 2022-09-27 UTC-0400, Garek Dyszel <garekdyszel@disroot=2E=
org> wrote:
 Hi Juli=
en and simon,

 I planned to write back yesterday but had to run out =
the door
 unexpectedly=2E

 At 18:52 2022-09-26 UTC+0200, zimoun &=
lt;zimon=2Etoutoune@gmail=2Ecom> wrote:
For instance the series reads, =2E=2E=2E where the logi=
c about the order is
not obvious

 The logic was esse=
ntially adding dependencies in reverse order=2E I
 started with the pack=
age that I wanted to build (coq-mathcomp-analysis),
 and added the depen=
dencies as I found they were needed=2E

 I'll stick with committing d=
ependencies in forward order (committing
 dependencies before packages) =
from now on=2E

 I h=
ave tried to clean the mess but I give up for now=2E :-) It would be
 mu=
ch easier if the series provides,

  1=2E the Git commit against whic=
h revision these patches apply (see the
     option --base of git-format=
-patch)

  2=2E the correct dependency order of the patches

 Probably it would also be easier to start over from the new mas=
ter
 branch and recommit the remaining packages in the proper order=2E
 If I don't have another major interruption, I will send out a new se=
t of
 commits, in the correct order, formatted with --base, before or by=

 Friday=2E Excluding those packages which were already pushed to master=
, of
 course :)

 At 20:39 2022-09-24 UTC+0200, Julien Lepiller &l=
t;julien@lepiller=2Eeu> wrote:
No need to repeat the license here=2E Also, this means that the =
license
should be lgpl2=2E1+, instead of plain lgpl2=2E1=2E

 Ah, seems like I was getting lost in package-ception there and did=
n't
 check over the descriptions too rigorously=2E I'll keep this in min=
d when
 preparing the next patchset for this thread=2E

For python packages, I see you add p=
ython to the inputs=2E Why is that?
The python-build-system already prov=
ides python=2E

 I had been getting errors of the form "=
python3 was not found on the
 PATH" during the 'configure' phase of some=
 python packages, even though
 the python-build-system was being used=2E=
 I added python to everything to
 avoid such errors, but forgot to remov=
e it for packages where it was not
 really needed=2E

 If I can fi=
nd the first package that produced that error, I'll submit a
 bug report=
 for it with the precise error quoted=2E 

It looks like python-jsonschema-next (4=2E5=2E1) doe=
s not have any
dependent, so updating this package instead might be bett=
er than
adding a new one, wdyt?

 I found evidence to=
 the contrary, I think=2E With graphviz installed, I
 ran

 $ guix=
 graph python-jsonschema > /tmp/py-js-deps=2Edot
 $ gc -n /tmp/py-js-=
deps=2Edot

 which says that there are 186 nodes, or (186 - 1) =3D 18=
5 packages
 dependent on python-jsonschema-next=2E If you prefer viewing=
 it as an
 image,

 $ dot /tmp/py-js-deps=2Edot > /tmp/py-js-de=
ps=2Epng
 $ feh /tmp/py-js-deps=2Epng

 shows all 185 packages ori=
ginating from the node named
 "python-jsonschema@4=2E5=2E1"=2E

 M=
aybe for now we could add this transitional python-jsonschema-4=2E15 to
=
 build coq-mathcomp-analysis, and remove it in a subsequent patchset? I
=
 don't want to tie this patch up unnecessarily=2E

 If I have malform=
ed patches now with only 20 packages,=2E=2E=2E well, let's
 just say I d=
on't know if I want to see the results just yet, if I'll
 need to rebuil=
d 185 :)

 -- Garek
<= /html> ------UE8W40XHUKL44TRR6YGB7H5U5FMOPC--