Bug#436260: closed by maximilian attems m...@stro.at (Re: linux-support-2.6.22-1: Support for exernal module packages broken)

2008-11-13 Thread Mark Brown 
On Wed, Nov 12, 2008 at 11:03:55PM +0100, Moritz Muehlenhoff wrote:
 On Mon, Jun 30, 2008 at 02:13:33PM +0200, maximilian attems wrote:

  if you can reproduce it with 2.6.25 or newer snapshots.
  i'm all ears unless so it is assumed fixed.

 Mark, does the problem still exist for you with the current Lenny packages?

Given that it took until six months after I'd left the job where I
encountered the bug for the patch to get looked at you may as well close
it - I don't really have the combination of time and enthusiam required
to do so myself.

-- 
You grabbed my hand and we fell into it, like a daydream - or a fever.



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

Bug#436260: closed by maximilian attems m...@stro.at (Re: linux-support-2.6.22-1: Support for exernal module packages broken)

2008-11-12 Thread Moritz Muehlenhoff 
On Mon, Jun 30, 2008 at 02:13:33PM +0200, maximilian attems wrote:
 On Mon, 30 Jun 2008, Mark Brown wrote:
 
  On Sun, Jun 29, 2008 at 11:01:43PM +0200, maximilian attems wrote:
  
   there was no patch provided nor any proof of any trouble by your
   side, so tagging with moreinfo and willl close in 10 days
   unless something substantial comes up.
  
  Uh, message 10 of the bug report contains the updated version of
  gencontrol.py that I provided and I wasn't exactly overburdened with
  requests for additional information...
 
 update for what and what was the error in the first place?
 it would be great to have that info.
  
   2.6.22 is really old and keeping cruft lying around helps noone.
  
  On the other hand, ignoring bugs for the best part of a year and then
  closing them on the basis that you haven't done anything about them
  doesn't exactly help either.
 
 if you can reproduce it with 2.6.25 or newer snapshots.
 i'm all ears unless so it is assumed fixed.

Mark, does the problem still exist for you with the current Lenny packages?

Cheers, 
Moritz



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