Hi all, I am currently wondering why the testing autopkgtests for suricata are failing [0] due to a missing dependency on libssl3 (= 3.1.5-1) via libssl-dev. That libssl3 version exists in testing [1, 2] but not in unstable (likely because of the t64 transition?). I would expect this testing test to use the testing version of the library though, right? The test itself is special only in that one of the jobs uses the "build-needed" restriction keyword to build a version of Suricata with unit tests enabled, just for testing purposes in one of the tests. ATM I am unsure what to do -- or if there is anything to do for me at all of if I only have to wait until the transition is over. Since the autopkgtests are gating for testing migration, I am inclined to remove that one test that needs "build-needed" to get things going since it would not test the actually installed package anyway. OTOH I acknowledge that running the unit tests at some point would be useful, if the build would ever get that far ;) Any ideas? Thanks in advance for any pointers. Best regards Sascha[0] https://ci.debian.net/data/autopkgtest/testing/amd64/s/suricata/45660670/log.gz
[1] https://packages.debian.org/trixie/libssl-dev [2] https://packages.debian.org/trixie/libssl3
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature