unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: goodoldpaul@autistici.org
Cc: 36667@debbugs.gnu.org
Subject: bug#36667: crates-io.scm packages should build on master
Date: Sun, 21 Jul 2019 16:21:42 -0700	[thread overview]
Message-ID: <87r26jug6x.fsf@gmail.com> (raw)
In-Reply-To: <625406f416329b6b7787020d9143416a@autistici.org> (goodoldpaul's message of "Mon, 15 Jul 2019 14:21:15 +0000")

[-- Attachment #1: Type: text/plain, Size: 884 bytes --]

Hi Giacomo,

Thank you for taking the time to submit a patch!

goodoldpaul@autistici.org writes:

> Rust libraries contained in gnu/packages/crates-io.scm are not
> building anymore because cargo wants to download crate dependencies
> inside the store.

Curious!  I wonder when this changed.

> The attached patch sets the CARGO_HOME environment variable  to "."
> much earlier than it previously was, just after the configure
> phase. With the attached patch all packages in crates-io.scm build
> without errors.
>
> I hope I did everything right,

Unfortunately, your patch does not apply cleanly to the current tip of
the master branch (d1e766e5c6b9e25ff0fa8e0a2adf3e764401a3a2).  Could you
please tell me what commit or branch it applies against, or send a new
patch that applies cleanly to the current tip of the master branch?

Thank you,

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-07-21 23:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 14:21 bug#36667: crates-io.scm packages should build on master goodoldpaul
2019-07-21 23:21 ` Chris Marusich [this message]
2021-10-26 21:02 ` paul via Bug reports for GNU Guix
2022-01-20 22:02 ` bug#36667: (No Subject) Attila Lendvai

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=87r26jug6x.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=36667@debbugs.gnu.org \
    --cc=goodoldpaul@autistici.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.
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).