Bug#494168: Still there.

notfound 494168 1.3.8-1lenny1 fixed 494168 1.3.8-1lenny1 thanks On Fri, Sep 05, 2008 at 11:01:14PM -0700, Brandon wrote: > found 494168 1.3.8-1lenny1 > thanks > This bug is still present, and shouldn't be closed until it is fixed. You are mistaken. Stop reopening this bug. > > This bug is *not

Bug#494168: Still there.

found 494168 1.3.8-1lenny1 thanks This bug is still present, and shouldn't be closed until it is fixed. > This bug is *not* present in 1.3.8-1lenny1. Brandon, you need to > open a separate bug report for whatever your unrelated issue is. That doesn't even make any sense. If I were to open a sep

Bug#494168: Still there.

found 494168 1.3.8-1lenny1 thanks Bug is still there. Can't say I was surprised. It looks like all that was done is porting a few changes from experimental, which is also broken. It appears that this bug applies to some people, but not others. Some fixes work for some, and not others. This means

Bug#494168: Still there.

found 494168 1.3.8-5 severity grave Justification: renders package unusable This bug is still present in experimental version 1.3.8-5. Although the exit code, for me, is 127. Also, how is this bug not grave? It makes the package completely useless, and should definitely be fixed before the next s