Coming from dev Roadmap on Haiku, I have a question on which path does Nightly builds follow ?? Beta/R5 is close but maybe it follows another upstream.
The beta 5 has been branched out from nightlies last week. However, all bugfixes will be merged in the two branches during that period, and with most people working on bugfixes, there won’t be much new features in nightlies for a few days.
So, they should be more or less identical for the moment. When the beta is released, the nightliest will start getting the next run of features, while the beta branch will only get well-tested bugfixes.
3 Likes
I’m getting errors when trying to upgrade from hrev57924. SoftwareUpdater even crashes.
pkgman says HaikuPorts repo cannot be found.
In the end, I could update all packages but Haiku itself, where a conflict with SSH was reported.
I’ll attach all relevant info below:
(cannot attach non images, how to?)
Tried to switch to the beta5 repo but that doesn’t seem to be available just yet, or not in EU:
~> pkgman add https://eu.hpkg.haiku-os.org/haiku/r1beta5/$(getarch)/current
Fetching repository info from https://eu.hpkg.haiku-os.org/haiku/r1beta5/x86_64/current …
Activating repository config from https://eu.hpkg.haiku-os.org/haiku/r1beta5/x86_64/current …
*** failed! : Bad data
SoftwareUpdater crash report:
Debug information for team /boot/system/apps/SoftwareUpdater (1687):
CPU(s): 8x Intel 11th Gen Core™ i7-1165G7
Memory: 31,85 GiB total, 1,11 GiB used
Haiku revision: hrev57924 Aug 7 2024 06:02:10 (x86_64)
Active Threads:
thread 1687: SoftwareUpdater (main)
thread 1692: w>SoftwareUpdater
thread 1710: team 1687 debug task
thread 1690: WorkingLooper
state: Exception (Segment violation)
Frame IP Function Name
-----------------------------------------------
0x7f168e97a0f0 0x8c57929848 /boot/system/lib/libbe.so + 0x335848
Unable to retrieve disassembly for IP 0x8c57929848: address does not point to a function.
Frame memory:
[0x7f168e97a0a8] ..=.......}..... 0c a8 3d fd bf 01 00 00 00 b1 7d fb 84 11 00 00
[0x7f168e97a0b8] ................ 00 00 00 00 00 00 00 00 18 a2 97 8e 16 7f 00 00
[0x7f168e97a0c8] G........}..... 20 47 f1 f7 84 11 00 00 00 b1 7d fb 84 11 00 00
[0x7f168e97a0d8] ................ 00 00 00 00 00 00 00 00 18 a2 97 8e 16 7f 00 00
[0x7f168e97a0e8] ........ 14 a2 97 8e 16 7f 00 00
0x7f168e97a180 0x1bffd3d6410 UpdateManager::HandleProblems() + 0x70
0x7f168e97a1a0 0xf0aafa478a BPackageKit::BManager::BPrivate::BPackageManager::_HandleProblems() + 0x1a
0x7f168e97a1c0 0xf0aafa7109 BPackageKit::BManager::BPrivate::BPackageManager::FullSync() + 0x29
0x7f168e97a210 0x1bffd3d5da0 UpdateAction::Perform(update_type) + 0x60
0x7f168e97a260 0x8c5774dfce BLooper::task_looper() + 0x28e
0x7f168e97a280 0x8c5774d55b BLooper::_task0_(void*) + 0x1b
0x7f168e97a2a0 0xa4660d8de7 thread_entry + 0x17
00000000 0x7f7ee5487258 commpage_thread_exit + 0
the beta4 repo is set to 404 deliberately currently.
2 Likes
You have to wait until beta 5 is released and don’t do any updates/installs until then, or switch to nightlies (which have a few broken things currently).
3 Likes
would be great to switch to a specific Haiku nightly revision… just want to get rid of the 20+s lockups:( (see Haiku nightly lags considerably since 19/07/2024 - #13 by zantak)
I and likely many others would appreciate it that if the next time something like this happens; That there is a pinned warning in the forum or a blogpost made. Ofcourse these changes come with complications and there is no direct link between all Haiku users and developer, comparable to that on Windows or other big operating systems. Mentioning it, the lack of a constant link is probably a good thing. That, however, doesn’t exempt the fact that a form of warning is far better then none. It may has been done and I simply had missed it or it simply wasn’t practical to warn the users. No developer on free software has any obligation to the users of said software. Nonetheless it’s an great inconvience and a time waster for those unaware of the migration.
2 Likes
You can switch to the beta5 HaikuPorts repository in conjunction with the master Haiku repository and update that way. I reverted the one change that was probably causing the lockups, BTW.
1 Like
Yes, we probably should have made an announcement, but as usual we are under-staffed. 
I will certainly mention it in the July activity report, which hopefully will be posted today.
5 Likes
We should probably add a pinned topic to the forum for now. : )
4 Likes