876817 – portage uses CARGO_HOME from root user environment

Bug 876817 - portage uses CARGO_HOME from root user environment

Summary: portage uses CARGO_HOME from root user environment

Status:	RESOLVED DUPLICATE of bug 876754

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2022-10-12 05:26 UTC by brankob
Modified:	2022-10-12 05:34 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
emerge --info (my_emerge.info,8.60 KB, text/plain) 2022-10-12 05:27 UTC, brankob	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description brankob 2022-10-12 05:26:41 UTC

This makes emerge of packages like librsvg (which uses Rust+cargo) fail when they try to update CARGO_HOME content (sandbox violations).
When CARGO_HOME is unset in root user's environment, librsvg compiles fine.

Reproducible: Always

Steps to Reproduce:
1. export CARGO_HOME="/some_unrelated_dir"
2. emerge -1 librsvg
3.
Actual Results:  
emerge  fails with various write access sandbox violations


I've attached content of emerge --info, just in case.

Comment 1 brankob 2022-10-12 05:27:10 UTC

Created attachment 823659 [details]
emerge --info

Comment 2 Sam James archtester

2022-10-12 05:34:27 UTC

It's still a duplicate, but this time a double one. 

This is actually fixed as of late last night - librsvg now has a version in ~arch using EAPI 8 and cargo.eclass (see the comments in the bug I marked your original as a duplicate of).

In future though, please include the full build.log.

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