Re: [HEADS UP] stable/15: new base packages for PAM, zstd

On Wed, Apr 22, 2026 at 10:01:20AM -0700, Mark Millard wrote:
> It is too bad that the pkg upgrade and the pkg install man pages do not
> document the .pkgsave and .pkgnew behavior and how to handle handle
> them. The wiki is not part of what installs on the local FreeBSD system
> as documentation.
> 
> Far more files than the wiki materials list can be affected, including
> scripts and such. I've also had examples of configuration files:
> 
> /etc/group.pkgsave /etc/group
> /etc/hosts.pkgsave /etc/hosts
> /etc/sysctl.conf.pkgsave /etc/sysctl.conf
> /etc/shells.pkgsave /etc/shells
> 
> /etc/ssh/sshd_config.pkgsave /etc/ssh/sshd_config
> So, after adjustment, also needing: service sshd restart
> 
> /.profile.pkgsave /.profile
> /.shrc.pkgsave /.shrc
> /root/.profile.pkgsave /root/.profile
> /root/.shrc.pkgsave /root/.shrc
> /usr/home/root/.profile.pkgsave /usr/home/root/.profile
> /usr/home/root/.shrc.pkgsave /usr/home/root/.shrc
> 
> /etc/rc.subr.pkgsave /etc/rc.subr
> /etc/rc.pkgsave /etc/rc
> /etc/defaults/rc.conf.pkgsave /etc/defaults/rc.conf
> /etc/kyua/kyua.conf.pkgsave /etc/kyua/kyua.conf
> /etc/periodic/daily/223.backup-zfs.pkgsave
>    /etc/periodic/daily/223.backup-zfs
> 
> /etc/mail/*.pkgsave
> /etc/mtree/*.pkgsave
> 
> Most of those I've not had an example of in a long time.
> 
> Even normal system programs/libraries can get such *.pkg* files. For
> example, if one has patched a program or library locally and then a
> later update has to deal with the patched file. The patched file can be
> saved (.pkgsave) or the new file can be separately saved (.pkgnew).
> 
> Checking for such files via find or the like is a good idea.
> 
> Similar points apply to any chroot worlds and/or jail worlds that happen
> to be pkgbase based.

yes, there are lots of those:

# find / -type f -name "*.pkgsave" | wc -l
     155

most under /rescue:

root@aob:~ # find /rescue -type f -name "*.pkgsave" | wc -l
     149

Anton