You can also track the progress at https://nixpk.gs/pr-tracker.html?pr=367042, is already part of nixos-unstable-small at the time of writing, though this is probably not what a lot of people use. I’ll see when it hits nixos-unstable and let you know, but don’t know when I used my machine the coming days

I have opened a pull request at https://github.com/NixOS/nixpkgs/pull/367042, there might be more changes needed as I had an error in the meta section of the package which I rectified according to the reviewers proposed changes. Not sure this is the end of it, but the request is open

No, Cargo.lock is the only relevant optional one for Rust packages and that is already there, so we should be good. I’ll request it tomorrow if someone else doesn’t beat me to it ;)

No, but I will try to incorporate the nixpkgs update script into it now that the metadata is fixed for the release. I’m not a nixpkgs maintainer (yet) though but usually this is close to automatic.

If you want, you can also submit and maintain the package, or I can put us both as maintainers

It’s rather simple in good cases, here’s my version:

{
  lib,
  fetchFromGitHub,
  rustPlatform,
  perl,
}:

let
  pname = "managarr";
  version = "0.4.1";
in

rustPlatform.buildRustPackage {
  inherit pname version;
  src = fetchFromGitHub {
    owner = "Dark-Alex-17";
    repo = pname;
    rev = "df9bba32cb1628fe0bdf33c71089d7ae085066d4";
    hash = "sha256-2KWuqv0nxMc+H+lmuNQ0lbEm5yE2akuZTa7PT5JcvBs=";
  };

  cargoHash = "sha256-hB4uRgVUp6YngMoXqd03U/n+HdlcYdL5bwvTxI4xCLE=";

  nativeBuildInputs = [ perl ];

  meta = {
    description = "A TUI and CLI to manage your Servarrs";
    homepage = "https://github.com/Dark-Alex-17/managarr";
    license = lib.licenses.mit;
    maintainers = [ ];
  };
}

No worries, I look forward to using this in the future :) (though probably rarely, I don’t use my *arr stack often)

Once you have pushed your next release, I’ll submit the package definition I wrote to nixpkgs, currently worked around the ordering by checking out two commits after the tag, but since there’s no rush to push this, I’ll wait for the next release.

So I’m currently building the package, and there’s one thing that irks me a bit about it, which is that you first tagged your release as 0.4.1 and then changed your Cargo.toml… which means that if you check out that tag on GitHub, the information is always one release behind. This also seemed to be the case with other releases (0.4.0 shows as 0.3.7, 0.3.7 as 0.3.6…). From the commit history, this also seems to affect Cargo.lock, so we’re always getting the lock file for the previous release when checking out the tag. Not ideal

An issue with the program itself: it will always show servers for both radarr and sonarr, regardless if you have them configured or not. Switching to an unconfigured one will yield an error for missing configuration. The program itself looks nice, though I’d prefer if there was the option to respect my shell’s color theme.

Cool stuff, thanks.

Now if Sonarr didn’t depend on a .NET version that is EOL… recently deactivated it for that reason

Lol no

There absolutely are minor versions, but no patch releases. E.g. https://github.com/systemd/systemd/releases/tag/v256.9 which includes no new functionalities, as these are limited to major releases

How’s the non-chain scene in Germany?

Generally pretty good, at least for Kebab, burgers, fries, sausage and grilled chicken. Sandwiches are a total niche though. Basically only smaller ones premade at bakeries and shops (premade still referring to made in store, but not upon request).

Well, this was my perspective from Germany. We don’t have and never had a real competing chain. We have McDonald’s, Burger King, KFC as big fast food chains. So this is what they compete against here

I also actually do like Subway.

It’s it the best thing ever? No. But when I have the choice between McDonald’s, some bread bun with maybe a single slice of salad and subway, the choice is very clear. All their options come with good amounts of veggies, they had decent vegetarian options quite early, their cookies rock and they were one of the few offering free refills.

I dunno what the snobbism is always about. I love it when I need to wait for a train and Subway is an option.

I didn’t have the chance

In the same way words like “antique” and “vintage” bring about specific time periods and aesthetics, “retro” does as well.

In my opinion, “retro” gaming is a misnomer and “vintage” is more fitting for what people usually mean. Retro is something modern or recent made in an older style. Actual old stuff is “vintage”. So a game like UFO 50 is actual retro gaming; of course the definition gets more fuzzy when you look at ROM hacks that don’t even work on the original hardware of the base ROM. But if you buy an original old console and play the games from back then, that’s not really retro by the original definition.

However, I’m well aware that this ship has sailed

It’s a bit of a problem that there’s no serious contender to NixOS. Especially Guix is in a good position to become an alternative.

But it will never happen, because of GNU. And before I continue, I want to make clear that this is not to shit on them.

But realistically, only a fork could make it relevant. NixOS, despite its issues (documentation, flakes, whatever), has a massive mindshare: it’s a huge repository with very up-to-date packages, a lot of modules, and devshells are just a very handy thing for developers. You often find flakes in random GitHub repositories for that reason. There are sponsored efforts around the distribution (like lanzaboote). There are (semi-)commercial entities set up around it (numtide, determinate systems, tweag…)

The difference between NixOS and Guix is probably so large that no commercial provider would want to put in the required work to bring Guix up to speed, and GNU is committed to other values. As such, I think only a very big volunteer effort could make a difference.

Ah, an homage to the killdozer. Such an odd occurrence, the Wikipedia article is wild. Bit of a loon the fella

They’re both stimulants with a dopamine re-uptake inhibitors.

That’s not how amphetamine works. It’s correct for cocaine, but amphetamine promotes dopamine release, it doesn’t inhibit reuptake.

In the end, both increase dopamine availability… but through different mechanisms and they’re chemically different as well.

healthy amphetamine breakfast

Now that’s a pleonasm

Coke isn’t an amphetamine