4 [NB: I use this as a thought record/scribble, not everything on here
5 makes sense and/or is actually ever going to get done, so IIWY I
6 wouldn't use it as gospel for the future of katie or as a TODO
7 list for random hacking.]
9 ================================================================================
14 o What to do with multi-suite uploads? Presumably hold in unapproved
15 and warn? Or what? Can't accept just for unstable or reject just
18 o Whenever we check for anything in accepted we also need to check in
21 o non-sourceful uploads should go straight through if they have
22 source in accepted or the archive.
24 o security uploads on auric should be pre-approved.
30 o need to decide on whether we're tying for most errors at once.. if
31 so (probably) then make sure code doesn't assume variables exist and
32 either way do something about checking error code of check_dsc and
33 later functions so we skip later checks if they're bailing.
35 o the .katie stuff is fundamentally braindamaged, it's not versioned
36 so there's no way to change the format, yay me. need to fix.
37 probably by putting a version var as the first thing and checking
38 that.. auto-upgrade at least from original format would be good.
39 might also be a good idea to put everything in one big dict after
42 o [?, wishlist, distant future] RFC2047-ing should be extended to
43 all headers of mails sent out.
45 o reject sparc64 binaries in a non '*64*' package.
47 o katie.py(source_exists): a) we take arguments as parameters that
48 we could figure out for ourselves (we're part of the Katie class
49 after all), b) we have this 3rd argument which defaults to "any"
50 but could in fact be dropped since no one uses it like that.
52 o jennifer: doesn't handle bin-only NMUs of stuff still in NEW,
53 BYHAND or ACCEPTED (but not the pool) - not a big deal, upload can
54 be retried once the source is in the archive, but still.
56 o security global mail overrides should special case buildd stuff so
57 that buildds get ACCEPTED mails (or maybe amber (?)), that way
58 upload-security doesn't grow boundlessly.
60 o amber should upload sourceful packages first, otherwise with big
61 packages (e.g. X) and esp. when source is !i386, half the arches
62 can be uploaded without source, get copied into queue/unaccepted
63 and promptly rejected.
65 o rene's NVIU check doesn't catch cases where source package changed
66 name, should check binaries too. [debian-devel@l.d.o, 2004-02-03]
68 o cnf[melanie::logfile] is misnamed...
70 <aj> i'd be kinda inclined to go with insisting the .changes file take
71 the form ---- BEGIN PGP MESSAGE --- <non -- BEGIN/END lines> --
72 BEGIN PGP SIG -- END PGP MESSAGE -- with no lines before or after,
73 and rejecting .changes that didn't match that
75 o rene should check for source packages not building any binaries
77 o heidi should have a diff mode that accepts diff output!
79 o halle doesn't deal with melanie'd packages, partial replacements
82 o lauren, the tramp, blindly deletes with no check that the delete
83 failed which it might well given we only look for package/version,
84 not package/version _in p-u_. duh.
86 o melanie should remove obsolete changes when removing from p-u, or
87 at least warn. or halle should handle it.
89 o need a testsuite _badly_
91 o lisa should have an Bitch-Then-Accept option
93 o jennifer crashes if run as a user in -n mode when orig.tar.gz is
96 <elmo_home> [<random>maybe I should reject debian packages with a non-Debian origin or bugs field</>]
97 <Kamion> [<random>agreed; dunno what origin does but non-Debian bugs fields would be bad]
99 o rhona should make use of select..except select, temporary tables
100 etc. rather than looping and calling SQL every time so we can do
101 suite removal sanely (see potato-removal document)
103 o melanie will happily include packages in the Cc list that aren't
106 o melanie doesn't remove udebs when removing the source they build from
108 o check_dsc_against_db's "delete an entry from files while you're
109 not looking" habit is Evil and Bad.
111 o lisa allows you to edit the section and change the component, but
114 o melanie needs to, when not sending bug close mails, promote Cc: to
115 To: and send the mail anyways.
117 o the lockfile (Archive_Maintenance_In_Progress) should probably be in a conf file
119 o madison should cross-check the b.source field and if it's not null
120 and s.name linked from it != the source given in
121 -S/--source-and-binary ignore.
123 o lauren sucks; she should a) only spam d-i for sourceful
124 rejections, b) sort stuff so she rejects sourceful stuff first. the
125 non-sourceful should probably get a form mail, c) automate the
126 non-sourceful stuff (see b).
128 o jennifer should do q-d stuff for faster AA [ryan]
130 o split the morgue into source and binary so binaries can be purged first!
132 o per-architecture priorities for things like different arch'es
133 gcc's, silly BSD libftw, palo, etc.
135 o use postgres 7.2's built-in stat features to figure out how indices are used etc.
137 o neve shouldn't be using location, she should run down suites instead
139 o halle needs to know about udebs
141 o by default hamstring katie's mail sending so that she won't send
142 anything until someone edits a script; she's been used far too
143 much to send spam atm :(
145 o $ftpdir/indices isn't created by rose because it's not in katie.conf
147 o sanity check depends/recommends/suggests too? in fact for any
150 [minor] kelly's copychanges, copykatie handling sucks, the per-suite
151 thing is static for all packages, so work out in advance dummy.
153 [madison] # filenames ?
154 [madison] # maintainer, component, install date (source only?), fingerprint?
156 o UrgencyLog stuff should minimize it's bombing out(?)
157 o Log stuff should open the log file
159 o helena should footnote the actual notes, and also * the versions
160 with notes so we can see new versions since being noted...
162 o helena should have alternative sorting options, including reverse
163 and without or without differentiaion.
165 o julia should sync debadmin and ftpmaster (?)
167 o <drow> Can't read file.:
168 /org/security.debian.org/queue/accepted/accepted/apache-perl_1.3.9-14.1-1.21.20000309-1_sparc.katie.
169 You assume that the filenames are relative to accepted/, might want
172 o <neuro> the orig was in NEW, the changes that caused it to be NEW
173 were pulled out in -2, and we end up with no orig in the archive
176 o SecurityAcceptedAutoBuild doesn't handle the case of foo_3.3woody1
177 with a new .orig.tar.gz followed by a foo_3.3potato1 with the same
178 .orig.tar.gz; jennifer sees it and copes, but the AA code doesn't
179 and can't really easily know so the potato AA dir is left with no
180 .orig.tar.gz copy. doh.
182 o orig.tar.gz in accepted not handled properly (?)
184 o amber doesn't include .orig.tar.gz but it should
186 o permissions (paranoia, group write, etc.) configurability and overhaul
188 o remember duplicate copyrights in lisaand skip them, per package
190 o <M>ove option for lisa byhand proecessing
192 o rene could do with overrides
194 o db_access.get_location_id should handle the lack of archive_id properly
196 o the whole versioncmp thing should be documented
198 o lisa doesn't do the right thing with -2 and -1 uploads, as you can
199 end up with the .orig.tar.gz not in the pool
201 o lisa exits if you check twice (aj)
203 o lisa doesn't trap signals from fernanda properly
205 o queued and/or perl on sparc stable sucks - reimplement it.
207 o aj's bin nmu changes
210 * priority >> optional
212 * build-depends wrong (via andrea)
215 * notification/stats to admin daily
216 o trap fernanda exiting
217 o distinguish binary only versus others (neuro)
219 o cache changes parsed from ordering (careful tho: would be caching
220 .changes from world writable incoming, not holding)
222 o katie doesn't recognise binonlyNMUs correctly in terms of telling
223 who their source is; source-must-exist does, but the info is not
226 o Fix BTS vs. katie sync issues by queueing(via BSMTP) BTS mail so
227 that it can be released on deman (e.g. ETRN to exim).
229 o maintainers file needs overrides
231 [ change override.maintainer to override.maintainer-from +
232 override.maintainer-to and have them reference the maintainers
233 table. Then fix charisma to use them and write some scripting
234 to handle the Santiago situation. ]
236 o Validate Depends (et al.) [it should match \(\s*(<<|<|<=|=|>=|>|>>)\s*<VERSIONREGEXP>\)]
238 o Clean up DONE; archive to tar file every 2 weeks, update tar tvzf INDEX file.
240 o testing-updates suite: if binary-only and version << version in
241 unstable and source-ver ~= source-ver in testing; then map
242 unstable -> testing-updates ?
244 o hooks or configurability for debian specific checks (e.g. check_urgency, auto-building support)
246 o morgue needs auto-cleaning (?)
248 o saffron: two modes, all included, seperate
249 o saffron: add non-US
250 o saffron: add ability to control components, architectures, archives, suites
251 o saffron: add key to expand header
253 ================================================================================
258 o change utils.copy to try rename() first
260 o [hard, long term] unchecked -> accepted should go into the db, not
261 a suite, but similar. this would allow katie to get even faster,
262 make madison more useful, decomplexify specialacceptedautobuild
263 and generally be more sane. may even be helpful to have e.g. new
264 in the DB, so that we avoid corner cases like the .orig.tar.gz
265 disappearing 'cos the package has been entirely removed but was
266 still on stayofexecution when it entered new.
268 o Logging [mostly done] (todo: rhona (hard), .. ?)
270 o jennifer: the tar extractor class doesn't need to be redone for each package
272 o reverse of source-must-exist; i.e. binary-for-source-must-not-exist
273 o REJECT reminders in shania.
274 o fernanda should check for conflicts and warn about them visavis priority [rmurray]
275 o store a list of removed/files versions; also compare against them.
276 [but be careful about scalability]
278 o fernanda: print_copyright should be a lot more intelligent
279 @ handle copyright.gz
280 @ handle copyright.ja and copyright
281 @ handle (detect at least) symlinks to another package's doc directory
282 @ handle and/or fall back on source files (?)
284 o To incorporate from utils:
287 o auto-purge out-of-date stuff from non-free/contrib so that testing and stuff works
288 o doogie's binary -> source index
289 o jt's web stuff, matt's changelog stuff (overlap)
291 o [Hard] Need to merge non-non-US and non-US DBs.
293 o experimental needs to auto clean (relative to unstable) [partial: rene warns about this]
295 o Do a checkpc(1)-a-like which sanitizes a config files.
296 o fix parse_changes()/build_file_list() to sanity check filenames
297 o saftey check and/or rename debs so they match what they should be
300 o Need to optimize all the queries by using EXAMINE and building some INDEXs.
301 [postgresql 7.2 will help here]
302 o Need to enclose all the setting SQL stuff in transactions (mostly done).
303 o Need to finish alyson (a way to sync katie.conf and the DB)
304 o Need the ability to rebuild all other tables from dists _or_ pools (in the event of disaster) (?)
305 o Make the --help and --version options do stuff for all scripts
307 o charisma can't handle whitespace-only lines (for the moment, this is feature)
309 o generic way of saying isabinary and isadsc. (?)
311 o s/distribution/suite/g
314 @ weekly postins to d-c (?)
315 @ backup of report (?)
316 @ backup of changes.tgz (?)
318 o --help doesn't work without /etc/katie/katie.conf (or similar) at
321 o rename andrea (clashes with existing andrea)...
325 o interrupting of stracing jennifer causes exceptions errors from apt_inst calls
326 o dependency checking (esp. stable) (partially done)
327 o override checks sucks; it needs to track changes made by the
328 maintainer and pass them onto ftpmaster instead of warning the
330 o need to do proper rfc822 escaping of from lines (as opposed to s/\.//g)
331 o Revisit linking of binary->source in install() in katie.
332 o Fix component handling in overrides (aj)
333 o Fix lack of entires in source overrides (aj)
334 o direport misreports things as section 'devel' (? we don't use direport)
335 o vrfy check of every Maintainer+Changed-By address; valid for 3 months.
336 o binary-all should be done on a per-source, per-architecture package
337 basis to avoid, e.g. the perl-modules problem.
338 o a source-missing-diff check: if the version has a - in it, and it
339 is sourceful, it needs orig and diff, e.g. if someone uploads
340 esound_0.2.22-6, and it is sourceful, and there is no diff ->
341 REJECT (version has a dash, therefore not debian native.)
342 o check linking of .tar.gz's to .dsc's.. see proftpd 1.2.1 as an example
343 o archive needs md5sum'ed regularly, but takes too long to do all
344 in one go; make progressive or weekly.
345 o katie/jenna/rhona/whatever needs to clear out .changes
346 files from p-u when removing stuff superseded by newer versions.
347 [but for now we have halle]
348 o test sig checking stuff in test/ (stupid thing is not modularized due to global abuse)
349 o when encountering suspicous things (e.g. file tainting) do something more drastic
353 o suite mapping and component mapping are parsed per changes file,
354 they should probably be stored in a dictionary created at startup.
355 o don't stat/md5sum files you have entries for in the DB, moron
356 boy (Katie.check_source_blah_blah)
357 o promote changes["changes"] to mandatory in katie.py(dump_vars)
358 after a month or so (or all .katie files contain in the queue
360 o melanie should behave better with -a and without -b; see
361 gcc-defaults removal for an example.
362 o Reject on misconfigured kernel-package uploads
363 o utils.extract_component_from_section: main/utils -> main/utils, main rather than utils, main
364 o Fix jennier to warn if run when not in incoming or p-u
365 o katie should validate multi-suite uploads; only possible valid one
367 o cron.daily* should change umask (aj sucks)
368 o Rene doesn't look at debian-installer but should.
369 o Rene needs to check for binary-less source packages.
370 o Rene could accept a suite argument (?)
371 o byhand stuff should send notification
372 o catherine should udpate db; move files, not the other way around [neuro]
373 o melanie should update the stable changelog [joey]
378 o drop rather dubious currval stuff (?)
379 o rationalize os.path.join() usage
380 o Rene also doesn't seem to warn about missing binary packages (??)
381 o logging: hostname + pid ?
382 o ANAIS should be done in katie (?)
383 o Add an 'add' ability to melanie (? separate prog maybe)
384 o Replicate old dinstall report stuff (? needed ?)
385 o Handle the case of 1:1.1 which would overwrite 1.1 (?)
386 o maybe drop -r/--regex in madison, make it the default and
387 implement -e/--exact (a la joey's "elmo")
388 o dsc files are not checked for existence/perms (only an issue if
389 they're in the .dsc, but not the .changes.. possible?)
393 o db_access' get_files needs to use exceptions not this None, > 0, < 0 return val BS (?)
394 o The untouchable flag doesn't stop new packages being added to ``untouchable'' suites
396 ================================================================================
401 o Fix stuff to look in sensible places for libs and config file in debian package (?)
403 ================================================================================
406 -----------------------------------------------------------------------------
438 ================================================================================
443 | <mdz_> SirDibos: that sentence sounds like it wants to be a bug report when it grows up
445 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
447 | From: Andrew Morton <akpm@osdl.org>
448 | Subject: Re: Linux 2.6.0-test1 Ext3 Ooops. Reboot needed.
449 | To: Ricardo Galli <gallir@uib.es>
450 | Cc: linux-kernel@vger.kernel.org
451 | Date: Fri, 18 Jul 2003 14:27:20 -0700
453 | Ricardo Galli <gallir@uib.es> wrote:
455 | > "File alteration monitor", from Debian.
459 | > $ apt-cache show fam
461 | I was attacked by dselect as a small child and have since avoided debian.
462 | Is there a tarball anywhere?
464 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
466 | From: Bob Hilliard <hilliard@debian.org>
468 | In my experience, James has been very responsive, albeit not
469 | verbose, to reasonable questions/requests that don't start out saying
470 | "James is a bum - throw him out".
472 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
474 | <eigood> Kamion: are you too busy to look at my generic
475 | include/exclude stuff for the bts yet?
476 | <Kamion> eigood: expect me to be busy for about the next week at this
478 | <eigood> my %field_match = (
479 | <eigood> 'subject' => \&contains_field_match,
480 | <eigood> 'severity' => \&exact_field_match,
481 | <eigood> that's how it works, basically
482 | <eigood> I'm a big fan of callbacks
484 | <eigood> Kamion: how do you feel about having
485 | per-bug/per-package/per-source notes support in the bts?
486 | <Kamion> eigood: as I said five minutes ago, I really don't have time
487 | to think about it right now, sorry
488 | <Kamion> here, maybe it would be clearer if I /part
489 | <-- Kamion (~cjwatson@host81-129-36-235.in-addr.btopenworld.com) has left #debian-devel (too busy. no, really.)
490 | <eigood> no need to be hostile
491 | <Joy> eigood: he told you he's too busy and you kept bugging him. take
494 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
496 <mstone> bwahahaha. Dear "security@debian.org" Thank you for your
497 email about "[SECURITY] [DSA-403-1] userland can access Linux
498 kernel memory" ...I need to filter out spam... To send email to
499 vhs@flexdesign.com please put "ducks" anywhere on your subject
500 line. ...Thanks, Bob...
501 <mstone> I'll be sure to do that...
503 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
505 <drow> Hmm, that was a nice short bug report.
506 <drow> to submit@: "strdup(NULL) segfaults" to -done@: "Yes, go away"
508 <Kamion> how did he pass T&S? sheer bloody-mindedness?
510 <drow> Good attention to detail?
511 <drow> Masking of psychopathic tendencies?
514 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
516 <DanielS> the people love me
519 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
521 test.c:5: `long long long' is too long for GCC
523 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
525 http://yro.slashdot.org/comments.pl?sid=91696&cid=7890274
527 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
530 <Joy> i accidentally banned all mails to the bts that had 'ossi' in them
533 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
535 <http://www.livejournal.com/users/mjg59/2003/12/24/>
537 Wednesday, December 24th, 2003
541 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).
543 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.
545 3) Simple maths suggests that if you have a 128MB DIMM with 4 chips on it, they are likely to be 256MBit parts.
547 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.
557 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
559 <http://www.livejournal.com/users/mjg59/2003/11/12/>
561 Wednesday, November 12th, 2003
563 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.
565 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
567 <http://www.livejournal.com/users/mjg59/2003/11/03/>
569 Monday, November 3rd, 2003
571 Hint to people attempting to sell things online:
573 DON'T PUT http://172.16.100.107/ IN YOUR URLS, YOU INCOMPETENT FUCKMONKEYS
575 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
577 | priviledged positions? What privilege? The honour of working harder
578 | than most people for absolutely no recognition?
580 Manoj Srivastava <srivasta@debian.org> in <87lln8aqfm.fsf@glaurung.internal.golden-gryphon.com>
582 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
584 <elmo_h> you could just r00t klecker through [...] and do it yourself
586 <mdz> I think there's a bit in the DMUP about that
588 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
590 <Yoe> well, thing is, he doesn't seem to understand you usually don't
591 have the time to give everyone status updates when a fly moves a
594 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
598 The cops arrest YOU for not showing papers. Wait, I didn't have to
599 reverse it this time, what's going on?
601 http://slashdot.org/comments.pl?sid=97501&cid=8334726
603 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
605 <infinity> <shrug>... Messaging IRCops isn't the end of the world,
606 unless its "/msg ircop I fucked your wife."
608 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
610 <aj> ooo, elmo has "special powers"
611 <neuro> ooo, does he have lasers that shoot out of his eyes?
613 <aj> maybe he can turn invisible? that'd sure help with improved transparency!
615 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
617 | From: Andrew Morton <akpm@osdl.org>
618 | Subject: Re: [PATCH] Compile kernel with GCC-3.5 and without regparm
619 | To: "Art Haas" <ahaas@airmail.net>
620 | Cc: linux-kernel@vger.kernel.org
621 | Date: Tue, 2 Mar 2004 16:59:28 -0800
622 | X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i586-pc-linux-gnu)
624 | "Art Haas" <ahaas@airmail.net> wrote:
626 | > I tried to build the kernel with my CVS GCC-3.5 compiler today, and had
627 | > all sorts of failures about prototypes not matching.
629 | -mm is where the gcc-3.5 action is. There seems to be a bit of an arms
630 | race going on wherein the gcc developers are trying to break the kernel
631 | build faster than I and others can fix it.
633 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
635 (Note that the above is a gross oversimplification, and ignores issues
636 including but not necessarily limited to subarchitectures, and quality
637 of hardware coverage within certian architectures. It contains forward
638 looking statements, and may cause cancer in lab animals.)
640 Joey Hess in <20040317065216.GA29816@kitenet.net>
642 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
644 <jdub> now there's a thought
645 <jdub> DD trading cards
646 <mdz> official joeyh action figure, with rapid-fire upload action
647 <jdub> lamont with pump-action NMU flame-thrower!
649 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%