Problem: ujust toggle-updates doesn't change AutomaticUpdatePolicy
#286
Comments
|
This is starting to strongly get into my workflow, is there a way to break the automatic download script in some other ways? |
This comment was marked as outdated.
This comment was marked as outdated.
Logmalix@malix-pc ~> ujust --show toggle-updates
# Turn automatic updates on or off
toggle-updates ACTION="prompt": #!/usr/bin/bash
source /usr/lib/ujust/ujust.sh
CURRENT_STATE="Disabled"
if systemctl is-enabled ublue-update.timer | grep -q enabled; then
CURRENT_STATE="Enabled"
fi
OPTION={{ ACTION }}
if [ "$OPTION" == "prompt" ]; then
echo "Automatic updates are currently: ${bold}${CURRENT_STATE}${normal}"
echo "Enable or Disable automatic updates?"
OPTION=$(ugum choose Enable Disable)
elif [ "$OPTION" == "help" ]; then
echo "Usage: ujust toggle-updates <option>"
echo " <option>: Specify the quick option - 'enable' or 'disable'"
echo " Use 'enable' to Enable automatic updates."
echo " Use 'disable' to Disable automatic updates."
exit 0
fi
if [ "${OPTION,,}" == "enable" ]; then
sudo systemctl enable ublue-update.timer
elif [ "${OPTION,,}" == "disable" ]; then
sudo systemctl disable ublue-update.timer
fi |
This comment was marked as outdated.
This comment was marked as outdated.
|
|
Now that I looked at Bluefin's topgrade config, I think Bluefin's ublue-update does handle rpm-ostree itself and the only issue here is that the classic rpm-ostree updates are enabled, when they shouldn't be. It's happening because the main image (that Bluefin is based on) pulls ublue-os/config, which contains the ublue-os-update-services package and main's post-install.sh script configures and enables it. This was used back when ublue-update didn't exist. The custom image module I'm using, that installs ublue-update removes this package. Try running this to see if As for whether ublue-update handles rpm-ostree, if you can, try running this (with auto-updates disabled & when you know a new image exists, new images are built daily at about 16:40 UTC) If I'm correct, it will update your system using rpm-ostree. You should see a new entry in Bluefin's / Aurora's maintainers would either have to override remove the ublue-os-update-services package as well or remove it from main / config entirely.
The line: Lastly, to be clear, if I am correct, then 'undoing the package' by disabling the classic rpm-ostree updates (AutomaticUpdatePolicy=none and disabling the service) + disabling the services handling Flatpak (All of them are listed at the end of my first comment) is everything you need to do and you can use the |
|
|
After the recent 3.0.0 update, I wanted to toggle the automatic updates again, |
This comment has been minimized.
This comment has been minimized.
|
Thanks for the It would be nice if it could be added to |
Malix-Labs
changed the title
ujust toggle-updates doesn't change AutomaticUpdatePolicy Updates still enabled after toggling it off
Malix-Labs
changed the title
ujust toggle-updates doesn't change AutomaticUpdatePolicy Updates still enabled after toggling it offujust toggle-updates doesn't change AutomaticUpdatePolicy
|
I installed Bluefin in a VM yesterday to not pollute this issue with assumptions anymore. Disabled classic automatic updates provided by Fedora
That means ublue-update does handle rpm-ostree, so I guess I was right saying the classic automatic updates provided by Fedora should not be enabled. (Two tools handling system updates, disabling ublue-update doesnt stop the other tool, so system updates are still handled, hence why this issue was created.)
Before ublue-update is triggered: ublue-update is running: ublue-update finished: @Malix-off Turn off the classic auto updates by Fedora In and do: Use |
My updates are still being made automatically even after having it disabled since yesterday
The text was updated successfully, but these errors were encountered: