[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#766000: RFS: id3lib3.8.3/3.8.3-16



Am Sonntag, den 26.10.2014, 15:34 +0100 schrieb Stefan Ott:
> On 10/26/2014 01:43 PM, Tobias Frost wrote:
> > (I do not intend to sponsor this package)
> > 
> > Stefan, 
> > your package does contain lintian warnings. Many sponsor will not even
> > look at your package with warnings present, so I advise you to fix them.
> 
> Hi Tobias
> 
> Thanks for the advice. Most of the current lintian warnings are
> "pedantic" or "wishlist" and some of them directly affect the build
> process. Since this upload adds multi-arch support to the package I
> didn't want to mess too much with other aspects of building the package
> - I'd rather have just one major building-related change per package
> revision, makes it a bit easier to find bugs.

<pedantic> There are no "wishlist" lintian messages </pedantic>

> Also, the warning about dev-pkg-without-shlib-symlink (which is the only
> real complaint from lintian that I see) is IMHO not entirely correct.
> lintian seems to expect a symlink called "libid3-3.8.so" while the
> policy manual says "The development package should contain a symlink for
> the associated shared library without a version number". I'm assuming
> that this is because the id3lib package has not seen an upstream release
> in over a decade and we are carrying lots of packing-related information
> in our version strings these days (such as the "c2a" from the C++ ABI
> change in 2005). I could of course just add a lintian override and be
> done with it but I figured it would be better to keep this warning
> around as a reminder for me to look into the issue.

I'm have doubts. I think lintian is right. You know what's your library
name and you know the version part? I'm not an library guru, but I think
the library name is "libid3-3.8" and the version is 3.0.0, so lintian
expectd a symling from  usr/lib/x86_64-linux-gnu/libid3-3.8.so to
usr/lib/x86_64-linux-gnu/libid3-3.8.so.3.0.0 

For the other messages, at least P no-dep5-copyright are easily fixable
and dep5 is IMHO now considered as best-practice.

just my 2 cents.

> Anyway, I *did* upload a new version which fixes a small issue with the
> previous upload and I'm looking forward to additional comments. If
> anyone feels the urge to upload it that would be appreciated.
> 
> cheers

--
tobi

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: