asterisk-opus reports

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 (1)

Created 2 years ago, accepted

The project needs some version(s) to be marked as ignored
The project needs to be split into multiple projects
Comment:
There are two variations of this package, the one is from Digium (semi proprietary, blob https://wiki.asterisk.org/wiki/display/AST/Codec+Opus, https://downloads.digium.com/pub/telephony/codec_opus/).

It should be noted this version has multiple major branches for the different asterisk versions (first version digit must match the first digit from asterisk versions).

The open-source version (which I suspect is where the dated version comes from). As I understand this can be compiled for any version of asterisk. Unfortunately I seem unable to locate the repository right at the moment.

I'm not 100% sure if these two sources should be split or whether the dated version merely needs to be ignored.
Repology reply:
Not sure either. Ignoring for now as there's no such tag.

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).

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 - these need homepage information to be split and will be split automatically as soon as homepage information is available.

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 (e.g. python- or python3-) (common problem for Slackbuilds and Debian source packages).
go:* packages, which have no official naming scheme.
Packages with incorrect names (which should be renamed in repositories instead).

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 asterisk-opus

Current reports (1)

New report