Contrary to other package loaders, a package can have multiple artifacts (per package version).
In those terms, we had to slightly adapt the swh.loader.package.loader.PackageLoader to demonstrate this.
Thus the impacts on pypi, npm, deposit modules as well.
ardumont retitled this revision from debian: Implement debian loader with package loader mechanism to package.debian: Re-implement debian loader within the package loader mechanism.Oct 15 2019, 2:41 PM2019-10-15 14:41:36 (UTC+2)
Because when i updated the diff against origin/master, it resetted the build's setup to build against origin/package-loader.
I triggered back the build against the right remote branch...
Ok, the head target for npm is 0.0.2 instead of 0.0.4 in the ci job (it's consistently ok locally :/)
So there is something amiss somewhere.
will check tomorrow.
there should not be mixed hex id and bytes id... checking...
ok that was one pb
somehow that works in current box!
wrongly
we are off in our snapshot branch computations
we no longer use the default_release, fortunately the ci caught it... (1 npm and 1 pypi tests failing for the same reason).