when deciding whether the `-y` argument should be added to an operation.
Previously the `-y` was implicitly assumed for regular updates but was
ignored for the cleanup steps.
Now, it is added as defined in the topgrade runtime configuration.
Authored-by: Andreas Hartmann <hartan@7x.de>
Approved-by: Thomas Schönauer <t.schoenauer@hgs-wt.at>
* Added new step: guix (basic support)
* Fixed clippy errors and better practice, Thanks To guidence from @enchant97 <Leo Spratt>
* Removed accidental swp file, as pointed out by @strangelittlemonkey in pull request #982
Authored-by: James Clarke <james@james-clarke.ynh.fr>
Approved-by: Thomas Schönauer <t.schoenauer@hgs-wt.at>
* Ensure `selfupdate` is enabled for SDKMAN!
This subcommand is unavailable when the `sdkman_selfupdate_feature`
option is disabled, as is the case when SDKMAN! is installed via
Homebrew.
https://github.com/sdkman/sdkman-cli/pull/1042
* Fix macOS build; simplify
Co-authored-by: Roey Darwish Dror <roey.ghost@gmail.com>
* Don't call gnome shell extensions if it's not registered in dbus (fix#835)
* fix
* Execute-elevated (#892)
* Introduce the execute elevated method (fix#885)
* fmt
* Fix nix with doas
* Bad import
* No gnome in macOS
* Unused imports
* containers: Pull newer versions of containers
Allows topgrade to update a users containers. It will automatically skip
containers which come from the `localhost` repo as these are self-built.
Respects the version number the containers were initially checked out
with in order not to introduce semver-breaking changes.
Works with podman and docker.
* topgrade: Add 'containers' step
* containers: Ignore some errors for docker
This patch is needed to achieve compatibility between docker and podman.
In particular, docker doesn't store/tell the user from which repository
(i.e. `hub.docker.com`, or `registry.fedoraproject.org`) a container
originates. This has the side-effect, that self-built containers cannot
be distinguished from publicly available containers. Therefore this
patch introduces an exception to the error handling when pulling, by
scanning the output of the `docker pull` command. If it finds the
`registry does not exist` substring in the output, it will skip the
container but **NOT** consider the whole update step failed.
* containers: Skip '<none>' containers
that result from either intermediate products of a container build or
when images are dangling.
* steps: containers: simplify error handling
And don't return errors from within the "unknown container registry"
handling, since that would immediately terminate the whole update which
isn't intended.
