================================================================================
-queue/approved
---------------
+Others
+------
- o What to do with multi-suite uploads? Presumably hold in unapproved
- and warn? Or what? Can't accept just for unstable or reject just
- from stable.
+ o tabnanny the source
- o Whenever we check for anything in accepted we also need to check in
- unapproved.
+ o drop map-unreleased
- o non-sourceful uploads should go straight through if they have
- source in accepted or the archive.
+ o check email only portions of addresses match too, iff the names
+ don't, helps with the "James Troup <james@nocrew.org>"
+ vs. "<james@nocrew.org>" case.
- o security uploads on auric should be pre-approved.
+ o ensure .dsc section/prio match .changes section/prio
+ o rhona's kind of crap when asked to remove a lot of files (e.g. 2k
+ or so).
-Others
-------
+ o we don't handle the case where an identical orig.tar.gz is
+ mentioned in the .changes, but not in unchecked; but should we
+ care?
+
+ o madison could do better sanity checking for -g/-G (e.g. not more
+ than one suite, etc.)
+
+ o use python2.2-tarfile (once it's in stable?) to check orig.tar.gz
+ timestamps too.
+
+ o need to decide on whether we're tying for most errors at once.. if
+ so (probably) then make sure code doesn't assume variables exist and
+ either way do something about checking error code of check_dsc and
+ later functions so we skip later checks if they're bailing.
+
+ o the .katie stuff is fundamentally braindamaged, it's not versioned
+ so there's no way to change the format, yay me. need to fix.
+ probably by putting a version var as the first thing and checking
+ that.. auto-upgrade at least from original format would be good.
+ might also be a good idea to put everything in one big dict after
+ that?
+
+ o [?, wishlist, distant future] RFC2047-ing should be extended to
+ all headers of mails sent out.
+
+ o reject sparc64 binaries in a non '*64*' package.
+
+ o katie.py(source_exists): a) we take arguments as parameters that
+ we could figure out for ourselves (we're part of the Katie class
+ after all), b) we have this 3rd argument which defaults to "any"
+ but could in fact be dropped since no one uses it like that.
+
+ o jennifer: doesn't handle bin-only NMUs of stuff still in NEW,
+ BYHAND or ACCEPTED (but not the pool) - not a big deal, upload can
+ be retried once the source is in the archive, but still.
+
+ o security global mail overrides should special case buildd stuff so
+ that buildds get ACCEPTED mails (or maybe amber (?)), that way
+ upload-security doesn't grow boundlessly.
+
+ o amber should upload sourceful packages first, otherwise with big
+ packages (e.g. X) and esp. when source is !i386, half the arches
+ can be uploaded without source, get copied into queue/unaccepted
+ and promptly rejected.
+
+ o rene's NVIU check doesn't catch cases where source package changed
+ name, should check binaries too. [debian-devel@l.d.o, 2004-02-03]
+
+ o cnf[melanie::logfile] is misnamed...
+
+<aj> i'd be kinda inclined to go with insisting the .changes file take
+ the form ---- BEGIN PGP MESSAGE --- <non -- BEGIN/END lines> --
+ BEGIN PGP SIG -- END PGP MESSAGE -- with no lines before or after,
+ and rejecting .changes that didn't match that
+
+ o rene should check for source packages not building any binaries
+
+ o heidi should have a diff mode that accepts diff output!
+
+ o halle doesn't deal with melanie'd packages, partial replacements
+ etc. and more.
+
+ o lauren, the tramp, blindly deletes with no check that the delete
+ failed which it might well given we only look for package/version,
+ not package/version _in p-u_. duh.
+
+ o melanie should remove obsolete changes when removing from p-u, or
+ at least warn. or halle should handle it.
+
+ o need a testsuite _badly_
+
+ o lisa should have an Bitch-Then-Accept option
+
+ o jennifer crashes if run as a user in -n mode when orig.tar.gz is
+ in queue/new...
+
+<elmo_home> [<random>maybe I should reject debian packages with a non-Debian origin or bugs field</>]
+<Kamion> [<random>agreed; dunno what origin does but non-Debian bugs fields would be bad]
+
+ o rhona should make use of select..except select, temporary tables
+ etc. rather than looping and calling SQL every time so we can do
+ suite removal sanely (see potato-removal document)
o melanie will happily include packages in the Cc list that aren't
being removed...
================================================================================
+queue/approved
+--------------
+
+ o What to do with multi-suite uploads? Presumably hold in unapproved
+ and warn? Or what? Can't accept just for unstable or reject just
+ from stable.
+
+ o Whenever we check for anything in accepted we also need to check in
+ unapproved.
+
+ o non-sourceful uploads should go straight through if they have
+ source in accepted or the archive.
+
+ o security uploads on auric should be pre-approved.
+
+================================================================================
+
Less Urgent
-----------
tea X
ziyi X
+
================================================================================
-<mdz_> SirDibos: that sentence sounds like it wants to be a bug report when it grows up
+Random useful-at-some-point SQL
+-------------------------------
+
+UPDATE files SET last_used = '1980-01-01'
+ FROM binaries WHERE binaries.architecture = <x>
+ AND binaries.file = files.id;
+
+DELETE FROM bin_associations
+ WHERE EXISTS (SELECT id FROM binaries
+ WHERE architecture = <x>
+ AND id = bin_associations.bin);
+
+================================================================================
projects / dak.git / blobdiff