• ⸻ Ban DHMO 🇦🇺 ⸻@aussie.zoneOP
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    11 months ago

    I’m not sure (I’m about to install it for the first time - on this computer) - According to this all you need to do is:

    # nix-channel --add https://channels.nixos.org/nixos-23.11 nixos
    # nixos-rebuild switch --upgrade
    
    • trillian@feddit.de
      link
      fedilink
      arrow-up
      4
      ·
      11 months ago

      This procedure doesn’t work with flakes as they come with “channels included”.

    • λλλ@programming.dev
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      11 months ago

      What if I just want to upgrade some packages? Like not change channel, but Firefox needs an update? I’m not op and don’t use flakes btw

      • trillian@feddit.de
        link
        fedilink
        arrow-up
        3
        ·
        11 months ago

        If using flakes you could just for instance add another input. You can also set the input URLs to specific states of the nixpkgs repository by eg referencing specific commits. Then, you should be able to just, e.g., pick Firefox from unstable, another package from the current stable channel, and maybe a broken package from a pull request fixing said package.

        If you are not using flakes you can also add system wide channels. IIRC you can then import these channels into your configuration.nix and select packages from the corresponding channels. But here the channels/inputs are not part of configuration itself in contrast to when using flakes.

            • λλλ@programming.dev
              link
              fedilink
              arrow-up
              1
              arrow-down
              1
              ·
              11 months ago

              Is that the equivalent to apt update and apt upgrade? I don’t want to apt dist-upgrade lol

              • Laser@feddit.de
                link
                fedilink
                arrow-up
                2
                ·
                11 months ago

                When not using flakes, nixos-rebuild switch --upgrade is equivalent to apt update; apt upgrade. The equivalent to dist-upgrade is nix-channel add $NEW-CHANNEL-URL nixos and then performing a regular update.

                • λλλ@programming.dev
                  link
                  fedilink
                  arrow-up
                  1
                  arrow-down
                  1
                  ·
                  11 months ago

                  Thanks. I’ve done switch many times after editing my config file. I’ve never added --upgrade!

          • Laser@feddit.de
            link
            fedilink
            arrow-up
            1
            ·
            11 months ago

            I’m a bit confused about what you actually want? Do you just want to update your packages, but stay on the same NixOS version? Just continue like before. Do you want to stay on your current version, but use some packages from the next version? That should also be possible if you somehow include that channel in your configuration.nix (though I don’t know how this would work in practice).

            Personally, I just run with unstable though, then the releases aren’t that important.

            • λλλ@programming.dev
              link
              fedilink
              arrow-up
              1
              arrow-down
              1
              ·
              11 months ago

              I think I thought unstable would mean, well, unstable. Like nightly releases or something. Would you use unstable for Firefox?

              • Laser@feddit.de
                link
                fedilink
                arrow-up
                1
                ·
                11 months ago

                I think unstable and the fixed versions use the same Firefox package, so you wouldn’t gain anything. The difference is rather in libraries that get used and how the distribution does things. For example, the changes listed in https://nixos.org/manual/nixos/stable/release-notes#sec-release-23.11-incompatibilities just appeared mostly one by one for me; one day, I wanted to update my system and got the error that the fonts option got renamed, so I had to change my configuration.

                The fonts.fonts and fonts.enableDefaultFonts options have been renamed to fonts.packages and fonts.enableDefaultPackages respectively.

                While when using a fixed point release, these changes won’t happen. Only when you switch releases. That’s what “unstable” refers to.