Various
-------
-* Lintian based automated rejects
- - Have a set of lintian tags each package *must* not have. If it does
- -> reject.
- - If a tag is overriden by the maintainer, do not reject, but put it
- into NEW. If the override is ok note that in a table and dont act on
- it for any future uploads of this package anymore.
- - possibly have two classes of tags. one for "shouldnt happen by
- accident" and one "shouldnt happen". the first gets ignored from us
- if overwritten in the package, the second only us can overwrite.
- - its a suite option in dak, not active for all at once.
+* Implement autosigning, see ftpmaster_autosigning on ftp-master host in text/.
* Throw away all DD uploaded .debs. (Depend on "Lintian based automated
rejects")
- its a suite option, not active for all at once.
- should have all buildd machines under dsa control
-* Implement autosigning, see ftpmaster_autosigning on ftp-master host in text/.
-
* Check TODO.old and move still-valid/useful entries over here.
* need a testsuite _badly_
- needs updateX.py written and then the rest of the code changed to deal
with it.
-* Checkout SQL Alchemy and probably use that for our database layer.
-
-* reject on > or < in a version constraint
-
* use pythonX.Y-tarfile to check orig.tar.gz timestamps too.
* the .dak stuff is fundamentally braindamaged for various reasons, it