[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#289822: Please let mp3burn back to sarge



Hi Steve!

On Sun, 08 May 2005, Steve Langasek wrote:

> Hi Alexander,
> 
> On Sun, May 08, 2005 at 10:22:18AM +0200, Alexander Wirt wrote:
> > due to the fact that I missed to downgrade a bug (#289822), 
> > mp3burn got removed from sarge. I don't think thats a bug in
> > mp3burn, maybe in cdrecord, but I'm not able to reproduce it. 
> > mp3burn works fine for me and others. So I would be pleased
> > if you could put it back to sarge.
> 
> Is mp3burn known to work on 2.6 kernels?  Does mp3burn invoke cdrecord with
> any particular commandline options that could trigger this bug, whereas
> cdrecord would normally work for people?
It is. I develop mp3burn under 2.6 and had never complains except that bug
that it doesn't works. 

> 
> Since cdrecord reports a *read* error on input file, not a write error to
> the disk, it seems very plausible to me that this could be a bug in mp3burn,
> and this was why I removed the package from testing.  I think I would like
> to know that this package at least works for someone other than the
> maintainer before letting it back in.
There was some kernel bug with cdrecord during that time that prevented cdrecord
properly, so maybe that was the problem...

Best wishes
Alex


Attachment: signature.asc
Description: Digital signature


Reply to: