Previously when performing the "system" upgrade step, rpm-ostree would
be passed a "--yes" argument when it was configured in topgrade.
However, this is not an option available for rpm-ostree, so it would
cause an error and abort execution of the updates.
On a rpm-ostree based system, topgrade would previously fail to detect
the rpm-ostree executable and fall back to yum instead, which isn't
available. This was caused by constructing a Path instance with
`Path::new`, rather than querying the underlying OS for a path to the
rpm-ostree executable.
Make the `system` update step use `which` to determine if an executable
called "rpm-ostree" is available on the system and get the correct path
to the executable.
* Bedrock Linux (fix#745)
* Add more distributions
* fix
* fix
* Fix
* Merge
* Move pacnew to the correct location
* Version bump
* Correct spelling for GNOME Shell extensions update (#778)
* fix gnome shell extensions update object path (#788)
* config: ArchPackageManager should be snake_case (#784)
* config: ArchPackageManager should be snake_case
* Remove unnecessary strum macro
* Add arch_package_manager to config.example.toml
* Add release pipeline
* Run GNOME update only when using GNOME
* Delete travis file and appveyor
* Bump
* Support rust 1.51.0 (#789)
* Cross compilation
* Bump
* fix: GNOME detection for customized version (#790)
Signed-off-by: Noel Georgi <git@frezbo.dev>
* Add a flag to disable showing Arch Linux news (fix#786)
* Bump
* Update pacstall (fix#769)
* Add an option to force vim plug update (#795)
* Add an option to force vim plug update (fix#751)
* Rustfmt
* Update src/config.rs
Co-authored-by: M*C*O <mcofficer@gmx.de>
Co-authored-by: M*C*O <mcofficer@gmx.de>
* Add new step pacdiff (#796)
* Add Support for Spicetify (#798)
* Look for ~/.config/emacs directory in Windows (fix#766)
* Pass --force to doom when -y is set (fix#799)
* Implement cleanup for flatpak (#801)
* Cleanup flatpak
* Fix compile error
* Make sure we only move our values at the very end
* Access config.cleanup() through ExecutionContext
* Improve man page (#803)
Wordings & argument format
* Avoid running remote topgrade on the current host (fix#804) (#807)
* Merge the command line and the configuration flags of --only and --disable (fix#805) (#806)
* Merge the command line and the configuration flags of --only and --disable (fix#805)
* Fix
* Fix rust requirement in the readme
* Selective yes (fix#802) (#808)
* Selective yes flag (fix#802)
* Selective yes flag (fix#802)
* selective yes
* MacOS
* Fix bedrock detection
* Bedrock fixes
* format
* Fedora fixes
Co-authored-by: Björn Daase <bjoern.daase@gmail.com>
Co-authored-by: modularTaco <37046961+modularTaco@users.noreply.github.com>
Co-authored-by: M*C*O <mcofficer@gmx.de>
Co-authored-by: Noel Georgi <git@frezbo.dev>
Co-authored-by: Manuel Hässig <mhaessig@users.noreply.github.com>
Co-authored-by: Janek <27jf@pm.me>
This change adds the option `flatpak.use_sudo` that allows to update
the system-wide installation with sudo. When set to `true` the
system-wide installation will be updated with sudo. If set to `false`
(default) the update will be run as regular user.
This solves the problem where running `flatpak update` on a remote
system fails if run as regular user.
Fixes#737.
This change adds an option, firmware.upgrade, that if set to `false`
only checks for and displays available firmware updates. If set to `true`
(default) the user is offered to run the firmware upgrade.
This commit makes it possible to *not* to use `rpm-ostree` even on
systems where it is detected.
This commit is fully backwards compatible with previous releases, and
without changing the config file all previous behaviors are the exact
same.
This commit adds the `rpm_ostree` field in the `[linux]` table of the
configuration, and defaults to `true`. This means Topgrade will first
check if `/usr/bin/rpm-ostree` exists, and only if so then check if the
user does not want to use `rpm-ostree` via the configuration. If the
user *does not* want to use `rpm-ostree`, then normal operation
continues checking for DNF or YUM.
This makes it possible for people where `rpm-ostree` is installed, but
where the system is not an `ostree` based distribtuion. This happens
when people are using things like `osbuild-composer` to build images,
or Cockpit with the Compose feature enabled (which uses
`osbuild-composer` internally).
An alternative to this commit would be to make the config field a
negative such as `no_rpm_ostree`, however that goes against the norm in
other fields.
Closes#710
