Comment 105 for bug 991179

Between you and I, I agree 7.0.27 should be in Precise.

But the process for updating stable versions is complex, in that unless the fixes also exist in the latest development version, they will rarely push the stable release update.

I ran into this with six other packages, so I speak from experience on this: when SRUing they prefer the fixes and the version that has fixes to be released in current dev release (Quantal) prior to the SRU. As a result, 7.0.27 needs to be able to build in Quantal first (which it currently does not).

I also wanted to send this to you directly, and not clutter up the bug too much ;P
------
Thomas

On May 10, 2012, at 4:43 AM, Steffen Möller <email address hidden> wrote:

> 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
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/991179
>
> Title:
> 7.0.24 "computation error" bug
>
> Status in “boinc” package in Ubuntu:
> Confirmed
>
> Bug description:
> Hi. Repository versions 7.0.24, (I assume 7.0.25) and 7.0.26 have a
> known bug which affects users with various hardware running Ubuntu
> 12.04. The bug makes the boinc software unable to process any work-
> units.
>
> This is a known bug by a growing group of S@H Boinc users running
> Ubuntu 12.04 and other Debain variants.
>
> As soon as there is a version out which overcomes this bug, the
> repository package may want to be changed.
>
> Thanks.
>
> [edit] it seems this bug is only caused by the repository installs of Boinc. When one installs Boinc from the Berkeley website the issue does not exist.
> Also, the bug only seems to exist for seti@home users, apparently all other projects are unaffected? (I'm now curious it may affect "Quake Catcher Network")
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/991179/+subscriptions