7.0.24 "computation error" bug

[Dave]

Hi. Repository version 7.0.24...precise has a known bug which affects users running Ubuntu 12.04. The bug makes the boinc software unable to process any work-units for some projects.

This is a known bug by a growing group of Seti@Home 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.

Please SRU

[Impact]
This bug affects all users of Precise attempting to run Boinc 7.0.24 for the Seti@home project.

[Test case]
Bug can be reproduced by installing Boinc 7.0.24 in Ubuntu 12.04 and connecting to the seti@home project.
Downloaded work-units will instantly error upon attempting to run. In other words the Boinc package currently in the precise repository is unusable for Seti@home, and a couple others.

[Regression Potential]
Quantal has had it's version of boinc changed to 7.0.27 from Debian SID. As far as I'm aware it fixes this bug.
7.0.27 has many upstream fixes for several issues, I think that the change may bring a few new bugs, but should fix far more issues than it causes, again the current package is unusable for one of the largest projects running on Boinc.

https://launchpad.net/~blueyed Daniel Hahler has agreed to sponsor the upload for SRU

[Gianfranco Costamagna (costamagnagianfranco)]

Please update to 7.0.26 from my ppa and tell if the problem is really fixed.
https://code.launchpad.net/~costamagnagianfranco/+archive/boinc

[Dave (xclusive585)]

I will do, but I already know from personal contact with the boinc developers that this bug is fixed in .26

Thanks

[Gianfranco Costamagna (costamagnagianfranco)]

I ask you this because I don't see in the checkin notes [1] any reference to this

[1] http://boinc.berkeley.edu/svn/tags/boinc_core_release_7_0_26/checkin_notes

[Dave (xclusive585)]

Wow. Time to go harass the developers in my other forum :-)

It is indeed NOT fixed in this version.

Thanks for the ppa link and the correction. I'm sorry about the misinformation I was given

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Dave (xclusive585)]

I've updated the bug description to be more accurate. Some further input from others would be helpful.

[Gianfranco Costamagna (costamagnagianfranco)]

Ok Dave, so this seems to has nothing to do with upstream boinc.

I don't understand, if this bug is downstream (probably caused from some debian/patch) why upstream developers told you the bug was fixed?

could you please link here the thread which are you referring too?

because if the bug is really downstream I can build a boinc without patches, but I prefer to wait until you or somebody else confirm this.

thanks

[Gianfranco Costamagna (costamagnagianfranco)]

*have

[Dave (xclusive585)]

Hi, it was misinformation I had gathered from the seti@home boards. The word I received was that 7.0.26 fixed the "computation error bug" for the seti crunchers.

Here's the link (you may need a seti account) where I gathered info that 7.0.26 had this bug fix, the second message is the "misinformation" I received (you can even see my last message, updating that 7.0.26 from your ppa still was borked):
http://setiathome.berkeley.edu/forum_thread.php?id=67670

But it appears only the upstream is currently working for seti@home in Ubuntu 12.04.

There is other talk in some other threads here but not ones that outsiders can access. I am desperately trying to get a (real) developer of Boinc in on this as they should know a lot more than us dumb ol users. :-)

I wish I knew more than this. And thanks for your help!

[Dave (xclusive585)]

And I too am trying to make sure of what will work and what doesn't. I still haven't confirmed that the upstream doesn't have this issue, and I'm hoping someone can confirm what the heck is broken.

[Dave (xclusive585)]

And this link:
http://setiathome.berkeley.edu/forum_thread.php?id=67864
Is where several of us have been discussing the issue, but you can't access it without having work credit (for crunching done) tied to your account.

[Gianfranco Costamagna (costamagnagianfranco)]

Unfortunately now s@h is down for maintenance, I'll try to do some s@h work later as soon seti becomes available again.

Now I'm doing some Einstein@Home work and I didn't notice any problem so far.

But I have to say I'm using BOINC from berkeley download and not from ubuntu repo.

If you want to try a "clean" boinc install you can download .26 from [1]

and run it by doing
sh http://boinc.berkeley.edu/dl/boinc_7.0.26_x86_64-pc-linux-gnu.sh
BOINC/run_manager

it will create a new boinc profile, in the directory you run the script, so you can easily avoid collisions from both profiles, so just make sure when you run it no other boinc instances are running on your system.

[1] http://boinc.berkeley.edu/dl/boinc_7.0.26_x86_64-pc-linux-gnu.sh
      http://boinc.berkeley.edu/dl/boinc_7.0.26_i686-pc-linux-gnu.sh

[Dave (xclusive585)]

Yes, every Tuesday we lose the server for the day typically. As I said from what we've deduced, it's only the seti@home project that is affected. People that have been finding this issue have mentioned not having trouble running the other projects...

Another thing to note, is it's not ALL machines that are finding the crunching error with seti@home and 12.04/ 7.0.24etc: I have a p4 system that works fine, however boinc was installed on it during the daily build period, and I haven't purged and re-installed on that machine to test if it would still work. Also, it's not dependent on architecture, as we have users with 32 bit and 64 bit processors reporting the error.

I will try the scripted install method in a few minutes here, from what I've read from the other users it should work. I'll report back.

[Dave (xclusive585)]

Ok, I installed it and got the necessary dependencies. It's running. But as the project is down for its weekly maintenance I cannot connect my account or get work. As soon as they get back online I'll let you know how it goes.

But I'm hopeful. If this works, I'll just make a neat little script to launch it as it is. Until we figure out what's up with the repository version.

[Dave (xclusive585)]

Oh, and one more weird thing I found. The 12.04 repository version of BOINC 7.0.24(etc) is installing the BOINC data in two locations...

It installs it in /var/lib/... as I understand is the norm for the Ubuntu repo version. But it also installs doubles directly in the home/user folder which I found odd.

[Dave (xclusive585)]

OK.

The Berkeley (upstream) Linux version 7.0.26 works great on my 12.04 ubuntu box.

So something in the repository package or something specific to the seti@home app is the culprit. Seeing as how seti works fine with the Berkeley version, it is most likely specific to the repository package??

Anything else I can do to help here? I plan on bringing up the topic on the Boinc message boards in a little while.

[Dave (xclusive585)]

I think this is the same bug:
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/985622

[Gianfranco Costamagna (costamagnagianfranco)]

Hi Steffen sorry for adding you to this bug, but I think you can might have a clue of what is happening here, boinc was copied from debian sid, so I think some patch is causing this bug and I think debian is affected too. What do you think about?

[Gianfranco Costamagna (costamagnagianfranco)]

HI Dave, I have just build a boinc 7.0.26 from another of my ppa's [1] and this is build with not patch at all (just three patch to make it build of course)

Could you give it a try?
With this version you shouldn't notice this bug, I'll release new version after you tell me if you see the bug or not until we figure out which of them causes the problem.

Thanks

[1] https://code.launchpad.net/~costamagnagianfranco/+archive/locutusofborg-ppa

[Steffen Möller (moeller-debian)]

Hello,

I can confirm this problem. I have only a hunch what may be wrong, most likely the boinc-client now produces lines in its communication with the scientific app that are complete - but too long. But I have to prove that, still. The problem occurred while I was excluding potential issues with the Einstein@Home scientific app, which had eventually been identified and fixed in upstream code of 7.0.26. Einstein@Home is not affected by this issue, please consider running that or Rosetta@Home until the update is in the archive.

I had compiled the SETI App locally but that still shows that bug, so I am a bit puzzled. Go ahead with your patch-free version. For Debian I aim at 7.0.27 to have that addressed, which has seen a major update of our patches in the upstream codebase. ... should come out any time soon, now.

Cheers,

Steffen

-------- Original-Nachricht --------
> Datum: Thu, 03 May 2012 09:09:15 -0000
> Von: LocutusOfBorg <email address hidden>
> An: <email address hidden>
> Betreff: [Bug 991179] Re: 7.0.24 "computation error" bug

> HI Dave, I have just build a boinc 7.0.26 from another of my ppa's [1]
> and this is build with not patch at all (just three patch to make it
> build of course)
>
> Could you give it a try?
> With this version you shouldn't notice this bug, I'll release new version
> after you tell me if you see the bug or not until we figure out which of
> them causes the problem.
>
> Thanks
>
> [1] https://code.launchpad.net/~costamagnagianfranco/+archive
> /locutusofborg-ppa
>
> --
> 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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/991179/+subscriptions

[Dave (xclusive585)]

@Locutus. Will do, happily! It's just gonna take about 12 hours til some AP units finish up, I don't wanna risk ruining them. I'll report back.

@Steffen, I believe 7.0.27 was released in the last couple days. :-)

Thanks for the efforts guys! We all appreciate it. I can't wait to test the new ppa tonight Locutus.

[Steffen Möller (moeller-debian)]

Hello,

-------- Original-Nachricht --------
> Datum: Thu, 03 May 2012 16:11:35 -0000
> Von: Dave <email address hidden>
> An: <email address hidden>
> Betreff: [Bug 991179] Re: 7.0.24 "computation error" bug

> @Locutus. Will do, happily! It's just gonna take about 12 hours til some
> AP units finish up, I don't wanna risk ruining them. I'll report back.
>
> @Steffen, I believe 7.0.27 was released in the last couple days. :-)
Yesterday night, I think?

> Thanks for the efforts guys! We all appreciate it. I can't wait to test
> the new ppa tonight Locutus.

I just uploaded something that runs SETI for me to the archive. It is in the git repo and on http://master.dermacloud.uni-luebeck.de/~moeller/oliver

I'll keep fiddling with it to locate the culprit.

Steffen

[Dave (xclusive585)]

OK
Locutus, that 7.0.26 from the ppa works wonderfully. No computation error bug.

(sorry about the delay I had workunits that took 20 hours to complete. I removed all my boinc related files and upgraded all my packages, then I waited to see how this was running)

I can't speak for everyone else's projects, but S@H is running great with this for me. :-)

Let me know if/when it gets pushed into the standard Ubuntu repository...

[Dave (xclusive585)]

and interesting, in the changelog for 7.0.27 I read "compile fix"... Don't really know what that means for you guys, but maybe it's good news?

[Steffen Möller (moeller-debian)]

Hello,

-------- Original-Nachricht --------
> Datum: Fri, 04 May 2012 17:22:10 -0000
> Von: Dave <email address hidden>
> An: <email address hidden>
> Betreff: [Bug 991179] Re: 7.0.24 "computation error" bug

> and interesting, in the changelog for 7.0.27 I read "compile fix"...
> Don't really know what that means for you guys, but maybe it's good
> news?

The bug is fixed by undoing some presumed improvements of mine. This needs some further investigation, but even if we fix it, all scientific apps would need an update, so ...

Maybe we should just fine those aliens quickly and have them fix it all for us...or eradicate man kind.

Cheers,

Steffen

[Gianfranco Costamagna (costamagnagianfranco)]

Hi Dave and Steffen, unfortunately the bug is fixed but I agree with Steffen that we need to know the EXACTLY patch that causes the problem, you might not notice this bug, but every patch is here to fix a bug, to increase stability, to make a better boinc experience.

So just removing patches isn't the solution, what I'm doing is enabling some of them, build boinc again and ask you to test it.

I have enabled 10 more patches and I'm currently building boinc - 7.0.26+dfsg-0~827~precise1, it will be hopefully available in a few hours, it would be nice if you can test it and report back here.
thanks

[Dave (xclusive585)]

All set to test it once it's available. Says "waiting to build" currently. I'll check back in a few hours.

[Gianfranco Costamagna (costamagnagianfranco)]

I'm currently building the x64 version, the i386 one is already published.

Dave if you didn't disable my repository you will notice that an update is available, so just update and check for the bug ;)

many thanks

[Dave (xclusive585)]

Another successful build. I'm not seeing the bug with this one either. :-)

I'll be waiting for your next test.

[Steffen Möller (moeller-debian)]

Hello,

Have many thanks for all your energies going into it. The patches are listed in
http://anonscm.debian.org/gitweb/?p=pkg-boinc/boinc.git;a=blob;f=debian/patches/series
and of those my personal hunch is the have a second look at the
app_ipc_uninitialised.patch, where I had improved (so I thought) initialisations of variables. Had you tried that one, yet? I have changed the order of lines in the init file ... not thinking that this makes much of difference .. but I may be wrong.

If you have located the issue - fine. If not I suggest to leave it.

Best,

Steffen

-------- Original-Nachricht --------
> Datum: Sat, 05 May 2012 15:37:27 -0000
> Von: Dave <email address hidden>
> An: <email address hidden>
> Betreff: [Bug 991179] Re: 7.0.24 "computation error" bug

> Another successful build. I'm not seeing the bug with this one either.
> :-)
>
> I'll be waiting for your next test.
>
> --
> 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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/991179/+subscriptions

[Gianfranco Costamagna (costamagnagianfranco)]

Hi Steffen et all, I'm building I think the latest build, I have enabled almos every patch but not app_ipc_uninitialised.patch so based on Steffen comment we will find the patch that causes this problem :)

[Dave (xclusive585)]

Sounds good, I'll let you know.

[Dave (xclusive585)]

This seems fine as well.

So far so good.

[Steffen Möller (moeller-debian)]

And I just read Dave's reply that this would be just fine, indeed.
If it is not the order of lines, then my hunch is that it is the size of the buffer that I had increased, which may create larger (too large) files for the client to read.

I will split that patch in two halves - buffer and reorder - so we can test it all more easily. But I would do so for 7.0.28 and ... maybe even only through upstream and not within Debian/Ubuntu.

Steffen

-------- Original-Nachricht --------
> Datum: Sun, 06 May 2012 00:13:12 -0000
> Von: LocutusOfBorg <email address hidden>
> An: <email address hidden>
> Betreff: [Bug 991179] Re: 7.0.24 "computation error" bug

> Hi Steffen et all, I'm building I think the latest build, I have enabled
> almos every patch but not app_ipc_uninitialised.patch so based on
> Steffen comment we will find the patch that causes this problem :)
>
> --
> 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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/991179/+subscriptions

[Gianfranco Costamagna (costamagnagianfranco)]

Hi Dave and Steffen, based on your latest comment I'm building just now the (I hope) latest version, which includes the app_ipc_uninitialised.patch

I wait for your feedback. :)

thanks

[Dave (xclusive585)]

another good one.....

[Dave (xclusive585)]

I got on another Ubutu 12.04 box just to try out that standard repository version (7.0.24) with seti@home- to verify it's still broke. It is. And what's surprising is that box worked with 7.0.24/s@h, during daily builds, but not anymore.

[Dave (xclusive585)]

@ Locutus....

If this ppa has the patch Steffen thought was breaking it, we made need to re-think things a little...

What are the differences, if any, between THIS ppa 7.0.26 that works (with that patch included), and the very first one I tried that was broke?

[Dave (xclusive585)]

I just double checked on two machines to be sure your current 7.0.26 works for s@h, it does. Even on my older p4 that errored when tested with the 7.0.24 today, works great with this ppa 7.0.26! :-)

hope it helps.

[Gianfranco Costamagna (costamagnagianfranco)]

Thanks Dave for your comment and your help, I'm building another shot, there are only for patch left to check.

So the problem is this: in ubuntu/debian we have added some patch to improve boinc stability, one of those patch causes this problem.

The first build you tryed was with every patch included, just an updated version (.24 was your version, .26 was the version in my ppa)

What I have done is to package .26 without patch and include some of them to find the wrong patch.

So the first build was "clean", the second one had 10 patch, the third one other 10 patch and so on.

This build that is coming is almost the same as the official build, just without 10 patch.

So there are two scenarios now:
1) you will encounter the problem and so we have found the patch
2) the wrong patch is in the 10 patch left to check.

In my opinion this build won't work as expected.

[Dave (xclusive585)]

Sounds good. I'll check it out as soon as I can.

[Steffen Möller (moeller-debian)]

-------- Original-Nachricht --------
> Datum: Sun, 06 May 2012 16:03:30 -0000
> Von: Dave <email address hidden>
> An: <email address hidden>
> Betreff: [Bug 991179] Re: 7.0.24 "computation error" bug

> @ Locutus....
>
> If this ppa has the patch Steffen thought was breaking it, we made need
> to re-think things a little...
>
> What are the differences, if any, between THIS ppa 7.0.26 that works
> (with that patch included), and the very first one I tried that was
> broke?

You find 7.0.27 in the git repository and in the home directory of mine. I suggest to go with some additional motivation on that new version. I have not tested it with SETI, yet. Their 6.33MB app crawls with 4-8kb/s across the Atlantic. We should really find a way to have their application in boinc-app-seti distributed distributively through Debian/Ubuntu again :o) ... Update: the download made it and SETI works, albeit with a more minimal set of patches.

Steffen

[Dave (xclusive585)]

That download speed is normal anywhere. Unfortunately. :-)
Ill test whatever you guys decide to compile and put in locutus' ppa.
On May 6, 2012 1:35 PM, "Steffen Möller" <email address hidden> wrote:

> -------- Original-Nachricht --------
> > Datum: Sun, 06 May 2012 16:03:30 -0000
> > Von: Dave <email address hidden>
> > An: <email address hidden>
> > Betreff: [Bug 991179] Re: 7.0.24 "computation error" bug
>
> > @ Locutus....
> >
> > If this ppa has the patch Steffen thought was breaking it, we made need
> > to re-think things a little...
> >
> > What are the differences, if any, between THIS ppa 7.0.26 that works
> > (with that patch included), and the very first one I tried that was
> > broke?
>
> You find 7.0.27 in the git repository and in the home directory of mine.
> I suggest to go with some additional motivation on that new version. I
> have not tested it with SETI, yet. Their 6.33MB app crawls with 4-8kb/s
> across the Atlantic. We should really find a way to have their
> application in boinc-app-seti distributed distributively through
> Debian/Ubuntu again :o) ... Update: the download made it and SETI works,
> albeit with a more minimal set of patches.
>
> 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
>

[Dave (xclusive585)]

ok Locutus. This build had the bug!

So something in that last batch of patches is the culprit.

Your guys decision here on what you do next. I'm just the "yes/no" man :-)

[Gianfranco Costamagna (costamagnagianfranco)]

Hi to all, unfortunately I cannot build the .27 from steffen git in launchpad. Previously I have thought that was due to a partial commit from Steffen, but now I see that this package builds with no errors at all in my local machine, so there should be something wrong with launchpad build system.

In the meanwhile I try to figure out what's wrong I should tell that the patch is one of them:
MoreInformativeAppStartFailure.patch
client_types_buffer_size.patch
uninitialised_client_types.patch
MainDocumentConst.patch

now I'm building a package without the 2nd and 3rd one...

[Dave (xclusive585)]

sounds good, I'll let you know. At least we can figure out the bad patch. :-)

[Dave (xclusive585)]

Ok still bad. so its the first or last patch on that list you posted?

[Steffen Möller (moeller-debian)]

-------- Original-Nachricht --------
> Datum: Sun, 06 May 2012 20:21:37 -0000
> Von: LocutusOfBorg <email address hidden>
> An: <email address hidden>
> Betreff: [Bug 991179] Re: 7.0.24 "computation error" bug

> Hi to all, unfortunately I cannot build the .27 from steffen git in
> launchpad. Previously I have thought that was due to a partial commit
> from Steffen, but now I see that this package builds with no errors at
> all in my local machine, so there should be something wrong with
> launchpad build system.
>
> In the meanwhile I try to figure out what's wrong I should tell that the
> patch is one of them:
> MoreInformativeAppStartFailure.patch
> client_types_buffer_size.patch
> uninitialised_client_types.patch
> MainDocumentConst.patch
>
> now I'm building a package without the 2nd and 3rd one...

I just had a look again at the MainDocumentConst.patch . That patch can go. Upstream will not accept anything in that direction. I have removed it from the archive. Since the "const" flags are of interest for the inheritance of methode in C++, there may be a consequence in this patch that is not easy to spot. The "const" flag is excellent for any novice to learn about how some code works. That is why I like it ...

It is not "MoreInformativeAppStartFailure.patch", just tested.

The "client type" ones I have removed in my transition to 7.0.27 as it seems.

Steffen

[Dave (xclusive585)]

Sounds like Locutus should build a 7.0.26 without that "MainDocumentConst" patch then, and I can test it, and if it works perhaps it can go into the Ubuntu repository without too much worry until a later version is available?

[Gianfranco Costamagna (costamagnagianfranco)]

I'm building a package without this patch :)

[Dave (xclusive585)]

It's broke. :-( I guess try one with all except the other one?

[Gianfranco Costamagna (costamagnagianfranco)]

So based on your last information seems to be MoreInformativeAppStartFailure.patch that causes this problem.

I'm building another package without this one. If you tell me that this is ok I'll build .27 from Steffen debian git trying to solve the patch problem.

[Dave (xclusive585)]

Sounds good. I'll test it soon as it's done building. Luckily I don't have to work today. YAY! :-)

[Steffen Möller (moeller-debian)]

On 05/07/2012 04:03 PM, LocutusOfBorg wrote:
> So based on your last information seems to be
> MoreInformativeAppStartFailure.patch that causes this problem.
This is weird. I have just compiled my 7.0.27 version with that patch in
and this works nicely from what I see. Anyway. Jump over to 7.0.27 and
then we see what happens.
It may be an interaction of two patches ... but ... somewhat unlikely.

Steffen

[Dave (xclusive585)]

MoreInformativeAppStartFailure.patch is the culprit of the computation error issue. :-)

I'm relieved that that one worked. .....

[Dave (xclusive585)]

Perhaps 7.0.27 doesn't have the negative interaction with with the patch like 7.0.24/26 do...?

[Gianfranco Costamagna (costamagnagianfranco)]

So I'm building again .24 with every patch and not MoreInformativeAppStartFailure.patch, If this is good I'll go to build .27

[Dave (xclusive585)]

will this be in the ppa?

[Gianfranco Costamagna (costamagnagianfranco)]

Building right now :)
https://code.launchpad.net/~costamagnagianfranco/+archive/locutusofborg-ppa/+build/3470216
https://code.launchpad.net/~costamagnagianfranco/+archive/locutusofborg-ppa/+build/3470217

[Dave (xclusive585)]

This last 7.0.26 works as well. :-)

[Dave (xclusive585)]

If I know Locutus by now, in about 10 hours he'll be back here, and then a few hours after that, I'll wake up. So let me know what we're doing next when you are here friend. I'll test it when I can, probably around 18:00 GMT.

[Gianfranco Costamagna (costamagnagianfranco)]

Unfortunately sometimes I have to sleep :)
I'm building right now 7.0.27 with the patch "parse_issues.patch" disabled, since it doesn't build with it included (and as far as I can tell the patch has no problem), I have already filled a bug against bzr.

With a little luck the package will build and upload in a few hours, I hope launchpad won't reject it because it has different content from the same revision (since I branched an older revision without my modifications).

[Steffen Möller (moeller-debian)]

On 05/07/2012 05:24 PM, Dave wrote:
> MoreInformativeAppStartFailure.patch is the culprit of the computation
> error issue. :-)
>
> I'm relieved that that one worked. .....
>
Please update to 7.0.27. I have the client working and that patch is in.

Steffen

[Steffen Möller (moeller-debian)]

On 05/08/2012 10:30 AM, LocutusOfBorg wrote:
> Unfortunately sometimes I have to sleep :)
> I'm building right now 7.0.27 with the patch "parse_issues.patch" disabled, since it doesn't build with it included (and as far as I can tell the patch has no problem), I have already filled a bug against bzr.
>
> With a little luck the package will build and upload in a few hours, I
> hope launchpad won't reject it because it has different content from the
> same revision (since I branched an older revision without my
> modifications).
>
But don't you take it all from the git repository? That should have the
series file and the patches adjusted. Took me a while :o/

Cheers,

Steffen

[Gianfranco Costamagna (costamagnagianfranco)]

According to this [1] which is based on your git [2] the patch isn't included, I see a
#convinceDavid# MoreInformativeAppStartFailure.patch
which is clearly commented.

I thought this patch was included upstream but I cannot find any reference in the source code files.

Is this the right git?

[1] https://code.launchpad.net/~blueyed/boinc/pkg-boinc
[2] http://anonscm.debian.org/gitweb/?p=pkg-boinc/boinc.git

[Steffen Möller (moeller-debian)]

On 05/08/2012 11:02 AM, LocutusOfBorg wrote:
> According to this [1] which is based on your git [2] the patch isn't included, I see a
> #convinceDavid# MoreInformativeAppStartFailure.patch
> which is clearly commented.

Right. I had not pushed. Sorry for that.

> I thought this patch was included upstream but I cannot find any
> reference in the source code files.
I need another look at the patch. There once was a bug in boinc that
produced non-executable scientific applications. And I found that
this or something like it should be communicated better. That is
what the patch is about.
> Is this the right git?
>
> [1] https://code.launchpad.net/~blueyed/boinc/pkg-boinc
> [2] http://anonscm.debian.org/gitweb/?p=pkg-boinc/boinc.git
Yes, it is fine. Here is the commitdiff that enables the patch
http://anonscm.debian.org/gitweb/?p=pkg-boinc/boinc.git;a=commitdiff;h=124c476cb5f04285fa044e1f3abd4bfc940e00ac

Cheers,

Steffen

[Dave (xclusive585)]

Seti@home is down for its Tuesdsay maintenance. Should be up in a few hours.

If your next build goes through Locutus I'll test it as soon as the project comes online.

Good luck.

[Gianfranco Costamagna (costamagnagianfranco)]

Hi Steffen and Dave.

7.0.27 will be available in a few minutes for i386 and a 3-4 hours for amd64.

I build it without parse_issues.patch since this patch has something wrong that make build fail.

[Gianfranco Costamagna (costamagnagianfranco)]

OT Steffen your .27 boinc doesn't build on quantal quetzal release, while .24 does, but now I have no time to look at which patch could be wrong, we are in the initial developing stadium, so there's time to make it work :)
/OT

[Dave (xclusive585)]

ok, the i386 has the bug, so I assume the am64 will too.

Was this built with the MoreInformativeAppStartFailure.patch?

[Dave (xclusive585)]

I'm confused... I just installed and tested a i386 7.0.27 from the ppa, and then I check back and it says that the i386 failed to build. wth?

[Dave (xclusive585)]

oh nevermind, the failed i386 was quantal. duh.

[Gianfranco Costamagna (costamagnagianfranco)]

(just look at my off topic above about the failing build)

Dave, I'm currently building x64 version, please try it and if I have negative feedback I'll push a build without MoreInformativeAppStartFailure.patch.

(Based on Steffen words this patch wasn't a problem in the .27 build, so I leaved it here)

[Dave (xclusive585)]

So I don't wanna push anyone here, but can't we just put a 7.0.24 without the "bad" patch into the Ubuntu repository while we play with the 7.0.27?

[Dave (xclusive585)]

Indeed. The am64 also has the bug. So that patch is definitely still an issue with 7.0.27, at least with Ubuntu.

[Steffen Möller (moeller-debian)]

On 05/08/2012 07:12 PM, Dave wrote:
> Seti@home is down for its Tuesdsay maintenance. Should be up in a few
> hours.
>
> If your next build goes through Locutus I'll test it as soon as the
> project comes online.
>
> Good luck.
>
Docking@Home was also affected.

Cheers,

Steffen

[Steffen Möller (moeller-debian)]

On 05/08/2012 11:56 PM, Dave wrote:
> So I don't wanna push anyone here, but can't we just put a 7.0.24
> without the "bad" patch into the Ubuntu repository while we play with
> the 7.0.27?
7.0.24 is bad for many reasons, especially for an incompatibility with
decent NVidia cards, no, please jump to 7.0.26 or later.

Cheers,

Steffen

[Steffen Möller (moeller-debian)]

On 05/09/2012 03:12 AM, Dave wrote:
> Indeed. The am64 also has the bug. So that patch is definitely still an
> issue with 7.0.27, at least with Ubuntu.
This is not expected. Have many thanks for identifying that.

Steffen

[Dave (xclusive585)]

Happy to help, Steffen.

@Locutus, I see you put a new build in.
the i386 works great. (I'll report on the am64 within a few hours, I see it's building now)

hoping if the am64 works as well, perhaps we'll see these packages in the precise repository?

[Thomas Ward (teward)]

The Precise repos can't be updated without an SRU. SRU(s) are not always approved.

Any new versions uploaded for the repositories will end up in Quantal, unless an SRU is filed to get an update pushed to the precise-updates repository (which you will need enabled to get those updated softwares)

[Thomas Ward (teward)]

As I said in my previous comment (#80 on this bug), the Precise repositories will not be updated with any updated packages without an SRU (Stable Release Update) being filed. That is outlined here: https://wiki.ubuntu.com/StableReleaseUpdates. Any updates pushed to the package at this point will be accepted for Quantal. Can you confirm that this package builds/runs in Quantal before I start messing around with the package in my test environments to remove the patch that is referreed to as the problem causer?

I am including part of the email which was sent to the Bug Squad mailing list:

There is a patch in the precise boinc package that make it run with a computation error with 2 or more project. See [1]

After trying some time we figured out that the cause is the patch MoreInformativeAppStartFailure.patch taken from debian.
The debian mantainer already knows this problem (I take boinc directly from debian's git) and disabled the affected patch.
So what I asking for is to disable this patch in the ubuntu repo, or maybe sync the latest 7.0.27 version from my recipe
https://code.launchpad.net/~costamagnagianfranco/+recipe/boinc-daily that fixes the problem for some GPU cards.

Packaging-Specific notes for this bug and the source package (from trekcaptainusa-tw) (most people don't need to read this):
* Current Precise version: 7.0.24+dfsg-1
* Current Quantal version: 7.0.24+dfsg-1
* Changes (at this time) if done to this package will require the version change to 7.0.24+dfsg-1ubuntu1 (unless this is fixed in Debian first and then synced to Quantal)

[Dave (xclusive585)]

Well. I'd hope an "Sru" would be approved considering you currently have a
boinc package that doesn't work for one of the most used projects and at
least one other.
On May 9, 2012 1:45 PM, "Thomas Ward" <email address hidden> wrote:

> The Precise repos can't be updated without an SRU. SRU(s) are not
> always approved.
>
> Any new versions uploaded for the repositories will end up in Quantal,
> unless an SRU is filed to get an update pushed to the precise-updates
> repository (which you will need enabled to get those updated softwares)
>
> --
> 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
>

[Gianfranco Costamagna (costamagnagianfranco)]

Hi Thomas, what I'm asking is to simply remove the patch and release for precise, this boinc doesn't build in quantal, probably due to another debian patch, I'm looking into it

[Thomas Ward (teward)]

LocutusOfBorg: I will research as well, but an SRU would need to be filed for any updates to Precise, and the Packaging-Specific notes for this bug (see comment 81) apply: the package name would change.

Considering this is in Universe, I can poke the MOTUs to help out in getting the SRU through, but someone will need to file the SRU.

As well, the patch issue in Precise (may) need changing in Quantal as well, but I'll check with the MOTUs first, they'd know (since boinc is in Universe).

[Dave (xclusive585)]

Its too bad this bug didn't show in 12.04 before its final release,
otherwise I would have reported it before 12.04 got locked. But for
whatever reason it worked fine until 12.04 was final and I reinstalled
boinc, it was only then that the bug showed
On May 9, 2012 2:55 PM, "Thomas Ward" <email address hidden> wrote:

> LocutusOfBorg: I will research as well, but an SRU would need to be
> filed for any updates to Precise, and the Packaging-Specific notes for
> this bug (see comment 81) apply: the package name would change.
>
> Considering this is in Universe, I can poke the MOTUs to help out in
> getting the SRU through, but someone will need to file the SRU.
>
> As well, the patch issue in Precise (may) need changing in Quantal as
> well, but I'll check with the MOTUs first, they'd know (since boinc is
> in Universe).
>
> --
> 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
>

[Dave (xclusive585)]

@Locutus, the am64 works also. Just in case your curious.

that 7.0.27 is running on a i386 machine of mine, and on a am64, running well on both with S@H.

Thanks Locutus for the work you put in trying all these builds out. I'm going to keep that working 7.0.27 on both of my boxes until I hear there is a repository change.

If anyone needs me to test anything, I'm around when I can be.

[Gianfranco Costamagna (costamagnagianfranco)]

Thanks for your help Dave, I think your help is not needed anymore, now we have to wait for some MOTU decision, to drop this version or other.

BTW for everyone affected by this bug I'm publishing this package in my boinc development ppa too
https://code.launchpad.net/~costamagnagianfranco/+archive/boinc

[Thomas Ward (teward)]

LocutusOfBorg:
Dave:

Does 7.0.27 work and build on Precise and Quantal? If that fixes this bug, then a sync request can (probably) be done for Quantal to get 7.0.27 from Debian Sid, and then either a backport or an SRU can be done to get that into Precise (if and only if it builds and runs correctly in Quantal).

[Dave (xclusive585)]

I can't/won't test for Quantal

But I do know Locutus has been unable to get 7.0.27 to build for it here at launchpad... He/I think it's probably due to another Debian patch?

[Dave (xclusive585)]

oh and again @thomas, this 7.0.27 that Locutus compiled without the problem patch, works fine in Precise for both i386 and am64. (I do not use a GPU for crunching, so I can't speak for that half of it.)

and @Locutus, thanks for putting the working 7.0.27 into it's own repository. Some people will be happy to have that option for now. :-)

[Daniel Manrique (roadmr)]

Importance: Medium, as per the following criteria by BugSquad member trekcaptainusa-tw:

given that the program is non-core, and given the bug affects 11 people, and given that it impacts the functionality of the non-core program in a significant manner, I believe it should be Medium. (from the Bugs/Importance page, under "Medium": A bug that has a severe impact on a non-core application.)

[Thomas Ward (teward)]

Dave: It's irrelevant if it builds in Precise or not, the SRU team (I checked with them) won't apply a Stable Release Update to Precise unless there's no other alternative, given that their methodology usually states that whatever update is occurring *should* build (and ideally exist) in latest Dev (Quantal).

[Dave (xclusive585)]

Well, that's Locutus' department. :-)

I hope it gets figured out why it wont build for quantal. I'll bet the source would, but when all those patches get thrown in... well you get the idea.

When it does get figured out and will build for quantal, I hope the update is applied. 12.04 is a LTS and therefore should have working packages IMHO. ;-)

[Dave (xclusive585)]

And one more thing to consider, Locutus has mentioned. The version in the Ubuntu repository need not change from 7.0.24 (though it would be preferred just due to the fixes in the source), 7.0.24 could be kept, and made to work, just by compiling without the ONE pad patch that's breaking it... Just an afterthought.

[Thomas Ward (teward)]

Dave: did Locutus test that on Quantal as well, with the building and running? that "fix" would need applied in quantal before its SRU'd (the same thing I said in comment #92 about the SRU stuff still applies, even to this kind of fix you've mentioned)

[Dave (xclusive585)]

He'll have to comment in the AM, but yes I believe they all built in quantal without the "bad" patch, except the 7.0.27

So perhaps he can try to build the 7.0.26 (without the "bad" patch), and push that for quantal, so that it can end up in Precise?

[Thomas Ward (teward)]

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. 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.

------
Thomas
BugSquad Member

[Rocky37 (regreen-deactivatedaccount)]

Just checked for updates and was surprised to find 7.0.27

Many thanks to you all for this wonderful fix -- Hugs to all!!!!

[TheDreamer (thedreamer-lhaven)]

Well, my bug #985622 was reported against 12.04 beta 2.

On 05/09/2012 02:12 PM, Dave wrote:
> Its too bad this bug didn't show in 12.04 before its final release,
> otherwise I would have reported it before 12.04 got locked. But for
> whatever reason it worked fine until 12.04 was final and I reinstalled
> boinc, it was only then that the bug showed
> On May 9, 2012 2:55 PM, "Thomas Ward" <email address hidden> wrote:
>

[Steffen Möller (moeller-debian)]

On 05/10/2012 06:48 AM, Rocky37 wrote:
> Just checked for updates and was surprised to find 7.0.27
>
> Many thanks to you all for this wonderful fix -- Hugs to all!!!!
>

Hey, great! Nice to "see" you happy. Thanks also from my side to
Lotus, Dave and the folks behind the PPA build demons.
Is it working for everyone?

The upload to Debian unstable has that patch in that has caused the trouble for Ubuntu. But at least on my machine all the prior
problematic projects do work with it. This would be somewhat in line with the late observation in 12.04. So, even when I think
that we have not understood everything about this bug, yet, let's go ahead.

Cheers,

Steffen

[Steffen Möller (moeller-debian)]

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

[Thomas Ward (teward)]

Steffen:

Referring back to my earlier comment regarding SRU, to update the Precise package (and get the updated version into the precise-updates repository), an SRU request would need filing. I went and talked with one of the SRU team, and they would want a version to exist in the current development version (Quantal) that builds and runs. Then, with that version, it can be SRU'd to Precise.

In short, Precise is in a sense 'frozen' on its current version (7.0.24+...) until a version exists that builds on Quantal (of which 7.0.27 does not).

I should point out that while I am BugSquad, the decision on Precise updating is up to the SRU team and the MOTUs, neither of which I am. Ideally, though, a version needs to exist in Quantal that builds an runs before SRU-ing to Precise, except on very rare circumstances (summarization of what the SRU team member told me). Given that UDS will be going on today and tomorrow, I am not going to poke the MOTUs or the SRU team about this until tomorrow.

[Thomas Ward (teward)]

Correction: I won't bother them until at leat Sunday.

[TheDreamer (thedreamer-lhaven)]

Well, I can't really comment on that....because I haven't been able to get
12.04 Release to install on such a system. The desktop installer panics right
away, the alternate installer panics on first boot after its done.

Its supposed to be my Windows desktop, but I had envisioned virtualizing
it....since it died mid-February after automatically installing a bunch of
patches from Microsoft, and I had been waiting for 12.04 release to make this
attempt. Probably going to go non-Linux, since I want a machine at home now
to learn/play with the environment that we're doing virtualization at work with.

I did try to push out a 12.04LTS server at work, but got called out when $boss
found out.... someday it might happen....but it'll have to wait until a bigger
customer asks for it. The other OS, came about because we support a .gov that
has an aging Solaris box...which they like, but had outgrown and its
dying....but they didn't want to spend money on a new Sunoracle server. Plus
they've gotten to like containers, and wanted to do more than just that.
$boss mentioned he had read about $X that might be something for them to try.
Now a couple years later (and 3 less FTEs, including the one that dealt with
them and could go on site [even though I lived across the street from them]
)....that customer has shown up with a new whitebox, and they want us to make
it happen. (says so in the new SLA)

On 05/10/2012 03:43 AM, Steffen Möller wrote:
> 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

[Thomas Ward (teward)]

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 on...

[Thomas Ward (teward)]

damn it, that email was addressed directly, stupid reply button.

Anyways, I'm poking the MOTUs or SRU people to comment on this bug, and I"m going to beat my email client.

[Thomas Ward (teward)]

also: minor correction: six should say several, my email client doesn't like the word 'several' for some reason.

[Dave (xclusive585)]

It seems like there is a plan here kind-of.

-Steffen compiles 7.0.27 without the patch affecting ubuntu.
-Locutus figures out how to get it to build for quantal.
-It gets put in as quantal's boinc package.
-We then file the SRU, and push this to Precise with good cause.

Am I missing anything?
On May 10, 2012 9:15 AM, "Thomas Ward" <email address hidden> wrote:

> also: minor correction: six should say several, my email client doesn't
> like the word 'several' for some reason.
>
> --
> 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
>

[Thomas Ward (teward)]

I'm going to let the SRU team and/or MOTUs comment here, i've asked them to outline the procedures on this bug, they'll give you a working plan.

[Thomas Ward (teward)]

New Updates:

It may be prudent to deal with the Quantal side first.

The issue on Quantal is that 7.0.27 has an issue of FTBFS (Fails to build from Source). It may be prudent to talk to the MOTUs and see whether they'd support a sync to Quantal with the FTBFS included, and then backport from Quantal to Precise where it does build.

This would require additional discussion with the MOTUs (in my opinion), either by someone here, or by myself, but if they're supportive of the idea of syncing with Quantal with the FTBFS issue for the sake of backporting to Precise (Note someone'd need to test build/run this), then unless any of you files the sync request, I'll file it.

------

Also, if the FTBFS issue on Quantal has anything to do with Debian Bug #671999, then that will be available for sync sometime next week.

[Thomas Ward (teward)]

NOTE: Comment #110 The thing doesnt like Debian bug numbers.

This link refers to that Debian bug: http://bugs.debian.org/671999

[Dave (xclusive585)]

I'm reallllllly trying to figure out how to free up a machine for quantal. I may be able to, but I'll only be able to test i386.

There's also virtualbox, but I don't think that's sufficient for testing...

[Steffen Möller (moeller-debian)]

Hello,

On 05/10/2012 04:05 PM, Thomas Ward wrote:
> New Updates:
>
> It may be prudent to deal with the Quantal side first.
>
> The issue on Quantal is that 7.0.27 has an issue of FTBFS (Fails to
> build from Source). It may be prudent to talk to the MOTUs and see
> whether they'd support a sync to Quantal with the FTBFS included, and
> then backport from Quantal to Precise where it does build.
>
> This would require additional discussion with the MOTUs (in my opinion),
> either by someone here, or by myself, but if they're supportive of the
> idea of syncing with Quantal with the FTBFS issue for the sake of
> backporting to Precise (Note someone'd need to test build/run this),
> then unless any of you files the sync request, I'll file it.
>
> ------
>
> Also, if the FTBFS issue on Quantal has anything to do with Debian Bug
> #671999, then that will be available for sync sometime next week.
>
> ** Bug watch added: Debian Bug tracker #671999
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671999
That is a friendly non-maintainer upload fixing the missing "#include
unistd.h" everywhere that gcc 4.7 requests. Sadly, the patch that should
be out is still in.
The version I just asked Thorsten to be uploaded closes that bug and
also this one (lp: 99179).

To me, the way through Quantal is just fine. Debian does the same with
backports.debian.org. What goes in there as a new package is also in
unstable.

Steffen

[Ben Giacalone (benjg011)]

Just tried to run your 7.27 on Dell 630 laptop which had no problem before 12.04 upgrade and I get computation error on all work units for Seti@home.

Thanks,

Ben

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Dave
Sent: Thursday, May 10, 2012 9:32 AM
To: <email address hidden>
Subject: [Bug 991179] Re: 7.0.24 "computation error" bug

I'm reallllllly trying to figure out how to free up a machine for quantal. I may be able to, but I'll only be able to test i386.

There's also virtualbox, but I don't think that's sufficient for testing...

--
You received this bug notification because you are subscribed to a duplicate bug report (994741).
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

[Thomas Ward (teward)]

Steffen: I'll point the MOTUs to here, eventually, but because of UDS, I'm going to give them a break until next week :P

Dave: I use VBox images to test backports and even builds, its a valid method to test package builds, and its acceptable for testing of backports and updates (especially when you dont have a spare machine to put the latest versions onto)

[Dave (xclusive585)]

Since we should have a few days while things get sorted out here, I guess I'll throw a Quantal virtual machine on my server in the meantime. :-)

[Steffen Möller (moeller-debian)]

On 05/10/2012 04:49 PM, Ben Giacalone wrote:
> Just tried to run your 7.27 on Dell 630 laptop which had no problem
> before 12.04 upgrade and I get computation error on all work units for
> Seti@home.
>
Hi Ben,

somewhere in this thread there is hidden a pointer to
https://launchpad.net/~costamagnagianfranco/+archive/boinc
with a corrected version of BOINC by LocutusOfBorg. This should get you
back to SETI. Projects that are not affected are Einstein@Home or
Rosetta. Feel free to contribute to those until we have this sorted out
here ... cannot take too long.

Anyway, nice to meet you all in this thread.

Steffen

[Ben Giacalone (benjg011)]

I just installed 7.0.27+dfsg-0~827~precise1 onto a Dell 630 laptop which had been running fine until 12.04 LTS upgrade. I am still getting "computation error" on (9) work units that just downloaded.

[Dave (xclusive585)]

Ben I'm wondering if it's possible you ended up with double files or just a borked install..

you should "apt-get remove boinc", "apt-get autoremove", and then install boinc again. You are the first to have this error with that package you are using.

[Steffen Möller (moeller-debian)]

Hello,

On 05/10/2012 05:16 PM, Ben Giacalone wrote:
> I just installed 7.0.27+dfsg-0~827~precise1 onto a Dell 630 laptop which
> had been running fine until 12.04 LTS upgrade. I am still getting
> "computation error" on (9) work units that just downloaded.

This is unexpected. I presume this is the version that Lotucus
created to prove the bug location. Sorry, then. As a quick fix,
please try

wget
http://master.dermacloud.uni-luebeck.de/~moeller/oliver/boinc-client_7.0.27+dfsg-3_amd64.deb
sudo dpkg -i boinc_client_7.0.27+dfsg-3_amd64.deb*

*That was built with gcc 4.7 and Debian but I would expect to work
nonetheless for 12.04.

Steffen

[Gianfranco Costamagna (costamagnagianfranco)]

Hi Steffen, I repeat, your latest boinc doesn't build from source. https://launchpadlibrarian.net/104761349/buildlog.txt.gz

I'll try to branch it and build without this patch.

[Dave (xclusive585)]

Locutus, I see your changing packages around in that PPA, is there going to be that "proven to work" 7.0.27 in a ppa, because people are already coming back on my end about the bug being back, with the version currently in ppa:costamagnagianfranco/boinc

[Dave (xclusive585)]

(Unfortunately I have to go to make some money, so) I won't be able to test anything out right now.

[Thomas Ward (teward)]

I'd recommend you pull something out of my book in terms of your PPA(s): create a staging PPA for you to test your builds in, and then when you have a working one, you upload to the deployment PPA (the PPA the public should use).

I find it useful for when you are constantly messing with packages to make em work. I do this for other projects in which I do packaging for them, and it prevents a lot of hassle when the community relies on a specific PPA.

Just my two cents on that.

Also, once the latest push to Debian gets accepted and published in Debian, I believe I have some of the MOTUs support to sync that to Quantal with the FTBFS errors, and then backport that to Precise where it does work (Locutus, please confirm if it builds in Precise).

[Gianfranco Costamagna (costamagnagianfranco)]

I know this, but what I'm doing is only to package 7.0.27 from Steffen's git, since it has disabled the patch causing this bug, so this update shouldn't trigger this bug anymore, it should be working and Steffen has confirmed this too.

So I'm just updating the package in my ppa because this update fixes so many GPU bugs and doesn't trigger this bug.

If somebody has this bug again the cause should be looked in another part.

Dave please when you can confirm that this build 7.0.27+dfsg-0~829~precise1 hasn't this bug.

I'm building for oneiric, precise and quantal, so it can be synced whenever you want.

[Gianfranco Costamagna (costamagnagianfranco)]

And BTW the 7.0.27 hasn't been published right now, so any people experiencing this bug has a different bug.

[Ben Giacalone (benjg011)]

Dave,

I did what you recommended below and installed Boinc. After a couple of hours Seti@home finally connected and I got the following message:

Seti@home: Notice from Server

Your app_info.xml file doesn’t have a usable version of Seti@home enhanced

Thanks,

Ben

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Dave
Sent: Thursday, May 10, 2012 10:25 AM
To: <email address hidden>
Subject: [Bug 991179] Re: 7.0.24 "computation error" bug

Ben I'm wondering if it's possible you ended up with double files or just a borked install..

you should "apt-get remove boinc", "apt-get autoremove", and then install boinc again. You are the first to have this error with that package you are using.

--

You received this bug notification because you are subscribed to the bug report.

 <https://bugs.launchpad.net/bugs/991179> 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> https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/991179/+subscriptions

[Dave (xclusive585)]

@ Locutus.

I can gladly confirm "7.0.27+dfsg-0~829~precise1" does not have our bug. I am running some units right now (i386)

:-)

I'll let you know about am64, but we already know our bug is not architecture dependent.

[Gianfranco Costamagna (costamagnagianfranco)]

Boinc 7.0.27+dfsg-0 building in quantal.
https://code.launchpad.net/~costamagnagianfranco/+archive/boinc

So I think we are ready for a SRU just now.

[Thomas Ward (teward)]

The MOTU SRU team isn't going to support an SRU in this case (because of a version change, according to the MOTUs I spoke to yesterday). They are more likely to be willing to support a sync to Quantal for the Debian version of the package, and then a backport of that to Precise (the repository that will contain the updated BOINC is therefore precise-backports).

On May 11, 2012, at 5:50 AM, LocutusOfBorg <email address hidden> wrote:

> Boinc 7.0.27+dfsg-0 building in quantal.
> https://code.launchpad.net/~costamagnagianfranco/+archive/boinc
>
> So I think we are ready for a SRU just now.
>
> --
> 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

[Dave (xclusive585)]

Isn't this last build the debian package? Or does it not count because it's GIT?

At least if we get the package in Quantal, its a start I guess.

But don't be surprised if people keep saying things like:
"I encountered the bug and was quite unhappy with it... I gave up on Ubuntu/Kubuntu and moved on over to OpenSUSE"
(actual Boinc user's advice to another)

[Gianfranco Costamagna (costamagnagianfranco)]

Sorry for that, I have not the power of Master Of The Universe, so I can't help for that.

The only thing you can do is to help in downloading the official package or use my ppa
https://code.launchpad.net/~costamagnagianfranco/+archive/boinc

I'll try to keep it up to date and bug free.

[Dave (xclusive585)]

It's not your fault locutus. You have been more than helpful, and we figured out an issue. There is nothing more you can do. :-)

I just get mad at those flamers on my end of the net. I'm defensive of Ubuntu vs other distros because I feel it has the most support... Anyways I'll keep the Ubuntu users over on my boards updated with your boinc ppa Locutus.

Thanks Locutus, Steffen, and Thomas. All your efforts are very much appreciated.

[Gianfranco Costamagna (costamagnagianfranco)]

I tryed to be menber of bug squad, but I wasn't ready. now I'm learning a little bit, and one day, maybe after my master degree I'll try to apply again for bugquad and maybe for the official boinc ppa here... But now I have to do my master thesis and the time is always a problem :) I need a 25 hours day ;)

regards, Hope they'll fix the problem soon.

[Thomas Ward (teward)]

Dave: no problem, happy to help where I can.

All: I'm testing whether the package would build with a direct sync from Debian, and then am testing the backport locally, i'll help get the sync request and backport requests done for ya.

[Thomas Ward (teward)]

Sync request from Debian Sid to Quantal for 7.0.27+dfsg-3 (in Debian): https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/998195

Once this goes through, i'll look into getting this backported to precise-backports

[Dave (xclusive585)]

And it's verified that package doesn't have the "bad" patch enabled?
On May 11, 2012 3:20 PM, "Thomas Ward" <email address hidden> wrote:

> Sync request from Debian Sid to Quantal for 7.0.27+dfsg-3 (in Debian):
> https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/998195
>
> Once this goes through, i'll look into getting this backported to
> precise-backports
>
> --
> 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
>

[Thomas Ward (teward)]

Dave: that will need testing, but afaict the changelog for the version in Debian closes this bug here.

lemme get you an excerpt.

(also, assigned to myself since i'm working on the sync request and the backport, which will ultimately close this bug)

debian/changelog for the version being synced to quantal (notice where it closes this bug, which is number 991179):

boinc (7.0.27+dfsg-3) unstable; urgency=low

  * Now truly reconstituting compatibility with SETI
    (Closes: #672328, lp: #991179).
  * builds with gcc 4.7 (Closes: #671999)
    Thanks to Matthias Klose for his patch, had sadly only seen it after
    I patched it myself :o/ The NMU of his should not kick in because
    of the SETI incompatibility.

 -- Steffen Moeller <email address hidden> Thu, 10 May 2012 10:59:30 +0200

[Thomas Ward (teward)]

bah, IRC lingo.

"afaict" should be "as far as i can tell"

[Steffen Möller (moeller-debian)]

Hello, yes, and I had one report from Debian in the meantime, too, who had already confirmed this version to be fine with him (and SETI). Cheers, Steffen

> debian/changelog for the version being synced to quantal (notice where
> it closes this bug, which is number 991179):
>
> boinc (7.0.27+dfsg-3) unstable; urgency=low
>
> * Now truly reconstituting compatibility with SETI
> (Closes: #672328, lp: #991179).

[Dave (xclusive585)]

Hi guys. Thanks for the verify Steffen.

Thomas if you update here when a repository change happens for Quantal: I have got my server's virtual machines up and running today (since my server's change to 12.04) and I installed a Qualtal-desktop-64, so I can test the updated quantal-64 boinc when it comes around.

[Launchpad Janitor (janitor)]

This bug was fixed in the package boinc - 7.0.27+dfsg-3

---------------
boinc (7.0.27+dfsg-3) unstable; urgency=low

  * Now truly reconstituting compatibility with SETI
    (Closes: #672328, lp: #991179).
  * builds with gcc 4.7 (Closes: #671999)
    Thanks to Matthias Klose for his patch, had sadly only seen it after
    I patched it myself :o/ The NMU of his should not kick in because
    of the SETI incompatibility.

 -- Steffen Moeller <email address hidden> Thu, 10 May 2012 10:59:30 +0200

[Thomas Ward (teward)]

the fix in Quantal is released, the package will be in Quantal as soon as the synced version is published in the repos (should be very soon).

I'll get to work on backporting this to Precise, so the people who are having this problem in Precise can have a (fixed) version. But someone should check to see whether that patch that had to be removed *is* actually removed in Quantal (I didn't check, since i've been busy fixing my system)h

[Dave (xclusive585)]

Thomas I'll check it out. Is there a link or somewhere I can see the repository package status, like when I was checking Locutus' PPA waiting for builds to finish?

[Thomas Ward (teward)]

I confirmed with MOTUs and the archives that the version from Debian is imported already.

You can just install it in Quantal.

The "Bad" patch is in the package, so the package'll need ubuntu-only changes, I'll work with the MOTUs on that, but I'll need a summary of why that patch is bad (i dont have the time to search through 144 comments :P)

[Thomas Ward (teward)]

Check, though, to see if the bad patch is still a troublemaker, if it is, file a bug specific for that patch's removal with the summary, i think i can get the ubuntu-only changes to be sponsored if there's a linked bug.

[Thomas Ward (teward)]

Actually, on further checks, the package correctly builds in Quantal with the trouble-patch included.

LocutusOfBorg: Do me a favor and pull a copy of the package as it exists in Quantal, and see if it builds. Since it (so far) builds correctly with the 'parse_issues.patch' patch you referenced in the sync request as being a troublemaker.

[Dave (xclusive585)]

well whichever patches are enabled or not, I am not getting the computation error in Quantal-64 (virtual box). Crunching away at a unit right now.

I can gladly report. :-)

[Steffen Möller (moeller-debian)]

Hello,

-------- Original-Nachricht --------
> Datum: Sun, 13 May 2012 16:54:19 -0000
> Von: Thomas Ward <email address hidden>
> An: <email address hidden>
> Betreff: [Bug 991179] Re: 7.0.24 "computation error" bug

> I confirmed with MOTUs and the archives that the version from Debian is
> imported already.
>
> You can just install it in Quantal.
>
> The "Bad" patch is in the package,
No, it is not.

> so the package'll need ubuntu-only
> changes,
This should not be required. And whenever there happen to be additional requirements for Ubuntu, please forward them to our shared git archive so they go through Debian.

> I'll work with the MOTUs on that, but I'll need a summary of
> why that patch is bad (i dont have the time to search through 144
> comments :P)

:o)

I consider the issue closed. Something we should now address together is the backporting to releases older than Precise with the notify 0.5 library (now at 0.7) . I will contact Daniel and Locutus about it.

Cheers,

Steffen

[Thomas Ward (teward)]

Steffen, the patch reported to have the problem, the 'parse_issues.patch' exists in the Quantal package, and the Debian package (I dissected the package myself, its still there).

Backporting to older than Precise may be a tiny bit difficult, but before I help out wiht the backports to Oneiric and earlier, it has to be backported to Precise.

I'm working on the paperwork now, but i have to finish fixing my dev environment. Once I fix my development environment, i'll test a no-changes backport to Precise, and then from there work my way onto Oneiric. Natty is going out when Quantal gets released, so I will look into backporting to that, but the backport priority order on that for me is as follows:

1) Precise
2) Oneiric
3) Natty
4) Lucid

[Dave (xclusive585)]

Just for clarification. I believe that patch Thomas refers to was believed
to be causing issues building the package for Ubuntu.
The patch found to cause the computation error was
moreinformativeappstart.patch or something like that.
On May 13, 2012 3:25 PM, "Thomas Ward" <email address hidden> wrote:

> Steffen, the patch reported to have the problem, the
> 'parse_issues.patch' exists in the Quantal package, and the Debian
> package (I dissected the package myself, its still there).
>
> Backporting to older than Precise may be a tiny bit difficult, but
> before I help out wiht the backports to Oneiric and earlier, it has to
> be backported to Precise.
>
> I'm working on the paperwork now, but i have to finish fixing my dev
> environment. Once I fix my development environment, i'll test a no-
> changes backport to Precise, and then from there work my way onto
> Oneiric. Natty is going out when Quantal gets released, so I will look
> into backporting to that, but the backport priority order on that for me
> is as follows:
>
> 1) Precise
> 2) Oneiric
> 3) Natty
> 4) Lucid
>
> --
> 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:
> Fix Released
>
> 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
>

[Thomas Ward (teward)]

That was the confusion, because Locutus referred to a different patch.

On May 13, 2012, at 3:31 PM, Dave <email address hidden> wrote:

> Just for clarification. I believe that patch Thomas refers to was believed
> to be causing issues building the package for Ubuntu.
> The patch found to cause the computation error was
> moreinformativeappstart.patch or something like that.
> On May 13, 2012 3:25 PM, "Thomas Ward" <email address hidden> wrote:
>
>> Steffen, the patch reported to have the problem, the
>> 'parse_issues.patch' exists in the Quantal package, and the Debian
>> package (I dissected the package myself, its still there).
>>
>> Backporting to older than Precise may be a tiny bit difficult, but
>> before I help out wiht the backports to Oneiric and earlier, it has to
>> be backported to Precise.
>>
>> I'm working on the paperwork now, but i have to finish fixing my dev
>> environment. Once I fix my development environment, i'll test a no-
>> changes backport to Precise, and then from there work my way onto
>> Oneiric. Natty is going out when Quantal gets released, so I will look
>> into backporting to that, but the backport priority order on that for me
>> is as follows:
>>
>> 1) Precise
>> 2) Oneiric
>> 3) Natty
>> 4) Lucid
>>
>> --
>> 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:
>> Fix Released
>>
>> 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
>>
>
> --
> 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:
> Fix Released
>
> 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.
>
...

[Steffen Möller (moeller-debian)]

Ah! I need to invest the github repository, I presume. Locutus checks out from there and apparently some adjustment of mine with the latest updates of BOINC has not made it back into the remote git repository....or something like it. What has found entry to the Debian archive comes from my local repository .. and that apparently just builds.

Cheers,

Steffen

-------- Original-Nachricht --------
> Datum: Sun, 13 May 2012 20:45:54 -0000
> Von: Thomas Ward <email address hidden>
> An: <email address hidden>
> Betreff: Re: [Bug 991179] Re: 7.0.24 "computation error" bug

> That was the confusion, because Locutus referred to a different patch.
>
>
> On May 13, 2012, at 3:31 PM, Dave <email address hidden> wrote:
>
> > Just for clarification. I believe that patch Thomas refers to was
> believed
> > to be causing issues building the package for Ubuntu.
> > The patch found to cause the computation error was
> > moreinformativeappstart.patch or something like that.
> > On May 13, 2012 3:25 PM, "Thomas Ward" <email address hidden> wrote:
> >
> >> Steffen, the patch reported to have the problem, the
> >> 'parse_issues.patch' exists in the Quantal package, and the Debian
> >> package (I dissected the package myself, its still there).
> >>
> >> Backporting to older than Precise may be a tiny bit difficult, but
> >> before I help out wiht the backports to Oneiric and earlier, it has to
> >> be backported to Precise.
> >>
> >> I'm working on the paperwork now, but i have to finish fixing my dev
> >> environment. Once I fix my development environment, i'll test a no-
> >> changes backport to Precise, and then from there work my way onto
> >> Oneiric. Natty is going out when Quantal gets released, so I will look
> >> into backporting to that, but the backport priority order on that for
> me
> >> is as follows:
> >>
> >> 1) Precise
> >> 2) Oneiric
> >> 3) Natty
> >> 4) Lucid
> >>
> >> --
> >> 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:
> >> Fix Released
> >>
> >> 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
> >>
> >
> > --
>...

[Gianfranco Costamagna (costamagnagianfranco)]

Sorry for misunderstanding I wasn't so clear.
This bug is triggered (as Dave said) by moreinformative... patch.

This patch has been removed upstream so no changes "ubuntu1" is needed.

I personally DON'T want to diverge brances of boinc from debian to ubuntu, the collaboration between those distros is so close, so I don't think we have to diverge. Patches can be accepted into debian if we find a patch here and maybe sent upstream (I have close collaboration with upstream developers too)

The parse_error.patch has been a problem for me, since I build with a recipe boinc directly synced from steffen's git.

For some reason quilt doesn't apply on bzr server correctly.
I filed a bug against bzr https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/998889

So to everybody I personally think boinc can be backported until oneiric with no changes at all. I built it for oneiric, precise and quantal, so for now earlier backports can wait a little bit.

Sorry for misunderstanding, I hope this post will clarify everything.

[Dave (xclusive585)]

I don't wanna beat a dead horse, but can someone update here if/when "apt-get install boinc" will install the working 7.0.27 in Precise?

thanks. :-)

[Gianfranco Costamagna (costamagnagianfranco)]

Hi Dave a bug has been opened against backport [1]

please test ppa [2] and tell which of test case from bug 1000492 works :)

thanks

[1] https://bugs.launchpad.net/precise-backports/+bug/1000492
[2] https://launchpad.net/~micahg/+archive/sru-test/

[Dave (xclusive585)]

I've tested the SRU package from Micah's ppa: (7.0.24+dfsg-1ubuntu0.1~ubuntu12.04.1~ppa1 boinc package), and it seems fine.

I do not see the "computation error bug", or any other issues so far. (I'll mention again I do not use a GPU for crunching so I cannot speak for that)

I haven't had time to test your 7.0.28 Locutus. Ill get to it soon.

[Dave (xclusive585)]

I think it's funny that after we decide to get the fix into quantal for a backport to precise, then they go the route of an SRU fix. LOL

[Dave (xclusive585)]

Items marked with an [X] have been confirmed/tested.

* precise:
[X] Package builds without modification
[X ] boinc-manager installs cleanly and runs
[ ] boinc-dbg installs cleanly and runs ***seemed to install cleanly, unaware how to "run" it.
[ ] boinc-cgi-stripchart installs cleanly and runs ***seemed to install cleanly, unaware how to "run" it.
[X ] boinc-client installs cleanly and runs
[X ] boinc installs cleanly and runs
[ ] boinc-dev installs cleanly and runs ***seemed to install cleanly, unaware how to "run" it.
[ ] boinc-app-examples installs cleanly and runs ***seemed to install cleanly, unaware how to "run" it.
[ ] boinc-server-maker installs cleanly and runs ***seemed to install cleanly, unaware how to "run" it.
[ ] boinc-nvidia-cuda installs cleanly and runs
[ ] boinc-amd-opencl installs cleanly and runs

That's the best I can offer (in all my noobish glory)

[Clint Byrum (clint-fewbar)]

Hello Dave, or anyone else affected,

Accepted boinc into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/boinc/7.0.27+dfsg-5ubuntu0.12.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!