Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#60930 - grub-mkconfig can't creates /boot/grub/grub.cfg clean install
Attached to Project:
Arch Linux
Opened by Denis Pershev (napaster) - Thursday, 29 November 2018, 05:18 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 29 November 2018, 05:21 GMT
Opened by Denis Pershev (napaster) - Thursday, 29 November 2018, 05:18 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 29 November 2018, 05:21 GMT
|
DetailsDescription:
grub-mkconfig cannot complete the installation if installed in a folder that was not created earlier. If you run the grub-install command before that, the / boot / grub folder is created and the grub.cfg configuration file is created in it. After that, grub-mkconfig runs without problems. Additional info: core/grub 2:2.02-8 * config and/or log files etc Steps to reproduce: [napaster@ArchPaster ~]$ sudo grub-mkconfig -o /tmp/test.cfg Generating grub configuration file … Found image linux: /boot/vmlinuz-linux Found image initrd: /boot/initramfs-linux.img Found fallback initrd image(s) in /boot: initramfs-linux-fallback.img done But if you point to a folder that is not created, then the result is [napaster@ArchPaster ~]$ sudo grub-mkconfig -o /tmp/test/test.cfg /usr/bin/grub-mkconfig: строка 245: /tmp/test/test.cfg.new: There is no such file or directory |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Thursday, 29 November 2018, 05:21 GMT
Reason for closing: Not a bug
Additional comments about closing: This is acting as expected, given that upstream code is what is causing it to happen. And I don't see why this is a problem in the first place, many commands are like that.
Thursday, 29 November 2018, 05:21 GMT
Reason for closing: Not a bug
Additional comments about closing: This is acting as expected, given that upstream code is what is causing it to happen. And I don't see why this is a problem in the first place, many commands are like that.