avoiding problem with html in report

allready open D2527

folowed the comment

Looks good to me.

correcting code style

modify the report.xml template to a better one

rebase against main

setup-nodesource-deb to upgrade first to test this as Node 6 (sic) doesn't provide a version for bullseye.

Revert to previous version

• added XML support

Solution implemented in D2525: we use /var/service.

Don't forget novolume

On Debian Bullseye, /etc/service is a symlink to /etc/runit/runsvdir/current.

Done. Last step is to ensure applications dependent of this image works correctly under Buster and Bullseye.

Partially reverted in rDPHPVIIFPMbbffa7c609bd.

Call runsvdir-init

Don't deprecate runsvdir-init, even if runsvdir-start isn't shipped by runit, we can maintain how we launch runit

Address runsvdir-init deprecation

As a workaround, I've compiled Git to 2.35.1 inside DevCentral container.

Builds fine:

Should be the final state before archiving the repository. It's possible to build image, and it uses the last PHP version, but we won't maintain that (e.g. no port to Debian recent releases).

Restore /usr/local/sbin/runsvdir-init: applications container calls that file

PixelFed requires intl and sodium extensions.

We discovered author now maintains code in a Git repository: https://github.com/simon-budig/woof

In T1547#23264, @dereckson wrote:

If we upgrade image to bullseye, we'll also get Git 2.30.2, but I've a 403 currently with current Dockerfile at D2522, so needs to investigate.

If we upgrade image to bullseye, we'll also get Git 2.30.2, but I've a 403 currently with current Dockerfile at D2522, so needs to investigate.

Some notes about the CLI tool.

Done for the base image (excepted the TODO noted above), we need to test Notifications Center, Auth Grove, etc. against 7.4 deprecations, and if applicable blocks them to 7.2 or 7.3.

TODO: novolume/ is still in Jessie, apply rDPHPVIIFPM630b49d9b604 and rDPHPVIIFPMf4465d1a9419 changes here too.