• ExtremeDullard@piefed.socialEnglish
      24·
      2 days ago

      No Linux system of mine upgrades itself without my explicit consent. That’s one of the many reasons why I don’t run Windows.

      • Snot FlickermanEnglish
        22·
        2 days ago

        Setting those up is me explicitly giving my consent for it to upgrade on a schedule.

        • ExtremeDullard@piefed.socialEnglish
          14·
          2 days ago

          Yeah alright. That’s one way of looking at it 🙂

          I guess what I meant is that I don’t like upgrades that happen without me explicitly requesting each and every one of them, and me watching the upgrade process as it happens for errors.

    • NeatNit@discuss.tchncs.de
      7·
      2 days ago

      I never got unattended-upgrades to work for me on the machine I tried it on. Best I could tell, it just didn’t do anything. It was frustrating.

      But many years back I set up my raspberry pi with a cron job that was effectively (if not literally) apt update && apt full-upgrade && reboot and that seemed to be working just fine.

      • curbstickle@anarchist.nexusEnglish
        5·
        2 days ago

        It broke some things (horrifically) for me because headers didn’t get updated, modules didn’t get rebuilt.

        To make it worse, I didn’t set it up. That shit is disabled now. Defunct. Toast. Never again to run.

        • NeatNit@discuss.tchncs.de
          3·
          2 days ago

          I followed a number of guides to try to get it to work. Including doing that. No dice.

          I still think it’s probably user error on my part, but I’m still shocked there was no command to effectively “force run an unattended upgrade now” to test that it works correctly.

          • boredsquirrel@slrpnk.net
            1·
            1 day ago

            I even set it up using ansible, should work lol

            Install the package, edit the config file, maybe enable a systemd service, maybe not even that