Message boards : Questions and problems : Boinc Reverted to 8.2.9
Message board moderation
| Author | Message |
|---|---|
DaveSend message Joined: 28 Jun 10 Posts: 3255
|
Today, after a reboot, none of the projects I had added were present when I opened up the manager. On checking Help>About, instead of the version number being 8.3.0 which I had compiled from the master, it was 8.2.9 going to the boinc-master folder in my home directory and running sudo make install put the version back but not the projects I had added. Not a major problem, It would be nice to understand what happened though. (I have not paid much attention when running sudo apt update and sudo apt upgrade and am guessing that 3.2.9 might have become the version packaged for my distribution now? |
Vitalii KoshuraSend message Joined: 29 Mar 17 Posts: 200
|
In reply to Dave's message of 6 Apr 2026: Today, after a reboot, none of the projects I had added were present when I opened up the manager. On checking Help>About, instead of the version number being 8.3.0 which I had compiled from the master, it was 8.2.9 going to the boinc-master folder in my home directory and running sudo make install put the version back but not the projects I had added. Yes, it looks like your package manager updated your installation to 8.2.9 (laest stable release) since it's unaware about any installations outside of it. BOINC maintainer. For any insight, check my BOINC Development Blog. |
DaveSend message Joined: 28 Jun 10 Posts: 3255
|
Yes, it looks like your package manager updated your installation to 8.2.9 (laest stable release) since it's unaware about any installations outside of it.I wonder if there is a way to tell the package manager not to do that so it sticks. Manually excluding it when I do an update each time seems like a lot of bother. |
Vitalii KoshuraSend message Joined: 29 Mar 17 Posts: 200
|
In reply to Dave's message of 6 Apr 2026: Yes, it looks like your package manager updated your installation to 8.2.9 (laest stable release) since it's unaware about any installations outside of it.I wonder if there is a way to tell the package manager not to do that so it sticks. Manually excluding it when I do an update each time seems like a lot of bother. It looks like you have it installed once using the package manager. So the obvious solution is to remove ti using the package manager and then install in your preferred way. Then for the package manager this package will look like not installed, so it will never try to install it again unless you tell it to do that. BOINC maintainer. For any insight, check my BOINC Development Blog. |
DaveSend message Joined: 28 Jun 10 Posts: 3255
|
Thank you. I should have thought of that. |
Copyright © 2026 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.