#include <hallo.h> * Joerg Schilling [Sat, Apr 08 2006, 11:25:09PM]: > Eduard Bloch <[EMAIL PROTECTED]> wrote: > > > Unfortunately you forgot to provide information about how the proper > > solutions should look like. Almost all that changes solve real problems > > documented in the BTS, and the changelog file tells you the numbers of > > the bug reports. Please explain how we should solve that problems > > (existing IRL) in a proper way without offending our users and kernel > > developers. > > If you did read my information, you would find that the named patches > _create_ problems.
You keep saying that but you don't tell which problems _exactly_ are created, ie. how the actual symptoms look like. Unless you proove that and show us _real_ bug reports from _real_ users with problems created by _our patches_, this talk about "new problems" is pure speculation. The only exception I can see is the problem with the locking patch and the "special" behaviour of libscg when doing the scanbus operation - and even this problem will be _solved_ by the patch 36 which just waits for the next release of cdrtools packages and has also been confirmed as beeing effective by a user in bug report 360295. > > > 23_o_excl.dpatch Causes libscg to fail and is the reason > > > for 3 bugs in the cdrtools Debuan bug > > > list. > > ... > > > 36_ATA_scanbus_ignore_locked.dpatch See 23_o_excl > > > > Yes, it solves that problem. The alternative would be a fundamental > > change of libscg which you would unlikely agree with. > > If you did read the bug list from Debian, you would see that the patches above > cause cdrecord to fail completely while an unpatched version works at the > same > time. 23 makes trouble, 36 fixes that again -> problem solved. Yes, unmodified version works under laboratory conditions and on many systems with "good" environment but IRL things may become more complicated. As said, please convince us that there is a better solution for reported bug (here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=262678 ) in your code, otherwise it's pure speculation. Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
