From: Maxime Devos <maximedevos@telenet.be>
To: Jim Newsome <jim@jimnewsome.net>, 56684@debbugs.gnu.org
Cc: Jim Newsome <jnewsome@torproject.org>
Subject: [bug#56684] [PATCH 1/3] Bump rust 1.57 -> 1.58
Date: Fri, 22 Jul 2022 02:08:25 +0200 [thread overview]
Message-ID: <86c503a4-bd43-6ba8-a307-452c57cf1cfa@telenet.be> (raw)
In-Reply-To: <0dacb7cb72945f7f6886602c47111661b746cbcc.1658440640.git.jnewsome@torproject.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 750 bytes --]
merge 54439 56684
thanks
You aren't bumping the version but adding a new version of the Rust
package, the old one is still there. Also, conventionally it is named
updating in Guix, and a commit message is missing. For examples see the
git history.
Are all the intermediate steps needed, or could you reduce the number of
new intermediate packages?
E.g., you could try going directly from 1.57 to 1.60 without
intermediate steps. If that's possible, it would be less inefficient to
compile.
Also, there are already patches for updating rust, see
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=54439>. Please look for
already existing patches before posting duplicates, to avoid double
work, etc.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-22 0:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 22:01 [bug#56684] [PATCH 1/3] Bump rust 1.57 -> 1.58 Jim Newsome
2022-07-21 22:09 ` [bug#56684] [PATCH 2/3] Bump rust 1.58 -> 1.59 Jim Newsome
2022-07-21 22:09 ` [bug#56684] [PATCH 3/3] Bump rust 1.59 -> 1.60 Jim Newsome
2022-07-21 22:14 ` [bug#56684] This is based on the core-updates branch Jim Newsome
2022-07-22 0:08 ` Maxime Devos [this message]
2022-07-22 0:47 ` [bug#56684] [PATCH 1/3] Bump rust 1.57 -> 1.58 Jim Newsome
2022-07-22 1:33 ` Jim Newsome
2022-07-22 9:07 ` Maxime Devos
2022-08-03 6:54 ` [bug#56684] Cannot bootstrap 1.59/1.60 -> 1.62.1 directly kiasoc5 via Guix-patches via
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=86c503a4-bd43-6ba8-a307-452c57cf1cfa@telenet.be \
--to=maximedevos@telenet.be \
--cc=56684@debbugs.gnu.org \
--cc=jim@jimnewsome.net \
--cc=jnewsome@torproject.org \
/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).