Update to upstream version '2.1.1'
with Debian dir 875ca28c2424bcb722c329226364dcce462de9fe

Turns these references into simple links in order for the rst checks
performed by PyPI to pass when uploading a new package version.

As the known_first_party isort option was not set yet, previous
imports ordering got broken so restore it.

It was placed in mypy.plugins.django-stubs section so it was not
taken into account.

The former does not always plays well with PEP420...

Update to upstream version '2.0.0'
with Debian dir 47794cbfa30288bb946314a5377d461aced389c0

vlorentz authored 1 year ago and vlorentz committed 1 year ago

It was deprecated years ago, and no client used it in staging or prod
since 2022-04-11

vlorentz authored 1 year ago and vlorentz committed 1 year ago

These are Codemeta terms, but they were used in the Atom namespace.
As they are not read by the tests using them, we can just remove them.

vlorentz authored 1 year ago and vlorentz committed 1 year ago

A future commit will reject these invalid tags

vlorentz authored 1 year ago and vlorentz committed 1 year ago

I found some deposits on staging which use
<entry xmlns="https://doi.org/10.5063/SCHEMA/CODEMETA-2.0"> instead

Update to upstream version '1.4.4'
with Debian dir bfe4348a86fbf037ddeaaad6842ec467143411d1

This ensures the deposit checks in the elastic infra (using azure objstorage) is
working. There is currently no way to prevent the content-encoding from being detected
and stored in the blobstorage (various tryouts have been tested to no avail). That
content-encoding, is then preventing the checking/reading to work (failing [2]).

Following the documentation, a workaround has been implemented to reset a posteriori the
content-encoding [1].

It's not proper but, from repl experimentation, it's working which is better than the
actual failure.

[1] https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-properties-metadata-python

[2]
```
HttpResponseError: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check'))
```

Refs. swh/infra/sysadm-environment#5129

Update to upstream version '1.4.3'
with Debian dir 5d705e553436af21a342fad000978b1f4f45899f

Use None instead of empty string to try to prevent content-encoding to be set when
writing.

Refs. swh/infra/sysadm-environment#5129

Update to upstream version '1.4.2'
with Debian dir 2b4aef9f7ac345385fda3320ce6b248a5c9e3950

Currently, the writing in the azure objstorage adds extra headers to the blobs. Which
prevents the correct reading of those blobs when checking the tarballs.

According to the documentation, this option opening should allow to configure more
appropriately.

Refs. swh/infra/sysadm-environment#5129

Update to upstream version '1.4.1'
with Debian dir ae89963d8b634ae2841b7c42ddbca165075036a3

If done on the full path, the conditional technically fails the check for the wrong
reason. This also adds tests on this case.

Refs. swh/infra/sysadm-environment#5129

Update to upstream version '1.4.0'
with Debian dir e0639530ad4e76de52dee4a5738eef298948d9d9

Refs. swh/infra/sysadm-environment#5129