Hi, On 20-11-2023 12:54, Adrian Bunk wrote:
It is a case where a binary tries to load the new soversion of the library and plugins for the old soversion of the library.
And, do we (as project) already have established processes where this is expressed correctly in package dependencies? Can that be done automatically (for packages that are likely to need it)?
I mean, in the ideal situation, this class of issues is prevented by proper package relations, but I also want to avoid manual labor that's a PITA to maintain and prone to wrong in the future.
Paul PS: I'll schedule the tests shortly
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature