[16:00] <rbasak> o/
[16:00] <nacc> o/
[16:00] <rharper> o/
[16:00] <rharper> wait a min and then I'll get started
[16:00] <jgrimm> o/
[16:02] <smoser> o/
[16:02] <rharper> #startmeeting ubuntu-server-team
[16:02] <meetingology> Meeting started Tue Jun 21 16:02:19 2016 UTC.  The chair is rharper. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:02] <meetingology> Available commands: action commands idea info link nick
[16:02] <rharper> #topic Review ACTION points from previous meeting
[16:02] <coreycb> o/
[16:02] <rharper> looking at the logs, I see no previous ACTION points to review, so we'll move on
[16:03] <rharper> #topic Yakkety Development
[16:03] <rharper> #link https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule
[16:03] <rharper> we've got an Alpha at the end of the month
[16:03] <jgrimm> steady progress being made against merges
[16:03] <jgrimm> reasonably happy there
[16:03] <cpaelzer> o/
[16:03] <rharper> jgrimm: do we have a number or anything compact ?
[16:04] <jgrimm> just mom
[16:04] <rharper> right
[16:04] <jgrimm> https://merges.ubuntu.com/main.html
[16:04] <rharper> #link https://merges.ubuntu.com/main.html
[16:04] <rharper> #subtopic Release Bugs
[16:04] <rharper> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-y-tracking-bug-tasks.html#ubuntu-server
[16:05] <rharper> not much there
[16:05] <jgrimm> indeed, also note.. openstack split into their own section now
[16:06] <rharper> #topic Server & Cloud Bugs (caribou)
[16:07] <rharper> just missed caribou it seems
[16:07] <rharper> I know smoser is cleaning up a number of cloud-init issues so we can get another upload into yakkety
[16:08] <smoser> i hope to getan sru upload into trusty today of yakkety level of cloud-init
[16:08] <rharper> shortly after that, we'll have a curtin update with fixes for known maas issues
[16:08] <jgrimm> SRU for newer docker in the works too
[16:08] <rharper> jgrimm: 1.12 ?
[16:08] <smoser> we need maas team to verification-done on https://code.launchpad.net/~smoser/cloud-init/trunk.net-improve-lo-dns/+merge/298035
[16:08] <jgrimm> 1.11.2
[16:08] <smoser> bah
[16:08] <smoser> on https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1577872
[16:08] <rharper> jgrimm: ack
[16:08] <smoser> we should push on that.
[16:08] <rharper> smoser: I have meeting tomorrow scheduled with maas team
[16:09] <rharper> so ping me with any other bugs we need them to verify and I'll add it to my list for them to poke at
[16:09] <rharper> caribou: welcome back, we're currently discussing Server & Cloud bugs if you have any
[16:10] <Karibou> rharper: well the Kubuntu version of me will have to anwser
[16:10] <rharper> hehe
[16:10] <jgrimm> heh
[16:10] <rharper> that'll work
[16:10] <smoser> caribou, do you go by Karibou when you run Kubuntu ?
[16:10] <caribou> ah ok, I'm back here too
[16:10] <caribou> Quassel is playing games with me
[16:10] <caribou> smoser: no just alternate nick
[16:10] <smoser> nice.
[16:11] <caribou> ok, been sprinting last week and used the opportunity to work on a few multipath-tools bugs
[16:11] <caribou> rharper: I'm planning to SRU the Xenial fix that you sent to debian
[16:11] <caribou> rharper: I'm also about to SRU a double-free segfault to Trusty
[16:12] <caribou> rharper: other than that, I'm about to push release 1.6.0 of makedumpfile/kdump-tools
[16:12] <caribou> that's about it
[16:12] <rharper> caribou: multipath-tools, yes ... and did you look at any additional items that xnox had identified  ?
[16:13] <caribou> rharper: spoke to him about it last week, yes
[16:13] <rharper> https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1583563
[16:13] <caribou> rharper: I'll check with him before SRUeing to Xenial
[16:13] <rharper> caribou: ok, great
[16:13] <caribou> rharper: well, looks like xnox updated it friday
[16:13] <rharper> yeah
[16:14] <caribou> rharper: maybe that should also be SRUed to Xenial
[16:14] <rharper> I'd think so
[16:14] <caribou> rharper: ok will get that one too
[16:14] <rharper> nice
[16:14] <rharper> thanks
[16:15] <rharper> anything else
[16:15] <caribou> nope, I'm good
[16:15] <rharper> #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
[16:15] <cpaelzer> note - IBM tested the fix of friday even if bugproxy still takes its time
[16:16] <cpaelzer> that was for multipath
[16:16] <rharper> cpaelzer: ack
[16:16] <cpaelzer> and FYI smb extends the sprint, so he is out this week
[16:16] <rharper> ok, so might not get and kernel team input
[16:17] <rharper> #topic Upcoming Call For Papers
[16:17] <rharper> anything to keep an eye on here?
[16:18] <rharper> moving on
[16:18] <rharper> #topic Ubuntu Server Team Events
[16:20] <rharper> #topic Open Discussion
[16:20] <rharper> any thing to discuss ?
[16:20] <jgrimm> rharper, i was going to add a AIO backend enablement item to the blueprint so we don't lose
[16:21] <jgrimm> but we should try to enable that soon, i think?
[16:21] <jgrimm> for tgt
[16:21] <rharper> jgrimm: yeah, I can rebuild, put it in PPA and see about getting a sponser to upload it to yakkety
[16:21] <jgrimm> cool
[16:22] <rharper> #action rharper to enable AIO backend in tgt in yakkety
[16:22] <meetingology> ACTION: rharper to enable AIO backend in tgt in yakkety
[16:22] <rharper> now I'll get bothered weekly =)
[16:22] <rharper> #topic Announce next meeting date, time and chair
[16:22] <jgrimm> rharper, ha!  thanks sir!
[16:22] <caribou> rharper: don't hesitate to ping me if you need a sponsor
[16:22] <rharper> next week's meeting same time and place, chair will be beisner
[16:22] <jgrimm> rharper,  don't forget about rbasak
[16:23] <rharper> caribou: thanks!
[16:23] <rharper> jgrimm: yep, rbasak updated the template
[16:23] <rharper> #topic Assigned merges/bugwork (rbasak)
[16:23] <rbasak> Thanks :)
[16:23] <rbasak> Progress reports first please.
[16:23] <rbasak> cpaelzer: bug 1507681, bug 1495988, bug 1581839, bug 1524526, bug 1590688
[16:23] <cpaelzer> 1581839 Sponsored by Brian Murrayi (thanks), waiting for 3rd party verify in proposed
[16:23] <cpaelzer> 1507681 Waiting in proposed for the reporter to verify
[16:23] <cpaelzer> 1495988 Waiting for Review/Sponsoring, but there is 2.4.7-1ubuntu4.10 SRU in flight (who clears that?)
[16:23] <cpaelzer> 1524526 Merge ready as of a few mnutes ago (importer process found various issues) + includes the dropping of the failing plugin
[16:23] <cpaelzer> That goes along with a no change rebuild of dovecot-antispam as discussed (also attached to the bug, and mentioned int the MP)
[16:23] <cpaelzer> 1590688 No chance to work on yet
[16:23] <rbasak> jgrimm: bug 1397250
[16:24] <rbasak> rharper: bug 1491406, bug 1472639
[16:24] <rbasak> I had bug 1571174 and that is now done.
[16:24] <rbasak> magicalChicken isn't here so I'll ask him in #ubuntu-server.
[16:24] <rharper> rbasak: 1491406 (marked verification-done)
[16:24] <rharper> rbasak: 1472639: did not touch yet
[16:25] <jgrimm> rbasak,: response from upstream is that they disabled their bugzilla, so testcase therein is lost.   so puts me back a bit to trying to recreate bug on my own.
[16:26] <jgrimm> s/disabled/decomissioned
[16:27] <rbasak> cpaelzer: 988 I just commented in the other bug.
[16:27] <cpaelzer> thanks
[16:28] <rbasak> cpaelzer: in the general case I would like you to chase as needed please, in order to drive your own bug. With no response, we can fail the SRU and go to the next one if a reasonable amount of time has passed and nobody seems interested.
[16:28] <cpaelzer> that is why I asked - ok, will keep an eye
[16:28] <cpaelzer> do you have the others bug # at hand ?
[16:29] <rbasak> bug 1286882 - sorry I didn't link to it from the other bug.
[16:30]  * rbasak is still catching up
[16:30] <rbasak> cpaelzer: I think I'm done with yours - thanks.
[16:30] <cpaelzer> great
[16:31] <rbasak> rharper: 406 looks landed? Thank you for driving that.
[16:31] <caribou> rbasak: regarding bug 1286882, I'll check that out first thing tomorrow morning
[16:31] <rharper> rbasak: cool!  Sure.
[16:31] <rbasak> caribou: thanks!
[16:32] <rbasak> magicalChicken: hello! Thank you for joining the meeting if you're here.
[16:32] <rbasak> magicalChicken: please can you report status on: bug 869017, bug 1394403, bug 1511222, bug 1519120
[16:32] <magicalChicken> rbasak: hi
[16:33] <magicalChicken> for 1511222, i have submitted a debdiff and verified it fixes the bug for me
[16:33] <rbasak> I think I remember you saying that you weren't sure where to go with 017 next, sorry.
[16:33] <magicalChicken> yeah, the kbd bug looks like it may just need to be a policy issue
[16:33] <magicalChicken> but 1394403 i still have not been able to reproduce with the first submitted patch in place
[16:34] <magicalChicken> i do think that it was fixed with that patch
[16:34] <rbasak> magicalChicken: for 222, does that need sponsoring now? Or do you want the reporter to test success first?
[16:34] <magicalChicken> i submitted a link to a build in my ppa for 222, so the reporter could verify
[16:34] <magicalChicken> it might be good to make sure that the package works for them first
[16:35] <rbasak> magicalChicken: OK, that's fine. Please can you make sure that it is clear in the bug that progress is blocked on the reporter?
[16:35] <magicalChicken> sure, I'll post a comment real quick
[16:35] <rbasak> I'll take the kbd bug.
[16:35] <magicalChicken> and for 120 it was a missing dep, so i have a debdiff that adds vlan to recommends
[16:35] <magicalChicken> awesome, thanks. yeah, i just couldn't figure out how to move forward there
[16:38] <rbasak> magicalChicken: where is the debdiff for 120 please?
[16:38] <magicalChicken> http://paste.ubuntu.com/17650089/
[16:38] <magicalChicken> I'm adding it to the bug rn
[16:38] <rbasak> Great, thanks
[16:38] <rbasak> magicalChicken: also subscribe ~ubuntu-sponsors please, if it's ready for sponsoring.
[16:39] <magicalChicken> sure, yeah
[16:39] <rbasak> That's everyone I think. nacc didn't have any bugs assigned this past week. Did I miss anything?
[16:40] <nacc> rbasak: mostly caught up with php (now just syncing the rest of them), will try to look at bacula today
[16:40] <rbasak> nacc: that's great, thanks!
[16:40] <rbasak> So I had lined up to assign: bug 1585771, bug 1553563, bug 1570923
[16:40] <rbasak> nacc: are you able to take 563 and 923 now please?
[16:40] <rbasak> And who wants 771?
[16:41] <rbasak> Who has capacity?
[16:41] <jgrimm> cpaelzer, were you looking for another bug?
[16:41] <cpaelzer> not really
[16:41] <cpaelzer> since I wasn't able to touch the one I got last week
[16:42] <nacc> rbasak: yeah
[16:42] <jgrimm> heh.  fair enough.
[16:43] <rbasak> nacc: thank you!
[16:43] <rharper> rbasak: I'll take 771
[16:44] <rbasak> rharper: thanks!
[16:44] <jgrimm> rharper, rbasak: that one just needs looking after right?
[16:44] <rbasak> Right.
[16:44] <jgrimm> that is, 771 looks like its making progress, i think robie was just wanting someone to watch after it
[16:44] <rharper> sure
[16:44] <rbasak> Actually, looking now, it looks like it might already be fixed by cyphermox, or at least an SRU in progress.
[16:45] <rharper> see cpaelzer you should have taken it
[16:45] <rbasak> So if rharper you could just check that it's all good from a server perspective, that would be appreciated.
[16:45] <rharper> rbasak: indeed
[16:45] <rharper> rbasak: anything else for the meeting ?
[16:45] <jgrimm> not from me
[16:45] <rbasak> That's all I had. Thanks all. Again, I'm really pleased about the progress everyone is making on this effort - thank you.
[16:46] <rharper> rbasak: thanks for keeping us on task =)
[16:46] <rharper> ok, thanks folks
[16:46] <rharper> #endmeeting
[16:46] <meetingology> Meeting ended Tue Jun 21 16:46:11 2016 UTC.
[16:46] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-06-21-16.02.moin.txt
[16:46] <jgrimm> thanks rharper!!
[16:46] <caribou> thanks rharper!
[16:46] <cpaelzer> thanks rharper, cu
[16:46] <cyphermox> rbasak: what was that that I fixed?
[16:46] <nacc> rbasak: thanks!
[16:47] <nacc> rharper: thanks!
[16:47] <rbasak> cyphermox: bug 1585771 (thanks!)
[16:47] <jgrimm>  bug 1585771
[16:47] <cyphermox> ah ok
[16:47] <cyphermox> yeah, help verifying the SRU is very welcome :)
[17:26] <kees> ogasawara: when/where are the kernel team meetings these days? it seems https://wiki.ubuntu.com/KernelTeam/Meeting is very out of date :)
[17:56] <beisner> hi jgrimm - i'm on holiday next week, and still have conflicts at the normal time.  can you cover me?   i'll be back in that chair one day, promise.  :)
[17:56] <jgrimm> beisner, yes, i'll cover you. thanks for the heads up
[17:56] <beisner> jgrimm, yw & thanks too


[07:47] <ejat> fta: i cant open this page with chromium http://is.gd/3M54x
[10:01] <fta> ejat, nope (snap)
[10:28] <ejat> yeah
[10:28] <ejat> snap ..
[10:31] <fta> *** glibc detected *** /usr/lib/chromium-browser/chromium-browser --type=renderer --lang=en-US --force-fieldtest=CacheSize/CacheSizeGroup_0/DnsImpact/_default_enabled_prefetch/GlobalSdch/_global_disable_sdch/SocketLateBinding/_disable_late_binding/ --channel=23481.a64dba0.1170317228: double free or corruption (!prev): 0x0b5364a8 ***
[11:14] <asac> fta: can you enable verbose build commands for chromium?
[11:15] <asac> or tell me how to do that so i can do it ;)?
[11:43] <asac> fta: i will enable version building for chromium now
[12:02] <ripps> fta: the daily bot gives me warnings when I try to use the ppa:~user/ppa as the ppa name.
[12:02] <ripps> Also, for some reason, my packages aren't adding *.changes to my ppa directory
[12:15] <asac> maybe your bzr-builddeb config does not set the build-area result dir properly?
[12:15] <asac> ripps: ?
[12:19] <ripps> asac: huh?
[12:20] <asac> the bot uses bzr builddeb
[12:20] <asac> that uses a config file or command line arguments
[12:20] <asac> to determine where to put the results
[12:20] <asac> the .changes are put there usually
[12:20] <asac> no clue if thats your problem but its unlikely that no .changes are produced
[12:20] <asac> i expect them to be just in a different dir ;)
[12:20] <ripps> asac: actually it seems to be the new package. The older packages are working and creating .changes, but the new package isn't... maybe I screwed up something in the configs
[12:21] <asac> ripps: do they fail to build?
[12:21] <asac> you should be able to see in log if they produce changes
[12:21] <ripps> asac: they build fine
[12:21] <asac> and you see that changes are produced?
[12:22] <asac> thats what usually happens near the end of the buiöd
[12:22] <asac> maybe you can see dpkg-genchanges or something
[12:26] <ripps> asac: okay, I know where it's going wrong, just now how or why:  http://paste.ubuntu.com/281213/
[12:29] <ripps> I'm using "%: dh $@" as my rules, and it works perfectly in my pbuilder, but for some reason, I think the automatica dh_clean is breaking something
[12:38] <asac> yeah. i think debhelper 7 is a huge mistake ;)
[12:38] <asac> s/think/feel that/
[12:43] <ripps> maaaan... it's way past my bedtime, I just want to get this uploaded and go to bed
[12:44] <ripps> I'm going to try and prevent dh_clean all together and see if it works
[12:44] <asac> heh
[12:44] <asac> ok
[12:45] <asac> if you find it, let us know
[12:59] <ripps> fta: if you read this at some point, it seems that the ppa-bot is causing somekind of issue with dh_clean or dh_auto_clean, http://paste.ubuntu.com/281213/, my issue was resolved by preventing dh_clean alltogether, but this is not an ideal solution.
[13:10] <asac> gah tbird crashed .. ... not evnough memory
[13:57] <ripps> fta: even cdbs is giving me issues, but only with the new package... I don't know what I did, but it's only this new package that get's these issues, not my old one's.  http://paste.ubuntu.com/281276/
[14:18] <asac> ripps: is your produced orig.tar.gz name good?
[14:18] <asac> ripps: can you build without the bot if you use the same tarball produced by bot?
[14:19] <fta2> ripps, could you give me the full logs (or forward me the email if you use -e)?
[14:19] <fta2> asac, taking interest in chromium?
[14:19] <asac> fta2: same as before.
[14:19] <[reed]> I hope not. He's restricted to Mozilla projects!
[14:19] <[reed]> :)
[14:20] <asac> hehe
[14:21] <asac> fortunately, i can also spend my time whereever my work is needed and where distro input is allowed/appreciated/recognized ;)
[14:32] <fta2> grr, it seems it's impossible to use dlsym() with gcc4 and -O2/3/s and strict aliasing
[14:32] <fta2> even the example in the man page is not clean
[14:34]  * asac would think it works. but havent tried
[14:35] <fta2> try to copy/paste the ex and build it with -Werror -O2
[14:36] <asac> ok let me try
[14:36] <asac> gcc -Werror -O2 -rdynamic -o foo test.c -ldl
[14:36] <asac> asac@hector:/tmp$ ./foo
[14:36] <asac> -0.416147
[14:36] <fta2> add -Wall
[14:37] <asac> gcc -pedantic-errors -Werror -O2 -rdynamic -o foo test.c -ldl
[14:37] <asac> asac@hector:/tmp$ ./foo
[14:37] <asac> -0.416147
[14:37] <asac> yeah
[14:37] <asac> that fails ;)
[14:37] <fta2> i use -Wall -pedantic -O2 -Werror in my code
[14:46] <asac> fta2: http://paste.ubuntu.com/281314/
[15:04] <av`> asac, what should we do with #239151
[15:04] <av`> asac, a simply backport or something more?
[15:05] <av`> Launchpad Bug #239151
[15:11] <asac> if flashblock is completely broken for everyone we should consider to do a SRU
[15:11] <asac> for harx
[15:11] <asac> dy
[15:11] <av`> yep
[15:12] <av`> let me know your decision
[15:28] <fta2> asac, hm, i see. a union trick. could work but it means re-engineer all my project as i have a bunch of plugins
[15:33] <asac> fta2: i found somewhere on the web that union type-punning was explicitly left allowed
[15:33] <asac> because that was always the best practice to do something like that
[15:34] <asac> its not a union trick, but the original and most portable way to do things like this ;)
[15:36] <fta2> well, the union adds a layer in my otherwise nice api
[16:04] <asac> fta2: you can wrap that union part
[16:04] <asac> under the API hood
[16:04] <asac> and return the properly type casted function
[16:05] <asac> at least i would expect that APIs pass properly typed funcs in and out
[16:05] <asac> so whatever does the dlsym should do the cast
[16:06] <fta2> trying that..
[17:00] <fta2> asac, why did you add armel? any plan to upload soon?
[17:01] <asac> the plan is to get this up asap. but that takes 1-2 month in my planning
[17:01] <asac> we would put that in karmic-updates as we wont make it for release
[17:02] <asac> this in particular was because someone wanted to compare ffox vs. chromium on arm
[17:03] <asac> and couldnt get it built
[17:03] <asac> once we have most archs built we can disable VERBOSE again by default
[17:03] <asac> just easier to look at buildd logs that way
[17:14] <fta2> i kept it disabled because some lines were really long at some point, more than what the shell allows in cli
[17:15] <asac> if it breaks todays daily we can back it out again
[17:15] <asac> but i hope not
[17:16] <fta2> todays build failed, but for another reason
[17:26] <asac> get-orig-source didnt package that .gyp file up?
[17:29] <fta2> src/native_client was dropped completely until now
[17:29] <fta2> meaning i need a new tarball
[17:30] <fta2> hence a fresher commit
[18:55] <LLStarks> asac. you there?
[18:56] <asac> LLStarks: for a bit
[18:58] <LLStarks> 1. can you tell me that mozilla changelog site again? 2. where can i find older firefox daily builds?
[18:58] <LLStarks> older = older than 1 month
[19:06] <asac> LLStarks: hg.mozilla.org/releases -> mozilla-1.9.2 (3.6) vs. mozilla-1.9.1 (3.5)
[19:07] <LLStarks> narrowed the change to between july 1st and august 1st.
[19:09] <LLStarks> after july 15th.
[19:11] <LLStarks> after 7/25 but before 8/1
[19:14] <asac> LLStarks: cant you find older builds in our ppa?
[19:14] <asac> hmm
[19:14] <asac> i think we only keep sources forever
[19:15] <LLStarks> i'm using http://ftp.mozilla.org/pub/firefox/nightly/2009
[19:16] <asac> LLStarks: we need a one day window
[19:16] <LLStarks> drilling it down right now
[19:17] <LLStarks> 7/28-8/1 right now
[19:20] <asac> thats the thru border thing right?
[19:20] <LLStarks> yup
[19:20] <asac> any better window? ;)
[19:20] <LLStarks> 7/29-8/1
[19:21] <LLStarks> i'm doing 7/30 right now
[19:21] <LLStarks> 7/30 build confirmed
[19:21] <LLStarks> now to find the change
[19:21] <asac> so between 29 and 30 or 30 and 1 ?
[19:22] <asac> LLStarks: ?
[19:22] <asac> worst case would be that it got fixed as a side effect in https://bugzilla.mozilla.org/show_bug.cgi?id=479220
[19:22] <LLStarks> between 7/29 and 7/30\
[19:23] <LLStarks> http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=55fd6820c596&tochange=3222b99f441c
[19:24] <LLStarks> http://hg.mozilla.org/mozilla-central/rev/4e85941dfbb5
[19:24] <LLStarks> https://bugzilla.mozilla.org/show_bug.cgi?id=486065
[19:24] <LLStarks> has to be it.
[19:27] <asac> give it a try ;)
[19:27] <asac> the commit i gave above is also from 30st
[19:28] <LLStarks> what commit was that?
[19:29] <asac> seems it landed early 31st
[19:30] <LLStarks> lemme do a before and after for the commit i linked to.
[19:30] <asac> do what?
[19:30] <asac> just put the patch in our xulrunner-1.9.1 package ;)
[19:30] <asac> thats simple patch
[19:31] <asac> or do you have per commit builds ready yet?
[19:31] <asac> how did you find the commits?
[19:31] <asac> i mean the bounds
[19:32] <LLStarks> i just picked an arbitrary date and then worked backwards.
[19:35] <LLStarks> using the mozilla-central builds
[19:36] <asac> let us know
[19:36] <asac> i am out for a while now
[19:37] <LLStarks> k
[19:37] <LLStarks> when will you be back?
[19:38] <asac> doesnt really matter ;) ... just talk to me i will read when back and if you are still here will answer ;)
[19:38] <asac> but i think 1-2 h
[19:38] <LLStarks> ok
[19:49] <LLStarks> micahg. sup.
[19:50] <micahg> hi LLStarks
[19:51] <micahg> asac: any chance of getting TB3.0b4 into karmic?
[19:51] <LLStarks> do you know how i could best way to test a commit without having to create an entire build setup?
[19:52] <micahg> LLStarks: push to PPA?
[19:52] <LLStarks> i guess, but i suck at debian packaging
[19:52] <micahg> LLStarks:you using a bzr checkout?
[19:53] <LLStarks> mercurial
[19:53] <micahg> ah
[19:54] <micahg> you can make a tarball out of it and use the code from our bzr branch to build the debian package
[19:57] <LLStarks> what's the bzr branch name?
[19:58] <LLStarks> lp:~ubuntu-mozilla-daily/firefox/firefox-3.1.head.daily
[19:58] <LLStarks> or do i need xulrunner?
[19:58] <micahg> LLStarks: which version of ff?
[19:58] <LLStarks> 3.5
[19:58] <LLStarks> this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=500368
[19:59] <micahg> and which component ar eyou changing
[19:59] <LLStarks> is fixed by this commit: http://hg.mozilla.org/mozilla-central/rev/4e85941dfbb5
[19:59] <LLStarks> micahg, i'm not sure.
[20:00] <micahg> probably xulrunner
[20:00] <LLStarks> do i also need to compile firefox with it?
[20:00] <micahg> nah, you can use one of the current versions of FF if you're not making any changes
[20:01] <micahg> you just want to test that patch on the 3.5 branch?
[20:01] <LLStarks> yah
[20:02] <LLStarks> will i be able to use firefox 3.5 shipped with karmic?
[20:02] <micahg> I think the easiest way would be to apply it as a patch in debian/patches
[20:02] <micahg> yeah, you would just need to push xulrunner to your ppa
[20:02] <micahg> I'd make the version smaller than current
[20:02] <LLStarks> how do i do that?
[20:02] <LLStarks> push to my ppa.
[20:03] <micahg> do you know how to pull down the source for xul-1.9.1?
[20:04] <asac> LLStarks: build xulrunner-1.9.1 from mozilla-1.9.2 branch
[20:04] <asac> use some local install location
[20:04] <asac> put the gre.conf into /etc/gre.d/
[20:04] <asac> and then firefox will pick up your xulrunner
[20:05] <LLStarks> why do i have to all the work when i know jackshit about packaging?
[20:07] <LLStarks> okay. where do i start.
[20:10] <asac> LLStarks: i told you how to do it without packaging
[20:11] <asac> you do an upstream xulrunner build
[20:11] <asac> make install
[20:11] <asac> ensure that the right gre file is there
[20:11] <asac> done
[20:11] <LLStarks> "build xulrunner-1.9.1 from mozilla-1.9.2 branch"
[20:11] <LLStarks> what does that mean? where do i get this mozilla-1.9.2 branch?
[20:12] <asac> i have you the url ;)
[20:12] <asac> http://hg.mozilla.org/releases/mozilla-1.9.2
[20:12] <fta> 1.9.1 from 1.9.2 ??
[20:13] <LLStarks> wouldn't everything be easier if asac applied this change himself? i'm bound to  **** up.
[20:13] <asac> thats a typo
[20:14] <asac> i never said you should do that
[20:14] <asac> i wanted you to confirm that the patch works
[20:14] <asac> not more
[20:14] <LLStarks> well, i can't confirm at the commit level
[20:14] <LLStarks> only at the binary build
[20:15] <LLStarks> this is precise as i can be: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=55fd6820c596&tochange=3222b99f441c
[20:16] <LLStarks> and common sense tells me that  commit 4e85941dfbb5 is the most likely fix
[20:18] <LLStarks> asac, if you could apply it to the next daily or a staging ppa, that would be lovely.
[20:20] <asac> LLStarks: give me a patch that applies cleanly
[20:20] <asac> and remember that i wont try like 10 different patches that way
[20:20] <asac> ok out again for a whil
[20:21] <micahg> asac: I could do this later tonight...after 1AM UTC
[20:21] <LLStarks> so... am i building xulrunner 1.9.1 or 1.9.2?
[20:21] <asac> micahg: go ahead. push that to some ppa and let LLStarks confirm the fix (or confirm yourself)
[20:21] <LLStarks> *diffing against
[20:21] <asac> LLStarks: 1.9.1
[20:22] <LLStarks> and cloning from 1.9.2?
[20:22] <asac> the patch is on 1.9.2 branch ... you want to por t that to 1.9.1
[20:22] <asac> LLStarks: you dont need to clone 1.9.2
[20:22] <micahg> LLStarks: what tz are you in?
[20:22] <LLStarks> EDT
[20:22] <asac> clone 1.9.1 and download the diff from the pushlog
[20:22] <LLStarks> eastern daylight, us
[20:22] <micahg> LLStarks: will you be around 9PM EDT?
[20:22] <LLStarks> yah
[20:22] <micahg> I can build it around then
[20:22] <micahg> push up to my ppa
[20:23] <micahg> and you can install to test
[20:23] <micahg> which LP bug is this for?
[20:23] <micahg> or rather what should I call the patch asac?
[20:23] <asac> we have an upstreawm commit. that should be references
[20:23] <LLStarks> https://bugs.edge.launchpad.net/gtk-engines/+bug/327863
[20:23] <asac> referenced
[20:24] <asac> like bzXXX_attXXX_short_desc.patch
[20:24] <asac> please dont pout that bug in the name
[20:24] <asac> use the one referenced in the upstream commit you cherry pick
[20:24] <LLStarks> "clone 1.9.1 and download the diff from the pushlog" gotcha
[20:24] <asac> and document in changelog or on top of the diff in the patch that this also fixes bug xyz
[20:24] <micahg> asac: what is att?
[20:24] <asac> micahg: the attachment id from the bug
[20:24] <asac> that was committed
[20:25] <micahg> ah
[20:25] <asac> usually in bugzilla tehy sign off a specific file for landing
[20:25] <asac> if you click on it you see the id
[20:25] <asac> is quite important for bugs where there are mulitple patches etc. for various branches
[20:25] <micahg> ok
[20:25] <asac> so https://bugzilla.mozilla.org/show_bug.cgi?id=516465
[20:25] <asac> its 403366
[20:25] <LLStarks> asac, the diff doesn't apply cleanly for you?
[20:26] <asac> i havent checked.
[20:26] <LLStarks> i'll check
[20:26] <micahg> asac: got it, thanks
[20:26] <asac> i am doing something else besides talking to you ;)
[20:26] <LLStarks> understood.
[20:26] <asac> now that micahg takes care you should ask him if you should rebase or if he does that ;)
[20:26] <asac> i would have been more happy to get a patch that is guaranteed to apply cleanly ;)
[20:27] <micahg> I was going to rebase it before applying it
[20:27] <fta> asac,   - chromium-browser (<IP_ADDRESS>~svn20090929r27475 -> <IP_ADDRESS>~svn20090929r27516) [78.30MB (+3085kB, +3.94%)]
[20:28] <fta> asac, that's native_client
[20:28] <micahg> I know the lines are off by at least 30
[20:29] <micahg> asac: can you take a quick look at bug 4375454
[20:29] <asac> off is ok ... just quickly check that the code surrounding it is similar
[20:29] <micahg> ugh... bug 437545
[20:29] <asac> yes
[20:29] <asac> we have a different bug for that
[20:29] <asac> its because of devmode
[20:31] <asac> too bad ... cannot find the bug right now
[20:31] <micahg> asac: the patch looks like it would apply cleanly
[20:31] <micahg> but I'll do a test build lateer
[20:32] <asac> micahg: just add to debian/patches/ and series and push to your ppa
[20:33] <asac> builders seem idle ;)
[20:33] <LLStarks> confirm. patches cleanly.
[20:34] <LLStarks> http://pastebin.com/m6699b91b
[20:44] <micahg> waiting for ppa
[20:58] <micahg> looking good
[20:58] <micahg> should be ready in another 10 minutes or so
[20:59] <LLStarks> i have the ppa added.
[20:59] <micahg> you do?
[20:59] <LLStarks> https://launchpad.net/~micahg/+archive/mozilla-test
[20:59] <LLStarks> right?
[20:59] <micahg> this one: https://edge.launchpad.net/~micahg/+archive/mozilla-test
[20:59] <micahg> yep
[21:00] <micahg> I guess good ppa names do help :)
[21:11] <asac> i think one cannot delete ppas yet. so choose a generic name rather than a topic ;)
[21:12] <asac> mozilla-test sounds generic enough of course
[21:17] <fta> asac, with VERBOSE=1, it's now very difficult to track errors, esp since i use --keep-going
[21:18] <fta> asac, i used to look for "error", now, there's -Werror at each line :P
[21:20] <fta> grrr, seems i need to add "libc6-dev-i386 [amd64]" to b-d
[21:24] <asac> fta: if that has impact on your work we can change that back soon.
[21:25] <asac> if possible keep it for a day or two
[21:25] <asac> till the toolchain issues are sorted for armel
[21:25] <asac> if its unbearable on your side: back it out now
[21:27] <asac> fta: ok. its half past 10 ;)
[21:27] <asac> i am leaving for today too
[21:29] <asac> micahg: before i leave. do you need help on the LLStarks patch?
[21:29] <asac> or is all fine?
[21:29] <asac> ok seems amd64 built fine
[21:29] <asac> so you are most likely fine
[21:29] <asac> ttyt
[21:30] <LLStarks> micahg. build is finishing up.
[21:30] <LLStarks> for i386
[21:31] <micahg> seems to be fine asac
[21:31] <micahg> you want me to propose a merge if it works?
[21:36] <LLStarks> i386 built
[21:37] <LLStarks> testing.
[21:38] <LLStarks> \IT WORKS!
[21:38] <LLStarks> holy shit
[21:41] <LLStarks> sorry about that. adrenaline rush. i've never really followed a bug from discovery to fix.
[21:41] <micahg> so, asac wanted this to go into karmic?
[21:42] <LLStarks> that or the default theme had to be changed after appearance freeze.
[21:45] <micahg> I'll propose a merge tonight
[21:51] <BUGabundo> boas noites
[21:51] <BUGabundo> asac: are you around?
[21:51] <BUGabundo> would like to ask you what you think of wish bug of mine
[21:51] <BUGabundo> _before_ I put it on LP
[21:52] <BUGabundo> asac: should NM autoconnect to known wifi networks by default ?
[21:53] <micahg> BUGabundo: doesn't it do that now?
[21:54] <BUGabundo> micahg: no. it remains untick
[21:55] <micahg> is that a regression?  NM connects for me to pomaticallyrevious networks I've connected to aut
[21:55] <BUGabundo> not me, with NM trunk PPA
[21:55] <BUGabundo> its not even selected on a NEW network profile
[22:03] <LLStarks> micahg. your ppa is behind karmic according to dpkg.
[22:03] <LLStarks> did you label correctly?
[22:49] <micahg> LLStarks: yes
[22:49] <micahg> I didn't want to make it above
[22:50] <micahg> micahg: that way if the tests fail, there aren't version issues
[22:57] <BUGabundo> district 9, starting
[22:57] <BUGabundo> bbl
[23:01] <micahg> LLStarks: do you want to change that upstream firefox bug?
[23:01] <LLStarks> to the one that actually fixed?
[23:01] <micahg> yeah :)
[23:03] <LLStarks> fixed.
[23:03] <LLStarks> https://bugs.launchpad.net/ubuntu/+source/xulrunner-1.9.1/+bug/327863/
[23:03] <LLStarks> and the upstream link fixed.
[23:06] <micahg> And I just set the importance and assigned to myseld
[23:06] <micahg> *myself
[23:54] <LLStarks> micahg, once merged with the dailies, how does the fix make it into main?
[23:57] <psyke83> asac: hi. Re: bug #422511, even if that patch works, I think that Firefox will still exhibit problems with a theme using a trough >0
[23:58] <psyke83> right now, with a theme using a trough of 2, if you edge-click on the scrollbar in firefox it won't respond - BUT - in other applications, edge-clicking will cause the scrollbar to jump, but you still cannot click on the scrollbar
[23:59] <psyke83> it must be a problem with firefox's gtk implementation. I'm recompiling libgtk2.0-0 with the proposed patch and will check this for certain
[23:59] <psyke83> should I file a new bug, or mention it in the same report and assign to firefox?


[06:49] <dholbach> good morning
[08:06] <iftikhar-tutul> In ubuntu , I have installed vmware and configured one vmware machine which is also ubuntu and total file size 212GB. After that I copied this whole vmware and paste my windows 7, it shows only 197.5GB. Several times I tried it and got the same result. I don't know what's wrong? Is there any file missing? But, it shows no error or any message while copying. please help me
[08:30] <dholbach> iftikhar-tutul, I'd recomment to ask in #ubuntu
[08:31] <dholbach> dpm, got time for the call today? :)
[08:33] <dpm> dholbach, yes, sorry for the delay
[08:35] <dholbach> no worries
[08:36] <dpm> dholbach, coming for real now, I was just wrapping up a discussion about translations on desktop
[08:36] <dholbach> a likely story
[08:36] <dholbach> :-P


[01:35] <nixternal> DarkwingDuck: pong
[01:35] <nixternal> getting ready to eat so i might be afk for a few
[02:06] <DarkwingDuck> nixternal: can you upload any and everything you have worked on and update https://wiki.kubuntu.org/Kubuntu/Todo/Natty so I have a snapshot of where we stand as I go into 48 hours of docbook?
[03:10] <c2tarun> I was building kde4libs and I got this error http://pastebin.com/kGidy8LF, when I looked I found that on the location instead of backend there is folder name helper, file inside helper is kauth_helper_plugin.so can anyone please help :/
[03:18] <c2tarun> I am asking this question again on #ubuntu-motu if anyone found the solution please reply there. thank you
[04:21] <c2tarun> Riddell: please dont turn of that maverick ec2, I'll be back shortly. Thank you :)
[08:54] <bambee> morning
[08:54] <skfin> Good morning
[09:24] <Riddell> 4.6.2 release day today
[09:24] <jussi> :)
[09:26] <ulysses> not yesterday?
[09:46] <c2tarun> I was building kde4libs and I got this error http://pastebin.com/kGidy8LF, when I looked I found that on the location instead of backend there is folder name helper, file inside helper is kauth_helper_plugin.so can anyone please help :/
[09:47] <apparle> hey guys, I need to do some interpolation for my project, do you know any library which has interpolation functions?
[09:52] <Riddell> c2tarun: that polkit stuff does change a bit
[09:52] <Riddell> let me look at how we did it in 4.6.1
[10:06] <Riddell> c2tarun: dunno looks much the same, I'll need to compile it here to see what's up
[10:12] <c2tarun> Riddell: I adjusted few install files and its building right now, but actually I commented out the lines which were causing trouble. :/
[10:20] <c2tarun> Riddell: kde4libs built perfectly for natty, but why I am getting these errors in maverick? and what is polkit?
[10:22] <Riddell> polkit is an authentication mechanism, it is known for making incompatible releases, there may be this issue because maverick has a different version than natty
[10:49] <Riddell> c2tarun: kde4libs build fine here without problem
[10:50] <c2tarun> Riddell: on what machine? maverick?
[10:50] <Riddell> on my local chroot, yes maverick
[10:51] <c2tarun> Riddell: well either you are using super computer or ec2 is slow, because I started building it long before posting the error message and its still 64% :(
[10:54] <c2tarun> Riddell: if its build can you please upload it :/
[10:55] <Riddell> c2tarun: running  apt-cache policy libpolkit-qt-1-dev  on your ec2 machine shows me you don't have the polkit from kubuntu-ninjas installed so that's why it didn't get picked up
[10:56] <Riddell> my machine is quad core, ec2 machines are single core
[10:56] <yofel> o/
[10:57] <c2tarun> Riddell: well if its absence is creating problem then it'll be a problem on pbuilder as well, dont you think it should be included in build-depends
[10:57] <yofel> c2tarun: what did you mean yesterday that you did what I already did?
[10:57] <Riddell> yofel: he was looking at the old version, nothing to worry about
[10:57] <yofel> ah ok
[10:57] <c2tarun> yofel: actually I saw a package with versino 4.6.1 and I thought its 4.6.2 :) I misreaad
[10:58] <yofel> heh
[10:58] <Riddell> c2tarun: yes you could say that
[10:58] <c2tarun> Riddell: ok, so if it build successfully there, are you uploading it to ppa?
[10:58] <Riddell> yes I've uploaded it
[10:59] <Riddell> also to your ec2 machine
[11:01] <c2tarun> Riddell: thanks :)
[11:01] <yofel> Riddell: is ~ppa1~maverick1 our new naming scheme?
[11:01] <Riddell> c2tarun: it's in ~jr on your ec2 machine if you want to install it and get onto kdepimlibs
[11:02] <c2tarun> Riddell: yup I am on it
[11:02]  * yofel backports meta-kde
[11:02] <Riddell> yofel: oh I got it the wrong way around didn't I?
[11:03] <yofel> Riddell: well, I was confused as you uploaded a ~ppa1~maverick1 now and bambee uploaded a ~maverick1~ppa1 2h ago
[11:03] <c2tarun> Riddell: biggest problem is accessing ktown ftp without my ssh key on that system, is there any solution for that? or I have to paste .ssh there
[11:04] <Riddell> c2tarun: you don't need ktown access, get the tars out of kubuntu-ninjas natty packages
[11:04] <c2tarun> Riddell: oh... I forgot :) thanks
[11:06] <yofel> and *who* is working on maverick kde4libs currently? since from what I get 3 people are doing the same thing and nobody put himself on the wiki page...
[11:06] <Riddell> I've done it and I'm editing the wiki page now
[11:06] <c2tarun> how can I pull any package from natty repo on maverick machine :/
[11:07] <c2tarun> without editint /etc/apt/sources.lit
[11:07] <c2tarun> without editint /etc/apt/sources.list
[11:07] <Riddell> c2tarun: by adding the deb-src line for kubuntu-ninjas natty to sources.list
[11:07] <c2tarun> ok
[11:07] <stikonas> can anybody help me with rekonq?  If I run rekonq from command line then version 0.7.0 launches but if I run it from KDE menu then version 0.6.85 launches
[11:08] <stikonas> and find /usr -type f -name 'rekonq' -print   prints only /usr/bin/rekonq
[11:08] <yofel> stikonas: what does 'which rekonq' say?
[11:08] <Riddell> stikonas: I expect that's some kdeinit fun
[11:08] <stikonas>  /usr/bin/rekonq
[11:08] <yofel> hm...
[11:09] <stikonas> I can't find any other executable in the path, that is what is strange
[11:09] <stikonas> and after aptitude purge rekonq, ir doesn't launch neither from GUI nor from command line
[11:11] <jussi> anyone know if koffice/calligra does proper MSoffice format stuf yet?
[11:14] <Riddell> jussi: it has supported MS Office formats for years
[11:15] <Riddell> now this iss scary, upgraded to 4.6.2 and logged out and X stopped taking input again
[11:15] <Riddell> but this time on reboot X is ok which wasn't the case yesterday
[11:16] <stikonas> ok, thanks for that kdeinit fun, I think I will be able to find now what goes wrong
[11:16] <jussi> Riddell: really? last time I checked I couldnt save as anything but rtf, and importing wasnt supported... (unless I was "doing it wrong"TM )
[11:17] <c2tarun> Riddell: is kdelibs5-dev (>= 4:4.5.85) and kde4libs are different packages?
[11:18] <Riddell> c2tarun: kdelibs5-dev is the binary from kde4libs
[11:18] <jussi> ahh, so it seems to open them ok, but I cant seem to save as Msoffice formats.  :(
[11:18] <c2tarun> Riddell: so if kde4libs is installed it shouldn't ask for kdelibs5-dev
[11:19] <yofel> you can't install kde4libs as that's only a source package, you can install kdelibs5-dev as it's a binary package
[11:19] <c2tarun> Riddell: oh... its not installed.
[11:21] <c2tarun> Riddell: ec2 machine is of 32 bit I guess and you uploaded binaries to it for 64-bit. They are still unavailable from the ppa, I'll will wait for sometime
[11:25] <Riddell> ah, fooey
[11:47] <steveire> Everyday at midnight Quassel dies.
[11:47] <steveire> I wonder why my blog didn't show up on planet ubuntu
[11:50] <steveire> Ah, it arrived now
[11:50] <steveire> Strange
[12:02] <c2tarun> Riddell: kde4libs build succesfully on ninja ppa, but still I am not able to install it on ec2 by apt-get install
[12:03] <Riddell> did you run apt-get update?
[12:04]  * Riddell prepares 4.6.2 for upload to natty
[12:05] <jussi> steveire: how old core are you running? I remember that issue was fixed a _long_ time ago.
[12:05] <jussi> steveire: http://bugs.quassel.info/issues/344
[12:06] <c2tarun> Riddell: yup
[12:07] <yofel> jussi, steveire: I actually got a crash too here, I'm using git client though (only the client crashes)
[12:08] <jussi> yofel: thats weird, please get a bug onto the bug tracker. (and a nice backtrace)
[12:08] <yofel> jussi: I forgot to save the trace, was an assertion from what I saw, I'll see if it happens again
[12:08] <jussi> it should drop a backtrace into ~/.config/quassel-irc.org
[12:09] <steveire> I'm using quassel from natty
[12:09] <c2tarun> Riddell: why I am not able to install it?
[12:10] <Riddell> c2tarun: I don't know, maybe it's not published yet
[12:10] <c2tarun> Riddell: how much time will it take?
[12:11] <steveire> http://dpaste.org/gEt3/ Funny :)
[12:11] <jussi> steveire: as I said to yofel, if you can get a backtrace, please report the bug on http://bugs.quassel-irc.org/
[12:11] <yofel> jussi: oh yeah, I forgot about that ^^
[12:11] <yofel> Fatal: ASSERT: "!_ircChannel && ircChannel" in file /build/buildd/quassel-0.8~alpha+81-g393ac8b/src/client/networkmodel.cpp, line 532
[12:12] <yofel> c2tarun: they are published
[12:12] <yofel> at least the amd64 ones here
[12:12] <steveire> "!_ircChannel && ircChannel" << That's the funny part
[12:12] <jussi> yofel: over to #quassel ;)
[12:13] <steveire> Ah, I didn't see the underscore before
[12:14] <c2tarun> yofel: how can I check whether its published or not?
[12:14] <Riddell> c2tarun: I installed it
[12:14] <c2tarun> Riddell: where on ec2?
[12:15] <yofel> c2tarun: https://launchpad.net/~kubuntu-ninjas/+archive/ppa/+packages - see that the build status is OK for kde4libs?
[12:15] <Riddell> c2tarun: yes
[12:16] <c2tarun> Riddell: how :/ still on running sudo apt-get install kde4libs I am getting error. :( can you just please explain me why I am getting this?
[12:16] <Riddell> c2tarun: kde4libs is a source package
[12:16] <Riddell> kdelibs5-dev is the package to install
[12:18] <c2tarun> well why source package name and package name to install is different?
[12:19] <yofel> c2tarun: while usually source and binary packages have the same name for small packages, a source package may build several binary packages, like here for kdelibs
[12:20] <yofel> c2tarun: in this case you can't very well name all binary packages the same, can you?
[12:20] <c2tarun> yofel: nope
[12:20] <yofel> and depending on the package, it might even make sense to not have a binary package with the same name as the source package, like in our case
[12:24] <yofel> bbl
[12:24] <c2tarun> yofel: ok, if I want to find binary name of some package? what should I do? look at the debian/control file?
[12:25] <yofel> c2tarun: apt-cache showsrc <source_package> will tell you what binary packages it built
[13:16] <c2tarun> Riddell: what is the issue with kdegraphics, you wrote missing symbols. Should I pack it for maverick?
[13:21] <Riddell> c2tarun: yes it needs packaged
[13:21] <Riddell> did you do kdepimlibs?
[13:21] <c2tarun> Riddell: yup its in ppa
[13:22] <Riddell> groovy
[13:26] <c2tarun> Riddell: i just picked kdebindings and it requires python-qt4 (>= 4.8.3) which is not in maverick but in natty. :/
[13:26] <c2tarun> should I pack the version in natty for maverick first?
[13:26] <yofel> c2tarun: we don't backport kdebindings
[13:27] <yofel> not really doable, use what's already in the ppa
[13:28] <c2tarun> yofel: I dont understand, what do you mean by we dont backport?
[13:29] <yofel> c2tarun: you would first need to backport SIP for pyqt4 and kdebindings, but SIP won't build until you fix dh_python3 in maverick. Have fun
[13:29] <c2tarun> yofel: fix dh_python3, that sounds scary..... I think I should leave this pacakge and take another one ;)
[13:30] <yofel> c2tarun: yes, you want to do that ;)
[13:30] <bambee> Riddell: our packages conflicted... this morning I have backported kde4libs into maverick and you too... (it's my fault I did not update the wiki page o_O)
[13:31] <Riddell> bambee: well as long as one of us got it in
[13:31] <yofel> both got it in actually ^^
[13:31] <yofel> ~ppa1~maverick1 was just greater than ~maverick1~ppa1 :P
[13:31] <Riddell> oh, bad me
[13:32] <bambee> :)
[13:33] <yofel> c2tarun: geh, someone of us ignored the editing warning on the wiki, can you please resolve the conflicts?
[13:34] <c2tarun> yofel: sure, but how? :/
[13:34] <yofel> nvm, took care of it
[13:35] <yofel> next time: just edit it again and merge the conflicting parts by hand
[13:45] <bambee> May be I am wrong ... kdebase has been versionned with "~ppa1" into archives (or launchpad says crap)
[13:45] <bambee> or I seriously need coffee ...
[13:45] <bambee> :)
[13:48] <Riddell> oh, bah
[14:18] <c2tarun> Riddell: I think I got the symbol issue with kdegraphics that you mentioned http://pastebin.com/1K6U4LMa :(
[14:21] <Riddell> c2tarun: pkgkde-symbolshelper batchpatch -v 4:4.6.2-0ubuntu1~maverick1~ppa1 ../*build
[14:23] <c2tarun> Riddell: what is that/
[14:23] <c2tarun> ?
[14:24] <yofel> c2tarun: http://pkg-kde.alioth.debian.org/symbolfiles.html
[14:30] <c2tarun> yofel: what exactly are symbols? that page teaches how to work with symbols
[14:33] <yofel> c2tarun: symbols are used to find the program functions the the binary files/libraries. nm -D /usr/lib/libkdecore.so.5 will give you a list of the symbols the file has for example. nm -DC will resolve them to the original c++ function names
[14:33] <yofel> s/the the/in the/
[14:33] <kubotu> yofel meant: "c2tarun: symbols are used to find the program functions in the binary files/libraries. nm -D /usr/lib/libkdecore.so.5 will give you a list of the symbols the file has for example. nm -DC will resolve them to the original c++ function names"
[14:34] <yofel> c2tarun: our symbol files are there to make sure that a library doesn't just drop functions/symbols without us noticing. As the package would need a bump of the library version then usually
[14:37] <c2tarun> yofel: sorry not getting, what do you mean by program functions? (are they simple functions?)
[14:38] <shadeslayer> Riddell: it won't, i just have to fix the url in the twitter settings online, done :)
[14:39] <steveire> Riddell: I don't get the akonadi self test dialog today, but I do still get the kwallet error.
[14:39] <Riddell> steveire: hmm, progress of sorts
[14:39] <Riddell> steveire: I thought you said that patch should fix both?
[14:39] <steveire> I did say it should, yes :)
[14:40] <steveire> There may be other synch calls that I didn't catch
[14:40] <yofel> c2tarun: take for example one of the c++ function from there:
[14:40] <yofel> OrgKdeKLauncherInterface::OrgKdeKLauncherInterface(QString const&, QString const&, QDBusConnection const&, QObject*)
[14:40] <yofel> if you compile the library, the compiler will make a computer recognizable unique string out of it, the symbol:
[14:40] <yofel> _ZN24OrgKdeKLauncherInterfaceC2ERK7QStringS2_RK15QDBusConnectionP7QObject
[14:40] <yofel> that is then used by the linker to bind a call for that function in an application to the library
[14:41] <c2tarun> yofel: ok, so this computer recongnizable unique string are symbols?
[14:42] <yofel> somewhat, yes, someone else might be able to explain that better I hope
[14:42]  * yofel is off for lunch
[14:42] <c2tarun> can anyone help me understanding what are symbols please :(
[14:42]  * c2tarun mean how do they work
[14:48] <Riddell> is a symbol goes missing it means the library has lost some functionality and we need to recompile everything that uses that library
[14:48] <Riddell> in this case the differences are due to the different gcc version so it's not an issue
[14:49] <c2tarun> Riddell: when we build a package symbols files are generated during compilation, right?  So how can anything go wrong when its compiling fine.
[14:50] <tsimpson> c2tarun: if someone changes the code between versions, the symbols change
[14:50] <tsimpson> symbols are basically names for locations in code, they are usually functions but can also be data
[14:50] <tsimpson> if an executable or library can no longer find them, then obviously it won't run
[14:51] <c2tarun> tsimpson: ok, just tell me one thing please, how symbols files are generated? (this may help me understand)
[14:52] <tsimpson> symbols are "exported" from compiled code, the exported symbols are the ones that are accessible from outside the library/program, the binary file(s) contain a table of these symbols
[14:53] <tsimpson> symbol files are basically a textual representation of that table
[14:53] <tsimpson> except symbol files can also contain which package version the symbol first appeared in, so dpkg knows what is the minimum version needed
[14:55] <Riddell> c2tarun: we make the symbols files when we first package a library following the procedure at http://pkg-kde.alioth.debian.org/symbolfiles.html
[14:56] <Riddell> c2tarun: for each new version we check if the symbols files need updated and if any of the missing symbols is a problem
[14:59] <c2tarun> Riddell: I think I am getting now, first thing symbols are for libraries and these symbols are used for packages. right? we make symbols while packaging the libraries and if there is any change in libraries then that needs updating symbols file also. am I right? :/
[14:59] <Riddell> c2tarun: yes
[15:00] <tsimpson> the symbols are created by the compiler and linker, but we create the file that contains a list of symbols
[15:00] <c2tarun> got if :) thanks everyone going to read working with symbols
[15:26] <steveire> Riddell: It's possible that the wallet bug is fixed for normal people but not for kolab accounts
[15:26] <Riddell> I'll try out a daily CD when I get a chance
[15:44] <Riddell> kde-l10n uploading to natty
[15:44]  * maco corsses fingers
[15:44] <maco> today, the bf's sister is introduced to Plasma Netbook
[15:45] <maco> UNR lucid was too buggy and annoying for her, so now she's beta testing kubuntu natty on her netbook
[15:45] <maco> (which means i still havent seen unity in action)
[15:46] <sikon> I... wasn't impressed by Unity back in Maverick, but things could have changed y now
[15:47] <Riddell> maco: at least you can blame any bugs on it being beta :)
[15:51] <Tm_T> sikon: gnome guys in my LoCo are bashing Unity ):
[15:52] <lucidfox> Eep, why was sikon? O_O
[15:52] <lucidfox> * I
[15:52] <Tm_T> lucidfox: evil personality did take over when login?
[15:52] <Tm_T> I've heard lots about unstability in Unity, cannot say else about it
[15:53] <lucidfox> I consider the GNOME stack enough of a mess these days to use exclusively Kubuntu
[15:53] <lucidfox> I was in a similar situation back around the release of KDE 4.0...
[15:56] <maco> i was going to give her unity, and then i remembered the bugginess...
[15:58] <Tm_T> lucidfox: I liked 3.50.50 (:
[16:12] <c2tarun> Riddell: can you please take a look at debdiff of kdegraphics http://pastebin.com/esAG7ShS I am uploading it to ppa.
[16:14] <Riddell> c2tarun: that's fine
[16:16] <c2tarun> Riddell: should I take kdebase for maverick?
[16:16] <Riddell> c2tarun: that needs -workspace first I think
[16:17] <c2tarun> Riddell: so workspace first!!
[16:17] <Riddell> c2tarun: I've just finished that
[16:18] <c2tarun> Riddell: thats great :) I'll wait for you to upload it :) meanwhile I'll take kdeartwork
[16:18] <Riddell> also needs -workspace, see https://wiki.kubuntu.org/Kubuntu/Ninjas/DependencyGraph
[16:19] <c2tarun> sorry I was on edit option so this link was not available
[16:20] <c2tarun> Riddell: ok :) so I'll simply wait till you upload it
[16:22] <Riddell> uploaded now but will need to wait for it to compile
[16:22] <c2tarun> Riddell: ok, meanwhile going to grab some coffee :)
[16:59] <Riddell> hello tim_
[16:59] <tim_> hi!
[17:02] <tim_> Riddell: do you know if a new version of kdepim will enter kubuntu-ppa/backports?
[17:03] <Riddell> tim_: there's no kdepim release scheduled yet
[17:03] <Riddell> ScottK: do you know what "Add udev (>= 166-0ubuntu4) to kdm Depends" is about in kdebase-workspace?
[17:04] <Quintasan> OH YEAH
[17:04] <Quintasan> sponsorship
[17:05] <tim_> What about the "HTML copy bug", will it be fixed? As far as I know it is fixed in the upstream Version?!
[17:05] <Riddell> Quintasan: oh?
[17:05] <Riddell> tim_: steveire might be able to answer that
[17:05] <Quintasan> Riddell: I've just got mail confirming they want to sponsor my trip etc.
[17:06] <Riddell> golly
[17:06] <steveire> tim_: I don't know about the packages, but if it's fixed upstream I'm ure it will get to the ppa
[17:06] <Riddell> Quintasan: as your reward I nominate you to start a KubuntuOnericSpecs wiki page!
[17:06] <Quintasan> @_@
[17:06] <Quintasan> Riddell: Can I get to it tomorrow?
[17:06] <Riddell> Quintasan: yes
[17:07] <tim_> thanks!
[17:08] <Quintasan> Riddell: Or wait, I will forget about it, I might as well start doing it now.  KubuntuOnericSpecs as in Ubuntu One client?
[17:09] <Riddell> Quintasan: as in a page for people to list sessions they want at UDS
[17:10] <Quintasan> Riddell: oh, Oneric sound strange to me
[17:11] <Riddell> oneiric
[17:12] <Riddell> I was missing an i
[17:12] <ulysses> OO could be Old Obi-van
[17:13] <Quintasan> That's even more confusing
[17:13] <ulysses> but it's from Star Wars!
[17:14] <Quintasan> Riddell: Can we have it like this -> https://wiki.kubuntu.org/Kubuntu/Specs/UDS-O ?
[17:15] <Quintasan> omfg
[17:15] <Quintasan> oneiric is the codename of next Ubuntu -_-'
[17:15] <maco> um...yes...
[17:16] <maco> did you think he was just putting gibberish in the example-wiki-page name?
[17:16] <Quintasan> Yeah :P
[17:17] <Riddell> Quintasan: yes
[17:24]  * c2tarun taking kdebase for maverick
[17:25] <c2tarun> Riddell: you building kdebase?
[17:25] <Riddell> c2tarun: not yet, go ahead and take it from me
[17:25] <c2tarun> Riddell: ok
[17:26] <c2tarun> Riddell: one more question, why are you rebuilding kdepim?
[17:28] <Riddell> c2tarun: the new akonadi changed library symbols so it needs a rebuild
[17:31] <bambee> Riddell: I will backport kdebindings,kdesdk and kdeutils into maverick when I back to home (I updated the wiki page)
[17:32] <Riddell> bambee: I think kdebindings won't work, needs too many other things updated
[17:32] <bambee> ohh really ?
[17:32] <Riddell> 13:29 < yofel> c2tarun: you would first need to backport SIP for pyqt4 and kdebindings, but SIP won't build until you fix dh_python3 in maverick. Have fun
[17:32] <bambee> arrff
[17:32] <bambee> well
[17:33] <bambee> ok so just kdesdk and kdeutils
[17:36] <c2tarun> Riddell: is anyone fixing dh_python3?
[17:36] <bambee> Riddell: also I am a bit confused : maverick backports must be versioned as ~maverick1~ppa1 or ~ppa1~maverick1 ?
[17:37] <c2tarun> bambee: I think first one
[17:37] <bambee> c2tarun: me too, however some backports are ~ppa1~maverick1, that's why I am asking :)
[17:38] <c2tarun> bambee: actually Riddell told me in morning :)
[17:38] <bambee> ok
[17:38] <bambee> thanks
[17:38] <Riddell> ~maverick1~ppa1 is right, I got it wrong earlier
[17:40] <c2tarun> Riddell: is anyone working on dh_python3?
[17:57] <Riddell> c2tarun: I don't think it's worth it
[17:57] <c2tarun> ohh.... :)
[18:48] <c2tarun> bambee: you should update that page when you upload a package :( I packed kdebase which you already packed two days ago.
[18:48] <bambee> ohhh...
[18:48] <bambee> sorry xD
[18:49] <c2tarun> bambee: np :) just for no conflicts I am building kdenetwork :)
[18:49] <bambee> okay
[18:49] <c2tarun> Riddell: you were building a package which bambee uploaded :/
[18:49] <bambee> I am packaging kdesdk+kdeutils
[18:50] <c2tarun> bambee: I saw that :)
[18:50] <bambee> c2tarun, Riddell: feel free to blame me when I don't upload the page or when I do something wrong...
[18:50] <bambee> :)
[18:51] <c2tarun> bambee: its not blaming :) its just why double a work when there is plenty
[18:51] <bambee> for the love of the art... :P
[18:52]  * bambee => [ ]
[18:53] <c2tarun> :P
[18:54] <c2tarun> is this a linker error? http://paste.kde.org/9061/
[18:55] <c2tarun> gcc version on ec2 I am using is 4:4.4.4-1ubuntu2
[18:55] <bambee> c2tarun: no a compiler error
[18:55] <c2tarun> bambee: why I am getting this error?
[18:56] <c2tarun> I mean is there something missing?
[18:56] <bambee> probably a bad dependency is used (incorrect version)
[18:57] <bambee> c2tarun: did you try with pbuilder (with a maverick basetgz)
[18:57] <bambee> ?
[18:58] <c2tarun> bambee: nope, its kind of a clean ec2.
[18:58] <c2tarun> why pbuilder?
[19:01] <c2tarun> bambee: ping
[19:02] <bambee> because with pbuilder it's built into a new and clean environnement without any pre-installed dependencies, it's easier to check errors
[19:02] <c2tarun> bambee: ok, let me try it with pbuilder, but I dont think it will do any good and I'll end up with this error :(
[19:03] <bambee> c2tarun: kdenetwork builds for natty so it's not a programming error :)
[19:03] <c2tarun> bambee: yeah you are right too
[19:03] <bambee> that's why I said that you probably missed something ;)
[19:03] <c2tarun> bambee: let me upgrade that ec2 first. may be that solve the probl
[19:05] <Riddell> c2tarun: I think the version in the PPA for natty has a wrong patch in it
[19:05] <Riddell> run   quilt pop
[19:05] <Riddell> then remove the patch in debian/patches
[19:06] <Riddell> and edit debian/patches/series
[19:06] <Riddell> and rebuild
[19:47] <c2tarun> bambee: kdesdk failed to build, https://i68471862.restricted.launchpadlibrarian.net/68471862/buildlog_ubuntu-maverick-amd64.kdesdk_4%3A4.6.2-0ubuntu1~maverick1~ppa1_FAILEDTOBUILD.txt.gz?token=a2f09ae286feb12978427de474032db6 please take a look
[19:57] <yofel> c2tarun: symbols again
[19:57] <c2tarun> yofel: yup, bambee was onto it, so I thought remind him :)
[19:58] <c2tarun> yofel: in this case also I think updating symbols will work? isnt it?
[19:59] <yofel> yep
[20:03] <bambee> c2tarun: w00t indeed
[20:03] <c2tarun> bambee: w00t??
[20:04] <bambee> s/w00t//
[20:04] <kubotu> bambee meant: "c2tarun:  indeed"
[20:04] <bambee> :)
[20:06] <Quintasan> godamn
[20:06] <Quintasan> how do I parse for \ in regexp?
[20:07] <Quintasan> I want to look up the "\"
[20:11] <yofel> \\ I would guess, depending on the syntax
[20:28] <bambee> c2tarun: should be fixed now
[20:28] <bambee> (kdesdk)
[20:28] <c2tarun> bambee: upload it :) we'll see
[20:29] <bambee> c2tarun: It has been uploaded
[20:32] <c2tarun> bambee: I dont think there is any packaging work left. ?
[20:34] <bambee> c2tarun: kde-l10n ?
[20:34] <c2tarun> bambee: ok I'll take it
[20:34] <bambee> crap... my packaged was rejected... I've to do a bumpfor that ? o_O
[20:34] <bambee> s/packaged/package/
[20:34] <kubotu> bambee meant: "crap... my package was rejected... I've to do a bumpfor that ? o_O"
[20:36] <c2tarun> bambee: where is the new tarball for kde-l10n?
[20:36] <c2tarun> its not in ktown
[20:36] <bambee> I don't know
[20:38] <c2tarun> hmm....
[20:42] <c2tarun> Riddell: ping
[20:47] <c2tarun> apachelogger_: ping
[20:47] <bambee> c2tarun: ktown => stable/4.6.2/src/kde-l10n
[20:48] <c2tarun> bambee: oh... I missed it :(
[20:48] <bambee> c2tarun: see also https://wiki.kubuntu.org/Kubuntu/Ninjas/Packaging/L10nOperatorGuide
[20:49] <c2tarun> bambee: what is so special about l10n? that there is a whole wiki page?
[20:52] <bambee> c2tarun: you really want to download 53 tarballs and package them ? it's an automatic way
[20:52] <bambee> read the wiki page
[20:52] <bambee> you will understand
[20:52] <c2tarun> 53 O_O
[20:52] <ulysses> the announcement tells there is more than 55:P somebody lies
[20:53] <bambee> :P
[20:54] <c2tarun> :P
[20:54]  * c2tarun reading wiki
[20:58] <yofel> c2tarun: I can take care of kde-l10n if you want, I know how it works (somewhat)
[20:59] <c2tarun> yofel: sure :) but I'll be very thankful if you allow me to try it once, if it failed I'll surely ping you.
[20:59] <yofel> sure, but setup a gpg agent before trying it, or you'll have to input your gpg key password a hundred times for debsign
[21:00] <yofel> (or maybe someone knows a different solution for that, that's mine)
[21:01] <c2tarun> yofel: I'll copy my .gnupg and .ssh in that ec2 and then after evrything is finished I'll delete it :)
[21:01] <yofel> well, have fun
[21:02] <c2tarun> yofel: sure :)
[21:03] <yofel> we *usually* don't upload kde-l10n to ninjas though, too much work, it goes straight to the backports ppa when we copy the packages
[21:03] <c2tarun> yofel: I'll tell you when build is successful
[21:03] <yofel> sure, the script will take quite a while to finish anyway
[21:05] <yofel> c2tarun: also, kde-l10n *is* on ktown, it's in a subfolder
[21:05] <yofel> one source per language
[21:06] <yofel> err, I should read the whole backlog, nvm...
[21:09] <c2tarun> yofel: where can I get the debian folder?
[21:10] <yofel> c2tarun: as it says on the wiki page, you want to get https://code.launchpad.net/~kubuntu-members/kubuntu-dev-tools/kde-l10n-common-maverick
[21:10] <yofel> hm, why is that still owned by -members...
[21:10] <c2tarun> yofel: I am going to pack for natty first
[21:11] <yofel> c2tarun: Riddell already uploaded that
[21:11] <yofel> you *want* to read natty-changes
[21:11] <yofel> as I said, kde-l10n doesn't go to ninjas, so don't expect it there
[21:12] <c2tarun> yofel: sorry, I checked it there, and if Riddell uploaded it well where can I see it?
[21:12] <yofel> c2tarun: https://lists.ubuntu.com/archives/natty-changes/2011-April/date.html scroll to the bottom
[21:13] <yofel> there's also an RSS feed http://feeds.ubuntu-nl.org/NattyChanges if you don't like mailing lists
[21:14] <c2tarun> yofel: and what about maverick?
[21:14] <yofel> that goes to kubuntu-ppa/backports when we release the packages
[21:15] <c2tarun> yofel: I mean he didn't packed it for maverick didn't he?
[21:16] <yofel> no, he didn't
[21:16] <yofel> https://launchpad.net/~kubuntu-ppa/+archive/backports/+packages shows the 4.6.1 packages still
[21:17] <yofel> c2tarun: are you a kubuntu-member though?
[21:17] <c2tarun> yofel: nope ;(
[21:18] <yofel> hm, well you can request a merge and I can review that when you need to commit, you can't run the script without commiting your changes first
[21:20] <c2tarun> yofel: its written there Members of Kubuntu Members can upload to this branch.
[21:20] <c2tarun> so it mean I cant
[21:20] <yofel> c2tarun: yes, but that's true for all other packaging branches too
[21:20] <yofel> so just do it like you did for the others
[21:21] <c2tarun> yofel: ok, so I got that branch and that got me the debian folder, now I have to get kde-l10n folder from ktown and then run that script in debian folder.
[21:21] <c2tarun> an I right?
[21:21] <yofel> Riddell: when are we going to start using ~kubuntu-packagers?
[21:21] <yofel> c2tarun: you first need to update the changelog and commit that
[21:22] <yofel> *then* you can run the script
[21:22] <c2tarun> ok.
[21:22] <yofel> as the script makes a fresh checkout from the branch, so all uncommitted changes are ignored
[21:26] <ScottK> Riddell: I think it was related to upstart changes, but it may be related to multi-arch.
[21:29] <c2tarun> yofel: I made changes to changelog, how to commit?
[21:30] <yofel> c2tarun: how did you commit changes for kdebase etc.
[21:30] <c2tarun> yofel: I simply uploaded them to kubuntu-ninjas ppa.
[21:30] <c2tarun> :/
[21:30] <yofel> c2tarun: er... do you remember our discussion about merge requests?
[21:31] <c2tarun> yofel: yup, I remember about adding file first by bzr add
[21:31] <c2tarun> but here I am gettin error
[21:31] <yofel> ahh, you probably don't have your bzr config on ec2 :S
[21:32] <yofel> I would make a local checkout on your PC, update that, commit, and then fetch the branch on ec2 once I merge your changes
[21:32] <c2tarun> yofel: may be, one question, do I have to make changes in changelog after moving debian folder inside kde-l10n?
[21:33] <yofel> why would you move the folder?
[21:33] <c2tarun> yofel: because I am getting this error bzr: ERROR: Not a branch: "/home/ubuntu/kde-l10n/kde-l10n/debian/changelog/".
[21:33] <yofel> you don't move the folder
[21:34] <yofel> or you would need to unpack every language, copy the folder there, edit changelog etc....
[21:34] <yofel> the script does that
[21:34] <c2tarun> yofel: ok changelog file is added by bzr add now,
[21:36] <yofel> good then push to lp
[21:39] <seaLne> steveire: have you come accros a probelm that if kontact starts before a network is available it won't ever manage to fetch imap even after network is available? you need to quit and restart it. this is 4.4 in natty. looosing network after it has started isn't a problem as it works again on reconnection
[21:40] <c2tarun> yofel: bzr: ERROR: Permission denied: "~kubuntu-members/kubuntu-dev-tools/kde-l10n-common-maverick~ppa1/": : Tarun K. Mall is not a member of Kubuntu Members :(
[21:41]  * c2tarun why I am not kubuntu member ;(
[21:41] <yofel> c2tarun: bzr push lp:~c2tarun/kubuntu-dev-tools/kde-l10n-maverick-4.6.2
[21:44] <yofel> c2tarun: did you push?
[21:44] <c2tarun> yofel: I think, I am looking for where I pushed :/
[21:44] <yofel> c2tarun: https://code.launchpad.net/~c2tarun/kubuntu-dev-tools/kde-l10n-maverick-4.6.2
[21:44] <yofel> did you get an error?
[21:45] <yofel> if it's about different rich-root ... something... push again
[21:45] <c2tarun> yofel: here is what I got http://paste.kde.org/9091/
[21:45] <c2tarun> yup
[21:45] <yofel> yeah, run the same push command again, will work this time
[21:46] <c2tarun> yofel: yup its done this time :)
[21:47] <yofel> k, propose that for merging into lp:~kubuntu-members/kubuntu-dev-tools/kde-l10n-common-maverick
[21:50] <c2tarun> yofel: I did https://code.edge.launchpad.net/~c2tarun/kubuntu-dev-tools/kde-l10n-maverick-4.6.2/+merge/56651
[21:52] <yofel> c2tarun: you did not update the svn revision
[21:52] <yofel> see step 2 on the wiki page
[21:53] <c2tarun> yofel: looking
[21:59] <c2tarun> yofel: https://code.edge.launchpad.net/~c2tarun/kubuntu-dev-tools/kde-l10n-maverick-4.6.2/+merge/56651 here please take a look
[22:02] <c2tarun> yofel: ok thanks :) what now just executing that script?
[22:02] <yofel> c2tarun: yep, should be enough
[22:03] <yofel> you run the build script as said on the wiki page, after that ignore the last step since that's for the archive
[22:03] <yofel> for the PPAs you'll need to debsign the packages and upload them to the ppa later
[22:04] <c2tarun> yofel: http://paste.kde.org/9092/
[22:04] <c2tarun> I got this error
[22:05] <yofel> .. give me a sec
[22:08] <yofel> c2tarun: try again
[22:09] <c2tarun> yofel: again same :(
[22:10] <yofel> really? Then just drop the packaging and use a fresh checkout
[22:10] <yofel> your changes are in the branch after all
[22:10] <c2tarun> hmm....
[22:16] <c2tarun> yofel: is there any other packaging work left?
[22:17] <yofel> not for 4.6.2 at least I think
[22:17] <c2tarun> so there is nothing else to do?
[22:18] <yofel> well, 4.6.2 is done, maybe Riddell knows if something else needs to be done
[22:19] <c2tarun> Riddell: ping
[22:19]  * yofel retries kdetoys
[22:20] <yofel> hm, the libqjson-dev build-dep in kdeutils has a really unlucky version choice :S
[22:21] <yofel> c2tarun: you can fix kdesdk if you want
[22:21] <yofel> esp. since bambee's gone
[22:21] <c2tarun> yofel: yup, I was looking into it, bambee is not here I guess.
[22:21] <yofel> I'll take kdeutils
[23:29] <Riddell> evening
[23:29] <Riddell> where are we at?
[23:30] <c2tarun> Riddell: are there any other packaging works?
[23:30] <Riddell> now it needs testing
[23:31] <c2tarun> Riddell: how can I do that?
[23:31] <Riddell> c2tarun: install it and run it
[23:32] <c2tarun> ok, I'll do it, anyother stuff?
[23:32] <Riddell> nope
[23:32] <c2tarun> Riddell: BTW do you know when SoC starts?
[23:33] <Riddell> no, google for soc timeline
[23:34] <c2tarun> Riddell: sorry, what do you mean?
[23:34] <Riddell> to find out I recomend you use google and search for "soc timeline"
[23:39] <yofel> Riddell: hm... a) when are we going to use ~kubuntu-packagers, b) would it make sense to subscribe ~kubuntu-bugs to the kubuntu-ppa bugs? some of us are subscribed to those, but no somewhat official team
[23:42] <c2tarun> Riddell: when can I apply for kubuntu-members?
[23:44] <Riddell> yofel: I think we'll do a mass migration during the new cycle merges
[23:45] <Riddell> c2tarun: usually two months of significant and sustained contribution is requested
[23:46] <yofel> k, sounds good
[23:46] <Riddell> yofel: bug subscriptions always confuse me, that seems sensible I think
[23:49] <yofel> Riddell: an admin needs to do that, you should have a checkbox for that on https://bugs.launchpad.net/kubuntu-ppa/+subscribe


[22:26] <ahoneybun> anyone know anything about ubuntu-co.org?
[22:26] <ahoneybun> it's owned by Canoncial
[22:27] <tsimonq2> ahoneybun: You might want to talk to Emma from System76
[22:27] <tsimonq2> afair she leads that LoCo
[22:27] <ahoneybun> mm I own ubuntu-fl.org so I was wondering
[22:28] <ahoneybun> odd that they did not grab that one before
[22:29] <ahoneybun> I think some adult content site had it for awhile


[09:28] <SilverSpace> dan
[17:22] <sillyslux_> https://www.youtube.com/watch?v=m0ZFAC_SP1M
[17:22] <datase> ^ YouTube :: Kradljivac ljutih umaka - Umak nije Voda :: Duration: 05:02 :: Views: 605 uploaded by 'Juta Spiza :: 11 likes :: 0 dislikes :: 0 favorites


[00:43] <pleia2> Darkwing: pong
[03:23] <toddc> you said that then my KB locked up till I rebooted
[03:23] <toddc> wrong channel
[05:38] <scientes> woot, touchdown on mars
[05:39] <nhaines> Wheels down, with two hires images coming back.
[05:56] <nhaines> That'll be it until Odyssey rises again: http://mars.jpl.nasa.gov/msl/multimedia/raw/
[05:56] <darthrobot> Title: [Mars Science Laboratory: Raw Images]
[05:57] <scientes> https://twitter.com/MarsCuriosity/status/232352290919567361/photo/1/large
[05:57] <darthrobot> Title: [Twitter / MarsCuriosity: No photo or it didn't happen? ...]
[05:58] <scientes> their raw server is hammered