| Summary: | portage's read-only fs check breaks mount-boot.eclass | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Michał Górny <mgorny> |
| Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | base-system, qa |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
*** This bug has been marked as a duplicate of bug 532264 *** |
>>> Installing (1 of 14) sys-boot/lilo-24.1::gentoo * One or more files installed to this package are set to be installed to * read-only filesystems. Please mount the following filesystems as read- * write and retry. * * /boot * * Package 'sys-boot/lilo-24.1' NOT merged due to read-only file systems. * If necessary, refer to your elog messages for the whole content of the * above message. The package used to install because mount-boot.eclass detected the case and remounted it r/w in pkg_preinst(). Not saying it's sane thing to do, just pointing out it's broken now. Maybe it's a good pretext to get rid of insanities like this.