Comment 101 for bug 991179

On 05/10/2012 06:19 AM, Thomas Ward wrote:
> 7.0.26 isn't in Debian, so I'd have to poke around with the MOTUs to get
> that into Quantal, if not take the source and repackage it for quantal-
> proposed.
>
> Once Locutus can confirm whether or not 7.0.27 builds in Quantal, I'll
> go poke the MOTUs. I should point out, though, that since 7.0.26 is not
> packaged in Debian, they may not accept it, that's their decision.

7.0.27 is now in unstable. Just, the problem appearing with Ubuntu is not appearing on my machine, and if I am not erroneous then
I had that patch in the version that was uploaded. Yes, it is in:
dpkg-source: info: applying MoreInformativeAppStartFailure.patch
as seen from the build logs. This was a bit stupid of mine, but I had not believed in the issue to be located in there at the time.

What I can offer is to have yet another version uploaded to that does not have that patch included. I just saw that BOINC has an
issue with gcc 4.7, so I need to address that anyway: https://buildd.debian.org/status/package.php?p=boinc This you can then
adopt directly for Precise. Would that be acceptable?

> If
> 7.0.27 will build in Quantal, this will save some time and effort. If
> it does not, then I'll take a look at Locutus' package of 7.0.26, and
> talk to the MOTUs to see if we can get that into Quantal (I'll do the
> uploading if necessary), and then see if we can't SRU that into Precise.

The version currently shipping with Ubuntu has issues with NVidia cards with >2GB of memory. Since those cards will become
increasingly popular, I strongly suggest to move away from 7.0.24.

Steffen