From: Andreas Enge <andreas@enge.fr>
To: Herman Rimm <herman@rimm.ee>
Cc: 70087-done@debbugs.gnu.org,
Sharlatan Hellseher <sharlatanus@gmail.com>,
Eric Bavier <bavier@posteo.net>
Subject: bug#70087: [PATCH 1/4] gnu: gecode: Update to development version 6.3.0.
Date: Wed, 15 May 2024 15:08:33 +0200 [thread overview]
Message-ID: <ZkSz0b1rOI4kvd9S@jurong> (raw)
In-Reply-To: <ZkStG0sHuOuf85lc@jurong>
Hello,
I have now applied your patch to add chuffed to minizinc, and I have
gexpified this latter package.
An update of minizinc to 2.8.3 (or 2.8.4, released 5 days ago) does not
build; I think one would need to move to a different commit of gecode
(but not the latest one...).
I am closing the current bug. If you are motivated to look for a combination
of newer gecode and minizinc versions that work together, please feel free
to open a new bug.
Andreas
next prev parent reply other threads:[~2024-05-15 13:10 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 ` Andreas Enge [this message]
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 ` [bug#70087] [PATCH v2 1/4] gnu: gecode: Update to 6.2.0-1.f7f0d7c Andreas Enge
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZkSz0b1rOI4kvd9S@jurong \
--to=andreas@enge.fr \
--cc=70087-done@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).