Bug#474947: the state of Bug#474947

2008-10-29 Thread Neil McGovern
clone 474947 -1 reassign -1 release-notes retitle -1 Update information about apt MMap problem in release notes thanks On Tue, Oct 21, 2008 at 12:03:49PM +0200, A Mennucc wrote: > hi bug, hi people, hi d-release > > I did some study on bug 474947, that is grave/RC, and is posted against APT. > >

Bug#474947: the state of Bug#474947

2008-10-27 Thread Eugene V. Lyubimkin
Elliott Mitchell wrote: >> Yes. So, If you claim this have to be fixed before Lenny, go ahead and ask >> Debian release >> team what they think about changes in internals of apt and additional >> month(s) of testing. >> > > I thought that was the point of copy the messages to their list was. And

Bug#474947: the state of Bug#474947

2008-10-26 Thread Elliott Mitchell
>From: Eugene V. Lyubimkin <[EMAIL PROTECTED]> > Elliott Mitchell wrote: > > I have made no such claims. I am merely stating that this is a serious > > bug. Severe enough to seriously consider delaying the release. This is > > what the release team gets to decide, which is worse (neither option is

Bug#474947: the state of Bug#474947

2008-10-26 Thread Eugene V. Lyubimkin
Dropped debian-release from CC. Elliott Mitchell wrote: >> - this patch reduces apt speed (not serious though, as I see) on most >> operations with the cache; > > I guess I should ask, do you have an less issues less relevant waiting in > the wings? While more speed is good, that is worthless if

Bug#474947: the state of Bug#474947

2008-10-25 Thread Elliott Mitchell
>From: Eugene V. Lyubimkin <[EMAIL PROTECTED]> > A Mennucc wrote: > > IMHO one way to decide if to accept a patch during the freeze is to > > see how large and "important" it is. Does anybody have an example > > patch, or a description of what code changes would be necessary? > I had a look on thi

Bug#474947: the state of Bug#474947

2008-10-23 Thread Eugene V. Lyubimkin
A Mennucc wrote: > On Wed, Oct 22, 2008 at 10:09:58PM -0700, Elliott Mitchell wrote: >> I must therefore suggest that at the very least, the first part of this >> bug is too severe to allow to continue on to yet another release. Despite >> the pain now, that it is better to solve this issue and avo

Bug#474947: the state of Bug#474947

2008-10-23 Thread A Mennucc
On Wed, Oct 22, 2008 at 10:09:58PM -0700, Elliott Mitchell wrote: > I must therefore suggest that at the very least, the first part of this > bug is too severe to allow to continue on to yet another release. Despite > the pain now, that it is better to solve this issue and avoid yet more > pain dow

Bug#474947: the state of Bug#474947

2008-10-22 Thread Elliott Mitchell
>From: A Mennucc <[EMAIL PROTECTED]> > In this same bug there were reported two different issues, a "Dynamic > MMap error" and a segmentation fault; moreover some people were using > APT in Etch, and some other in Lenny. I believe this is a good estimation of how it breaks down. > The only way t

Bug#474947: the state of Bug#474947

2008-10-21 Thread A Mennucc
retitle 474947 "fix Dynamic MMaps error" severity 474947 important tag 474947 -unreproducible thanks hi bug, hi people, hi d-release I did some study on bug 474947, that is grave/RC, and is posted against APT. Since I was told that the APT team is understaffed, I decided to take action myself.