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

Re: Bug#624997: writerperfect: FTBFS: Style.hxx:36:45: error: 'NULL' was not declared in this scope

On Tue, May 03, 2011 at 07:21:28AM +0200, Lucas Nussbaum wrote:
> (Ccing -devel@, since I have been asked about that by others)
> On 03/05/11 at 01:16 +0200, Rene Engelhard wrote:
> > tag 624997 - wheezy
> > thanks
> > 
> > On Mon, May 02, 2011 at 02:39:43PM +0200, Lucas Nussbaum wrote:
> > > Source: writerperfect
> > > Version: 0.8.0-3
> > > Severity: serious
> > > Tags: wheezy sid
> > 
> > No. gcc 4.6 is not in wheezy. If you find gcc 4.6 FTBFSes please take
> > care on where and when this stuff actually takes place.
> > 
> > Grüße/Regards,
> Note that the alternatives are:
> - tag it 'sid'. But then, I would need to determine the root cause of
>   each FTBFS, and when the status of the FTBFS changes in testing.
> - do not tag it. But then, it would be seen as affecting stable.
> What I would need is a way to express "It FTBFS in sid. I know it
> doesn't FTBFS in stable, I don't know about wheezy."

Tagging it with wheezy *is* the correct thing to do.  If you're
tagging it with only sid it means that it can never affect
anything else than sid.  And since this is a bug caused by some
other package and you can't prevent that other package from
migrating to testing, you have to assume that it will affect
testing in the future.  Else when it does migrate to testing this
is a bug that nobody will care about since it only affects


Reply to: