I rebased the patch on the newest version and filed a new MP at [1].
The package is available in a PPA at [2].
When I first prepared this patch, I stumbled upon [3], where there was some resistance in hard coding a compression format upstream due to the technical debt it could cause. Specially when we would want to revert the change once [4] is accepted. Still, I am submitting it there as suggested [5].
I ran the dep8 test suite locally, here is the result summary:
On a note for my future self, when reviewing this bug I started wondering (for the second time) why we are only seeing this in Debian an not in older Ubuntu releases. The reason is because zstd support was back-ported all the way down to xenial.
I rebased the patch on the newest version and filed a new MP at [1].
The package is available in a PPA at [2].
When I first prepared this patch, I stumbled upon [3], where there was some resistance in hard coding a compression format upstream due to the technical debt it could cause. Specially when we would want to revert the change once [4] is accepted. Still, I am submitting it there as suggested [5].
I ran the dep8 test suite locally, here is the result summary:
On a note for my future self, when reviewing this bug I started wondering (for the second time) why we are only seeing this in Debian an not in older Ubuntu releases. The reason is because zstd support was back-ported all the way down to xenial.
[1] https:/ /code.launchpad .net/~athos- ribeiro/ ubuntu/ +source/ autopkgtest/ +git/autopkgtes t/+merge/ 412406 /launchpad. net/~athos- ribeiro/ +archive/ ubuntu/ autopkgtest- use-xz/ +packages /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 883167 /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 892664 /salsa. debian. org/ci- team/autopkgtes t/-/merge_ requests/ 133
[2] https:/
[3] https:/
[4] https:/
[5] https:/