all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Herman Rimm <herman@rimm.ee>
Cc: Eric Bavier <bavier@posteo.net>,
	Sharlatan Hellseher <sharlatanus@gmail.com>,
	70087@debbugs.gnu.org
Subject: [bug#70087] [PATCH v2 1/4] gnu: gecode: Update to 6.2.0-1.f7f0d7c.
Date: Wed, 15 May 2024 19:08:37 +0200	[thread overview]
Message-ID: <ZkTsFXbsH4IQY5nG@jurong> (raw)
In-Reply-To: <a5751f750c3aa223830e82826d4f3204c509c314.1715786322.git.herman@rimm.ee>

Hello Herman,

it looks like we have worked in parallel on this patchset, sorry for this!
With my previous commits to master, your v2 does not apply any more.

I have updated chuffed to version 0.13.2, which covers your patch 2.
Your patch 3 has already been applied in a form derived from your v1.
I have compiled minizinc with the new chuffed, and could use them together
to solve the magic square. So we are in a working and consistent state.

Could you please send a v3 of your patches 1 and 4, based on current
master? I suppose patch 4 can remain as it is.
For patch 1, the new revision should then be 3, as we are currently at 2.
As written above, updating minizinc and gecode simultaneously to their
latest versions did not work out of the box for me. I suppose that these
two features:

Am Wed, May 15, 2024 at 05:51:22PM +0200 schrieb Herman Rimm:
> [arguments]: Add patch-msc-and-version phase.
> (minizinc)[arguments]: Copy provided gecode.msc file instead.

solve the problem?

I have reopened the bug, and will let you go ahead now; I think you
are in a better position than me for adapting your patches to the
current master.

Thanks,

Andreas





  parent reply	other threads:[~2024-05-15 17:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30 11:40 [bug#70087] [PATCH 1/4] gnu: gecode: Update to development version 6.3.0 Herman Rimm via Guix-patches via
2024-03-30 11:42 ` [bug#70087] [PATCH 2/4] gnu: Add chuffed Herman Rimm via Guix-patches via
2024-03-30 11:42 ` [bug#70087] [PATCH 3/4] gnu: minizinc: Add chuffed backend Herman Rimm via Guix-patches via
2024-03-30 11:42 ` [bug#70087] [PATCH 4/4] gnu: minizinc: Update to 2.8.3 Herman Rimm via Guix-patches via
2024-05-12 19:08 ` [bug#70087] [PATCH 1/4] gnu: gecode: Update to development version 6.3.0 Andreas Enge
2024-05-14  7:31   ` Herman Rimm via Guix-patches via
2024-05-14 11:44     ` Andreas Enge
2024-05-15 10:12     ` Andreas Enge
2024-05-15 12:06       ` Andreas Enge
2024-05-15 12:39         ` Andreas Enge
2024-05-15 13:08           ` bug#70087: " Andreas Enge
2024-05-15 15:51 ` [bug#70087] [PATCH v2 1/4] gnu: gecode: Update to 6.2.0-1.f7f0d7c Herman Rimm via Guix-patches via
2024-05-15 15:51   ` [bug#70087] [PATCH v2 2/4] gnu: Add chuffed Herman Rimm via Guix-patches via
2024-05-15 15:51   ` [bug#70087] [PATCH v2 3/4] gnu: minizinc: Add chuffed backend Herman Rimm via Guix-patches via
2024-05-15 15:51   ` [bug#70087] [PATCH v2 4/4] gnu: minizinc: Update to 2.8.4 Herman Rimm via Guix-patches via
2024-05-15 17:08   ` Andreas Enge [this message]
2024-05-15 18:01 ` [bug#70087] [PATCH 0/3] Update minizinc and solvers Herman Rimm via Guix-patches via
2024-05-15 18:01   ` [bug#70087] [PATCH 1/3] gnu: gecode: Update to 6.2.0-1.f7f0d7c Herman Rimm via Guix-patches via
2024-05-15 18:01   ` [bug#70087] [PATCH 2/3] gnu: chuffed: Update to 0.13.2 Herman Rimm via Guix-patches via
2024-05-15 18:02   ` [bug#70087] [PATCH 3/3] gnu: minizinc: Update to 2.8.4 Herman Rimm via Guix-patches via
2024-05-15 19:03   ` [bug#70087] [PATCH 0/3] Update minizinc and solvers Andreas Enge
2024-05-22 15:12     ` Andreas Enge
2024-06-02 10:17       ` bug#70087: " Ludovic Courtès

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=ZkTsFXbsH4IQY5nG@jurong \
    --to=andreas@enge.fr \
    --cc=70087@debbugs.gnu.org \
    --cc=bavier@posteo.net \
    --cc=herman@rimm.ee \
    --cc=sharlatanus@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.