@douardda's work for cast exchange
referenced to not lose it

• README: Fix link to template documentation

Remove unneeded instructions from documentation

• Initialize terraform/proxmox to build vm
• init-template: Convert to markdown

• init-template: Convert to markdown

So turns out an automount unit was mounting back silently the mount point.
So there was a slight misunderstanding of what actually happened:

My two cents
I think landing by reviewer is a good idea, because when the diff is passed(accepted to land), author can still make changes in it and push it, and that changes might not be good one.
This could be a potential threat to code quality and other factors.
On the other hand, landing by reviewer would add one more task in their plate.

See T1234's amended description

Branch diff to another branch

In D1516#34010, @olasd wrote:

I'm not convinced this is such a good idea; this machine is way more than a "db replica" server (it only has one replica, most its databases are actually primary) and I don't think DNS provides the appropriate granularity level to record this information.

I'm not convinced this is such a good idea; this machine is way more than a "db replica" server (it only has one replica, most its databases are actually primary) and I don't think DNS provides the appropriate granularity level to record this information.

This org-mode source got exported to mediawiki.

As of rDLSGH533f6fa1a3dc, the GitHub lister uses swh.storage instead of SQLAlchemy.

The transfer is now in progress on uffizi:/srv/softwareheritage/mirros/gitorious.org/, within a screen session of my user with title "gitorious-transfer".

ardumont closed this task as "Wontfix".

s3 downloaded contents can be injected in swh.
worker01 is currently doing it.

As of yesterday, 10M were done.

Multiple problems:

• slow
• ssh connection problems when too many concurrent jobs (either with ssh multiplex or with simple scp).

Query sample to update jsonb field:

The files mentioned are only the ones with size <= 100Mib for now.

worker01 is producing messages in the swh_antelink_sesi_download queue.
Each message represents either roughly 100Mib of compressed files or 1000 compressed files to scp.

Important: we want to provide these informations *for all the content stored in SWH*

Depending on the form of the archived code, and the needs of the user that reference it, a variety of different references may be needed
Here is the original list from the team meeting, that completes the one mentioned in the ticket.

We are now all set to start (after having automated it properly…) the transfer of Gitorious stuff to SWH.

This has been fixed a while ago, for both debian and tarball ingestion.