I believe this is not a duplicate of bug 771126 (I think that one is a problem with the repology data, while this one is not). At the time of this writing, the latest version of media-sound/gnome-music is 40.1.1 which is in ::gentoo. https://packages.gentoo.org/packages/media-sound/gnome-music says: > Version 40.1 is available upstream. Please consider updating! > It seems that version 40.1 is available upstream, while the latest version in the Gentoo tree is 40.0. > You think this warning is false? Read more about it here. Versions 40.1.1 and 40.0 are both in ::gentoo, while 40.1 is not. The `Available Versions` table looks correct, with 40.1.1 appearing above 40.0. For an example of a similar case where there are no older missing version in tree, x11-wm/mutter has versions 40.2.1, 40.2-r1, and 40.1-r4 in tree (as well as 40.1-r2 and 3.36.7-r1, but I don't think those are relevant). packages.gentoo.org correctly recognizes 40.2.1 as the latest version and does not display the message quoted above. My suspicion is that if I remove 40.2-r1 from the tree, packages.gentoo.org will then think that a newer version (40.2) is available upstream. I'd be happy to perform that experiment if it would be useful. I think that something is going wrong with the sorting of versions, perhaps where the number of components in the version are unequal. FWIW, the version comparison algorithm used by portage is described in the Package Manager Specification, section 3.3 Version Comparison (see https://dev.gentoo.org/~ulm/pms/head/pms.pdf)
Also, https://packages.gentoo.org/packages/media-gfx/ahoviewer 2.0.0_beta is above 2.0.0_preDate even though in PMS it's the other way around. alpha < beta < pre < p
The problem appears to be a combination of things: 1) gentoo's soko (the thing that powers p.g.o) ignores "devel" versions 2) repology misidentifies 42.1.1 as a devel version. See https://github.com/repology/repology-rules/issues/608
