Skip to content

Release v1.3.0

Compare
Choose a tag to compare
@sakaki- sakaki- released this 26 Sep 19:19
· 58 commits to master since this release

This is an incremental release to v1.2.2.

If you would like to upgrade an existing, older version of this image to v1.3.0 (rather than just downloading and using the latest v1.3.0 image directly), please see below.

Changes in this release (see main project page for further details):

  • Migrated from porthash repository verification to Gentoo's own, official gemato-based approach (with failure quarantine). Accordingly, the porthash USE flag on dev-embedded/rpi3-64bit-meta has switched from default-on to default-off as of v1.3.0, and the weekly-gated rsync URI has changed (to one without polluting porthash signatures), from rsync://isshoni.org/gentoo-portage-pi64 to rsync://isshoni.org/gentoo-portage-pi64-gem. (The older version will continue to be supported for a time, for backwards compatibility during the changeover period.)
  • Added support for the transparent-compression write-through zswap cache to bcmrpi3-kernel-bis, and created a startup service (rpi3-zswap) to start using it. Given the highly compressible nature of most RAM pages on a running system, and the RPi3's relatively meagre I/O capabilities, this should materially improve system responsiveness under load. Parameterized via /etc/conf.d/rpi3-zswap.
  • Added a startup service (rpi3-expand-swap), to increase the ('real', backing-store-based) swapfile size to 1GiB, space permitting, as a one-off operation post root partition and filesystem resize. Parametrized via /etc/conf.d/rpi3-expand-swap.
  • Various minor ebuild tidy-ups.
  • All packages brought up-to-date against the Gentoo tree, as of 16 September 2018. Most packages have been rebuilt on gcc-8.2 (which should bring a small performance improvement).
  • Kernel upgraded to sys-kernel/bcmrpi3-kernel-bis-bin-4.14.71.20180922, accompanying boot firmware to sys-boot/rpi3-64bit-firmware-1.20180919 (these will of course auto-update as new versions are unmasked).

Upgrading from an Earlier Release of the Image

Users downloading this v1.3.0 image directly can of course omit the instructions below; as all settings have been correctly set up for you already.

First check your current release version, by issuing:

demouser@pi64 ~ $ eix rpi3-64bit-meta

(look at the Installed versions: stanza)

Then follow the appropriate directions as shown (based on your release version):

  • If your version is >= 1.3.0, you are already up-to-date! However, if you did not directly download the 1.3.0 image, you should still follow the instructions given immediately below, to ensure all your ancillary settings etc. (which genup may not have conformed for you) are also correct.
  • Or, if your version is 1.2.0, 1.2.1 or 1.2.2, follow these instructions (below).
  • Or, if your version is 1.1.3 or earlier, follow instead these instructions (below).

Upgrading for Users on Version 1.2.x of the Image

For those users on a 1.2.x release, the majority of the upgrade can be taken care of simply by running (as root, or using sudo):

pi64 ~ # emaint sync --repo sakaki-tools
pi64 ~ # emerge --update --oneshot app-portage/genup
pi64 ~ # nice genup

This may take a number of hours to complete.

Next, assuming the genup step completed successfully, you should then perform the following steps to finalize your upgrade.

First, ensure that all fixups have been run (these are small scripts, normally executed by /etc/cron.weekly/fixup, and managed by app-portage/weekly-genup; they may be viewed here). Issue:

pi64 ~ # /etc/cron.weekly/fixup

The output from this may be reviewed in /var/log/latest-fixup-run.log.

Next, ensure that your regular user is a member of the cron group, so that they can maintain their own crontabs. Issue:

pi64 ~ # gpasswd --add demouser cron

Obviously, if you have setup your own regular user, substitute their username for demouser in the above. Repeat the step for each such user you have created.

Then, ensure that your audio settings are persisted across reboots. To do so, issue:

pi64 ~ # rc-update add alsasound boot

Lastly check that you are using the correct binhost. As of 1.3.0, the official Gentoo gemato repository verification (with failure quarantine) is being used, so your binhost needs to be set to the version without additional porthash signed master hashes (since these cause the augmented tree to fail the gemato check). This switch should have been made automatically be the dev-embedded/rpi3-64bit-meta-1.3.0 ebuild, but you should double-check this. To do so, issue:

pi64 ~ # grep sync-uri /etc/portage/repos.conf/gentoo.conf
sync-uri = rsync://isshoni.org/gentoo-portage-pi64-gem

If you do not see the output above, edit /etc/portage/repos.conf/gentoo.conf to correct it, and then run genup again.

Also, ensure you do not have any custom porthash USE flag set in /etc/portage/package.use/rpi3-64bit-meta (this flag has gone from being default enabled in rpi3-64bit-meta-1.2.2 to default disabled in rpi3-64bit-meta-1.3.0). For avoidance of doubt, if you are unsure what is meant by the preceding comment, you have not set a custom flag, and may disregard this point.

Next, clean up any configuration files that may have been changed by the release, using dispatch-conf. When this tool prompts you what to do about a proposed file modification, you should use z to 'zap' any changes you are unsure of (keeping your original configuration file), u to 'use' (accept) any changes that look benign (e.g., where only comments have been modified) and m to 'merge' more complicated proposed changes, some parts of which (only) you wish to keep. If in doubt, use z!

In particular, be sure to zap any proposed changes to /etc/conf.d/rngd and /etc/conf.d/xdm!

Note that your kernel and boot firmware will be upgraded as part of this release, so be sure to reboot your RPi3 once you have completed the above process, to start using them.

Once you have done that, congratulations! You are now running on version 1.3.0!

Upgrading for Users on Version <= 1.1.3 of the Image

Users on v1.1.3 or earlier of the image should first temporarily inhibit upgrade to version 1.3.0, by issuing:

pi64 ~ # echo ">=dev-embedded/rpi3-64bit-meta-1.3.0" > /etc/portage/package.mask/rpi3-64bit-meta

and then follow the instructions for upgrade to 1.2.2 given previously.

Once this has been completed successfully, release the temporary mask:

pi64 ~ # rm -v /etc/portage/package.mask/rpi3-64bit-meta

and then follow the instructions given above to complete the upgrade to 1.3.0.