You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to XML Security Library News, the XML Security Library 1.3.0 release includes the following changes (trimmed to point out the relevant criminal activity):
pick a synthetic SONAME of our own; e.g., libxmlsec1.so.999.1.3 which includes three components: one that makes it clear we're working around past silly behaviour, and then the major and minor version from the upstream repository as apparently a move from 1.2 to 1.3 is allowed to break all the fine crystalware in the shop on the way in.
build and ship both the existing library and the breaking new library in the package together with appropriate links; probably we could put the old library under a facet so that it could be skipped as required. The compilation link would point to the new library.
An alternative is to move to a package name that includes the major and minor version; e.g., libxmlsec13 or whatever. We'd need to mediate the compilation link and the include files at that point, I think, and the libxmlsec13 package would have to have an optional dependency on a branch version bump of the libxmlsec1 package to get one that doesn't conflict, etc.
According to XML Security Library News, the XML Security Library 1.3.0 release includes the following changes (trimmed to point out the relevant criminal activity):
Literally no preparation for this has been made:
Sigh.
The text was updated successfully, but these errors were encountered: