On Tue, Sep 13, 2011 at 10:25:24PM +0200, Torsten Werner wrote:
On Tue, Sep 13, 2011 at 8:31 PM, Bill Allombert
bill.allomb...@math.u-bordeaux1.fr wrote:
Symptoms include 'apt-get dist-upgrade' from stable to next-stable trying to
remove a lot of packages by failure to find a better upgrade
On Tue, Sep 13, 2011 at 8:31 PM, Bill Allombert
bill.allomb...@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*
On Mon, Sep 12, 2011 at 05:07:18PM +0200, Torsten Werner wrote:
Hi,
On Mon, Sep 12, 2011 at 3:12 PM, Bill Allombert ballo...@debian.org wrote:
Complex circular dependencies are known to cause problems during upgrade,
so we
should try to get rid of them.
may you explain a bug scenario
On Tue, Sep 13, 2011 at 8:31 PM, Bill Allombert
bill.allomb...@math.u-bordeaux1.fr wrote:
Symptoms include 'apt-get dist-upgrade' from stable to next-stable trying to
remove a lot of packages by failure to find a better upgrade path, to
maintainer scripts failing because they assume the
Package: libmaven-scm-java
Version: 1.3-3
Severity: important
Hello Debian Java Maintainers,
There is a circular dependency between libmaven-scm-java, libmaven2-core-java
and libwagon-java:
libmaven-scm-java :Depends: libmaven2-core-java
libmaven2-core-java :Depends: libwagon-java
Hi,
On Mon, Sep 12, 2011 at 3:12 PM, Bill Allombert ballo...@debian.org wrote:
Complex circular dependencies are known to cause problems during upgrade, so
we
should try to get rid of them.
may you explain a bug scenario that can be reproduced, please? I am
not aware of update problems of
6 matches
Mail list logo
