Bug 166920 - sci-misc/boinc-5.8.11 update
|
Bug#:
166920
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: TEST-REQUEST
|
Assigned To: sci@gentoo.org
|
Reported By: william@heuts.net
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: sci-misc/boinc-5.8.11 update
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-02-14 22:53 0000
|
!!! One of the following masked packages is required to complete your request:
- sci-misc/boinc-5.5.6 (masked by: package.mask)
# Marcus D. Hanwell <cryos@gentoo.org> (03 Nov 2006)
# Masking beta versions of boinc - may not work with all projects.
since current stable release is 5.8.11 even this masked "beta" is well out of
date.
If there are outstanding issues with more recent boinc not working with major
projects (and I say if based on the mask, I am not saying it is still the case)
then it should probably require slotting.
It seems this package needs and update since it sources from the tar.bz2 on the
mirrors not the .sh that Berkley seem to distribute.
TIA.
Created an attachment (id=111333) [details]
diff to 5.5.6 ebuild
This patch makes boinc 5.8.11 compile and install correctly. It is based on the
boinc 5.5.6 ebuild, with updated dependencies, CFLAGS taken from the boinc
website, and removed sed statement which is no longer useful.
Since there is no tarball on the mirror, I created one on my computer for the
purpose of testing. It comes from cvs:
cvs -d :pserver:anonymous:@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout -r
boinc_core_release_5_8_11 boinc
*bump*
Latest stable version is 5.8.15.
Any word of the maintainer if this is going to be resolved or not in the near
future would be much appreciated.
I am very busy currently with work in real life, hence my latency replying to
bugs. If anyone else in the sci herd has the time to take a look at this I
would appreciate it. Otherwise I will get to it when I have the time.
This package is very time consuming to bump... I am hoping to improve that when
I get time but they currently do not offer source releases. Hopefully I will
have some spare time this weekend.
Although I'm eagerly awaiting the latest stable release in portage real-life
worries always have priority. No problems here if you take your time.
I'll jump in and take a look also...focus on your thesis cryos.
no, curl-7.16.0 is not required. Curl 7.15.5 is however. So you don't need the
masked version at least according to the configure file, just the ~arch one.
I'm testing the version currently with just fa@h. Who else is attached to this
and what have you tested with the new version?
The 5.8.15 ebuild removed all init.d scripts on ~amd64.
The new version is in the tree. Wait about 4+ hours from now to actually try
and emerge it though. As the distfile will not of hit the mirrors before then.
Please test it, with your project to make sure it works.
oh also note that 5.8.15 is masked still. You'll have to unmask it to test it.
I'd like to get it tested and make sure it works before we go about unmasking
it on the general population.
Works fine on amd64 and World Community Grid. Much appreciated, thanks.
works for amd64. -march=opteron
Does not work for me on AMD64 (AMD Athlon 64 Processor 3000+) with Seti@home
:-/ I get this error msg:
[SETI@home] Message from server: platform 'x86_64-pc-linux-gnu' not found
-march=k8
setiathome does not work on amd64 as they do not provide amd64 binaries. The
setiathome ebuild did attempt to build a binary from source but I have not been
able to get a recent binary to compile. This has always been an issue with
boinc - getting quality source that will build. They don't do source releases,
and the CVS checkouts don't have everything.
Recently I just have not had the time to invest in trying to get to the bottom
of this. The init script is basically broken as they have changed how you
attach to projects, although admittedly it never worked amazingly well as I
never got the time to stop boinc from deleting the binaries we had just built
for the project. It builds on my amd64 machine though which is a great start!
(In reply to comment #16)
> setiathome does not work on amd64 as they do not provide amd64 binaries. The
> setiathome ebuild did attempt to build a binary from source but I have not been
> able to get a recent binary to compile. This has always been an issue with
> boinc - getting quality source that will build. They don't do source releases,
> and the CVS checkouts don't have everything.
>
> Recently I just have not had the time to invest in trying to get to the bottom
> of this. The init script is basically broken as they have changed how you
> attach to projects, although admittedly it never worked amazingly well as I
> never got the time to stop boinc from deleting the binaries we had just built
> for the project. It builds on my amd64 machine though which is a great start!
>
Yea most projects DO NOT have 64bit binaries and you'll just have to wait until
they release them or someone provides them for you,.. SETI@HOME provides 64bit
binaries but you'll have to manually download them and put them inside the
projects folder under /var/lib/boinc yourself. I have a boinc-cvs ebuild which
works but i still need to add more ebuilds for projects like seti@home etc..
Works fine for me on x86 with einstein@home. Thanks a lot.
5.8.15 is working great on both my ~x86 boxes