Re: please add fix for bz 408596 to etch [SRM]

2008-04-05 Thread Luk Claes
On Wed, Apr 02, 2008 at 09:00:28PM +0200, Aurelien Jarno wrote:
 Hi Stable Release Managers,

Hi

 Alex Chiang a écrit :
  Hi Aurelien,
  
  * Aurelien Jarno [EMAIL PROTECTED]:
  Alex Chiang a écrit :
  I'm hitting:
 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408596
 
  On my ia64/etch install. This is causing problems for me when I
  attempt to use sparse.
 
  Is there any chance you could consider this fix for etch? The fix
  itself looks very benign, and non-intrusive.
  I don't think such a fix is possible for Etch, as this bug does not meet
  the requirements for an update in a stable version. See:
 
  http://release.debian.org/stable/3.1/3.1r8/

Indeed, it doesn't seem to qualify.

Cheers

Luk



Re: please add fix for bz 408596 to etch [SRM]

2008-04-02 Thread Aurelien Jarno
Hi Stable Release Managers,

Please could you comment on the mail below?

Thanks,
Aurelien

Alex Chiang a écrit :
 Hi Aurelien,
 
 * Aurelien Jarno [EMAIL PROTECTED]:
 Alex Chiang a écrit :
 I'm hitting:

 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408596

 On my ia64/etch install. This is causing problems for me when I
 attempt to use sparse.

 Is there any chance you could consider this fix for etch? The fix
 itself looks very benign, and non-intrusive.
 I don't think such a fix is possible for Etch, as this bug does not meet
 the requirements for an update in a stable version. See:

 http://release.debian.org/stable/3.1/3.1r8/
 
 I don't want to push this too hard, because:
 
   a) I'm running sparse with -Werror
   b) obviously cpp doesn't seem to care
 
 But I would like to point out that:
 
   a) sparse is a quite useful tool for developers[1]
   b) it will give a *lot* of spurious warnings because of 408596
   c) the fix for 408596 is trivial and obviously correct
 
 Since etch is 'stable', it's gonna be around for a long time. It
 would be nice to backport [EMAIL PROTECTED] fix to support FOSS developers who
 have chosen debian/stable as a development environment.
 
 FWIW, I tripped across this bug even though upstream did not,
 because upstream was developing against a Fedora 9 userspace. And
 we did end up working around this problem [2].

Well trying to convince me won't help, as I am not the one taking the
decision. Asking the stable release manager for their opinion.

 Thanks.
 
 /ac
 
 1: http://www.kernel.org/pub/software/devel/sparse/
 2: http://oss.oracle.com/mercurial/zab/crfs/rev/f8c423608c93
 
 


-- 
  .''`.  Aurelien Jarno | GPG: 1024D/F1BCDB73
 : :' :  Debian developer   | Electrical Engineer
 `. `'   [EMAIL PROTECTED] | [EMAIL PROTECTED]
   `-people.debian.org/~aurel32 | www.aurel32.net


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