[00:32] hello, I cannot commit any changes to my branch hosted at Launchpad anymore [00:33] I always get the following error: No handlers could be found for logger "bzr" [00:33] afterwards bzr hangs forever [00:33] bzr+ssh://glatzor@bazaar.launchpad.net/%7Edisplayconfig-gtk/python-xrandr/main/ [00:34] glatzor: AIUI its actually pushing, unless you have hit ctrl-C, which actually breaks it [00:34] glatzor: or it might be locked [00:34] try sftp [00:35] mwhudson: lifeless: I already made a break-lock [00:35] glatzor: but that's a bit erratic over bzr+ssh too :/ [00:36] this happened after I was asked for my ssh passphrase, but I was to busy to enter it immediately. entering it after some minutes resulted in this situation [00:39] ok, using sftp is a workaround [00:39] thanks [00:49] cprov-out: how long are you gonna be up? [00:50] LaserJock: dunno, 20 minutes or so [00:52] k, trying to get the source [00:54] cprov-out: hmm, where are you getting the source? [00:54] from what's on the PPA? [00:54] LaserJock: http://ppa.launchpad.net/schooltool-owners/ubuntu gutsy [00:55] ok [00:55] well, I found the source that they have on the schootool.org site too [00:57] hmm, that's some lovely packaging [00:58] LaserJock: do you suspect of something in the package itself ? [01:01] good night! [01:03] cprov-out: well, apt has been around for a long time ;-) [01:03] my first guess is always packaging [01:03] cprov-out: have you by chance reproduced it? [01:03] LaserJock: well, it could also be the indexes generated by LP :( [01:04] cprov-out: could be yes [01:04] yes, it's trying to update the package in my machine [01:05] LaserJock: do you know how to make apt *verbose* on its actions ? [01:05] cprov-out: do you think this could possibly be caused by the ogre-model crush? [01:06] like what happens if it gets confused about component? is that a possibility? [01:07] cprov-out: try apt-get -V [01:09] LaserJock: no luck [01:13] cprov-out: I'm trying it now as well [01:22] cprov-out: I just don't know dude [01:22] I don't see anything obvious [01:23] LaserJock: yes, me neither ... better go to bed and try this again tomorrow. [01:23] LaserJock: thanks for the help and g'night. [01:23] cprov-out: yeah, I gotta get home, I'll try to poke it again some and let you know if I figure anything out === cprov-out is now known as cprov-zZz [01:23] LaserJock: great, thank you. [02:21] hi all. i'm getting an error when trying to push something to launchpad via bzr. (http://pastebin.ca/798862) can anyone help? [02:29] j1mc: You can't push over HTTP... [02:30] You need to use sftp or bzr+ssh. [02:31] Fujitsu: here's the command i'm using: bzr push bzr+ssh://jwcampbell@bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-doc/xubuntu-hardy === hexmode` is now known as hexmode [02:32] j1mc, did you do bzr unbind? [02:33] beuno: i tried it. it gave errors, too. might it because i did a lightweight checkout? [02:34] j1mc, let's take this back to #bzr <---- :D [02:34] ok [02:34] j1mc: You'll have to rebind. Just bind to bzr+ssh, etc. [02:35] cprov-zZz: erm, why did i get subscribed to a spec that i cant read? :) [02:37] Fujitsu: pardon me, but how would i rebind? i am new to bzr. [02:37] j1mc, maybe bzr bind bzr+ssh...? [02:38] Hobbsee: because you know if something going on with that something [02:38] LaserJock: eparse? [02:39] beuno: i'll try. thx. [02:39] oh, as in, i'll see when it's all done, or what it's general status is - just not how they're going to do it? [02:39] exactly === ember_ is now known as ember [03:00] New bug: #165322 in ubuntu "Launchpad bug reporting needs a 'me too' button (dup-of: 149775)" [Undecided,New] https://launchpad.net/bugs/165322 [06:01] Hello hello [06:01] hello hello [06:01] Shall we have a reviewer meeting? [06:02] lifeless may not be around for the meeting [06:02] hello hello hello [06:02] and I am one handed as I'm eating dinner [06:05] I feel that we've become stalled. [06:05] Shall I run it then? [06:05] jml: go for it! [06:05] = Meeting Starts = [06:06] Welcome to the Launchpad Reviewer meeting! [06:06] * Roll call [06:06] here [06:06] BjornT, jamesh, jtv, lifeless: ping [06:07] hi [06:07] hi [06:07] and that's a quorum [06:07] * Next meeting [06:07] Same time next week, I assume. [06:07] I'm happy to chair. [06:07] * thumper would really like it earlier [06:07] but then we'd have EU problems [06:08] I'll live [06:08] OK. [06:08] Nov 27+7, 0600 UTC [06:08] * Action items [06:08] I see there are two here for me [06:09] jml, create a ReviewerMeetingTemplate wiki page similar to BazaarMeetingTemplate with template for minutes and instructions on preparing the email. [06:09] * [06:09] jml to confirm that SteveA's email about using properties rather than no-arg functions on view classes is in a relevant checklist on wiki [06:09] I'll get to those this week. Sorry about the delay. [06:09] * Queue status [06:09] How are your queues guys? [06:10] I didn't get round to allocating reviews yesterday [06:10] mine is empty [06:10] except for one [06:10] thumper: heh [06:11] jamesh: I see you have a massive branch in your queue [06:11] well, visibly empty, but secretly not [06:11] jml: which one? [06:11] SteveA's queue [06:11] oh, I misread [06:11] oh. SteveA rubberstamped that [06:12] I can't see anything else to comment on here. Let's move on. [06:12] * Mentoring update [06:12] Anyone here a mentor? [06:12] not me [06:13] Moving on. [06:13] * Review process changes [06:13] Were these discussed at last week's meeting? [06:13] * thumper doesn't think so [06:14] I don't feel qualified to chair a discussion on these without knowing what sort of outcome we are expecting from that discussion. [06:15] You've got five seconds to say something :) [06:15] Done. [06:15] * Any other business [06:15] 3 [06:15] 2 [06:15] 1 [06:15] me [06:15] thumper: go [06:16] what to people think about flacoste's idea of team leads not doing on call reviewing? [06:16] BjornT ? [06:17] thumper: it has a practical ring to it. [06:17] i think that's a quite sane idea. we should have enough reviewers to go around anyway, and there's nothing stopping team leads from helping out doing reviews, even though they are not officially on-call [06:17] right, that's generally my thoughts too [06:18] * thumper is done now [06:18] ok. [06:18] Then so am I. [06:18] = Meeting ends = [06:18] I'll talk to Barry to understand the agenda better. [06:18] thanks jml [06:18] thanks jml [06:19] np. [06:30] New bug: #172248 in launchpad "milestone pages should (optionally) hide finished bugs" [Undecided,New] https://launchpad.net/bugs/172248 [07:35] New bug: #172253 in rosetta "Translation overview pages for distro and project should link to filtered PO file pages" [Undecided,New] https://launchpad.net/bugs/172253 [08:15] New bug: #172256 in launchpad "Builds page erroneously reports no packages building" [Undecided,New] https://launchpad.net/bugs/172256 === LaserJock is now known as LaserRock [08:24] morning [08:25] Hi carlos. === \sh_away is now known as \sh === mpt_ is now known as mpt [09:04] mpt: where can I enable the bug tracker for my launchpad project? the option seems to be quite hidden [09:04] glatzor, wow, coincidence [09:04] I'm just right now transcribing one of the user test videos where someone has the same problem [09:05] :) [09:05] So until we fix it, the steps are: (1) tabs > "Overview" (2) Actions > "Change details" (3) scroll down to "Bugs are tracked in: [ ] Launchpad" [09:05] * Fujitsu has helped a few people find that in the past, too. [09:07] mpt: would be nice to have this on the bugs tab [09:07] I think it should be visible directly from the table on the right of the Overview page, and on the Bugs tab, yes [09:07] mpt: thanks. [09:08] mpt: how can I add files to the download section? [09:09] * Fujitsu thinks you need to add a series, then a release, then add files within that release. [09:10] glatzor, what Fujitsu said [09:11] ... which also should be more obvious [09:11] Or perhaps there could be some documentation. [09:11] Preferably both, I guess. [09:12] Writing documentation would be quicker for us. Fixing the dang problem would make it quicker for users. [09:13] Some content in the help tab (that must be a first, except for launchpad-bazaar) of +download might help once Launchpad stops crying wolf. [09:13] We have a plan for the wolf problem [09:14] That is very probably a good thing. [09:14] What are you going to do to it? [09:14] It's not approved yet. Ask me again in two weeks. :-) [09:14] Ah. [10:31] New bug: #172275 in soyuz "vmware-server in feisty-commercial keeps getting reinstalled" [High,New] https://launchpad.net/bugs/172275 [11:06] mwhudson: hi. thanks for fixing the Drupal main branch! Would it be possible to mirror DRUPAL-5 and when it comes (soon), DRUPAL-6 too? [11:07] * mwhudson blinks [11:07] chx: was that me? :) [11:07] mwhudson: I do not know but someone fixed the Drupal branch. [11:07] mwhudson: it stoppped updating I complained here to you, I fild a question on launchpad [11:08] mwhudson: and now, it seems like up to date. [11:08] chx: ok, cool :) [11:08] chx: but in general we only mirror the trunk series of development [11:08] mwhudson: the last commit as of liek ~40 minute ago is not yet mirrored but i guess it will eb soon. i do not know how often the mirror script runs [11:08] mwhudson: fine, fine [11:09] chx: cvs repos get updated every 12 hours by default [11:10] mwhudson: ouch. may I get a speedier update :) ? [11:10] yes, it should be possible [11:11] mwhudson: http://ubuntu.com is Drupal. Does this give us some special position :D ? [11:11] chx: probably :) [11:11] mwhudson: so, every 30 min :) ? [11:12] eh, that's probably a bit too often [11:12] 31 min :D ? [11:12] sure. Hourly? [11:12] the systems that run the imports are pretty heavily loaded [11:12] Whatever works for you, works for me. [11:13] oh, haha [11:13] it is already set to hourly [11:13] really? [11:13] great, great! [11:13] but there are too many jobs being processed currently [11:13] I see. [11:13] which is why it hasn't been updated for over an hour right now [11:14] Would donating help? Do you guys need funding or sabdfl provides practically infinite funds :) ? [11:14] um [11:14] we need more time and less other things to do i guess :) [11:15] we're working hard on a more flexible code import system [11:15] great! we are working hard to provide a better CMS for all of you :) [11:15] that would let us, e.g., give certain jobs higher priority [11:15] chx: not my end of things at all :) [11:15] New bug: #172286 in launchpad-bazaar "timing out a branch puller worker leaves a locked branch" [Undecided,New] https://launchpad.net/bugs/172286 [11:15] chx: but seriously man, cvs? :) === cprov-zZz is now known as cprov [11:16] mwhudson: going over to svn is on the plate for 2.5yrs now [11:16] mwhudson: it looks more realistic after this SoC but it's extremely hard [11:17] mwhudson: we have.... what the stats was... um I remember 5000 projects maintained by 1000 people. [11:17] or something like that. [11:18] i suppose svn would be a bit better ... :) [11:20] yes but what I am saying that we educated a legion of people to use cvs and no matter how easy it is , we will have another set of problems [11:20] we have integrated cvs pretty heavily [11:21] one of the most important parts, as said above, was rewritten in an RCS independent way during SoC with a CVS plugin and the SVN plugin has recently been written [11:21] but it's not easy [11:21] also, believe me I would be happier with bzr or git [11:22] but the lack of integration and fancy GUI shells makes it impossible. Think Tortoise here. [11:23] ah right, that one [11:24] yes, that one [11:24] the problem here is that the people who most understand bzr are the least likely to be using windows :) [11:24] and most happy at the command line [11:24] well there is a tortoisebzr now [11:25] and believe me, the heaviest Drupal guns do not run Windows [11:25] especialyl the early DrupalCons looked like macfests :D [11:26] New bug: #172292 in rosetta "Don't offer Download translations to anonymous users" [Medium,New] https://launchpad.net/bugs/172292 [11:26] still, when nine of us walked into a bar in Barcelona to spend the evening with something good (read core hacking), there were like... what, two PCs, one being mine? Apple hardware does not fit my needs, sorry. [11:26] i'm running gutsy on a macbook [11:26] the wifi is occasionally infuriating but other than that it's a very nice machine [11:27] well, a macbook, from my viewpoint, and especially the macbook pro, is extremely heavy [11:27] and also, very fragile. [11:28] I am running a Panasonic CF-Y5 which is very light and very very durable [11:28] i feel this is getting off topic :) [11:28] it is :) [11:28] so back to RCS... [11:28] You also need the local "whatever RCS" guru [11:28] we have a CVS guru [11:28] we possibly can pull SVN off [11:29] but even if TortoiseBZR matures [11:29] I have no idea who will be the bzr "captain" [11:29] there are a few people using bzr [11:29] but aside from bzr pull -- bzr revert -- bzr diff we do not use bzr really. [11:30] as usual, the challenges are more human resources than technical [11:34] it's hard to change this sort of thing because the costs are immediate and the benefits long term and often a bit vague seeming [11:35] the big problem here is that SVN would solve little at all of our problems [11:35] which are, people have a problem with grasping tags and branches [11:35] what problems does cvs give you? [11:35] ah [11:35] this is hardly cvs specific [11:35] i've never understood branches in cvs :) [11:36] SVN is somewhat easier -- but then again, tags there are highly artifical unless you introduce some commit script nothing stops changing a tag, if i understand correctly === kiko-zzz is now known as kiko [11:50] sky fallen in yet? [11:55] not yet. we're waiting. [11:55] ah. pity [12:04] cprov: when should i hope for an email? [12:06] Hobbsee: ideally soon, but it's unlikely, sorry. BTW, do you have some time to help me to follow the soren's hint on https://bugs.edge.launchpad.net/soyuz/+bug/165230 ? [12:06] Launchpad bug 165230 in soyuz "PPA generates an endlessly upgrading package" [Undecided,In progress] - Assigned to Celso Providelo (cprov) [12:06] cprov: I'm right here, if you need me? [12:08] soren: ahh, good. I wonder how the conflicting binary metadata was generated. Can you explain ? [12:09] cprov: Are the PPA's using apt-ftparchive? [12:09] soren: same bug as partner [12:09] thegodfather: It smeels quite similar, yes. that's how I stumbled upon it. [12:09] i am pretty sure it is [12:09] PPA doesn't use apt-f-a IIRC === Hobbsee_ is now known as Hobbsee [12:10] !primary uses NoMoreFTPArchive, I'm pretty sure. [12:10] +Apt there somewhere. [12:10] cprov: pkg-binarymangler replaces the maintainer, afair. [12:10] soren: let's check the buildlog [12:10] cprov: I suppose it's debatable whether that should even be installed in ppa buildd's. [12:11] * Hobbsee curses hardy [12:11] * soren pats Hobbsee [12:11] * Hobbsee would appreciate it if X did not freeze [12:12] cprov: pkgmaintainermangler: Maintainer field overridden to "Ubuntu Core Developers " [12:13] cprov: Where does NoMoreAPTFTPArchive get its info from? [12:14] soren: when it process the incoming deb control-file [12:14] cprov: -v [12:16] cprov: That doesn't add up, IMO. [12:16] It looks like it's getting the maintainer from the source, not the post-mangling binary. [12:16] cprov: The Packages file does not match the control file from the control.tar.gz in the ar archive. [12:17] Fujitsu: Yeah, but it's got the right Depends.. [12:17] soren: That's true. [12:17] soren: and the difference is only the 'Maintainer' field ? [12:18] cprov: For the package, I looked at, yes. [12:18] cprov: I've reported another similar bug that bigjools is looking at. [12:19] https://bugs.edge.launchpad.net/soyuz/+bug/172275 [12:19] Launchpad bug 172275 in soyuz "vmware-server in feisty-commercial keeps getting reinstalled" [High,New] - Assigned to Julian Edwards (julian-edwards) === meduxa is now known as toscalix [12:22] soren: uhm, the inconsistency source is that we use the Maintainer field set in the source metadata in the index and not the one coming in the binary controlfile [12:22] * Fujitsu headdesks. [12:22] cprov: I see. [12:22] cprov: Ok, that doesn't explain the missing Pre-Depends, though. [12:23] * Fujitsu suspects somebody left that out of the field whitelist... [12:23] soren: 'pre-depends' is not modeled in NoMoreAF [12:24] cprov: It probably should be. [12:24] cprov: EH? [12:24] soren: ok, let's make it a bug. [12:24] should my crack alert be going off? === mrevell is now known as mrevell-lunch [12:28] cprov: is there any visible documentation on NMAFA? either current, or future plans? [12:29] Hobbsee: there is a spec, but it's private. We should indeed cook a public documentation for it [12:30] yay. [12:32] Fujitsu: you know, i really think that cprov should make the use of yada mandatory for packages to build in PPAs. [12:32] YES! [12:33] mutating packaging files would be fun! [12:33] Heh heh heh. [12:33] and oh so much simpler, when there's only one file of importance [12:34] Hobbsee: I have no idea what are you talking about. Can you point me to some doc on this ? [12:34] cprov: you don't want to know, and you want to run away and hide before Fujitsu gets violent === doko_ is now known as doko [12:35] oh my goodness, it's mutated into something mroe evil! [12:35] New bug: #172308 in soyuz "BinaryPackageRelease should store 'Pre-Depends'" [Undecided,New] https://launchpad.net/bugs/172308 [12:35] cprov: yada is one of the most evil of packaging `aids' to ever exist. It mutates control files and such on each build, and was just brought up by myself in #-motu. [12:35] Fujitsu: dude....please file a removal request for it, before it takes over. [12:36] Description: Yet Another Debianisation Aid [12:36] YADA is a Debian packaging helper. It parses a special file, [12:36] debian/packages, in a source package, and generates an appropriate [12:36] debian/rules to control building of the package. [12:36] . [12:36] This package provides YADA script. [12:36] . [12:36] The /usr/bin/yada script can be also copied as source package's debian/yada [12:36] file if this package won't be available on system for package building. [12:36] the latter part is new. [12:36] even purging yada is not enough - you now need to purge all yada-infested files. it's a virus! [12:37] aff .. [12:38] Fujitsu: well, now you're not annoyed at NMAFA, are you? :) [12:38] Hobbsee: Heh. [12:39] cprov: In Soyuz's current state, sources are semi-published on upload, so we sort of have build-from-accepted? [12:40] Fujitsu: we've got binaries in the accepted queue already. unsure if you can see them [12:40] iirc [12:42] Fujitsu: or replace sbuild with checkinstall, if you really want some crack. [13:03] wake up launchpad [13:04] it's sleepy. you should feed it more === mrevell-lunch is now known as mrevell [13:43] cprov, my ppa still hasn't cleared :/ [13:44] PriceChild: the indexes or the pool ? [13:44] well there's nothing on my ~archive page... but it still shows all the source and binaries still there. [13:44] * +archive [13:45] apart from the upload i made last night that you said i should do [13:45] PriceChild: URL ? [13:45] https://edge.launchpad.net/~pricechild/+archive [13:45] New bug: #172320 in rosetta "Empty translations must be always represented with a TranslationMessage without translations" [High,Confirmed] https://launchpad.net/bugs/172320 [13:46] PriceChild: http://ppa.launchpad.net/pricechild/ubuntu/dists/gutsy/main/source/Sources seems to be correct [13:47] cprov, its still rejecting my upload of version 3.4 (different md5sum to original) [13:49] PriceChild: right, it is still published in http://ppa.launchpad.net/pricechild/ubuntu/pool/universe/g/gizmod/ [13:51] So how do we unpublish it? [13:52] "you don't" [13:53] or you madly petition bigjools to code you a way to do it :P [13:55] Hobbsee, I know I can't yet (feature on way?)... but surely there must be a way for them to do it seen as other people have had this fixed for them... [13:57] PriceChild: right, the information I passed you yesterday was inaccurate, gizmod _3.4-0ubuntu1~ppa1 source will be removed after 2007-11-27 17:40:16.293285 UTC, i.e, tonight. It was submitted to the 24 hours quarantine period. [13:58] Great so 3 and a bit hours :) [13:58] Thanks cprov. [13:59] PriceChild: bear in mind that the removal procedure only runs at 3am, you will have to wait a little bit more, sorry. [14:00] cprov: 3am UTC? [14:01] <_MMA_> Sorry. I can imagine this might have been asked a bunch. I cant log in to LP. Is there a issue right now? I cleared cookies and all. [14:01] Hobbsee: yes [14:02] cprov, wait I'm confused then... when you mark something for deletion, It has to wait for at least 24 hours before it is queued for deletion incase I change my mind? [14:04] PriceChild: yes for the first part, but it's not exactly to cover the changing-mind case. [14:05] * Hobbsee wonders if it has then had time to definetly hit the backups [14:05] PriceChild: it's just to allocate in-progress work of new versions possibly depending on what you are removing. [14:09] cprov: which means what, in laymans terms? [14:09] cprov: what difference does it make when you remove it, if other stuff depends on it? [14:09] it's still going to break, no matter when you remove it [14:10] Hobbsee: no, new versions depending on the same orig would hold the file in disk, for instance [14:10] cprov: depending? why? [14:10] oh! [14:11] cprov: so...then you're assuming that the packages will have built within the 24 hours, so then you can remove part of the source? [14:11] I'm not sure if the exactly intent of this feature in the real world, but it's one of the effects it causes [14:11] * Hobbsee thought you removed by entire package, not just a version of a package [14:11] ah so like removing ~ppa1 means it needs to wait 24 incase there's a ~ppa2 scheduled to build? [14:12] cprov: what other things does it cause? [14:12] Hobbsee: gives time for daily backup-procedure [14:13] cprov: which means that data is never removed from LP fully, then - even deleted stuff. [14:13] Hobbsee: but currently it's done hourly ;) [14:13] cprov: what...because LP is likely to fall over more regularly than once a day? :P [14:14] Hobbsee: it will be removed fully when a new sources series is started, so the old orig is not need anymore [14:14] cprov: i dont understand "sources series" [14:14] i've never understood launchpad's series stuff. [14:14] unless it's a form of mozilla-esque [14:14] Hobbsee: versions that share the same upstream source (orig.tar.gz) [14:15] cprov: do you remove by versions of a package, or do you nuke the entire package? [14:15] Hobbsee: by version [14:15] {source,binary}packagerelease [14:16] cprov: right, that explains a bit more... [14:17] * Hobbsee still thinks there's some botched logic there, but it makes somewhat more sense. [14:19] Hobbsee: I believe we could get rid of the quarantine period for PPA deletions. [14:20] cprov: erm...how does soyuz blow up if it's published a source package, but can't find the original tarball to build? [14:21] does sbuild curl up and die, and lock up the builld in question, or? [14:21] * Hobbsee has no running sbuild, so cannot check. [14:21] hang on, i could ssh into a friends machine and check - if i actually knew the runes to call sbuild. [14:23] Hobbsee: builders grab sources directly from librarian, so they won't blow if they are not in the archive. [14:23] cprov: oh, so you're not actually deleting the files (orig.tar.gz, .diff.gz, .dsc) from librarian at all? [14:23] Hobbsee: although we would detect the lack of source when processing the binary (it has never happened, since deletions are done carefully) [14:24] Hobbsee: no, librarian has the *world* and the files are offered via LP UI === cprov is now known as cprov-lunch [14:25] cprov-lunch: so when you're talking about "delete", you actually mean "hiding it from the user, so it appears to be deleted, but isn't" [14:26] * Hobbsee wonders if the buildds then pick it up from librarian or the LP UI, then. [14:26] Hobbsee: well, the immediate deletion result is 'exclude it from the archive indexes' [14:26] if librarian, then surely hiding it on the UI wouldn't help you. [14:26] right, yes [14:26] Hobbsee: later on it will result in remove the file from the archive disk [14:27] cprov-lunch: the archive disk - but never librarian too? [14:27] Hobbsee: exactly, librarian will stored the sources and binaries as long as we think it's useful [14:28] * Hobbsee suddenly is reminded of "google: do no evil" [14:28] or better s\will store\can store [14:28] * Hobbsee checks what the LP privacy policy says about that [14:29] err ... evil word was mentioned, it definitely means "lunch-time" :) [14:29] haha [14:30] cprov-lunch: ah, it is there. "Launchpad retains all data submitted by users permanently. " [14:31] unless it's inappropriate. great. [14:31] ah, yes, and then you use the "delete", which means "hide from view", not delete as in real delete - but never actually say that. [14:32] as it's not mutually exclusive with the "Launchpad retains all data submitted by users permanently. " statement. [14:34] Hobbsee, we sometimes delete porn spam if it's bad porn. [14:34] kiko: this would be covered under the "canonical deems it inappropriate" clause, yes. [14:34] * kiko had a weird dream about porn tonight. yes, insert random quote about porn in dreams and disturbed engineers [14:35] I was at a race conference, having dinner [14:35] and I gave the organizers a DVD to show which was of a race that happened this year [14:35] and it had racing but it then clipped into a porn video much to my chagrin [14:35] now, i wasn't going to say that....but [14:35] heh [14:36] it was horribly embarassing. but nobody but me seemed to care [14:36] maybe they liked it. *shrug* [14:36] maybe it was more interesting than the race :P [14:37] I think it's more an artifact of it being in a dream [14:37] yeah well. you clearly have strange dreams. [14:40] I shouldn't have dinner that late === kiko is now known as kiko-fud === bigjools-afk is now known as bigjools === matsubara is now known as matsubara-lunch [15:27] anyone an idea why antargis-trunk failed importing? === LaserRock is now known as LaserJock === cprov-lunch is now known as cprov [15:57] LaserJock: Hi [15:58] hi mrevell [15:58] Hey LaserJock. Do you have a few minutes to chat about tomorrow's PPA 101 session? [15:58] sure [15:59] anything interesting? [16:00] LaserJock, Hobbsee: I think the most useful thing would be to adopt the same intro section as last time and devote most of the session to Q&A. Would you agree? [16:00] yep [16:01]