Source: libzia Version: 4.36-1 Severity: normal Hello, I am working to update tucnak and libzia to 4.37 and am finally fully grokking something Christoph mentioned a while back about the tight coupling between these packages. The libzia-4.37 package is ready to upload. However, doing so will immediately break the current version of tucnak in the archive until it is rebuilt, since it expects to find /usr/lib/<triplet>/libzia-4.36.so. Only to see if it would work, I tested the version of tucnak 4.36 in the archive against a locally install libzia-4.37 by creating a symlink. This works fine, but the current situation seems generally "broken." Is there a reason why libzia shouldn't install a libzia.so or libzia.0.so symlink to the currently installed version of the library so we can potentially upgrade the library without necessarily breaking tucnak installs (and vice-versa)? Or if there is a good reason why this will never work, should we combine tucnak and libzia into a single package? Thanks, tony
Attachment:
signature.asc
Description: PGP signature