I sucked down Sid the other night, and along the way one file
failed to download, I was using 'apt-get -d' so I could monitor
the update later. So I grabbed this file, and a couple of others
on a 'doze box at work and put them on a floppy, with the intention
of using 'apt-cache add'. But when I
--8-
E:The package cache file is corrupted.
--8-
Did you hear that?
Hear what?
I think it's the sound of all the apt-get fans running for cover! ;-)
Martin Visser
Technology Consultant - Compaq
Steven downing was once rumoured to have said:
[Details snipped]
This seems (to me!) to imply some kind of lack of memory (MMap??)
So I made sure nothing much was running and tried again, but every
subsequent apt-cache add came up with..
E:The package cache file is corrupted.
Which made
Crossfire [EMAIL PROTECTED] 28/02/01 15:16:26
Steven downing was once rumoured to have said:
[Details snipped]
E:The package cache file is corrupted.
Which made me think the .deb was corrupted via Windows
stoopidnes (It might still be I guess), but closer reading leads
me to think the
Steven downing wrote:
'Apt-get update' updates the list of available packages yeah?
And I was thinking that the packages cache file
(/var/cache/apt/packages.bin??), was an index of files which had
been downloaded from a network source (and possibly not
yet installed on the system)
Read
