https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-lang/rust-1.56.0-r1 installs files into unexpected paths. Discovered on: amd64 (internal ref: ci) NOTE: This machine uses GCC-11: https://gcc.gnu.org/gcc-11/porting_to.html
Created attachment 746097 [details] build.log.xz build log and emerge --info (compressed because it exceeds attachment limit, use 'xzless' to read it)
ci has reproduced this issue with version 1.61.0-r1 - Updating summary.
* QA Notice: The ebuild is installing to one or more unexpected paths: * * /usr/share/doc/rust-1.56.0 * this is required for now to be able to switch docs in eselect-rust as rust version in eselect does not use revision numbers, so it will be unable to switch revision doc dir symlink. I'll leave this open for now, but this bug will happen for every non -r0 rust version.
Do the symlinks in /usr/share/doc serve any purpose other than user convenience? It seems like you could just drop them and direct people to look in /usr/lib/rust/... instead.
Yes, it’s tied to rustup and eselect-rust Rustup, in configured to use system toolchain (default gentoo configuration) will use that to show docs, so will some IDEs. It looks for /usr/share/doc/rust, which is a symlink created by eselect-rust. But eselect-rust doesn’t work with revisions right now, and ebuild installs ${PV} suffixed binaries and directories, I will have to do a big chunk of work to silence this harmless warning. I will do it, but later. It’s not breaking anything at all after all.
Ok, so if I understand correctly the critical part is the /usr/share/doc/rust symlink. So long as that points at a valid path, we could drop /usr/share/doc/rust-${PV}. Thanks for explaining.
tinderbox_musl has reproduced this issue with version 1.63.0-r1 - Updating summary.
ci has reproduced this issue with version 1.64.0-r1 - Updating summary.
ci has reproduced this issue with version 1.69.0-r1 - Updating summary.
slibtool_tinderbox has reproduced this issue with version 1.75.0-r1 - Updating summary.
*** Bug 927378 has been marked as a duplicate of this bug. ***
binutils2.42_tinderbox has reproduced this issue with version 1.76.0-r1 - Updating summary.