@DorianWinty Would be useful to apply https://laravel.com/docs/9.x/upgrade so we're really up to date.

I forgot about DirectoryIterator and the glob pattern, could be more convenient than the glob() method we wrap.

Everytthing work

the stendard will aaa_bbb and not AaaBbb

2013-01-19 03:51:09 UTC comment:

If we want to have it in the multi-services container, run like a charm through runit, without any need for the environment:

@DorianWinty That one could be a candidate to publish at rSCHEMA too.

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

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.

We need this, as container still runs on Jessie, and, as such, doesn't provide a recent enough Git version to be compatible with Phabricator.

Furthermore, Jenkins CD uses the deploy account to publish static website updates on Ysul through:

Can't repro with current Etherpad version.

As the port is maintained, the best course of action is to send a patch for this port upstream.

Works fine on WindRiver with ImageMagick 7 and Wikimedia Commons pictures of the day from February 2020 as test:

We can wait upstream updates for the ImageMagick 7 API, especially as upstream was active in November 2019.

Still GID to do.

I need this task to solve T1572.

5.4 migration is done for the running source code, but tests require to cope with the undocumented internal framework mechanisms changes for events.

The migration is generally a straightforward class replacement (they are now sorted in namespace)

See also T100.