Processed: Re: Bug#324795: libc6 in stable broken on arm4vl

2005-08-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 324795 normal Bug#324795: libc6 in stable broken on arm4vl Severity set to `normal'. > tags 324795 moreinfo Bug#324795: libc6 in stable broken on arm4vl There were no tags set. Tags added: moreinfo > thanks Stopping processing

Bug#324795: libc6 in stable broken on arm4vl

2005-08-24 Thread GOTO Masanori
severity 324795 normal tags 324795 moreinfo thanks At Wed, 24 Aug 2005 09:11:30 -0400, Rob Warren wrote: > I was upgrading from woody to sarge when apt-get choked on upgrading > libc6 from 2.2.5-11.8 to 2.3.2.ds1-22 with a message along the lines of > 'can't seek in file xx'. dmesg would rep

Bug#324795: libc6 in stable broken on arm4vl

2005-08-24 Thread Rob Warren
Goto, I was upgrading from woody to sarge when apt-get choked on upgrading libc6 from 2.2.5-11.8 to 2.3.2.ds1-22 with a message along the lines of 'can't seek in file xx'. dmesg would report 'Bad number of arguments for llseek()' (paraphrasing) every so often. It was impossible to reserve

Bug#324795: libc6 in stable broken on arm4vl

2005-08-24 Thread Rob Warren
It's dead jim. I'm running stable to present this kind of thing. :( best, rhw On 24-Aug-05, at 1:29 AM, Nathanael Nerode wrote: I don't suppose you know whether this affects libc6 in unstable? I doubt you would know. :-( It would be nice to know for bug tracking purposes though. -- Nath

Bug#324795: libc6 in stable broken on arm4vl

2005-08-24 Thread GOTO Masanori
At Tue, 23 Aug 2005 22:38:15 -0400, Rob Warren wrote: > Version: 2.3.2.ds1-22 > > Keeping up with Stable the new release for libc6 is broken. dpkg dies > on the upgrade. Did you try to upgrade from woody to sarge? Or from sarge to the current sid? Please imagine 2.3.2.ds1-22 is broken - many a

Bug#324795: libc6 in stable broken on arm4vl

2005-08-23 Thread Nathanael Nerode
I don't suppose you know whether this affects libc6 in unstable? I doubt you would know. :-( It would be nice to know for bug tracking purposes though. -- Nathanael Nerode <[EMAIL PROTECTED]> This space intentionally left blank. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subje