Norbert Preining <prein...@logic.at> writes: > # unmerging because it is a completely different issue than the one in > # the above bug > unmerge 534965 > # could have set severity to grave again, now aptitude SIGSEGVs > thanks > > On Mo, 29 Jun 2009, Goswin von Brederlow wrote: >> > - aptitude UI with upgrading does not work, redownloads everything again >> > and again >> >> I know update does not work in aptitude. I wasn't aware of other >> breakage. Can you provide some sort of log? This is a duplicate of >> 533746, merging. > > No log now, because now after calling > /usr/share/ia32-apt-get/convert-all-sources.list I even get: > mithrandir:~# aptitude > Ouch! Got SIGSEGV, dying.. > Segmentation fault > mithrandir:~# > > Simple gdb-ing gave me: > Program received signal SIGSEFC, Segmentation fault. > [Switching to Thread =x7fcf06fe7710 (LWP 8165)] > 0x00007fcf06b60455 in DynamicMMap::WriteString () > from /usr/lib/libapt-pkg-libc6.9-6.so.4.7 > > It is getting worse.
That will be the same issue apt-get has. They both use libapt after all. >> As mentioned in NEWS and as of version 19 also in README.Debian for >> the time being you need to run >> /usr/share/ia32-apt-get/convert-all-sources.list >> when you change your sources.list. > > Yes but since that packages is *pulled*in* automatically how should > anyone know about it??? I wasn't even aware that there is some magic > going on. Ideally you shouldn't be aware of it at all. On install the sources.list are converted automatically once and the plan is to automatically update the converted list when needed. I just haven't had time to write the code for that yet. >> > - calling apt-get update from the command line (recommended in another >> > bug report) finishes in a core dump >> > /usr/bin/apt-get: line 46: 30757 Segmentation fault apt-get.real >> > --no-list-cleanup --no-download update >> >> One other user managed to produce that on irc today. I can't reproduce >> it and the user purged and reinstalled ia32-apt-get, thereby solving >> the problem for some reason, before I could ask him to send a tar of: >> /etc/apt >> /var/lib/apt >> /var/cache/apt (without archives/) > > 70M, I will try to upload from the slow link I have here. Should I put > them on a web space or send by email to your personally?. Webspace is probably best. Not sure how soon such a large mail would get killed in my mail chain. But I highly doubt it would survive. Once you have a tar of them try if rm /var/cache/apt/*.bin /var/cache/apt/*/*.bin solves the problem. >> I don't know what causes this but something is triggering a bug in >> the real apt-get. Best guess apt-get manages to break its *.bin cache >> files. Maybe when it complains about the APT::Cache-Limit being too >> small. Did you have to increase APT::Cache-Limit just before you got >> the Segmentation fault? > > No, I didn't change anything in the cache or apt at all. Odd. I have sid and experimental in my sources.list and run out of space with the default size. Maybe it is experimental that pushes apt over the top. > Best wishes > > Norbert MfG Goswin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org