Hello,
In fact, i have also this bug. It comes from a circular versionned
dependency betwee lipam0g and libpam-modules :
libpam0g depend on libpam-modules 0.7.X and
libpam-modules depends on libpam0g 0.7.X...
So if you try to upgrade from a version below 0.7.X you cannot get it
Hi,
Adam Heath wrote:
this is a bug in apt. dpkg correctly handles this case(it breaks the dep loop
randomly, which means postinsts of the affected packages need to be aware of
the issue.
The apt developer has refused to fix apt to work around this non-problem in
the past, I suggest you
On Thu, Jun 26, 2003 at 11:15:37PM +0100, Esteban Manchado Vel?zquez wrote:
On Wed, Jun 25, 2003 at 05:39:36PM -0400, Sam Hartman wrote:
[Please cc me; I'm very behind on -devel]
I'm very confused by this bug and am sufficiently busy this week that
I'm not going to be able to
On Sat, 28 Jun 2003, Sylvain LE GALL wrote:
On Thu, Jun 26, 2003 at 11:15:37PM +0100, Esteban Manchado Vel?zquez wrote:
On Wed, Jun 25, 2003 at 05:39:36PM -0400, Sam Hartman wrote:
[Please cc me; I'm very behind on -devel]
I'm very confused by this bug and am sufficiently busy
On Wed, Jun 25, 2003 at 05:39:36PM -0400, Sam Hartman wrote:
[Please cc me; I'm very behind on -devel]
I'm very confused by this bug and am sufficiently busy this week that
I'm not going to be able to diagnose it right now.
Could anyone who has a chance to do so please look at exactly
[Please cc me; I'm very behind on -devel]
I'm very confused by this bug and am sufficiently busy this week that
I'm not going to be able to diagnose it right now.
Could anyone who has a chance to do so please look at exactly what is
failing from a dependency standpoint?
I get the feeling I'm
6 matches
Mail list logo
