/srv/irclogs.ubuntu.com/2011/02/07/#ubuntu-meeting.txt

=== davidm_ is now known as Guest27591
=== davidm_ is now known as Guest18305
=== Ursinha-afk is now known as Ursinha
=== Guest14562 is now known as ogra
=== bilalakhtar_ is now known as cdbs
=== bilalakhtar_ is now known as cdbs
bbgollihey people, who should I contact if my @ubuntu email not be created in 7 days?11:51
bbgolliany chance?11:52
Tm_Tbbgolli: #canonical-sysadmin might be the first stop11:53
bbgolliTM_T: I could never get an answer from their channel!11:54
Tm_Tbbgolli: patience is a virtue; also follow the instructions in the channel topic11:54
bbgolliok thnx11:55
bbgollilet me try11:55
=== davidm_ is now known as Guest99521
=== yofel_ is now known as yofel
=== dholbach_ is now known as dholbach
=== oubiwann is now known as oubiwann_
=== Quintasan_ is now known as Quintasan
=== Ursinha is now known as Ursinha-lunch
* skaet waves sconklin15:56
sconklino/15:56
zulhi15:57
skaethi zul,  pitti15:57
pittihey skaet15:57
pittiskaet: FYI, I don't have that much time today, just 30 mins15:57
* marjo waves15:58
skaetpitti,  thanks for letting know,  will see if I can get a kernel style efficient meeting.15:58
skaet:)15:58
skaethi marjo15:58
skaethttps://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-02-07-SR15:58
marjoskaet: i like the goal of "kernel style efficient meeting"15:58
skaetheh15:59
skaetto aid the efficiency,   agenda is in the link I just posted.15:59
skaetwill repreat it for the minutes, but feel free to look now ;)15:59
skaetokie,  time to start I think16:00
skaet#startmeeting16:00
MootBotMeeting started at 10:00. The chair is skaet.16:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:00
skaetAgenda can be found:16:00
skaet[LINK]https://wiki.ubuntu.com/ReleaseTeam/Meeting/StableReleaseAgenda16:00
MootBotLINK received: https://wiki.ubuntu.com/ReleaseTeam/Meeting/StableReleaseAgenda16:00
skaetReminder, please follow the convention  of using ".." on a separate line when you've finished typing.    Also, If someone wants to comment on the last point, please "o/", so we know to wait.16:00
skaetFocus for this week is 10.04.2.16:00
skaet[TOPIC] 10.04.216:01
MootBotNew Topic:  10.04.216:01
skaetpitti,  2 milestoned bugs left - any update on them?16:01
pittiskaet: I just moved the desktopcouch one which newly appeared on the 10.04.2 list to .316:02
skaetpitti,  thanks.16:02
pittia year after release it can't be that urgent to re-do all the cert and other validation16:02
pittiwhat's the other one?16:02
skaetfoundations one that's been on the list a while.16:02
skaetsee on agenda.16:02
pittihttps://launchpad.net/ubuntu/+milestone/ubuntu-10.04.2 has quite a bit more, so it's a bit hard to see16:03
skaet635273:Building debs with SWIG libraries do not work16:03
* skaet was just focusing on the high/critical 16:03
pittithis doesn't look like a deal-breaker for .2 at all16:03
pittiI think we should just move it16:03
skaetfair enough,  will confirm with cjwatson, but lets assume that's the case.16:04
skaetwhat is the update on the language packs?   which ones landed?16:04
pittiFTR, I'm still wrestling with langpacks, I have build take #4 running right now16:04
pittiskaet: we'll land all of them in -proposed, and then quick-verify the ones that are shipped on the images16:04
pittion desktops, anyway (not DVDs, as they probably ship all of them)16:05
pittiI hope I can get them uploaded to -proposed within 2 hours now16:05
pittiI'll coordinate testing handover with dpm16:05
pittibut if anything should go wrong, we just use what we have now16:06
skaetpitti,  sounds good.16:06
skaet..?16:06
* skaet wondering if pitti has anything else to add or is done, before moving on?16:08
pitti..16:08
pittisorry16:08
skaet:)16:08
skaetnp16:08
skaetara,  how are we looking on HW cert?16:08
ara* Almost all the servers and desktops are already covered. No regressions found so far. \o/16:08
ara* This week the scope is testing laptops and netbooks and finishing the remaining desktops and servers.16:08
araWe are on track to finish on time before Thursday.16:08
ara..16:09
skaetara,  thanks!  very good news.16:09
skaetany questions for ara?16:09
marjoara: are there specific things you're depending on, or are all your dependencies ok?16:10
aramarjo, everything is OK16:10
marjoara: in other words, there are no blockers for hw cert, right?16:10
arano :)16:10
marjoara: great to hear16:10
skaetmarjo, how are things looking from your side?16:11
marjoskaet: this week we're doing the kernel/security testing16:11
marjoand for 10.04.2, jibel has  started syncing images and will do upgrade testing this week.16:12
marjo..16:12
skaetmarjo,  sounds good.   encourage jibel to flag early if any issues show up with the upgrade testing ;)16:12
marjoskaet: is there time today to discuss "tweaks to SRU kernel process"?16:12
skaetmarjo,  after 10.04.2 - we'll go on to SRU16:13
jibelskaet, I will :-)16:13
skaetthanks jibel16:13
marjoskaet: thx much!16:13
skaetpitti,  final images will be cut on Friday or Monday?16:13
pittican we do the final validation if we do them on Monday?16:13
pittiwould give us a tad more time for the langpacks16:14
pittibut if Friday would be better, that works, too16:14
skaetpitti,  suspect ara and jibel would prefer friday if at all possible,  so less of a scramble next week.16:14
skaetara, jibel - ?16:15
araskaet, I don't have a preference16:15
jibelskaet, I'm fine with both16:15
marjopitti: what happens if you don't get the "tad more time for the langpacks" what's the downside risk?16:15
pittimarjo: no risk involved; the less time we have, the fewer langpacks will make it to -updates, but no other harm done16:16
skaetok16:16
pittiwe don't depend on these, they would just be a "nice to have"16:16
marjopitti: understood; i like plans w/ "no risk involved" :)16:16
marjoskaet: i would say let's go for Friday final image, ok?16:17
pittiack16:17
marjoto avoid the scrambling16:17
marjopitti: thx much!16:17
skaetpitti,  if langpaks are looking reasonable, cut the images on Friday and broadcast widely then.  If langpaks are problematic we can discuss.16:17
pittibah, they just failed again; firefox translations are broken16:18
skaetwe'll use u-release for discussions.16:18
marjopitti: will the initial langpacks include the ones used for the recent Qin image?16:18
pittiQin?16:19
skaetQin - chinese image16:20
skaetmarjo, wasn't that a maverick one?16:20
marjoskaet: oh sorry16:20
pittiI think so16:20
skaetnp16:20
skaetany other questions about 10.04.2?16:20
pittimarjo: but it only takes what launchpad translations has, no other sources16:20
marjopitti: then we're ok16:21
pittiso if the chinese edition strings are on launchpad, it will be taken from langpack-o-matic16:21
* skaet keeps fingers crossed its only langpacks that are problematic for 10.04.216:21
skaetok,  moving on..16:21
skaet[TOPIC] SRU updates16:21
MootBotNew Topic:  SRU updates16:21
skaetsconklin - what's happening with the kernels?16:22
sconklin|16:22
sconklin| Latest Lucid -proposed is 2.6.32-29.5716:22
sconklin| Call for verification went out on Feb 4th16:22
sconklin|16:22
sconklin| Latest Maverick -proposed is 2.6.35-26.4616:22
sconklin| Call for verification went out Feb 1st16:22
sconklin|16:22
sconklin| These were both copied out to -proposed last week.16:22
sconklin|16:22
sconklin| The status page with tracking bugs is here.16:22
sconklin| Our tools will need changes to accomodate16:22
sconklin| the ARM based kernels, so ignore all the information16:22
sconklin| on that page for ARM kernels.16:22
sconklin|16:22
sconklinI got throttled, hold on16:23
sconklin|16:23
sconklin| https://kernel-tools.canonical.com/srus.html16:23
sconklin|16:23
sconklin..16:23
skaetwhat are the tracking bug numbers for maverick, lucid?16:23
sconklinthey are in the page I just linked16:23
skaetthanks16:24
skaetany questions for sconklin?16:24
arao/16:24
skaetgo ara16:25
araAs we said, we were no going to be able to test SRUs this week. What is going to happen, then?16:25
araa new kernel is going to be uploaded next week?16:25
sconklinWhatever is done will just wait in the queue until you are able to test16:25
araOK16:26
marjosconklin: does that mean QA team should hold off also?16:26
sconklinWe may upload new kernels to the PPA, but they will not be copied into -proposed until the ones in -proposed are published to updates16:26
marjosconklin: or keep going w/ regression testing starting today?16:26
sconklinI thought that you were unable to do regression testing. Whether you can test or not and when cert can test will determine what we do next.16:27
marjosconklin: we can do "regression testing" this week, since alpha2 is done16:28
sconklinIf there will be no testing in the next week, we can just roll a new version to -proposed, and you can test that after a week in verification.16:28
sconklinif Cert is blocked for another week, then it probably makes sense for us to publish new -proposed, and take all the existing verifications as done16:29
marjojibel: any suggestions?16:29
skaetmarjo,  thinking in dallas, was that this was opportunity to catch up on hardy and karmic.16:29
sconklinskaet: catch up meaning what?16:29
skaetsconklin,  run the regression testing16:30
sconklinextra regression testing will never hurt, even if the tested versions are superseded in -proposed and not ultimately released16:30
skaetsconklin,  was refering to hardy & karmic16:31
skaet?16:31
sconklinthat statement applied to every series16:31
skaetheh16:31
skaet:)16:31
sconklinapplies16:31
sconklinbut - in particular, we are concerned about server and virt testing for hardy in this and the next release16:32
skaetmarjo, jibel - ok to look at hardy, karmic this week?   then back into the regular pattern after 10.04.2 comes out.16:32
sconklin(probably) for the next because there are some more rather invasive patches in the queue but they haven't been finalized16:32
sconklinshould good to me16:33
marjo skaet: ok, will do16:33
* pitti waves, need to leave16:33
sconkliner . . . sounds good16:33
* skaet thanks pitti16:33
skaetsconklin,  er... ?16:33
skaethave I misunderstood/overlooked something?16:34
sconklinsounds good to me to test Hardy and Karmic16:34
sconklin..16:34
skaetara - any updates/questions?16:35
araskaet, not from me16:35
jibelso, on the QA side the plan is to do regression testing on Karmic and Hardy this week, then what's in -proposed for maverick and lucid after 10.04.2 is out ?16:35
skaetjibel,  yup,  that's my understanding16:36
marjojibel: yup, that's my understanding16:36
jibelokay. thanks16:36
arathe certification team is not planning on testing until the week 19, as marked in:16:36
arahttps://wiki.ubuntu.com/NattyReleaseInterlock16:36
skaetara,  yup.  :)16:36
sconklinwith the understanding that we may roll out a new -propsed for lucid and maverick before testing gets to it16:36
skaetsconklin,  ack.16:37
marjosconklin: ack16:37
* skaet is doing a good snap set with marjo. ;)16:37
skaetany other questions about SRU updates?16:37
skaetmarjo did you want to talk about tweaks?16:38
marjoskaet: thx16:38
marjohi folks16:38
marjoi have a few simple tweaks and suggestions for the Kernel SRU process16:38
marjo1. I suggest that this be an agenda item for the SRU & LTS meeting, and make sure HW Cert team raise issues early. I've already asked Kate to include it.16:39
marjo2. Ensure all critical and high importance bugs are verified in a timely manner. If not, Jean-Baptiste or his backup will perform the testing.16:39
marjo3. Jean-Baptiste will specifically ask at the meeting if there are specific bugs that need verification that aren't being done by the bug reporter. If necessary, a QA team member will do the verification. If not able (e.g. lack of specific HW), will do more calls for testing and nag the bug reporter again.16:40
marjo4. Set up separate SRU verification program, for big packages like eglibc, python, X. As you know, we've done that before for mesa.16:40
marjo..16:40
marjotoo bad pitti's not here...16:40
sconklinfor 3, who will do the tracking and asking?16:41
marjosconklin: by default, jibel, but we don't want to duplicate efforts already in place by pitti & sconklin16:41
skaetmarjo,  yeah,  we need to take this suggestion up with with pitti off line as well.16:42
sconklinmarjo, so are you proposing that someone from QA begin to track all the bugs requiring verification?16:42
marjosconklin: i'm trying to avoid the last minute scrambling to do fix verification when bug reporters don't do them16:42
pittistill catching up on backscroll, but only 1/4 brain here16:43
marjosconklin: no, we just want to get heads up on those that are not getting verified in a timely manner16:43
sconklinHas there been a problem with this? We have had almost 100% of verifications done quickly for the last few cycles16:43
sconklinAnd has that impacted QA or cert?16:43
pittialso, the kernel is really quite special here16:43
pittiwe just need a large amount of testing there because it changes so much16:43
bjfmarjo, are you trying to solve a real problem today or anticipating an issue ?16:43
pittiwe don't allow these kind of changes in any other package (like in X.org)16:43
marjobjf: i'm trying to head off the cases where bug reporter doesn't do verification, so someone (QA team) has to try16:44
skaetsconklin, marjo - tags of verification needed can be surveyed to figure out which are outstanding,  and then look at high/critical.16:44
marjoand we want to know ASAP16:44
sconklinmarjo: How often has this happened? I wasn't aware that this was happening16:45
marjoskaet: yes, that's one way to implement this16:45
bjfmarjo, we have a clear policy on that, if it's not verified by the reporter, we revert the patch16:45
skaetsconklin,  bjf - outside the kernel,  there are some good fixes getting no love, since the reporter is the one that fixed it.16:45
marjobjf: ok, so maybe these don't apply to kernel, because it's more well behaved16:46
sconklinoh, sorry. I'm in my kernel bubble16:46
marjosconklin: yes, you are :)16:46
skaet[LINK] http://people.canonical.com/~ubuntu-archive/pending-sru.html16:46
MootBotLINK received:  http://people.canonical.com/~ubuntu-archive/pending-sru.html16:46
sconklinwell, you said that these were kernel SRU tweaks, . . .16:47
marjosconklin: yes, i did ..16:47
sconklinHave you been having to do verification for any kernel bugs?16:47
marjosconklin: would you say that this is NOT a problem for the kernel case16:47
marjo?16:48
marjosconklin: in general, we (QA team) try to verify fixes if the bug reporter doesn't16:49
sconklinit's not a problem because if people don't test their changed we revert them. I know that some people have had to scramble for testing because they lacked hardware, but I didn't know that it was falling on your team. If it is, we'll look at it16:49
marjobut only if we have the HW, resources, etc.16:49
marjowe try to help...16:49
marjosconklin: thx much16:49
skaetmarjo, sconlin,  thanks.16:50
sconklinmarjo: ok, that sounds great - and the best way to determine what needs verification is just to look at our sru status page and see what's not verified16:50
marjoskaet: so i think that's it from me16:50
victorpmarjo for #1 could you give an example when hw cert have not raised an issue early?16:50
sconklinIf you can verify fixes and save us the pain of reverting and get good fixes out, I'm all for that16:50
marjovictorp: remember ara had to raise the issue re: eglibc? i think you and i agree this should have been caught earlier16:51
marjovictorp: that's why i'm making these suggestions16:51
marjoso, hw cert doesn't have to scramble16:51
marjosconklin: ack16:52
victorpyes, but couldnt possibly find it earlier because we are not involve in it16:52
marjovictorp: we know16:52
victorpbasically QA has to find it earliear so it is not up to hw cert to find it16:52
marjovictorp: we know16:52
marjovictorp: we're trying to help you (HW cert)16:53
victorpmarjo, great16:53
marjovictorp: thx!16:53
victorpin that case you may rephrase the problem statement16:53
marjoskaet: thx, that's it from me16:53
skaetokie,  thanks.16:53
victorpand it will help every one if we get it right not just he cert16:53
victorphw cert16:53
marjovictorp: ack16:53
skaetbefore meeting ends... any input from security,  OEM,  support teams?   any escalations?16:54
* skaet looks around?16:54
skaetany other questions?16:55
skaetgoing once16:55
skaetgoing twice16:55
skaet#endmeeting16:55
MootBotMeeting finished at 10:55.16:55
marjothx skaet!16:55
sconklinthanks!16:55
skaetthanks marjo, victorp, sconklin, bjf, ara, pitti16:56
arathanks skaet!16:56
victorpskaet -thanks16:56
=== Ursinha-lunch is now known as Ursinha
=== skaet is now known as skaet_afk
jdstrando/18:00
mdeslaurhi!18:00
jdstrandlet's wait a couple of minutes for sbeattie, kees and jjohansen18:01
sbeattiehey18:01
jjohanseno/18:02
kees\o18:02
jdstrand\o/18:02
jdstrandalrighty, let's get started18:02
jdstrand#startmeeting18:03
MootBotMeeting started at 12:03. The chair is jdstrand.18:03
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:03
jdstrandThe meeting agenda can be found at:18:03
jdstrand[LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting18:03
MootBotLINK received:  https://wiki.ubuntu.com/SecurityTeam/Meeting18:03
jdstrand[TOPIC] Review of any previous action items18:03
MootBotNew Topic:  Review of any previous action items18:03
jdstrandso, for my actions, I:18:03
jdstrandwrote up meeting minutes and submitted to team for review. These can now be found in https://wiki.ubuntu.com/SecurityTeam/Meeting under 'Previous Meetings'18:03
jdstrandadded keyring and apt tests to TODO in the QRT scripts (that was surprisingly easy ;)18:03
jdstrandadded vm-iso work to Roadmap (that too :)18:04
jdstrandfollowed up with skaet on Dapper eol. she is aware. it is currently at 30 days prior to eol. I advised doing a 'heads-up' announcement 90 days before eol for LTS to give LTS users an easier migration path18:04
jdstrandshe thoguht it was a good idea and is taking it to other interested parties18:04
jdstrandso, I think that is it for me...18:04
jdstrandkees: update umt to use update-maintainer. iirc you did that already, right?18:04
keesjdstrand: eek, no, it got lost. will do asap.18:05
jdstrandah, no worries18:06
jdstrandkees: thanks18:06
jdstrandsbeattie: I have you down with 'respin ia32-libs'18:06
sbeattiejdstrand: no progress there.18:06
jdstrandok18:06
jdstrandthose can just carry through then18:06
jdstrand[TOPIC] Weekly stand-up report18:06
MootBotNew Topic:  Weekly stand-up report18:06
jdstrandI guess I'll go first18:06
jdstrandstarted writing aa-disable (based on aa-complain) and I should send that up later today18:07
jdstrandneed to follow up on chromium-browser on armel18:07
jdstrandI published chromium-browser on saturday, but armel mysteriously restarted18:07
jdstrand(thanks Mr Buildd)18:08
jdstrandso I uploaded a no change rebuild18:08
jdstrandfirefox is this week, so I'll be testing that18:08
jdstrandlooking at dbus/apparmor18:08
jdstrandand I'm on triage18:08
kees(jdstrand: okay, update-maintainer done now)18:08
jdstrandkees: thanks18:09
jdstrandkees: you're up18:09
keesokay, I'm on community this week.18:09
keeslast week I spent way too much time working on an embargoed issue, but the maintainer popped up on friday18:10
keesso now we're kind of starting over on how to fix the problem, so that'll probably burn more time this week.18:10
jdstrandheh18:10
keeshopefully I won't need to fight for my %pK patches on lkml this week, as that debate should be over18:10
keesbut it's not in -mm yet18:11
jdstrandnice18:11
keesbut they should be in natty at least.18:11
keesI was going to spend some time updating chroots for debian's release18:11
keesand report /proc DAC bypasses to lkml18:11
keesif by magic I have free time, I wanted to work on gcc testsuite updates for the hardening bits. the other half needs to go upstream.18:12
keesthat's it from me.18:12
jdstrandmdeslaur: do you want to go next?18:13
mdeslaursure18:13
mdeslaurso, I'm currently publishing dovecot updates18:14
mdeslaurlast week took a lot of my time fixing the dovecot test suite18:14
mdeslaurI plan on working on exim4 and fuse next18:14
mdeslauralthough I might wait until the fuse stuff in -proposed goes through first18:15
mdeslauras it's aggravated by installing fuse security updates18:15
mdeslaurand that's it from me18:15
mdeslaursbeattie: you're up18:16
sbeattiemdeslaur: you may need to do some pushing to get fuse through -proposed, but I haven't look at the specific issues.18:16
mdeslauris lucid still frozen?18:16
mdeslaurwhen does it unfreeze?18:16
sbeattieyeah, lucid is still frozen, until 10.04.2 releases.18:16
sbeattieI *think* that's this week, but not sure (need to check the schedule)18:17
jdstrandI thought it released next week18:17
jdstrandwhich is why QA has time this week to QA the kernel security updates18:17
* jdstrand is not sure18:17
sbeattienot sure, either, should have read through the SRU meeting scrollback from this morning.18:18
sbeattieAnyway, I released openjdk and posgresql last week.18:18
sbeattieI was also on community last week, and uploaded twiki and drupal6 to security-proposed.18:19
* jdstrand takes hint from sbeattie and finds "Planned Release Date: February 17, 2011"18:19
sbeattieI got partway through reviewing a patch for cacti, and will finish looking at that this week.18:20
sbeattie(for sponsering)18:20
mdeslaurjdstrand: cool, thanks18:20
sbeattieI think that's all for me.18:21
jdstrandsbeattie: are you carrying over the 2.5.2 and 2.6 snapshots to this week?18:22
jdstrand(apparmor)18:22
sbeattieyes18:22
jdstrandcool18:22
sbeattieyeah, planning on doing a bit of release management there this week.18:22
jdstrandalright, moving on18:23
jdstrand[TOPIC] Miscellaneous18:23
MootBotNew Topic:  Miscellaneous18:23
jdstrandjust a couple of things, no action items unless people get excited about one18:23
jdstrandI've added AppArmor profiles for totem-video-thumbnailer, gnome-thumbnail-font and telepathy backends to the Roadmap since the all could easily handle untrusted content18:23
sbeattieOh cool.18:23
jdstrandI very quickly looked at the apparmor bp, and postponed a couple of things based on the current status. eg, I postponed the techdoc stuff. I think it may be less important now with all the other doc updates in the wiki, but we can discuss that another time18:24
jdstrandjjohansen: I'm curious about 'Merge in parser cleanups' and 'Reduce dfa creation memory use'. both are INPROGRESS. are these actually done (I thought they were)?18:25
jjohansenjdstrand: no, they are works in progress18:25
jjohansenjdstrand: bits and pieces of them are done18:25
jdstrandjjohansen: ok, then the status is correct. thanks18:26
jdstrandthat is all I have. does anyone from the team have anything else to discuss?18:26
jjohansenjdstrand: there are bits and pieces I could start asking for patch reviews on but really they should come as a unit (ie a complete patch set)18:26
jdstrandjjohansen: that is fine. no rush, just curious :)18:27
jjohansenjdstrand: nor will all the cleanups get merged this cycle18:27
jjohansenthere are lots and lots of them18:27
jjohansenbut we will do what we can18:27
keesI have one: we should schedule conference times18:28
jdstrandjjohansen: sure. maybe we could break them up a bit, and then move the ones we know won't hit to future items?18:28
jdstrandkees: yes, I have it on my todo to investigate/ask about that18:28
keesokay, sounds good.18:28
jdstrandjjohansen: it doesn't have to be super detailed, but just so we have a better idea of what will hit and what won't18:29
jjohansenjdstrand: sure18:29
jdstrandjjohansen: in fact, future cleanups could be very general, and we can pull in the specific ones per cycle as work items18:29
jdstrandjjohansen: thanks18:29
jdstrandok, moving on18:30
jdstrand[TOPIC] Questions18:30
MootBotNew Topic:  Questions18:30
jdstranddoes anyone have any other questions or items to discuss?18:30
* jdstrand might change the to Miscellaneous & Questions...18:30
jdstrandalright, thanks everyone!18:31
jdstrand#endmeeting18:31
MootBotMeeting finished at 12:31.18:31
mdeslaurthanks!18:31
sbeattiejdstrand: thanks!18:31
jdstrandsure! :)18:32
keesthanks jdstrand!18:32
=== davidm_ is now known as Guest95278
=== skaet_afk is now known as skaet
Laneyaccount on19:23
Laneyerr you aren't bitlbee19:24
=== davidm is now known as dm_afk
=== fosdemlogger is now known as austrialogger
=== austrialogger is now known as apachelogger
=== oubiwann_ is now known as oubiwann
=== dm_afk is now known as davidm
=== tumbleweed_ is now known as tumbleweed
=== bjf is now known as bjf[afk]
=== Craig_Dem_ is now known as Craig_Dem

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!