| Summary: | sys-firmware/intel-microcode-20191115_p20200209 requires mounted /boot | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Joerg Schaible <joerg.schaible> |
| Component: | Eclasses | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED CANTFIX | ||
| Severity: | normal | CC: | jstein |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=532264 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
(In reply to Joerg Schaible from comment #0) > An update to intel-microcode fails if /boot is not mounted. Packages like > grub will auto-mount /boot. Please elaborate what you mean with "packages like grub will auto-mount" because this should be wrong. Since commit https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2d90570e81469bf75b2d4a4275151e282632c18e (bug 532264), mount-boot.eclass is no longer able to mount /boot. |
An update to intel-microcode fails if /boot is not mounted. Packages like grub will auto-mount /boot. =============== %< =============== >>> Running pre-merge checks for sys-firmware/intel-microcode-20191115_p20200209 * Your boot partition is not mounted at /boot. * Please mount it and retry. * ERROR: sys-firmware/intel-microcode-20191115_p20200209::gentoo failed (pretend phase): * /boot not mounted * * Call stack: * ebuild.sh, line 125: Called pkg_pretend * intel-microcode-20191115_p20200209.ebuild, line 50: Called mount-boot_pkg_pretend * mount-boot.eclass, line 87: Called mount-boot_check_status * mount-boot.eclass, line 72: Called die * The specific snippet of code: * die "/boot not mounted" * * If you need support, post the output of `emerge --info '=sys-firmware/intel-microcode-20191115_p20200209::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-firmware/intel-microcode-20191115_p20200209::gentoo'`. * The complete build log is located at '/var/log/portage/sys-firmware:intel-microcode-20191115_p20200209:20200216-020507.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/portage/sys-firmware/intel-microcode-20191115_p20200209/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/portage/sys-firmware/intel-microcode-20191115_p20200209/temp/die.env'. * Working directory: '/var/tmp/portage/portage/sys-firmware/intel-microcode-20191115_p20200209/homedir' * S: '/var/tmp/portage/portage/sys-firmware/intel-microcode-20191115_p20200209/work' =============== %< =============== Reproducible: Always Steps to Reproduce: 1. ensure /boot is not mounted 2. emerge sys-firmware/intel-microcode 3. Actual Results: Ebuild fails Expected Results: Auto-mount of /boot and a successful build