[pacman-dev] backup handling

Xavier shiningxc at gmail.com
Wed Sep 19 06:14:55 EDT 2007

On Wed, Sep 19, 2007 at 11:21:20AM +0300, Roman Kyrylych wrote:
> Thanks for bringing this up.
> I think it would be nice to have such files saved as .pacsave.
> But how many of those files (that were in NoUpgrade) still exist
> without backup information now? I think they are <0.1%.

Hmm, I was afraid this would be confusing/misleading :)
All my references to NoUpgrade don't refer to the static NoUpgrade definition
in /etc/pacman.conf , but the representation of it in pacman at runtime.

So pacman temporarily adds files a noupgrade list, so that remove_commit()
doesn't kill them. And when it's done, it removes them from the noupgrade
It never edits the NoUpgrade files in pacman.conf.

The case I described is when a config file that was in the backup array
leaves the backup array, like what happened with /etc/pacman.d/current.

More information about the pacman-dev mailing list