Incorrect derivation file sometimes

[ryantm]

Our new way of figuring out the derivation file is sometimes wrong. For example,

libgit2 picked the specific version instead of the non-specific one: "libgit2_0_25: 0.25.1 -> 0.26.3"
NixOS/nixpkgs#37474

Same for isl "isl_0_15: 0.15 -> 0.19"
NixOS/nixpkgs#37453

cc @matthewbauer

[ryantm]

Maybe we can filter the list coming from nix-env -qa to remove things containing the _\d+ regex.

[dotlambda]

How about just taking the shortest matching name?
EDIT: the shortest attribute name of course

[matthewbauer]

The libgit2 issue should be fixable without hacks. We have two versions of libgit2 in Nixpkgs but we only want to update the newest one. Repology correctly disagnoses it on the website:

https://repology.org/metapackages/?search=libgit&maintainer=&category=&inrepo=nix_unstable&notinrepo=&repos=&families=&repos_newest=&families_newest=&outdated=on

(notice the "legacy" and "outdated" labels)

Maybe there is a way to only query the "outdated" ones from Repology API? Not too familiar with it.

On the other hand, isl isn't as easy to fix given how the file is structured. The best solution right now might just be to blacklist them. We don't have too many 'multiple versions, single name' anyway.

[matthewbauer]

Maybe we can filter the list coming from nix-env -qa to remove things containing the _\d+ regex.

That won't work because the name of the attribute is still 'isl' and 'libgit2'. We query isl-0.15 and libgit2-0.25.1. The issue is that the "OLD_VERSION" is wrong that we're getting from Repology.

[ryantm]

Maybe there is a way to only query the "outdated" ones from Repology API?

Yes, I'm already doing that. Is there some bit of information we need that we don't get from this line?

libgit2 0.25.1 0.26.3

[matthewbauer]

It should be:

libgit2 0.26.0 0.26.3
isl 0.17.1 0.19

[ryantm]

Oh sorry, I see now that there are multiple entries for nixpkgs unstable. Yes, I think I can fix my repology api code to handle that better.

[matthewbauer]

Yeah looking at the API, the "status" code returned should be "outdated" (as opposed to "legacy").

[ryantm]

Fixed repology-api and checked the output matches what @matthewbauer said above.

[ryantm]

I added a check for version compatibility. It should give up trying to update an attrpath that contains an incompatible version string now.

[ryantm]

This is probably the correct file, but it got to it the wrong way, so it has the wrong attrpath: NixOS/nixpkgs#40830

[ryantm]

I'm closing this in favor of having specific issues about each problem related to this.