From: Efraim Flashner <efraim@flashner.co.il>
To: Gottfried <gottfried@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: "rust-sha2" and "tealdeer" packages fail to be build
Date: Tue, 14 Feb 2023 11:59:12 +0200 [thread overview]
Message-ID: <Y+tbcN8spW7vpWlY@3900XT> (raw)
In-Reply-To: <1ce93450-efe1-bd95-08ba-73b9d1ebc114@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
On Mon, Feb 13, 2023 at 02:50:53PM +0000, Gottfried wrote:
> Hi,
> since many weeks the two packages
>
> rust-sha2 and tealdeer fail to be build during upgrading.
>
> Do only I have this problem?
>
> or is something wrong with those packages?
I assume you mean rust-sha2@0.8 since we have 4 different versions
currently of rust-sha2. It shouldn't matter that it fails its test
suite, nothing directly depends on it.
I looked into tealdeer and it looks like it needs a newer version of
rust-pin-project@0.4. I've updated it on the staging branch, but it
causes a rebuild of librsvg so it'll have to get merged in.
I'll look into doing a rust-updates branch as part of the rust team and
see if it's possible to schedule that in.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-02-14 9:59 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
2023-02-14 9:59 ` Efraim Flashner [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
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=Y+tbcN8spW7vpWlY@3900XT \
--to=efraim@flashner.co.il \
--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).