Thanks @vlorentz.
Is this something that can be fixed easily or should I ask the client to change the names on the deposited archives?

It should be easy to fix

I believe the right fix would be to change Django's storage class to deduplicate file
names in a different ways (add the random string as prefix, or create a dir):
https://docs.djangoproject.com/en/3.0/topics/files/#the-built-in-filesystem-storage-class

We (@vlorentz and I) agreed on a simpler fix: changing the upload file path on
the deposit model (which was already defined). Current implementation is thus
D3197.

Cheers,

Deployed.

Triggered a check (deposit id 650) and now everything is still fine.

Here is the path where archive are uploaded:

softwareheritage-deposit=> select dr.archive from deposit d inner join deposit_request dr on d.id=dr.deposit_id where d.id=650 and dr.archive is not null;
                    archive
-----------------------------------------------

 client_3/20200601-105256.359626/jesuisgpl.tgz

The timestamp 20200601-105256.359626 is built out of the deposit reception
date. So there should be no longer clash in names.

Closing this task. Feel free to reopen or comment if anything is wrong.

Cheers,