Hi all, Issues i will list here are so related that i make only one bug report, depending on the underlying bug(s), it can be split. Context: i run emerge with ROOT, PORTAGE_CONFIGROOT, and SYSROOT all set to the same r/w directory, as a simple user under fakeroot. When /etc/portage is not readable: $ (fake#) ROOT=$r PORTAGE_CONFIGROOT=$r SYSROOT=$r emerge --info Permission denied: '/etc/portage/make.conf' I'm not sure it is expected, PORTAGE_CONFIGROOT being set (this behaviour seems ancient IIRC). Once /etc/portage made readable: $ (fake#) ROOT=$r PORTAGE_CONFIGROOT=$r SYSROOT=$r emerge app-editors/nano looks to work fine (i didn't complete the merge) but: $ (fake#) ROOT=$r PORTAGE_CONFIGROOT=$r SYSROOT=$r emerge app-admin/syslog-ng !!! Read-only file system: /var/db/pkg I suspect python eclass to trigger the bug, it fails the same way for certifi. Adding a custom error message, i could figure out where error is raised: --- /usr/lib/python3.12/site-packages/_emerge/actions.py.orig 2024-12-10 10:53:53.436666627 +0000 +++ /usr/lib/python3.12/site-packages/_emerge/actions.py 2024-12-10 10:54:00.123333294 +0000 @@ -592,6 +592,7 @@ for eroot in eroots: if need_write_vardb and not trees[eroot]["vartree"].dbapi.writable: + writemsg_level("Bad eroot\n", level=logging.ERROR, noiselevel=-1) writemsg_level( f"!!! Read-only file system: {trees[eroot]['vartree'].dbapi._dbroot}\n", level=logging.ERROR, Reproducible: Always
Portage will always require write access to /; it must be able to satisfy BDEPEND by installing packages there.
