Bug#402519: Reopen

2007-07-04 Thread Frank S. Thomas
Hi Filipus,

On Monday 02 July 2007, Filipus Klutiero wrote:
 Le lundi 2 juillet 2007 06:04, Frank S. Thomas a écrit :
  Hi Filipus (or Philippe?),
 
  On Wednesday 21 March 2007, Filipus Klutiero wrote:
   reopen 402519
   severity 402519 grave
   thanks
  
   [...]
 
  I understand that you reopened this bug because it is still found in the
  current kernel-patch-debianlogo (1.5), but could you please explain why
  you raised it's severity from important to grave?

 Yes. The package is now unusable in stable, testing and unstable. (A bug
 preventing a package from being used in a suite is grave)

You mean because there is no kernel source package  2.6.18 in all three 
suites? Still the diff in /usr/src/kernel-patches/diffs/debianlogo/ can be 
applied manually, hence I find severity important more appropriate.

However, as soon as the new kernel-patch-debianlogo version, which is an empty 
transitional package for easier upgrades to linux-patch-debianlogo, enters 
the archive, this bug vanishes and can be closed.

Grüße,
Frank



Bug#402519: Reopen

2007-07-04 Thread Filipus Klutiero
Le mercredi 4 juillet 2007 04:36, Frank S. Thomas a écrit :
 Hi Filipus,

 On Monday 02 July 2007, Filipus Klutiero wrote:
  Le lundi 2 juillet 2007 06:04, Frank S. Thomas a écrit :
   Hi Filipus (or Philippe?),
  
   On Wednesday 21 March 2007, Filipus Klutiero wrote:
reopen 402519
severity 402519 grave
thanks
   
[...]
  
   I understand that you reopened this bug because it is still found in
   the current kernel-patch-debianlogo (1.5), but could you please explain
   why you raised it's severity from important to grave?
 
  Yes. The package is now unusable in stable, testing and unstable. (A bug
  preventing a package from being used in a suite is grave)

 You mean because there is no kernel source package  2.6.18 in all three
 suites?
Yes.
 Still the diff in /usr/src/kernel-patches/diffs/debianlogo/ can be 
 applied manually, hence I find severity important more appropriate.
Yes, but manually involves unspecified knowledge. Even if they're not 
actually unusable, we consider packages that need to be fixed to be used as 
simply unusable.



Bug#402519: Reopen

2007-07-02 Thread Frank S. Thomas
Hi Filipus (or Philippe?),

On Wednesday 21 March 2007, Filipus Klutiero wrote:
 reopen 402519
 severity 402519 grave
 thanks

 [...]

I understand that you reopened this bug because it is still found in the 
current kernel-patch-debianlogo (1.5), but could you please explain why you 
raised it's severity from important to grave? Since the package is still 
usable with older kernels, I think severity important is more appropriate.

Thanks,
Frank


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#402519: Reopen

2007-07-02 Thread Filipus Klutiero
Le lundi 2 juillet 2007 06:04, Frank S. Thomas a écrit :
 Hi Filipus (or Philippe?),

 On Wednesday 21 March 2007, Filipus Klutiero wrote:
  reopen 402519
  severity 402519 grave
  thanks
 
  [...]

 I understand that you reopened this bug because it is still found in the
 current kernel-patch-debianlogo (1.5), but could you please explain why you
 raised it's severity from important to grave?
Yes. The package is now unusable in stable, testing and unstable. (A bug 
preventing a package from being used in a suite is grave)