unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: peter@polidoro.io, 56298@debbugs.gnu.org
Subject: [bug#56298] [PATCH 5/7] gnu: rust-anyhow-1: Update to 1.0.58.
Date: Wed, 27 Jul 2022 18:01:11 +0200	[thread overview]
Message-ID: <25b4e04e-8fe5-61c9-5f98-14fc3fa112d7@telenet.be> (raw)
In-Reply-To: <9c646934de8160f6782e20fbd6ebadf5bf11f69e.1656513323.git.peter@polidoro.io>


[-- Attachment #1.1.1: Type: text/plain, Size: 953 bytes --]


On 29-06-2022 16:46, peter@polidoro.io wrote:
>       (build-system cargo-build-system)
>       (arguments
> -     `(#:cargo-development-inputs
> +     `(#:cargo-inputs (("rust-backtrace" ,rust-backtrace-0.3))
> +       #:cargo-development-inputs
>          (("rust-futures" ,rust-futures-0.3)
>           ("rust-rustversion" ,rust-rustversion-1)
> +        ("rust-syn" ,rust-syn-1)
>           ("rust-thiserror" ,rust-thiserror-1)
>           ("rust-trybuild" ,rust-trybuild-1))))

I assume you updated rust-rustversion to update rust-anyhow?  If so, I 
have looked at the Cargo.toml of anyhow. It is very picky in the version 
of dependents, so if in the future we update rust-rustversion again, 
rust-anyhow will fail to build. To be robust to that, the Cargo.toml 
needs to be patched to be less picky, or alternatively you could wait 
for antioxidant which ignores the version specifications entirely.

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 --]

  reply	other threads:[~2022-07-27 16:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 14:41 [bug#56298] python-cmsis-pack-manager and dependencies Peter Polidoro
2022-06-29 14:46 ` [bug#56298] [PATCH 0/7] Add " peter
2022-06-29 14:46   ` [bug#56298] [PATCH 1/7] gnu: Add python-milksnake peter
2022-06-29 14:46   ` [bug#56298] [PATCH 2/7] gnu: Add rust-quick-xml-0.17 peter
2022-07-27 15:55     ` Maxime Devos
2022-06-29 14:46   ` [bug#56298] [PATCH 3/7] gnu: Add rust-minidom-0.12 peter
2022-07-27 16:02     ` Maxime Devos
2022-06-29 14:46   ` [bug#56298] [PATCH 4/7] gnu: rust-rustversion-1: Update to 1.0.7 peter
2022-06-29 14:46   ` [bug#56298] [PATCH 5/7] gnu: rust-anyhow-1: Update to 1.0.58 peter
2022-07-27 16:01     ` Maxime Devos [this message]
2022-07-29 19:26       ` Maxime Devos
2022-06-29 14:46   ` [bug#56298] [PATCH 6/7] gnu: Add rust-loom-0.5 peter
2022-06-29 14:46   ` [bug#56298] [PATCH 7/7] gnu: Add python-cmsis-pack-manager peter

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=25b4e04e-8fe5-61c9-5f98-14fc3fa112d7@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=56298@debbugs.gnu.org \
    --cc=peter@polidoro.io \
    /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).