Something is broken with the repo for nightlies, I cant “lock” (or “downgrade”) to a working hrev,
the official instructions on Updating and downgrading your system | Haiku Project
do not work to lock to hrev56575 which is working fine.
I get the option to basically remove 40-50 (critical) programs, or keep the hrev that doesnt work with said programs.
Getting lots of “missing symbol” errors, in bepdf and webpositive
Is there any way to revert “forcefully”/manually to a previous hrev?
Or at least preselect the boot menu option to said hrev instead of latest installed one?
A full build from scratch takes 2 hours on my machine. I have to do this from inside Haiku. I am not interested in doing this on a Haiku system running in a virtual machine on a server in the other side of the world. Also I don’t do full builds all the time, so when I’m testing simple changes it takes maybe 30 seconds to 1 minute.
And it still wouldn’t solve the main problem: I don’t have a lot of time to work on this, maybe a few hours every weekend.
Other people have slower/older machines than mine, but if you want to help them, I think it would be more interesting to send them a new computer than to give them access to a server.
Thats why I suggested to inform the user what awaits them in my thread about “libshared explained”…
If user knows what awaits them, they will be careful and understand what to do. Update or not!?
Communication with the user or give Information about what is going on and what might happen keeps the user calm.
Also if you had informed user or the Press or Reporter beforhand, they would consider doing a review or an update, later, after Beta 4…
Hello. Yes, there is a way: during the boot process, if you press the space bar, or hold the Shift key, a boot menu will appear. On this menu, you can choose a previous state. You can get more information on this link:
Under Select boot volume you can specify what former “version” of Haiku to boot. Every time you un/install a package, the old state is saved and you can boot into it by choosing it from the list presented in the boot loader options.
So, if you encounter boot problems after installing some package, boot a Haiku state from before that time and uninstall the offending package. You can permanently revert to a specific Haiku revision as described in the topic SoftwareUpdater.
To be fair, we’re trying to fix this. It’s why we have been striving to getting on a yearly beta release cycle.
R1/beta4 is just around the corner. I feel like the absolute bare minimum for R1 is improving the stability of WebPositive. Our browser needs to be world class at minimum before finalizing R1.
