You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
package uqm-content is shown as version 0.8.0+deb with status ignored, which according to docs means:
version is ignored and excluded from comparison for some other reason (e.g. snapshots).
However, correct package version is (and has been for months) 0.8.0+deb-1 as evidented by https://packages.debian.org/bookworm/uqm-content, but it seems to be misdetected by repology by dropping -1 at the end. It is no snapshot, but normal final release of the package.
Could it be fixed if the problem is in repology, or is the problem upstream in Debian?
The text was updated successfully, but these errors were encountered:
Upstream version is 0.8.0, neither 0.8.0+deb nor 0.8.0+deb-1 is correct and usable by repology. Tailing -N component is dropped from deb versions as it denotes a debian revision and is not usable for version comparison, but it does not affect this case.
Thanks for quick reply and clarification on repology use!
In Debian, +deb, +dfsg and +ds are AFAIK common debian-specific upstream-version suffix for repacked stuff (e.g. due to upstream tarball not being DFSG-free, multiple sources being merged into one package etc.). So it is part of Debian revision code, and not upstream version.
I don't know if/how you want to add handling of that to repology, though.
In either case, it might be a good idea to mention in a FAQ repology/repology-webapp#180 (if/when it gets done) what ignored actually means / when it is triggered. Current oneliner at https://repology.org/docs/about is misleading at least in such cases.
On https://repology.org/project/uqm/versions#debian_12
package
uqm-content
is shown as version0.8.0+deb
with statusignored
, which according to docs means:However, correct package version is (and has been for months)
0.8.0+deb-1
as evidented by https://packages.debian.org/bookworm/uqm-content, but it seems to be misdetected by repology by dropping-1
at the end. It is no snapshot, but normal final release of the package.Could it be fixed if the problem is in repology, or is the problem upstream in Debian?
The text was updated successfully, but these errors were encountered: