Bug#657076: Updating and maintaining barry in Debian / Ubuntu
On Thu, Mar 01, 2012 at 09:26:34AM +0100, intrigeri wrote:
> The answer is basically "none". Once can maintain a package in Debian
> (as is: doing maintenance work, being responsible, and being in the
> Maintainer: control field) without any kind of special status.
Excellent!
In the latest Barry git tree, I've updated the debian packaging to
Standards-Version 3.9.1 (the latest for Squeeze) and the compat level
to 7 (the latest for Ubuntu 10.04 LTS). I can keep pressing forward
with the Standards-Version, but not the compat, since that halts builds
on older systems. But compat 7 isn't too bad.
I've also fixed some lintian errors. The following warnings remain:
> W: opensync0-plugin-barry: new-package-should-close-itp-bug
This can be ignored, I think.
> W: barrydesktop: binary-without-manpage usr/bin/bsyncjail
> W: barry-util: binary-without-manpage usr/bin/hal-blackberry
bsyncjail is used by the Desktop GUI to isolate the sync process,
in case opensync crashes. It is not meant to be run by the user.
Is there any harm in putting this in /usr/lib/barry or /usr/lib/barrydesktop?
Similarly for hal-blackberry... that is just a script run by HAL
to fill in device identification info. This could go in /usr/lib as
well.
Is it bad form to share a /usr/lib/barry directory between multiple
packages?
> W: barrydesktop: package-name-doesnt-match-sonames libosyncwrap18
This is a library only used by the Desktop GUI, and therefore packaged
right along with it. Someday it may be useful as a standalone library,
and could be packaged that way, but it is not ready for that yet.
I'm thinking this warning can be ignored for now too.
Barry 0.18 is not yet released yet, but the Debian packaging is just
about ready for when it is released.
- Chris
Reply to: