patch: New 24199687 upstream release 0.10.2!

[github-actions]

The upstream 24199687 released new software version - 0.10.2!

This automated PR updates code to bring new version into repository.

[SuperQ]

I guess we need better handling of the gitlab project updates.

[mgariepy]

anyone can fix this ? the same issue blocks #474

for the latest release gitlab does do a 308 redirect that doesn't seems to be handled correctly by older version of python (<3.11) #474 (comment)

[gardar]

Since the issue seems to be that urllib in older python versions does not handle 308 redirects I wonder if changing the follow_redirects option for the url lookup would have any effect.
https://docs.ansible.com/ansible/latest/collections/ansible/builtin/url_lookup.html#parameter-follow_redirects or if we can avoid that redirect somehow by updating the checksum url

[mgariepy]

Since the issue seems to be that urllib in older python versions does not handle 308 redirects I wonder if changing the follow_redirects option for the url lookup would have any effect. https://docs.ansible.com/ansible/latest/collections/ansible/builtin/url_lookup.html#parameter-follow_redirects or if we can avoid that redirect somehow by updating the checksum url

from a quick tests it doesn't work with ansible.builtin.get_url when running ansible 2.14.0 on python 3.10.12 (from jammy utuntu python). Also the options was added on 2.10 so 2.9 would need to be bumped a bit.

[mgariepy]

Since the issue seems to be that urllib in older python versions does not handle 308 redirects I wonder if changing the follow_redirects option for the url lookup would have any effect. https://docs.ansible.com/ansible/latest/collections/ansible/builtin/url_lookup.html#parameter-follow_redirects or if we can avoid that redirect somehow by updating the checksum url

from a quick tests it doesn't work with ansible.builtin.get_url when running ansible 2.14.0 on python 3.10.12 (from jammy utuntu python). Also the options was added on 2.10 so 2.9 would need to be bumped a bit.

Also it's a gitlab.com issue here with the double '/' in the 302 redirect. would be better to have them fix the 302.

[mgariepy]

just created an issue concerning the gitlab problem: https://gitlab.com/gitlab-org/gitlab/-/issues/508161