Processed: Re: Bug#485956: Errata - resetting severity

2008-06-13 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 485956 serious Bug#485956: FTBFS: uses chown inappropriately Severity set to `serious' from `minor' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Bug#485956: Errata - resetting severity

2008-06-13 Thread Pierre Habouzit
On Fri, Jun 13, 2008 at 02:07:29PM +, Jon wrote: Perhaps you can explain something to me then. I am able to build the package without being root, and have explained this to the user. He just can't get it to work with his command line. Please explain why this makes the bug serious?

Bug#485956: Errata - resetting severity

2008-06-13 Thread Pierre Habouzit
Please stop removing the bug from the CC list. On Fri, Jun 13, 2008 at 03:50:57PM +, Jon wrote: But that's my exact point. The commands you listed work perfectly, as they always have. What doesn't work is the command -*he*- used. Try those commands you sent in the email, and they will

Bug#485956: Errata - resetting severity

2008-06-13 Thread Pierre Habouzit
On Fri, Jun 13, 2008 at 04:24:55PM +, Jon wrote: I'll take a look at it. STOP REMOVING THE CC TO THE BUG# ITS RUDE. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org

Processed: Re: Bug#485956: Errata - resetting severity

2008-06-12 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 485956 minor Bug#485956: FTBFS: uses chown inappropriately Severity set to `minor' from `serious' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Bug#485956: Errata - resetting severity

2008-06-12 Thread Jon Marler
severity 485956 minor thanks Actually, I disagree. This is not a serious bug, and will build with the standard Debian tools, including the autobuilder. It doesn't work using the command you have chosen for it, but there is nowhere in the policy you referred to that states that specific