Bug#751111: Improper shared lib package (SONAME contains python/tcl/java version)
severity 75 important thanks 2014-06-11 7:45 GMT+02:00 Mathieu Malaterre ma...@debian.org: severity 75 serious Again, stop doing it! I would like to hear also other's people opinions about this issue. Then I will agree to raise up the severity if the problem really serious. Thanks Anton I've even mentioned the debian policy section related to this issue, so keep the severity as required. On Tue, Jun 10, 2014 at 8:35 PM, Anton Gladky gl...@debian.org wrote: 2014-06-10 14:49 GMT+02:00 Mathieu Malaterre ma...@debian.org: Should be removed from the package since the SONAME will change when python 2.7 will not be the default python version (for example). It will unlikely happen: Python 2.7 is scheduled to be the last major version in the 2.x series [1] Switch to 3.x requires a lot of modifications and will definitely have a new soversion. [1] https://www.python.org/download/releases/2.7 So what ? The policy is pretty clear about that, it *will* make it difficult. The point is to make it easy before hand (when in doubt). Please fix your package and split python/tcl/java binding out of the shared package, they are totally unrelated (different SONAME). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751111: Improper shared lib package (SONAME contains python/tcl/java version)
On 11/06/2014 08:10, Anton Gladky wrote: severity 75 important thanks 2014-06-11 7:45 GMT+02:00 Mathieu Malaterre ma...@debian.org: severity 75 serious Again, stop doing it! I would like to hear also other's people opinions about this issue. Then I will agree to raise up the severity if the problem really serious. Well, the policy is pretty clear on the topic. And for users (and maintenance), it would be way better to have a package per binding. Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751111: Improper shared lib package (SONAME contains python/tcl/java version)
severity 75 serious thanks On Wed, Jun 11, 2014 at 8:10 AM, Anton Gladky gl...@debian.org wrote: 2014-06-11 7:45 GMT+02:00 Mathieu Malaterre ma...@debian.org: Again, stop doing it! You're the one doing the ping-pong. I did explain the severity in my original post, you did not (solely a comment about python). I would like to hear also other's people opinions about this issue. Then I will agree to raise up the severity if the problem really serious. What for ? The policy is clear, the shared package should not contains python, tcl, java and the Qt bindings (no clear ABI and not even a clear API). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751111: Improper shared lib package (SONAME contains python/tcl/java version)
severity 75 important thanks It is maintainer's prerogative of changing the severity of bug. Isn't it? 2014-06-11 8:55 GMT+02:00 Mathieu Malaterre ma...@debian.org: What for ? The policy is clear, the shared package should not contains python, tcl, java and the Qt bindings (no clear ABI and not even a clear API). The issue is only in Python27D-suffix, which will never change. I do not see problems here. Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751111: Improper shared lib package (SONAME contains python/tcl/java version)
Package: libvtk6.1 Version: 6.1.0+dfsg-5 Severity: serious This package provides 355 shared lib (different SONAME, but SOVERSION set to the same value). However as per policy: https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-runtime [...] If you have several shared libraries built from the same source tree, you may lump them all together into a single shared library package provided that all of their SONAMEs will always change together. Be aware that this is not normally the case, and if the SONAMEs do not change together, upgrading such a merged shared library package will be unnecessarily difficult because of file conflicts with the old version of the package. When in doubt, always split shared library packages so that each binary package installs a single shared library. [...] For example: $ readelf -d libvtkImagingColorPython27D-6.1.so.6.1.0 Dynamic section at offset 0xa020 contains 32 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [libvtkImagingColor-6.1.so.6.1] 0x0001 (NEEDED) Shared library: [libvtkWrappingPython27Core-6.1.so.6.1] 0x0001 (NEEDED) Shared library: [libvtkImagingCorePython27D-6.1.so.6.1] 0x0001 (NEEDED) Shared library: [libvtkCommonExecutionModelPython27D-6.1.so.6.1] 0x0001 (NEEDED) Shared library: [libpython2.7.so.1.0] 0x0001 (NEEDED) Shared library: [libvtkCommonCore-6.1.so.6.1] 0x0001 (NEEDED) Shared library: [libstdc++.so.6] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libvtkImagingColorPython27D-6.1.so.6.1] Should be removed from the package since the SONAME will change when python 2.7 will not be the default python version (for example). Indeed the SONAME contains the Python version (per upstream convention). Solution: Remove python, tcl and java specific binding out of this shared lib package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751111: Improper shared lib package (SONAME contains python/tcl/java version)
severity 75 important thanks 2014-06-10 14:49 GMT+02:00 Mathieu Malaterre ma...@debian.org: Should be removed from the package since the SONAME will change when python 2.7 will not be the default python version (for example). It will unlikely happen: Python 2.7 is scheduled to be the last major version in the 2.x series [1] Switch to 3.x requires a lot of modifications and will definitely have a new soversion. [1] https://www.python.org/download/releases/2.7 Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751111: Improper shared lib package (SONAME contains python/tcl/java version)
severity 75 serious thanks I've even mentioned the debian policy section related to this issue, so keep the severity as required. On Tue, Jun 10, 2014 at 8:35 PM, Anton Gladky gl...@debian.org wrote: 2014-06-10 14:49 GMT+02:00 Mathieu Malaterre ma...@debian.org: Should be removed from the package since the SONAME will change when python 2.7 will not be the default python version (for example). It will unlikely happen: Python 2.7 is scheduled to be the last major version in the 2.x series [1] Switch to 3.x requires a lot of modifications and will definitely have a new soversion. [1] https://www.python.org/download/releases/2.7 So what ? The policy is pretty clear about that, it *will* make it difficult. The point is to make it easy before hand (when in doubt). Please fix your package and split python/tcl/java binding out of the shared package, they are totally unrelated (different SONAME). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
