Any Boot ISO missing from nightly download links

[hey68you]

Hi,

Where can I download a nightly image?

as of April 27, 2021: missing links for Any Boot ISO at ​https://download.haiku-os.org/nightly-images/x86_64/

Same for 32bit

Thanks in advance hey68you@…

[modeenf]

You get this error.

<Error>
<Code>TemporarilyUnavailable</Code>
<Message>The bucket haiku-nightly is temporarily unavailable: egress</Message>
<RequestId>F92DB527B8803108</RequestId>
<HostId>625Br9r89I6l7BeGW2gvZbfiY+B3xT+V0/RIPml2WUwpHqK+P35a3AQNAhm1FSTDAnNjCRt5wd0a</HostId>
</Error>

[mutterhunt]

I'm the classical "me too"! Plz. make them visible again; it's nothing to feel ashamed of, really!

[mutterhunt]

ahhh.... know what! I think this should leed to people making their own "nighly-build". doing so on a FreeBSD-machine at the moment. It's 4pm here so I think the "nightly" will become a "morningly" built if everything works, if not, I have something for the mailing list!

greetz, lizbeth

[korli]

the links are working for me (both archs).

[mutterhunt]

juist! (right on nederlands!) they are working again! so what to do with the configuring I started 3 hours ago? let's finish them and see what comes out, the anyboot-versions can be used if it doesn't get the jam-target or on compile failures - I think the .init-scripts have been updated, as I got the /gcc/isl buildtool withouth any mistakes (prob. with compiling for arm).

How about a Haiku OS mobile system? Use the pin64-tablet or phone and compile it for them? can this be a future project???

thx a lot for the repair!

lizbeth

[hey68you]

Working for me now too. This ticket can be closed

[pulkomandy]

It seems downloads are back.

[kallisti5]

Here's a rundown of what happened:

In 2018 when we decided to use wasabi.com for hosting our artifacts, they had a policy of unlimited egress traffic. As of April 26th, they walked back that commitment and shut down egress traffic on our buckets for using too much bandwidth. We store around 1TiB of data, and have 3TiB of monthly outbound traffic.

Wasabi tech support has temporarily removed the egress block, but I feel like we're going to run into it again.

Here is some scope information:

• Haiku master/r1beta1/r1beta2 repos
  • Where: Wasabi s3
  • What: Haiku's core update repositories
  • Signed: Yes. minisig on repo file
• Haiku nightly images
  • Where: Wasabi s3
  • What: Haiku's nightly builds
  • Signed: Yes. minisig on artifacts
• Haikuports repo - Our own server
  • Where: Digital Ocean block volume
  • What: Haikuports repos
  • Signed: No
• Haiku releases - Wasabi s3 (US), our own server (EU), generous mirrors
  • Where: Wasabi S3, Digital Ocean block volume, rsync Mirrors
  • What: Haiku releases (r1beta2, etc)
  • Signed: Yes

Anything on "Wasabi S3" was impacted, including the financial tracker on haiku-inc.org.

We really can't depend on external rsync mirrors until every repository is signed *AND* haikuporter gets some signature checking ability.

I've been panic mirroring our Haiku repos from Wasabi onto IPFS as a temporary measure incase they pull down access again. (IPFS has deduplication, easy mirroring, *AND* transparent signature checking. You can access the US gateway here: ​https://us.hpkg.haiku-os.org (and notes on how to use it here: ​https://us.hpkg.haiku-os.org/readme.html)

"haikuports" is empty there since my only focus at the moment is stuff on Wasabi.

So.. this issue isn't solved yet, but we're working on backup options incase this stuff goes down again.