repology-updater
repology-updater copied to clipboard
Repology backend service to update repository and package data
Currently, comparison of vulnerability against package version is dump as it doesn't take versionflags (such as P_IS_PATCH) into account. This should be fixed. Examples of affected projects: - https://repology.org/project/opensmtpd/information -...
Tracking issue for nixpkgs related issues Issues: - [x] Position missing for perl packages https://github.com/NixOS/nixpkgs/pull/158856 - [x] Position missing for many fonts, simple packages (which are largely just fetchers) https://github.com/NixOS/nixpkgs/pull/158844...
- [ ] Introduce ZFS snapshot support to the update process to allow preserving last parsable repository state - Make repository failures more visible - [ ] Add update log...
For outdated statuses, store version which outdates in a dedicated field. Allows clients to query latest version, including for branches.
**TL;DR:** Some repository has some CVE patched, but Repology shows the package as vulnerable. This is known, and that's why Repology uses the term "potentially vulnerable". However there's no easy...
We need more links for each repository, including bug trackers, mailing list archives etc.
E.g. * ```pkg install {name}```, ```apt-get install```, ```pip install```, ```gem install```, ```choco install``` etc. Need help for other repos.
_TL;DR: see Summary below_ So, we have support for normal versions, and we now also have a special support for prerelease versions. However, we still have to ignore a lot...
Currently some repos are marked as _shadow_, which means that if a metapackage exists only in shadow repos, it's hidden from the list. The purpose is to avoid noise from...