-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 2008/6/21 Florian Kulzer : > On Sat, Jun 21, 2008 at 13:04:54 +0100, Anton Piatek wrote: >> Hi, >> Does anyone know why apt-get crashes when updating? >> >> Hit http://security.debian.org lenny/updates/main Sources >> Hit http://security.debian.org lenny/updates/contrib Sources >> Hit http://security.debian.org lenny/updates/non-free Sources >> Fetched 9B in 2s (4B/s) >> Segmentation faultsts... 60% >> >> Removing a deb source solves the problem (5 sources works, 6 fails). >> I have had this happen before, with sarge i think, and upgrading apt >> to a newer level solved it, however uprading apt now will require >> upgrading libperl >> My apt is currently at version 0.7.6 on a mixed lenny/sid system (with >> some packages from etch, unison in particular) > > I think you are not doing yourself any favors by running your system > like that.
Unfortunately unison is designed such that both client and server versions must match, so as my servers are etch I need the etch version on my laptop. I need software from Lenny/Sid on my laptop. I suppose I could move to complete Sid however I do not want to have to worry about the extra effort of all the extra updates that I would have to install on Sid rather than Lenny. The only solution other than running a mixed system is to move to Ubuntu and get backports of unison that match Etch, however I'd rather stay on Debian. >> Surely apt should be able to handle 6 sources lists - why can't it? >> and is there anything I can do to help debug why? > > Maybe it is just a problem of insufficient memory being reserved for the > cache. Try this: > > apt-get -o APT::Cache-Limit="20000000" update > > This tells apt to reserve 20 MB for the cache; you can of course > increase the value further if it still does not work with 20 MB. I have > stable, testing, unstable, experimental and debian-multimedia in my > sources.list and my cache cache limit is set to 50 MB. > > If you find a Cache-Limit value that works for you then you can make it > permanent in a file in /etc/apt/apt.conf.d/. > > Assuming that insufficient cache size is to blame, apt should probably > handle such a situation more gracefully. However, I think it is only > worthwhile to track this down further if the segfault can be reproduced > for the current version of apt. (I did not check the bug reports; maybe > it is already a known problem.) It is indeed solved by increasing the apt-cache limit. There does appear to be a bugreport open, though I doubt I can add much to it without moving apt up to the unstable level. Aptitude has the same problem, though is more explicit about why. It seems that once I run apt with a 20mb limit the problem goes away, so presumably apt is happy keeping the cache at a larger size once it gets that big. I will add the option to my config anyway, so hopefully will not see this again. Is it worth suggesting that the default cache size be increased? Anton - -- Anton Piatek email: [EMAIL PROTECTED] blog/photos: http://www.strangeparty.com pgp: [0xB307BAEF] (http://tastycake.net/~anton/anton.asc) fingerprint: 116A 5F01 1E5F 1ADE 78C6 EDB3 B9B6 E622 B307 BAEF No trees were destroyed in the sending of this message, however, a significant number of electrons were terribly inconvenienced. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: http://getfiregpg.org iD8DBQFIXQXSWG/uFE1FAgwRAvOVAKCjRrRCXo0dcnWLmk/St9rujuGxkACfXkuU lU8yx2oMU9LUE1CrwGpcEFk= =z0NV -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
