No, the developer ran into difficulties building the new libCURL, OpenSSL, Zlib and Sqlite3 libraries since there are projects out there that started dropping support for the program they were originally built with. As such he's rebuilding everything with a new version, which is slowing it all down.

Plus the plan is to release .26 on all platforms with bug-fixes for all in them. Somewhere this week.
____________Jord

Berkeley installer 7.0.26 is now available.
See the change log thread (last post) for change log and links to binaries.

Remember, if you're using a BOINC from repositories, you cannot use this BOINC to upgrade. The Berkeley installer installs to a different directory. You either have to bug your distro's devs for a version bump, or you can try your hand at compiling it yourself following these instructions.
____________Jord

Thanks, but the sh and rm lines there make no sense to me, what
does
rm http://<anything>
mean? Yes, I know what you meant to type.

A more important is is my question: will this image
use the existing records in /var/lib/boinc-client
in the same way the Ubunto package would?

I don't see
how given the Ubuntu stuff installs as user boinc.
And unless one does something about the existing stuff
the existing boinc-mgr will still be attempting to run.

I appreciate your effort, I've been too busy on other things
to even attempt to understand the issues (Compiling boinc
was easy, but the same user/location issues arise as with
the berkeley shell version).

Since the Ubuntu 12.04 repository Boinc package currently has the "computation error" for many seti@home users, I thought I'd re-post this in the Q+A where newcomers can see it.
Ubuntu 12.04 users experiencing the bug with the 7.0.24 repository package, can install and use the working 7.0.26 Boinc directly from Berkeley.

To install and use Berkely's 7.0.26 Boinc in Ubuntu:
Start by opening a terminal. (you can simply type "terminal" into unity's search to find the icon)

Type each line EXACTLY as written, hitting enter after typing each line.
[For 64bit:]

This will leave a folder named "BOINC" located at "/home/<yourusername>/BOINC"
If you know your way around Ubuntu you can make a shortcut icon to "/home/<username>/BOINC/run_manager" that launches it as a .sh (shell script).

And yes you need to remove your existing stuff. My instructions assume a system that has had boinc-manager and client removed, but have the required libs in place. It's just a simple way to get the client up and running. It's not perfect.
I think the Berkeley version depends on the same lib files the Ubuntu repo version does. I satisfied the dependencies by installing boinc from the repository which adds all of the lib files, then I removed just "boinc-manager" and "boinc-client" which just leaves the lib files left over, and allows you to run the client downloaded directly from Berkley.

You can see our discussion here on s@h of the Ubuntu 12.04/boinc 7.0.24(25/26) issue.

The issues with Boinc erroring instantly when crunching s@h units only now exists in the Ubuntu repo package. So I've been trying to "ruffle the feathers" of a package maintainer over at launchpad to figure out why their package is broke when the upstream one works... (even their packaged 7.0.26 was broken in the same fashion)

See here. Maybe someone has some information that could help them get their repository package right. (I'll bet it's the way they patch (break) it for Debian/Ubuntu)

Thanks for the input! And thanks for being involved with S@H!
____________-Dave#2

While seti still errors off immediately (still no usable Ubuntu 12.04
repo package of boinc for seti), Einstein cpu tasks seem to run fine,
at least so far (tried both today, only Einstein working).

And the boinc-mgr screen still is screwed up unless
you resize the window (there have been various gnome
updates so I thought that part might have been papered
over, but no).

Yea that boincmgr menu bug is annoying. I've been sick of it for awhile.

(I know I've said this many times now, and it's taken weeks longer that it's supposed to have, but)
12.04 will have a fixed repository package soon. It will either be a fixed 7.0.24, or a backported 7.0.27(current working package from ubuntu 12.10 precise)

It is in the works, we figured out the bug about a week and a half ago, it's just been the red tape with the ubuntu repository people, they are trying to be careful about what goes into the standard repository (better late than never)

If you see the other thread "Boinc quit working again with newest..." there is a ppa listed that currently has 7.0.28 (alpha or beta I'm not sure)