================================================================================
-approved
---------
+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
Others
------
+<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...
+
+ o melanie doesn't remove udebs when removing the source they build from
+
+ o check_dsc_against_db's "delete an entry from files while you're
+ not looking" habit is Evil and Bad.
+
+ o lisa allows you to edit the section and change the component, but
+ really shouldn't.
+
+ o melanie needs to, when not sending bug close mails, promote Cc: to
+ To: and send the mail anyways.
+
+ o the lockfile (Archive_Maintenance_In_Progress) should probably be in a conf file
+
+ o madison should cross-check the b.source field and if it's not null
+ and s.name linked from it != the source given in
+ -S/--source-and-binary ignore.
+
+ o lauren sucks; she should a) only spam d-i for sourceful
+ rejections, b) sort stuff so she rejects sourceful stuff first. the
+ non-sourceful should probably get a form mail, c) automate the
+ non-sourceful stuff (see b).
+
+ o jennifer should do q-d stuff for faster AA [ryan]
+
+ o split the morgue into source and binary so binaries can be purged first!
+
+ o per-architecture priorities for things like different arch'es
+ gcc's, silly BSD libftw, palo, etc.
+
+ o use postgres 7.2's built-in stat features to figure out how indices are used etc.
+
+ o neve shouldn't be using location, she should run down suites instead
+
+ o halle needs to know about udebs
+
+ o by default hamstring katie's mail sending so that she won't send
+ anything until someone edits a script; she's been used far too
+ much to send spam atm :(
+
+ o $ftpdir/indices isn't created by rose because it's not in katie.conf
+
+ o sanity check depends/recommends/suggests too? in fact for any
+ empty field?
+
[minor] kelly's copychanges, copykatie handling sucks, the per-suite
thing is static for all packages, so work out in advance dummy.
o UrgencyLog stuff should minimize it's bombing out(?)
o Log stuff should open the log file
- o [melanie] bomb out if a) no '[rene]' in the -m/--message, and b)
- no other -d/--done or -C/--carbon-copy
-
o helena should footnote the actual notes, and also * the versions
with notes so we can see new versions since being noted...
o <neuro> the orig was in NEW, the changes that caused it to be NEW
were pulled out in -2, and we end up with no orig in the archive
:(
-
+
o SecurityAcceptedAutoBuild doesn't handle the case of foo_3.3woody1
with a new .orig.tar.gz followed by a foo_3.3potato1 with the same
.orig.tar.gz; jennifer sees it and copes, but the AA code doesn't
o <M>ove option for lisa byhand proecessing
o rene could do with overrides
-
+
o db_access.get_location_id should handle the lack of archive_id properly
o the whole versioncmp thing should be documented
o Fix BTS vs. katie sync issues by queueing(via BSMTP) BTS mail so
that it can be released on deman (e.g. ETRN to exim).
- o write our own locking module or in some other way fix things so we
- don't require a patch to python since upstream refuse to fix it.
-
- o maintainers file needs overrides
-
+ o maintainers file needs overrides
+
[ change override.maintainer to override.maintainer-from +
override.maintainer-to and have them reference the maintainers
table. Then fix charisma to use them and write some scripting
o morgue needs auto-cleaning (?)
+ o saffron: two modes, all included, seperate
+ o saffron: add non-US
+ o saffron: add ability to control components, architectures, archives, suites
+ o saffron: add key to expand header
+
================================================================================
Less Urgent
-----------
- o Accept "," as a seperator in -a, -s etc. args
-
o change utils.copy to try rename() first
o [hard, long term] unchecked -> accepted should go into the db, not
o Logging [mostly done] (todo: rhona (hard), .. ?)
- o jennifer is leaking file descriptors..
-
- o the tar extractor class doesn't need to be redone for each package
+ o jennifer: the tar extractor class doesn't need to be redone for each package
o reverse of source-must-exist; i.e. binary-for-source-must-not-exist
o REJECT reminders in shania.
@ backup of report (?)
@ backup of changes.tgz (?)
+ o --help doesn't work without /etc/katie/katie.conf (or similar) at
+ least existing.
+
+ o rename andrea (clashes with existing andrea)...
+
* Harder:
- o interrupting of stracing jennifer causes exceptions errors from apt_inst calls
+ o interrupting of stracing jennifer causes exceptions errors from apt_inst calls
o dependency checking (esp. stable) (partially done)
o override checks sucks; it needs to track changes made by the
maintainer and pass them onto ftpmaster instead of warning the
o catherine should udpate db; move files, not the other way around [neuro]
o melanie should update the stable changelog [joey]
o update tagdb.dia
-
+
* Bizzare/uncertain:
-
+
o drop rather dubious currval stuff (?)
o rationalize os.path.join() usage
o Rene also doesn't seem to warn about missing binary packages (??)
implement -e/--exact (a la joey's "elmo")
o dsc files are not checked for existence/perms (only an issue if
they're in the .dsc, but not the .changes.. possible?)
-
- * Cleanups & misc:
-
+
+ * Cleanups & misc:
+
o db_access' get_files needs to use exceptions not this None, > 0, < 0 return val BS (?)
o The untouchable flag doesn't stop new packages being added to ``untouchable'' suites
o Fix stuff to look in sensible places for libs and config file in debian package (?)
================================================================================
+
+ --help manpage
+-----------------------------------------------------------------------------
+alyson X
+amber X
+andrea X
+ashley X
+catherine X X
+charisma X X
+cindy X X
+claire X
+denise X
+fernanda X
+halle X
+heidi X X
+helena X
+jenna X
+jennifer X
+jeri X
+julia X X
+kelly X X
+lisa X X
+madison X X
+melanie X X
+natalie X X
+neve X
+rene X
+rose X
+rhona X X
+saffron X
+shania X
+tea X
+ziyi X
+
+================================================================================
+
+Possible Quotes:
+----------------
+
+| <mdz_> SirDibos: that sentence sounds like it wants to be a bug report when it grows up
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+| From: Andrew Morton <akpm@osdl.org>
+| Subject: Re: Linux 2.6.0-test1 Ext3 Ooops. Reboot needed.
+| To: Ricardo Galli <gallir@uib.es>
+| Cc: linux-kernel@vger.kernel.org
+| Date: Fri, 18 Jul 2003 14:27:20 -0700
+|
+| Ricardo Galli <gallir@uib.es> wrote:
+| >
+| > "File alteration monitor", from Debian.
+|
+| OK.
+|
+| > $ apt-cache show fam
+|
+| I was attacked by dselect as a small child and have since avoided debian.
+| Is there a tarball anywhere?
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+| From: Bob Hilliard <hilliard@debian.org>
+|
+| In my experience, James has been very responsive, albeit not
+| verbose, to reasonable questions/requests that don't start out saying
+| "James is a bum - throw him out".
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+| <eigood> Kamion: are you too busy to look at my generic
+| include/exclude stuff for the bts yet?
+| <Kamion> eigood: expect me to be busy for about the next week at this
+| rate
+| <eigood> my %field_match = (
+| <eigood> 'subject' => \&contains_field_match,
+| <eigood> 'severity' => \&exact_field_match,
+| <eigood> that's how it works, basically
+| <eigood> I'm a big fan of callbacks
+| [...]
+| <eigood> Kamion: how do you feel about having
+| per-bug/per-package/per-source notes support in the bts?
+| <Kamion> eigood: as I said five minutes ago, I really don't have time
+| to think about it right now, sorry
+| <Kamion> here, maybe it would be clearer if I /part
+| <-- Kamion (~cjwatson@host81-129-36-235.in-addr.btopenworld.com) has left #debian-devel (too busy. no, really.)
+| <eigood> no need to be hostile
+| <Joy> eigood: he told you he's too busy and you kept bugging him. take
+| a hint :)
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+<mstone> bwahahaha. Dear "security@debian.org" Thank you for your
+ email about "[SECURITY] [DSA-403-1] userland can access Linux
+ kernel memory" ...I need to filter out spam... To send email to
+ vhs@flexdesign.com please put "ducks" anywhere on your subject
+ line. ...Thanks, Bob...
+<mstone> I'll be sure to do that...
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+<drow> Hmm, that was a nice short bug report.
+<drow> to submit@: "strdup(NULL) segfaults" to -done@: "Yes, go away"
+[...]
+<Kamion> how did he pass T&S? sheer bloody-mindedness?
+[...]
+<drow> Good attention to detail?
+<drow> Masking of psychopathic tendencies?
+* drow shrugs
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+http://yro.slashdot.org/comments.pl?sid=91696&cid=7890274
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+<Joy> argh.
+<Joy> i accidentally banned all mails to the bts that had 'ossi' in them
+<Joy> "possible" etc
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+<http://www.livejournal.com/users/mjg59/2003/12/24/>
+
+Wednesday, December 24th, 2003
+3:34 pm
+Dear PC World,
+
+1) The most common chipset used in Pentium-II machines is the Intel 440BX. It is also relatively common in slower P-IIIs, and is approximately identical to the 440MX (a one-chip version aimed at laptops).
+
+2) The 440BX has the interesting feature of only being able to address up to 128MBit density RAM. This is a relatively widely known issue.
+
+3) Simple maths suggests that if you have a 128MB DIMM with 4 chips on it, they are likely to be 256MBit parts.
+
+4) Marking said DIMMs as being suitable for Pentium-IIs is therefore really indescribably stupid, you wankwits. Please fuck off and die in a great big chemical fire before I get back there to beat you.
+
+Love,
+
+Matthew.
+
+PS,
+
+Die. No, really.
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+<http://www.livejournal.com/users/mjg59/2003/11/12/>
+
+Wednesday, November 12th, 2003
+2:43 am
+It's true that you learn something new every day. Yesterday I discovered that playdough is electrically conductive. I also discovered that RAM becomes unhappy if all of its pins are joined together with electrically conductive material.
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+<http://www.livejournal.com/users/mjg59/2003/11/03/>
+
+Monday, November 3rd, 2003
+3:13 pm
+Hint to people attempting to sell things online:
+
+DON'T PUT http://172.16.100.107/ IN YOUR URLS, YOU INCOMPETENT FUCKMONKEYS
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%