Summary: | sys-boot/grub-2.12-r2 fails to emerge on my laptop | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Karl Hakimian <hyedad> |
Component: | Current packages | Assignee: | Mike Gilbert <floppym> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | base-system, hyedad |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
emerge --info environment file from emerge |
Description
Karl Hakimian
2024-03-07 14:21:26 UTC
Created attachment 886903 [details]
build.log
build.log file from failed emerge
Created attachment 886904 [details]
emerge --info
emerge --info on system with the issue
Are you setting GRUB_AUTORECONF or GRUB_BOOTSTRAP or GRUB_AUTOGEN? Not purposefully, where would I check? Could you upload the environment file? It's in the temp directory next to the build log. Created attachment 886905 [details]
environment file from emerge
Requested environment file from
/var/tmp/portage/sys-boot/grub-2.12-r2/temp/environment
Looks like GRUB_AUTOGEN is set to 1. Any idea where that is happening? (In reply to Karl Hakimian from comment #7) > Looks like GRUB_AUTOGEN is set to 1. Any idea where that is happening? env | grep -i GRUB_AUTOGEN grep -rsin GRUB_AUTOGEN /etc/portage ? That seems to be it. There was a file created Septermber 2022. This was around the time I installed the laptop. Must have been something I added to fix some other problem, but I have no memory of the problem or the fix. I've removed it and now things are emereging. Thanks, this was driving me crazy. |