website: re-generate commons

Author: ilg-ul

website/blog/2025-02-13-xbb.mdx

@@ -0,0 +1,59 @@
+---
+
+# DO NOT EDIT!
+# Automatically generated from docusaurus-template-liquid/templates/docusaurus.
+
+title: The project was upgraded to use XBB v6.0.0
+seo_title: Upgrade to XBB v6.0.0
+description: The project was upgraded to use XBB v6.0.0 based on Debian 10 and macOS 11.0.
+keywords:
+  - xpack
+  - qemu-riscv
+  - website
+
+date:  2025-02-13 13:21:00 +0300
+
+authors: ilg-ul
+
+tags:
+  - xbb
+
+---
+
+import {PageMetadata} from '@docusaurus/theme-common';
+
+The project configuration was upgraded to use **XBB v6.0.0** based
+on **Debian 10** and **macOS 11**
+and **support for Arm 32-bit was discontinued**.
+
+Therefore, all future builds will use XBB v6.0.0 or later.
+
+<!--truncate-->
+
+<PageMetadata title={frontMatter.seo_title} />
+
+## GLIBC 2.28
+
+The GNU/Linux base was raised to GLIBC 2.28, with builds performed on **Debian 10**.
+The resulting binaries should run on Ubuntu 20 or later, RedHat 8 or later,
+Fedora 29 or later, etc.
+
+## MacOS 11.0
+
+The macOS base was raised to 11.0, with builds performed on** macOS 11.7** with
+`MACOSX_DEPLOYMENT_TARGET="11.0"`. The resulting binaries, both x64 and arm64,
+should run on any macOS 11 or later.
+
+## Support for Arm 32-bit discontinued
+
+With regret for the inconvenience caused to some Raspberry Pi users,
+due to the extremely high burdon on maintenance (toolchain builds took
+more than half a day), support for Arm 32-bit GNU/Linux had to be discontinued.
+
+This allowed all arm64 GNU/Linux builds to be performed on the Oracle Ampere
+machine, which is many times faster than the Raspberry Pi 4 machines.
+
+## Website updates
+
+The website was also updated to reflect the new changes, and references to
+**arm GNU/Linux**, **linux-arm** and **xbbla32**  were removed.

website/blog/_common/_deprecation-notices-glib-2.28.mdx

@@ -0,0 +1,19 @@
+
+{/* DO NOT EDIT! */}
+{/* Automatically generated from docusaurus-template-liquid/templates/docusaurus. */}
+
+{/* ------------------------------------------------------------------------ */}
+
+## Deprecation notices
+
+### GNU/Linux minimum requirements
+
+The minimum requirement is **GLIBC 2.28**, available starting
+with Ubuntu 20, Debian 10 and RedHat 8.
+Support for RedHat 7 was dropped in 2022.
+Support for Ubuntu 18 was dropped in 2025.
+
+### 32-bit support
+
+Support for 32-bit x86 GNU/Linux and x86 Windows was
+dropped in 2022 and for 32-bit Arm GNU/Linux in 2025.

website/blog/_common/_prerequisites-glib-2.28.mdx

@@ -0,0 +1,18 @@
+{/* DO NOT EDIT! */}
+{/* Automatically generated from docusaurus-template-liquid/templates/docusaurus. */}
+
+{/* ------------------------------------------------------------------------ */}
+
+## Prerequisites
+
+- x64 Windows: Windows 7 with the Universal C Runtime
+  ([UCRT](https://support.microsoft.com/en-us/topic/update-for-universal-c-runtime-in-windows-c0514201-7fe6-95a3-b0a5-287930f3560c)),
+  Windows 8, Windows 10, Windows 11
+- x64 macOS: 11.0 or later
+- arm64 macOS: 11.0 or later
+- x64 GNU/Linux: any system with **GLIBC 2.28** or higher
+  (like Ubuntu 20 or later, Debian 10 or later, RedHat 8 or later,
+  Fedora 29 or later, etc)
+- arm64 GNU/Linux: any system with **GLIBC 2.28** or higher
+  (like Raspberry Pi OS, Ubuntu 20 or later, Debian 10 or later,
+  RedHat 8 or later, Fedora 29 or later, etc)

website/blog/tags.yml

@@ -4,3 +4,5 @@
 releases:
 
 web:
+
+xbb:

website/docs/developer/_common/_content.mdx

@@ -62,7 +62,6 @@ for each platform:
 - `darwin-arm64`
 - `linux-x64`
 - `linux-arm64`
-- `linux-arm`
 
 :::note
 
@@ -305,10 +304,6 @@ git -C ~/Work/xpack-dev-tools/xbb-helper-xpack.git pull
 <PlatformDockerSection platform="linux-arm64"/>
 </TabItem>
 
-<TabItem value="linux-arm" label="GNU/Linux arm" default>
-<PlatformDockerSection platform="linux-arm"/>
-</TabItem>
-
 </Tabs>
 
 ### Compile with debug info

website/docs/getting-started/_common/_benefits.mdx

@@ -9,7 +9,7 @@ The main advantages of using the **xPack QEMU RISC-V** are:
 
 - A convenient, uniform and portable install/uninstall/upgrade
   procedure; the same procedure is used for all major
-  platforms (**x64 Windows**, **x64 macOS**, **arm64 macOS**, **x64 GNU/Linux**, **arm64 GNU/Linux**, **arm GNU/Linux**).
+  platforms (**x64 Windows**, **x64 macOS**, **arm64 macOS**, **x64 GNU/Linux**, **arm64 GNU/Linux**).
 - Multiple versions of the same package can be installed at the same time on
   the same system.
 - No need to worry about dependent libraries, they are all included.

website/docs/install/_common/_content.mdx

@@ -596,7 +596,6 @@ Download the latest version named like:
 <ul>
 <li><code>xpack-qemu-riscv-8.2.6-1-linux-x64.tar.gz</code></li>
 <li><code>xpack-qemu-riscv-8.2.6-1-linux-arm64.tar.gz</code></li>
-<li><code>xpack-qemu-riscv-8.2.6-1-linux-arm.tar.gz</code></li>
 </ul>
 
 :::note

website/docs/maintainer/_common/_content.mdx

@@ -179,7 +179,7 @@ or run the following in a terminal:
 ```
 
 Navigate to the **Maintainer Info** page,
-the **[Update the version specific code](http://localhost:3000/openocd-xpack/docs/maintainer/#update-the-version-specific-code)** section.
+the **[Update the version specific code](http://localhost:3000/qemu-riscv-xpack/docs/maintainer/#update-the-version-specific-code)** section.
 
 <UpdateVersionSpecific/>
 
@@ -238,7 +238,7 @@ will build again the previous release!
 
 ## Run the development builds
 
-The builds currently run on 5 dedicated machines (x64 GNU/Linux, x64 macOS, arm64 macOS, arm64 GNU/Linux, arm GNU/Linux).
+The builds currently run on 4 dedicated machines (x64 GNU/Linux, x64 macOS, arm64 macOS, arm64 GNU/Linux).
 
 Before the real build, run test/development builds on all platforms.
 
@@ -273,7 +273,7 @@ commits are pushed to GitHub.
 
 :::caution
 
-This is particularly crucial for extensive projects; otherwise,
+This is particularly crucial for large projects; otherwise,
 the build may proceed with the previous version.
 
 :::
@@ -359,26 +359,15 @@ caffeinate ssh xbbli
 
 ### Build the arm64 GNU/Linux binaries
 
-Run the docker build on the production machine (`xbbla`);
+Run the docker build on the production machine (`ampere`);
 start a VS Code remote session, or connect with a terminal:
 
 ```sh
-caffeinate ssh xbbla
+caffeinate ssh ampere
 ```
 
 <PlatformDockerBuild platform="linux-arm64"/>
 
-### Build the arm GNU/Linux (32-bit) binaries
-
-Run the docker build on the production machine (`xbbla32`);
-start a VS Code remote session, or connect with a terminal:
-
-```sh
-caffeinate ssh xbbla32
-```
-
-<PlatformDockerBuild platform="linux-arm"/>
-
 ### Update the durations of the development builds
 
 In `website/docs/_shared/_development-durations.mdx`, update
@@ -456,14 +445,13 @@ is available in the `xbb-helper` and
 requires `GITHUB_API_XPACK_DEV_TOOLS_RUNNERS_TOKEN` to be present.
 
 - on the development machine (`wksi`) open
-ssh sessions to the build machines (`xbbli`, `xbbmi`, `xbbma`, `xbbla`, `xbbla32`):
+ssh sessions to the build machines (`xbbli`, `xbbmi`, `xbbma`, `ampere`):
 
 ```sh
 caffeinate ssh xbbli
 caffeinate ssh xbbmi
 caffeinate ssh xbbma
-caffeinate ssh xbbla
-caffeinate ssh xbbla32
+caffeinate ssh ampere
 ```
 
 Create a `screen` session, to provide a persistent standard output for
@@ -475,7 +463,7 @@ screen -S ga
 
 To quit it, use `# Ctrl-a Ctrl-d`.
 
-For `xbbli` & `xbbla`, which have more memory, start two runners:
+For `xbbli` & `ampere`, which have more memory, start two runners:
 
 ```sh
 ~/actions-runners/xpack-dev-tools/1/run.sh &
@@ -486,7 +474,7 @@ For the macOS x64 runners, be sure the deployment target is defined:
 
 ```sh
 unset WORK_FOLDER_PATH
-export XBB_ENVIRONMENT_MACOSX_DEPLOYMENT_TARGET="10.13"
+export XBB_ENVIRONMENT_MACOSX_DEPLOYMENT_TARGET="11.0"
 ~/actions-runners/xpack-dev-tools/run.sh &
 ```
 
@@ -576,6 +564,13 @@ rm -rf ~/Work/xpack-dev-tools/*/build-assets/build
 
 - **push** the `xpack-development` branch to GitHub
 
+:::caution
+
+This is particularly crucial for large projects; otherwise,
+the build may proceed with the previous version.
+
+:::
+
 ### Check if the helper is pushed and published
 
 The helper `xpack` branch must be updated and the npm package published.
@@ -591,7 +586,6 @@ To trigger the GitHub Actions builds, use the xpm actions:
 - **trigger-workflow-build-linux-x64**
 - **trigger-workflow-build-win32-x64**
 - **trigger-workflow-build-linux-arm64**
-- **trigger-workflow-build-linux-arm**
 
 
 ```sh
@@ -600,7 +594,6 @@ xpm run trigger-workflow-build-darwin-arm64 -C ~/Work/xpack-dev-tools/qemu-riscv
 xpm run trigger-workflow-build-linux-x64 -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build-assets
 xpm run trigger-workflow-build-win32-x64 -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build-assets
 xpm run trigger-workflow-build-linux-arm64 -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build-assets
-xpm run trigger-workflow-build-linux-arm -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build-assets
 ```
 
 The scripts behind these actions require the `GITHUB_API_DISPATCH_TOKEN`
@@ -654,13 +647,6 @@ These actions use the `xpack-development` branch of this repo and the
 [pre-releases/test](https://github.com/xpack-dev-tools/pre-releases/releases/tag/test/)
 binaries.
 
-:::caution
-
-Some of the `docker-linux-arm` tests have an issue on Debian and the
-**Clean working area** step fails.
-
-:::
-
 The tests results are available from the
 [GitHub Actions](https://github.com/xpack-dev-tools/qemu-riscv-xpack/actions) page.
 
@@ -733,10 +719,6 @@ with all binaries attached.
 
 - edit the draft and be sure it is attached to the `xpack-development` branch (important!)
 - perform the final edits (maintenance vs. new release) and check if everything is fine
-- add entries in the **Bug fixes**; use the following syntax
-  ```
-  - [[#N](https://github.com/xpack-dev-tools/qemu-riscv-xpack/issues/N)]:
-  ```
 - **keep the pre-release button enabled**
 - do **not** enable Discussions yet
 - click the **Publish release** button
@@ -758,6 +740,10 @@ this will add a file in the `website/blog` folder:
   ```
 - edit the `description` property in the post front matter
 - select the correct summary (maintenance vs. new release)
+- add entries in the **Bug fixes**; use the following syntax
+  ```
+  - [[#N](https://github.com/xpack-dev-tools/qemu-riscv-xpack/issues/N)]:
+  ```
 - copy/paste the folders hierarchies from the install guide
 - **commit** with the message _**website: blog post release 8.2.6-1 published**_
 

website/docs/maintainer/_common/_platform-native-build.mdx

@@ -22,7 +22,8 @@ xpm run clear-all-projects-builds -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git
 To update the build scripts and build the development binaries:
 
 <CodeBlock language="sh"> {
-`rm -f ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build-assets/package-lock.json && \\
+`export XBB_ENVIRONMENT_MACOSX_DEPLOYMENT_TARGET='11.0' && \\
+rm -f ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build-assets/package-lock.json && \\
 git -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git pull && \\
 xpm run install -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build-assets && \\
 git -C ~/Work/xpack-dev-tools/xbb-helper-xpack.git pull && \\
@@ -44,7 +45,8 @@ the <code>build-assets/build/{props.platform}/deploy</code> folder:
 To update the build scripts and build the release binaries:
 
 <CodeBlock language="sh"> {
-`rm -f ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/package-lock.json && \\
+`export XBB_ENVIRONMENT_MACOSX_DEPLOYMENT_TARGET='11.0' && \\
+rm -f ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/package-lock.json && \\
 git -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git pull && \\
 xpm run install -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build-assets && \\
 \\