Chris Hiestand wrote: > Bob Proulx wrote: > > Chris Hiestand wrote: > >> It seems that during a preseeded installation today my squeeze VM > >> installed a proposed update when it shouldn't have: > > > > Or did you simply catch an archive in the middle of being updated? > > That shouldn't happen but depends upon the mirror you are using. > > The problem turned out to be caused by my missing the squeeze-updates > entries in sources.list. It was just never noticeable until this update.
Interesting. Yes for whatever reason that update appears in squeeze-updates.
$ apt-cache policy libc6-i386
libc6-i386:
Installed: (none)
Candidate: 2.11.3-3
Version table:
2.11.3-3 0
500 http://ftp.us.debian.org/debian/ squeeze-updates/main amd64
Packages
2.11.3-2 0
500 http://ftp.us.debian.org/debian/ squeeze/main amd64 Packages
> That's because you're running i386 arch. I was on an amd64 machine.
That makes a large difference!
Out of curiosity, what are you using libc6-i386 for on your amd64
machine?
Debian biarch support isn't multiarch and is pretty poor. I realize
that poor doesn't mean broken. It just means poor. It is missing the
full package system behind it. I find it unsuitable for my use. I
avoid it. Instead I do the chroot thing to run a 32-bit chroot on my
64-bit machines that need it. Then I get full apt capability and can
install anything and can manage the system normally. Although the
chroot is more overhead to set up initially. Other people might use a
vserver. Other people might use a full VM.
But I acknowledge that installing the current x86 libs on a 64-bit
machine may be what I would brand a "quick and dirty" way to support
doing something. Just wondering what people find useful there? Since
I am pretty happy with a native 64-bit system these days. The
previous problems of Adobe Flash and Sun Java and other 32-bit binary
blobs have mostly been mitigated.
Bob
signature.asc
Description: Digital signature
