all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: rust-tempfile-3 update to 3.2.0 breaks sequoia build
Date: Sun, 04 Apr 2021 11:08:01 +0200	[thread overview]
Message-ID: <87wntio1se.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <36597302-d083-38fe-5d63-52d57ee6011c@crazy-compilers.com> (Hartmut Goebel's message of "Tue, 30 Mar 2021 19:19:46 +0200")

Hello,

Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> building sequoia is currently broken in master with
> "syn::export::ToTokens" not found.
>
> I tracked this down to 6513650d40f74 "gnu: rust-tempfile-3: Update to
> 3.2.0." (2021-02-16). The updated package also updates some
> dependency-requirements: cfg-if 0.1 -> 1, rand 0.7 -> 0.8 and
> redox-syscall 0.1 -> 0.2.
>
> While in theory - according to semantic versioning -, updating 3.1.x to
> 3.2.x should not any effect on others packages, this updates has :-(

Ouch :(

> I tried building with rust-tempfile-3.1, with no success - this fails
> with "rand::rngs::OsRng" missing. Updating rust-rand-core-0.6 to 0.6.2
> (since 0.6.1 was yanked), did not help either - then I gave up.

I confirm this.

> Any ideas how to make sequoia build again?

Not really. Is it possible to upgrade it to a more recent commit? I see
that Cargo.lock references tempfile 3.2.0 in HEAD.

Regards,
-- 
Nicolas Goaziou


  reply	other threads:[~2021-04-04  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 17:19 rust-tempfile-3 update to 3.2.0 breaks sequoia build Hartmut Goebel
2021-04-04  9:08 ` Nicolas Goaziou [this message]
2021-04-06  7:37   ` Hartmut Goebel
2021-05-02  7:59     ` Hartmut Goebel
2021-05-04  8:18       ` Nicolas Goaziou
2021-05-04  8:26         ` Hartmut Goebel

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wntio1se.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.