Unmaintained FreeBSD ports which are out of date

[portscout]

Dear port maintainers,

The portscout new distfile checker has detected that one or more
unmaintained ports appears to be out of date. Please take the opportunity
to check each of the ports listed below, and if possible and appropriate,
submit/commit an update. Please consider also adopting this port.
If any ports have already been updated, you can safely ignore the entry.

An e-mail will not be sent again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
emulators/libretro-ppsspp   | 1.17.1  | v1.18
+-+
emulators/ppsspp| 1.17.1  | v1.18
+-+
emulators/ppsspp-qt5| 1.17.1  | v1.18
+-+
graphics/py-ueberzug| 18.1.8  | 18.3.0
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Reported by:portscout!

Anybody seeing NextCloud crash?

[Kevin P. Neal]

I'm seeing a problem with NextCloud's php-fpm instance crashes when trying
to handle a request over the web interface. My web server is Apache 2.4
if it matters. The MacOS desktop sync client works just fine, and so does
the app from iOS 16 (I have an iPhone 8 that I'm upgrading soon).

Apache responds with a "Service Unavailable" error page.

In my /var/log/php-fpm.log I find this:

[03-Nov-2024 11:06:45] WARNING: [pool www] child 68236 exited on signal 4 
(SIGILL) after 5.975134 seconds from start

Every time I tried to reload a page on the web site I get a failure like
that one. The php-fpm processes are dying.

I use the checkrestart package after every pkg upgrade and I restart
anything that gets mentioned. This handy utility isn't foolproof, but
I've had good luck with it.

Reinstalling all my packages with pkg upgrade -f changed nothing.

I rolled back my ZFS dataset to October 30's, rebooted (needed, don't know
why), and I have it back up and running now.

I did "service php_fpm restart" after the bad update, but I forgot to check
that everything was still working. That's why I had to rollback so far --
I have SMS messages on my phone that imply it was working on that date.

The problem was introduced with one of these updates:

The following 11 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
openh264: 2.3.0,2
openjph: 0.17.0

Installed packages to be UPGRADED:
ffmpeg: 6.1.2_4,1 -> 6.1.2_5,1
glib: 2.80.5,2 -> 2.80.5_1,2
libheif: 1.18.2_1 -> 1.19.1
libnghttp2: 1.63.0 -> 1.64.0
libssh2: 1.11.0_1,3 -> 1.11.1,3
libvpx: 1.14.1 -> 1.15.0
pciids: 20240920 -> 20241024
py311-redis: 5.1.1 -> 5.2.0
svt-av1: 2.2.0 -> 2.3.0

Number of packages to be installed: 2
Number of packages to be upgraded: 9

I do have my own poudriere setup, but I don't think I have any custom
settings at this point. I can doublecheck if anyone is curious, though.

Anyone else seen this? Or should I file a bug report?
-- 
Kevin P. Nealhttp://www.pobox.com/~kpn/

   "I like being on The Daily Show." - Kermit the Frog, Feb 13 2001