Thank you Nathan, the first issue is fixed now using cdn for os and apps delivery while signatures are delivered still from central download server, this seems the recommended way by the ASF? :-)
https://github.com/apache/nuttx-website/pull/191 We need to fix archive releases downloads (BSD code before ASF). Can we put these releases on the archive download server at ASF? Or we need to use external site / our www server? Thanks :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On Mon, Oct 5, 2026, 00:21 Nathan Hartman <[email protected]> wrote: > ASF uses a Content Distribution Network (CDN). This may be an artifact > of the way the CDN works. A few years ago, the CDN replaced the ASF's > older system of mirrors worldwide that used to be operated by > volunteers. When the changeover was done, they made it backwards > compatible to avoid breaking project websites. > > On Sun, Oct 4, 2026 at 11:41 AM Tomek CEDRO <[email protected]> wrote: > > > > https://github.com/apache/nuttx-website/issues/189 > > > > While testing NuttX 13.1.0 release notes I noticed two issues on our > > website https://nuttx.apache.org/download/ > > > > 1. Current release artifacts url is outdated and leads to redirect. > > This seems simple issue of updating url base for downloads. Someone > > noticed that issue 2 weeks ago and tried to fix but either fix did not > > work or broke the downloads. > > > > 2. Historical releases url is invalid as bitbucket repo is gone. We > > need to consider where we want to put historical release artifacts on > > a website or github/apache/nuttx releases? I have all historical > > packages backup just in case :-) > > > > Thanks :-) > > Tomek > > > > -- > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >
