From: swedebugia <swedebugia@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 36456@debbugs.gnu.org
Subject: bug#36456: Guix stumbles on duplicates?
Date: Tue, 2 Jul 2019 11:30:52 +0200 [thread overview]
Message-ID: <2ad3fe4d-1528-96b4-800b-4a305f707a75@riseup.net> (raw)
In-Reply-To: <87sgrpv8cj.fsf@elephly.net>
On 2019-07-01 21:54, Ricardo Wurmus wrote:
>
> Hi swedebugia,
>
> I don’t understand the bug you are reporting. What duplicates are you
> referring to? How can I reproduce this bug?
I sent the whole crates-io.scm to the bug-adress which you can use to
reproduce.
The duplicates in that file are a lot of double imported crates by arne.
I'm pruning the duplicates by hand right now and building some of the
most referenced packages (like rust-rand) with some degree of success.
The error reported only arises with arnes duplicates added to my own
~200 imported crates.
>
>> guix/build-system/cargo.scm:128:4: Invalid keyword:
>> ("rust-lazy-static" #<package rust-lazy-static@1.3.0
>> /home/user/src/guix/gnu/packages/crates-io.scm:98 3690d10>)
>
> What’s the code at the reported line?
>
(define-public rust-lazy-static
(package
(name "rust-lazy-static") <--- line 98
(version "1.3.0")
(source
(origin
(method url-fetch)
(uri (crate-uri "lazy_static" version))
(file-name
(string-append name "-" version ".tar.gz"))
(sha256
(base32
"052ac27w189hrf1j3hz7sga46rp84zl2hqnzyihxv78mgzr2jmxw"))))
(build-system cargo-build-system)
(arguments
`(#:cargo-inputs (("rust-spin" ,rust-spin))))
(home-page
"https://github.com/rust-lang-nursery/lazy-static.rs")
(synopsis
"A macro for declaring lazily evaluated statics in Rust.")
(description
"This package provides a macro for declaring lazily evaluated
statics in Rust.")
(license #f)))
--
Cheers Swedebugia
next prev parent reply other threads:[~2019-07-02 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 8:38 bug#36456: Guix stumbles on duplicates? swedebugia
2019-07-01 9:01 ` swedebugia
2019-07-01 19:54 ` Ricardo Wurmus
2019-07-02 9:30 ` swedebugia [this message]
2019-07-05 21:33 ` Ludovic Courtès
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=2ad3fe4d-1528-96b4-800b-4a305f707a75@riseup.net \
--to=swedebugia@riseup.net \
--cc=36456@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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.