Bug 876754 – CARGO_HOME from root user environment leaks into portage

• Status: RESOLVED DUPLICATE of bug 753764
• Product: Gentoo Linux

[Description brankob 2022-10-11 11:09:10 UTC]

I'm using portage-3.0.38.1 and have just noticed that, for example, emerge of gnome-base/librsvg-2.54* ( which uses Rust & Cargo) fails if I have set CARGO_HOME in my environment.

It fails in final phase when sandbox stops the ebuild trying to write into it.



Reproducible: Always

Steps to Reproduce:
1. export CARGO_HOME=/some/dir
2. emerge -1 librsvg
3.
Actual Results:  
 * Final size of installed tree:   25528 KiB ( 24.9 MiB)
 * ----------------------- SANDBOX ACCESS VIOLATION SUMMARY -----------------------
 * LOG FILE: "/var/tmp/portage/gnome-base/librsvg-2.54.4-r1/temp/sandbox.log"
 * 
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line

F: open_wr
S: deny
P: /home/000_MAIN/000_PROJECTS/000_CARGO/.package-cache
A: /home/000_MAIN/000_PROJECTS/000_CARGO/.package-cache
R: /home/000_MAIN/000_PROJECTS/000_CARGO/.package-cache
C: cargo --locked build --verbose --release --bin rsvg-convert

[Comment 1 brankob 2022-10-11 11:12:51 UTC]

Created attachment 823603 [details]
emerge --info of the machine

[Comment 2 Sam James 2022-10-11 11:28:19 UTC]

*** This bug has been marked as a duplicate of bug 753764 ***

[Comment 3 Sam James 2022-10-12 05:34:27 UTC]

*** Bug 876817 has been marked as a duplicate of this bug. ***