dosbox reports - Repology

While repology tries its best in matching packages across different repositories, this is quite a complex task:

Packages of a single software project may be named differently in some repositories (for instance, libagg vs. agg, dungeoncrawl vs. dungeon-crawl, fonts-linuxlibertine vs. fonts-ttf-linuxlibertine vs. linux-libertine-fonts vs. linuxlibertine-fonts-ttf).
There may be multiple unrelated software projects with a same name (for instance, clementine is both X11 window manager and a media player).
Some packages may use incorrect versions (for instance, picking "next" version number which was not released yet when packaging a git snapshot, or using dates and commit hashes instead of version numbers).

Repology uses a set of manually edited rules to resolve these cases. You may submit a change to the ruleset directly or use this form to suggest an improvement to the ruleset. Please only use this for problems which may be fixed by the ruleset (which are basically problems listed above).

Current reports (3)

Created more than a year ago, accepted

The project needs some version(s) to be marked as ignored
The project needs to be split into multiple projects
Comment:
Dosbox laest version really is 0.74.3.
0.77.0 and 0.77.1 does not exists...
But version 0.77 seems to be related to dosbox-staging project on github : https://github.com/dosbox-staging/dosbox-staging , which looks like some kind of fork in the manner of dosbox-x or dosbox-pure.

Created 2 years ago, accepted

The project needs some version(s) to be marked as ignored
Comment:
dosbox itself has still no 0.76.0 version.
This version only exists in dosbox-staging.

Created 4 years ago, rejected

Comment:
0.74.3.r4253 is not an outdated version, it is a development version.
Repology reply:
This is an unofficial snapshot scheme, there's no way to meaningfully compare it neither with releases nor with other snapshots (which have different format). Since there is a latest release in slackbuilds as well which makes this snapshot marked as legacy (as opposed to outdated which would needlessly call for action from maintainer), I consider this "works as indended".

New report

Needs version ignore

Check if the latest version detected for this project is incorrect (e.g. a non-existing version, version with incorrect format, version with date or a git commit hash) and should be ignored. Please provide a prooflink for unapparent cases (e.g. a list of VCS tags or official site mentioning actual latest version).

Prerequisites:

If upstream does not tag/publish official releases, please submit an issue asking them to do so first.

Needs split

Check if this entry refers to multiple unrelated projects and thus needs to be split into multiple entries. Naming suggestions for new projects are welcome.

Will not split:

Legacy or ESR branches of the same project.
*-unclassified projects which lack valid homepage information.

Needs merge

Check if there are other Repology entries for the same project under different names which should be merged into one. Please list them in the comment field, as well as suggested target name.

Will not merge:

Modules (e.g. python) without consistent prefix (such as python- or python3-) (common problem for Slackbuilds and Debian source packages).
go:* packages, which have no official naming scheme.
Packages with incorrect names (should be renamed in repositories instead).
Lots of package variants (common for AUR and Nix) - repositories are expected to provide master project name for these.

Needs vulnerability information update

Check if there are known older CVEs (vulnerabilities) for this project. Note that there's expected lag of CVE information propagation so there's no need to report very recent CVEs. The idea is to fill missing CPE bindings which allow matching both past and future vulnerabilities to projects.

Will not accept:

Reports for recent CVEs which have not been analyzed by NVD yet (so please check NVD first).
Reports for incorrect version ranges - please report these to NVD.

Additional comments

Report problem for dosbox

Current reports (3)

New report