GitXplorerGitXplorer
r

distro-tracker

public
6 stars
2 forks
0 issues

Commits

List of commits on branch master.
Verified
3b02853e5040cccfc904b7a3dadc322a82761d83

Ensure we are able to extract the signature from the message body

rrhertzog committed 2 years ago
Verified
80ac4967c863a599fc8c7b3d52b7b479fb2d0f42

Properly deal with multipart signed messages in EmailNews

ccpina committed 2 years ago
Verified
4db169b5b5441875afd0bc9ff0214e736c966b58

Get rid of the link to lintian.debian.org for now

rrhertzog committed 2 years ago
Verified
6f13e5ea65d34bad02a40a40df00e509129b8abd

use explicit querystring variable name, for clarity

mmapreri committed 2 years ago
Verified
842defbac3030641f0f6a6b7f7db80a8f5527981

Switch lintian data source to udd

rrhertzog committed 2 years ago
Verified
4eca5c7ab6f29e0dba4be4b4526b49070d755a37

Do not use xvfb since we use --headless in test suite

rrhertzog committed 3 years ago

README

The README file for this repository.

distro-tracker

distro-tracker is a set of services tailored to distribution developers, package maintainers, and anybody who might have to interact with those people (upstream developers, bug reporters, advanced users, etc). It lets you follow almost everything related to the life of a package (or of a set of packages).

Documentation

The documentation always matches what's in the git repository's master branch.

Otherwise you can generate the documentation yourself by doing make html in the docs subdirectory of the distro-tracker git repository.

Interacting with the project

How to contribute

Have a look at the "Contributing" section of the documentation.

Contact information

You can interact with the developers on the debian-qa@lists.debian.org mailing list (archive) or on the #debian-qa IRC channel on the OFTC network (irc.debian.org server for example).

The lead developer is Raphaël Hertzog (buxy on IRC).

Reporting bugs and vulnerabilities

We are using GitLab's bug tracker to manage bug reports which are related to the source code itself. You should file new bugs there.

However, we also use the Debian bug tracker with its tracker.debian.org pseudo-package to manage bug reports which are related to the instance which is currently running at https://tracker.debian.org. You should thus check its list of open issues before filing a new bug to avoid duplicates. You can also have a look at all the closed bug reports too.

Security issues should be reported to the bug tracker like other bugs. If you believe that the issue is really sensitive, then you can mail Raphaël Hertzog privately.

Misc information

Badges

CII Best Practices

Known distro-tracker deployments