From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Aleksandr Vityazev <avityazev@posteo.org>
Cc: 52497-done@debbugs.gnu.org, 52497@debbugs.gnu.org
Subject: [bug#52497] [PATCH] gnu: boost-signals2: Update hash
Date: Wed, 15 Dec 2021 01:57:15 +0100 [thread overview]
Message-ID: <871r2evcs2.fsf@nckx> (raw)
In-Reply-To: <502a90e38bb6f5832fb4230c09e8c9d3343be868.1639528799.git.avityazev@posteo.org>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Aleksandr,
Aleksandr Vityazev 写道:
> * gnu/packages/boost (boost-signals2): [source]: Update hash.
Thanks!
Hash changes happen… ‘but they shouldn't’. Commit messages should
not imply that they're routine.
The diff is quite significant:
$ git diff 10b030be782b979509cee15e0f0afde59d2f9581..\
4a51d6e47230123d413cbecb19eb94f195301b8e | wc -l
1829
We should record the two commits in the change log.
10b030b is from October 2019. Boost 1.77.0 wasn't released until
August 2021[0].
The boost-1.77.0 tag hasn't been moved from 4a51d6e since June
2021. It seems likely that upstream creates boost-X.Y.Z tags
targetting unreleased future Boost versions, moves them freely,
but stops once that Boost version is released.
That's something we could document in a comment, at least.
I'll ask for confirmation on their bug tracker.
Only two formatting nitpicks:
> gnu: boost-signals2: Update hash
Missing ‘.’.
> * gnu/packages/boost (boost-signals2): [source]: Update hash.
Drop the first ‘: ’.
Pushed as 04b6e1ed265e64a004c7ea93018179785b979f31 with those
changes.
Kind regards,
T G-R
[0]: https://lists.boost.org/boost-announce/2021/08/0593.php
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2021-12-15 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 0:40 [bug#52497] [PATCH] gnu: boost-signals2: Update hash Aleksandr Vityazev
2021-12-15 0:57 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
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=871r2evcs2.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=52497-done@debbugs.gnu.org \
--cc=52497@debbugs.gnu.org \
--cc=avityazev@posteo.org \
--cc=me@tobias.gr \
/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.