binutils 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 (5)

Created 8 months ago, accepted

Comment:
binutils-gold needs to be classified as a legacy release.
GNU only releases gold sources on even releases now (2.44, 2.46, etc).
So currently binutils 2.45 has been released (no gold sources) so binutils including gold can only be release 2.44 at the highest.

Created 4 years ago, rejected

The project needs other projects merged into it
Comment:
binutils-wrapper
Repology reply:
Description says it's a wrapper script, not binutils

Created 7 years ago, accepted

The project needs some version(s) to be marked as ignored
Comment:
*.90 devel

Created 8 years ago, accepted

Comment:
ignore GNU GUIX, "2281" version

Created 8 years ago, accepted

The project needs some version(s) to be marked as ignored
Comment:
regression caused by haiku versioning: e.g. 2.29.0_2017_08_05

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.
Maintained forks of abandoned projects, unless a fork has known fatal drawbacks.

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) which are not listed in CVEs section 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 binutils

Current reports (5)

New report