[arch-dev-public] keep config file on system when upgrading to package without the config file
aaronmgriffin at gmail.com
Wed Mar 17 21:07:12 CET 2010
On Wed, Mar 17, 2010 at 3:03 PM, Daenyth Blank <daenyth+arch at gmail.com> wrote:
> On Wed, Mar 17, 2010 at 16:01, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
>> In which case the behavior is normal and expected, yes? I mean, if I
>> understand the new grub2 correctly, there should be no config, but the
>> mkconfig command needs to be run.
> I think the issue was that the maintainer didn't realize removing it
> from backup would remove it from user systems. I don't have the thread
> at hand right now.
Pacman should even handle that. The backup array is checked for both
the incoming package and the outgoing one, for stuff like this.
Now if it was never in the backup array to begin with, that's another story
More information about the arch-dev-public