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 1/4] gnu: gecode: Update to development version 6.3.0.
Date: Sun, 12 May 2024 21:08:55 +0200	[thread overview]
Message-ID: <ZkETxxAlMKIbzPXz@jurong> (raw)
In-Reply-To: <f5a006def8b65680ffe79602658825e2b25bfb56.1711794209.git.herman@rimm.ee>

Hello,

Am Sat, Mar 30, 2024 at 12:40:05PM +0100 schrieb Herman Rimm:
> * gnu/packages/maths.scm (gecode): Update.
> -    (version "6.2.0")
> +    (version "6.3.0")
>      (source (origin
>                (method git-fetch)
>                (uri (git-reference
>                      (url "https://github.com/Gecode/gecode")
> -                    (commit (string-append "release-" version))))
> +                    (commit "2d20e88cae176584b6e09d909aca3eb72ae76829")))

we normally only package the latest released version; indeed this dates
from 2019 and is 6.2.0 according to their webpage.
Is a newer package really needed? Why this commit from 2020, and not another
one from 2024? Their git repository is, let us say, unusual: The master
branch has not seen any commit after the 6.2.0 release except for a license
change. Work seems to be done in the origin/release/6.3.0 branch.

So without compelling reason, I would suggest to not do the update;
in any case it could not be called 6.3.0, since there is no such release.

Maybe joining issue
   https://github.com/Gecode/gecode/issues/177
from last August to make a new release would be a path forward?

Andreas





  parent reply	other threads:[~2024-05-12 19: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 ` Andreas Enge [this message]
2024-05-14  7:31   ` [bug#70087] [PATCH 1/4] gnu: gecode: Update to development version 6.3.0 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   ` [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZkETxxAlMKIbzPXz@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.