From: Greg Hogan <code@greghogan.com>
To: Gottfried <gottfried@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: "rust-sha2" and "tealdeer" packages fail to be build
Date: Mon, 13 Feb 2023 12:09:20 -0500 [thread overview]
Message-ID: <CA+3U0ZmmAu5+ACfF7m9t-d_X4hmGc9JZVVkY8WjM-EXfRj+zbw@mail.gmail.com> (raw)
In-Reply-To: <1ce93450-efe1-bd95-08ba-73b9d1ebc114@posteo.de>
On Mon, Feb 13, 2023 at 9:51 AM Gottfried <gottfried@posteo.de> wrote:
>
> Hi,
> since many weeks the two packages
>
> rust-sha2 and tealdeer fail to be build during upgrading.
>
> Do only I have this problem?
No, though at least for tealdeer the issue has been previously reported.
> or is something wrong with those packages?
Recent releases of tealdeer require Rust 1.62+, whereas Guix only
makes available 1.60. Rust 1.65 is in master but not publicly
available as this is a "core-updates" change. The new teams process
should expedite changes like this.
https://github.com/dbrgn/tealdeer/blob/v1.6.1/Cargo.toml#L15
Greg
next prev parent reply other threads:[~2023-02-13 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 14:50 "rust-sha2" and "tealdeer" packages fail to be build Gottfried
2023-02-13 17:09 ` Greg Hogan [this message]
2023-02-14 9:59 ` Efraim Flashner
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=CA+3U0ZmmAu5+ACfF7m9t-d_X4hmGc9JZVVkY8WjM-EXfRj+zbw@mail.gmail.com \
--to=code@greghogan.com \
--cc=gottfried@posteo.de \
--cc=help-guix@gnu.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.
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).