From: Maxime Devos <maximedevos@telenet.be>
To: kiasoc5@disroot.org, guix-devel@gnu.org
Subject: Re: Repology and outdated packages
Date: Tue, 07 Jun 2022 23:32:35 +0200 [thread overview]
Message-ID: <4239c2707242bde2ba1b54ba6781975c2379c1ea.camel@telenet.be> (raw)
In-Reply-To: <f563cd29cc2130f0aa54c2eeb139a5bddd8e98ff@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
kiasoc5@disroot.org schreef op di 07-06-2022 om 18:39 [+0000]:
> So without demanding more maintainer time, for now I just convince myself that:
> - key toolchains such as Rust and Go are not always up to date, thus blocking the
> upgrade of several packages
In my experience with antioxidant, not-up-to-date Rust toolchains do
not prevent upgrading packages -- in the process of resolving build
failures, I updated some crates. This never resulted in a ‘you need an
new toolchain error’. At worst, I had to disable the "unstable",
"nightly" or "generic-simd" features of the crate.
There are a lot of outdated crates in Guix, but AFAICT this is
unrelated to the newness of the toolchain.
I don't know about Go.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-07 23:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 18:39 Repology and outdated packages kiasoc5
2022-06-07 18:47 ` Nicolas Goaziou
2022-08-11 22:46 ` Vagrant Cascadian
2022-08-14 2:32 ` Maxim Cournoyer
2022-06-07 21:32 ` Maxime Devos [this message]
2022-06-09 8:02 ` Maxime Devos
2022-06-07 21:41 ` Maxime Devos
2022-06-08 21:38 ` Ludovic Courtès
2022-06-09 3:07 ` Oleg Pykhalov
2022-06-09 3:49 ` kiasoc5
2022-06-09 4:05 ` kiasoc5
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=4239c2707242bde2ba1b54ba6781975c2379c1ea.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=kiasoc5@disroot.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).