all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Brendan Tildesley <mail@brendan.scot>, 52072@debbugs.gnu.org
Subject: bug#52072: [core-updates-frozen] rust-bitflags 1.2.1 fails to build.
Date: Fri, 26 Nov 2021 10:43:29 +0100	[thread overview]
Message-ID: <861r33qmke.fsf@gmail.com> (raw)
In-Reply-To: <1692331808.40671.1637725435027@office.mailbox.org>

Hi,

Thanks for the report.  I do not think it is blocking for the merge.

--8<---------------cut here---------------start------------->8---
$ /tmp/core-updates-frozen/bin/guix refresh -l rust-bitflags@1.2.1
Construire les 9 paquets suivants s'assure que les 14 paquets dépendants sont reconstruits : rust-winit@0.20.0-alpha6 rust-winit@0.19.5 rust-wayland-protocols@0.28.3 rust-wayland-cursor@0.28.3 rust-winit@0.24.0 rust-glutin@0.21.2 rust-glutin@0.26.0 rust-glutin@0.22.0-alpha5 alacritty@0.9.0
--8<---------------cut here---------------end--------------->8---


On Wed, 24 Nov 2021 at 04:43, Brendan Tildesley <mail@brendan.scot> wrote:

> starting phase `build'
> error: could not find `Cargo.toml` in `/tmp/guix-build-rust-bitflags-1.2.1.drv-0` or any parent directory
> error: in phase 'build': uncaught exception:
> %exception #<&invoke-error program: "cargo" arguments: ("build" "--release") exit-status: 101 term-signal: #f stop-signal: #f> 
> phase `build' failed after 0.0 seconds
> command "cargo" "build" "--release" failed with status 101

Which change about rust on core-updates-frozen implies this error?


Cheers,
simon




  reply	other threads:[~2021-11-26  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24  3:43 bug#52072: [core-updates-frozen] rust-bitflags 1.2.1 fails to build Brendan Tildesley
2021-11-26  9:43 ` zimoun [this message]
2022-01-24 21:57 ` Brendan Tildesley

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=861r33qmke.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=52072@debbugs.gnu.org \
    --cc=mail@brendan.scot \
    /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.