Bug#657076: Updating and maintaining barry in Debian / Ubuntu
On Sat, Mar 03, 2012 at 02:54:34PM +0100, intrigeri wrote:
> We don't wait until all previous Debian releases are EOL'd before we
> start following the latest Debian Policy. Please follow the latest
> available Standards-Version: Debian Policy 3.9.3 was released.
> See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz :)
Stable is what I had handy. I realize this is a work in progress.
I used the upgrade checklist to move from 3.8.0 to 3.9.1, without
much change needed.
> I agree compat level 7 is not too bad, and this is obviously not
> a blocker at all, but I must state I strongly dislike the idea of
> refraining from using compat level 9 in Debian before 2015, merely
> because nobody has uploaded a recent debhelper into lucid-backports.
> We manage to be slow enough, by ourselves, to adopt recent changes at
> Debian, without needing any such external help to get things stalled.
There's a large body of work on the opensync side that is not yet
visible to anyone in Debian. Maybe I can get that into Debian as well,
but I doubt it will make the Wheezy deadline.
> > 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.
>
> Putting two source packages into the same Git repository will be
> a pain. Let's talk about this other, new source package
> (opensync0-plugin-barry) later, and keep focused on the barry one to
> start with. By the way, I think the source package would be better
> called opensync-plugin-barry; and if it really needs to be a separate
> source package, Lintian is right, you need to fill an ITP for
> opensync-plugin-barry, and close it in its debian/changelog.
I named it opensync0 since that plugin depends on libopensync0, which
is available in Squeeze. The opensync-plugin-4x plugin depends on
libopensync1 which is not yet officially released, but does work.
That plugin is named opensync1-plugin....
In order to use both 0.22 opensync and 0.4x on the same system, the
specific naming was needed.
There used to be an opensync-plugin-barry in Lenny, as I recall.
According to the Barry PTS log (if I read it right), the entire set of barry
binaries was removed because of a python 2.6 issue, which was triggered
by opensync. Barry should not have been yanked due to that. Only
the opensync plugin.
But the entire opensync side of things can be postponed for now,
at least where Debian is concerned. The opensync subdirectories
do not get built automatically.
> IIRC /usr/lib/$BINARY_PACKAGE/$PROGRAM is appropriate, but please
> check the Debian Policy and FHS.
I couldn't find any mention of /usr/lib in the policy. Glad to see
my assumption was correct.
> I find it misleading to write "barry (0.18.0-1) unstable" in
> debian/changelog right now; I think it should only be done at the last
> minute, once the package is really ready to be uploaded to Debian
> unstable, which is not presently the case. Until this point is
> reached, I find it saner to:
>
> * either keep UNRELEASED instead of unstable
> * or manually manage lower-than-release but increasing version
> numbers (e.g. 0.18.0-1~1, 0.18.0-1~2, etc.)
> * or use git-dch to get automated lower-than-release but increasing
> version numbers
I'm not sure how this is misleading, since if it doesn't exist in
Debian, then Debian shouldn't care. If git-dch can completely eliminate
editing the changelog file, though, that might be worth looking into.
> Building in a sid chroot fails for me:
>
> checking for OPENSYNC22... no
> checking for OPENSYNC40... no
> configure: error:
> Unable to find development libraries for either opensync 0.22 or 0.4x.
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables:
>
> OPENSYNC22_CFLAGS and OPENSYNC22_LIBS
> or
> OPENSYNC40_CFLAGS and OPENSYNC40_LIBS
>
> to avoid the need to call pkg-config.
>
> See the pkg-config man page for more details.
>
> configure: error: ./configure failed for desktop
> make: *** [debian/stamp-autotools] Error 1
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>
> => missing build-deps?
The Desktop GUI currently requires either libopensync0 or libopensync1,
or both, and is fairly useless without the plugins to go along with it.
It is tricky to compile the Desktop for both.
Without opensync plugins, though, we should leave the Desktop out of Debian
for now. Is there an easy way to make packages optional? The way I've
done it so far is adding debian/ directories in the subprojects, as
completely separate source trees, like the opensync plugins are.
As for the rest of your list, thank you for the feedback. This will
take some time to process.
- Chris
Reply to: