Dmitry Marakasov

Add repository contacts

2

There are a lot of people among Repology contributors which are affiliated with repositories Repology parses. I'd like to have a complete list of them, to have contact points for...

After successful fetch, then parse failure, the repository won't be parsed until next successful fetch, and that doesn't happen until repository is updated again.

A notice could be added to the repository pages if repository support is lacking in any way. A list of improvements may be set in the `repos.d` yaml files.

Rename all mentions of `metapackage` to `project`

1

Let's use correct and not invented terms. We aggregate `packages` under a single `project`, and track its versions.

Add more links to build logs

1

Logs contain warnings and other useful stuff

Add links to FreeBSD build logs

1

It's not that trivial. https://pkg-status.freebsd.org/ - list of all build servers. Pick 11.0-default for all archs. There are two kinds of log collection: * Global latest for packge: ```http://beefy9.nyi.freebsd.org/data/latest-per-pkg/{pkgname}/{origversion}/110amd64-default.log``` *...

Also introduce explicit `no maintainer` / `unparsable maintainer` flags so we can decide whether to set `default_maintainer` value (see #824). _Originally posted by @AMDmi3 in https://github.com/repology/repology/issues/817#issuecomment-481418342_

Make version setting in PackageMaker more straightforward

1

Currently, we have `set_version()` which sets `version`, `origversion` and `rawversion` with optional normalization of the former two and `set_rawversion()` which sets the latter. It's unobvious and does not allow setting...

Revisit untrusted status

1

(I think I've got related issue, but I can't find it now) So, we `untrusted` package status as a member of `ignored` group. But we don't have clear rules on...

Currently, 80257 of 472995 projects (about 17%) in `metapackages` table have no packages, e.g. they are remains of no longer existing entries. Since the number of them is going to...