Hi,
This is a second email to contact you about a Non Maintainer Upload for
rsnapshot 1.3.1-5.1 (first is
1413919144.31970.3.ca...@yamcha.kamehouse.iroqwa.org the 2014-10-21
@21:19:09). You've uploaded rsnapshot the 2014-10-21 @21:44 [1] (and
unless i'm wrong without using DELAYED queue) and maybe
Package: tracker.debian.org
Severity: normal
Dear maintainers,
strangely, (old and new) PTS report a new upstream for the
mini-buildd package:
https://tracker.debian.org/pkg/mini-buildd
First, it reports '1.0.0~alpha.8' as new although '1.0.5' is
currently in unstable. Second, it imho should no
Package: qa.debian.org
Severity: minor
User: qa.debian@packages.debian.org
Usertags: debsources
Debsources test suite spans several Debian releases/suites. However, at present
sid and jessie in the test suite are made of exactly the same packages. This is
suboptimal and might hide errors.
We
Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org
Usertags: debsources
Various parts of Debsources UI should really be exposed only if specific
plugins are enabled, e.g., ctags-based search, sloccount statistics, etc. The
way to go about this with Flask are pluggable
Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertags: debsources
Debsources should offer a parseable feed of changes to its dataset (package
addition, removal, suite changes, etc). RSS/Atom is the most natural format to
use here. Implementing this will need a
5 matches
Mail list logo