all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 52164@debbugs.gnu.org
Subject: [bug#52164] [PATCH] gnu: coq: Update to 8.14.0.
Date: Mon, 29 Nov 2021 08:39:23 -0500	[thread overview]
Message-ID: <89F34741-9EFC-4C19-8167-3B990D90533F@lepiller.eu> (raw)
In-Reply-To: <CAJ3okZ23f-Vsm2fSJobjt3zLn+Wfy3YshfzKw4FtSLvQ2-YCzw@mail.gmail.com>




>
>Hum, the breakage of coq-bignums or coq-equations is recent.  Because
>using 65234d0 from Nov. 2nd, they are substituable; using coq@8.13.2.
>Or do you mean that coq-binums@8.13 is broken with coq@8.14?

I meant to say bignums 8.13 is broken with coq 8.14, and bignums 8.14 is broken with coq 8.13.

>
>In all cases, it appears to me clearer to have:
>
> 1. update coq
> 2. update coq-bignums
> 3. update coq-equations
>
>i.e., update the "compiler" and fix then the breakage introduced by
>this "compiler" upgrade, e.g., upgrade other packages.  We are always
>doing like that, no?

I've always updated dependents first whenever possible (without breaking anything), then the compiler, then the rest that needs the new compiler. However, I've always been careful not to introduce breakage with a commit, even if it's inside a series. I think that's the policiy, but I'm not sure if it overrides the one-change per commit policy.

>
>
>Cheers,
>simon




  reply	other threads:[~2021-11-29 13:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 16:44 [bug#52164] [PATCH] gnu: coq: Update to 8.14.0 Julien Lepiller
2021-11-28 17:27 ` [bug#52164] [PATCH 1/3] gnu: ocaml-semantics: " Julien Lepiller
2021-11-29  9:05   ` zimoun
2021-11-28 17:27 ` [bug#52164] [PATCH 2/3] gnu: proof-general: Update to latest commit Julien Lepiller
2021-11-29  9:06   ` [bug#52164] [PATCH] gnu: coq: Update to 8.14.0 zimoun
2021-11-28 17:27 ` [bug#52164] [PATCH 3/3] " Julien Lepiller
2021-11-29  9:42   ` [bug#52164] [PATCH] " zimoun
2021-11-29 12:29     ` Julien Lepiller
2021-11-29 13:21       ` zimoun
2021-11-29 13:39         ` Julien Lepiller [this message]
2021-11-29 14:13           ` zimoun
2022-05-03 12:35 ` bug#52164: " zimoun

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=89F34741-9EFC-4C19-8167-3B990D90533F@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=52164@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.