Nicolas schrieb am Mittwoch der 09. Februar 2022 um 15:29 +01: > Hello, > > Xinglu Chen writes: > >> The point of the Repology updater is to act as a fallback if none of >> the other updaters can update a package, e.g., ‘maven-dependency-tree’. >> I already mentioned that language-specific updaters usually provide more >> accurate and detailed information, so they should be used when possible; >> we aren’t losing anything here. > > One issue is that such an updater will introduce frequent false > positives. It is common for Repology to get the latest release wrong, > because some distribution is doing fancy versioning, or because > different distributions disagree about what is upstream. Yeah, I have noticed that it sometimes thinks that a version like “20080323” is newer than something like “0.1.2-0.a1b2b3d”, even though it might not necessarily be true. This seems to be the case for a lot of Common Lisp packages which usually don’t have any proper releases. > I don't think we can rely on Repology's "newest" status. The updater may > need to provide its own version comparison tool, because Repology's tool > and Guix versioning do not play nice, in particular when using > `git-version'. In my testing, the “newest” status does a pretty good job (besides the problem I mentioned above) Some other “bad” updates I found[*] are listed below (excluding Common Lisp packages). --8<---------------cut here---------------start------------->8--- guile-ac-d-bus would be upgraded from 1.0.0-beta.0 to 1.0.0-beta0 sic would be upgraded from 1.2 to 1.2+20210506_058547e tla2tools would be upgraded from 1.7.1-0.6932e19 to 20140313 quickjs would be upgraded from 2021-03-27 to 2021.03.27 stow would be upgraded from 2.3.1 to 2.3.1+5.32 cube would be upgraded from 4.3.5 to 2005.08.29 python-ratelimiter would be upgraded from 1.2.0 to 1.2.0.post0 gr-osmosdr would be upgraded from 0.2.3-0.a100eb0 to 0.2.3.20210128 countdown would be upgraded from 1.0.0 to 20150606 http-parser would be upgraded from 2.9.4-1.ec8b5ee to 2.9.4.20201223 xlsx2csv would be upgraded from 0.7.4 to 20200427211949 keynav would be upgraded from 0.20110708.0 to 20150730+4ae486d --8<---------------cut here---------------end--------------->8--- It seems like most of these could be solved by checking if the version scheme changed from semver to calver. I think that’s a pretty good result considering how many packages we have. [*] Until I ran into