Enable autorefresh.
This repository does not provide links to package recipes or sources in a way accessible by Repology. This is critical, because one of the goals of Repology is to make the details of how a project is packaged visible to anyone. It makes Repology maintenance harder as it's not possible to easily check where a specific version comes from; it does not allow upstream to check the recipe and improve their software to simplify packaging, or suggest corrections to the maintainer; it does not allow other maintainers to learn new ideas. It may be as well dangerous to users due to lack of transparency. Because of that, this repository is subject to removal in the near future.
See documentation for a best way to make package metadata available for Repology.
Package filtering in Repology is very flexible, so you can combine all kinds of conditions. But here are some preset queries to start with:
There are 3693 maintainer(s) for this repository
There are 6519 known problems for packages in this repository
Markdown code:
[![Repository status](https://repology.org/badge/repository-big/deepin_unstable.svg)](https://repology.org/repository/deepin_unstable)
HTML code:
<a href="https://repology.org/repository/deepin_unstable"> <img src="https://repology.org/badge/repository-big/deepin_unstable.svg" alt="Repository status"> </a>
Badge header may be changed or removed by header
URL parameter, for example: https://repology.org/badge/repository-big/deepin_unstable.svg?header=deepin+20