Αρχικό μήνυμα από David Kalnischkies <[email protected]>:
> Hello Nikos Kokkalis, > > first of all: thanks for reporting your issue! > (i think many people will see this with the current situation on amd64) > > > bo...@i0n:~$ apt-cache rdepends wine > > terminate called after throwing an instance of 'std::bad_alloc' > > what(): std::bad_alloc > > Aborted > > > APT::Cache-Limit "99999999999999999"; > > You set your Cache-Limit far to high. > This setting would require a total of > 99 999 999 999 999 999 Bytes (= 99 Petabyte!) > of free RAM to generate a new package cache. > So please choose a value which is more realistic (and actually available). > > You should use the default value if possible - if not increase the value > with this setting a bit and try again (Also consider removing source.list > entries you don't need - they will only waste space which apt needs here). > > > Best regards / Mit freundlichen Grόίen, > > David "DonKult" Kalnischkies > > > P.S.: Bugreports and Information why this setting is actually needed and > why it is not easy to made the dynamic MMap really dynamic can be found > in bugreport #195018 and his merged friends. > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=195018 > First of all, David thanks for all. It seems that it's time to close that bug report. Generally i don't need a custom Cache-Limit, but ia32-apt-get messed a little the setup and i tried various things. I didn't think that this was the fault. :) Thanks again for all. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
