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

Re: PAM module packaging help

I have started a debian package by following the example of libacl. I apologize for being confusing but since I know hardly anything about debian packaging, I don't really know what to ask to get started. So to start, for my shared library, could you recommend a good shared library example that I can follow. If libacl is fine, I am stuck with the following lintian warnings:

Now running lintian...
W: mypackage source: binaries-have-file-conflict libmypackage-dev libmypackage1 usr/lib/i386-linux-gnu/libmypackage.so
W: mypackage source: binaries-have-file-conflict libmypackage-dev libmypackage1 usr/lib/i386-linux-gnu/libmypackage.so.1
W: mypackage source: binaries-have-file-conflict libmypackage-dev libmypackage1 usr/lib/i386-linux-gnu/libmypackage.so.1.0.0
W: libmypackage1: non-dev-pkg-with-shlib-symlink usr/lib/i386-linux-gnu/libmypackage.so.1.0.0 usr/lib/i386-linux-gnu/libmypackage.so
W: mypackage: empty-binary-package
W: libmypackage-dev: package-name-doesnt-match-sonames libmypackage1

I am using bzr builddeb -- -us -uc to create the packages.


On Fri, Jan 22, 2016 at 5:37 AM, Gianfranco Costamagna <costamagnagianfranco@yahoo.it> wrote:
Hi, I don't understand what are you asking...

anyway, if you add the libfoo-dev to the build dependencies
you should be fine, as long as you have the shlibs:Depends substvar
on your runtime dependencies.

With some code/packaging we might provide better answers



Il Giovedì 21 Gennaio 2016 23:12, Karsten Rage <karstensrage@gmail.com> ha scritto:

I am looking for help packaging up my PAM module. I am prepared to add
my package to Debian. The PAM module depends on a shared library that
in turn, depends on two other shared libraries (libxml2 and
libssl). Both the PAM module and the shared library are open source on
GitHub and are written in C.

I have read over the packaging documentation but I can't get my head
around how to actually package the binaries up with the
proper dependencies

Reply to: