Bug#725143: Bug#728521: ogre-1.9 / gcc-4.8

2013-12-20 Thread Rebecca N. Palmer
My whole intent of posting my previous message was to agree that you had been right about 4.8 becoming required and that this was hence no longer our problem. I think that your attempt to merge the bugs failed. Yes, can't merge bugs when only one of them is forwarded, and since the forwarded

Bug#725143: Bug#728521: ogre-1.9 / gcc-4.8

2013-12-20 Thread Manuel A. Fernandez Montecelo
2013/12/20 Manuel A. Fernandez Montecelo : > - The solution of "gcc-default (>= 4.8) | gcc-4.8" would have been > nice if not because of the problem with buildds (I thought that it > would already have been fixed, it's an old problem). But the contrary > is not so nice because when GCC 4.9 becomes

Bug#725143: Bug#728521: ogre-1.9 / gcc-4.8

2013-12-20 Thread Manuel A. Fernandez Montecelo
Hi, 2013/11/30 Rebecca N. Palmer : > Control: severity 728521 normal > Control: merge 725143 728521 I think that your attempt to merge the bugs failed. It's OK to keep them separate because they are slightly different, so it doesn't matter. > It's now official that gcc 4.8 will be required in

Bug#728521: ogre-1.9 / gcc-4.8

2013-11-30 Thread Rebecca N. Palmer
Control: severity 728521 normal Control: merge 725143 728521 It's now official that gcc 4.8 will be required in jessie [1], so this is now not an RC (and could even be closed altogether, though that isn't my decision to make; the current non-working attempts to select gcc-4.8 are ugly, but har