GitXplorerGitXplorer
r

distro-tracker

public
6 stars
2 forks
0 issues

Commits

List of commits on branch master.
Verified
674d89ff943ec8d831ebdc1b0aee4724d1c7ca69

Adding tarfile member sanitization to extractall()

TTrellixVulnTeam committed 2 years ago
Unverified
70564213d31a440890973014446a9ba2adb5eee1

Merge branch 'drop-clang' into 'master'

rrhertzog committed 2 years ago
Unverified
447bed2d4272619d1c595ae2b8926650eb4af4fd

debian: drop the outdated clang service

committed 2 years ago
Verified
c444311335caf88ee5b257e9f074dda25e0e1218

Deal with leading spaces/linefeeds in subjects

rrhertzog committed 2 years ago
Verified
0bf7999f0e5fc2d855c0d6bd31b36069637ada8a

Update some versions in tox.ini

rrhertzog committed 2 years ago
Verified
c6f503dcc0dc64a102b5fc63c4eea1cb1ce8ef0f

Use external logrotation combined with WatchedFileHandler

rrhertzog committed 2 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