Description of problem: The squirrelmail included in Fedora doesn't work with PHP 8. It was working on F34, and the upgrade to F35 broke it. There is absolutely nothing in any logs, it just shows a blank page with error 500. Upstream has fixed this, please update. From upstream: ANNOUNCE: PHP 8 Compatibility Oct 15, 2021 by Paul Lesniewski The nightly snapshots for versions 1.4.23 and 1.5.2 found on our download page include compatibility for the newest versions of PHP 8. We encourage all SquirrelMail administrators to use a recent snapshot of either version and as always, let us know if there are any fixes, additions or changes you think SquirrelMail would benefit from. Version-Release number of selected component (if applicable): squirrelmail-1.4.23-6.fc34.20190710.noarch How reproducible: always
Enabling debug logging in php.ini you can see the errors: Fatal error*: Array and string offset access syntax with curly braces is no longer supported in */usr/share/squirrelmail/functions/strings.php* on line *634* Many files have this syntax. Any ETA on at least a test RPM?
ping? package is broken
This package is orphaned. Anyone willing to pick it up?
I have a package built that works. Pretty trivial to build. How do I get this added to the repo?
Created attachment 1879470 [details] Spec file for current version of Squirrelmail This is what I used to rebuild squirrelmail. Also may need to fix the rpmnew files for dovecot to make it work. (/etc/dovecot/conf.d/10-ssl.conf and /etc/dovecot/dovecot.conf.)
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.