Bug#389934: severity of 389934 is important

2006-11-27 Thread Andreas Barth
severity 389934 important thanks * Bill Allombert ([EMAIL PROTECTED]) [061126 07:27]: However, the best course of action is to fix these bugs for Etch so that the release team does not have to make such compromise between stability and security. It is possible to achieve that thanks to

Bug#389934: severity of 389934 is important

2006-11-27 Thread Bill Allombert
On Mon, Nov 27, 2006 at 08:42:17AM +0100, Andreas Barth wrote: severity 389934 important thanks I upgraded the severity with permission from Steve. * Bill Allombert ([EMAIL PROTECTED]) [061126 07:27]: However, the best course of action is to fix these bugs for Etch so that the release

Bug#389934: severity of 389934 is important

2006-11-27 Thread Andreas Barth
* Bill Allombert ([EMAIL PROTECTED]) [061127 15:20]: I upgraded the severity with permission from Steve. Yes. Nobody said you did something wrong. As far as I am concerned, this is not a release goal, just basic sanity of the distribution, much like checking packages actually build from

Bug#389934: severity of 389934 is important

2006-11-26 Thread Bill Allombert
severity 389934 serious thanks On Sun, Nov 26, 2006 at 04:24:22AM -080O0, Steve Langasek wrote: Hi Bill, So my own opinion is that this class of bug should not be RC, at least when the embedded rpath doesn't lie in an obviously user-writable space such as /home or /tmp. If you feel strongly

Bug#389934: severity of 389934 is important

2006-11-26 Thread Steve Langasek
Hi Bill, On Mon, Nov 20, 2006 at 07:13:14PM +0100, [EMAIL PROTECTED] wrote: On Thu, Sep 28, 2006 at 02:31:19PM -0700, Steve Langasek wrote: # Automatically generated email from bts, devscripts version 2.9.21 severity 389934 important I don't see how you reached this conclusion. Users