On Sun, Apr 17, 2016 at 11:49:32AM +0200, Christoph Berg wrote: > Re: Bill Allombert 2016-04-15 <20160415195507.GA13901@yellowpig> > > There is a circular dependency between cluster-glue, liblrm2, libpils2, > > libplumb2, libplumbgpl2 and libstonith1: > > > > cluster-glue :Depends: liblrm2 (>= 1.0.12-4), libpils2 (>= > > 1.0.12-4), libplumb2 (>= 1.0.12-4), libplumbgpl2 (>= 1.0.12-4), libstonith1 > > (>= 1.0.12-4) > > liblrm2 :Depends: libplumb2, cluster-glue (= 1.0.12-4) > > libpils2 :Depends: cluster-glue (= 1.0.12-4) > > libplumb2 :Depends: libpils2, cluster-glue (= 1.0.12-4) > > libplumbgpl2 :Depends: libpils2, cluster-glue (= 1.0.12-4) > > libstonith1 :Depends: libpils2, cluster-glue (= 1.0.12-4) > > Hi, > > the reason for the cluster-glue -> lib* dependency is that the former > uses these libs, and the reason for the dependency the other way is > that the libs have a /usr/share/doc-lib* -> cluster-glue symlink. > (The lintian override explains that as well.) > > > Complex circular dependencies are known to cause problems during upgrade, > > so we > > should try to get rid of them. > > I'd argue that this isn't a "complex" circular dependency, but we'll > see what we can do. Possibly moving the doc directory to a new > cluster-glue-common package would work.
Or you can get rid of the /usr/share/doc/lib* symlinks and replace them by proper directories. Such symlinks have always been a bad idea by forcing artificially strong dependencies, and being generally fragile. In any case, it is strange to force users of any of theses libs to install cluster-glue. For example a package might want to Build-Depends on liblrm2-dev but do not need cluster-glue to build. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.
