This repository has been archived by the owner on Nov 22, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 22
Publish fuse-sys on crates.io #20
Comments
Can you elaborate on the error in
Please refrain from these kinds of snarky comments on this project. They are neither productive nor appreciated. |
On Wed, 17 Mar 2021 17:03:15 -0700 Andrew Moffat ***@***.***> wrote:
Can you elaborate on the error in `cargo package` please? It should
be able to pull in locally defined packages, like `fuse-sys` is.
It is pulled in, that's not the issue. It builds and everything, but
cargo package fails.
Since re-running it again would take too long, I dug up the relevant
conversation from IRC:
```
[7:57:09 pm] <raingloom> heyo, i'm trying to package supertag on guix
and am running into this error: dependency `fuse-sys` does not specify
a version.
[7:58:08 pm] <raingloom> it's part of the same git repo and
its Cargo.toml defines version as 0.1.0 [7:59:18 pm] <raingloom> if i
change supertag's Cargo.toml to include `fuse-sys = { version = "*",
path = "./fuse-sys" }` then it fails with `no matching package named
`fuse-sys` found`
[7:59:27 pm] <raingloom> what's going on here?
[7:59:59 pm] <raingloom> this is supertag v0.1.4
[8:03:29 pm] <Arnavion> What are you running that's giving you the
error
[8:05:27 pm] <raingloom> Arnavion: "cargo" "package"
"--no-metadata" "--no-verify"
[8:08:49 pm] <Arnavion> Looks like `cargo
package` requires the deps to be on crates.io even if they're specified
via a path dep
[8:09:27 pm] <Arnavion> I'm not sure what `cargo
package` does that can't be done with `cargo vendor` + tar'ing
yourself, which will definitely work for your use case
[8:09:55 pm] <Arnavion> because we use the latter at $dayjob to build
dist tarballs for debbuilder and rpmbuild
[8:11:55 pm] <raingloom> Arnavion: this is what the cargo-build-system
of Guix runs by default, i'm not sure what the reasoning behind it is.
[8:13:42 pm] <raingloom> cargo doesn't even have networking access in
the Guix build environment, so I'm not sure how it's trying to access
crates.io
[8:20:47 pm] <raingloom> well, whatever, i guess i can just
disable the package phase in Guix since we don't actually need the
sources
```
>And again, I am not thrilled to have to through GitHub to report
>issues.
Please refrain from these kinds of snarky comments on this project.
They are neither productive nor appreciated.
It's not sarcasm, I'm being completely honest. I don't condone GitHub
and Microsoft working with ICE. Yes I'm aware of their followup. They
shouldn't be allowed to put a price on human rights.
When there are reports of a group (ICE in this case) doing forced
hysterectomies, the correct response is not "we will still do business
with them because something something corporate rights".
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Apparently that's needed for
cargo package
to work. Ran into that while trying to package Supertag for Guix.And again, I am not thrilled to have to through GitHub to report issues.
The text was updated successfully, but these errors were encountered: