Hey Andreas, On Wed, Jan 8, 2014 at 1:14 PM, Andreas Tille <[email protected]> wrote:
> :-) > > It is good to build a positive feeling about gbp to come over the hard > times you might have in some point in time. Sometimes it takes a bit > longer to make real friends between a developer and gbp. ;-) > > hehe! I am definitely liking it. But I suppose I like it because a lot of the hard work was done before I started using it. :) > > One of the first bugs pointed out by lintian: > > > > $ lintian -i snp-sites_1.0-1_amd64.changes > > W: snp-sites source: package-needs-versioned-debhelper-build-depends 9 > > ... > > > > Because I am using compat level 9 I guess I can override this flag? > > No. Lintian tells you exactly what you need to do. *Since* you are > using compat level 9 you really *need* to bump also the versioned > Build-Depends to 9 (currently you have 8). This is not the kind of > warning you should override at all. > Cool. Thanks for clarifying that. > > > Also, this one has been worrying me for quite sometime: > > > > W: libsnp-sites1: non-dev-pkg-with-shlib-symlink > > usr/lib/x86_64-linux-gnu/libsnp-sites.so.1.0.0 > > usr/lib/x86_64-linux-gnu/libsnp-sites.so > > N: > > N: Although this package is not a "-dev" package, it installs a > > N: "libsomething.so" symbolic link referencing the corresponding > shared > > N: library. When the link doesn't include the version number, it is > used > > by > > N: the linker when other programs are built against this shared > library. > > N: > > N: Shared libraries are supposed to place such symbolic links in their > > N: respective "-dev" packages, so it is a bug to include it with the > main > > N: library package. > > N: > > N: However, if this is a small package which includes the runtime and > the > > N: development libraries, this is not a bug. In the latter case, > please > > N: override this warning. > > N: > > N: Refer to Debian Policy Manual section 8.4 (Development files) for > > N: details. > > N: > > N: Severity: normal, Certainty: possible > > N: > > N: Check: shared-libs, Type: binary, udeb > > N: > > > > > > I'm not yet sure how to fix it, but I'll see what I can do. > > Creating library packages is a bit more advanced task. Since you have > decided to be brave and created these you should finish the hard way, > thought. It was Sasha's recommendation. And a good recommendation at that. > I really like to use d-shlibs which is implementing the Debian > Library packaging guide automatically. The expense you have to pay is > to learn how to deal with d-shlibs and its pickyness to some extend. > IMHO the easiest way is to copy some example and I'd recommend for > instance > > svn://anonscm.debian.org/debian-med/trunk/packages/volpack/trunk/ > > You should have a look into its rules file and its control file. > D-shlibmove will tell you everything else you need to do - if it is > not verbose enough for you feel free to keep on asking. > > For sure you can move around the files manually without d-shlibs but the > *.a file needs to go to the *-dev package as well as the *.so symlink. > > Hope this helps > This helps immensely. Thanks a lot for all the help you've been giving me. Kind regards, Jorge
