apteryx changes
We’re pleased to announce a major new version of the apteryx package manager (0.8.2) is now available for our Ubuntu and Debian platforms. This has a couple of big new features that will make it much more robust and reliable. There are also a few minor bug fixes and other tweaks thrown in for good measure. Here are all the details…
Keep Current Kernel
This is an exciting new feature that massively reduces the chance of removing all kernel packages which could catastrophically leave a system in an unbootable state. When enabled apteryx will not remove the package for the version of the currently running kernel (according to uname). It will also retain all reverse-dependencies for the kernel package so that essential kernel modules packages (e.g. linux-modules or openafs-modules) are not removed. Once a system reboots into a new kernel the older packages will be automatically removed. The feature can be enabled using the Apteryx::Keep-Current-Kernel
option, in LCFG it is done like this:
LCFG_APT_OPTION(kck,Apteryx::Keep-Current-Kernel,true)
This is the default behaviour for the new Ubuntu Noble platform.
Package Cache Updates
When apteryx runs it first loads the package sources and updates the cache. This new version checks the return values from the methods called and raises an exception if any failures occur. This should help avoid a system getting into a reboot-loop if apteryx fails to connect to package repositories for any reason (e.g. network or service issues).
Dry-Run Mode
In dry-run/test mode apteryx now tries harder to not make any changes. In particular, it will no longer update files that are used to record boot-only packages and reboot requirements.
Logging
To make the log file contents more consistent and easier to read, when logging to a file apteryx will now format the time in the same way as the LCFG apt component.
Recent comments