• Stupendous@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 days ago

    Ehh. 7.1 isnt that old. If they don’t make any newer available until 28.04, then this’ll just be a major baseline. It’ll nice regardless just if it leads to more rocm support. The package and maintainers are in place for this to keep going every 6 months

  • chrash0@lemmy.world
    link
    fedilink
    arrow-up
    40
    arrow-down
    1
    ·
    8 days ago

    there’s a world of options. this is an LTS distro. use Arch or Nix or whatever if you want the latest packages. i actually switched to NixOS because the CUDA drivers were too new on Arch, and i wanted a better way to pin versions.

    or i dunno keep publicly complaining about it until someone does the work for you

    • grue@lemmy.world
      link
      fedilink
      arrow-up
      15
      arrow-down
      1
      ·
      8 days ago

      I mean, even in an LTS distro, it sure would be nice if the packages were reasonably up-to-date on the day the version was released.

      • chrash0@lemmy.world
        link
        fedilink
        arrow-up
        11
        ·
        8 days ago

        i guess it would be nice, but packages being a few months out of date is pretty normal for Ubuntu, in my experience. i’m not sure what their testing process is like, but part of using something like Ubuntu is stability guarantees. if they felt like the couldn’t do that for newer versions for whatever reason (resource constraints, lack of downstream interest from stakeholders, etc) they’re not necessarily obligated to.

        • adarza@lemmy.ca
          link
          fedilink
          English
          arrow-up
          11
          ·
          8 days ago

          2 months. lts or not, ubuntu’s freeze date is and has historically been about two months before release.

          if the 2 year cycle between lts is too long for someone, they don’t have to stay on that ride.

      • non_burglar@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        7 days ago

        It would be nice, but the time it takes to do the work of validating package versions for LTS candidacy is either limited or not free, so this is the acceptable compromise.

          • NotSteve_@lemmy.ca
            link
            fedilink
            arrow-up
            8
            ·
            7 days ago

            I’d love to hear what your solution would be? They freeze everything two months out to allow for thorough testing and unless your answer to the problem is switching to a rolling release cycle (which is exactly the opposite of what its supposed to be), then I don’t think there’s anything to be done

            This sort of distro is and always has prioritised stability over having the latest of everything and that’s a good thing. I use CachyOS on my desktop but it’s the absolute last thing I’d put on a server, let alone a production one.

            Just use Docker if you need something newer

            • caseyweederman@lemmy.ca
              link
              fedilink
              arrow-up
              1
              arrow-down
              1
              ·
              7 days ago

              I’m very familiar with their freezing schedule. The impression I’d gotten from this thread was that the package was much more out of date.

              • NotSteve_@lemmy.ca
                link
                fedilink
                arrow-up
                6
                ·
                7 days ago

                It was about 4 months out of date at code freeze from my understanding and 6 months out of date on release which is honestly better than I’d expect normally for packages in official repos

  • SavvyWolf@pawb.social
    link
    fedilink
    English
    arrow-up
    11
    ·
    8 days ago

    Especially with the newer ROCm 7.2.x releases improving hardware support and other improvements. Especially with the rate of improvements to ROCm recently, it’s unfortunate to see ROCm 7.1 shipped in the Ubuntu 26.04 archive.

    Improvements!

    But yeah, 3 months out of date for software that isn’t security critical is fine. Probably just hit the feature freeze at a bad time. It still presumably works well enough for most people.

    • Bloefz@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      edit-2
      8 days ago

      3 months isn’t bad though. Especially since it’s going to be locked out of changes so in 5 years it will be 5 years and 3 months out of date. The bigger problem with rocm is that they cut off older cards way too soon.

      I bought a radeon pro vii brand new from a shop (granted it was a runout sale) and it was already cut off. It still works but not supported.

      AMD can’t keep complaining everyone focuses on CUDA when they don’t even bother to support their own product. It supports very few cards and they get cut off way too soon.

      Nvidia supports even midrange consumer cards and they keep supporting them a long time.

      • kunaltyagi@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        7 days ago

        Support for older cards is getting more common. Some of them are working but not officially supported but I’ve seen more cards entering support than leaving

  • middlemanSI@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    8 days ago

    Being old != bad. Some software is not critical in terms of cyber security. You have to assess the use case. Feels like you’re screaming wolf, without knowing the package.

    • ohshit604@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      8 days ago

      Yeah, would much rather a package designed for my distro than a flatpak.

      I recall a time where the native package on my distro wasn’t working at all, I think this was when I was using discord and tried to use Vencord on Debian 12, so I tried the flatpak version and again it did not work. I was between a rock and a hard place, do I troubleshoot what is essentially a containerized/sandboxed application or try to figure out what’s going on my host machine.

      I chose the latter and eventually got it working, but now I don’t use discord so waste of my time regardless.

      • ☂️-@lemmy.ml
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        8 days ago

        if properly implemented, it shouldn’t matter. much the same way android apks works in pretty much any android “distro”, despite a few snags on the more aggressive manufacturer roms.

        • Excel@lemming.megumin.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 days ago

          No, Flatpak limitations literally make it impossible to get all Discord features working. It’s not a problem with the config, it’s a design flaw of Flatpak itself.

          • ☂️-@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            7 days ago

            then it’s not properly implemented yet, on either side.

            i’m curious as to which ones though, what can’t you do? i have everything working.

  • ratatouille@feddit.org
    link
    fedilink
    Deutsch
    arrow-up
    1
    ·
    8 days ago

    Will test it as soon as possible. Does someon know how compartible it is with a qemu VM ? I need some GPU abilities like Vulkan there.

  • Chaser@lemmy.zip
    link
    fedilink
    arrow-up
    4
    arrow-down
    5
    ·
    8 days ago

    Surprise! A Debian based distro uses antique packages! Who would have seen that coming? 🙀 /s

    • Lemmchen@feddit.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      8 days ago

      This only holds true if you’re talking about Debian Stable, there are definitely Sid or Testing based distros for which that doesn’t hold true.
      See PikaOS for example.