Simson L. Garfinkel
Simson L. Garfinkel
> The problem you're having is due to putting the new E01 tests into `test/tools/vstools/test_mmls.sh`, which runs unconditionally, instead of `test/tools/vstools/test_mmls_E01.sh`, which runs only when Sleuthkit was compiled with E01...
> Wanting E01 support isn't the issue---it's having E01 support that's the problem. Tests which require E01 support ought not run when Sleuthkit is compiled without E01 support. > >...
> > But then what do we do about tests that require disk images if we don't have E01 support? > > I think I don't understand your question. >...
> > > But then what do we do about tests that require disk images if we don't have E01 support? > > > > > > I think I...
Well, we could manually convert the E01 to a .raw after it is downloaded in the host operating system. Are the tests important on every platform, or just some of...
In the GitHub actions runners we have E01 support everywhere in the libewf tools, do we not? On Tue, Nov 19, 2024 at 9:42 AM Joel Uckelman ***@***.***> wrote: >...
> No. E.g., the CI mingw builds are missing nearly all the optional dependencies: > > ``` > Building: > afflib support: no > libaff4 support: no > libbfio support:...
> > Well, we could manually convert the E01 to a .raw after it is downloaded in the host operating system. > > Wouldn't it be better to provide an...
Thanks to @uckelman-sf for helping me through this.
Tagging @bcarrier and @jayaramcs for awareness. I don't think that this will impact the Java interface.