- Apr 21, 2022
-
-
Jenkins for Software Heritage authored
-
Jenkins for Software Heritage authored
Update to upstream version '3.0.0' with Debian dir 09d4482132a835ebc53013aa28657fa00d7b2ed1
-
vlorentz authored
- Apr 20, 2022
-
-
vlorentz authored
For consistency with VCS loaders. A future commit will introduce more code shared between package and VCS loaders, and will need to use this attribute.
-
- Apr 19, 2022
-
-
vlorentz authored
-
- Apr 14, 2022
-
-
Jenkins for Software Heritage authored
-
Jenkins for Software Heritage authored
Update to upstream version '2.6.2' with Debian dir ff9c2dde9f4ad09d1f81ed036a94465ca60c82c6
-
Antoine R. Dumont authored
Prior to this commit, the test data were in the wrong format. They were passing along an url within the artifact parameter which is not provided by the lister. This fixes the inconsistency. Related to T3874
- Apr 08, 2022
-
-
Antoine Lambert authored
-
Antoine Lambert authored
Related to T3922
-
Antoine Lambert authored
black is considered stable since release 22.1.0 and the version we are currently using is quite outdated and not compatible with click 8.1.0, so it is time to bump it to its latest stable release. Please note that E501 pycodestyle warning related to line length is replaced by B950 one from flake8-bugbear as recommended by black. https://black.readthedocs.io/en/stable/the_black_code_style/current_style.html#line-length Related to T3922
-
Jenkins for Software Heritage authored
-
Jenkins for Software Heritage authored
Update to upstream version '2.6.1' with Debian dir f47640479f60ac5953ae27bed149658969098344
-
Antoine R. Dumont authored
This has been changed in latest swh.deposit v1.0 Related to T4125
-
- Apr 07, 2022
-
-
vlorentz authored
Just in case they also vary despite using the same id.
-
- Mar 30, 2022
-
-
vlorentz authored
In at least one occurence, replicate.npmjs.com shows the exact same tarball for two different versions. As we only used the shasum to identify a release (formerly revision) when loading incrementally, this causes two ExtIDs to be created for the same target, which causes a crash when re-loading incrementally (formerly, this caused duplicate branches' revision to be replaced by the other one). For example, https://archive.softwareheritage.org/swh:1:snp:9fe3ba7515a9b567ab7f66e20d1f4ff7f9f5cf23;origin=https://www.npmjs.com/package/koreanbots has a branch named "releases/3.0.0-alpha3" which points to a revision with the right date and directory, but "3.0.0-beta" as commit message. This may have been caused by both revisions having the same directory. This seems to have confused the next load of the loader, whose result can be seen at https://archive.softwareheritage.org/swh:1:snp:e9dca2ee671f8d12a0163fe4cacfc61eabf7d8fe;origin=https://www.npmjs.com/package/koreanbots as it used the revision in the "releases/3.0.0-alpha3" branch as the target of the "releases/3.0.0-beta" branch.
-
- Mar 22, 2022
-
-
Antoine Lambert authored
Due to test modules being copied in subdirectories of the build directory by setuptools, it makes pytest fail by raising ImportPathMismatchError exceptions when invoked from root directory of the module. So ignore the build folder to discover tests.
-
- Mar 02, 2022
-
-
Jenkins for Software Heritage authored
-
Jenkins for Software Heritage authored
Update to upstream version '2.6.0' with Debian dir c4bb5079cf38d1e373751e7598339fabbf018b7d
- Mar 01, 2022
-
- Feb 25, 2022
-
-
Jenkins for Software Heritage authored
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
Related to T3973 Related to T3976 (drop this when this task is dealt with)
-
Antoine R. Dumont authored
-
Jenkins for Software Heritage authored
Update to upstream version '2.5.4' with Debian dir 2bc3748c932323f6e57d1fb7885a5f6d22e2a2eb