On Wed, 2003-11-19 at 02:01, Ken Treis wrote:
>
> Reading Package Lists... 0%
> Program received signal SIGSEGV, Segmentation fault.
> 0x0ffb0094 in
> pkgCacheGenerator::ListParser::NewDepends(pkgCache::VerIterator,
> std::string, std::string, unsigned, unsigned) () from
> /usr/lib/libapt-pkg-l
Geert Uytterhoeven wrote:
Usually libc6 is too blame. If you still have the old one in
/var/cache/apt/archives/ (or can get it on the box) just reinstall it manually.
Tried rolling back to libc6_2.3.2-9, but that didn't help. I'm not
exactly sure what I was running before, and of course I did
On Tue, 18 Nov 2003, Ken Treis wrote:
> I just upgraded one of my briQ-based servers to the latest from sarge,
> and now I get segmentation faults when apt reads package lists:
>
> # apt-get update
> [various sites hit]
> Fetched 7066B in 0s (7482B/s)
> Segmentation faultsts... 1%
>
> # apt-cach
On Tue, Nov 18, 2003 at 09:43:52AM -0800, Ken Treis wrote:
> I just upgraded one of my briQ-based servers to the latest from sarge,
> and now I get segmentation faults when apt reads package lists:
>
> # apt-get update
> [various sites hit]
> Fetched 7066B in 0s (7482B/s)
> Segmentation faultsts.
> Ken Treis <[EMAIL PROTECTED]> [2003-11-18 19:11]:
>
> I just upgraded one of my briQ-based servers to the latest from sarge,
> and now I get segmentation faults when apt reads package lists:
>
...
>
> # apt-cache update
> Segmentation fault
>
...
> I can still get files onto the system, and I ca
5 matches
Mail list logo
