573958ce64
Depending on some instances, we have some specific heuristics, some instances: - have summary pages which do not not list metadata_url (so some computation happens to list git:// origins which are cloneable) - have summary page which reference metadata_url as a multiple comma separated urls - lists relative urls of the repository so we need to join it with the main instance url to have a complete cloneable origins (or summary page) - lists "down" http origins (cloning those won't work) so lists those as cloneable https ones (when the main url is behind https). Refs. swh/devel/swh-lister#1800
13 lines
145 B
Text
13 lines
145 B
Text
python_debian
|
|
requests
|
|
setuptools
|
|
iso8601
|
|
beautifulsoup4
|
|
launchpadlib
|
|
tenacity >= 6.2
|
|
lxml
|
|
dateparser
|
|
dulwich
|
|
testing.postgresql
|
|
psycopg2
|
|
repomd
|