prepare v8.1.0-1

Author: ilg-ul

CHANGELOG.md

@@ -2,8 +2,28 @@
 
 Entries in this file are in reverse chronological order.
 
+## 2023-08-28
+
+* v8.1.0-1 prepared
+* 267dd60 READMEs update
+* 1d73428 package.json: rm xpack-dev-tools-build/*
+* 886242b package.json: bump deps
+
+## 2023-08-21
+
+* 1485a45 READMEs update
+* 4140333 package.json: bump deps
+
+## 2023-08-19
+
+* 20484ba READMEs update
+* 5be0d36 package.json: bump deps
+
 ## 2023-08-15
 
+* 32b0ba0 CHANGELOG.update
+* 088b615 dot.*ignore update
+* 46712d9 re-generate workflows
 * 8dd711a .vscode/settings.json ignoreWords
 * bc8bf52 re-generate workflows
 * 1aa7f46 README-MAINTAINER rename xbbla

README-MAINTAINER.md

@@ -124,15 +124,15 @@ update the dependencies in `package.json`.
 ### Check the latest upstream release
 
 Identify the latest stable [tag](https://gitlab.com/qemu-project/qemu/-/tags),
-like `v7.2.0`.
+like `v8.1.0`.
 
 Also check the very latest
 [VERSION](https://gitlab.com/qemu-project/qemu/-/blob/master/VERSION) file.
 
 ### Increase the version
 
-Determine the version (like `7.2.0`) and update the `scripts/VERSION`
-file; the format is `7.2.0-1`. The fourth number is the xPack release number
+Determine the version (like `8.1.0`) and update the `scripts/VERSION`
+file; the format is `8.1.0-1`. The fourth number is the xPack release number
 of this version. A fifth number will be added when publishing
 the package on the `npm` server.
 
@@ -143,7 +143,7 @@ Check GitHub issues and pull requests:
 - <https://github.com/xpack-dev-tools/qemu-riscv-xpack/issues/>
 - <https://github.com/xpack-dev-tools/qemu/issues/>
 
-and fix them; assign them to a milestone (like `7.2.0-1`).
+and fix them; assign them to a milestone (like `8.1.0-1`).
 
 ### Check `README.md`
 
@@ -164,20 +164,20 @@ Use a new version, suffixed by `.pre`.
 
 - open the `CHANGELOG.md` file
 - check if all previous fixed issues are in
-- add a new entry like _* v7.2.0-1 prepared_
-- commit with a message like _prepare v7.2.0-1_
+- add a new entry like _* v8.1.0-1 prepared_
+- commit with a message like _prepare v8.1.0-1_
 
 ### Update qemu.git for development builds
 
 - checkout the `master` branch
-- merge the upstream `v7.2.0` tag into current
+- merge the upstream `v8.1.0` tag into current
 - push `master`
 - checkout the `xpack-develop` branch
 - merge `master` into current
 - push `xpack-develop`
 - checkout the `xpack` branch
 - merge `xpack-develop` into current
-- add a `v7.2.0-xpack` tag
+- add a `v8.1.0-xpack` tag
 - push tag to `origin`
 
 ### Update the version specific code
@@ -207,48 +207,19 @@ triggered via the VS Code graphical interface, using the
 For Intel macOS, first run the build on the development machine
 (`wksi`, a recent macOS):
 
-Update the build scripts (or clone them at the first use):
-
 ```sh
+# Update the build scripts.
 git -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git pull
 
-xpm run deep-clean -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git
-```
-
-If the helper is also under development and needs changes,
-update it too:
-
-```sh
-git -C ~/Work/xpack-dev-tools/xbb-helper-xpack.git pull
-```
-
-Install project dependencies:
-
-```sh
 xpm run install -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git
-```
 
-If the writable helper is used,
-link it in the place of the read-only package:
-
-```sh
+git -C ~/Work/xpack-dev-tools/xbb-helper-xpack.git pull
 xpm link -C ~/Work/xpack-dev-tools/xbb-helper-xpack.git
 
 xpm run link-deps -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git
-```
-
-For repeated builds, clean the build folder and install de
-build configuration dependencies:
 
-```sh
 xpm run deep-clean --config darwin-x64  -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git
-
 xpm install --config darwin-x64 -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git
-```
-
-Run the native build:
-
-```sh
 xpm run build-develop --config darwin-x64 -C ~/Work/xpack-dev-tools/qemu-riscv-xpack.git
 ```
 
@@ -290,8 +261,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build/darwin-x64/deploy
 total 35008
--rw-r--r--  1 ilg  staff  17458565 Jan 31 10:56 xpack-qemu-riscv-7.2.0-1-darwin-x64.tar.gz
--rw-r--r--  1 ilg  staff       109 Jan 31 10:56 xpack-qemu-riscv-7.2.0-1-darwin-x64.tar.gz.sha
+-rw-r--r--  1 ilg  staff  17458565 Jan 31 10:56 xpack-qemu-riscv-8.1.0-1-darwin-x64.tar.gz
+-rw-r--r--  1 ilg  staff       109 Jan 31 10:56 xpack-qemu-riscv-8.1.0-1-darwin-x64.tar.gz.sha
 ```
 
 #### Apple Silicon macOS
@@ -324,8 +295,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build/darwin-arm64/deploy
 total 34480
--rw-r--r--  1 ilg  staff  17129362 Jan 31 10:41 xpack-qemu-riscv-7.2.0-1-darwin-arm64.tar.gz
--rw-r--r--  1 ilg  staff       111 Jan 31 10:41 xpack-qemu-riscv-7.2.0-1-darwin-arm64.tar.gz.sha
+-rw-r--r--  1 ilg  staff  17129362 Jan 31 10:41 xpack-qemu-riscv-8.1.0-1-darwin-arm64.tar.gz
+-rw-r--r--  1 ilg  staff       111 Jan 31 10:41 xpack-qemu-riscv-8.1.0-1-darwin-arm64.tar.gz.sha
 ```
 
 #### Intel GNU/Linux
@@ -360,8 +331,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build/linux-x64/deploy
 total 19292
--rw-r--r-- 1 ilg ilg 19747356 Jan 31 08:44 xpack-qemu-riscv-7.2.0-1-linux-x64.tar.gz
--rw-r--r-- 1 ilg ilg      108 Jan 31 08:44 xpack-qemu-riscv-7.2.0-1-linux-x64.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 19747356 Jan 31 08:44 xpack-qemu-riscv-8.1.0-1-linux-x64.tar.gz
+-rw-r--r-- 1 ilg ilg      108 Jan 31 08:44 xpack-qemu-riscv-8.1.0-1-linux-x64.tar.gz.sha
 ```
 
 ##### Build the Windows binaries
@@ -387,8 +358,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build/win32-x64/deploy
 total 21980
--rw-r--r-- 1 ilg ilg 22501694 Jan 31 08:41 xpack-qemu-riscv-7.2.0-1-win32-x64.zip
--rw-r--r-- 1 ilg ilg      105 Jan 31 08:41 xpack-qemu-riscv-7.2.0-1-win32-x64.zip.sha
+-rw-r--r-- 1 ilg ilg 22501694 Jan 31 08:41 xpack-qemu-riscv-8.1.0-1-win32-x64.zip
+-rw-r--r-- 1 ilg ilg      105 Jan 31 08:41 xpack-qemu-riscv-8.1.0-1-win32-x64.zip.sha
 ```
 
 #### Arm GNU/Linux 64-bit
@@ -421,8 +392,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build/linux-arm64/deploy
 total 18660
--rw-r--r-- 1 ilg ilg 19099789 Jan 30 22:57 xpack-qemu-riscv-7.2.0-1-linux-arm64.tar.gz
--rw-r--r-- 1 ilg ilg      110 Jan 30 22:57 xpack-qemu-riscv-7.2.0-1-linux-arm64.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 19099789 Jan 30 22:57 xpack-qemu-riscv-8.1.0-1-linux-arm64.tar.gz
+-rw-r--r-- 1 ilg ilg      110 Jan 30 22:57 xpack-qemu-riscv-8.1.0-1-linux-arm64.tar.gz.sha
 ```
 
 #### Arm GNU/Linux 32-bit
@@ -455,8 +426,8 @@ archive and its SHA signature, created in the `deploy` folder:
 ```console
 $ ls -l ~/Work/xpack-dev-tools/qemu-riscv-xpack.git/build/linux-arm/deploy
 total 17636
--rw-r--r-- 1 ilg ilg 18051448 Jan 30 22:54 xpack-qemu-riscv-7.2.0-1-linux-arm.tar.gz
--rw-r--r-- 1 ilg ilg      108 Jan 30 22:54 xpack-qemu-riscv-7.2.0-1-linux-arm.tar.gz.sha
+-rw-r--r-- 1 ilg ilg 18051448 Jan 30 22:54 xpack-qemu-riscv-8.1.0-1-linux-arm.tar.gz
+-rw-r--r-- 1 ilg ilg      108 Jan 30 22:54 xpack-qemu-riscv-8.1.0-1-linux-arm.tar.gz.sha
 ```
 
 ### Update README-MAINTAINER listing output
@@ -688,7 +659,7 @@ To test graphical mode, use Thomas Huth's presentation:
 curl -L https://www.qemu-advent-calendar.org/2018/download/day24.tar.xz \
   -o ${HOME}/Downloads/day24.tar.xz
 (cd ${HOME}/Downloads; tar xvf day24.tar.xz)
-export PATH=${HOME}/Downloads/xpack-qemu-riscv-7.2.0-1/bin:$PATH
+export PATH=${HOME}/Downloads/xpack-qemu-riscv-8.1.0-1/bin:$PATH
 bash ${HOME}/Downloads/day24/run.sh
 ```
 
@@ -702,14 +673,14 @@ They could be BIOS/firmware images, a guest kernel, initrd or some other file lo
 Check whether you intended to load all this guest code, and whether it has been built to load to the correct addresses.
 
 The following two regions overlap (in the memory address space):
-  /home/ilg/Downloads/xpack-qemu-riscv-7.2.0-1/bin/../share/qemu/opensbi-riscv64-generic-fw_dynamic.bin (addresses 0x0000000080000000 - 0x0000000080019b50)
+  /home/ilg/Downloads/xpack-qemu-riscv-8.1.0-1/bin/../share/qemu/opensbi-riscv64-generic-fw_dynamic.bin (addresses 0x0000000080000000 - 0x0000000080019b50)
   /home/ilg/Downloads/day24/risk-v.elf ELF program header segment 0 (addresses 0x0000000080000000 - 0x000000008005d348)
 aplay: read_header:2861: read error
 ```
 
 ## Create a new GitHub pre-release draft
 
-- in `CHANGELOG.md`, add the release date and a message like _* v7.2.0-1 released_
+- in `CHANGELOG.md`, add the release date and a message like _* v8.1.0-1 released_
 - commit with _CHANGELOG update_
 - check and possibly update the `templates/body-github-release-liquid.md`
 - push the `xpack-develop` branch
@@ -720,8 +691,8 @@ The workflow result and logs are available from the
 
 The result is a
 [draft pre-release](https://github.com/xpack-dev-tools/qemu-riscv-xpack/releases/)
-tagged like **v7.2.0-1** (mind the dash in the middle!) and
-named like **xPack QEMU RISC-V v7.2.0-1** (mind the dash),
+tagged like **v8.1.0-1** (mind the dash in the middle!) and
+named like **xPack QEMU RISC-V v8.1.0-1** (mind the dash),
 with all binaries attached.
 
 - edit the draft and attach it to the `xpack-develop` branch (important!)
@@ -744,7 +715,7 @@ If any, refer to closed
 ## Update the preview Web
 
 - commit the `develop` branch of `xpack/web-jekyll` GitHub repo;
-  use a message like _xPack QEMU RISC-V v7.2.0-1 released_
+  use a message like _xPack QEMU RISC-V v8.1.0-1 released_
 - push to GitHub
 - wait for the GitHub Pages build to complete
 - the preview web is <https://xpack.github.io/web-preview/news/>
@@ -785,18 +756,18 @@ watching this project.
 - compare the SHA sums with those shown by `cat *.sha`
 - check the executable names
 - commit all changes, use a message like
-  _package.json: update urls for 7.2.0-1.1 release_ (without _v_)
+  _package.json: update urls for 8.1.0-1.1 release_ (without _v_)
 
 ## Publish on the npmjs.com server
 
 - select the `xpack-develop` branch
 - check the latest commits `npm run git-log`
-- update `CHANGELOG.md`, add a line like _* v7.2.0-1.1 published on npmjs.com_
-- commit with a message like _CHANGELOG: publish npm v7.2.0-1.1_
+- update `CHANGELOG.md`, add a line like _* v8.1.0-1.1 published on npmjs.com_
+- commit with a message like _CHANGELOG: publish npm v8.1.0-1.1_
 - `npm pack` and check the content of the archive, which should list
   only the `package.json`, the `README.md`, `LICENSE` and `CHANGELOG.md`;
   possibly adjust `.npmignore`
-- `npm version 7.2.0-1.1`; the first 4 numbers are the same as the
+- `npm version 8.1.0-1.1`; the first 4 numbers are the same as the
   GitHub release; the fifth number is the npm specific version
 - the commits and the tag should have been pushed by the `postversion` script;
   if not, push them with `git push origin --tags`
@@ -825,12 +796,12 @@ The tests results are available from the
 When the release is considered stable, promote it as `latest`:
 
 - `npm dist-tag ls @xpack-dev-tools/qemu-riscv`
-- `npm dist-tag add @xpack-dev-tools/qemu-riscv@7.2.0-1.1 latest`
+- `npm dist-tag add @xpack-dev-tools/qemu-riscv@8.1.0-1.1 latest`
 - `npm dist-tag ls @xpack-dev-tools/qemu-riscv`
 
 In case the previous version is not functional and needs to be unpublished:
 
-- `npm unpublish @xpack-dev-tools/qemu-riscv@7.2.0-1.1`
+- `npm unpublish @xpack-dev-tools/qemu-riscv@8.1.0-1.1`
 
 ## Update the Web
 
@@ -852,7 +823,7 @@ In case the previous version is not functional and needs to be unpublished:
 
 - in a separate browser windows, open [TweetDeck](https://tweetdeck.twitter.com/)
 - using the `@xpack_project` account
-- paste the release name like **xPack QEMU RISC-V v7.2.0-1 released**
+- paste the release name like **xPack QEMU RISC-V v8.1.0-1 released**
 - paste the link to the Web page
   [release](https://xpack.github.io/qemu-riscv/releases/)
 - click the **Tweet** button

README.md

@@ -105,8 +105,8 @@ After install, the package should create a structure like this (macOS files;
 only the first two depth levels are shown):
 
 ```console
-$ tree -L 2 /Users/ilg/Library/xPacks/@xpack-dev-tools/qemu-riscv/7.2.0-1.1/.content/
-/Users/ilg/Library/xPacks/@xpack-dev-tools/qemu-riscv/7.2.0-1.1/.content/
+$ tree -L 2 /Users/ilg/Library/xPacks/@xpack-dev-tools/qemu-riscv/8.1.0-1.1/.content/
+/Users/ilg/Library/xPacks/@xpack-dev-tools/qemu-riscv/8.1.0-1.1/.content/
 ├── README.md
 ├── bin
 │   ├── qemu-system-riscv32
@@ -192,15 +192,15 @@ For more details please read the
 ### Versioning
 
 The version strings used by the QEMU project are three number strings
-like `7.2.0`; to this string the xPack distribution adds a four number,
+like `8.1.0`; to this string the xPack distribution adds a four number,
 but since semver allows only three numbers, all additional ones can
 be added only as pre-release strings, separated by a dash,
-like `7.2.0-1`. When published as a npm package, the version gets
-a fifth number, like `7.2.0-1.1`.
+like `8.1.0-1`. When published as a npm package, the version gets
+a fifth number, like `8.1.0-1.1`.
 
 Since adherence of third party packages to semver is not guaranteed,
-it is recommended to use semver expressions like `^7.2.0` and `~7.2.0`
-with caution, and prefer exact matches, like `7.2.0-1.1`.
+it is recommended to use semver expressions like `^8.1.0` and `~8.1.0`
+with caution, and prefer exact matches, like `8.1.0-1.1`.
 
 ## Maintainer info
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xpack-dev-tools/qemu-riscv",
-  "version": "7.2.0-1.1",
+  "version": "8.1.0-1.1.pre",
   "description": "A binary xPack with QEMU RISC-V executables",
   "main": "",
   "scripts": {
@@ -65,7 +65,7 @@
       "qemu-system-riscv64": "./.content/bin/qemu-system-riscv64"
     },
     "devDependencies": {
-      "@xpack-dev-tools/xbb-helper": "^1.10.0"
+      "@xpack-dev-tools/xbb-helper": "^1.10.7"
     },
     "properties": {
       "appName": "QEMU RISC-V",

scripts/VERSION

@@ -1 +1 @@
-7.2.0-1
+8.1.0-1