.

@odoo/rd-security

Eit: Nevermind this won't be enough, will need to vendor urls I think

@Xavier-Do this pull request has forward-port PRs awaiting action (not merged or closed):

• [FW][FIX] *: adapt for noble #159994

@Xavier-Do this pull request has forward-port PRs awaiting action (not merged or closed):

• [FW][FIX] *: adapt for noble #160449

@Xavier-Do this pull request has forward-port PRs awaiting action (not merged or closed):

• [FW][FIX] *: adapt for noble #160841
• [FW][FIX] *: adapt for noble #160842

@Xavier-Do this pull request has forward-port PRs awaiting action (not merged or closed):

• [FW][FIX] *: adapt for noble #160853

Hello, @Xavier-Do , I believe this PR breaks a test here :

You can view an example on the branch 17.0-run-tests of this DB https://logipren.odoo.com/_odoo/support/

We will check that, you can disable this test waiting for a fix :)

Perfect thanks ! I'm not in a hurry so it's fine, I'm happy to know you guys are going to take a look :)

Perfect thanks ! I'm not in a hurry so it's fine, I'm happy to know you guys are going to take a look :)

We made a fix pr to make the test more robust, we are still investigating to understand why this tz is missing on odoosh but the purpose of this test is mainly to check that the mapping gives the same result if both tz exists. So once #160868 is merged the issue should be solved, tell us if the problem persist after that :)

@Xavier-Do this pull request has forward-port PRs awaiting action (not merged or closed):

• [FW][FIX] *: adapt for noble #160853

Hello, @Xavier-Do , I believe this PR breaks a test here :

This made it into the most recent odoo:15 docker image, suggesting that the release process does not ensure that only ✅ docker images are published.

Hello, @Xavier-Do , I believe this PR breaks a test here :

This made it into the most recent odoo:15 docker image, suggesting that the release process does not ensure that only ✅ docker images are published.

The official docker images are not made to run tests, a lot of tools are missing on the images to do that.

The official docker images are not made to run tests, a lot of tools are missing on the images to do that.

Right, but if the tests failed, why was the image created?

The test only fails if the os is in a particular state. After our investigation it was more a mistake in the tzdata package.
The docker image is build automaticaly, the test are not ran, it is not the purpose of this image. The image is valid, even with this failing test.