Understood, so since the source package name changed from "php8.2" to "php8.4", the patches need to be applied again. Makes sense to have a checklist to go through patched source packages which (usually) change names in spring before a new Debian release, after transition freeze or maybe soft freeze.The problem is that the processes we use in raspbian for semi-automatically bringing changes forward are source package based, so things can get lost when Debian changes the source package name.The problem with PHP (Raspbian repo - so not your problem) is an issue though. It looks like Debian changed to use VFPv3 some time back, and previous Raspbian builds have changed that back to VFPv2 but it's been missed on PHP8.4 on trixie.
Btw, we are starting to test Debian + Raspbian testing versions (and provide images) moreless right after they are available, hence often recognize such issues early. If there was a public repository for Raspbian patches where we could open PRs/MRs, I'd do that, and could help with such chore work. Just an idea, but I know that setting this up and maintaining the repo itself adds some significant initial and also other ongoing maintenance efforts. Another benefit would be transparency and easier feedback/quality control of patches by volunteers.
Statistics: Posted by MichaIng — Thu Oct 23, 2025 1:20 pm