[Debian-ha-maintainers] Bug#768922: Bug#768618: pacemaker: FTBFS in jessie: build-dependency not installable: libqb-dev (>= 0.16.0.real)

[Jonathan Wiltshire]

On Sat, Dec 13, 2014 at 04:42:38PM +0100, Paul Gevers wrote:
> Summary: The current upstream version of pacemaker should not have
> migrated to jessie because it build-dependency (and corresponding
> dependency library) is not high enough in jessie. Either pacemaker
> should be removed from jessie, or libqb in sid should be allowed to
> migrate (after removal of the kfreebsd-* packages). I leave the decision
> for either direction to the RT, but am willing file the appropriate bugs
> on request.

Thanks for looking into this. I am already working on a way out of the
mess, which I'll have time to finish up in the next few days.

> On Wed, 12 Nov 2014 23:17:32 +0500 Andrey Rahmatullin <wrar at debian.org>
> wrote:
> > On Sat, Nov 08, 2014 at 06:57:27PM +0100, Lucas Nussbaum wrote:
> > > >  sbuild-build-depends-pacemaker-dummy : Depends: libqb-dev (>= 0.16.0.real) but it is not going to be installed
> > libqb 0.17.0-2 has no chance of migrating until release.
> 
> There are multiple interesting issues with the pacemake/libqb chain.
> 
> First of all, the shlibs file in libqb does not contain a version. The
> result of this is that any package building against libqb will get an
> unversioned run time dependency on libqb0. However, pacemaker requires
> at least version 0.13; see the check in configure when building against
> jessies version: "configure: error: Version of libqb is too old: v0.13
> or greater requried" Bug 768922 indicates that that dependency is also
> reflected during runtime. I will file a bug against libqb shortly to fix
> the shlibs file.

It's worse than this; there appear to be dropped symbols in the library, so
it needs a soname bump (which I'm discussing with upstream, though I'm not
convinced that is going anywhere).

(That is partly why package managed to migrate, since britney considers
installability but not buildability, and libqb's symbols table is a
complete lie.)

> Furthermore, libqb started to activate the build tests in version
> 0.14.3-2, which since than hasn't built on kfreebsd-* because it fails
> on the tests. Nobody seems to have taken care to look into the FTBFS or
> to file a RM request for the kfreebsd packages. However they blocked
> migration of libqb to testing. Since the decision to not have kfreebsd-*
> as release archs, this is sort of a shame as libqb would have migrated
> to jessie if not for kfreebsd-* (no further RC bugs).
> 
> As I see it, the simple solution for these RC bugs is to remove
> pacemaker from jessie. However, I want to also offer the idea of letting
> libqb migrate to jessie, as it is "only" blocked by kfreebsd-* failing
> builds (since March 2014). This would require a RM request against the
> ftp.debian.org pseudo package.

Migrating libqb isn't really an option either - apart from the required
soname bump, the changes are quite large.

I'm working on a reversion of pacemaker instead, which is better (IMO) than
having to ship without one. That would make Debian a laughing-stock. The
final decision is not mine though, since I have a conflict of interest.


-- 
Jonathan Wiltshire                                      jmw at debian.org
Debian Developer                         http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/debian-ha-maintainers/attachments/20141213/873038c5/attachment-0003.sig>