Set ZIP strict_timestamps to false

[bpedersen2]

Since python 3.8 timestamps before 1980 are disallowed by default,
but seem to occur in streams.

Fixes: awx#12126

Signed-off-by: Björn Pedersen bjoern.pedersen@frm2.tum.de

[softwarefactory-project-zuul]

Build succeeded.

• ansible-build-python-tarball : SUCCESS in 5m 31s

[bpedersen2]

Hint: As python >=3.8 seems to be the minimum supported version we don't need a feature gate.

[AlanCoding]

I wrote a test for this fix: bpedersen2#1

I confirmed that it fails with the error you give in the issue, and passes with your fix here. We would like to capture test coverage when merging something like this. If you merge that commit or add it manually, this will have my support to merge.

[weiyentan]

@bpedersen2 @AlanCoding how do we get these changes? In what tag did the fix come in?
I used this image in my AWX environment
EE_BASE_IMAGE: 'quay.io/ansible/ansible-runner:stable-2.12-latest' and i am still getting this error when having contents in my collections.

[jinja2ninja]

I'm getting the same issue as @weiyentan on stable-2.12-devel

[weiyentan]

@fahcsim i am testing with 21

[Shrews]

FYI, the images on quay.io are not being updated, at the moment. We are working on a new container image release pipeline, which will likely include a new image tagging scheme. We ask for patience while we develop this process, which we hope to have finished soon. In the meantime, it is easy enough to build your own image based on the current release. For the 2.2 release, something along the lines of:

git clone https://github.com/ansible/ansible-runner.git
git checkout -b release_2.2 origin/release_2.2
docker build -t my_tag_name .

Use the release_2.1 branch if you prefer that release.

[weiyentan]

Thank you for your confirmation. What will set need to change in the image?