Closed stefson closed 2 years ago
I can confirm this issue. Having the same error when trying to create an ebuild for a different project.
can I throw the patch into /etc/portage/patches to test it?
I am not a Rust developer and for this reason i am pretty much stuck with this issue. But /etc/portage/patches
is a great idea, if the PR you've provided is working.
Maybe it's a better idea to fill a bug in bugs.gentoo.org instead of here. This is just a Github mirror and i wonder if anyone is actually reading the issues submitted here.
if you're really stuck, there is a secret escape hatch called --noaudit
the patch revendors the crates, therefore its propably going to be a point release
I've figured what the patch is doing. Just wondered how long it might take to end up as an actual release in Portage. I'll try the --noaudit
option or might even try to add a the patch to /etc/portage/patches
. Thanks allot!
the patch revendors the crates, so you have to take the old ebuild and adapt it accordingly
I got it working. Thanks allot. But i still hope there'll be an updated version of this project soon.
you care to share your new ebuild here?
it should get fixed for the tree in the not to long future, cargo-ebuild is an official gentoo project after all
This is the Ebuild i've created. It's not for this project and i've just used --no-audit
and it went through without any issues.
I meant to ask for the cargo-ebuild-0.5.0-r1.ebuild you used, with patch and updated crates to emerge it. Bumped it myself in the evening, now all is fine with the patch indeed.
I didn't change anything to cargo-ebuild and i don't have any Ebuild beside the default one in Portage. Just using --no-audit
did the job for me for now.
sorry I was not around, back now. release 0.5.1 will land to gentoo soon.
hey everyone,
I'm using the cargo-ebuild-0.5.0 from gentoo tree to get a working ebuild for cargo-xbuild. Tried v.0.6.5 and v.0.5.35 from their repo at https://github.com/rust-osdev/cargo-xbuild
cargo-ebuild ebuild gives me a plain segfault, and dmesg is full of these:
tried removing the linking against systems libssh2+libgit2 from the ebuild, to no effect.