Brian May writes:
> Yes, have considered that myself. However, the SONAME doesn't change
> very frequently on these libraries. In fact I think some of these
> libraries the SONAME never have changed since I started maintaining
> them.
Yeah, that's not surprising. I'll be surprised if upstream e
On 20 March 2010 10:53, Russ Allbery wrote:
> For that, if I were you I'd drop the -heimdal from any library package
> that doesn't actually conflict with an MIT Kerberos library package, which
> is the majority of the cases. I don't see any obvious reason why, say,
> libkafs0 or libhx509-5 need
Brian May writes:
> The other issue with the package-name-doesnt-match-sonames tag remains.
For that, if I were you I'd drop the -heimdal from any library package
that doesn't actually conflict with an MIT Kerberos library package, which
is the majority of the cases. I don't see any obvious rea
On 19 March 2010 16:43, Russ Allbery wrote:
> Yes, note the missing ~ in the version number in the dependencies. The
> version shlibs creates a dependency on is different (higher) than the
> package version and therefore can't be satisfied by it. This is why the
> libraries are currently uninsta
Brian May writes:
> W: libhx509-5-heimdal: shlibs-declares-dependency-on-other-package
> libhx509-5-heimdal (>= 1.4.0git20100221.dfsg.1)
[...]
> The package-name-doesnt-match-sonames is an old issue, the
> shlibs-declares-dependency-on-other-package is a new one that makes no
> sense to me. Ha
Package: lintian
Version: 2.3.3
Severity: normal
W: libkafs0-heimdal: package-name-doesnt-match-sonames libkafs0
W: libhx509-5-heimdal: package-name-doesnt-match-sonames libhx509-5
W: libhx509-5-heimdal: shlibs-declares-dependency-on-other-package
libhx509-5-heimdal (>= 1.4.0git20100221.dfsg.1)
W
6 matches
Mail list logo
