Arch Linux

Salkay

Member

Registered: 2014-05-22

Posts: 644

[SOL]warning: /boot/grub/grub.cfg saved as /boot/grub/grub.cfg.pacsave

I just upgraded grub from 2:2.02-7 to 2:2.02-8. During the upgrade, I got the following warning:

warning: /boot/grub/grub.cfg saved as /boot/grub/grub.cfg.pacsave
(3/6) upgrading grub                                           [##################################] 100%

However, there is no file at /boot/grub/grub.cfg.pacsave. I'm also confused, because /boot/grub is not managed by pacman. FWIW I found an old thread with a similar problem, but it doesn't seem related. What's going on here?

Last edited by Salkay (2018-11-28 08:25:18)

amish

Member

Registered: 2014-05-10

Posts: 475

Re: [SOL]warning: /boot/grub/grub.cfg saved as /boot/grub/grub.cfg.pacsave

Thats because grub.install file moves grub.cfg.pacsave back to grub.cfg

https://git.archlinux.org/svntogit/pack … kages/grub

post_upgrade() {
  # We used to package /boot/grub/grub.cfg, but there is no reason to.
  # Remove the file from package, but move real file back in place.
  if [ ! -f /boot/grub/grub.cfg -a -f /boot/grub/grub.cfg.pacsave ]; then
    mv /boot/grub/grub.cfg.pacsave /boot/grub/grub.cfg
  fi
}

PS: grub.cfg used to be part of grub package. Its no more the case.

Last edited by amish (2018-11-28 07:26:50)

Salkay

Member

Registered: 2014-05-22

Posts: 644

Re: [SOL]warning: /boot/grub/grub.cfg saved as /boot/grub/grub.cfg.pacsave

Thats because grub.install file moves grub.cfg.pacsave back to grub.cfg

Oh, that's… odd. Thanks for the clarification!

RalphCorderoy

Member

Registered: 2017-01-25

Posts: 27

Re: [SOL]warning: /boot/grub/grub.cfg saved as /boot/grub/grub.cfg.pacsave

I arrived here having the same confusion. This is a one-off warning on upgrading grub; it shouldn't occur next time. See 2018-12-09's email from Eli: https://lists.archlinux.org/pipermail/a … 45827.html

Salkay

Member

Registered: 2014-05-22

Posts: 644

Re: [SOL]warning: /boot/grub/grub.cfg saved as /boot/grub/grub.cfg.pacsave

Thanks for chasing that up and reporting back here. Good to know!