I’m planning on switching us over to our new package repositories this evening. (and, we’re switching over to the new S3-based haikuporter buildmaster)
This should resolve the checksum errors folks have been seeing from our repositories. The switchover of haikuports and haiku repositories should be seamless and fairly quick.
Getting everything (concourse, buildmaster) delivering artifacts will likely be broken for a few hours.
Plan:
Disable concourse pipelines
Halt haikuports builds
eu.hpkg.haiku-os.org outage beginsSwitch us over to new package repositories via hpkgbouncer changes
eu.hpkg.haiku-os.org outage endsSwitch concourse over to new s3 system
Switch haikuports buildmaster over to new s3 system
Switch over nightly download pages, etc.
Live status information can be found here: https://status.haiku-os.org
8 Likes
The critical updates were successful:
eu.hpkg.haiku-os.org has been pointed over to the new server.
Haiku, Haikuports repositories are working as expected from the new location.
build-packages have been fixed to keep builds going.
haiku builds via concourse is working
nightly images (isos, etc) aren’t showing up on download.haiku-os.org (yet)
haiku repositories are being updated nightly as expected though
haikuports buildmaster is “ready”, but force stopped. I’m going to wait until the morning to flip it on… if something bad happens I don’t want to be panic fixing it at 1am US time
There are a bunch of little things to move, but overall the operation was successful.
12 Likes
michel
June 29, 2025, 10:31am
4
I hate to be that guy, but
~/Desktop> pkgman full
100% repochecksum-1 [65 bytes]
Validating checksum for BeSly Software Solutions...done.
100% repochecksum-1 [65 bytes]
Validating checksum for FatElk_64...done.
100% repochecksum-1 [65 bytes]
Validating checksum for Haiku...done.
100% repochecksum-1 [2 bytes]
Refreshing repository "HaikuPorts" failedValidating checksum for HaikuPorts...: I/O error
Nothing to do.
1 Like
apl
June 29, 2025, 11:36am
6
Hi Alex; would you be able to check the HDS logs to make sure it is pulling the HPKR and HPKG files the next time it imports a new package.
could you show the output of pkgman list-repo ?
See Making sure you're not a bot! for potential a solution to that one.
Prior to this change, we were running on a CDN which cached the repo file causing these checksum mismatches.
1 Like
will do. Buildmaster has been stopped overnight
2 Likes
kallisti5:
pkgman list-repo
From Hungary/Europe
~> pkgman list-repo
BeSly Software Solutions
base-url: https://software.besly.de/repo64
identifier: tag:besly.de,2020:hap
priority: 2
FatElk_64
base-url: http://fatelk.com/repo_64
identifier: http://fatelk.com/repo_64
priority: 1
Haiku
base-url: https://eu.hpkg.haiku-os.org/haiku/r1beta5/x86_64/current
identifier: tag:haiku-os.org,2001:repositories/haiku/r1beta5/x86_64
priority: 1
HaikuPorts
base-url: https://eu.hpkg.haiku-os.org/haikuports/r1beta5/x86_64/current
identifier: tag:haikuports.org,2013:repositories/haikuports/master/x86_64
priority: 1
KapiX's Depot
base-url: http://haiku.kacperkasper.pl/repo/x86_64
identifier: <http://haiku.kacperkasper.pl/repo/x86_64>
priority: 2
LOTE
base-url: https://www.haikuware.ru/repo/lote
identifier: http://haikuware.ru/repo/lote
priority: 1
~>
This is output of pkgman refresh
~> chk_pkgs.sh
Tároló ellenőrzőkódjának letöltése (https://software.besly.de/repo64) ...
Ellenőrzőkód érvényesítése a tárolóhoz (BeSly Software Solutions) ...
Tároló ellenőrzőkódjának letöltése (http://fatelk.com/repo_64) ...
Ellenőrzőkód érvényesítése a tárolóhoz (FatElk_64) ...
Tároló ellenőrzőkódjának letöltése (https://eu.hpkg.haiku-os.org/haiku/r1beta5/x86_64/current) ...
Ellenőrzőkód érvényesítése a tárolóhoz (Haiku) ...
Tároló ellenőrzőkódjának letöltése (https://eu.hpkg.haiku-os.org/haikuports/r1beta5/x86_64/current) ...
Ellenőrzőkód érvényesítése a tárolóhoz (HaikuPorts) ...
*** failed! : I/O error
~>
Seems Haikuports needs some touches … or we , end users, should wait …
michel
June 29, 2025, 1:19pm
10
Sure
~> pkgman list-repo
BeSly Software Solutions
base-url: https://software.besly.de/repo64
identifier: tag:besly.de,2020:hap
priority: 2
FatElk_64
base-url: http://fatelk.com/repo_64
identifier: http://fatelk.com/repo_64
priority: 1
Haiku
base-url: https://eu.hpkg.haiku-os.org/haiku/r1beta5/x86_64/current
identifier: tag:haiku-os.org,2001:repositories/haiku/r1beta5/x86_64
priority: 1
HaikuPorts
base-url: https://eu.hpkg.haiku-os.org/haikuports/r1beta5/x86_64/current
identifier: tag:haikuports.org,2013:repositories/haikuports/master/x86_64
priority: 1
I just updated few minutes ago, no problem with Haikuports repo.
1 Like
Doesn’t work on my machine either, nor on a clean install (beta5, both 32 and 64 bit)
An update - I also include time/Haiku version info …
~> pkgman refresh
Tároló ellenőrzőkódjának letöltése (https://software.besly.de/repo64) ...
Ellenőrzőkód érvényesítése a tárolóhoz (BeSly Software Solutions) ...
Tároló ellenőrzőkódjának letöltése (http://fatelk.com/repo_64) ...
Ellenőrzőkód érvényesítése a tárolóhoz (FatElk_64) ...
Tároló ellenőrzőkódjának letöltése (https://eu.hpkg.haiku-os.org/haiku/r1beta5/x86_64/current) ...
Ellenőrzőkód érvényesítése a tárolóhoz (Haiku) ...
Tároló ellenőrzőkódjának letöltése (https://eu.hpkg.haiku-os.org/haikuports/r1beta5/x86_64/current) ...
Ellenőrzőkód érvényesítése a tárolóhoz (HaikuPorts) ...
*** failed! : I/O error
~> pkgman update
100% repochecksum-1 [65 bájt]
Ellenőrzőkód érvényesítése a tárolóhoz (BeSly Software Solutions)...done.
100% repochecksum-1 [65 bájt]
Ellenőrzőkód érvényesítése a tárolóhoz (FatElk_64)...done.
100% repochecksum-1 [65 bájt]
Ellenőrzőkód érvényesítése a tárolóhoz (Haiku)...done.
100% repochecksum-1 [2 bájt]
Sikertelen a tároló "HaikuPorts" frissítéseEllenőrzőkód érvényesítése a tárolóhoz (HaikuPorts)...: I/O error
100% repochecksum-1 [65 bájt]
Ellenőrzőkód érvényesítése a tárolóhoz (KapiX's Depot)...done.
100% repochecksum-1 [71 bájt]
Ellenőrzőkód érvényesítése a tárolóhoz (LOTE)...done.
Nothing to do.
~> date; uname -a
V jún. 29 15:57:59 CEST 2025
Haiku HiQ_R1B5_256GO.szabadpart.net 1 hrev57937+129 Dec 10 2024 21:49 x86_64 x86_64 Haiku
~>
ok, I found a critical thing I missed this morning. Stable versions of Haiku reference “r1beta5” in their haikuports repository configuration instead of “current” (which is what the nightlies do)
I’ve put fixes in place to address this. Let me know if the situation is resolved for stable versions
Sorry for missing this one. We have a lot of stuff
1 Like
Not yet.
~/Desktop> pkgman refreshhttps://eu.hpkg.haiku-os.org/haiku/r1beta5/x86_64/current …https://eu.hpkg.haiku-os.org/haikuports/r1beta5/x86_64/current …
For now* changing haikuports repository to master should work on R1B5, on nightly it’s not an issue here.
I can confirm that switching haikuports repository to master does resolve the issue.
1 Like
I missed the mark lol. NOW it should be working. I added the aliases in the wrong part of the path
The issue with the Checksum Error has been addressed as well. Our package kit does a http HEAD on the repo file and checks the date… when we accidentally serve an incorrect file, I have to make sure I touch the repo file on our end to force an update.
2 Likes
Confirmed working again, using r1beta5 in the repository works again, big thumbs up @kallisti5 !!
2 Likes
Confirmed working here too. Thanks!
2 Likes
