Bug#641298: libmaven-scm-java: circular dependency hell

[Torsten Werner]

On Tue, Sep 13, 2011 at 8:31 PM, Bill Allombert
<Bill.Allombert at math.u-bordeaux1.fr> wrote:
> See threads
> http://lists.debian.org/debian-devel/2005/06/msg02111.html

I've re-read the policy. I've found out that the circular dependency
'hell' is about the configure phase and can happen only if *all*
packages in the circle have a postinst file. That is not hard to
check. On my local system I can find no match for *maven*.postinst
(that renders the current bug report invalid) and only a few matches
for lib*java*.postinst. The matches can be categorized into:

1) install-docs snippets added by old versions of debhelper. A simple
rebuild is enough to fix this.

2) ldconfig snippets added by debhelper in jni packages. Such packages
are not very common and are probably never part a dependency circle.

3) rebuild-gcj-db snippets in gcj packages. Many of these package will
get dropped if they still exist. We will maintain only a small set of
gcj packages in the future and they probably won't be part of
dependency circle.

4) There is a very small number of packages left. The risk is low that
they will cause real issues.

IMHO there is no reason to file random bug reports for innocent packages.

Torsten