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
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 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
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
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
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
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
7 matches
Mail list logo
