Haiku Software Update Failed with no errors.
Also pckman full-sync fails with no errors.
Perhaps is not correct to assume that Software Update Failed because i did not received any errors. I have waited a few days reboot and started again. The last successful update was on: Feb 25, 2025
(upload://h66L7vypse3fNp5Wk2vGmvPaNaR.jpeg)
I’m pretty sure both SoftwareUpdater and pkgman show an error,at least for me they do.
Unfortunately it happens from time to time that broken packages end up in the CDN cache,leading to checksum errors for anyone who tried to install updates until it’s fixed.
I also experienced that today when trying to update to hrev58816.
That is a server-side issue and there’s nothing you can do about it.
Please wait for our admins to clean the CDN cache,then you can try again.
I see, I actually started the update a few weeks ago and today I just tried to check if it works. Even pkgman refresh freeze at Validating checksum for HaikuPorts …
Thanks a lot for confirming that!
mine is hrev58682
I disabled HaikuPorts and software refresh/update completed. Will for admins to clean the CDN cache, thanks again
This is likely spot on.
Essentially, we moved to an alternative s3 object storage host which we needed to front-end with a caching CDN to make cost effective. I quickly learned the CDN didn’t detect updated files and continued to serve old repo definition files with updated hpkg files.
This shouldn’t happen theoretically. I worked around it by having our build systems clear the CDN cache of the individual files every update. This also didn’t solve it. Turns out our CDN cache has a major bug in their API (confirmed by their support team… waiting 6 months now for their “engineering team” to respond).
I worked around the above “harder” by clearing the whole CDN cache (not individual files). This seemed to solve it, but now literally defeats the purpose of a CDN 
Anyway. I’m in negotiations with Haiku, Inc. to do some changes here. We’re going to get a “big dumb” server with lots of storage to act as our central package / repo storage, and rely more on mirrors moving forward. This gives us the best of all worlds (production infrastructure not tightly coupled directly to big complex storage arrays, while giving us “big cheap” storage at scale via dedicated servers)
Cost should be pretty like-for-like
9 Likes