[00:06] <sinzui> wgrant, mumble?
[00:08] <nigelb> Is everyone free to use the LP logo to denote link to Lp profile?
[00:09] <lifeless> wgrant: try this please:
[00:09] <lifeless> sudo rm -rf /var/lib/rabbitmq/mnesia/rabbit/*
[00:09] <lifeless> then start rabbit
[00:09] <nigelb> ah, found the license. Ignore me.
[00:22] <lifeless> wgrant: hi
[00:22] <lifeless> wgrant: have you tried that rabbit fix?
[00:22] <wgrant> lifeless: On a call right now. Will test soon.
[00:22] <lifeless> thanks
[00:31] <michaelh1> lifeless: can't move to London: ash cloud.  Plus, not enough earthquakes...
[01:00] <LPCIBot> Project devel build #832: STILL FAILING in 5 hr 38 min: https://lpci.wedontsleep.org/job/devel/832/
[01:10] <wgrant> :q
[01:11] <wgrant> lifeless: I'm using avahi for now, but any idea how to get the IP address of a guest?
[01:16] <lifeless> cat /var/lib/lxc/$host/var/lib/dhcp3/dhchp3.eth0.leases
[01:16] <lifeless> or check the libvirt dhcp server log/status
[01:17] <wgrant> I was hoping I could inspect the interfaces somehow.
[01:18] <lifeless> ask hallyn in #ubuntu-server?
[01:35] <wgrant> Hmm.
[01:35] <wgrant> Why does avahi get stuck registering on first startup :(
[01:43] <mwhudson> is there a tag for new person picker bugs?
[01:45] <wgrant> person-picker
[01:46] <StevenK> mwhudson: But if you file bugs, wgrant will frown at you.
[01:46] <mwhudson> ah i think it was just https://bugs.launchpad.net/launchpad/+bug/800654
[01:46] <_mup_> Bug #800654: Assign Me link on person picker visible when it should be hidden <disclosure> <picker> <qa-ok> <Launchpad itself:Fix Committed by wallyworld> < https://launchpad.net/bugs/800654 >
[01:46] <mwhudson> ... maybe
[01:47] <StevenK> RARGH, why does apt-mirror feel it needs to download most of the archive?
[01:47] <mwhudson> i guess i should get devel running and see if it happens there
[01:47] <wgrant> mwhudson: Or qastaging.
[01:48] <mwhudson> wgrant: good point
[01:49] <mwhudson> ah bug still present there
[01:49] <mwhudson> the person picker on $team/+addmember has the "assign me" stuff
[01:49] <mwhudson> wgrant: does this sound like a bug you know about?
[01:49] <wgrant> Is that a problem?
[01:49] <wgrant> Apart from the wording?
[01:49] <mwhudson> wgrant: yes, it's the "add member" picker
[01:50] <mwhudson> wgrant: neither "remove assignee" or "assign me" make sense
[01:50] <mwhudson> at all
[01:50] <wgrant> "Assign me" does, except it should be "Pick me" or so.
[01:50] <wgrant> "remove assignee" does not.
[01:50] <mwhudson> well maybe
[01:50] <mwhudson> it's not a /common/ use case for a team
[01:50] <wgrant> wallyworld_: ^^
[01:51] <mwhudson> i guess if you're an owner you might still want to add yourself
[01:51] <wallyworld_> the assign me link has been on the picker for a while. the above bug was to hide it when not needed
[01:52] <wallyworld_> what's the issue with the links? i'm not quite across what is being said above
[01:53] <wgrant> "A while" is about a week, right?
[01:53] <wallyworld_> no, longer
[01:53] <wallyworld_> months
[01:53] <wgrant> No...
[01:53] <wallyworld_> the last epic iirc
[01:53] <wgrant> Only since jcsackett refactored it a couple of weeks ago?
[01:53] <wgrant> Before then it was only on the bugtask assignee picker.
[01:53] <wgrant> AFAIK
[01:53] <wallyworld_> no, the refactoring was to make the code which provided the links better and consistent
[01:54] <wallyworld_> across the picker refactoring
[01:54] <wallyworld_> but the functionality was added last epic
[01:55] <wallyworld_> oh, only the bugtask picker
[01:55] <wallyworld_> perhaps that's correct
[01:55] <wallyworld_> yes, i think so
[01:56] <wallyworld_> so perhaps we should plug the "leak"
[01:56] <wallyworld_> only the bugtask picker needs "Assign Me"
[01:57] <wallyworld_> others may want "Pick Me" as mentioned above, but do we really need that?
[01:57] <mwhudson> http://people.linaro.org/~mwh/silly.png
[01:57] <wallyworld_> my fix for the above bug was for the bugtask case - do not show "Assign Me" if "me" was already assigned to the bug
[01:57] <mwhudson> wallyworld_: should i file a bug?
[01:57] <mwhudson> wallyworld_: yeah, i see that now (about the bug i linked to)
[01:58] <wgrant> https://bugs.launchpad.net/launchpad/+bug/787595
[01:58] <_mup_> Bug #787595: person picker could have a link to choose myself when I am a valid choice <disclosure> <person-picker> <qa-ok> <Launchpad itself:Fix Released by jcsackett> < https://launchpad.net/bugs/787595 >
[01:58] <wgrant> It's new.
[01:58] <wallyworld_> mwhudson: yes please, i think it's bad that way it is atm
[01:58] <wallyworld_> mwhudson: perhaps it's just the wording that is bad
[01:59] <mwhudson> wallyworld_: i beg to differ in this case
[01:59] <mwhudson> wallyworld_: particular when i'm already in the team
[02:00] <wallyworld_> fair point
[02:00] <wallyworld_> could you please include the screenshot in the bug
[02:00] <mwhudson> yay double filing
[02:01] <wallyworld_> that will help reinforce the need for a fix in case whoever reads the bug report can't immediately see the issue
[02:01] <mwhudson> wallyworld_: https://bugs.launchpad.net/launchpad/+bug/801388
[02:01] <_mup_> Bug #801388: some person pickers show "assign me"/"remove assignee" when that makes no sense <Launchpad itself:New> < https://launchpad.net/bugs/801388 >
[02:01] <wallyworld_> thanks.
[02:02] <wallyworld_> i think perhaps the quickest fix is to have those links off by default and only enabled when needed. initially just for bugtask assignee
[02:02] <wallyworld_> we can add other cases as and when required
[02:02] <wgrant> wallyworld_: But jcsackett only made it global three weeks ago, as requested.
[02:03] <wallyworld_> hmmm. but there's been some collateral damage :-)
[02:04] <wallyworld_> certainly "Assign Me" only makes sense in certain contexts
[02:04] <wallyworld_> "Choose Me" is better in other contexts
[02:05] <lifeless> this is polish, and very visible polish at that
[02:05] <wgrant> Indeed
[02:05] <lifeless> wgrant: rabbit test ?
[02:06] <wallyworld_> so, i think: default wording should be "Choose Me". bugtask assignee picker can override wording. select team member picker can disable links
[02:06] <wallyworld_> but the links will remain on by default
[02:07] <wallyworld_> and we can deal with other cases as the arise
[02:07] <wallyworld_> they
[02:19] <wgrant> lifeless: Doesn't help. I think something might be wrong with epmd.
[02:19] <wgrant> rabbit says it starts fine, but the LP side of things can't see it.
[02:23] <lifeless> wgrant: the outer rabbit ?
[02:24] <wgrant> lifeless: By disabling the hardlink restrictions on the host the system rabbit now starts. But the LP rabbit does not.
[02:26] <wgrant> Ah, and it's still broken without aufs.
[02:28] <lifeless> wgrant: so I have similar symptoms
[02:29] <lifeless> the host rabbit I have running and responding to rabbitmqctl
[02:31] <lifeless> Status of node 'tmpMn00ML@lucid-test-lp' ...
[02:31] <lifeless> Error: unable to connect to node 'tmpMn00ML@lucid-test-lp': nodedown
[02:31] <lifeless> is what the test suite sees
[02:31] <wgrant> Yes.
[02:32] <wgrant> Status of node 'tmpp9GAiQ@lucid-lp-temp-uxeO' ...
[02:32] <wgrant> Error: unable to connect to node 'tmpp9GAiQ@lucid-lp-temp-uxeO': nodedown
[02:32] <wgrant> diagnostics:
[02:32] <wgrant> - nodes and their ports on lucid-lp-temp-uxeO: [{rabbit,57084}, {tmpp9GAiQ,41334}, {rabbitmqctl1385,39815}]
[02:38] <wgrant> So, only two aufs-specific problems now. And one of them is fixed by disabling the overzealous hardlink protection.
[02:38] <wgrant> The other is that containers do strange things on reboot unless you remount.
[02:39] <wgrant> Possibly they unmount too aggressively.
[02:39] <lifeless> I had my pg corrupt itself
[02:39] <lifeless> there is a known bug in upstart in lucid
[02:39] <wgrant> I guess I should test the overhead of not using aufs.
[02:39] <wgrant> See how it affects the cache.
[02:40] <wgrant> Are LVM and the block cache friendly enough that snapshots will share cache?
[02:40] <lifeless> AIUI -
[02:40] <lifeless> new blocks written will be distinct
[02:40] <lifeless> reads will be common
[02:41] <wgrant> Let's use btrfs and see what happens.
[02:42] <lifeless> I've found btrfs a little slow
[02:42] <lifeless> anyhow
[02:42] <lifeless> gl
[02:57] <wgrant> Intriguing.
[02:57] <wgrant> Same reboot issue with btrfs.
[02:58] <lifeless> AIUI its a race condition, not fs
[02:58] <lifeless> kill -9 too early
[03:53] <wgrant> lifeless: Ah.
[03:53] <wgrant> lifeless: Shutting down the guest remounts the root FS ro.
[03:53] <wgrant> lifeless: Normally that fails, since there are files open rw on the host.
[03:53] <wgrant> But with aufs/btrfs, the host doesn't usually have rw handles, so the remount succeeds.
[03:54] <lifeless> wgrant: the guest fs ?
[03:54] <wgrant> lifeless: Yes. But that is a tree in a host mount, so it takes the whole mount ro, it seems.
[03:55] <lifeless> thats special; I haven't seen that happen to me
[03:55] <wgrant> Are you running it on an FS that isn't your root fs?
[03:55] <lifeless> no
[03:55] <wgrant> Then you're always going to have files open, so the ro remount will fail.
[03:55] <lifeless> its mount table has nothing but proc etc + the home bind mount
[03:56] <lifeless> bug filing time ;)
[03:56] <wgrant> Possibly.
[03:56] <wgrant> dbus won't start on a btrfs snapshot :(
[03:56] <lifeless> big loss :P
[03:56] <wgrant> Well, means no avahi.
[03:57] <wgrant> Which means I have to go hunting in dhclient's status files for the IP address.
[03:58] <wgrant> Ah, stale pid got caught in the snapshot.
[03:59] <jtv> Anyone mind if the dogfood appserver gets a solid kick?
[04:00] <wgrant> Kill it!
[04:00] <wgrant> Even better if you're QAing your stuff :)
[04:00] <jtv> BTW I finally put LC_ALL in my mawson .profile… what a relief!
[04:00] <wgrant> Yes!
[04:00] <jtv> LC_ALL=C, that is
[04:00] <wgrant> It is a bit spammy otherwise.
[04:00] <jtv> I didn't dare do it for the launchpad user, but…
[04:00] <wgrant> It doesn't matter.
[04:01] <wgrant> It should persist through the sudo.
[04:01] <wgrant> Shouldn't it?
[04:01] <jtv> It does.  Just such a nuisance for everyone to have to do this.
[04:08] <wgrant> Bah.
[04:10] <jtv> Bah indeed.  That branch I needed to Q/A hasn't hit db-devel yet.
[04:11] <jtv> Maybe I'm pulling the wrong df branch.
[04:11] <jtv> I'm going to restart the df appserver again.
[04:12] <wgrant> Well, this bah was because I accidentally deleted the root subvolume and not just the snapshots.
[04:13] <jtv> You accidentally the root volume?
[04:13] <wgrant> Indeed.
[04:13] <jtv> 8 out of 10 doctors recommend not deleting your root volume.
[04:15] <wgrant> Hmm, Sunday is going to be warmish in Dublin, and the rest of the week is only slightly warmer than it is here. What summer!
[04:16] <jtv> hi wallyworld_!  I won't be around much today because of travel stuff.
[04:16] <jtv> wgrant: and "here" means winter, right!
[04:16] <wgrant> jtv: Right.
[04:16] <wallyworld_> jtv: hi, me too. i've been in and out this morning getting stuff sorted
[04:17] <jtv> At the Wellington sprint I kept saying "winter" not because the hemisphere had me confused, but because the weather was so bad.
[04:17] <jtv> It was cold everywhere I went that winter, pretty much all around the world.
[04:17] <jtv> It went onto the books as the hottest winter ever.
[04:18] <mwhudson> the weather in wellington that week was really very horrible for the time of year
[04:18] <mwhudson> heck, it was pretty horrible for any time of year
[04:19] <wgrant> Excuses, excuses.
[04:19] <wgrant> Still.
[04:19] <wgrant> Was better than the 46 we had back home during that week.
[04:24] <wgrant> lifeless: Hmm, it works.
[04:24] <lifeless> econtext
[04:27] <lifeless> wgrant: ^
[04:28] <wgrant> Bah.
[04:28] <wgrant> Thought testr run --parallel was working.
[04:28] <wgrant> Just blew up.
[04:31] <lifeless> wgrant: well, progress
[04:31] <lifeless> we need to fix the mangling of stdout
[04:34] <jtv> This is getting far too annoying.  Rebooting.
[05:01] <lifeless> -> shoopermarket
[05:02] <StevenK> "Shupper Shulloper"
[05:02] <StevenK> (Not sure how prevalent 12th Man is)
[05:17] <LPCIBot> Project db-devel build #662: STILL FAILING in 5 hr 33 min: https://lpci.wedontsleep.org/job/db-devel/662/
[05:19] <jtv> Well there's a reboot I came to regret.  Looks like today's update renders my MacBook unbootable!
[06:01] <wallyworld_> lifeless: have you tried connecting to postgres using an sql client from outside the lxc container?
[06:03] <StevenK> wallyworld_: O hai. https://code.launchpad.net/~stevenk/launchpad/dsp-vocab/+merge/65762
[06:03]  * wallyworld_ looks
[06:27] <lifeless> wallyworld_: I have not; you'll need to reconfgure postgresql to permit that
[06:28] <wallyworld_> lifeless: any ftfm page you can point me to? if you don't have it handy, i'll search for it
[06:28] <wallyworld_> rtfm
[06:29] <lifeless> http://wiki.postgresql.org/wiki/Client_Authentication
[06:43] <LPCIBot> Project devel build #833: STILL FAILING in 5 hr 42 min: https://lpci.wedontsleep.org/job/devel/833/
[06:48] <jtv> How do we test that zope won't allow a user to access something?  I'm trying assertRaises(ForbiddenAttribute, <operation>) but that, er, fails with a ForbiddenAttribute exception.  :-)
[06:48] <jtv> In doctests it's easy, but what about TestCases?
[06:49] <jtv> attrgetter?
[06:50] <jtv> yup, getattr does the trick.
[07:05] <StevenK> wallyworld_: I think I'm calling SimpleTerm() correctly. And secondly, toTerm() isn't supposed to be called directly, in which case the query in searchForTerms would have warmed up the cache.
[07:10] <wgrant> Yay, all containers 6 connected to testr...
[07:44] <wgrant> lifeless: Much slower with btrfs, it seems :(
[07:45] <wgrant> lifeless: But I've got testr integration mostly working now.
[07:45] <wgrant> Seems to be running OK.
[07:45] <wgrant> hopefully will take less than an hour :)
[07:45] <StevenK> wallyworld_: Prod?
[07:46] <lifeless> wgrant: \o/ \o/ \o/
[07:47] <wgrant> lifeless: (back to aufs, seems to be running quickly)
[07:48] <wgrant> And a lot less memory pressure now it's not 6 instances of the one memory hungry test running at once.
[07:56] <LPCIBot> Project parallel-test build #67: STILL FAILING in 1 hr 14 min: https://lpci.wedontsleep.org/job/parallel-test/67/
[08:04] <jtv> hi rvba
[08:29] <wgrant> Hmm. 12000 tests done, CPU idle... but it's just sitting there.
[08:29] <wgrant> Upsetting.
[08:32] <wallyworld_> StevenK: sorry, i was out buying dinner before. i'll take another look at it
[09:13] <StevenK> wallyworld_: Did you have another look? I hate to be pushy, but I'd love to land this before my flight.
[09:14] <wallyworld_> StevenK: started to but now i have to head off to soccer. i was going to finish when i got back but that doesn't help you. all the other cases of initialising the simple term i know of pass the object as the first param, hence my confusion
[09:16] <bigjools> morning all
[09:16] <wallyworld_> StevenK: i guess it depends on what you expect or want the vocab to represent
[09:18] <wallyworld_> and how it's values will be used - that's the context i am missing
[09:19] <StevenK> wallyworld_: So, since this isn't used any where, I don't think it matters much. It can be fixed when it gets hooked up the UI?
[09:20] <wallyworld_> if you want. if i were doing it i would prefer to get the terms correct so that the next branch was cleaner. you need to get a +1 from jtv anyway, so maybe he can provide a view :-)
[09:20] <jtv> Was I invoked?
[09:21] <jtv> hi bigjools
[09:21] <wallyworld_> jtv: i need to head off to soccer. there's a review that needs +1. StevenKwants to land it before his flight. i had some questions as to whether the SimpleTerm was being correctly constrcuted
[09:22] <jtv> StevenK: url?
[09:22] <wallyworld_> jtv: https://code.launchpad.net/~stevenk/launchpad/dsp-vocab/+merge/65762
[09:22] <jtv> I'm on it.
[09:22] <wallyworld_> jtv: thanks. i'll have a look when i get back to see what transpired
[09:51] <jtv> bigjools: I just remembered — differences in how overrides were set were what led me to the fixes I made.  It's just possible that (a) my branches fix the queue-tool overrides problem as well, (b) trying the overrides on sync jobs from the script now fails more spectacularly because of the security changes, or (c) the script doesn't set overrides at all somehow.  I forget the details.
[09:52] <bigjools> jtv: well let's see!
[09:52] <bigjools> I did write you a lovely addOverride method
[09:58] <jtv> for which I thank you
[09:58] <jtv> (not saying how, but I do)
[09:59] <jtv> StevenK, wallyworld_: to cut things short I apprved, with remarks.
[10:12] <StevenK> jtv: For your reference, there is a self.assertProvides()
[10:12] <jtv> the great thing about standards...
[10:12] <jtv> GAAAAAAAAAAAAAAAAAH
[10:13] <jtv> All that effort to enter objectives and *one* *lousy* *bad* *page* *load* undoes it all for me.
[10:13] <jtv> Which happen all the time.
[10:13] <jtv> And the page is constructed such that even if you have it all ready for copy & paste it's still a chore and a risk.
[10:24] <bigjools> my external monitor has a bug
[10:39] <bigjools> ok, I wish I had discovered bzr qdiff a long time ago, it makes reviewing much easier
[10:46] <bigjools> wgrant: do you want to double check rvb's multi-parent branch?  I am happy for it to land.
[10:52] <wgrant> bigjools: I'm not here, but doesn't that need to use the copier if the archive is distinct and not empty?
[10:53] <wgrant> Now it uses the cloner whenever the series is empty.
[10:53] <bigjools> what did I miss ...
[10:54] <bigjools> wgrant: what do you mean by distinct?
[10:57] <bigjools> ah never mind
[11:04] <wgrant> bigjools: Intra-archive copies can't produce file conflicts, inter-archive copies can. Regardless of series content.
[11:05] <bigjools> yeah
[11:49] <jml> allenap: thanks again for fixing up the doctest id to not have the 'tests/../doc' bit in it
[11:50] <jml> allenap: makes running tests so much easier and eliminates an annoying bit of friction
[11:50] <allenap> jml: Hehe, I'm glad :)
[12:25] <LPCIBot> Project db-devel build #663: STILL FAILING in 5 hr 41 min: https://lpci.wedontsleep.org/job/db-devel/663/
[12:47] <LPCIBot> Yippie, build fixed!
[12:47] <LPCIBot> Project devel build #834: FIXED in 5 hr 52 min: https://lpci.wedontsleep.org/job/devel/834/
[14:03] <deryck> Morning, all.
[14:03] <deryck> Morning, abentley
[14:03] <deryck> abentley, shall we do a standup?  Just you and I today.
[14:03] <abentley> deryck: morning.
[14:03] <abentley> deryck: sure.
[14:03] <deryck> cool
[14:04] <bac> morning deryck
[14:06] <jml> deryck, huwshimi: fwiw, it looks like landscape use lazr.anim and the lazr-js loader.
[14:10] <jml> wiki page updated accordingly
[14:12] <huwshimi> jml: From memory we use lazr.anim but don't use the loader
[14:13] <deryck> jml, yeah, I think they use the green flash and spinner stuff.
[14:17] <jml> deryck: ok. cool. I raised this because the wiki said, "they don't" and lifeless said, "they do", and I'd hate for us to get bogged down in a discussion about a verifiable fact.
[14:18] <deryck> jml, right.  understood.
[14:18] <deryck> what is this wiki page we speak of?
[14:20] <huwshimi> deryck: The agenda for the Thunderdome
[14:21] <deryck> ah
[14:21] <StevenK> deryck: O hai -- I have silenced Windmill on Jenkins.
[14:21] <deryck> StevenK, thank you sir!
[14:26] <deryck> jml, huwshimi -- looked at the page.  I'm very confident that no one else cares if we abandon lazr-js. No one is supporting it, even if they use bits.
[14:26] <wgrant> Burn!
[14:26] <wgrant> Burn it.
[14:27] <wgrant> U1 has abandoned it entirely, yeah?
[14:27] <huwshimi> wgrant: I believe so
[14:27] <jml> wgrant: I just spent 10 mins finding out for landscape. I think it's someone else's turn to verify facts.
[14:28] <huwshimi> deryck: You have spoken to rockstar about lazr-js. Are they using it?
[14:29] <wgrant> The only lazr-js references in the ubuntuone-servers tree are in test/lint configs.
[14:31] <rockstar> huwshimi, we are not.
[14:32] <huwshimi> rockstar: OK, just checking. Do you have plans to use any of it in the future?
[14:32] <rockstar> huwshimi, no.  The first thing I did when rotating to U1 is to get rid of it.
[14:33] <huwshimi> rockstar: OK thanks :)
[14:33] <rockstar> huwshimi, after I finish this (very large) project, I'll probably start focusing on bringing phazr in.
[14:33] <huwshimi> rockstar: Ah right. I thought you might have been using that already
[14:34] <rockstar> huwshimi, well, in a way, we are.  We're just not using it as a dependency.
[14:38] <deryck> but to be clear, the goals for phazr are much different... generic, extensible widgets, that each project can build in....
[14:38] <deryck> the goal is for each project to do their own js development in their own tree, though.
[14:38] <deryck> rockstar, right ^^ ?
[14:38] <rockstar> deryck, indeed.
[14:39] <rockstar> huwshimi, to be clear, much of what is in phazr now is stuff that we have in U1, but are pushing to a place where LP et al. can use it.
[14:45] <huwshimi> rockstar: Right, got it.
[14:45] <LPCIBot> Project parallel-test build #68: STILL FAILING in 1 hr 17 min: https://lpci.wedontsleep.org/job/parallel-test/68/
[14:50] <rockstar> huwshimi, ideally, I'd like to be able to push phazr stuff upstream into the yui3-gallery or yui3 as well.
[14:51] <huwshimi> rockstar: That sounds great. yui could do with some more contributors
[14:53] <bac> hi cr3, your branch passed all of the ec2 tests last night but got kicked out of PQM due to testfix mode.  it is in PQM right now.
[14:54] <cr3> bac: thanks for the update, when should it finally land in production?
[14:57] <deryck> rockstar, huwshimi -- I agree... we really should be thinking about yui as the dependency more.
[14:57] <deryck> and less about lazr or phazr.
[14:57] <bac> cr3: it'll go onto qastaging.launchpad.net later today.  when that happens the bug will be tagged with 'qa-needstesting'.  at that point, you should verify that everything works as expected and the tag changed to qa-ok or qa-bad.
[14:58] <bac> cr3: er, s/the tag changed/change the tag/
[14:58] <rockstar> deryck, indeed.  lifeless' concept of owning the whole stack is important in this case.
[15:00] <jml> hey
[15:00] <jml> what's bugtask.priority for?
[15:01] <wgrant> 2005
[15:01] <maxb> lol
[15:01] <wgrant> severity was renamed to importance, priority was apparently never deleted.
[15:01] <deryck> heh
[15:01] <deryck> what wgrant said ;)
[15:01] <wgrant> Maybe it was 2006.
[15:01] <jml> I'm no DBA, but wouldn't deleting it mean faster queries?
[15:01] <wgrant> a while ago, anyway
[15:02] <jml> also, there are bounty tables in the db
[15:03] <deryck> this stuff should be removed, yes.
[15:03] <maxb> I can imaging narrowing a huge table by a single int not necessarily being worth the downtime
[15:04] <maxb> *imagine
[15:05] <wgrant> Well, it depends on the table :)
[15:05] <wgrant> But BugTask.priority isn't BranchRevision.id.
[15:05] <cr3> bac: I should do that? will I get a notification or will the notification appear in the bug report?
[15:06] <bac> cr3: you'll get bug mail when the tag is added
[15:06] <cr3> bac: awesome, thanks for the heads up, I get so much bug mail it's possible that I could miss it but I'll pay particular attention to that one
[15:06] <nigelb> o/
[15:07] <nigelb> mhall119 and I need some help with LP API.
[15:07] <nigelb> Or rather the optimal way to use the LP API.
[15:07] <jml> shoot.
[15:07] <nigelb> loco.ubuntu.com needs to know the members of all the teams under loco-teams
[15:07] <mhall119> we need to get user data from everybody who's a member of https://launchpad.net/~locoteams
[15:08] <mhall119> most will be indirect members
[15:08] <nigelb> Does doing a +participants call make sense?
[15:09] <nigelb> and does it overload LP too much.
[15:09] <nigelb> especially for a team with 18370 members.
[15:10] <mhall119> oh, and we'll need to keep our data updated, so we'll need to do this regularly
[15:10] <jml> huwshimi: now officially at https://dev.launchpad.net/Projects/Rebranding
[15:10] <jml> mhall119, nigelb: good question
[15:10]  * jml flees to a meeting
[15:10] <huwshimi> jml: Thanks
[15:11] <mhall119> lol
[15:11] <nigelb> haha
[15:11] <nigelb> he's already fleeing from LP team ;)
[15:12] <sinzui> jcsackett, do you have time to mumble for the minutes my computer is operating?
[15:12] <jcsackett> sinzui: sure.
[15:34] <jml> my script tells me that we've closed 500 critical bugs since the start of the year and had 150 opened. that can't be right, can it?
[15:37] <nigelb> Oh, its the friday before the sprint. jml will not get a pie on his face :(
[15:38] <jml> ahh, I see. I'm not counting bugs that have been raised to Critical that were already opened.
[15:40] <jml> hmm.
[15:40] <jml> I guess I'd need to look at BugActivity to get that info
[15:44] <bac> mhall119, nigelb: you may want to investigate using the team.membership_details method
[15:45] <bac> mhall119, nigelb: it'll give you back a list that only includes a link to each member, not a fully populated person object
[15:45] <bac> but, sadly, it doesn't account for subteams.  you'd have to dive into each separately
[15:46] <nigelb> ouch
[15:46] <nigelb> doesn't team.participants do that diving for me automatically?
[15:46] <bac> but you can get a list of those with team.sub_teams
[15:46] <bac> nigelb: it does.  but it returns fully populated person objects...each of which is pretty big
[15:46] <nigelb> in our use case there is a team with only sub teams.
[15:46] <mhall119> bac: that's going to be a lot of hits to LP
[15:47] <bac> nigelb: if your structure is that flat, one team with one layer of subteams underneath, it would be pretty easy
[15:47] <nigelb> so its either one big request to LP or a whole bunch of small requests (18000).
[15:47] <bac> nigelb: no, it would be one request per subteam
[15:48] <nigelb> ah, get a participants call in each subteam?
[15:48] <mhall119> and the sub-team request would give us a list of populated person objects?
[15:48] <mhall119> it's not going ot be quite that flat
[15:48] <mhall119> as lots of loco teams have subteams
[15:48] <bac> mhall119: no, it would give you a populated team.  you'd then ask for membership_details on each of those teams
[15:49] <bac> mhall119: and you might get a lot of duplicate persons who are members of multiple locos
[15:49] <nigelb> I should probably try doing this with launchpadlib and see how it goes
[15:49] <mhall119> bac: which is fine, we can ignore them
[15:49] <bac> nigelb: if you do this:  'import httplib2; httplib2.debuglevel=1' before instantiating your lplib object, you can see the traffic being generated
[15:50] <nigelb> oh, w00t, that would help us understand the calls better :)
[15:53] <bac> mhall119, nigelb: stating the obvious, you could then keep a minimal reference to each person, find the changes, and only have to ask lplib for the full updates for the new people or those that leave.  first time will be rough, though.
[15:54] <nigelb> bac: the other thing we have to figure out make sure we don't count people who changed LP names and include old/new as different people.
[15:54] <bac> nigelb: urgh
[15:54] <mhall119> nigelb: we're getting the new django-openid-auth package ready that'll let us follow renames
[15:55] <nigelb> mhall119: not in the gap when we do this.
[15:55] <mhall119> worst case we'll have both old and new usernames in LD for a short time
[15:55] <nigelb> yeah.
[15:55] <sinzui> deryck, abentley I believe you can now get html5-browser 0.0.6-0 which works with 64bit natty
[15:55] <deryck> sinzui, yay!  Will try here shortly.
[16:02] <abentley> sinzui: I get a bunch of Permission Denied: http://pastebin.ubuntu.com/631839/
[16:02] <sinzui> oh dear
[16:02] <sinzui> abentley, I know that is the out-of-proc calling the pyc
[16:03] <sinzui> I need to see if I lost code, or setup.py did something
[16:04] <sinzui> abentley, was this on the first of second run?
[16:04] <abentley> sinzui: second run, I believe.
[16:05] <sinzui> That is a little more comforting
[16:05]  * sinzui reads code
[16:05] <abentley> sinzui: the first run also failed.
[16:05] <sinzui> oh, okay then
[16:10] <sinzui> abentley, I see python support and my change are not compatible. The file is not executable when it is copyied/installed.
[16:10] <sinzui> I think I can have a fix deployed in a couple of hours
[16:11] <huwshimi> jcsackett: Hi
[16:11] <jcsackett> huwshimi: hello.
[16:12] <huwshimi> jcsackett: Just having a look at those mockups. Thanks for that.
[16:12] <huwshimi> jcsackett: Just wondering if you looked at wording changes
[16:12] <huwshimi> jcsackett: Or is that something that'll be looked a separately?
[16:13] <jcsackett> huwshimi: no, this was just about the icon/signage.
[16:13] <jcsackett> i think "Details..." vs "More info..." etc is something we can look at separately.
[16:13] <huwshimi> jcsackett: Ah good. OK just making sure that's still going to be looked at.
[16:13] <jcsackett> while the mockups center on the "Details..." link, the question of new windows is something that can be answered more generally, so looking at that first. :-)
[16:14] <sinzui> abentley, thank you for your assistance. I have a fix. I am preparing a release
[16:14] <abentley> sinzui: Cool.
[16:14] <huwshimi> jcsackett: Yeah OK, understand.
[16:17] <timrc> abentley, ping, question about addArchiveDependency... is this not a valid use case? https://pastebin.canonical.com/49006/ (being able to add a dependency with more than one component?)
[16:18] <timrc> oh, oops, let me post to pastebin.ubuntu.com (for the record)
[16:18] <abentley> timrc: I don't know.  I just exported the existing functionality.
[16:18] <timrc> http://pastebin.ubuntu.com/631848/
[16:19] <timrc> abentley, okay, fair enough...
[16:19] <abentley> timrc: You could ask bigjools.
[16:19] <timrc> bigjools, should one be able to specify multiple components when adding an archive dependency?
[16:20] <bigjools> timrc: no
[16:20] <bigjools> it works dependent ones out automatically
[16:20] <bigjools> so if you say "main" it only uses main.  If you say "universe" it'll pull in universe and main
[16:21] <timrc> bigjools, interesting... that seems rather nonobvious, but I'm a noob, so that could be it
[16:21] <bigjools> timrc: it's the OGRE model :)
[16:22] <bigjools> it has to be like this because many universe packages depend on ones in main, but not vice-versa
[16:24] <timrc> bigjools, if I specified universe in my sources.list but left out main, it would not make that assumption though, right?
[16:24] <bigjools> timrc: no, you'd end up with uninstallable packages if you did that
[16:25] <timrc> personally I'd expect one to have the same intuition about setting up archive dependencies as they would for their own systems
[16:25] <timrc> at any rate, I'll note the subtlety
[16:25] <bigjools> timrc: well the problem is that there are many stupid people out there and LP tries to save their feet from getting holes in
[16:27] <bigjools> timrc: the UI page goes to some extent to make this more obvious, FWIW.
[16:27] <gary_poster> abentley, hi.  question from CHR.  https://code.launchpad.net/~lyx-outline-devel/lyx/lyx_2.0.x (new import of svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_2_0_X) is not importing correctly (http://launchpadlibrarian.net/74011932/lyx-outline-devel-lyx-lyx_2.0.x.log).
[16:27] <gary_poster> Is this because there is another svn import (https://code.launchpad.net/~vcs-imports/lyx/trunk of svn://svn.lyx.org/lyx/lyx-devel/trunk) created on 2009-02-03 and so therefore maybe a CSCVS import?
[16:27] <gary_poster> More generally, do you have a suggestion on what I can do for this person?
[16:28] <timrc> bigjools, aye, fair enough
[16:28] <abentley> gary_poster: I don't think imports can interfere with each other.  Lemme look.
[16:28] <gary_poster> thanks
[16:28] <abentley> gary_poster: This looks like a timeout.
[16:29] <abentley> gary_poster: The import system kills timed-out workers with SIGINT.
[16:30] <gary_poster> abentley, oh, ok.  so...is the timeout on his side somehow, on the svn server?  svn ls svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_2_0_X seems fast enough
[16:30] <abentley> gary_poster: I think what's happening is that repacking is taking too long and not giving enough progress updates, so the import system concludes that it's hung.
[16:30] <gary_poster> oh
[16:31] <abentley> gary_poster: this could probably be fixed by having a LOSA manually issue "bzr pack" on the branch.
[16:32] <abentley> gary_poster: Though it looks like the following failures were different.
[16:32] <sinzui> jcsackett, I took the survey. I could not complete the form twice because the question requires a different option for each picture. I wanted to mark 2 as clear, but I cannot
[16:32] <abentley> gary_poster: e.g. bzrlib.errors.PathError: Generic path error: '4d28ec951c2cd6f54f2f6567909f2054.rix': Failure: unable to rename to '../indices/4d28ec951c2cd6f54f2f6567909f2054.rix'
[16:33] <jcsackett> sinzui: that was the point--ranking them in preference so we get more unambiguous results. i can redo it if you think that's a bad idea. it's a quick edit.
[16:33] <abentley> gary_poster: You'd have to get a losa to examine the branch, but I suspect the repository is broken.  Probably has an ../indices/4d28ec951c2cd6f54f2f6567909f2054.rix without the rest of the related files.
[16:34] <sinzui> jcsackett, it was not clear to me that I had to rank each picture, sorry
[16:34] <gary_poster> abentley, ok, thank you.  (1) If I point a LOSA to the LP page, will they know where to look?  I don't know
[16:34] <gary_poster> where it would be
[16:34] <jcsackett> sinzui: as i'm thinking about it, i think forced ranking isn't necessary.
[16:35] <gary_poster> (2) if the repo is broken, then a LOSA should blow away the repo and then the import can try again?
[16:35] <jcsackett> sinzui: i've removed force ranking.
[16:35] <gary_poster> (3) Should I file a bug about the scenario you described?
[16:35] <gary_poster> (done)
[16:35] <abentley> gary_poster: I don't know.  I'm not familiar with where the import branches are stored, etc.
[16:35] <gary_poster> abentley, ok fair enough :-)
[16:37] <gary_poster> abentley, I didn't highlight you for my questions 2 and 3 above.  did your "I don't know" apply to them, or should I wait for a reply?
[16:37] <gary_poster> (I figured it applied to question one)
[16:38] <abentley> 2.  I think so.  3. There are at least two bugs; the repack timeout, and the inability to continue after the repack timeout.
[16:39] <sinzui> jcsackett, http://blog.launchpad.net/?p=2646&preview=true
[16:39] <gary_poster> ack abentley, thanks
[16:40] <jcsackett> sinzui: i cannot see previews.
[16:40] <sinzui> jcsackett, even after you login to the blog?
[16:42] <jcsackett> logged-in, i can only see the dashboard (not do or open anything in it).
[16:42] <sinzui> jcsackett, used the drop-down menu to see the drafts.
[16:43] <sinzui> The menu says New Posts by default
[16:45] <jcsackett> sinzui: i don't see a dropdown in my view.
[16:45] <sinzui> :(
[16:45] <sinzui> jcsackett, will the survey link change?
[16:46] <jcsackett> sinzui: it has not changed.
[16:48] <sinzui> jcsackett, try it now
[16:48] <sinzui> I think I made you an editor
[16:48] <jcsackett> sinzui: \o/ i see it.
[16:49] <jcsackett> sinzui: last line. s/Please, take the link opens a new window survey/Please take "link opens a new window" survey/.
[16:50] <jcsackett> er, s/Please, take the link opens a new window survey/Please, take the "link opens a new window" survey/
[16:50] <jcsackett> worth keeping "the" in there, i think. :-P
[16:50] <sinzui> jcsackett, do you not have permission to edit?
[16:50] <jcsackett> sinzui: ah, i do. i just didn't see the link.
[16:53] <jcsackett> sinzui: okay, i think it's good. you have any other thoughts before we throw the publish switch?
[16:54] <sinzui> no more thoughts. publish!
[16:56] <jml> :)
[16:57] <gary_poster> sinzui, on https://dev.launchpad.net/Registry/RegistryReview , the section titled "Remove owned teams" seemed to imply that I should remove ~launchpad and ~canonical-bazaar.  Am I correct in assuming that I should update the wiki page to say that those two teams may be members, or do I misunderstand?
[16:58] <sinzui> gary_poster, I do not see any participations: https://launchpad.net/~registry/+participation
[17:00] <gary_poster> sinzui, I guess I just woefully misunderstood the text.  I thought https://launchpad.net/~registry/+members#active was pertinent
[17:00] <gary_poster> sinzui, actually, I thought from the text that both directions were pertinent
[17:00] <sinzui> gary_poster, We better revise the text then, removing those teams would be catastrophic
[17:01] <gary_poster> I had just deleted a team from the participations
[17:01] <sinzui> thanks
[17:03] <gary_poster> sinzui, so I want to change "Remove owned teams
[17:03] <gary_poster> ~registry does not delegate responsibilities to other teams, it does not use other teams to manage the project's it stewards. Launchpad does not provide a to know what teams a person or team owns, You can examine your admined teams and investigate those you do not understand." to
[17:03] <gary_poster> "Remove owned teams
[17:03] <sinzui> abentley, deryck: I believe html5-browser - 0.0.7-0~25~natty1 is now published
[17:03] <gary_poster> ~registry only delegates responsibilities to ~launchpad and ~canonical-bazaar.  Any other teams should be removed (https://launchpad.net/~registry/+members#active)"
[17:03] <gary_poster> Agree?
[17:04] <sinzui> gary_poster, more than that. ~registry should not own a team or be a member of a team. We do not participate in a community
[17:04] <gary_poster> sinzui, we already have this:
[17:04] <gary_poster> Remove superteams
[17:04] <gary_poster> These have appeared because of merge-delete team defects.
[17:05] <gary_poster> I was going to leave that alone
[17:05] <sinzui> gary_poster, The team does not participate in a community.
[17:05] <gary_poster> it has a nice lplib snippet that helps
[17:05] <gary_poster> OH!
[17:05] <gary_poster> owned teams
[17:05] <abentley> sinzui: I got it.  Now everything is failing with AssertionError: js timed out.
[17:06] <gary_poster> The snippet I gave still confuses me a lot
[17:06] <gary_poster> the titles says owned teams
[17:06] <gary_poster> but we *are* delegating responsibilty
[17:06] <sinzui> abentley, did you build the tree?
[17:06] <gary_poster> I'm just going to leave this.  I don't feel I understand it well enough
[17:06]  * sinzui only sees that when js is not built
[17:08] <abentley> sinzui: I ran make, and it still happened afterward.  running make clean.
[17:09]  * sinzui hacks installed lib
[17:12] <abentley> sinzui: make clean; make does not help.
[17:12] <sinzui> abentley, is do not see  `make` creating the js
[17:13] <sinzui> abentley, does `make jsbuild` make the js
[17:13] <abentley> sinzui: it does nothing.
[17:17] <deryck> sinzui, sometimes you need a make clean_js && make jsbuild to get a rebuild of js.
[17:17] <sinzui> deryck, This is my lib again :(
[17:17] <deryck> ah, sorry :(
[17:18] <sinzui> deryck, I added this to see exactly what you are seeing:
[17:18] <sinzui> html5browser.requires_external_process(True)
[17:18] <sinzui> There is a module level config so that we can disable the hack when natty or oneiric are fixed
[17:22] <deryck> sinzui, gotcha.  I'm seeing the same as abentley.  So should I change something this config to see what happens?
[17:22] <sinzui> deryck, no.
[17:23] <sinzui> This is another manifestation of pyshared built the lib differently that what setup assumed
[17:23] <sinzui> deryck, I can see what you are seeing using the switch in the module and my current tree. You will need to wait another 90 minutes :(
[17:24] <deryck> sinzui, ah, gotcha now.  Ok, no worries.  Thanks for continuing to work on this.
[17:24] <sinzui> yep bad magic
[17:25] <sinzui> I just ran a success. I will need another install to ensure my fix is carried all the way to /usr/lib/pymodules/python2.6/html5browser
[17:25] <sinzui> at least this shows the cost of the fork is not scarry
[17:40] <sinzui> ;;;;p89999999999999999'
[17:42] <jml> yes.
[18:07] <sinzui> deryck, abentley-lunch: I just verified my newest package fixes the permission/timeout issue seen when running from the Lp testrunner. I am copying the package to Lp's ppa now
[18:08] <deryck> nice!
[18:11]  * bigjools heads off
[18:11] <bigjools> see you all in Dublin Town
[18:18] <LPCIBot> Project devel build #835: FAILURE in 5 hr 31 min: https://lpci.wedontsleep.org/job/devel/835/
[18:20] <sinzui> deryck, abentley-lunch: I think html5-browser - 0.0.8-0~26~natty1 is now available
[18:21] <deryck> ok, trying now....
[18:24] <LPCIBot> Yippie, build fixed!
[18:24] <LPCIBot> Project db-devel build #664: FIXED in 5 hr 38 min: https://lpci.wedontsleep.org/job/db-devel/664/
[18:26] <abentley> sinzui: It works!
[18:27] <sinzui> abentley, \o/
[18:27] <sinzui> abentley, I saw a 40% increase in time to run the tests (65s). How log does it take for you to run them
[18:28] <abentley> sinzui: 1 minutes 1.359 seconds.
[18:28] <sinzui> thanks
[18:28] <abentley> sinzui: did you use any of the solutions we talked about?
[18:29] <sinzui> abentley, I have a branch trying the single instance. I hope to complete to today
[18:29] <abentley> sinzui: neat.
[18:32] <deryck> sinzui, works for me too!  Hurrah! :)
[18:32] <sinzui> fab
[18:33] <sinzui> I am just waiting for a buildbot iteration to verify this phase is complete
[18:37] <deryck> sinzui, so now that I can run the entire suite nicely, I see my branch shaves about 20 seconds off the run... from 1:12 to :53 between branches.
[18:37] <deryck> sinzui, just by cleaning up some of the waits stuff.
[18:38] <sinzui> You are my hero!
[19:01] <timrc> When I go to "permanently" delete a PPA, when I attempt to create a new PPA with the same name, Launchpad complains that it already exists... that seems wrong to me, but I'm guessing it's be design :/ ?
[19:02] <timrc> Is there a way to ever reclaim that PPA name (for testing purposes)?
[19:03] <timrc> I see the PPA names of PPA's I deleted weeks ago still grayed out on my lp page, so I'm guessing not
[19:10] <LPCIBot> Project parallel-test build #69: STILL FAILING in 1 hr 11 min: https://lpci.wedontsleep.org/job/parallel-test/69/
[19:23] <abentley> bac: could you please review https://code.launchpad.net/~abentley/launchpad/resubmit-inactive/+merge/65820 ?
[19:23] <bac> abentley: sure
[20:10] <deryck> sinzui, if you're interested, I have my yui speed up branch up for review.
[20:28] <bac> deryck: i just reviewed it.  nice!
[20:40] <lifeless> timrc: yea
[20:41] <lifeless> timrc: I think you can undelete them though
[20:41] <timrc> timrc, maybe delete is the wrong word, then, maybe 'disable'?
[20:47] <deryck> bac, thanks!
[20:48] <deryck> bac, and yeah, I feel like it needs pulling out as well, since it's repeated in several spots, but wasn't sure how.....
[20:48] <deryck> bac, unless we patched effects duration regardless of whether we use it or not.
[20:48] <deryck> but I thought this had value on its own and wanted to land it as is.
[20:59] <cjohnston> I would like to hear some feedback on bug 801514.. Would making a team contact a required field have a negative effect as I think it might? I can see users and teams not wanting to be forced to have a team contact
[20:59] <_mup_> Bug #801514: making team contact a mandatory field when creating a team <Launchpad itself:Triaged> <LoCo Team Directory:New> < https://launchpad.net/bugs/801514 >
[21:00] <mhall119> cjohnston: who are you asking?
[21:00] <cjohnston> Any of the devs of LP
[21:01] <cjohnston> or users
[21:19] <maxb> cjohnston: That is not feasible at all. It would immediately forbid any use-case of using teams as a handle on a group of related launchpad subscriptions
[21:20] <cjohnston> maxb: that's kinda what I was thinking.
[21:20] <maxb> For example, we have a ~bzr-codereview-subscribers team to make it easier to subscribe to the set of all main bazaar series branches
[21:20] <cjohnston> I just didn't want to make a decision for LP on my own.
[21:20] <cjohnston> maxb: would you mind marking that in the bug please?
[21:22] <maxb> So noted
[21:26] <cjohnston> Thanks maxb
[21:28] <cjohnston> maxb: just confirming that this would make the bug "Won't Fix" for LoCo Directory?
[21:30] <maxb> I don't really understand how this impacts loco directory, I'm just making a statement that removing the ability to have launchpad teams without contact addresses would be an irksome loss of functionality
[21:30] <cjohnston> PM maxb please?
[21:32] <maxb> Well, if you like, but why not continue on the channel?
[21:33] <maxb> Are we even talking about the same thing?
[21:33] <maxb> I'm talking about the email field in Launchpad teams
[21:35] <bac> deryck: yeah, those were my thoughts.  very landable now. thanks.
[21:43] <lifeless> cjohnston: yes, its wontfix.
[21:44] <cjohnston> thanks lifeless
[23:36] <Ursinha> I hate whoever installed sl on devpad
[23:44] <LPCIBot> Project devel build #836: STILL FAILING in 5 hr 25 min: https://lpci.wedontsleep.org/job/devel/836/


[15:53] <Salt> androidbruce, BGL, bkerensa, cj, shirgall, thefinn93, ubuntulo12, valorie: Anyone know if there will be ubuntu-wa tabling going on at lfnw? Also, if you'd like to come to GSLUG today, it may be a good time to get together and plan one out.
[18:36] <androidbruce> Salt,  what time does GSLUG start and where is it?


[00:48] <len> ScottL: Looked at test page as above. Looks ok but the page pointed to for the iso has old stuff from last cycle still. Not that it matters as the new one won't install yet anyway.
[00:48] <ScottL> len, the page will update when the new qa images are available
[00:50] <len> Ok
[01:03] <astraljava> ScottL: I was pinging you, yes. I just said if I can't sleep soon, I'll be eyeing over the pages. But I ended up trouble-shooting some other issues with Xubuntu people. It turned out we didn't include indicator-sound-gtk2 in the seeds, and thus people are missing the volume icon in the default install.
[01:03] <astraljava> I don't know whether we should do something about it, or rather, can we do anything about it?
[01:07] <ScottL> astraljava, hmmm, not sure really
[01:07] <ScottL> we could update the desktop meta and they would have an update after installation, no?
[01:09] <astraljava> ScottL: I suppose. If they kept the package installed, then yes logically that should happen, silly me.
[01:28] <astraljava> ScottL: Ok, I made the change.
[01:28] <astraljava> Question is, shall we ask for a SRU?
[01:59] <falktx__> crap
[02:00] <falktx__> sorry, wrong clicks
[02:12] <ScottL> astraljava, would they rebuild the image for it?
[02:13] <ScottL> i'm not sure on the SRU though
[05:00] <micahg> ScottL: it's a meta package, so fairly low risk for a rebuild depending on what's added (in this case stuff is broke, so an SRU seems warranted)
[05:23] <ScottL> thank you micahg :)
[13:12] <ScottL> astraljava,  i would be happy to file the SRU bug if you haven't already
[13:13] <astraljava> ScottL: I haven't had time yet, sort of busy at work.
[13:13] <astraljava> I'll do it later in the evening unless you notify that you've done it.
[13:23] <ScottL> i'll try today during work, but make sure i let you know if i do it though, astraljava
[13:26] <astraljava> ScottL: Don't worry, LP tells me if I try to add an existing one.
[13:32] <ScottL> oh yeah :)
[13:32]  * ScottL is out the door with the kids
[14:50] <falktx> scott-work: ScottL: ping
[14:51] <scott-work> hi falktx
[14:54] <falktx> scott-work: do you have a minute?
[14:56] <scott-work> falktx: if it is a short minute, i'm pretty busy this morning at work, but in four hours or so i should a lot more time
[14:56] <scott-work> i did want to talk to you about some of the things from the work flows meeting though at some point
[14:56] <falktx> scott-work: ok, later then
[15:16] <l33o> hi
[15:16] <holstein> l33o: o/
[15:16] <falktx> hey l33o
[15:17] <l33o> hi buddies ;)
[15:21] <holstein> las changed the topic of #ardour to: ardour 3.0-beta1 is released!!
[15:26] <falktx> holstein: it is!?
[15:26] <falktx> weeee
[15:26] <holstein> :)
[15:26] <falktx> http://ardour.org/node/4658
[17:42] <scott-work> new blog post:  http://dullass.blogspot.com/2011/11/contributor-developments.html
[17:43] <scott-work> comments always welcome, even contrary ones  ;)
[18:49] <l33o> c u later
[23:35] <ScottL> hi falktx , wanna talk?
[23:35]  * ScottL just got home and is going ot change clothes quickly
[23:37] <astraljava> Slipping into something more comfortable, aye?
[23:44] <ScottL> aye ;)
[23:44] <ScottL> or at least not slacks, shirt, and dress shoes
[23:45] <falktx> ScottL: hey there
[23:45] <falktx> ScottL: I really want to help US
[23:45] <falktx> but I'm leaving Ubuntu
[23:46] <ScottL> falktx, that's sad...but i understand
[23:46] <ScottL> you're going to arch-land
[23:47] <knome> falktx, may i ask what are the reasons?
[23:48] <falktx> knome: I don't like the direction ubuntu is going, and arch seems just like what I was trying to do
[23:48] <knome> okay
[23:48] <falktx> ie, building from the ground up, a complete your-way setup
[23:49] <ScottL> that is true, the power user would certainly go that directly
[23:49] <falktx> I always install ubuntu that way, starting with a netboot iso and moving forward package by package
[23:49] <falktx> ScottL: 12.04 will probably be the last version for which I support the KXStudio PPAs
[23:50] <falktx> I hope UbuntuStudio becomes good enough
[23:52] <ScottL> falktx, i think there is a good plan going on now and it will improve as the longer plan is further developed
[23:53] <ScottL> and since we would be targeting a different audience i think it will be good enough
[23:54] <falktx> yep


[06:30] <adnanh> knome, ochosi, is creating monochrome icons of various applications for the notification area anywhere on the 13.04's todo list?
[08:28] <astraljava> http://www.everydaylinuxuser.com/2012/11/xubuntu-1210-day-1-first-impressions.html
[08:29] <astraljava> Not too much analysis, though. But then what do you expect from a day-1 review.
[10:46] <pjotr> Hello, I've found a bug in Alacarte in Xubuntu 12.10. When you check a menu item in one category, then click on another category, and then click on the first category again, the menu item has suddenly become unchecked.
[10:46] <pjotr> I've filed this bug report: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1077326
[10:48] <pjotr> OK, ubottu seems to have noticed a duplicate.... :P
[10:48] <mr_pouit> no, that was me :P
[10:48] <mr_pouit> I've already prepared a fix for quantal-proposed, but it hasn't been accepted yet
[10:49] <pjotr> Great! A solution is on the way, then. :-)
[19:48] <GridCube> ochosi, http://i.imgur.com/2sLMV.png http://imagebin.org/235367
[19:48] <GridCube> today two different people came with this same issue
[19:48] <GridCube> the applications icons are huge
[19:48] <GridCube> and are not getting resized


[05:40] <akgraner> hey all!
[05:40] <akgraner> finally getting a chance to login and :-)
[05:40] <akgraner> scott_ev, I have people working on the last emea membership board so we can post the new members
[05:41] <akgraner> nhandler, thank you!
[05:50] <scott_ev> akgraner: awesome, thank you


[06:01] <duflu> Morning seb128
[06:22] <duflu> Morning oSoMoN. I just added some components you mentioned recently to https://docs.google.com/spreadsheets/d/e/2PACX-1vRDHPxGBHqM6XkT_S8ggtYfD0xchKSUD_z9PopNVE3G1rU05fVSnxDGcDsEstl7gu7N-tzCU6mLUp2V/pubchart?oid=254968654&format=interactive
[06:42] <didrocks> oopps, forgot to say "good morning", was already deep in packaging
[06:43] <duflu> Good morning didrocks. Everyone else is still asleep, even if logged in
[06:45] <didrocks> all those slackers! :-)
[06:55] <oSoMoN> good morning desktoppers
[06:55] <duflu> Hello oSoMoN
[06:55] <oSoMoN> hey duflu
[06:55] <oSoMoN> which components did you add?
[06:56] <duflu> oSoMoN, thunderbird and chromium-browser
[06:56] <duflu> with as much history as I could find
[06:56] <oSoMoN> (I was outside overseeing workers who are drilling ventilation holes for the crawl space below the house)
[06:56] <oSoMoN> duflu, cool, thanks
[06:59] <oSoMoN> duflu, does the LP API expose bug number history?
[07:00] <duflu> oSoMoN, I don't know. I only use the Wayback Machine :)
[07:00] <duflu> It's a tricky question to answer -- what was the net opens-minus-closes on date X
[07:00] <duflu> ?
[07:01] <duflu> I wouldn't be surprised if LP had no such records
[07:05] <oSoMoN> duflu, yeah, it doesn't as far as I know, using the wayback machine is a clever way of getting that info
[07:16] <didrocks> salut oSoMoN
[07:18] <oSoMoN> salut didrocks, ça va?
[07:18] <didrocks> ça va, et toi oSoMoN ?
[07:19] <oSoMoN> bien
[07:34] <seb128> hey duflu
[07:34] <seb128> lut oSoMoN didrocks
[07:34]  * seb128 is back from morning "errands" :) I should have started earlier than 8am today, it's nice and fresh still
[07:35] <duflu> Real life. Always gets in the way
[07:35] <seb128> indeed
[07:39] <didrocks> salut seb128
[07:50] <oSoMoN> salut seb128
[08:01] <Laney> yo
[08:01] <didrocks> hey Laney, good long week-end?
[08:03] <Laney> heeeeeeeeeeeeeeeeyy didrocks
[08:03] <Laney> YEP
[08:03] <Laney> nice swimming in the river / sea, good food & drinks, hot sun!
[08:03] <didrocks> nice!
[08:04] <didrocks> it's time for https://github.com/ubuntu/communitheme/pull/649
[08:04] <gitlab-bot> ubuntu issue (Pull request) 649 in communitheme "New theme name" (comments: 1) [Open]
[08:05] <Laney> 🏊 🌊🍹🍺☕🌞
[08:06] <Laney> yeahhhh
[08:06] <Laney> how are you?
[08:07] <didrocks> I'm fine, thanks!
[08:08] <Laney> groovy
[08:09] <willcooke> morning all
[08:13] <didrocks> morning willcooke
[08:16] <oSoMoN> good morning Laney, willcooke
[08:16] <didrocks> seb128: when you have time, do you mind pre-reviewing the packaging before I upload it to cosmic? https://github.com/ubuntu/yaru
[08:17] <Laney> moin willcooke oSoMoN
[08:17] <Laney> what's new
[08:18] <willcooke> didrocks, woot!    Wide awake at 2 = hard to wake up at 9.
[08:19] <willcooke> How was your holiday?
[08:19] <Laney> yeah pretty sweet
[08:19] <Laney> we mainly pottered around eating, drinking and swimming in various bodies of water
[08:20] <Laney> we were in totnes
[08:20] <Laney> good river there for swimming in, can walk a few minutes out of the town
[08:21] <willcooke> nice part of the world that
[08:27] <Laney> aye
[08:32] <duflu> Morning(ish) willcooke
[08:36] <duflu> Morning Laney too
[08:37] <willcooke> ar'noon duflu
[08:40] <Trevinho> Morning
[08:40] <Trevinho> Hi Laney
[08:46] <didrocks> hey Trevinho
[08:48] <seb128> didrocks, sure, I'm having a look to that today
[08:48] <didrocks> thanks!
[08:48] <duflu> Hi Trevinho
[08:48] <seb128> np!
[08:48] <seb128> hey Trevinho Laney
[08:48] <seb128> & willcooke
[08:50] <Trevinho> Hi didrocks, duflu, seb128 & willcooke
[08:51] <Laney> hey Trevinho and seb128!!!
[08:51] <Laney> what's going on
[08:55] <duflu> I see blue sky. It's been a while
[08:58] <seb128> summer is here, it's still nice in the morning but I might hunt for a place with a/c for the afternoon :/
[09:00] <didrocks> already 27°C inside
[09:06] <Laney> /o\
[10:40] <seb128> didrocks, nice job on the yaru blog post!
[10:44] <Laney> YYYYYYEAHHHHHHHHHH!
[10:44] <Laney> cyphermox: hey, did you see that people are still reporting kbd_mode bugs?
[10:44] <Laney> there was a console-setup sru to bionic which probably set them off (not that I've investigated)
[10:50] <oSoMoN> Laney, would you mind approving and merging https://code.launchpad.net/~osomon/britney/hints-ubuntu-libreoffice/+merge/350721 ?
[10:51] <Laney> ok
[10:51] <oSoMoN> thanks
[10:51] <Laney> why do we still have that problem :((((((((((((((((((((((((((((((((((((((
[10:53] <oSoMoN> the kernel team spent some time trying patches but I don't think we ever got to the bottom of it…
[10:54] <oSoMoN> Laney, once merged, do I need to do anything for the autopkgtest failure to be ignored and migration to proceed?
[10:54] <Laney> nah, it happens at the next run
[10:58] <seb128> Laney, speaking of hint can you update the udisks2 version on s390x?
[10:59] <Laney> I thought that was going to be looked at
[11:01] <Laney> done
[11:01] <Laney> but I still thought that
[11:01] <Laney> If not, make the next upload kill the testsuite on s390x
[11:01] <Laney> please, or something like that
[11:02] <seb128> good point, thx (I poked a bit at it but don't remember if I said I would do a bit more of that of the outcome is that some of the things don't make sense on s390x ... I had back that in my backlog to have a look again)
[11:03] <xnox> i agree....
[11:03] <seb128> I add back*
[11:03] <seb128> xnox, you agree with killing the testsuite on s390x?
[11:03] <xnox> yes
[11:04] <seb128> great :)
[11:04] <xnox> chances of people connecting usb camera to a mainframe are -1
[11:04] <Laney> still
[11:04] <Laney> http://autopkgtest.ubuntu.com/packages/u/udisks2/bionic/s390x
[11:04] <Laney> what broke it?
[11:04] <Laney> that's worth being concerned about imho
[11:05] <xnox> seb128, it would be ok if it did test the dasd/zfcp/loops etc all the generic things.
[11:05] <xnox> but not the usb stuff, for example.
[11:05] <xnox> looking
[11:05] <Laney> if things go from working to broken
[11:05] <Laney> understanding why is important
[11:05] <xnox> glibc broke it?! =)
[11:06] <xnox> yeah looks odd / bad
[11:06] <seb128> I think the main failing test is new in 2.7 and never worked
[11:07] <seb128> https://github.com/storaged-project/udisks/issues/517
[11:07] <gitlab-bot> storaged-project issue 517 in udisks "test_md_raid_methods fails on s390x" (comments: 2) [Open]
[11:07] <seb128> that didn't exist in 2.6
[11:07] <seb128> the other issues are transient/flaky tests (should be addressed too yes)
[11:08] <Laney> ah nice bug
[11:08] <seb128> they milestoned for 2.8 so hopefully they get back to it
[11:09] <xnox> well that's just basic linux raid, i can poke things there to see what's wrong.
[11:09] <xnox> in general linux raid should just work.
[11:09] <seb128> that would be useful
[11:09] <seb128> thx
[11:09] <xnox> so possibly simply racy
[11:09] <xnox> and mainframe fast, hence always racy
[11:18] <Laney> 😘
[12:50] <andyrock> seb128: can you take a look at https://code.launchpad.net/~azzar1/software-properties/fix-lp-1770686/+merge/345437
[12:50] <andyrock> it has been there approved for a while
[12:51] <seb128> andyrock, hey, sure, I've a meeting in 10min so probably after that/the team meeting, but it's on my list now :)
[12:51] <andyrock> kk thx :)
[13:04] <didrocks> would be nice if gbp had a --split mode as bzr bd did
[13:04]  * didrocks looks at the doc but didn't find an equivalent if I'm correct
[13:15] <cyphermox> Laney: I did not, where do you see these bugs?
[13:22] <didrocks> ok, I think I found some options to emulate it
[13:28] <Laney> cyphermox: some comments on 1710637
[13:28] <Laney> and p_opey reported it here
[13:30] <willcooke> ding ding!
[13:30] <willcooke> it's meeting time
[13:30] <willcooke> #startmeeting Desktop Team Weekly Meeting - 2018-07-24
[13:30] <meetingology> Meeting started Tue Jul 24 13:30:28 2018 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:30] <meetingology> Available commands: action commands idea info link nick
[13:30] <oSoMoN> o/
[13:30] <willcooke> Roll call: andyrock, dgadomski, didrocks, duflu (out), jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (hols)
[13:30] <didrocks> hey
[13:31] <Trevinho> o/
[13:31] <andyrock> o/
[13:31] <Laney> _O_
[13:31] <seb128> hey
[13:31] <jibel> o/
[13:31] <willcooke> Looks like we have enough people to start, so....
[13:31] <willcooke> #topic andyrock
[13:32] <kenvandine> o/
[13:32] <andyrock> Reviewed https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/349670
[13:32] <andyrock> Update MP for https://gitlab.gnome.org/GNOME/gnome-shell/issues/373 to support x11 too
[13:32] <andyrock> Bug “media-keys: Some shortcuts should ignore auto-repeat key events”:
[13:32] <andyrock> MP for gnome-shell: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/156
[13:32] <andyrock> MP for gnome-settings-daemon: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/34
[13:32] <andyrock> MP for mutter: https://gitlab.gnome.org/GNOME/mutter/merge_requests/169
[13:32] <andyrock> Working on fix for LP: #1772831
[13:32] <andyrock> Working on adding ‘http over unix’ support to libsoup. This likely requires a major reworking of the api
[13:32] <gitlab-bot> GNOME issue 373 in gnome-shell "Some keybindings should discard auto-repeat events" (comments: 0) [Opened]
[13:32] <gitlab-bot> GNOME issue (Merge request) 156 in gnome-shell "shellDBus: Add ignore_key_repeat paramater" (comments: 8) [Opened]
[13:32] <gitlab-bot> GNOME issue (Merge request) 34 in gnome-settings-daemon "media-keys: Allow some key repeated events" (comments: 1) [Opened]
[13:32] <gitlab-bot> GNOME issue (Merge request) 169 in mutter "keybindings: Add flag param to grab_accelerator" (comments: 8) [Opened]
[13:33] <andyrock> eow
[13:33] <willcooke> thanks andyrock
[13:33]  * willcooke makes a note to trim the topic when the meeting is over
[13:33] <willcooke> #topic dgadomski
[13:33] <dgadomski> hey
[13:33] <dgadomski> * bug #1782152 fixed upstream, tested & prepared debdiffs
[13:33] <dgadomski> * working on bug #1721988, for some it's fixed in 18.04, but not according to my tests, will continue working on this
[13:33] <dgadomski> eof
[13:34] <willcooke> thanks dgadomski
[13:34] <willcooke> #topic didrocks
[13:34] <didrocks> Communitheme:
[13:34] <didrocks>  * Finalizing communitheme rename (some fix up for upstream devs to test and iterate over it easier)
[13:34] <didrocks>  * Debian packaging for cosmic
[13:34] <didrocks>  * Some changes (like Shell not taking capital letters for modes)
[13:34] <didrocks>  * Change repository name
[13:34] <didrocks>  * Resync Travis, do some cleanups in the CI build system, adapt gtk-common-themes to it.
[13:34] <didrocks>  * Converted ubuntu-settings to git and release a fix for communitheme for both cosmic and bionic (LP: #1782190). However, cosmic is stuck in proposed due to a meson bug.
[13:34] <didrocks>  * Investigated the meson regresstion and opened https://github.com/mesonbuild/meson/issues/3914 (tagged as such by upstream)
[13:34] <gitlab-bot> mesonbuild issue 3914 in meson "Symlinks can't be copied by install_subdir() since 0.47.0" (comments: 1) [Install Targets, Regression, Open]
[13:34] <didrocks> Apport:
[13:34] <didrocks>  * Some rereviews with Brian, and discussion on services. Now in bionic-proposed! (Needs testing). Should be released post .1.
[13:34] <didrocks>  * Prepare with the communitheme core team the Yaru annoucement blog post.
[13:34] <didrocks> GSConnect:
[13:34] <didrocks>  * Spent some time trying it, found a lot of issues/warnings with current releases.
[13:34] <didrocks>  * Still did a first packaging on it and started to fix some issues like harcoded path for settings not being able to be installed distro-wide.
[13:34] <didrocks>  * Read github issue tracker and found that a WIP rewrite is currently being done. Talking with upstream on https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/158 who hilighted that the best route is to wait for the rewrite. Iterating with him currently on the packaging and feedback.
[13:34] <gitlab-bot> andyholmes issue 158 in gnome-shell-extension-gsconnect "Inclusion by default in ubuntu" (comments: 7) [Open]
[13:34] <didrocks> Misc:
[13:34] <didrocks>  * Reviewed and sponsor Marco's Nautilus update.
[13:34] <didrocks> .
[13:34] <willcooke> nice, thanks didrocks
[13:35] <oSoMoN> didrocks, cool new name
[13:35] <didrocks> it is a cool name ;)
[13:35] <willcooke> :D
[13:35] <willcooke> #topic duflu
[13:35] <willcooke> * Gnome Shell performance (what changed this week):
[13:35] <willcooke>   - Reduced input lag and cursor stutter! I wasn't looking for a lag problem but it's definitely improved now. Most noticeable inside apps (https://gitlab.gnome.org/GNOME/mutter/merge_requests/168)
[13:35] <willcooke>   - Wayland: Implemented proper hardware vsync (https://gitlab.gnome.org/GNOME/mutter/merge_requests/171). Previously Wayland sessions would blindly always render at 60.00Hz regardless of how appropriate that was for the display.
[13:35] <willcooke>   - More work in progress: Avoid frame skipping and artificially low frame rates:
[13:35] <willcooke>     . https://gitlab.gnome.org/vanvugt/mutter/commits/super-smooth
[13:35] <willcooke>     . https://gitlab.gnome.org/vanvugt/mutter/commits/super-smooth-v2
[13:35] <willcooke>     . Basically done for Wayland (when combined with !171 above) but Cogl's X11 backend is proving surprisingly buggy.
[13:35] <gitlab-bot> GNOME issue (Merge request) 168 in mutter "clutter: Reduce input lag and cursor stutter [performance]" (comments: 19) [Performance, Opened]
[13:35] <willcooke>     . One eager user has been helping me test it and also confirms his 2010-era Intel system sees a doubling in frame rate.
[13:35] <willcooke> * Daily bug management:
[13:35] <gitlab-bot> GNOME issue (Merge request) 171 in mutter "Sync to the hardware refresh rate, not just 60.00Hz [performance]" (comments: 16) [5. Backend: Native, Opened]
[13:35] <willcooke>   - Mostly good news - shrinking backlogs in the problem areas.
[13:35] <willcooke>   - Added thunderbird and chromium-browser to the chart.
[13:35] <willcooke>   - https://docs.google.com/spreadsheets/d/e/2PACX-1vRDHPxGBHqM6XkT_S8ggtYfD0xchKSUD_z9PopNVE3G1rU05fVSnxDGcDsEstl7gu7N-tzCU6mLUp2V/pubchart?oid=254968654&format=interactive
[13:36] <willcooke> #topic jamesh
[13:36] <willcooke> snapd/pulseaudio:
[13:36] <willcooke> * I am working on updating the "snap support" patches for Pulse Audio
[13:36] <willcooke> to restrict microphone access based on the connected plugs of the
[13:36] <willcooke> snap.
[13:36] <willcooke> * When I had a similar problem in the past, zyga had suggested I use
[13:36] <willcooke> the new interfaces REST API.  This isn't currently supported in
[13:36] <willcooke> snapd-glib, so I put together a merge proposal here:
[13:36] <willcooke> https://github.com/snapcore/snapd-glib/pull/40
[13:36] <gitlab-bot> snapcore issue (Pull request) 40 in snapd-glib "WIP: Add support for the "interface info" mode of the /v2/interfaces API" (comments: 1) [Open]
[13:36] <willcooke> * It turns out that this API doesn't currently provide a way to
[13:36] <willcooke> reliably tell which interfaces are connected, so it looks like the
[13:36] <willcooke> legacy "ask for data about every single connection on the system and
[13:36] <willcooke> then filter client side" is the only option for now:
[13:36] <willcooke> https://forum.snapcraft.io/t/should-v2-interfaces-select-connected-return-unconnected-plugs-slots/6455/2
[13:36] <willcooke> * I hope to have a version of the PA patch ready for testing soon.
[13:36] <willcooke> #topic jibel / heber
[13:37] <jibel> - Preparing the release of 18.04.1 this thursday
[13:37] <jibel>     - Troubleshooted bug 1772844 that prevented launch of preinstalled snap and installation of some other snaps (eg gedit)
[13:37] <jibel>     - Tested EFI installation with an existing legacy installation (typical use case is the side by side installation with MS Windows)
[13:37] <jibel>     - Reviewed upgrade bugs to 18.04
[13:37] <jibel>     - Smoke tests of 18.04.1 with proposed enabled.
[13:37] <jibel> done
[13:37] <willcooke> thanks jibel
[13:37] <willcooke> #topic kenvandine
[13:37] <kenvandine> * Sprint last week
[13:37] <kenvandine> * Decided on the name for our fork of gnome-software, it will be "snap-store".  When run on Ubuntu you'll get the full experience you would get from our current deb but when run on other distros it will be a fro
[13:37] <kenvandine> ntend to just the snap store.
[13:37] <kenvandine>   - The snappy team is working on adding the interfaces we need to run snap-store confined
[13:37] <kenvandine> ⚾
[13:37] <willcooke> thanks kenvandine
[13:38] <willcooke> #topic Laney
[13:38] <Laney> • short week, was on holiday friday & monday
[13:38] <Laney> • mainly did some updates / reviews / sponsoring (some to SRU too)
[13:38] <Laney> • gtk, mutter, gnome-shell, vala
[13:38] <Laney> • had to fix a few issues in gtk to get it to build / test, all merged upstream
[13:38] <Laney> • usual git stuff, some fixes merged but also some of the updates above were done using this workflow which was nice
[13:38] <Laney> • Florian reviewed my gnome-shell branches; I fixed according to the comments and they got merged. systemd 👏
[13:38] <Laney> 🚲🚲🚲
[13:38] <willcooke> thanks Laney
[13:39] <willcooke> #topic oSoMoN
[13:39] <oSoMoN> hey
[13:39] <oSoMoN> • chromium
[13:39] <oSoMoN>   ∘ working on content snap for chromium-ffmpeg-extras (https://trello.com/c/iOMMKdy7/52-snap-that-provides-a-content-interface-for-chromium-ffmpeg-extras)
[13:39] <oSoMoN>   ∘ updated beta to 68.0.3440.68
[13:39] <oSoMoN>   ∘ updating dev to 69.0.3493.3
[13:39] <oSoMoN> • libreoffice
[13:39] <oSoMoN>   ∘ fixed https://github.com/ubuntu/gtk-communitheme/issues/350 (theming with communitytheme)
[13:39] <oSoMoN>   ∘ promoted <IP_ADDRESS> snap to stable channel
[13:39] <oSoMoN>   ∘ pushed <IP_ADDRESS> snap to the candidate channel and issued call for testing (https://forum.snapcraft.io/t/call-for-testing-libreoffice-6-0-6/6468)
[13:39] <oSoMoN>   ∘ pushed <IP_ADDRESS> snap to the beta channel, then updated to <IP_ADDRESS>
[13:39] <oSoMoN>   ∘ uploaded 6.0.6~rc1 to cosmic-proposed and updated hint to ignore i386 autopkgtest failure (https://code.launchpad.net/~osomon/britney/hints-ubuntu-libreoffice/+merge/350721)
[13:39] <oSoMoN> • snaps
[13:39] <oSoMoN>   ∘ gnome-software: added logic to hide Updates tab when we're not on Ubuntu and exposing only the snap backend: https://gitlab.gnome.org/Community/Ubuntu/gnome-software/commit/50e0cfeb1e3529b6e5c04820ddffa64754312ac5
[13:39] <oSoMoN> 🥑
[13:39] <willcooke> thanks oSoMoN
[13:39] <willcooke> #topic seb128
[13:40] <seb128> • one day off (friday swap for GUADEC over the w.e)
[13:40] <seb128> • sponsored g-s segfault fix from andyroc_k to cosmic&bionic - https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1781996
[13:40] <seb128> • reviewed notes from Montréal & GUADEC conference report
[13:40] <seb128> • some cosmic updates (gnome-keyring, alsa-plugins)
[13:40] <seb128> • spent some time playing with/learning the workflow of the new git packaging
[13:40] <seb128> • verified some bonic SRUs for .1
[13:40] <seb128> • opened a MIR for sshfs which is a depends of gs-connect

[13:40] <willcooke> thanks seb128
[13:40] <willcooke> #topic tkamppeter
[13:42] <willcooke> #topic Trevinho
[13:43] <Trevinho> · Nautilus:
[13:43] <Trevinho>   - Prepared upstream release 3.26.4:
[13:43] <Trevinho>     - https://gitlab.gnome.org/GNOME/nautilus/merge_requests/269
[13:43] <Trevinho>   - Proposed to salsa 3.26.4:
[13:43] <Trevinho>     https://salsa.debian.org/gnome-team/nautilus/merge_requests/2
[13:43] <Trevinho>     https://salsa.debian.org/gnome-team/nautilus/merge_requests/3
[13:43] <Trevinho>   - Prepared 3.26.4 (<IP_ADDRESS> first) for Ubuntu:
[13:43] <Trevinho>     cosmic, https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+ref/ubuntu/master
[13:43] <Trevinho>     bionic, https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/349984
[13:43] <Trevinho>   - Continued fixes for bug #1767027 upstream
[13:43] <Trevinho>     https://gitlab.gnome.org/GNOME/nautilus/merge_requests/249
[13:43] <Trevinho>   - Doing debugging work to fix https://bugs.launchpad.net/ubuntu/bionic/+source/nautilus/+bug/1756826
[13:43] <gitlab-bot> GNOME issue (Merge request) 269 in nautilus "Prepare gnome-3-26 branch for 3.26.4 release" (comments: 2) [Merged]
[13:43] <gitlab-bot> GNOME issue (Merge request) 2 in nautilus "Add nautilus 3.26.4 to pristine-tar" (comments: 0) [Merged]
[13:43] <gitlab-bot> GNOME issue (Merge request) 3 in nautilus "Update upstream/3.26.x with 3.26.4" (comments: 0) [Merged]
[13:43] <gitlab-bot> GNOME issue (Merge request) 249 in nautilus "Recursive query flags" (comments: 48) [3. Review Ready, Opened]
[13:43] <Trevinho> · Mutter, prepared 3.28.3:
[13:43] <Trevinho>   - https://salsa.debian.org/gnome-team/mutter/merge_requests/5
[13:43] <Trevinho> · GNOME Shell, prepared 3.28.3 (with patch refreshes):
[13:43] <Trevinho>   - debian, https://salsa.debian.org/gnome-team/gnome-shell/merge_requests/2
[13:43] <Trevinho>   - cosmic, https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+ref/ubuntu/master
[13:43] <Trevinho>   - bionic, https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/349984
[13:43] <Trevinho>   - Updates to https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/8#note_267751 (now merged!)
[13:43] <Trevinho> 🇪🇸
[13:43] <gitlab-bot> GNOME issue (Merge request) 5 in mutter "Update upstream/latest" (comments: 0) [Merged]
[13:43] <gitlab-bot> GNOME issue (Merge request) 2 in gnome-shell "New upstream release 3.28.3" (comments: 0) [Merged]
[13:43] <gitlab-bot> GNOME issue (Merge request) 8 in gnome-shell "Repositioned window in activities" (comments: 17) [1. Bug, Merged]
[13:43] <willcooke> thanks Trevinho
[13:43] <willcooke> #topic rls-bugs
[13:43] <willcooke> I'm unprepared for this section, as usual
[13:44] <seb128> haha
[13:44] <willcooke> looking at rls-bb
[13:44] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html has 1 new bug
[13:44] <seb128> which we discussed there some days ago and needs an assigne
[13:44] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226
[13:44] <willcooke> that one?
[13:45] <seb128> yes
[13:45] <kenvandine> yeah
[13:45] <willcooke> kenvandine, can Robert take a look?  Would probably be quickest
[13:45] <willcooke> except he's on hols
[13:45] <seb128> basically rbalin_t find the trigger, clicking on "refresh" in g-s triggers offline updates
[13:45] <willcooke> oh, back tomorrow
[13:45] <kenvandine> willcooke, yeah... or oSoMoN
[13:45] <seb128> no, he's away autoresponder said 31st no?
[13:45] <seb128> still one week?
[13:45] <kenvandine> he should be back tomorrow
[13:46]  * willcooke checks the HR system
[13:46] <seb128> ah ok, maybe I remember wrongly
[13:46] <oSoMoN> I can have a look
[13:46] <willcooke> (btw, emailed them about getting an ical feature.  It's on their backlog)
[13:46] <willcooke> oki, thanks oSoMoN
[13:46] <oSoMoN> once I'm done with chromium ffmpeg content snap
[13:46] <kenvandine> oSoMoN, yeah... might be a good way to get started :)
[13:46] <willcooke> assigned it
[13:46] <seb128> willcooke, good news!
[13:46] <seb128> oSoMoN, thx
[13:47] <willcooke> (my shell has crashed, bear with me)
[13:47] <seb128> willcooke, kenvandine, HR has robert off until friday included
[13:47] <kenvandine> i was just checking that :)
[13:47] <seb128> which matches his email autorespond
[13:47] <willcooke> cc looks clear
[13:47] <willcooke> anyone got any other bugs / lists of bugs to talk about?
[13:48] <kenvandine> ok, oh i think he extended that and we never updated the calendar
[13:48] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html
[13:48] <seb128> same 1 bug there
[13:48] <willcooke> yeah
[13:48] <Laney> that's probably a return TRUE in the plugin somewhere
[13:48] <Laney> like the other one I added
[13:48]  * Laney hints
[13:48] <seb128> oSoMoN, ^
[13:48] <Laney> :-)
[13:49] <willcooke> :)
[13:49] <willcooke> k, moving on to...
[13:49] <oSoMoN> ack
[13:49] <willcooke> #AOB
[13:49] <willcooke> #topic AOB
[13:49] <willcooke> anyone got anything to share?
[13:49] <seb128> L_aney pointed out that now would be a good time to get going with updating GNOME to 3.29
[13:49] <seb128> would be nice if we did it as a team effort
[13:49] <kenvandine> +1
[13:50] <andyrock> happy to help
[13:50] <Beret> hi
[13:50] <didrocks> agreed, however, unsure we have scheduled enough slots for everyone to deal with it, but let's see :)
[13:50] <seb128> those who want to join please do, use IRC & version and open bugs for updates so we don't duplicate work
[13:50] <Beret> does the desktop installer support RAID at all these days?
[13:50] <Beret> I want to install a machine with software RAID and FDE
[13:50] <willcooke> Beret, two secs..
[13:50] <Beret> hah
[13:51] <seb128> Beret, we are in a meeting atm
[13:51] <willcooke> I thought you were going to ask in the other channel :D
[13:51] <Beret> oh
[13:51] <Beret> you're all in a meeting
[13:51] <willcooke> nearly finished
[13:51] <Beret> I was trying to save will from my ping
[13:51] <Beret> take your time
[13:51] <Beret> this is obviously not urgent
[13:51] <Beret> my shiney NUC is awaiting its new softwrae load
[13:51] <seb128> k, so yeah, let's update GNOME
[13:51] <willcooke> k, so seb128 can you lead the co-ordination of the upgrade
[13:51] <seb128> :)
[13:51] <seb128> yes
[13:51] <willcooke> woot
[13:52] <willcooke> anyone got anything else?
[13:52] <seb128> also good time to start using the new workflow
[13:52] <willcooke> +1
[13:52] <willcooke> MOAR Trello
[13:52] <seb128> since we have git branches for quite some components now
[13:52] <seb128> haha
[13:52] <willcooke> ;)
[13:52] <kenvandine> oh yeah...
[13:52] <seb128> it's documented on http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[13:52] <seb128> ups
[13:52] <seb128> https://wiki.ubuntu.com/DesktopTeam/git
[13:52] <Laney> yes, do people feel like we have a handle on the rls tracking bugs?
[13:52] <willcooke> will be nice to see if we can iron out all the git process issues
[13:52] <Laney> I think it was considered fake news last time I raised this
[13:52] <Laney> but...
[13:53] <Laney> seems to me like there's things which sit there from week to week
[13:53] <seb128> I'm happy to have another look to the current list, like I did the first time that was raised
[13:54] <seb128> my gut feeling is that we have an handle on the important issues
[13:54] <seb128> but we are not that good at getting some of the things that don't look important off the list
[13:54] <willcooke> I think the list itself is in good shape.  The problem we have is when there is something that we don't know what to do about right away we skip it for a week.  We need to be better at assigning an owner who can look at it outside of the meeting when times is
[13:54] <willcooke> time isn't as pressured
[13:54] <seb128> or some of the things we keep dismissing and having to come back to
[13:54] <Laney> not to pick on any one person
[13:54] <Laney> but https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758035
[13:55] <Laney> this is on theh list and didn't see an update for ages
[13:55] <seb128> right, it should probably be off the list
[13:55] <Laney> this is what I'm raising
[13:55] <Laney> if the list is things to work on
[13:55] <seb128> it's one of those which we keep skipping over because that's not really one we can act on
[13:55] <Laney> then it should be kept that way imho
[13:55] <seb128> right & agreed
[13:56] <seb128> we should probably just be more agressive to remove those
[13:56] <seb128> and maybe create trello cards in backlog in exchange
[13:56] <seb128> the reason we have that one (and some others) still tagged is that some team members argue it's important we keep an eye on the issue
[13:56] <seb128> but yeah, rls-nn is probably the wrong way to do it
[13:57] <Laney> to me the point of that list was things that were going to be worked on to a resolution
[13:58] <seb128> yes
[13:59] <seb128> the issue is that we believe some of the items ought to be driven to a resolution but we don't have the manpower at the time we review the list to do something about them
[13:59] <seb128> so they never get properly handled / stay on the backlog
[13:59] <seb128> I'm unsure what's the best way to deal with that
[13:59] <willcooke> seb128, perhaps we should have a section in our managers meeting to check on the progress of things which were flagged as needing work but dont have anyone to do it
[13:59] <willcooke> that's likely to use a lot of time up though, but it needs to be done
[14:00] <willcooke> or, as you say, a Trello list
[14:00] <Laney> everything in that list is meant to be assigned when it is put there (by us), or when we notice it at a weekly meeting
[14:00] <seb128> yeah, I think my preference would be to get those that needs investigation in the trello backlog
[14:00] <seb128> but it's moving from one backlog list to another one
[14:00] <Laney> the issue is that the meeting is what? too rushed to consider it properly?
[14:00] <seb128> so I'm unsure it's solving anything
[14:00] <willcooke> Laney, yeah, feels too rushed
[14:01] <seb128> also we don't have the whole team
[14:01] <seb128> often assigning things to e.g robert_ancell or duflu doesn't have the outcome we want
[14:01] <Laney> right
[14:02] <willcooke> If part of the problem is that people need chasing more, that's easily addressed
[14:02] <Laney> sort of confused to be honest why assigning work to people doesn't result in the work getting done
[14:02] <Laney> but I probably don't understand properly the problem
[14:02] <Laney> s/bad english/good english/
[14:02] <seb128> well, that's another issue
[14:03] <seb128> I discussed a bit that at GUADEC with Robert, his view was that it's difficult to keep track of things when they are not at the same place
[14:03] <seb128> like he uses the trello board but doesn't keep up with launchpad
[14:03] <seb128> so he said he would prefer to have those as trello cards
[14:03] <kenvandine> so getting cards for those should help
[14:03] <kenvandine> at least for him
[14:03] <seb128> yeah
[14:04] <seb128> but we can't flex for each individual preference
[14:04] <Laney> facepalm
[14:04] <seb128> we can also decide that people who don't deal with their assigned bugs needs to be reminded to
[14:04] <seb128> anyway, that starts being a management's discussion and probably an issue we need to resolve but not here/now
[14:04] <Laney> like, fix your filters so you see assigned bugs
[14:04] <Laney> would be my preference
[14:05] <seb128> yeah
[14:05] <didrocks> (agreed)
[14:05] <seb128> so going back to the topic
[14:05] <seb128> I would suggest to not assign to people who didn't agree to during the meeting
[14:05] <seb128> in case we don't know what to do, let's add an action item for the most-appropriate-manager to find an assignee by the next meeting
[14:05] <seb128> and review those actions in the next meeting
[14:05] <kenvandine> yeah
[14:05] <willcooke> +1 sounds like a good step forward
[14:06] <willcooke> then we at least get an owner between now and the next meeting
[14:06] <seb128> Laney, let's try that + make clear cut on the items rather than skip when we don't know waht to do
[14:06] <seb128> and see how it goes?
[14:07] <seb128> k, I think we are done with this topic
[14:07] <seb128> other topic?
[14:07] <willcooke> #topic tkamppeter
[14:07] <willcooke> - ippusbxd: Release of version 1.33, containing changes contributed by Google's Chrome OS printing guru David Valleau, for more robust operation and compatibility with more printer manufacturers/models.
[14:07] <willcooke> - cups-browsed: Investigating crash bug on manual definition of printer clusters.
[14:07] <willcooke> - Google Summer of Code 2018: Mentoring of the students on Common Print Dialog Backends and printer auto-selection by job. Especially gave ideas to the students on point where they got stuck.
[14:07] <willcooke> - Upgraded main laptop to Cosmic.
[14:07] <willcooke> - Bugs.
[14:08] <willcooke> #topic AOB
[14:08] <Laney> that would be good, but I'm still worried about activity once things are assigned
[14:08] <Laney> maybe that's not my problem
[14:08] <Laney> what is this quote cutting off the meeting bot :-)
[14:08] <seb128> right, that's probably something we need to keep an eye on
[14:08] <seb128> that doesn't work
[14:08] <seb128> the bot is going to put it back next time it changes the topic :p
[14:08] <willcooke> Right, lets wrap up and see how we get on next week
[14:09] <willcooke> thanks all
[14:09] <willcooke> #endmeeting
[14:09] <meetingology> Meeting ended Tue Jul 24 14:09:04 2018 UTC.
[14:09] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-07-24-13.30.moin.txt
[14:09] <didrocks> thx!
[14:09]  * Laney holds breath
[14:09] <seb128> right
[14:09] <Laney> DAMN IT
[14:09] <seb128> thx
[14:09] <seb128> see :)
[14:09] <willcooke> :D
[14:09] <seb128> hehe
[14:09] <Laney> sorry I'm sure it was funny :P
[14:09] <willcooke> :)
[14:09] <seb128> we should probably remove the other 2 quotes
[14:09] <seb128> unsure how it looks like for new comers
[14:09] <seb128> it's a bit weird
[14:09] <willcooke> thanks for caring about this stuff Laney (bugs)
[14:09] <didrocks> short titles ftw!
[14:10] <Laney> Home of the No Fun Desktop Team
[14:10] <Laney> ;-)
[14:10] <oSoMoN> or configure the bot to override the topic during the meeting, instead of appending to it?
[14:10] <seb128> lol
[14:10] <Laney> np willcooke
[14:10] <willcooke> speaking of no fun, Beret - you want to do software RAID?
[14:10] <willcooke> ;DD
[14:10] <oSoMoN> :)
[14:10] <Beret> hah
[14:11] <Beret> yes, I bought a machine and put two NVMe SSDs in it
[14:11] <Beret> I want to do software RAID 1 and FDE
[14:11] <Laney> the main reason for me to care is that it's annoying when there is no way to get things worked on other than pinging
[14:11] <Beret> it doesn't look like RAID is in the desktop installer these days
[14:11]  * Laney stares at the "track rls bugs" card in trello
[14:11] <Laney> bbbbbrrrrbbbb
[14:11] <willcooke> Beret, I think LVM used to take care of that, but haven't looked for a while.  jibel - have you looked at LVM doing software raid?
[14:12] <willcooke> also maybe xnox knows (software raid in the desktop installer)
[14:12] <seb128> https://askubuntu.com/questions/505446/how-to-install-ubuntu-14-04-with-raid-1-using-desktop-installer
[14:12] <Beret> my tentative plan was to boot the server installer, setup the RAID device, then boot the desktop installer and see if I could pikc that as a target
[14:13] <Beret> seb128, thanks
[14:14] <Beret> interesting that the last comment on there recommends going the server route
[14:15] <didrocks> well, if you don't want to do the chroot, it's indeed easier
[14:15] <didrocks> however, you will have server + desktop components installed
[14:15] <didrocks> and thanks god for mdadm --assemble compared to the old way of manually declaring all of this :)
[14:16] <willcooke> didrocks, sounds like a good usecase for installer+1 ;)
[14:16] <Beret> agreed
[14:16] <didrocks> willcooke: depends on what we are asked for it. But yeah
[14:16] <didrocks> automated RAID has a lot of complex use case
[14:16] <Beret> though tbh, I can't imagine many people would use it
[14:16] <didrocks> like here, it's doing the "let's have 2 grubs"
[14:17] <Beret> I myself haven't done desktop + RAID in years
[14:17]  * didrocks has only done server on RAID
[14:17] <Beret> right
[14:17] <willcooke> same. When I had 3 1TB drives I did it
[14:17] <didrocks> for desktop, I rely on backup instead of RAID1
[14:17] <willcooke> and lot data because of it
[14:17] <willcooke> *lost
[14:17] <Beret> I only did it in the case of a server that I turned into a desktop
[14:17] <didrocks> and RAID1 < backups, before if you remove a file, it's lost
[14:17] <jibel> install the desktop task (ubuntu-desktop^) not the meta package
[14:17] <jibel> on top of a server installation
[14:17] <didrocks> and the gain perf from it, for a desktop… ~average
[14:18] <Beret> you're doing a great job of talking me out of a non-existing feature of the desktop installer
[14:18] <Beret> pretty sure you get extra credit for that
[14:19] <willcooke> good work team
[14:19] <jibel> same I've a standard disk setup for on the desktop and a NAS with RAID that syncs my home dir for backup
[14:19] <didrocks> I explain probably why it's not implemented :) Not a lot of gain going RAID for desktop :p
[14:19] <willcooke> IMO, create a normal boot partition and then stick, say, /home on a software raid
[14:19] <willcooke> dont boot from s/w raid
[14:22] <Beret> ok
[14:22] <Beret> you win
[14:22] <Beret> I think I'm going to a normal fde deskopt install on the first disk, and a dedicated zpool disk on the second for containers
[14:22] <Beret> and stick to my NAS backup
[14:23] <didrocks> Beret: we can still discuss it if/when we do a new installer thingy, and do a + / - comparison to see if there is a real use case. Would be great to collect regular data on this though
[14:23] <Beret> yeah
[14:23] <didrocks> Beret: yeah, sounds like a better setup to me
[14:23] <Beret> I'd be surprised if there were enough consumers of such a solution to warrant building it
[14:23] <didrocks> yeah
[14:27] <jibel> it's also cheaper. You can use a fast SSD on your desktop and cheap rotational drives on your NAS with lot of space for backups. Instead of several SSDs with wasted space on your desktop for the RAID array
[14:31] <ricotz> oSoMoN, I have copied 6.1.0~rc2 to -prereleases ppa
[14:32] <oSoMoN> ricotz, ack, thanks
[14:32] <ricotz> I have some local changes which are not worth another rebuild
[14:47] <seb128> andyrock, is the pr I added to https://trello.com/c/tPfrSALh/147-fix-auto-repeated-bindings-for-g-s-d-too right or is that a different work?
[14:50] <andyrock> seb128: I already got this https://trello.com/c/caeUuKkH/148-media-keys-some-shortcuts-should-ignore-auto-repeat-key-events
[14:51] <seb128> andyrock, are those duplicates card? if so feel free to archive 147
[14:51] <andyrock> seb128: done
[14:51] <seb128> thx
[14:51] <andyrock> I've one card for gnome-shell and one for g-s-d
[14:57] <seb128> k
[15:00] <xnox> Beret, server installer + install ubuntu-desktop should work; if your nvme/machines is fancy, you may be able to setup intel matrix raid using preos/uefi screens - then i think that could work even with desktop installer.
[15:40] <ricotz> are language-support-translations-* packages/references are still a thing?
[16:04]  * Laney is about to push a mass update to remove the content of many of the packaging bzr repos
[16:16] <Laney> DONE
[16:16] <Laney> LONG LIVE BZR


[05:49] <pavlushka> Morning Kilos !
[05:49] <Kilos> morning pavlushka how are yoiu today lad
[05:50] <pavlushka> Great and fixing little things in the house :)
[05:51] <Kilos> if you keep the litle things in good order the big things never break
[05:52] <pavlushka> exactly, :)
[05:52] <pavlushka> bbl, goota run.
[05:52] <Kilos> ok
[05:57] <Kilos> you didnt use my additions
[05:57] <Kilos> hmm...
[06:06] <pavlushka> oh my, Kilos I used meld to merge diff, I will re-check the revision, no problem.
[06:06] <Kilos> lol
[06:07] <Kilos> np
[06:10] <Kilos> too much to read again
[07:40] <pavlushka> AudaciousTUX: howdy?
[12:40] <pavlushka> Hello zaki I was looking for you:)
[12:48] <zaki> hi pavlushka good afternoon.
[12:52] <zaki> Kilos: and pavlushka haow are you?
[12:54] <pavlushka> zaki: me fine, cant tell about Kilos :p
[12:55] <pavlushka> zaki: I need you testimonial on this https://wiki.ubuntu.com/pavelsayekat.
[12:57] <zaki> thinking about this tomorrow. when your going to apply?
[12:58] <zaki> yesterday* :p
[12:58] <pavlushka> may be this month, so the board will hold at the beginning of the next month, :)
[12:58] <pavlushka> zaki: I got that you meant yesterday, lol
[12:59] <zaki> he he.   :D i have no problem now with wired or wireless connectivity.
[17:27] <zaki> work nicely.
[17:32] <pavlushka> zaki: but kamrul is still facing the issue, right?
[17:32] <pavlushka> wb AudaciousTUX !
[17:34] <zaki> yess pavlushka
[17:34] <pavlushka> AudaciousTUX: anything wrong? you seem to be quiet lately, ^^
[17:38] <pavlushka> zaki: we have to work more on this issue, wifi, lets see.
[17:40] <zaki> oky. (y)
[17:42] <AudaciousTUX> ghumailam etokkhon pavlushka
[17:42] <pavlushka> অবশেষে অরিন্দম কহিল, :)
[17:43] <AudaciousTUX> by the rasta.... meetup chai -_-
[17:46] <pavlushka> sure, by the Highway, আমি ঢাকা গেলেই ফার্মগেইট দিয়া রামপুরা যাই, টিভি দেখতে, :p
[17:47] <AudaciousTUX> :3
[19:40] <pavlushka> brb