!lZLfSUtSOVjwYTmPbU:nixos.org

nixpkgs-update

169 Members
Keeping nixpkgs up to date. r-ryantm bot. https://github.com/ryantm/nixpkgs-update and https://github.com/nix-community/infra/blob/master/build02/nixpkgs-update.nix54 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
18 May 2025
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) Okay, i give up-
Following package:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/sd/SDL_ttf/package.nix
We currently set the version "2.0.11.1-unstable-2024-04-23.
Upstream only has a tag for 2.0.11. They won't be tagging any more old versions for SDL_ttf for SDL1. But, canonically, we are on 2.0.11.1: https://github.com/libsdl-org/SDL_ttf/commit/e31d11a692e5b55e8e624ad766e4e44d655422c8
Currently, running the update script on SDL_ttf just crashes, because the 2.0.11.1 tag does not exist. But removing the .1 isn't entirely correct either. What is the best way to make the update script succeed and still correctly represent the version?
21:17:46
@fliegendewurst:matrix.orgFliegendeWurstRemoving the ".1" seems correct to me, we use the last released version in the unstable naming scheme.21:21:51
@fliegendewurst:matrix.orgFliegendeWurstAnd 2.0.11 is the last released version21:21:58
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)

pbsds said 2.0.11.1 was the actual version, but dropping the .1 would have been my solution too. It is common for release notes entries to be prepared before the tag (and edited later!). And https://repology.org/docs/requirements also explicitly says to do -post of tagged too:

Obviously, no fake versions, e.g. versions which were not officially released by upstream. Note that a mere mention of "next" version by upstream (in changelog or build system script) does not make it official. A git tag or a release announcement does.

21:23:36

Show newer messages


Back to Room ListRoom Version: 9