Matt Zimmerman <[EMAIL PROTECTED]> (15/11/2007):
> "The run-time shared library needs to be placed in a package whose
> name changes whenever the shared object version changes."
> 
> If you do not pay attention to this issue, then when the soname of
> this library changes, you will break upgrades for all of its users.

And? The soname version isn't present in the package name (rather soname
version+1). I don't see what the policy violation is. As you quoted, the
name as to change when the shared object version changes. And such a
change didn't seem to have happened. What's the actual breakage?

> So regardless of how severe you think this issue is with regard to the
> requirements of Debian policy, please do fix it.

The only issue I can see here is a cosmetic one, and gratuitously
renaming packages sounds a bad idea to me.

-- 
Cyril Brulebois

Attachment: pgpirpRsYuGCT.pgp
Description: PGP signature

Reply via email to