Date: Thu, 23 Apr 2026 22:22:40 +0100 From: Lexi Winter <ivy@freebsd.org> To: stable@freebsd.org, pkgbase@freebsd.org Subject: Re: [HEADS UP] stable/15: new base packages for PAM, zstd Message-ID: <aeqNoNk-Mhc45WZr@amaryllis.le-fay.org> In-Reply-To: <23bb166c-ec8e-4c98-b03c-5fbc7f364f2a@yahoo.com> References: <adTq6tMP4GWQS35e@amaryllis.le-fay.org> <aeedOZ7VcQAOsQCV@cmplx.uk> <3847a70c-f2d8-4c4a-a5f0-56a4a90168b0@yahoo.com> <aeh6ddAuDClL4YFn@cmplx.uk> <aek7L4X26D0zQTU-@amaryllis.le-fay.org> <23bb166c-ec8e-4c98-b03c-5fbc7f364f2a@yahoo.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Mark Millard wrote in <23bb166c-ec8e-4c98-b03c-5fbc7f364f2a@yahoo.com>: > A 14.x FreeBSD-runtime package would be replaced by a 15.0-RELEASE-p4 > package would it not (if that pkgbase -> pkgbase upgrade is the type of > upgrade that was done)? Would that produce a .pkgsave file for the > /etc/master.passwd (given the RE-unsupported nature of 14.* pkgbase)? from pkg's point of view, it doesn't matter what the old version number of the package is; if the package is being upgraded, it will not overwrite configuration files. this would only happen if master.passwd was not marked as @config in 14, but i'm fairly sure it was. a couple of files were missing @config, but that wasn't one of them. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaeqNnQAKCRD1nT63mIK/ YEQ5AQDt+h3QtqORFjBZMh5NK/1rZndggnu8qPKqfWg9216KVAD/Urk9ijhOWLCI Wo01fFGh1+vjPG5r03jabMcpjY4B9ww= =0z41 -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aeqNoNk-Mhc45WZr>