Georgy Yakovlev

this project has been moved to https://gitweb.gentoo.org/proj/cargo-ebuild.git and mirrored to https://github.com/gentoo/cargo-ebuild for pull requests. this repo still remains but should be marked as deprecated soon. I've merged this PR and...

actually even 0.2.0 can't generate working CRATES string. still getting missing crates, for example ``` >>> Compiling source in /var/tmp/portage/dev-util/sccache-0.2.13/work/sccache-0.2.13 ... error: failed to select a version for the requirement...

`bincode = "= 1.2.0` failure was easy to workaround by manually adding, but 0.3.0 still needs to be looked at, as it produces incomplete crate list.

FYI, 2.0.7 includes fixes for SEEK_DATA problem: https://github.com/openzfs/zfs/commit/a524f8d6afa141dd82bc60554610679614ea0f54 https://github.com/openzfs/zfs/commit/33fa3985a9791a6dcd2ee60ac9ea21486d068c0f those commits are on 2.0.x branch and are included with 2.0.7 tag. I agree that compat PR looks harmless to me,...

``` * QA Notice: Pre-stripped files found: * /usr/bin/lsd ``` upstream has this ``` [profile.release] lto = true codegen-units = 1 strip = true debug = false ``` in `Cargo.toml`...

some useful tips here as well: https://wiki.gentoo.org/wiki/Package_testing you don't need all things from there, just use as overview.

https://github.com/rust-lang/rust/issues/97255 downstream gentoo bug: https://bugs.gentoo.org/847421 in gentoo we've added those 2 patches on top of 1.61.0 and it fixes the problem 1. https://github.com/rust-lang/llvm-project/commit/fe8a27acd716a42667f5a572f52f2b04636010ff and 2. https://github.com/rust-lang/llvm-project/commit/67a290460c374d5e0d18a06c798896cac0b19e59 I think it's the...

> Can not reproduce on Pop OS 22.04 (Based on Ubuntu 22.04) -- `cargo install exa` works fine. > # Meta > >  it's only happening on 1.61.0 release...

> This seems to happen on gentoo too (: `error: could not compile `exa` > > Caused by: process didn't exit successfully: `rustc --crate-name exa --edition=2018 src/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type...

confirmed This option is only useful if you have a processor that supports SPE (e500, otherwise known as 85xx series), but does not have any effect on a non-spe cpu...