Github messages for voidlinux
 help / color / mirror / Atom feed
From: RossComputerGuy <RossComputerGuy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Cargo fails to compile
Date: Mon, 01 Feb 2021 01:47:35 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28372@inbox.vuxu.org> (raw)

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

New issue by RossComputerGuy on void-packages repository

https://github.com/void-linux/void-packages/issues/28372

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  `Void 5.10.10_1 x86_64 AuthenticAMD uptodate rrrrmmnFFFFF`
* package:  
  *affected package(s) including the version*: cargo-0.49.0_1

### Expected behavior
Cargo should be packages

### Actual behavior
```
error[E0283]: type annotations needed
   --> src/cargo/util/config/de.rs:530:63
    |
530 |                 seed.deserialize(Tuple2Deserializer(1i32, env.as_ref()))
    |                                                               ^^^^^^ cannot infer type for struct `std::string::String`
    |
    = note: cannot satisfy `std::string::String: AsRef<_>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0283`.
error: could not compile `cargo`

To learn more, run the command again with --verbose.
=> ERROR: cargo-0.49.0_1: do_build: './cargo build --release ${cargs}' exited with 101
=> ERROR:   in do_build() at srcpkgs/cargo/template:10
```

### Steps to reproduce the behavior
`./xbps-src pkg cargo`


             reply	other threads:[~2021-02-01  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01  0:47 RossComputerGuy [this message]
2021-02-01  1:04 ` ericonr
2021-02-01  1:05 ` RossComputerGuy
2021-02-01  1:47 ` RossComputerGuy
2021-02-01  4:13 ` RossComputerGuy
2021-02-01  4:13 ` [ISSUE] [CLOSED] " RossComputerGuy

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28372@inbox.vuxu.org \
    --to=rosscomputerguy@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).