• DasTechniker@lemmy.world
    30·
    2 days ago

    I have a script I run daily (named daily) that makes a timeshift backup, checks for updates from pacman, then checks for updates from the AUR. I’m very fond of it :]

        • jimerson@lemmy.world
          4·
          2 days ago

          Heck yeah! I hope it helps simplify things!

          This might be the first time my limited Linux knowledge has been helpful to an internet stranger. Feels good.

      • ArchAengelus@lemmy.dbzer0.com
        4·
        2 days ago

        I’ve been using yay for years, and it is sufficient. First time I’ve heard of paru.

        Other than being written in rust, how does paru improve the experience of AUR wrapping?

        • DasTechniker@lemmy.world
          3·
          2 days ago

          Googling it, it just seems like yay but in rust and it shows PKGBUILD by default. Still cool to find alternative tools though

        • jimerson@lemmy.world
          2·
          2 days ago

          To be honest, it’s just what I’ve been using since I switched to Cachy half a year ago. There was no conscious decision made between yay or paru.

          I think Go and Rust are both great languages, but there are apparently some speed benefits from using rust/paru. That’s not anything I can factually confirm, just what I’ve heard.

          • ranzispa@mander.xyz
            3·
            2 days ago

            I doubt that speed in a package manager would depend greatly on programming language choice. A package manager downloads the repository index, evaluates your current environment, decides what packages you need and then downloads them. You may get minor speed improvements due to a more performing programming language, but we’re talking about milliseconds differences in a process that likely takes several minutes. I wouldn’t take that into account when choosing across options. Indeed speed can greatly vary across package managers, but that mainly depends on implementation; as such you may have a package manager implemented in a slower language that is faster than one implemented in a faster language.

            If I have to choose a package manager, I wouldn’t even consider speed and rather evaluate functionality. I don’t know paru, I imagine it allows doing what yay allows doing and as such I’d be satisfied with either of them.

  • wltr@discuss.tchncs.de
    11·
    2 days ago

    I do sudo pacman -Syu as a ritual each time when I start my computer or laptop. Like, the very first thing after the system is booted. So far so good, been doing that for 7 years.

      • wltr@discuss.tchncs.de
        1·
        2 days ago

        I had this too, but I use ctrl + r all the time (with fzf), and really have no need for that many aliases.

          • wltr@discuss.tchncs.de
            2·
            2 days ago

            I don’t understand why Syncthing is still not version 2 on Fedora. Did I do something wrong? Did the repo changed? Apart from that, I agree, I really like Fedora on systems where I don’t want to mess with the system. But I do want to mess with my systems, that’s the point of Linux for me now :)

            • ranzispa@mander.xyz
              2·
              2 days ago

              I didn’t even know syncthing 2 was released. As a service type of software I don’t really care too much for new features, I want it to be stable. Judging from this thread it wasn’t really stable until a couple months ago: https://forum.syncthing.net/t/syncthing-2-0-august-2025/24758/30

              I guess I’m fine with that. Software for which I need the latest release I wouldn’t install from package manager anyway.

              I used to mess a lot on my Linux system, now I just want it to work and not have to change anything. Still on default plasma config after years, I guess I just mess with my vim config and little else.

              • wltr@discuss.tchncs.de
                1·
                2 days ago

                I can say about the stability, as I use Syncthing extensively and the version 2 since day one. It had the database issue, perhaps upon migration, which lead the program to crash on my Raspberry Pi 2B with 1 GB RAM. At some point I noticed the issue, removed the database and let it rebuilt it cleanly, which did the job and fixed the issue. Plus, I made a swap partition just in case. Haven’t seen any other issues after that. That was DietPi distro, based on Debian.

                I had no issues like that on Arch, but my Arch desktops, laptops, and servers are more powerful, perhaps they handled the migration better. I expect that this was some bug that was fixed later. Fedora still syncs, but I wonder when would they update the repo, or if that’s me that wasn’t attentive somewhere and I need to change the repo. Maybe they follow the topic closer.

  • palordrolap@fedia.io
    7·
    2 days ago

    For me, it’s about reducing the amount of time the “update available” icon shows up in the system tray, because its very presence bothers me. Maybe there’s something cool and new. Maybe it fixes a severe security problem. If it’s for programs I’m not using right now, then the update can be applied right now. Otherwise it’s going to have to wait until I’m done. And bother me.

    Yes, I could turn updates off and never see it, but that seems like a bad plan in the long run.

    • Buddahriffic@lemmy.world
      2·
      2 days ago

      Can’t you update it all regardless of whether you’re using it because the Linux file system leaves the old file intact and just writes a new file and updates the pointer so anything still using the old file carries on as if nothing happened and just gets the update the next time you run it?

      • palordrolap@fedia.io
        3·
        2 days ago

        This is true. But then I’m not using the latest version while I still have an active session, and that can lead to weird behaviour or errors after the fact.

        Case in point, I once received an Xorg update that I allowed to install, but didn’t restart the computer properly until much, much later.

        By then I’d forgotten about the update, so when I restarted and started having graphics problems, I was mystified.

        I’ve also forgotten how that all panned out, but in the same situation I’d roll back to a previous Timeshift snapshot and work the system forward again until I find the culprit or things are stable, so I assume that’s what I did back then.

        • Buddahriffic@lemmy.world
          2·
          2 days ago

          Yeah, that’s fair. It might be possible to get incompatible versions between two different tools that interact with each other, if say one shuts down and then starts up with the new version but the other doesn’t shut down and stays on the old.

  • rtxn@lemmy.worldM
    7·
    2 days ago

    My home PC, about once a week, or whenever I have to install new software. My work PC, about once a month because the nvidia driver takes fucking ages to update because of DKMS.

    As for the servers under my professional care… it depends. Most of the servers that I made run Debian that I update three times a year whenever the downtime is acceptable for the university (spring break, late summer, early december) or if a CVE needs fixing (e.g. xz-utils). One internet-facing server that I inherited still runs Ubuntu 16.04 because some teachers can’t possibly live without some legacy software and will throw a tantrum if upgrading is even mentioned – that one gets zero updates, and I got the dean’s promise in writing that I wouldn’t be held responsible for it.

    The big virtualization server still runs ESXi 6 because the university didn’t want to pay for a lifetime license when it was available, doesn’t want to pay for a subscription now, and doesn’t want the downtime required to fully migrate to Proxmox VE. So it gets no updates. Plus it has a bad SSL cert and I need Chromium’s thisisunsafe to bypass the error.

    It’s fucking rough out here.

    • poinck@lemmy.world
      1·
      1 day ago

      I inherited a lot of Ubuntu servers at the university, too. But I am not directly responsible which makes life easier; I am just managing it.

      Interestingly, they agreed to monthly updates with possible restarts and they are fine with it, because I keep the servers healthy. And: We even plan to move from VMWare hypervisor to Proxmox VE as well, but we can do it in stages without big downtimes.

      There is one CentOS server carefully isolated which cannot be updated anymore. Moving it to Rocky would introduce a big downtime and redoing a lot of custom config. Luckily the user-facing server of that cluster is running a current Rocky Linux.

      The things, I established so far, are running stable Debian. Nice to see Proxmox VE being based on Debian. (:

      It is interesting that you are in a similar boat, but with a different outcome. I hope that your colleguas will reconsider some day.

  • tal@lemmy.todayEnglish
    7·
    2 days ago

    My Debian trixie desktop system rotates /var/log/apt/history once a month. So over the past year:

    $ zgrep upgrade /var/log/apt/history.log*gz|wc -l
25
$ ls /var/log/apt/history.log*gz|wc -l
12
$

    25 upgrades in 12 months. So about twice a month on average on that one.

    • FauxLiving@lemmy.world
      3·
      2 days ago

      when I have to reboot anyway.

      I do the same, then you have these days: “Ok, I’ll run a quick update before reboot… Updating qt-webengine?, nooooooo”