Re: upgrade glitches with php, maybe

[maya%NetBSD.org@localhost]

On Thu, Mar 27, 2025 at 03:25:39PM -0400, Greg Troxel wrote:
> >From the log:
> 
> 
> 2025-03-27T13:18:41Z [1/1] removing php-8.2.26...
> Package `php-8.2.26' is still required by other packages:
>         php82-mbstring-8.2.26
>         php82-sysvsem-8.2.26
>         php82-intl-8.2.26nb15
>         php82-zlib-8.2.26nb2
>         php82-sodium-8.2.26
>         php82-iconv-8.2.26nb1
>         php82-fpm-8.2.26nb11
>         php82-opcache-8.2.26
>         php82-pdo_sqlite-8.2.26nb15
>         php82-nextcloud-30.0.2
>         php82-posix-8.2.26
>         php82-pdo-8.2.26
>         php82-curl-8.2.26nb21
>         php82-exif-8.2.26
>         php82-gd-8.2.26nb9
>         php82-zip-8.2.26nb16
> 2025-03-27T13:19:52Z [23/138] upgrading php82-pdo-8.2.28nb1...
> 2025-03-27T13:21:26Z [57/138] installing php82-8.2.28...
> 2025-03-27T13:21:52Z [70/138] upgrading php82-posix-8.2.28nb1...
> 2025-03-27T13:21:54Z [71/138] upgrading php82-pdo_sqlite-8.2.28nb16...
> 2025-03-27T13:22:12Z [81/138] upgrading php82-sodium-8.2.28nb1...
> 
> (and more, but nothing remarkable)
> 
> 
> So somehow, the removal of php removed its config files, or something
> else did.
> 

I'll admit I'm not super familiar with the life cycle of config files...
but, I wonder whether the renaming of the PHP packages could be avoided,
so we won't have to use SUPERSEDES, avoiding this issue.

That does leave what happens to someone who had the intermediate PHP
installed and made local changes to the config, and I'm not sure how it
should be best handled. It's certainly less people affected.