Control: severity -1 grave Hi Mikko,
Mikko Rasa, on 2024-10-10: > EDFbrowser contains a runtime check for libedf version. Since edfbrowser > 2.11 the required version of edflib is 1.27 (exact, not greater-or-equal). > If the version check fails, the UI is disabled and the program is unusable. > > Debian currently ships EDFlib 1.26, meaning that the versions of edfbrowser > in testing and unstable (2.11 and 2.12 respectively) cannot be used. Thanks for your report, my apologies, that's what happens when I work on too many packages at once. Our current automated test is superficial and would capture only some segmentation faults caused by libraries version mismatch, maybe a runtime check prompted to the terminal, but not a runtime check prompted through the graphical interface. I bumped the severity as this renders the package unusable. > Upstream has not made a release of EDFlib 1.27, which presumably is the > reason for Debian not having packaged it. However upstream also includes > an embedded copy of edflib in the edfbrowser repository, which is up to > date. Debian has removed this embedded copy in favor of using a shared > library package. > > The fix is probably to package a prerelease version of EDFlib 1.27, but I'm > filing this bug in edfbrowser because that's what's broken for me. Also it > would be a good idea to make edfbrowser depend on an exact version of > edflib, to match the runtime check in the code. Again, thanks for the report, it prompted me to liaise with upstream[1] to see whether the standalone EDFlib 1.27 can be released timely. If not, then I plan to revert the EDFbrowser package to 2.10 this evening UTC. [1]: https://gitlab.com/Teuniz/EDFlib/-/issues/19 Have a nice day, :) -- .''`. Étienne Mollier <emoll...@debian.org> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/1, please excuse my verbosity `-
signature.asc
Description: PGP signature
