Summary: | Sandbox violations when XDG_CONFIG_HOME is set in the calling environment | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Justin Lecher (RETIRED) <jlec> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mgorny, pacho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 481822, 488378, 499068, 499288 | ||
Bug Blocks: |
Description
Justin Lecher (RETIRED)
![]() I sent a note to gentoo-dev asking for advice. Ideally this would be dealt with by Portage, but it looks like that's going to get caught up in the usual EAPI lag time. same problem with mpv xdg.eclass was added by Gilles some weeks ago for this kind of issue (and yes, I would also like to see this done at PM level for not needing to keep adding xdg.eclass to random ebuilds when bugs are reported but, until that is done...) This looks tracker-ish, and it seems that all tracked bugs have been fixed. The only remaining point is to have ENV_UNSET from EAPI 7 implemented and in use. |