| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Out-of-Date BOINC Repositories Debian (Ubuntu) |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 8
|
|
| Author |
|
|
Mgruben
Advanced Cruncher Joined: May 26, 2013 Post Count: 94 Status: Offline Project Badges: 
|
Just curious, and I'm hoping I can ask this here rather than making a forum account on the more general BOINC site, but why does apt-get in Ubuntu report that the latest version of boinc-client and boinc-manager are 7.0.27? And can I trick apt-get or synaptic into downloading and installing as a package the actual most recent version, 7.0.65?
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Can't you get them all from here ?
|
||
|
|
sgoll
Advanced Cruncher Joined: Oct 24, 2006 Post Count: 87 Status: Offline Project Badges: 
|
Just curious, and I'm hoping I can ask this here rather than making a forum account on the more general BOINC site, but why does apt-get in Ubuntu report that the latest version of boinc-client and boinc-manager are 7.0.27? And can I trick apt-get or synaptic into downloading and installing as a package the actual most recent version, 7.0.65? In Debian Wheezy you are doomed to use 7.0.27 because newer versions of the boinc software requires a newer version of the glibc. No chance ... except you are moving to testing, unstable or experimental. In ubuntu you can use newer boinc clients because ubuntu is mainly a mix of Debian experimental and some other pakets. I think the boinc devs are using ubuntu as reference system when developing their software so I think you can use the newest boinc version from http://boinc.berkeley.edu/download_all.php. Please have in mind that I may be wrong. Stephan  |
||
|
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges: 
|
You can get the latest version of BOINC (usually still in testing, so not guaranteed to work properly) by adding the following repository to your Ubuntu system's Software Sources:
----------------------------------------https://launchpad.net/~costamagnagianfranco/+archive/boinc There are directions at that link for how to do this. Once you have added the repository, every time a new version of BOINC is placed there, your Update Manager will include BOINC in the list of packages that it proposes that you update. It is wise to stop BOINC before doing the update, although I have on occasion forgotten to do this and have not lost WUs. The same person maintains the repository at the link below for BOINC and other software for Ubuntu. Its most recent BOINC version is 7.0.27, so at this moment it's not ahead of the regular Ubuntu repository. https://launchpad.net/~costamagnagianfranco/+archive/locutusofborg-ppa (edited to add second repository link)  [Edit 1 times, last edit by kateiacy at Aug 20, 2013 4:14:38 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
7.0.27 And 7.2.7 are close enough to miss a digit, but I see 7.2.7 listed, which I've been running for almost as long as Gianfranco ported this one ;>)
(The first link actually shows there's 7.2.10 build for testing) |
||
|
|
Mgruben
Advanced Cruncher Joined: May 26, 2013 Post Count: 94 Status: Offline Project Badges:
|
This is all great information; my main reason for preferring a package installation is for the feature of apt-get update and apt-get upgrade without having to install newer versions myself, though admittedly this is more born of an aversion to messing with the installation since I'm not terribly familiar with how installs on Debian go.
----------------------------------------For instance, for a while I had installed both the packages and the Berkeley installer on the machine at the same time, and needless to say that led to some confusion on my part as to which was running and which could be accessed through which means. Currently I am using the Berkeley installer (.sh) .65 version, though whenever a newer version comes out I won't know how to upgrade; I assume it would be placing the newer .sh in the directory from which I unpacked the previous .sh and unpacking it through the terminal? Or would this cause funky overwrites and lose projects / slots? |
||
|
|
captainjack
Advanced Cruncher Joined: Apr 14, 2008 Post Count: 144 Status: Offline Project Badges: 
|
Mgruben,
I have had reasonable success at doing minor upgrades using the Berkeley installer. For example moving from 7.0.27 to 7.0.65 keeps the same settings and sometimes it even keeps the same tasks. However, from time to time during a major upgrade the BOINC developers change the BOINC table structures so an upgrade can cause some confusion. For example moving from a 6.10.x release to any 7.x.x release. To use your words, it would "cause funky overwrites and lose projects / slots" / tasks. So when I am in the mood to be cautious, I set the project(s) to no new tasks, let them all finish, then do the upgrade. Your assumption on doing the upgrade is correct. You just move the version you want to install into the same folder where you previously installed, then run the Berkeley installer through the terminal. Best of luck, CaptainJack |
||
|
|
Mgruben
Advanced Cruncher Joined: May 26, 2013 Post Count: 94 Status: Offline Project Badges:
|
CaptainJack,
----------------------------------------Thank you for your confirmation of my suspicions haha; I do lament somewhat that installing on Linux isn't as streamlined or idiot-proof as installing on a Windows platform, but it is entirely possible that I am merely espousing the viewpoint of the unwashed / unitiated masses, and it may well be that in time I will learn to stop worrying and love the penguin. |
||
|
|
|