move e2fsprogs dependency from fork to upstream#1254
Conversation
|
|
|
It is very strange, that the failure https://github.com/onekey-sec/unblob/actions/runs/17400208989/job/49391774625?pr=1254#step:5:1047 happens only in one of the python environments, not all of them. |
It's affecting all of them, it's just that the others got cancelled. If a failure is observed in one of the tests, the others are cancelled. |
we may run the tests inside docker or force install e2fsprogs from debian |
95e44c1 to
a221185
Compare
|
Chose to run tests in docker container with Ubuntu 25.10 but building dev dependencies (taplo, specifically) is .. difficult. |
7867a75 to
4221e65
Compare
|
We need this #1368 first |
10dc348 to
d24edae
Compare
3a04593 to
40e7bc1
Compare
Our debugfs fix¹ is present in the debian trixie version² and in latest Ubuntu³. We can therefore go back to installing it from upstream rather than relying on our own fork. ¹: tytso/e2fsprogs@56a444e ²: https://metadata.ftp-master.debian.org/changelogs//main/e/e2fsprogs/e2fsprogs_1.47.2-3_changelog ³: https://launchpad.net/ubuntu/+source/e2fsprogs
This reverts commit c13a053.
90197a2 to
00d6416
Compare
00d6416 to
990c497
Compare
Our debugfs fix is present in the debian trixie version and in latest Ubuntu. We can therefore go back to installing it from upstream rather than relying on our own fork.
Which means we can revert c13a053 and move to Debian Trixie for the Docker container.