On Fri, Oct 14, 2005 at 08:58:18AM -0400, Daniel Jacobowitz wrote:
> Funny, I've got the same setup, and the check has not triggered in the
> past. I can reproduce it, though. Let me poke around.
... that would be because I installed this system after the last upload
of glibc. I've got a fix no
On Fri, Oct 14, 2005 at 09:37:53AM +0200, Konrad Rosenbaum wrote:
> On Friday 14 October 2005 04:47, Daniel Jacobowitz wrote:
> > > When upgrading libc6 it checks for other installations of libc on the
> > > same system. Unfortunately it does not distinguish between the amd64
> > > and x86 versions
On Friday 14 October 2005 04:47, Daniel Jacobowitz wrote:
> > When upgrading libc6 it checks for other installations of libc on the
> > same system. Unfortunately it does not distinguish between the amd64
> > and x86 versions and stops the installation although no real conflict
> > would have resul
Hi Konrad,
> When upgrading libc6 it checks for other installations of libc on the same
> system. Unfortunately it does not distinguish between the amd64 and x86
> versions and stops the installation although no real conflict would
> have resulted since the conflicting version is x86 and not amd64
Package: libc6
Version: 2.3.2.ds1-21
Severity: important
When upgrading libc6 it checks for other installations of libc on the same
system. Unfortunately it does not distinguish between the amd64 and x86
versions and stops the installation although no real conflict would
have resulted since the co
5 matches
Mail list logo
