/srv/irclogs.ubuntu.com/2009/03/17/#ubuntu-meeting.txt

=== rgreening_ is now known as rgreening
=== Andre_Gondim is now known as Andre_Gondim-afk
=== tuxlinux_ is now known as tuxlinux
=== nijaba` is now known as nijaba
* persia peers about10:01
* Hobbsee throws rotten tomatoes at persia10:01
HobbseeGOTCHA!10:01
* persia applies the handy uncursed towel (P)10:02
Hobbseeer, what are you actually peering about for?10:03
persiaThere was a rumor that the AsiaOceania RMB might meet now, when there might be quorum about.  Given the lack of others, I'm guessing the rumour was unfounded.10:04
persiaAs a result, I expect the meeting will be held later, and don't know if we'll get quorum, as it will be late in Australia.10:04
MaWaLepersia: the meeting is planned fot the 15UTC (on the wiki page)10:07
persiaMaWaLe, Indeed, that's what the wiki page says.  As I said, it was an apparently unfounded rumour.  So, 5 hours from now, I'll peer about again :)10:08
MaWaLehope that it'll be a quorum this time10:09
Technovikingmorning all10:59
dholbachhello10:59
dholbachmdke and Burgundavia are not around and I guess mako is not up yet11:00
dholbach#startmeeting11:01
MootBotMeeting started at 06:01. The chair is dholbach.11:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]11:01
dholbachit seems we have one agenda item today: https://wiki.ubuntu.com/CommunityCouncilAgenda11:02
dholbach[TOPIC] Forums Council Re-Elections and New Members11:02
MootBotNew Topic:  Forums Council Re-Elections and New Members11:02
* dholbach needs a minute or two to get on top of the discussion :)11:02
sabdflarrgh, south african bandwidth11:04
ubuntugeek:)11:05
dholbachso https://wiki.ubuntu.com/CommunityCouncil/Delegation only applies partly, there's no real "team" connected to the "Forums Community"11:05
Technovikingsabdfl: lagging here too, never heard of St. Patick day lag before:)11:05
sabdflusually, post-St Patrick's day lag :-)11:06
jussi01*g*11:07
sabdfldholbach: i thought we agreed to create such a team?11:07
dholbachsabdfl: there's https://launchpad.net/~forum-council/+members but there's no "members through Forum's participation" - I think I recall us saying that we revisit the decision in a few months of time again11:08
dholbachsabdfl: IIRC the IRC and the Forums community did not like the idea much11:08
dholbachTechnoviking would know better than I do :)11:08
sabdflright11:09
sabdfli keep thinking we agreed it, because it's what i wanted, but that's not always true :-)11:09
* dholbach hugs sabdfl :)11:09
Technovikingare you talk about a team for all forums members?11:10
dholbachTechnoviking: ubuntumembers through forums activity11:10
dholbachso in the absence of such a team right now, it'd make sense for all CC members to review the nominations and cast a vote11:10
persiaCould perhaps the polity be all ubuntumembers?  Those inactive in the forums would likely abstain.11:11
sabdfl1i.e., a team of folks who have made significant and sustained contributions to Ubuntu  *in the forums*11:11
nhandlerpersia: That vote wouldn't be able to take place via IRC it would need to be on LP11:12
sabdfl1i don't think there's a *requirement* for voting on LP11:12
sabdfl1if there's an agreed, fair and safe voting mechanism in the forums, or the IRC world, communities can use that11:12
sabdfl1for votes inside that domain, where people are comfortable with those tools11:13
nhandlersabdfl: But if we allow all ubuntumembers to vote, it would be difficult to do it on irc (especially to enforce that only members vote)11:13
persiaAnd the polity needn't necessarily even vote, as long as the right polity is identified/11:13
sabdfl1it's cross-team things that usually need LP11:13
=== sabdfl1 is now known as sabdfl
sabdflsorry, with all the dropping off and reconnecting, i fear i'm not keeping up with the conversation11:14
nhandlerYou didn't miss anything sabdfl11:14
dholbachfor now I think we should decouple the ubuntumembers-through-forums-activity from the new FC members discussion11:16
elmoI agree11:17
TechnovikingI guess first thing is, is the CC ok with the Forums Council expanding to 7 members?11:19
elmoI am11:20
dholbachme too, it is a big responsibility and the FC will definitely benefit from more trusted Forums leader to be on board11:21
dholbachsabdfl?11:22
Technovikingmust have dropped again11:23
dholbachif we don't come to a conclusion in this meeting I'd suggest starting a new thread with all the voting options to the CC and set a cut-off date in 1-2 weeks so everybody has enough time to send in their vote11:26
dholbachthe FC election organisation thread got fairly long already and maybe it wasn't sufficiently clear what was expected of each member11:26
Technovikingdholbach: sounds good11:26
dholbachelmo, sabdfl: does that sound fair to you?11:27
elmodholbach: sounds good to me11:27
TechnovikingI will prepare it11:27
dholbachthanks a lot Technoviking11:27
dholbach[TOPIC] Any other business?11:28
MootBotNew Topic:  Any other business?11:28
persiaI'd just like to thank the CC for continuing the meeting schedule reliably over the past many months, regardless of DST changes, inconveniences of personal schedules, or other matters.11:29
dholbachthanks persia, I'd like to give credit to Claire Newman who reminded me of the meeting dates when I did not think of them. :-)11:29
dholbachok seems we have no other business - thanks everybody11:30
dholbach#endmeeting11:30
MootBotMeeting finished at 06:30.11:30
* dholbach will update the Team Report11:30
Technovikingthanks dholbach11:31
dholbachTechnoviking: thank YOU11:31
sabdflargh. ftr, +111:41
sabdfldholbach: ^ sorry for the lag11:41
dholbachsabdfl: no worries - I think it's good if we get all votes of the CC for such an important decision11:42
sabdflme too11:42
=== Igorots is now known as pyc1
=== pyc1 is now known as Igorots
=== Andre_Gondim-afk is now known as Andre_Gondim
=== zaafouri is now known as zaafouri`
* persia peers about14:54
* MaWaLe hoping that there'll be a quorum14:56
aamachuhi14:56
hito_jphi14:56
Belutzamachu, sorry for my long absence14:56
MaWaLehi amachu14:56
persiahey Belutz14:56
Belutzhi persia14:57
Belutzpersia, how things going?14:57
persiaAlright.  For you?14:57
BelutzI'm alright too, thanks :)14:57
Belutzjust a lot of work to do14:57
Belutzand i'm still in the office at 10pm now :D14:58
nijaba@paris14:59
sommerhey all14:59
persianijaba, The bot can't process the google calendar, and so doesn't track the schedule.  Checkhttp://fridge.ubuntu.com/calendar14:59
persiaServer Team meeting is at 16:00 UTC, which is in an hour14:59
nijabaoki, ta persia14:59
aamachuBelutz: you there :-)14:59
aamachugreat the time change worked?14:59
Belutzamachu, i'm here :D15:00
aamachupersia: yes.15:00
aamachuso let me check for one more person15:00
aamachuelky: Hey are you there?15:00
Belutzamachu, maybe it's not working for our friend in australia15:00
Belutzit's probably 2am in there15:01
aamachulifeless: ?15:01
aamachuBelutz: Yes. persia had commented with his concerns on that15:01
b0i_kut3^^hello15:02
=== b0i_kut3^^ is now known as khanh_coltech
aamachuBelutz: got to know about zakame?15:02
Belutzamachu, no i'm not15:02
aamachupersia: we still need one.15:03
persiaaamachu, Indeed.  If zakame doesn't join us, I think we won't reach quorum.15:03
mathiazHello all - for those attending the Ubuntu Server Team we'll move to #ubuntu-server15:04
nealmcbhmmm - the fridge says 16:00 UTC for server team meeting, but Mathias said we'd changed to 15:0015:04
khanh_coltechcan i become Ubuntu member?15:04
persianealmcb, It seems to be related to some confusion based on some governments insistence that there should be changes to the hours on clocks.15:04
nealmcbindeed....15:05
persiakhanh_coltech, Possibly.  If we can get one more of our board members to arrive in the next 10 minutes or so, we'll process the applications in the order they appear on the wiki page.15:05
persiakhanh_coltech, If not, we'll try to reschedule the next meeting to assure a sufficient number of people will be present, and review them then.15:06
khanh_coltechpersia: thanks, i will wait :)15:06
hito_jpkhanh_coltech: please fix your wikipages link, I think that it needs "s/k/K/'.15:07
aamachupersia: while we wait lets decide on concerns you had raised on your comments while editing the wiki page15:08
khanh_coltechhito_jp: ok, it fixed15:09
aamachuyes. I too agree 2 AM is difficult for Aussies15:09
persiaI'm just not convinced we can reach quorum at 15:00, and think we oughtn't schedule any meetings then until we are assured of quorum, as it's unfair to those who attend.15:09
aamachupersia: yes. And it getting repeated for quite a number of time15:09
aamachuand themuso ?15:10
persiais in Australia15:10
PmDematagodapersia: has the meeting been held before?15:11
Belutzaamachu, actually, the previous time is fine with me, but sometimes works in the way15:11
persiaPmDematagoda, Several times, but we have yet to reach quorum this evening.15:11
PmDematagodapersia: Ive been having trouble attending any meeting all this time, most of the time I was caught up in something, my apologies for that15:11
aamachuBelutz: you mean the 11.00 UTC or 9.00 UTC?15:11
Belutztoo many different time zones for asia & oceania :D15:12
Belutzaamachu, both, but at both time i will be still at the office15:12
persiaBelutz, Can you meet from the office?15:12
aamachuits office time here in India too..15:12
Belutzpersia, yes, if there's no meeting :)15:13
aamachubut I can manage15:13
=== khanh_coltech is now known as b0i_kut3^^
persiaTo avoid colliding with the CC, let's do 10:0015:13
=== b0i_kut3^^ is now known as khanh_coltech
aamachupersia: you mean to say consistently for all four weeks?15:13
Belutzand because sometimes i travel out of town, it's sometimes hard for me to get a connection15:14
aamachuon tuesdays?15:14
persiaaamachu, Or even just every other week.  We didn't do so well with every week, but I think we'd do better with every other week.15:14
persiaI do like Tuesdays.15:14
aamachupersia: as long as we could meet it I am Ok. So the first and the third or the second and the fourth?15:15
aamachuBelutz: what do you say?15:15
persiasecond and fourth is better for me, but only marginally.15:16
Belutzaamachu, ok, let's try that15:16
MaWaLeso there will not be a meeting today?15:17
Belutzaamachu, could you please set up a google calendar, so I could subscribe to the meeting schedule and get sms notification for that? :D15:17
persiaMaWaLe, We haven't reached quorum, and we're 15 minutes in, so likely no.15:17
persiaaamachu, Just be sure to invite the fridge when you do :)15:17
* MaWaLe is so sad15:18
aamachuyes15:18
aamachuBelutz: and for you?15:18
Belutzyes, it's ok with me15:19
MaWaLecan i ask a question please15:19
Belutzi hope the candidate won't be to dissapointed :)15:19
aamachupersia: : I do update fridge these days15:19
persiaMaWaLe, Go ahead.15:19
aamachuMaWaLe: has been waiting for so long :-)15:19
MaWaLehow do you (RBM) calculate the needed quorum?15:19
persiaThe RMB is 7 members, so it requires at least 4 to make a binding decision.15:20
aamachuMaWaLe: We are seven on the board - > 50% is four15:20
MaWaLei think that waiting was a good experience for me to have more activities and knowing more people (like amachu and persia)15:20
MaWaLebut now it's taking to much to wait all this time15:20
aamachuMaWaLe: I suggest you also apply to other Boards15:21
aamachuyes I agree its taking long here15:21
MaWaLeamachu: but like mentioned on the edward's rule : for the next and the third time when there's no quorum for an official meeting, the quorum needed is no more 50%15:21
aamachubut without quorum we can't proceed. Hope you understand15:21
MaWaLeamachu: actually i didn't have an internet connection at home so i can't attend to toher RB15:22
MaWaLethis one fit perfectly with mu job time15:22
MaWaLei understand perfectly15:22
aamachuMaWaLe: Thanks for that.15:23
MaWaLethanks for all of you15:23
MaWaLeit was a pleasure and thank you for the reply amachu15:23
aamachuThe fourth Tuesday comes next week, and I will schedule the meeting at 10.00 UTC15:25
aamachuwill that be fine persia, Belutz?15:25
persiaGood for me.  Please also send out an announcement to our Australian colleagues, so that we have a good chance of quorum.15:25
Belutzfine with me15:25
aamachupersia: yes.15:25
persiaExcellent then.  Good night.15:26
MaWaLegood night15:26
aamachufine. lets wind up for the day.15:26
aamachupersia: Belutz: look out for your nominations for Board Member15:26
aamachu:-)15:26
aamachuThank you everyone for participating15:27
Belutzaamachu, thanks :)15:27
MaWaLethanks15:27
Belutzpersia, thanks :)15:27
Belutzfor all candidates, thanks for your understanding :)15:27
zaafouri=)15:27
MaWaLeBelutz: I'm a regularI'm a regular now :p15:28
Belutz:D15:28
MaWaLeBelutz: can i speak to you in private please15:29
BelutzMaWaLe, feel free to pm me :)15:30
MaWaLethx15:30
=== mib_ua4w0h is now known as ALAYA
=== Andre_Gondim is now known as Andre_Gondim-afk
=== beuno_ is now known as beuno
=== fader is now known as fader|lunch
=== beuno_ is now known as beuno
=== mc44_ is now known as mc44
* manjo waves16:58
cooloneycooloney, waves16:59
* smb_tp waves back16:59
* amitk waves17:00
pgranerIts about time for the Weekly Kernel Team IRC meeting17:00
pgraner#startmeeting17:00
MootBotMeeting started at 12:00. The chair is pgraner.17:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]17:00
* apw hovers at the edge of your vision17:00
pgraner[TOPIC] Open Items from last week17:01
MootBotNew Topic:  Open Items from last week17:01
Riddell** Kubuntu meeting in #kubuntu-devel incase anyone is in here for it17:01
pgraner* sconklin, bring up archiving of Hardy/Intrepid OEM LPIA trees after the sprint17:01
* smb_tp remembers he still has to add some calendar entries17:02
pgraner* sconklin, coordinate testing by the OEM team for Hardy and Jaunty lpia17:02
rtgpgraner: sconklin is out today17:02
pgranerrtg: Understand, just for completeness.17:02
pgranerawe: the OEM team testing and news?17:03
* pgraner look at awe17:03
aweno news...working on testing this week17:03
pgranerawe: thanks can you send an email to kernel-team letting us know how it goes?17:03
awei'm bringing the hpmini up to the latest abi / oem-kernel first17:04
awewill send an email when i've finished testing17:04
pgraner[ACTION] awe to report back to kernel-team on LPIA testing status17:04
MootBotACTION received:  awe to report back to kernel-team on LPIA testing status17:04
pgraner* ogasawara, handle another call for testing for A617:04
ckingawe: so no pushing new commits then?17:04
ogasawarapgraner: sent email, although I'm concerned about the fact that Beta should have users testing via check box but that wasn't available for the A6 cft17:04
apwyes the upload i expected to occur tue last week did not occur17:04
pgranerogasawara: yea, I found out about that yesterday, rtg is pushing the package, so we should send out a revised CFT17:05
apwseems it needed some FF exception and so it being requested now17:05
rtgrt will puch the package as soon as apw delivers it17:05
pgranerogasawara: once the checkbox pkgs is uploaded17:05
awecking: correct17:05
ogasawarapgraner: ok good.  I'll send another pre-beta cft when it's ready.17:05
pgranerapw: can you let ogasawara know when to fire the CFT out since you working it behind the scenes?17:06
apwyep17:06
pgraner[ACTION] apw to inform ogasawara when revised CFT can go out17:06
MootBotACTION received:  apw to inform ogasawara when revised CFT can go out17:06
pgraner* apw and smb, look through the bugs ogasawara mentioned .... hows it going?17:06
apwack17:06
smb_tpWe have one which is a bit tricky (the crash)17:07
smb_tpOne is fixed by now17:07
smb_tpAnd one could go to manjo (he just isn't aware of it yet)17:07
manjosmb_tp, send it my way17:08
smb_tpack17:08
ogasawarapgraner: from my end they look to be getting the proper attention17:08
smb_tpmanjo, Its another Dell server hardware issue on Hardy17:08
manjook17:08
pgraner[ACTION] smb to send manjo bug on Dell server hw issue on Hardy17:09
MootBotACTION received:  smb to send manjo bug on Dell server hw issue on Hardy17:09
manjois that the hibernate problem ?17:09
pgranerogasawara: thanks for the update17:09
smb_tpmanjo, No some sort of sata3 disk17:09
manjok17:09
pgraner* apw, confirm the ack requirements for jaunty...  not sure what this one is about17:09
apwthat one was done, in the last meeting and can be closed17:10
pgranerapw: nice17:10
* pgraner likes closed actions17:10
apwjust confirming we need one ACK for commit to Jaunty currently17:10
pgraner[TOPIC] Security & bugfix kernels - Hardy - Intrepid17:10
MootBotNew Topic:  Security & bugfix kernels - Hardy - Intrepid17:10
* rtg has been slacking on that a bit17:10
smb_tpHardy: Upload planned for tomorrow including17:10
smb_tp• rt: Updated PREEMPT_RT support to rt2717:10
smb_tp• fix apparmor memory leak on deleted file ops17:10
smb_tp• KVM: MMU: Add locking around kvm_mmu_slot_remove_write_access()17:10
smb_tp• serial: 8250: fix shared interrupts issues with SMP and RT kernels17:10
smb_tp• 8250.c: port.lock is irq-safe17:10
smb_tp• ACPI: Clear WAK_STS on resume17:11
smb_tpIntrepid: Upload has been done, linux-meta needs to get through17:11
smb_tpCVE updates are currently being triaged and processed17:11
smb_tpThats basically it17:11
* pgraner is impressed with smb_tp cut n paste ability :-)17:11
smb_tp:-P17:11
pgraner[TOPIC] Jaunty Status17:11
MootBotNew Topic:  Jaunty Status17:11
pgranerrtg: how we a lookin'?17:11
rtgan ABI bumper is coming today.17:12
rtgit contains ATI r6/r7 bits17:12
rtg2.6.28.817:12
rtgand some other stuff17:12
rtgoh, and built in EHCI/UHCI/OHCI17:12
IntuitiveNippleha!17:12
amitkrtg: OHCI too?17:13
rtgI think its looking pretty good. no serious problems that I know of.17:13
pgranerrtg: any expected fall out from EHCI and friends?17:13
rtgactually, it ought to clear up some issues with USB transfer speeds.17:13
IntuitiveNippleAs long as the link order is correct :)17:13
rtgessentially, its the same solution in the kernel that folks have employed in initramfs17:13
IntuitiveNippleThat one will solve a lot of USB speed complaints17:14
rtgI think the biggest issues with Jaunty are ARM related at this point17:14
* cking is encouraged by this 17:14
amitkhow widely is OHCI used?17:14
pgranerrtg: will hit arm in a few min17:14
rtgAA and aufs do play well together17:14
rtgdon't17:15
rtgok, full stop17:15
pgranerJaunty Alpha 6 ... ogasawara how does it look from your standpoint?17:15
pgranerwill come back to that...17:16
ogasawarapgraner: looking good here, but seem to be getting more suspend resume bugs17:16
pgranerah17:16
pgranerogasawara: what type? hangs?17:16
apwi get the feeling suspend/resume has not been that great ever and we are now17:17
apwseeing the badness via the incoming bug stream as people switch over17:17
ogasawarapgraner: the ususal, failure to resume.  and I think the increased bug reporting is because of the apport hooks17:17
apwto jaunty.17:17
IntuitiveNippleFrom my experience the suspend/resume code in many drivers was an after-thought to catch up with the API17:18
pgranerogasawara: any way to tell if they are false positive? For example I have shut the lid (with it set to suspend) and then opened it immediately and I get the apport notification... anything like that?17:18
rtgIntuitiveNipple: I think most drivers have caught up wrt to suspend.17:18
ogasawarapgraner: I do see what seem to be false positives coming in too.  I've tried to tag them "false-report" so we can investigate.17:18
pgranerogasawara: great...17:19
apwogasawara, yeah i have a couple of thoughts on that one17:19
IntuitiveNippleWe have a few false positives based on the TEST_SUSPEND_SECONDS = 5 and I'm investigating what would be a sesnsible higher value to set that based on a collection of kern.log reports ogasawara collected from launchpad17:19
apwif they are false we can start dup'ing them onto matt's original false one17:19
IntuitiveNippleIt looks like increasing it to 9 or 10 would solve alot of those false positives17:19
ogasawaraapw: sounds good17:20
pgranerWell that lead us into the Suspend/Resume topic... which we just covered17:20
pgraner[TOPIC] ARM17:20
MootBotNew Topic:  ARM17:20
pgraneramitk: what say you?17:21
amitkas rtg mentioned aufs and apparmor don't like each other17:21
bradFthe AA and aufs issue that rtg was referring to ... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/34437017:21
amitkor rather AA doesn't like imx5117:21
ubottuError: Could not parse data returned by Ubuntu: timed out (https://launchpad.net/bugs/344370/+text)17:21
amitkbradF is looking at the problem17:22
pgraneramitk: ok, any other show stoppers out there for ARM?17:22
rtgI'm concerned that the problem is something systemic.17:22
amitkI am working on finalising the imx51 configs for mobile team17:22
pgraneramitk: thanks17:23
amitkpgraner: we have dying ttys on the babbage boards. That seems to be the major showstopper right now17:23
pgraneramitk: I guess that keeps the end user experience short huh?17:23
apwphysical or virtual dying?17:23
pgraneramitk: any theories on why/how etc...?17:24
amitkpgraner: yeah, a bit17:24
amitkcompiling in AA causes problems, w/o it things are somewhat better17:24
ckingjust somewhat?17:24
pgraneramitk: have we reached out to upstream to see what they think?17:25
amitkcking: we don't know the next problem we'll encounter after that :)17:25
amitkpgraner: I've talked to John Johansen17:25
rtgpgraner: or the Freescale dudes?17:25
amitkhe seemed to think it shouldn't happen17:25
pgraneramitk: let me know if you need to talk to Freescale and I'll get some one on the line for you.17:26
amitkhonestly, given our time constraints, we don't have the experience to track down the AA issue17:26
rtgJohn's explanation made it sound like it could be a fundamental problem.17:26
amitkso I am trying to bypass it for now17:26
amitkpgraner: thanks17:26
pgraneramitk: ok, sounds like a solid plan forward for now17:27
pgranerSince sconklin is not here we'll skip the lpia for this week, if there are no objections....17:27
* rtg has no objections17:28
ckingnope17:28
pgraner[TOPIC] Incoming Bugs17:28
MootBotNew Topic:  Incoming Bugs17:28
pgranerogasawara: your time to shine :-)17:28
ogasawarapgraner:  I only have 2 to bring up and both seem to be getting looked at17:28
ogasawarabug 343556 - regression-potential but apw looks to be investigating17:28
ogasawarabug 212485 - hardy SRU that smb_tp looks to already be taking care of17:28
ubottuLaunchpad bug 343556 in linux "MacBook rev3: Wireless works in 8.10 but not in Jaunty" [Medium,Incomplete] https://launchpad.net/bugs/34355617:28
ubottuLaunchpad bug 212485 in linux "kernel bug rpc nfs client" [High,In progress] https://launchpad.net/bugs/21248517:28
pgranerogasawara: thanks... looks in order17:29
pgraner[TOPIC] Open Discussion17:29
MootBotNew Topic:  Open Discussion17:29
pgranerFloor is open...17:29
manjois ext4 going to be a default in jaunty ?17:30
pgranermanjo: no17:30
pgranermanjo: purely optional17:30
manjocurrent option is the chose manual partition to get ext4...17:30
pgranermanjo: as planned17:30
manjok17:30
pgranerAny idea when we will see 2.6.29 go final?17:30
rtgwe're seeing some complaints about ext417:31
ckingjust some?17:31
rtg175 on one report at last count :)17:31
cooloneyrtg, right, ext4 lost data ?17:31
manjoin my testing ext4 has major issues17:31
amitkpgraner: its already -rc8, so soon17:31
=== fader|lunch is now known as fader
rtgthe next upload has some patches that change some behaviors to be closer to ext317:31
apwrtg is that the patch kit to expedite the open modify rename stuff17:32
rtgI did so at apw's suggestion17:32
rtg^^17:32
ckingkde users will be happy17:32
pgranerogasawara: should we highlight the new ext4 patches and ask for some out of band testing for the willing?17:32
rtgthe truncated files will be happier too :)17:32
Riddellwe will?17:33
ogasawarapgraner: sure, wouldn't hurt.17:33
pgranerogasawara: can you arrange?17:33
ogasawarapgraner: yup17:33
pgraner[ACTION] ogasawara to issue CFT around ext4 data loss patches17:33
MootBotACTION received:  ogasawara to issue CFT around ext4 data loss patches17:33
cjwatsonmanjo: (also you can boot with partman/default_filesystem=ext4 on the kernel command line, if that makes things more convenient for you while testing)17:34
pgranerRiddell: yea, ext4 eats kde dot files and leave them zero length17:34
cooloneypgraner, sorry, CFT = ?17:34
rtgcall for testing17:34
Tonio_hi (sorry was locked in a meeting here...)17:34
cooloneyOK17:34
RiddellTonio_: kubuntu meeting in #k-d17:34
manjocjwatson, thanks that works lot better17:34
pgranerAnyone have other items... going once... twice17:35
* rtg flees to another meeting17:35
pgraner[TOPIC] Next Meeting17:35
MootBotNew Topic:  Next Meeting17:35
pgranerSame time and channel17:35
apwack17:35
smb_tpack17:35
cking..different reality17:35
ckingack17:35
lieb_ack17:36
cooloneyok17:36
manjok17:36
pgranerThanks everyone! Appreciate it!17:36
=== lieb_ is now known as lieb
amitkthanks17:36
pgraner#endmeeting17:36
MootBotMeeting finished at 12:36.17:36
cooloneythanks17:36
* smb_tp shuffles away17:36
=== Andre_Gondim-afk is now known as Andre_Gondim
=== mc44_ is now known as mc44
=== Andre_Gondim is now known as Andre_Gondim-afk
=== mc44_ is now known as mc44
=== RainCT_ is now known as RainCT
juliux@schedule berlin22:29
nhandlerjuliux: FYI, ubottu no longer manages the schedule. Look at the gcal23:02
=== asac_ is now known as asac
Laneynhandler: Have you time for a couple of FFes?23:59

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