From: Guillaume Le Vaillant <glv@posteo.net>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 63583@debbugs.gnu.org, Michael Ford <fanquake@gmail.com>
Subject: [bug#63583] gnu: bitcoin-core: Update to 24.1.
Date: Fri, 19 May 2023 16:52:12 +0000 [thread overview]
Message-ID: <87353suuk3.fsf@kitej> (raw)
In-Reply-To: <87wn14xp2e.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
Simon Tournier <zimon.toutoune@gmail.com> skribis:
> Hi,
>
> On ven., 19 mai 2023 at 13:30, Michael Ford <fanquake@gmail.com> wrote:
>
>> -(define-public bitcoin-core-23.1
>> +(define-public bitcoin-core-24.1
>
> [...]
>
>> - (version "23.1")
>> + (version "24.1")
>
> [...]
>
>> - "03k56vgk0a0wr84gpj256hvijk6iyshl85hcrx800hiznyzl5hkl"))))
>> + "0kmgpzknbykgwb8vd7hj3j1xxn35785gf4vii5705k6rnarks2la"))))
>
> [...]
>
>> -(define-public bitcoin-core bitcoin-core-23.1)
>> +(define-public bitcoin-core bitcoin-core-24.1)
>
> Out of curiosity, why are these two symbols required? Maybe, it could
> be nice to drop ’bitcoin-core-xy.z’ and keep only ’bitcoin-core’, no?
>
> WDYT?
>
> Cheers,
> simon
Hi.
IIRC, at some point in the past we had two versions of bitcoin-core, and
the 'bitcoin-core' variable was pointing at one of the packages. Then
one of the versions became outdated and was removed.
Since we now have only one version, removing the leftovers from the
multiple package version support stuff seems like a good idea...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2023-05-19 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 12:30 [bug#63583] gnu: bitcoin-core: Update to 24.1 Michael Ford
2023-05-19 15:24 ` bug#63583: " Guillaume Le Vaillant
2023-05-19 16:29 ` [bug#63583] " Simon Tournier
2023-05-19 16:52 ` Guillaume Le Vaillant [this message]
2023-05-20 7:24 ` Guillaume Le Vaillant
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=87353suuk3.fsf@kitej \
--to=glv@posteo.net \
--cc=63583@debbugs.gnu.org \
--cc=fanquake@gmail.com \
--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 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).