[06:51] <brobostigon> morning boy and girls.
[07:10] <zmoylan-pi> o/
[07:13] <brobostigon> o/
[07:28] <marshmn> o/
[13:04] <ali1234> interest... the steal message alert thing appears to stop counting at 101 items :)
[13:04] <ali1234> *steam
[15:10] <marshmn> I'm giving some Google 'mesh' WiFi adapters a try... (replacing previous TP-Link powerline network) - seems OK so far, but early days...
[15:10] <marshmn> very nice and easy to configure
[15:12] <marshmn> and I already see some benefits - with my powerline WiFi adapters there seemed to be some issues with uPNP traffic not getting passed through very well (resulting in not being able to use Noson to control Sonos speakers)
[15:12] <marshmn> that seems to work fine with the new setup
[15:15] <daftykins> the earlier adapters possibly didn't handle things at a low enough level, although to my mind the idea of wireless packets hopping multiple times is horrible - much rather wired infrastructure and access points centralised to a switche - but granted you might be renting or some such and not have that option
[15:15] <daftykins> s/switche/switch/
[15:17]  * penguin42 is surprised they had problems with uPNP - I'd assumed they were layer2
[15:17] <daftykins> yeah i can't think what's up with that
[15:17] <daftykins> i think lower end ones can fail to handle broadcast traffic of types o0
[15:31] <marshmn> I'm renting - so yes, my options are limited
[15:32] <marshmn> I think that with the powerline adapters the uPNP traffic wasn't passed between the 2.4GHz and 5GHz networks
[15:32] <marshmn> at least that's my guess
[15:32] <marshmn> Sonos devices only operate on 2.4GHz (I believe) and my laptop was on 5GHz


[00:00] <balloons> elopio, no, because it's under ~/, not our fake home
[00:00] <balloons> I mean, yes it's created but not where it needs to be
[00:01] <elopio> balloons: yes, because I suppose gi.repository uses the env var HOME, not the initctl var HOME
[00:01] <elopio> but we can't patch both because the app will not open.
[00:02] <elopio> balloons: maybe on the phone we can stop patching home for now.
[00:02] <balloons> elopio, music is currently shipping with a backup/restore
[00:03] <balloons> it's the same problem
[00:03] <elopio> balloons: well, we can do it without restore either.
[00:03] <balloons> elopio, but I think we can work around it for reminders
[00:03] <elopio> it will fail in the case you already have evernote accounts on the phone.
[00:03] <balloons> launch the app, then set initctl
[00:04] <elopio> and it will leave accounts behind if you stop the test before clean up
[00:04] <elopio> balloons: how will the app see the new HOME if it's already launched?
[00:05] <balloons> I'm trying to think.. but it's the account creation bit that doesn't have the proper home right?
[00:05] <balloons> so launch, then tweak for account creation. The app just cares about env HOME
[00:08] <balloons> i'll try what I'm thinking
[00:08] <elopio> balloons: you mean
[00:08] <elopio> 1. launch with initctl patched
[00:08] <elopio> 2. create the account patching also env var
[00:08] <elopio> 3. enjoy.
[00:08] <balloons> elopio, yes.. let me try :-[)
[00:08] <elopio> if that's the case, 1. will fail anyway because it seems the app has no permission to access the patched initctl home.
[00:09] <elopio> the step #2 I think will work
[00:13] <balloons> elopio, the patched home is the same as initctl home
[00:14] <balloons> atm, you have initctl home as ~/ and HOME as our fake dir
[00:15] <elopio> balloons: on the phone?
[00:15] <balloons> elopio, indeed
[00:15] <elopio> I don't think so, but I've been slow for 2 hours now
[00:16] <balloons> lol.. I think it's time to call it
[00:16] <balloons> let's land as-is with everything
[00:16] <balloons> agreed?
[00:16] <elopio> balloons: in the end, I reverted to the patch_home you made
[00:16] <elopio> that's if click, patch only initctl
[00:17] <balloons> alright.. and jenkins is hating on my pep8 changes
[00:17] <balloons> i think this is a wrap for tonight
[00:18] <elopio> :D
[00:18] <elopio> yeah, lets continue tomorrow.
[00:18] <balloons> cheers elopio :-_
[00:18] <elopio> I think we have two things to find out
[00:18] <balloons> ty much as usual
[00:18] <elopio> why it doesn't launch if HOME is patched.
[00:18] <elopio> and why when initctl is patched, the app can't read it.
[00:19] <balloons> my brain is mush.. I was thinking you were only patching home not initctl home
[00:19] <balloons> that's very odd then
[00:19] <elopio> it's the other way around. Well, I started patching both and that works for credentials.py, but the app can't be launched which should be the purpose :)
[00:19] <elopio> but you go and get some rest. I will switch context.
[04:19] <pitti> Good morning
[08:30] <jibel> pitti, for sudo on the ssh host, what I did is: if there is a password passed to the ssh runner (can be a file containing the password or the password in clear text) I setup askpass, then the runner tries to determine if it can sudo with askpass and sudo without it. Depending on the result it adds root-on-testbed and write the right auxverb, do you think it's okay?
[08:33] <pitti> jibel: where "sudo without it" means "sudo with an SSH_ASKPASS which just returns an empty string"?
[08:33] <pitti> jibel: it must never try and call sudo without an askpass, that might hang eternally
[08:34] <pitti> jibel: yes, that sounds nice; so with sudo being available, the auxverb would always run commands as root
[08:34] <jibel> pitti, sudo -n /bin/true
[08:34] <pitti> fun, so we'd call sudo su -c ... phablet :)
[08:34] <pitti> jibel: oh cool, I didn't know about -n
[10:33] <jibel> pitti, I pushed latest version of the ssh driver to lp:~jibel/+junk/adt-virt-ssh
[10:36] <jibel> pitti, tried on mako connected other usb with libpng and tabix
[10:37] <jibel> the command looks like: ./run-from-checkout -d libpng --- ssh -s virt-subproc/adb.ssh -d -l phablet -P /tmp/test -- --rw -s 04dc228756e547e7
[10:38] <jibel> where /tmp/test contains the password for user phablet and the id at the end is the serial of the device
[10:38] <jibel> not needed if there is only one device
[10:38] <pitti> \o/
[10:42] <pitti> jibel: only 6 retries to re-fix nut, go broken tests!
[10:45] <pitti> jibel: ah, I suppose root-on-testbed can go from the "capabilities" initialization at the top?
[10:47] <pitti> jibel: FYI, any bomb() terminates the whole thing, so a "return False" will never be needed; so execute_ssh_script() doesn't need to return a bool (exceptions are more pythonic, anyway)
[10:50] <pitti> jibel: oh, I see you do "if not execute_ssh_script('revert')", then perhaps that bomb() should rather be adtlog.warning()?
[11:02] <pitti> jibel: ah, need to figure out the magic to export the session bus and other environment to that shell
[11:18] <elfy> wxl: just a gentle prod that the lubuntu alpha images will want to be marked as ready
[11:29] <pitti> jibel: I imported it into a new branch for now: http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=shortlog;h=refs/heads/adt-virt-ssh
[11:30] <pitti> jibel: I'm running into a few cases which don't work (specifying password, not specifying a script, etc.), I'll hack on it, commit fixes there, and once everything is ready consolidate the commits
[11:30] <pitti> jibel: many thanks!
[11:34] <jibel> pitti, I didn't expect it to be very robust as I just tried the happy path with basic deb tests
[11:34] <jibel> pitti, feel free to change it the way you think it best
[11:34] <jibel> is
[12:41] <pitti> jibel: meh @ all those new broken tests -- folks in Debian really ought to actually try their tests before uploading :/
[12:42] <jibel> pitti, and lot of them are failing with the same error "cannot locate Dh_Lib.pm ..."
[12:42] <pitti> yeah
[12:44] <pitti> jibel: can I just delete http://d-jenkins.ubuntu-ci:8080/view/Upgrade/job/upgrade-kubuntu-precise-trusty-desktop-backports-{i386,amd64} (see shadeslayer's ping) or does that need some bzr update?
[12:46] <jibel> pitti, you can it won't be auto-recreated (unless I republish trusty) Which channel did he ping? I missed it
[12:46] <pitti> jibel: in #u-devel
[12:50] <jibel> pitti, I'll remove the profiles from the branch too. So they won't be recreated just in case I'd need to for 14.04.1
[12:50] <pitti> jibel: merci
[13:10] <elfy> balloons: if you could cast your eye over https://code.launchpad.net/~elfy/ubuntu-manual-tests/1334643/+merge/224612 that would be super :) would like to get that done prior to me calling for the next set of our tests
[13:59] <pitti> jibel: do I see that right, you only pass the --password to the setup script for configuring sudo? or did you actually have an SSH_ASKPASS command somewhere that I'm missing?
[14:00] <pitti> jibel: I now taught adt-virt-ssh to create SUDO_ASKPASS if the setup script didn't return a sudo_askpass and there's a --password
[14:03] <jibel> pitti, right if you do that then you can probably remove all the askpass thing from adb.ssh. It's better to have this in adt-virt-ssh as it's quite generic for any type of host
[14:04] <pitti> jibel: ack, thanks for confirming
[14:04]  * balloons looks at https://code.launchpad.net/~elfy/ubuntu-manual-tests/1334643/+merge/224612
[14:05] <jibel> so adb.ssh will only setup the forwarding rule and copy the keys which is saner
[14:06] <balloons> elfy, I'm going to leave a few inline comments on your mp
[14:18] <elfy> balloons: thanks for that - done those - pushed it back again I have
[14:18] <elfy> that inline comments thing is pretty useful :)
[14:18] <jibel> pitti, ah I remember why I did it this way, it's because in adt-virt-ssh you can only setup SUDO_ASKPASS over ssh, so you have to 1rst setup the connection then create SUDO_ASKPASS. But since we are using the connection anyway to verify if the user can sudo it doesn't matter where it's done, and it's better to do it in adt-virt-ssh anyway
[14:19] <pitti> jibel: right, can_sudo() already has the ssh_cmd, it doesn't need to use the full auxverb
[14:20] <pitti> jibel: http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=commitdiff;h=6839dc works quite well here
[14:20] <balloons> elfy, approved :-)
[14:21] <elfy> balloons: cheers I'll merge and sync it then :)
[14:22] <jibel> pitti, very nice!
[14:23] <balloons> excellent.. did we get phillw's bug yet elfy ?
[14:23] <elfy> balloons: not seen one yet
[14:23] <elfy> as soon as I do I will pounce on it though
[15:09] <jibel> pitti, thinking about the ssh runner for cloud instances, the ssh script needs know the instance-id for example for shuting down the instance. What do you think is best to make it persistent, pass it to the runner then back to the script that manages the instances in the close hook would be ok?
[15:10] <pitti> jibel: I think more generically it could return a workdir= which gets passed back on subsequent invocations
[15:10] <jibel> pitti, right that was the idea.
[15:11] <jibel> nothing specific to any type of cloud but some kind of data field that is passed back
[15:11] <pitti> jibel: or maybe just a "state=", which the setup script can interpret in any way it likes
[15:11]  * jibel nods
[15:36] <pitti> jibel: the adb setup script determines the key from your ~/.ssh; it should export that as identity=, right?
[15:36] <jibel> pitti, right
[15:36] <pitti> jibel: i. e. search for private keys instead of public keys, copy the corresponding pub key, and identity= the private key
[15:36] <pitti> jibel: ok, doing that
[16:01] <wxl> elfy: now i need to check if i have permissions to do so :)
[16:03] <elfy> :p
[16:03] <elfy> wxl: you done the release notes?
[16:04] <wxl> elfy: phillw mentioned some template that i don't think i've yet had a link to but it won't be too hard
[16:04] <wxl> elfy: sadly i had no luck rallying the ppc/amd64+mac crowd :(
[16:05] <elfy> pretty much evrywhere is quiet I think
[16:05] <phillw> wxl: it's not urgent at alpha1 :)
[16:05] <wxl> elfy: where does one mark the images as ready?
[16:05] <wxl> phillw: i know but i fear it's a harbinger of what's to come
[16:05] <balloons> my guess is you'll see posts after it's released about how it doesn't work :-)
[16:05] <elfy> http://iso.qa.ubuntu.com/qatracker/milestones/317/builds
[16:05] <balloons> which is fine for alpha1
[16:06] <elfy> wxl: ^^ - find the looby lou ones - click the button in the 'grey' bar for it - selects all
[16:06] <phillw> wxl: julien will be adding you as lubuntu-product-manager (hopefully today).
[16:06] <elfy> wxl:  then you go to the bottom - administration - status - mark as read and update build status
[16:06] <wxl> sigh don't see any option there elfy. my guess is i still lack permissions to do it.
[16:07] <elfy> wxl:  you want me to do it for you?
[16:07] <wxl> yeah no administration business so it's on julien i guess
[16:07] <wxl> elfy: sounds like i'll need yyou to siiiiiiiiiiiiiiigh
[16:07] <elfy> or that :P
[16:07] <wxl> unfortunately he takes a bit to respond and i bothered him about it on monday in two separate ways..
[16:07] <phillw> elfy: if you'd kindly mark the tested ones as good to go :)
[16:07] <elfy> I can't mark them - ask balloons to do it for you
[16:08] <phillw> or balloons ^^
[16:08] <elfy> phillw: no has perms to mark it - I'd be able to do xubuntu and studio only
[16:08] <elfy> s/no/I no have perms
[16:09] <balloons> mark which ones?
[16:09] <elfy> lubuntu alpha 1's
[16:10] <balloons> everything you say?
[16:10] <elfy> wxl: ^^
[16:10] <wxl> oh sorry
[16:10] <balloons> I marked what had results
[16:10] <wxl> not ppc/amd64+mac
[16:10] <wxl> everything else
[16:10] <wxl> so yeah that's right :/
[16:12] <balloons> gotta love the prints :-) <3 queuebot!
[16:12] <wxl> yay thanks balloons
[16:14] <elfy> just the release notes now then :p
[16:14] <elfy> I love this not having alphas to worry about this cycle \o/
[16:15] <phillw> elfy: you guys not playing alphas?
[16:15] <elfy> not this time around
[16:19] <wxl> phillw: so release note template?
[16:21] <phillw> wxl: https://wiki.ubuntu.com/TrustyTahr/Alpha1/Lubuntu
[16:21] <phillw> only new thing is kernel :)
[16:23] <wxl> phillw: stupid question but i assume i should copy and paste to /UtopicUnicorn/Alpha1/Lubuntu, no? ;)
[16:23] <phillw> wxl: that's as easy a way as any :)
[16:23] <wxl> phillw: that's what i thought :)
[16:24] <phillw> or, you can chose copy from the drop down of options :)
[16:24] <phillw> which is easier :)
[16:24] <wxl> ah k
[16:27] <wxl> argh logging in is taking FOR-EV-ER
[16:35] <phillw> wxl: do you want me to copy it over?
[16:35] <wxl> phillw: no i'm editing now. is upgrading from previous versions relevant?
[16:36] <phillw> it could be. I usually switch to release+1 once A1 is out :)
[16:36] <phillw> but, I'm a glutton for punishment :P
[16:37] <wxl> phillw: https://help.ubuntu.com/community/UtopicUpgrades%7CUpgrade%20Instructions is a fail
[16:37] <wxl> for that matter, so is trusty
[16:39] <phillw> wxl: use the command line... http://manpages.ubuntu.com/manpages/precise/man8/do-release-upgrade.8.html
[16:39] <phillw> it will be release agnostic :)
[16:40] <phillw> if someone wants to run lubuntu a1, they should now of the command line.... they will no doubt need it at some point :D
[16:40] <phillw> s/now/know
[16:51] <wxl> phillw: um, what's new? :)
[16:52]  * wxl looks up the kernel
[16:55] <wxl> 3.15.0
[16:58] <wxl> not seeing anything particularly exciting :)
[17:02] <wxl> um how do i find out what the upstream is for the kernel?
[17:02] <phillw> wxl: let me just fire up the VM :)
[17:03] <phillw> wxl: 3.15
[17:04] <phillw> ditto :)
[17:04] <wxl> phillw: how does one figure this out?>
[17:05] <phillw> I just do a uname :), you can ask on #ubuntu-kernel to confirm that it will remain as 3.15. But as it is A1, just state what it comes with?
[17:05] <wxl> ah
[17:05] <phillw> the kernel freeze is late in the cycle.
[17:43] <phillw> wxl: I've replaced me with you at https://wiki.ubuntu.com/Lubuntu/Testing/#When_do_they_build I will keep an eye on the builds and ping Julien if I see them fail to build :)
[17:43] <phillw> But, that page is now yours :P
[18:12] <elopio> ping ubuntu-qa, somebody around for a quick review?
[18:12] <elopio> https://code.launchpad.net/~elopio/ubuntu-calendar-app/fix1334777-pep8/+merge/224700
[18:13] <la_juyis> elopio, I'll take a look, but we'll need someone else as well :)
[18:13] <elopio> la_juyis: thanks
[18:14] <elopio> la_juyis: this is just static checks, so if you can run flake8 on an up-to-date trusty and you like the diff, it's good to go.
[18:15] <la_juyis> elopio, yeah, was just realising that
[18:15] <la_juyis> let's see
[18:22] <la_juyis> elopio, and some code cleanup as well! good
[18:22] <la_juyis> elopio, everythin looks good from here
[18:22]  * balloons awaits la_juyis to approve :-)
[18:23] <la_juyis> balloons, coming!
[18:23] <la_juyis> :)
[18:23] <balloons> hehe
[18:24] <la_juyis> balloons, done :)
[18:27] <elopio> la_juyis: thanks.
[18:27] <elopio> la_juyis: for when you get bored and want to do some programming, this is waiting for you:
[18:27] <elopio> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1327354
[18:28] <balloons> I may have had something to do with that bug :-)
[18:30] <la_juyis> elopio, I'll have some time tomorrow. Wanna pair up? :)
[18:31] <elopio> la_juyis: sure, but you lead.
[18:38] <wxl> phillw: https://wiki.ubuntu.com/UtopicUnicorn/Alpha1/Lubuntu#preview
[18:38] <wxl> s/\#preview//
[18:39] <phillw> wxl: If I vanish, it will be because
[18:39] <phillw> update-manager -d -c
[18:39] <phillw> killed piglet :)
[18:39] <wxl> phillw: uh oh ;)
[18:40] <phillw> wxl: looks great to me :)
[18:42] <wxl> phillw: official release coming right up
[18:42] <phillw> I ran out of room on / last attempt, have freed up some room.
[18:44] <wxl> alpha2 won't be available until ~july 3rd, right?
[18:44] <phillw> wxl: yeah, wait for the release team to say 'go'. Premature announcements are frowned upon :)
[18:44] <wxl> ko
[18:45] <phillw> wxl: bookmark https://wiki.ubuntu.com/UtopicUnicorn/ReleaseSchedule :)
[18:45] <wxl> phillw: already done :)
[18:45] <phillw> not sure who is announcing it, possibly stgraber ?
[18:47] <stgraber> phillw: yeah, that'll be me
[18:47] <phillw> ooh, net split!
[18:49] <phillw> stgraber: thanks, I'm just easing our new release manager in. Thanks for all your and balloons help in getting him up to speed on things. He is an experienced lubuntu tester, just needs to find his way round release management :)
[18:49] <phillw> ooh, and elfy :)
[18:51] <wxl> announced
[18:51] <phillw> wxl: had you got confirmation from stgraber ? :)
[18:53] <phillw> greetings DalekSec
[18:54] <wxl> phillw: oops. :(
[18:54] <wxl> i didn't announce alpha2. that's what i thought you meant phillw
[18:54] <phillw> wxl: wait for the duty announcer to say it is live. As it's A1, no real harm done. :)
[18:55] <DalekSec_> Howdy.
[18:55] <elfy> hi DalekSec_
[18:55] <wxl> phillw: well i'll wait before spreading the word any farther. sorry stgraber
[18:57] <phillw> wxl: also, if I'm not about on milestone release, give unit193 a polite ask to update the mirror server. As he is here as DalekSec I'm sure he will do so once the announcement goes out :)
[18:57] <phillw> well, was before net split :P
[18:59] <elfy> lol
[19:00] <elopio> balloons: on calendar, the clean environment is not working, right?
[19:06] <balloons> elopio, I seem to remember saying that yes
[19:07] <elfy> balloons: replied to the mail - did you see the pastebin in PMs ?
[19:08] <balloons> elfy, no weird.. it didn't ping me, but I see the pm now
[19:09] <elfy> ok - must have been the tomaw business I guess
[19:09] <balloons> blame the netsplit ;-)
[19:09] <elfy> yep :)
[19:10] <ianorlin> hmm testcase for pcmanfm still mentions open folder as root although that was removed in version 1.2.0
[19:10] <balloons> so for time, yea 30 mins to maybe an hour of demo.. hopefully not an hour, heh
[19:10] <balloons> ianorlin, file a bug, or even file and propose something to fix :-
[19:10] <balloons> it's quick to do, and me and elfy would happily help you
[19:11] <elfy> indeed
[19:11] <balloons> ianorlin, https://bugs.launchpad.net/ubuntu-manual-tests/+filebug
[19:12] <phillw> elfy: once 14.10 upgrade is done (running), I'll go through the alternate test cases, the dual boot has changed terminology and there could well be a bug with the 32bit one.
[19:13] <elfy> ianorlin: make sure to put the testcase number in the bug
[19:13] <elfy> saves someone searching for it :)
[19:14] <elfy> phillw: okey doke
[19:16]  * wxl hums the final jeopardy song
[19:16] <phillw> 32 bit one did not offer me any options in side-by-side. But I was running off-line as using a 3G device gets expensive :)
[19:17]  * elfy just sits back and watches wxl
[19:17] <elfy> :p
[19:18] <balloons> elfy, what's a good day for you for the hackfest for testwriting?
[19:18] <balloons> I'll make an event page for it once we have a day.. let's just pick now
[19:18] <balloons> July 8th ok?
[19:19] <elfy> if we run them 19-22 UTC any day is good
[19:19] <balloons> elfy, yep I'm thinking that;s the timeframe to run it
[19:20] <balloons> ok, I'll put down July8th 19-22 UTC
[19:20] <elfy> but I'd rather have it a bit later in the schedule - give me some time to sort it out
[19:20] <balloons> elfy, yea we need to tag the bugs or otherwise link them so we can provide it on the event page
[19:20] <balloons> so say July 15th instead?
[19:20] <elfy> ok - that's fine with me :)
[19:23] <balloons> elopio, I have a surprise for you
[19:24] <balloons> but first a question, do you have a tag for bugs for the toolkit helper that need completed>/
[19:24] <elopio> balloons: no, I don't
[19:24] <elopio> generally I tag them 'elopio'
[19:25] <balloons> elopio, hmm.. need something that tags all of them, so I can get a list of bugs affecting only the AP helper
[19:25] <elopio> balloons: feel free to make up one.
[19:25] <balloons> elopio, the reason is the same as the surprise. We're going to make fixing the toolkit helper bugs part of the hackfest ;-)
[19:26] <elopio> woohoo.
[19:26] <elopio> balloons: when is that?
[19:26] <balloons> elopio, I'll go through and try and tag everything with autopilot-helper
[19:26] <balloons> elopio, it's what elfy and I were just talking about
[19:26] <balloons> he'll be focusing on the manual side of things, while I'm hoping to con you into helping out on the automated side
[19:26] <balloons> does July 15th from 1900-2200 UTC work for you?
[19:27] <elopio> balloons: sure, I'll be there.
[19:28] <elopio> balloons: https://docs.google.com/a/canonical.com/document/d/1cpLCK3DMfos9A4hiS-EHuP5pJmHVBnZwmQu-0uLTLus/edit#
[19:29] <balloons> sounds great. Any meta-bugs for the tests that happen to still exist I figure we could tackle then as well.. Like replacing custom code with a helper, or removing OSK useage, stuff like that
[19:29] <elopio> not all of them have bugs reported, but almost all of them are mentioned on that documetn.
[19:29] <balloons> I'd like to host several of these.. looks like we have plenty of content to do :-)
[19:35] <wxl> stgraber: soooo we can announce now officially?
[19:35] <wxl> ahhh hahah thanks :)
[19:38] <elfy> thanks ianorlin
[19:38] <elfy> I'll try and get to that over the next day or so balloons
[19:50] <balloons> elfy, elopio here's the event page: https://wiki.ubuntu.com/QATeam/Hackfest/20140715. I'll send the mail to the list
[19:51] <elopio> thanks
[19:52] <elfy> thanks balloons
[19:53] <elfy> balloons: at some point can we have a look at the manual bugs together - with regard to what you'd like to see worked on - then I'll tag things and change the wiki page to suit
[19:54] <elfy> would perhaps be useful to have that conversation with stgraber before that
[19:57] <balloons> elfy, yea, we'll just nab a tag or tags we want to target for the event. I'd be happy to review with you. With stgraber, might be best to send a mail
[19:58] <elfy> ok
[19:59] <elfy> I just hate seeing those bugs sitting there :p
[20:02] <elfy> balloons: I've added the manual testcase check script where appropriate on the wikis
[20:13] <elopio> balloons: do you know somebody from the calendar that could help with:
[20:13] <elopio> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1334833
[20:17] <balloons> elopio, hmm.. no one right at the moment. you missed the meeting that was this morning :-)
[20:18] <elopio> balloons: ok, I'll work it around because I don't understand the code.
[20:18] <balloons> elopio, I can ask kunal to have a look, but he's asleep atm I'm sure
[20:18] <balloons> elopio, is it a toolkit bug or calendar?
[20:19] <elopio> balloons: don't know.
[20:19] <elopio> I guess calendar.
[20:25] <balloons> elopio, I'll take a look.. at least confirm things for you
[20:45] <balloons> elopio, I don't see what you are seeing in https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1334833
[20:46] <balloons> the timeline components I see correspond to the 3 visible days
[20:47] <balloons> do you have a failing test, or what is driving this?
[20:47] <balloons> ohh wait; ok I do see the duplicate eventbubble now
[20:47]  * balloons invesitgates
[20:47] <elopio> it's not the timeline components the ones that get duplicated, it's the events.
[20:48] <balloons> elopio, yes sorry I see it now
[20:48] <elopio> balloons: don't worry, it's a long path to find them.
[20:48] <balloons> and indeed, the first is duplicated
[20:49] <elopio> balloons: I think this might be affecting the delete too
[20:49] <elopio> because some of the events I delete remain on the screen.
[20:49] <elopio> I have it solved for my test, so I'm going to have lunch.
[20:50] <balloons> elopio, k.. I confirmed and will chase the dev on
[20:50] <elopio> thanks
[20:53] <balloons> I made 4 events, I have 10 objects
[20:54] <balloons> seems to be pretty straightforward duplication


[07:07] <BreakPoint> hi all
[07:31] <helpmeeeee-plz> hey, i really need some help about installing ubuntu 6.06
[07:31] <helpmeeeee-plz> can anybody help me?


[06:03] <bduk1> More almal
[06:08] <Kilos> hi bduk1 and others
[06:08] <Kilos> hi ThatGraemeGuy
[06:09] <ThatGraemeGuy> mornings
[06:29] <theblazehen> Hi Kilos ThatGraemeGuy
[06:29] <Kilos> hi theblazehen
[06:30] <theblazehen> Kilos: since you a DIY guy you may like this idea:
[06:30] <theblazehen> http://imgur.com/a/CGEY7
[06:30] <Kilos> lemme see
[06:30] <Kilos> hahaha
[06:33] <Kilos> one doesnt do much solder anymore nowadays, not much you can change on motherboards anymore with modern pc boards
[06:33] <theblazehen> I fixed PC :)
[06:33] <theblazehen> Ya
[06:33] <Kilos> soldering
[06:33] <Kilos> what did you find?
[06:33] <theblazehen> I think of got a bit hot or something
[06:33] <theblazehen> I turned it on this morning and it worked
[06:34] <Kilos> maybe a good spring clean
[06:34] <Kilos> check where air comes out and look for dust
[06:34] <theblazehen> Ya
[06:34] <theblazehen> I'm just leaving case off for now
[06:35] <theblazehen> Case was hot yesterday...
[06:35] <Kilos> ah
[06:35] <Kilos> that other okey had that prob
[06:35] <Kilos> um
[06:35] <Kilos> the one in ceres
[06:36] <theblazehen> Ah. Don't remember him
[06:36] <Kilos> golynx
[06:37] <theblazehen> Ah
[06:41] <Kilos> was a major job with him
[06:41] <Kilos> he wanted ubuntu because windows over heated the lappy\
[06:42] <Kilos> sent him a dvd and ubuntu made it worse
[06:42] <Kilos> hehe
[06:53] <nuvolari> o/ oh hi
[06:53] <nuvolari> morning oom Kilos, theblazehen
[06:53] <theblazehen> Hi nuvolari
[06:53] <theblazehen> Ah yeah, I remember
[06:55] <Kilos> lo nuvolari
[06:55] <Kilos> gaanit seun?
[06:58]  * superfly lurks
[07:00] <theblazehen> Hi superfly
[07:00] <superfly> hi theblazehen
[07:00]  * superfly is installing KDE 5
[07:01] <superfly> although, they've made KDE much more modular, so now you don't have "KDE 5" you have "Frameworks 5 plus Plasma 5"
[07:01] <theblazehen> superfly: looks real good with the breeze dark theme, but too buggy for me
[07:01] <theblazehen> Yeah
[07:01] <superfly> theblazehen: haven't tried it in a while
[07:01] <theblazehen> I tried it a month or so ago
[07:01] <theblazehen> Back to awesome for me
[07:01] <theblazehen> And hopefully to i3 soon
[07:02] <superfly> awesome and i3 are just too nerdy for me
[07:02] <Kilos> morning superfly
[07:02] <superfly> hi Kilos
[07:21]  * superfly logs out to try KDE 5
[07:21] <Kilos> sjoe
[07:45] <ThatGraemeGuy> I considered awesome and i3 but it turns out I'm too lazy to be bothered :-D
[07:47] <Kilos> lol
[07:47] <Kilos> old age catching up
[07:51] <superfly> not bad, not bad
[07:51] <superfly> needs some tweaking, but not unusable
[08:04] <Kilos> lol
[08:45] <charl> good morning
[08:45] <charl> Maaz: coffee on
[08:45]  * Maaz flips the salt-timer
[08:45] <charl> hi Kilos, superfly, theblazehen
[08:45] <Kilos> hi charl
[08:46] <charl> hi Kilos
[08:46] <charl> how are you this morning
[08:46] <charl> last werk day of the week, tomorrow holiday!
[08:47] <Kilos> good ty, cant have cyber coffee and ricoffy they will resonate in my inners
[08:47] <Kilos> how are you
[08:47] <charl> good good
[08:47] <Kilos> is good good better than good
[08:47] <Kilos> hehe
[08:48] <charl> yes :)
[08:48] <charl> especially because it is friday
[08:49] <Maaz> Coffee's ready for charl!
[08:49] <charl> Maaz: danke
[08:49] <Maaz> Bitteschön
[08:49] <charl> sehr gut, sehr gut
[08:50] <charl> ich mag diese kaffee
[08:58] <Kilos> lol
[09:00] <nuvolari> Maaz: coffee on
[09:00]  * Maaz starts grinding coffee
[09:00] <nuvolari> \o/
[09:01] <Kilos> lol
[09:01] <Kilos> ok ok Maaz coffee please
[09:01] <Kilos> ai!
[09:01] <Kilos> Maaz: coffee please
[09:01] <Maaz> Kilos: Sure
[09:03] <Kilos> dont geek type jobs calm down around this time like everything else
[09:03] <Kilos> except dairy farming of course
[09:04] <Maaz> Coffee's ready for nuvolari and Kilos!
[09:04] <Kilos> Maaz: dankie man
[09:04] <Maaz> Groot plesier my vriend
[09:08] <Kilos> haha i beat them
[09:08] <Kilos> http://businesstech.co.za/news/general/76322/sa-life-expectancy-declines/
[09:11] <Kilos> the big boss said i could have 3 score and ten, plus some for good behaviour
[09:19] <nuvolari> thank you Maaz
[09:19] <nuvolari> Maaz: thank you
[09:19] <Maaz> nuvolari: Okay :-)
[09:20] <nuvolari> oom Kilos, no, it doesn't calm down, and then some companies wants to attempt Friday-before-everyone-is-on-leave-launches
[09:20] <Kilos> eish
[09:20] <nuvolari> in the online world, that's a horror-story
[09:21] <Kilos> looks like they all crazy
[09:21] <Kilos> only we are the sane ones
[09:21] <inetpro> story of my life
[09:21] <inetpro> good mornings
[09:21] <Kilos> hi there inetpro
[09:23] <inetpro> the only way too calm things down is to shut down
[09:29] <Kilos> yourself?
[09:29] <Kilos> or the equipment
[09:36] <Squirm> morning people
[09:37] <Kilos> hi Squirm
[10:30] <theblazehen> Hi charl
[10:31] <theblazehen> Hi Squirm
[10:31] <Squirm> going to find some lunch
[11:20] <ThatGraemeGuy> byeee
[11:21] <ThatGraemeGuy> time for burgers and beer
[11:21] <ThatGraemeGuy> not in that order
[13:01] <inetpro> Kilos: the equipment
[13:01] <Kilos> hmm...
[13:01] <inetpro> unfortunately in this modern world of ours, that is not going to happen
[13:01] <Kilos> oh ya
[13:20] <Squirm> Kilos: we're flat out
[13:21] <Squirm> Working 10-12 hours
[13:21] <Kilos> eish Squirm
[13:21] <Squirm> Not really in IT though, just shipping our stock
[13:21] <Squirm> for Christmas
[13:21] <Kilos> oh ya
[13:22] <Squirm> we finish 2pm on Wednesday and back at work on Saturday(Though I have the day off)
[13:22] <Kilos> sjoe
[13:23] <Kilos> even the dairy farmer milks morning and evening but5 the has rest of day off
[13:23] <Kilos> only the cows wont allow a day off
[13:59] <Kilos> hmm... banana sandwich be lekker
[14:36] <inetpro> wb theblazehen
[14:41] <theblazehen> ty inetpro
[14:41] <theblazehen> was rebooting the bouncer
[14:42] <charl> banana and peanut butter milkshake
[14:42] <charl> that stuff is criminal
[14:42] <charl> i make it a couple of times every week
[14:42] <charl> use peanut butter and other nut butters with no additives
[14:43] <charl> Kilos ^^
[14:43] <inetpro> charl: how do you make it?
[14:43] <Kilos> lol
[14:43] <charl> inetpro: i just put peanut butter (etc) together with various bananas and some tap water in the blender and blend it
[14:43] <charl> really simple :)
[14:44] <charl> if you like milk you can add that too, but i don't
[14:44] <Kilos> milkshake must have milf
[14:44] <Kilos> milk
[14:44] <charl> milf... no i think not :P
[14:44] <charl> milk yes
[14:44] <Kilos> flavours are your choice
[14:44] <charl> smoothie is a better name
[14:44] <charl> not milkshake
[14:44] <Kilos> hehe you getting cheeky again
[14:44] <charl> :D
[14:45] <Kilos> ive never had a smothie
[14:45] <Kilos> but many milkshakes
[14:45]  * inetpro wonders about the taste
[14:45] <Kilos> favourite is raspberry
[14:45] <charl> banana and blueberry is also very nice
[14:45] <charl> we buy blueberries here imported from south africa
[14:45] <inetpro> should actually try it, but rather with milk not with water
[14:46] <charl> do it inetpro ! it's really nice but don't use peanut butter with salt in otherwise the taste can becoe overpowering
[14:46] <charl> unless you like that of course
[14:46] <Kilos> just blend banana in milk and taste inetpro
[14:46] <Kilos> then add other stuff and tatse all the time
[14:47] <inetpro> banana in milk I know, but with peanut butter!? Hmm...
[14:47] <inetpro> don't know
[14:47] <Kilos> when i starts tasting not lekker you are either full or you added something not lekker
[14:47] <Kilos> it
[14:47] <inetpro> unfortunately no bananas and no unsalted peanut butter in available at the moment
[14:47] <Kilos> peanut butter be lekker stuff man
[14:48] <Kilos> hehe
[14:49]  * inetpro shall try it asap
[14:49] <charl> inetpro: if you can buy unsalted grilled peanuts it is easy to make your own in a food processor
[14:50] <inetpro> oh, so you take even crunchy peanuts as well?
[14:50] <charl> yes just chop them up really finely
[14:50] <inetpro> interesting
[14:50] <charl> it becomes almost like peanut butter
[14:50] <charl> when it turns buttery you just scoop it out and straight onto bread or into the blender
[14:51] <charl> but for good result they will need to be at least lightly grilled
[14:51] <charl> if they are raw you can also do stuff with it but it's a bit different
[14:51] <charl> the taste is different i mean
[14:51] <inetpro> and with a bit of honey, sounds lovely
[14:52] <charl> yes ! honey and peanut butter go really well together
[14:52] <charl> but with bananas too it becomes too sweet for me
[14:52] <charl> depends on personal taste of course, and on how ripe the bananas are
[14:52] <Kilos> only prob is peanut butter doesnt last as long once family tastes how lekker it can be
[14:52] <charl> true Kilos :D
[14:53] <Kilos> haha
[14:53] <charl> problem with most commercial peanut butters are that they contain hydrogenated fats, additives, sugar and salt
[14:53] <Kilos> its something for single peeps methinks
[14:53] <Kilos> that dont matter man
[14:54] <charl> it's like margarine - it's essentially plastic
[14:54] <Kilos> lol
[14:54] <charl> they use the same process to make plastic (hydrogenation)
[14:55] <charl> turning a liquid into a solid by modifying the chemical structure so the molecules stick together
[14:56] <charl> well i mean they stick together in any case, but not in fixed form i mean
[14:56] <theblazehen> Finally my organic chemistry stuff is coming in handy...
[14:56] <Kilos> hahaha
[15:00] <Kilos> inetpro: try tropica peach from supermarkets
[15:00] <Kilos> blenned fruit milk drink
[15:00] <Kilos> blended
[15:00] <Kilos> very lekker
[15:04]  * inetpro hates how the price of fruit juices in the shops has gone berserk
[15:05] <inetpro> even coca-cola is cheaper than fruit juice these days
[15:10] <Kilos> yeah
[16:04]  * theblazehen is starting to like i3
[16:12] <Kilos> lol
[16:14]  * theblazehen is liking i3 with awesome keybinds
[16:14] <Kilos> human beings are funny animals, they get accustomed to anything sooner or later
[16:14] <Kilos> screenshot?
[16:16] <theblazehen> screenshit: http://imgur.com/5gjb0Ok
[16:16] <theblazehen> shot* -_-
[16:17] <theblazehen> basically the default config
[16:20] <Kilos> ai! you peeps and your funny stuff
[16:23] <theblazehen> haha, it's fun
[16:23] <theblazehen> And upgrades only a few KB for it :)
[16:25] <Kilos> but so ugly and hards to use
[16:26] <Kilos> look at this
[16:26] <Kilos> http://picpaste.com/pretty-qjF9fd4r.png
[16:26] <Kilos> see top panel on left
[16:26] <Squirm> Home time
[16:26] <Squirm> finally
[16:27] <Kilos> workspace switcher
[16:27] <Squirm> been here since 7
[16:27] <theblazehen> hard to use? Me and charl (IIRC) would disagree.
[16:27] <theblazehen> hi Squirm
[16:27] <Kilos> go safe Squirm
[16:27] <Squirm> and yesterday was 7-19h30
[16:27] <theblazehen> but ya, looks nice
[16:27] <Squirm> Well - Sushi time
[16:27] <Kilos> 10 workspaces
[16:27] <Kilos> you choose on by clicking on it
[16:28] <Kilos> so certain well used things like email pidgin and konversation ahd opera etc have their own workspace
[16:28] <theblazehen> 10 here too :)
[16:29] <Kilos> not as well organized man
[16:29] <Kilos> you need good eyes to run that
[16:29] <theblazehen> heh, I like it
[16:30] <Kilos> well enjoy
[16:30] <Kilos> charl likes it too ya
[16:30] <Kilos> im sure i heard today its too nerdy
[16:31] <Kilos> took me a lifetime to get a bit geeky. cant live long enough to become nerdy too
[17:03] <Kilos> Maaz: seen bushteck
[17:03] <Maaz> Kilos: I don't know who bushteck is
[17:03] <Kilos> hmm...
[17:04] <Kilos> Maaz: seen bushtec
[17:04] <Maaz> Kilos: I don't know who bushtec is
[17:04] <Kilos> oi!
[17:04] <Kilos> Maaz: seen bushtech
[17:04] <Maaz> Kilos: bushtech was last seen 27 days, 4 hours, 4 minutes and 57 seconds ago in #ubuntu-za on freenode [2014-11-22 04:59:30 PST], and has been offline on freenode since 2014-11-22 21:07:02 PST
[17:04] <Kilos> whew
[17:22] <theblazehen> Kilos: you got some nice rain now?
[17:25] <Kilos> nothing
[17:27] <theblazehen> Ai. Lots in pta now
[17:27] <Kilos> wow
[17:28] <theblazehen> Maybe you get lucky still
[17:31] <Kilos> ya we hope so
[17:43] <Kilos> hi deegee  hows davey doing
[17:43] <Kilos> drussel died
[18:18] <captine> evening all
[18:19] <inetpro> hello captine
[18:23] <Kilos> hi captine
[18:23]  * Kilos watching some skifi thing
[18:23] <Kilos> agents of sheild
[18:25] <captine> Kilos, sounds like fun
[18:25] <Kilos> yeah lekker series
[18:27]  * theblazehen is watching the dictator (again)
[18:27] <Kilos> lol
[18:29] <superfly> everyone in my company waltzed off to the local bar for drinks at 3:30 this afternoon
[18:29] <superfly> not much work happening here
[18:29] <superfly> inetpro: did you see my README?
[18:29] <charl> nice i3 setup theblazehen
[18:30] <charl> i have been using it for 18 months now
[18:30] <theblazehen> charl: ty :) Basically the default still
[18:30] <charl> and have never looked back
[18:30] <charl> mine is totally default too :P
[18:30] <theblazehen> lemme see if I have a scrot of my awesomeWM still, unless you remember how it looks? I wanna theme it to look similar if it's possible..
[18:31] <charl> on ubuntu i just install the i3 package and then add exec --no-startup-id xsetroot -solid "#000000" to the i3 config
[18:31] <charl> oh and i have bindsym $mod+p exec "i3lock -c 000000"
[18:31] <charl> the rest i leave as is
[18:31] <theblazehen> ah, I use $mod+p for dmenu, like in awesome
[18:31] <theblazehen> I use $mod+{Left,Right} for next/previous workspace
[18:32] <charl> i might add a few extra key bindings for some stuff i use regularly but i try to keep it to a minimum
[18:32] <theblazehen> yeah
[18:32] <theblazehen> I have might map my power keys on keyboard to something
[18:33] <theblazehen> I wonder if it's possible to map something to last used workspace?
[18:33] <inetpro> superfly: you changed again?
[18:34] <inetpro> ok, see no further updates... yes that README is cool
[18:35] <inetpro> now we just need to go full circle
[18:35] <Kilos> theblazehen: you supposed to be fixing ibid not watching dictator again
[18:36] <inetpro> superfly: now what would be the recommended way for me to contribute to this, do I start my own branch or do I just have upload rights to the same repo?
[18:36] <theblazehen> Kilos: I'm also installing a ROM on my phone..
[18:36] <theblazehen> inetpro: ibid?
[18:36] <inetpro> theblazehen: no, the new site
[18:36] <theblazehen> inetpro: ah, kk
[18:36] <Kilos> ai! ek sukkel darem
[18:36] <inetpro> we're doing it as if it's a development project
[18:37] <Kilos> how do i see what you doing inetpro ?
[18:37] <inetpro> nice to learn the devlopment cycle
[18:38] <Kilos> make it nice and fast
[18:38] <Kilos> no bloat
[18:38] <inetpro> theblazehen: https://launchpad.net/~ubuntu-za/+junk/ubuntuza-site
[18:38] <theblazehen> inetpro: ty
[18:39] <superfly> inetpro: you already have a branch, it's on your computer
[18:40] <superfly> inetpro: make a change, build it, see that it works.
[18:40] <Kilos> julle slim ne
[18:40] <superfly> inetpro: bzr commit -m "Made a really cool about us page"
[18:41] <inetpro> superfly: sure, but do I push back to your branch?
[18:41] <superfly> inetpro: no... there are a few ways of going about this
[18:42] <inetpro> see, that's what I thought as well
[18:42] <superfly> you can push up to your own remote branch (bzr push lp:~inetpro/+junk/ubuntuza-site) and then propose a merge into the main branch
[18:42] <Kilos> my browser logs in there np
[18:42] <Kilos> must i still get the ssh key
[18:43] <superfly> inetpro: or you can make sure you have the latest code merged into your branch, and then just push directly up to the main branch
[18:43] <superfly> if we have enough people, we could make the site an official project
[18:44] <Kilos> how many is enough
[18:44] <inetpro> that is what I was thinking... could be a nice simple way to introduce the development cycle to newcomers
[18:44] <superfly> OK, I'll set that up then
[18:45] <inetpro> may be best if the main branch is read only for most peeps
[18:45] <superfly> kk, will do
[18:46] <inetpro> superfly: but only if it makes practical sense, not sure whether it's worth it
[18:46] <inetpro> don't want to waste your precious time
[18:46] <superfly> inetpro: well, I can make it a project, which will make things easier in the long run
[18:47] <superfly> and we can sort out the access control later
[18:47] <inetpro> cool
[18:51] <inetpro> some nice examples of distributed workflows: http://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows
[18:51] <superfly> inetpro: license?  Apache Licence, GNU Affero GPL v3, GNU LGPL v2.1, Simplified BSD Licence, GNU GPL v2, GNU LGPL v3, Creative Commons - No Rights Reserved, GNU GPL v3, MIT / X / Expat Licence
[18:52] <inetpro> oh goodness
[18:54] <inetpro> hmm... either, GPL v2, or v3, or Creative Commons... or what do you think?
[18:55] <superfly> I'm tending to lean towards BSD and MIT style licenses these days
[18:55] <inetpro> why?
[18:56] <captine> i have been trying to get GIT to be used for our Cognos Budgetting tools rules.  thanks for that link...
[18:57] <superfly> by the way, a nice comparison of git and bzr merging: http://toykeeper.net/tutorials/bzr-vs-git/
[18:57] <inetpro> captine: you're welcome
[18:58] <superfly> inetpro: freer
[18:58] <superfly> the GPL is actually not that free
[18:59] <inetpro> obviously we still prefer bzr but git has really become pervasive these day
[18:59] <superfly> inetpro, captine: http://doc.bazaar.canonical.com/bzr.2.6/en/user-guide/bazaar_workflows.html
[18:59] <superfly> inetpro: mostly due to github.
[19:00] <inetpro> superfly: BSD or MIT is fine by me as well
[19:01] <inetpro> thanks for the links superfly
[19:07] <Kilos> so lekker to see you two active here agin
[19:08] <inetpro> Kilos: don't just sit there, you need to follow and take part also
[19:08] <inetpro> we're in this together
[19:08] <Kilos> i was at the page
[19:08] <inetpro> have you installed bzr yet?
[19:09] <Kilos> nope
[19:09] <inetpro> ai!
[19:09] <Kilos> from repos
[19:09] <inetpro> and nikola?
[19:09] <superfly> inetpro: I think Kilos needs some money for data first...
[19:09] <inetpro> yes from repos
[19:09] <Kilos> i have the wrong nikola
[19:09] <inetpro> superfly: oops, ok
[19:09] <Kilos> the fly was gonna write down the how to'\
[19:10] <theblazehen> superfly: you see that new python compiler?
[19:10] <superfly> theblazehen: which one?
[19:10] <Kilos> how much data will it use?
[19:10] <superfly> Kilos: http://doc.bazaar.canonical.com/bzr.2.6/en/user-guide/bazaar_workflows.html
[19:10] <theblazehen> superfly: http://nuitka.net/pages/overview.html
[19:10] <superfly> Kilos: it depends on what you have installed, but probably about 300 megs
[19:11] <Kilos> lemme check vouchers
[19:11] <superfly> inetpro: I'll be honest, I prefer http://doc.bazaar.canonical.com/bzr.2.6/en/user-guide/bazaar_workflows.html#decentralized-with-human-gatekeeper
[19:12] <inetpro> superfly: yes, that is what we need indeed
[19:13] <inetpro> somebody has to make sure that all is fine
[19:13] <theblazehen> Yes! i3 config perfect! keybinds anyway
[19:14] <Kilos> ok i have airtime and still 700m data
[19:15] <theblazehen> Kilos: nice
[19:15] <Kilos> i will need to go the route the pro went last night
[19:15] <Kilos> i also got the repo nikola
[19:15] <Kilos> and some of those funny files
[19:16] <inetpro> install bzr from repo
[19:17] <inetpro> sudo aptitude install bzr
[19:17] <Kilos> done
[19:17] <Kilos> quite a few dependancies too
[19:18] <inetpro> introduce yourself to bzr
[19:18] <Kilos> lol
[19:18] <inetpro> bzr whoami 'Joe Doe<EMAIL_ADDRESS>[19:20] <Kilos> so is my new nick Joe Doe?
[19:20] <inetpro> ai!
[19:20] <Kilos> rofl
[19:20] <Kilos> got you
[19:21] <Kilos> whew that was a lekker laugh\
[19:21] <inetpro> Then show or set your Launchpad user ID
[19:21] <inetpro> bzr launchpad-login [NAME]
[19:21] <Kilos> first name or full name
[19:21] <inetpro> if you login to launchpad as bob then it would be
[19:21] <inetpro> bzr launchpad-login bob
[19:22] <Kilos> ai!
[19:22] <Kilos> you mean that ~msdomdonner
[19:22] <superfly> yes, but without the ~
[19:22] <Kilos> ok
[19:23] <Kilos> ai!
[19:23] <Kilos> bzr: ERROR: The user name [msdomdonner] is not registered on Launchpad.
[19:26] <Kilos> must it have the @gmail.com bit in?
[19:27] <inetpro> Kilos: hang on, you need to do the ssh-keygen thing if you haven't done that, I think
[19:27] <inetpro> do you have a file ~/.ssh/id_rsa.pub ?
[19:28] <inetpro> ls -l ~/.ssh/*.pub
[19:28] <inetpro> Kilos: ^^
[19:28] <Kilos> ls: cannot access /home/miles/.ssh/*.pub: No such file or directory
[19:28] <inetpro> ok
[19:28] <inetpro> ssh-keygen -t rsa
[19:29] <inetpro> When prompted, press Enter to accept the default file name for your key
[19:29] <inetpro> Next, enter then confirm a password to protect your SSH key. Your key pair is stored in ~/.ssh/ as id_rsa.pub (public key) and id_rsa (private key)
[19:29] <inetpro> I think most people just press ENTER without a password
[19:30] <inetpro> Now you need to upload the public portion of your SSH key to Launchpad
[19:30] <Kilos> funny thing came there
[19:31] <Kilos> RSA 2048 and stuff under it
[19:31] <Kilos> tell how to do that inetpro
[19:32] <inetpro> that's all perfect
[19:32] <theblazehen> Question: Am I the only one here who battles to understand elliptic curve diffie hellman?
[19:32] <Kilos> how do i upload the public portion
[19:33] <Kilos> and what is the public portion
[19:33] <Kilos> starts with a long fingerprint
[19:33] <Kilos> then prompt
[19:34] <Kilos> oh that thing is a random art image
[19:36] <inetpro> Kilos: go to https://launchpad.net/~msdomdonner/+editsshkeys
[19:36] <superfly> Kilos: there'll be a ~/.ssh/id_rsa.pub file. You need to open that in gedit, and then copy the contents and paste it on Launchpad
[19:37] <Kilos> no gedit is nano good?
[19:37] <inetpro> cat is good as well
[19:37] <Kilos> or kate
[19:37] <inetpro> cat ~/.ssh/id_rsa.pub
[19:38] <inetpro> highlight, copy and paste
[19:38] <superfly> Kilos: oh, you on KDE?
[19:38] <superfly> Kate is AWESOME
[19:38]  * superfly loves Kate
[19:38] <superfly> she's so pretty
[19:39] <Kilos> ya but sec i gotta reset password
[19:40] <inetpro> superfly: don't let your wife see that
[19:40] <superfly> inetpro: the wife knows about all of my girlfriends, don't you worry
[19:40] <Kilos> Invalid OpenID transaction
[19:41] <Kilos> why it tells me that when i reset password
[19:41] <inetpro> ai!
[19:41] <inetpro> Kilos: don't you member your password?
[19:42] <Kilos> but here it shows me as logged in
[19:42] <Kilos> https://login.ubuntu.com/+bad-token
[19:42] <Kilos> nope not sure anymore
[19:42] <superfly> Kilos: go to launchpad.net and see if you're logged in there
[19:43] <inetpro> Ubuntu One died long ago
[19:43] <Kilos> it went there https://launchpad.net/~stefanor
[19:43] <Kilos> but ill try login from there
[19:44] <inetpro> uh
[19:44] <inetpro> he's spying on the weed?
[19:47] <Kilos> lol i was looking ibid stuff man 2 weeks ago
[19:47] <Kilos> now i reset password so will try again
[19:49] <inetpro> :-)
[19:49] <inetpro> superfly: anything I can do yet?
[19:49] <Kilos> do i paste that funny image there now
[19:49] <superfly> inetpro: bzr pull lp:ubuntu-za --remember
[19:49] <inetpro> Kilos: no
[19:50] <Kilos> key fingerprint?
[19:50] <inetpro> the contents of the file ~/.ssh/id_rsa.pu
[19:50] <Kilos> ai!
[19:50] <inetpro> b
[19:51] <inetpro> that one long line
[19:51] <inetpro> looks like three lines on my screen
[19:51] <superfly> https://launchpad.net/ubuntu-za
[19:51] <Kilos> mine has 10
[19:52] <inetpro> starts with ssh-rsa
[19:54] <inetpro> superfly: No revisions or tags to pull.
[19:54] <superfly> I have a DSA key, so mine starts with "ssh-dss ..."
[19:54] <superfly> inetpro: perfect
[19:58] <Kilos> must i now add an ssh key  to https://launchpad.net/~msdomdonner/+editsshkeys
[19:58] <inetpro> Kilos: I can see your new key
[19:59] <Kilos> yay
[19:59] <inetpro> now check the cli again
[19:59] <Kilos> nothing changed
[19:59] <inetpro> bzr launchpad-login
[19:59] <inetpro> bzr launchpad-login msdomdonner
[20:00] <Kilos> it did something and went back to prompt
[20:01] <inetpro> bzr launchpad-login
[20:01] <inetpro> it should now return with your login name if you don't specify it
[20:01] <Kilos> ya showed msdomdonner this time
[20:01] <inetpro> cool
[20:02] <inetpro> now go create a new folder to start bzr projects from
[20:02] <inetpro> mkdir Projects
[20:03] <inetpro> or ~/projects
[20:03] <inetpro> or ~/bzr
[20:03] <Kilos> first one done
[20:03] <inetpro> then cd ~/projects
[20:04] <inetpro> now pull this new website project
[20:04] <inetpro> bzr pull lp:ubuntu-za --remember
[20:04] <Kilos> you mustnt change fro P to p in Projects
[20:04] <inetpro> sorry
[20:04] <Kilos> you will be
[20:05] <Kilos> ill have a heart attack
[20:05] <inetpro> doing it to confuse you on purpose
[20:05] <Kilos> ai!
[20:05] <inetpro> :-)
[20:05] <Kilos> who needs friends
[20:05] <Kilos> bzr: ERROR: Not a branch: "/home/miles/Projects/".
[20:07] <Kilos> im in miles@P64:~/Projects$
[20:07] <inetpro> superfly: what's that first pull command?
[20:08] <superfly> Kilos: in Projects, "mkdir UbuntuZA"
[20:08] <superfly> Kilos: then, "cd UbuntuZA"
[20:08] <superfly> Kilos: then "bzr branch lp:ubuntu-za"
[20:08] <inetpro> ahh
[20:10] <Kilos> done
[20:10] <superfly> inetpro: you should actually do a checkout
[20:11] <Kilos> inetpro: dont go ahh write all this down
[20:11] <superfly> Kilos: http://bazaar.launchpad.net/~ubuntu-za-dev/ubuntu-za/website/view/head:/README.rst
[20:11] <inetpro> Kilos: see ^^ it's all there
[20:12] <Kilos> lol
[20:13] <inetpro> superfly: now please explain the checkout for me so I can understand where you're going with this
[20:13] <Kilos> ok must i first cd out again before all the installs and updates
[20:13] <superfly> Kilos: now you must cd into that directory that bzr created
[20:14] <superfly> inetpro: "branch" creates an isolated local branch. "checkout" creates a local branch connected to the remote branch, so that when you do a commit locally, it is automatically pushed up to the remote branch.
[20:14] <Kilos> miles@P64:~/Projects/UbuntuZA$ //
[20:15] <Kilos> im on 14.04 remember
[20:15] <inetpro> Kilos: that was written for 14.04
[20:16] <Kilos> so which is the directory bzr created
[20:16] <Kilos> is that where i am now
[20:16] <inetpro> Kilos: ls -l
[20:17] <inetpro> superfly: but then why let kilos run branch?
[20:17] <Kilos> drwxrwxr-x 9 miles miles 4096 Dec 19 22:10 ubuntu-za
[20:17] <Kilos> that?
[20:17] <inetpro> yes
[20:18] <inetpro> superfly: I'm trying to go slow together with Kilos again as if starting afresh
[20:18] <Kilos> cd /ubuntu-za
[20:18] <Kilos> is that the command or must i add the ~
[20:18] <superfly> inetpro: because he's not part of the core team, it's just you and i for the moment
[20:18] <inetpro> ahh
[20:19] <superfly> Kilos: cd ubuntu-za
[20:19] <superfly> Kilos: there's no such directory as /ubuntu-za
[20:19] <Kilos> bash: cd: /ubuntu-za: No such file or directory
[20:19] <Kilos> hehe
[20:19] <superfly> gee, isn't that what I just said?
[20:20] <Kilos> ya i was copy/pasting
[20:20] <Kilos> you too fast
[20:20] <Kilos> miles@P64:~/Projects/UbuntuZA/ubuntu-za$
[20:20] <Kilos> whew getting long now
[20:23] <superfly> Kilos: now follow the instructions for 14.04
[20:24] <Kilos> i am superfly done second install
[20:27] <inetpro> superfly: I made a simple change as proof of concept
[20:29] <Kilos> ln: failed to create symbolic link ‘/path/to/ubuntuza-site/nikola’: No such file or directory
[20:29] <inetpro> simply did a commit and it was automagically pushed
[20:29] <superfly> inetpro: that's OK for now, but please don't do that in future
[20:29] <superfly> let's use the workflow
[20:29] <inetpro> ok
[20:29] <superfly> Kilos: ai
[20:30] <Kilos> why did it do that after running ln -s /path/to/venv/bin/nikola /path/to/ubuntuza-site/nikola
[20:30] <Kilos> ive done all the installs and commands up to there
[20:32] <inetpro> Kilos: when someone writes /path/to/somefile you have to start adding one plus one
[20:32] <Kilos> ai!
[20:33] <inetpro> some little bit of attention and thinking is still required
[20:33] <Kilos> so path to will be /home/miles right
[20:34] <Kilos> dunno what somefile must be
[20:35] <inetpro> venv/bin/nikola
[20:35]  * inetpro lagging
[20:35] <inetpro> lemme try rebooting my router
[20:38] <Kilos> hmm...
[20:38]  * inetpro is back
[20:38] <Kilos> wb
[20:38] <Kilos> just in time
[20:38] <inetpro> why?
[20:38] <superfly> inetpro: bzr up
[20:38] <Kilos> whats the rest of that command now
[20:39] <Kilos> ln -s /home/miles/venv/bin/nikola /
[20:39] <superfly> Kilos: I don't know, you did all the work
[20:39] <Kilos> ai!
[20:40] <Kilos> sjoe
[20:40] <Kilos> ok this is the command from the readme
[20:40] <inetpro> Kilos: you are in the folder ~/Projects ?
[20:40] <Kilos> ln -s /path/to/venv/bin/nikola /path/to/ubuntuza-site/nikola
[20:41] <Kilos> ya
[20:41] <Kilos> so that now becomes
[20:41] <inetpro> instructions say "You may want to create a symlink for ease-of-use"
[20:41] <inetpro> not completely necessary
[20:41] <Kilos>  ln -s /home/miles/venv/bin/nikola /path/to/ubuntuza-site/nikola
[20:42] <Kilos> where is that site
[20:42] <Kilos> also here?
[20:42] <inetpro> cd UbuntuZA/ubuntu-za
[20:42] <superfly> Kilos: where is your "venv" directory?
[20:43] <Kilos> who knows
[20:43] <superfly> Kilos: only you do, you made it
[20:43] <Kilos> oh that ls -l
[20:43] <inetpro> ../../venv/bin/nikola build
[20:43] <superfly> Kilos: it's on your computer, find it
[20:43] <inetpro> :-)
[20:44] <Kilos> the ubuntu-site is here now?
[20:45] <Kilos> ai!
[20:45] <inetpro> and then if the above was successful, which it should do:
[20:45] <inetpro> ../../venv/bin/nikola serve
[20:47] <inetpro> ai!
[20:48] <Kilos> it shows
[20:48] <Kilos> [2014-12-19T20:46:57Z] INFO: serve: Serving HTTP on <IP_ADDRESS> port 8000...
[20:48] <Kilos> and standing there
[20:49] <inetpro> uh
[20:49] <inetpro> Kilos: see http://<IP_ADDRESS>:8000/ in your browser
[20:50] <Kilos> thats the hello world page
[20:53] <Kilos> now i ended up at http://ubuntu-za.org
[20:55] <inetpro> Kilos: now that is as simple as it get's
[20:55] <inetpro> gets
[20:55] <Kilos> oh
[20:57] <Kilos> ok so then ive done what needs to be done to get there
[20:57] <inetpro> now we have slowed down the fly in his effort to start building this new site of ours
[20:57] <inetpro> but hopefully if we can all help out and contribute together we can speed up to get a final product asap
[20:57] <Kilos> but whats with the cli stuff
[20:57] <Kilos> what do you want me to do
[20:57] <Kilos> i should just be a name there
[20:58] <inetpro> look at the files inside that folder and read the nikola handbook
[20:58] <inetpro> it's actually very very simple
[20:58] <inetpro> see http://getnikola.com/handbook.html
[20:58] <Kilos> i think i got that yesterday
[21:00] <Kilos> the site is already generated right?
[21:01] <Kilos> or must i make one here too
[21:04] <Kilos> and what is this pip thing, like apt-get?
[21:05] <inetpro> man pip
[21:06] <Kilos> lol
[21:06] <inetpro> ai!
[21:06] <inetpro> man can tell you more than I will ever know about it
[21:06] <superfly> Kilos: pip is like apt-get for Python modules
[21:07] <Kilos> ty superfly
[21:12] <Kilos> i only used about 50m data
[21:12] <Kilos> so all good
[21:13] <Kilos> ty for the help inetpro and superfly
[21:13] <inetpro> you are welcome, good night Kilos
[21:13]  * inetpro also tired now
[21:14] <Kilos> oh that konsole is watching where i go with the browser
[21:14] <Kilos> night inetpro superfly
[21:14] <Kilos> sleep tight
[21:14] <inetpro> Kilos: yep, just press Ctrl+C to cancel that
[21:14] <Kilos> ty
[21:14] <Kilos> why is it doing that if i may ask
[21:15] <Kilos> what do the 2 do together
[21:15] <Kilos> as in cli and browser
[21:15] <inetpro> Kilos: you have yourself a simple and small little web server right there
[21:15] <Kilos> similar to ibid and irc?
[21:16] <Kilos> so do you do all the work on the site from cli?
[21:16] <inetpro> and when superfly or any other contributor for that matter has gone and updated pages etc... all you do is pull from the bzr project again and you can test again
[21:16] <Kilos> ai!
[21:17] <superfly> ibid is an IRC bot
[21:17] <Kilos> i dont need to test him man, he knows what he is doing
[21:17] <inetpro> ai!
[21:17] <Kilos> i mean it runs from cli and then joins the channels
[21:18] <inetpro> Nikola  is  a  tool  to  create  static websites and blogs
[21:19] <superfly> Kilos: that's about as close as to "similar" as you are going to get
[21:19] <Kilos> haha
[21:19] <superfly> "they both run from the command line"
[21:19] <Kilos> ya
[21:19] <superfly> Kilos: use Kate to edit the pages. the pages are stored in "stories"
[21:19] <superfly> actually, maybe I should change that.
[21:20] <Kilos> when im awake you can explain what the cli part does
[21:20] <Kilos> i dont see stories anywhere
[21:21] <inetpro> Kilos: look at the files in the folders with dolphin
[21:22] <Kilos> is that thing running in virtual here
[21:23] <Kilos> ah i see stories when i ls
[21:23] <inetpro> virtualenv is just for python to run different versions
[21:24] <inetpro> virtualenv creates virtual Python executables, each of which can have its own set of installed modules
[21:24] <Kilos> slim ding ne
[21:24] <Kilos> ek gaan dooi nou
[21:24] <Kilos> lekker slaap
[21:24] <charl> have a good one Kilos
[21:24] <inetpro> good night
[21:24] <Kilos> ty charl you too
[21:24] <charl> thanks :)
[21:24]  * inetpro going to crash also
[21:25] <charl> same here
[21:25] <charl> good night all
[21:25] <Kilos> if you okes break my kde im gonna cry


[09:14] <frankban> morning gmb
[09:14] <gmb> Hi frankban
[11:52]  * gmb -> lunch
[12:58] <frankban> gmb: thanks for the review
[13:01] <gmb> np
[13:08] <gary_poster> benji frankban gmb call in 2
[13:09] <gmb> ack
[14:17] <benji> gary_poster: I'm about to send this to the -tech list: https://pastebin.canonical.com/61706/; feedback?
[14:21] <benji> gmb and frankban: have you used the terminal broadcasting hack?  If so (or not, even), do you have any feedback on my future message to the tech list (https://pastebin.canonical.com/61706/) or on the wiki page describing the hack (https://dev.launchpad.net/yellow/RemoteTerminalBroadcasting)?
[14:22] <frankban> benji: not used, taking a look
[14:25]  * gmb neither
[14:25]  * gmb looking
[14:28] <gmb> benji, Both look good to me. Looking forward to having something to try this with properly :)
[14:36] <gary_poster> benji, sorry, didn't see notification. looking.  Also, I'm looking at testrepository to see feasibility of adding a -v
[14:36] <gary_poster> more important is to help you if that is valuable
[14:36] <gary_poster> lemme know
[14:36] <benji> gary_poster: the slave just started so I'm looking at it now; I'll know more in a few minutes
[14:38] <gary_poster> benji, pastebin looks good.  one possible change: terminal size doesn't need to match.  viewer terminal must be same size or bigger.  Maybe what you said is simpler for an email.  I think it is more nuanced on the web page itself
[14:39] <benji> gary_poster: I changed it on the wiki; I /think/ that under some circumstances being exactly the same size is important
[14:39] <gary_poster> huh, ok
[14:50] <frankban> benji: maybe I am missing something, but, in the first scenario, if 2 users have ssh access to a machine, isn't it easier to just use tmux with a shared socket?
[14:50] <benji> frankban: it may; how do you do that?
[14:56] <gary_poster> whee
[14:56] <gary_poster> benji, am back post-crash-and-update if you were looking for me
[14:57] <benji> gary_poster: I wasn't ;)
[14:57] <gary_poster> :-) k
[15:01] <frankban> benji: http://readystate4.com/2011/01/02/sharing-remote-terminal-session-between-two-users-with-tmux/
[15:01] <benji> frankban: thanks!  I'll take a look.
[15:01] <gmb> Every day's a school day on the Launchpad Yellow Squad :)
[15:02] <benji> frankban: that's a little different than what we're doing here, in one good way and one bad way.  Good: both users can control the session.  Bad: both users have to be able to SSH into the host box, which is often an issue (either of security or hassle)
[15:02] <gary_poster> heh :-)
[15:03] <gary_poster> but that's your first case though, yeah?
[15:03] <gary_poster> the heh was to school day comment
[15:03] <gary_poster> the first case comment was an aside to benji's reply to frankban
[15:03] <benji> gary_poster: nope; using the tmux (or screen) approach means that we'd have to *work* on chinstrap, not just use it as a shared conduit
[15:03] <gary_poster> :-)
[15:04] <gary_poster> ah!
[15:06] <frankban> benji: ah, I see
[15:07] <gary_poster> benji, I'd expect a lot of comments of the sort "why don't you just use X".  Positioning the tool maybe should come first (i.e., why not screen, why not tmux, and so on).  Just a thought
[15:08] <benji> gary_poster: good point; by "positioning" do you mean describing it relative to the other solutions?  I tried to do that vs. hangouts, but I only glanced at screen/tmux.
[15:09] <benji> gary_poster: oh, that is what you meant (if only I could read)
[15:09] <gary_poster> Maybe "I was interested in finding a screen-equivalent that didn't do X; a tmux-equivalent that didn't do Y; a hangout/skype screen sharing that allowed Z; and a tool that was easy to set up and use.  Unix to the rescue."
[15:14] <benji> gary_poster: I like that, but I already wrote it another way and I'm lazy ;) https://pastebin.canonical.com/61714/
[15:14] <benji> gary_poster: the bit starting at "We've tried using screen" is new.
[15:21] <gary_poster> benji, second sentence needs editing (probably just delete "The one drawback is" and capitalize "That."  Reading more...
[15:22] <gary_poster> I mean
[15:22] <gary_poster> delete "that" too
[15:22] <gary_poster> and capitalize "sharing"
[15:23] <gary_poster> benji, "lessoned" -> "lessened"
[15:23] <benji> gary_poster: good catch, I wanted to use a contrasting word, so I deleted "The one drawback is that" and added "Unfortunately, "
[15:23]  * benji fixes spelling.
[15:24] <gary_poster> I would mention talking about tmux and...what's that canonical thing in the same space that has an asian name meaning foldable temporary wall...
[15:24] <gary_poster> in the same area as screen
[15:25] <gary_poster> since AIUI the arguments are the same
[15:25] <benji> b... something
[15:26] <gary_poster> gmb, do you remember the name of that canonical I-am-not-tmux thing?  juju uses it too; looking there
[15:26] <benji> byobu
[15:26] <gary_poster> that's it
[15:26] <gary_poster> sorry gmb nm :-)
[15:26] <gary_poster> otherwise looks good benji
[15:27] <gary_poster> gmb, I know you have gone down this maze of twisty passages before: following code path through subunit + testtools + testrepository = think about doing something else instead :-)
[15:31] <gmb> gary_poster, benji: Sorry, was getting a cup of tea. Can I assume that I can just raise an eyebrow at this conversation and move on, or is there still a question dangling...?
[15:32] <gary_poster> gmb, you can move on, but the very last comment was directly addressed to you and had nothing to do with the foregoing...and is not particularly important
[15:32] <gmb> Oh, er. Right.
[15:33] <benji> heh
[15:33] <gmb> gary_poster, And yes, it's a knotty and horrible place to be.
[15:33] <gary_poster> :-)
[15:33] <gmb> Oftentimes the only way to navigate out of it is to ask one of {lifeless,jml} for a map.
[15:33] <gary_poster> ah
[15:33] <gary_poster> ok
[15:34] <gmb> lifeless, of course, is like the guy at a crossroads who gives you really long-winded directions and then, when he's finished, goes back and corrects himself on one of the more esoteric but fundamentally important things that you've already forgotten he said.
[15:34] <gary_poster> lol, yes
[15:34] <gary_poster> well described
[15:34] <gmb> Note that I may be jaded about asking him for questions when I'm not capable of physically stopping him.
[15:34] <gmb> s/questions/answers/
[15:34] <gary_poster> heh
[15:35]  * gary_poster goes to branch subunit...
[15:36] <gmb> Best of luck. We'll let your children know you love them if you don't come back.
[15:36] <gary_poster> lol thank you
[15:36] <benji> lol
[15:36] <benji> gary_poster: email to -tech away
[15:36] <gary_poster> cool benji
[15:37] <benji> gary_poster: the tests are very quietly running at http://ec2-107-21-150-52.compute-1.amazonaws.com:8010/builders/lucid_lp/builds/0/steps/shell_8/logs/stdio while I work on the tracking issue report
[15:37] <gary_poster> cool benji.  yeah, no errors so far...
[16:05] <benji> gary_poster: that's an interesting exception coming from the stdlib tempfile module: http://ec2-107-21-150-52.compute-1.amazonaws.com:8010/builders/lucid_lp/builds/0/steps/shell_8/logs/stdio
[16:05] <gary_poster> benji, smells like another overlayfs error on the face of it, yeah?
[16:06] <benji> gary_poster: yep, that's what I was thinking
[16:09] <benji> gary_poster: tracking issue report: https://pastebin.canonical.com/61724/
[16:09] <benji> let me know if there is something else you'd like on it
[16:24] <gary_poster> benji, for the test failure, also looks like pub_config.htaccessroot was not made, and that's the problem that led to the traceback, so we can't simply expect to run "tempfile.mkstemp" to trigger the problem.  tracking issue: excellent thanks.  I have the RT info, as you'd guess.
[16:25] <benji> gary_poster: re. failure: hmmm; re. report: cool
[16:52] <frankban> gary_poster (or someone else): the MP for shell toolbox is ready: https://code.launchpad.net/~frankban/python-shell-toolbox/helpers/+merge/96180
[16:53] <frankban> ... and I am sorry for the long diff
[17:07] <gary_poster> frankban, interesting, so you opted to put run later down in the file to keep things alphabetized?
[17:07] <frankban> gary_poster: yes, i've reordered functions inside the module
[17:07] <gary_poster> cool
[17:32] <gmb>  gary_poster, Er, I *think* I just uploaded a new version of charm-tools to my PPA... If this works I can push it to the yellow PPA, too...
[17:34] <gary_poster> gmb, cool.  Do you want me to check something or other?  Uh, and charm-tools...oh, so you mean, this includes the new binary of python-charm-tools or whatever it is?
[17:35] <gmb> gary_poster, Well, AIUI, all we actually needed to do was and a python charm helpers package, which bac already did. My job was to package it up for us to use, which I think I just acheived.
[17:36] <gmb> ... after spending some time fighting build deps on precise, which was fun.
[17:37] <gary_poster> gmb, right I forgot bac had gotten pretty far on that
[17:38] <gmb> gary_poster, The good news is that once you're system's not being a dork, bzr builddeb is mind-blowingly excellent.
[17:38] <gary_poster> so, yeah, gmb, I think we ought to put it in yellow, and then propose it to clint
[17:38] <gmb> I must remember to by jamesw a beer.
[17:38] <gary_poster> :-)
[17:38] <gmb> gary_poster, Okay, let me make sure it's uploaded to mine first... it's in the ether somewhere at the moment.
[17:38] <gmb> (i.e. dput says "yay", Launchpad says "No")
[17:38] <gary_poster> ack
[17:45] <gary_poster> frankban, approved with comments https://code.launchpad.net/~frankban/python-shell-toolbox/helpers/+merge/96180
[17:45] <frankban> thank you gary_poster
[17:46] <gary_poster> thank you!
[17:48] <gary_poster> benji, sabdfl is following you :-)
[17:53] <gmb> Argh, silly man. Trying to upload a binary to a PPA. Nevergunnahappen.
[17:53]  * gmb rebuilds with -S
[17:54] <gmb> \0/ accepted.
[17:55] <gmb> gary_poster, I've copied the package to the Yellow PPA.
[17:56] <benji> gary_poster: heh, it seems so
[17:56] <gary_poster> gmb, yay!  So...if we need to do this again, is the knowledge on bac's page, or in your brain, or some combination?
[17:56] <gmb> gary_poster, I'm going to update bac's page.
[17:56] <gary_poster> awesome, thanks gmb
[17:57] <gmb> how do you strikethrough an entire wiki page again? ;)
[17:59] <gmb> Ah, although builddeb mightn't help us with the no-such-package-exists-yet case, actually.
[18:02] <gary_poster> gmb, are you going to have the MP for the change to charm tools today?  If so, I'd love to have a URL
[18:02] <gary_poster> If not, np, but I won't wait for it.
[18:02] <gmb> gary_poster, I will, yes.
[18:03] <gary_poster> great, thank you.  Lemme know and I will include it in our review response to ~charmers
[18:06] <gary_poster> benji, we have changes for the master and slave charm, right?  If you can make MPs for them, that would be good to get them landed before I ask the ~charmers to approve our charm.
[18:06] <gary_poster> Or ask me to make MPs, pointing me to the branches
[18:06] <benji> gary_poster: I can do MPs momentarily.
[18:06] <gary_poster> thank you
[18:10] <gmb> gary_poster, https://code.launchpad.net/~gmb/charm-tools/add-charm-helpers/+merge/96204
[18:10] <gary_poster> thank you gmb, great
[18:11] <gmb> np.
[18:11]  * gmb -> dinner, but will check back later w.r.t build status of the package, etc.
[18:11] <gary_poster> gmb, could you quickly remove "7	+# NOTE TO LAUNCHPAD DEVELOPERS: This is a bootstrapping file from the
[18:11] <gary_poster> 8	+# setuptools project.  It is imported by our setup.py."
[18:11] <gary_poster> :-)
[18:12] <gary_poster> well, do it later
[18:12] <gary_poster> :-)
[18:14] <gary_poster> benji, do you recall details as to why we rejected the idea of combining the master and slave charm into one?  My memory is that we felt that overlap was not significant, and that the idea of flexibly becoming the master or the slave did not jibe with our need to have a time-consuming preparation of slaves, and...there was something else about how a charm decided to be the mysql master or slave that didn't make s
[18:14] <gary_poster> ense for us.  Any other recollections from you?
[18:15] <benji> gary_poster: the "no overlap at all" but was the biggest, but also our desire to do as little dynamic setup as possible was another.  With the two-in-one approach everything would have been dynamic
[18:16] <gary_poster> right, thanks benji
[18:46] <benji> gary_poster: it turns out that all of my changes to the slave have already been landed or superseeded, so the trunk is good to go as-is
[18:46] <gary_poster> benji, even to args?
[18:46] <benji> gary_poster: as for setuplxc: I might have been a little light on this MP, but I think the diff is small enough for me to get away with it: https://code.launchpad.net/~benji/launchpad/more-integration/+merge/96211
[18:46] <gary_poster> benji, I saw it; will be happy to get to it very soon
[18:46] <benji> gary_poster: surprisingly, yes; I think frankban must have done it
[18:47] <gary_poster> ah ok...there were two changes to args...one was ssh key
[18:47] <gary_poster> what was the other
[18:48] <benji> gary_poster: user (-u buildbot)
[18:48] <benji> maybe I accidentally pushed to the slave trunk and that's how those got there... I don't know (being able to commit to the trunk isnt' good if we want to do reviews)
[18:49] <gary_poster> :-)
[18:49] <gary_poster> ok thanks benji
[18:49] <gary_poster> was there anything for the master?
[18:50] <gary_poster> I thought there was
[18:50]  * gary_poster checks notes
[18:50] <benji> nope
[18:50] <gary_poster> No
[18:50] <gary_poster> Right ok
[18:50] <gary_poster> I'll go look at setuplxc
[18:50] <gary_poster> btw benji, thoughts on https://docs.google.com/a/canonical.com/document/d/1UuW2T7Vhmp4zqa5Rz31TErg46EnO936Yehddp8p10AY/edit welcome
[18:51] <benji> gary_poster: I've already corrected a typo and am almost done reading it
[18:51] <gary_poster> Cool thank you :-)
[18:52] <benji> gary_poster: bikeshed: "DONE?" sounds weak, I'd say either "DONE" or remove it alltoghether so it's just "BLOCKED ON..."
[18:53] <benji> gary_poster: looks good
[18:54] <gary_poster> benji fair enough, changed.  The deployment plan might actually be done; not sure if we need more approval than Robert.  Since I don't know that, I guess it is not done either way :-)
[18:54] <benji> :)
[18:58]  * benji works on bash completion for juju for a few more minutes before delving back into the tests-on-slave issues.
[18:59] <gary_poster> benji, ow: http://ec2-107-21-150-52.compute-1.amazonaws.com:8010/builders/lucid_lp/builds/0/steps/shell_8/logs/stdio
[18:59] <benji> gary_poster: yeah, I'm not sure what's going on there; I /think/ there was a timeout or other ssh failure between the host and container that caused at least a restart, but it may have caused some of that flood
[19:00] <gary_poster> huh
[19:00] <gary_poster> maybe so
[19:21] <gary_poster> benji, setuplxc approved with trivial comment
[19:21] <gary_poster> https://code.launchpad.net/~benji/launchpad/more-integration/+merge/96211
[19:36] <benji> gary_poster: I now know as much about bash completion as I do about zsh (which isn't saying much) :)
[19:36] <benji> gary_poster: if you're looking for something to pair on, I'm going to start looking at those test failures now
[19:48] <gary_poster> benji, cool.  I'll be available in 12 or so
[19:48] <benji> gary_poster: k
[20:13] <gary_poster> benji, I'm in goldenhorde, and for some reason my camera is working again.  <shrug>
[21:12] <gary_poster> benji, what we did with the sleep is in the wrong place
[21:12] <gary_poster> it needs to be on the ssh side
[21:12] <benji> gary_poster: ah! you're right
[21:13] <gary_poster> benji flacoste suggests protocol keep alive
[21:13] <gary_poster> an ssh setting
[21:14] <benji> gary_poster: that rings a bell... let me look
[21:29] <gary_poster> benji ProtocolKeepAlives 240
[21:30] <benji> gary_poster: I'm not sure that does what we want; that's more about keeping an interviening party from cutting the connection (like some firewalls do)
[21:31] <gary_poster> benji, we can move the xvfb card to landing, right?  it will be done when that branch I reviewed lands right?
[21:31] <benji> gary_poster: right, we believe xvfb is happy now
[21:31] <benji> do we have a card for "make all the tests pass"?
[21:31] <gary_poster> benji, no that's the final stage
[21:53] <benji> gary_poster: broken pipe error with ProtocolKeepAlives (actually, ServerAliveInterval which is it's real name, ProtocolKeepAlives is an alias for what was once a Debian-only feature)
[22:15] <gary_poster> benji, :-/


[02:31] <chegney> hello
[02:34] <chegney> If I were to create a linux install on a usb drive, what would be the best size for the drive?
[02:35] <wxl> 8+
[02:37] <chegney> is it possible to use the usb drive only for the os, but have a windows directory be the main portion of the file system /usr?
[02:37] <wxl> amutjomg
[02:37] <wxl> oops
[02:37] <wxl> anything is possible
[02:37] <wxl> whether or not it's easy is another question
[02:37] <chegney> another windows director for /home?
[02:41] <chegney> it would just be a matter of mounting those windows directories as drives during the install right?
[02:41] <chegney> or mount points rather
[02:41] <wxl> yeah they'd certainly need to be mounted
[02:42] <chegney> so I could have everything including /boot on the usb drive except /usr and /home on windows partion right?
[02:43] <wxl> i'm sure that /home would be trivial to do with the installer. /usr might require some manual partitioning. i've never tried
[02:43] <wxl> manual in this case may mean dropping into a terminal and doing the heavy lifting
[15:57] <chegney> I'm running lubuntu on an old mac mini from 2005
[15:57] <chegney> very usable still for simple things
[15:59] <chegney> still have 394M memory left with X and some terminal windows open
[16:00] <mpmc> Looks like I'm stuck on 16.04 until a kernel fix for r8168/9 is released.
[16:01] <chegney> is there something after 16.04?
[16:01] <chegney> I thought that was the latest
[16:02] <mpmc> chegney: the upcoming 18.04 (or 17.10 if you want).
[16:02] <chegney> Ah yeah, I forgot 17s were out
[16:02] <mpmc> 17.10 isn't worth it as 18.04 is about a month or so away.
[16:03] <chegney> I don't think anything above 16.04 runs on the old powerpc though, right?
[16:06] <mpmc> sem idéia
[16:17] <chegney> 18.04 won't have support for powerpc right?
[17:16] <chegney> is there a console player for google play music?
[17:16] <chegney> I found something called Jam on github, but can't seem to get it to install
[18:16] <JohnDoe_71Rus> chegney: you can install this kernels http://kernel.ubuntu.com/~kernel-ppa/mainline/
[18:17] <JohnDoe_71Rus> i use 14.04 with 4.15 kernel
[18:17] <wxl> chegney: https://github.com/96AA48/gmplayer
[20:24] <chegney> I need that kernel to use the gmplayer?
[20:24] <wxl> 0916 < chegney:#lubuntu> is there a console player for google play music?
[20:58] <chegney> ah, okay, thanks
[21:11] <chegney> where are the instructions to install gmplayer?
[21:14] <chegney> I try the npm command in the readme and I get Illegal instruction (core dumped)


[23:04] <charlie-tca> first accessibility installation test case is at http://testcases.qa.ubuntu.com/Install/DesktopAccessibility
[23:50] <jibel> charlie-tca, hi, good job! I made a quick review and have 2 comments (I didn't ran the test though)
[23:51] <jibel> charlie-tca, step 3. How do you select your language ? there's no screen reader at this stage.
[23:51] <jibel> charlie-tca, small typo, replace 10.04.1 by 10.04.2 which has been release this week.
[23:52] <jibel> charlie-tca, do you want to had it to the next natty iso testing ?
[23:52] <jibel> s/had/add


[02:28] <rww> ubottu: tell Cyd about enter
[02:43] <gpc> ubottu: tell Cyd about codeofconduct
[02:43] <rww> Cyd is a really fast reader.
[02:44] <gpc> I think he is reading it now
[02:44] <gpc> maybe not
[02:44] <rww> that's not what 'before' means, gpc >.>
[02:44] <gpc> I know what before means, rww 0.>
[02:45] <gpc> hehe
[02:50] <tonyyarusso> It's too bad COPPA doesn't require an apparent-age maturity test too :(
[02:51] <rww> I think we need #ubuntu-offtopic-unregged. Not because of bots, but because I think the questions would screen out some of our users.
[02:52] <tonyyarusso> I'd be fine with that.  The unregistered ones have a much higher incidence of annoyingness lately.
[02:52]  * rww files in the "bad ideas for #ubuntu-offtopic" folder
[03:14] <Flannel> rww: Should require a Myers-Briggs test in -unregged too
[03:15] <Flannel> Can't get in unless you pass
[03:15] <rww> or sort people into different rooms depending on type compatibility!
[03:31] <Flannel> That'd be fun.  Just think of how quiet #ubuntu-offtopic-ISTP would be!
[03:41] <tonyyarusso> hey, Howard Stern.  Just failed the maturity test right there.
[04:36] <gpc> ubottu: tell abhijain about nickspam
[04:36] <gpc> ha
[04:36] <gpc> thanks
[04:36] <rww> ubottu just reinforced your point ;)
[05:55] <bazhang> want me to PM?
[05:55] <tonyyarusso> sure
[05:59] <bazhang> no response so far
[05:59] <bazhang> well not in PM..
[06:02]  * tonyyarusso sigh
[06:03] <bazhang> he seemed to be deliberately provocative
[06:04] <tonyyarusso> Of course, such is the pattern lately.
[11:10] <ikonia> didn't think that screen shot was coming....the ident "snot" was familier from a few days ago
 i need to complain with some official ubuntu people
[12:29] <ikonia> lets see
[12:47] <bazhang> support questions via PM from jungli
[12:48] <ikonia> from where/what nick ?
[12:48] <ikonia> just report it to freenode as he's known and been told to stop it
[12:49] <ikonia> ahh spicemaster
[14:17] <bazhang> * [DrummerBoy38] (~bearblack@pool-72-91-149-20.tampfl.fios.verizon.net): Burt durt smurt
[14:18] <bazhang> judging by the commentary that's hoober et al
[15:19] <ikonia> looking
[15:19] <bazhang> he's abusing all and sundry
[15:20] <ikonia> sorry, didn't have it all on screen
[15:20] <bazhang> thanks. tried to PM him but he just kept escalating abuse
[15:20] <gpc> thank you
[15:26] <tonyyarusso> bazhang: the "bearblack" ident confirms your suspicions.
[15:27] <bazhang> tonyyarusso, I'd thought 'Hoober' was banned in #ubuntu , perhaps a ban evasion
[15:32] <tonyyarusso> yup
[15:43] <gpc> now he is cursing in -il
[15:43] <gpc> eternal that is
[15:43] <bazhang> I'd tried to ping an op from there
[15:44] <gpc> bazhang: <eternal> אם אין כאן כוסיות אני הולך
[15:45] <bazhang> thats not good
[15:45] <gpc> ok we need a ban on this troll
[15:45] <bazhang> topyli, you around? he's really going overboard
[15:52] <gpc> bazhang: maybe we should give him the chan list, he can dig himself deeper and get banned from all of them
[15:53] <bazhang> gpc, nah. mistake on the first one, did not know the extensive issues -il had with him
[15:53] <bazhang> uh jussi
[15:53] <bazhang> he just wants to disrupt them
[15:53] <gpc> jussi: has a plan I sense
[16:01] <bazhang> plan to let him continue abusing people in -ot?
[16:01] <bazhang> may as well contact freenode if the -ot ops can't step in
[16:02] <ikonia> ?
[16:02] <ikonia> what's up
[16:02] <bazhang> eternal continually abusing ljl and others.
[16:03] <ikonia> I thought the kick was enough of a warning
[16:03] <bazhang> longtime issue in -il apparently
[16:03] <ikonia> can't do anything with that
[18:46] <DrummerBoy38> what is the cheatcode to show my kernel? i received update through manager. i am expecting a .35 or so from a .34
[18:46] <DrummerBoy38> this was regular updates afaik.
[18:49] <DrummerBoy38> is there an autocomplete feature? intellisense or w/e
[18:49] <DrummerBoy38> i can barely recall how to list ubuntu version which lists kernel alongside
[18:57] <popey> DrummerBoy38: you probably meant to ask that in #ubuntu, not here in #ubuntu-ops
[18:57] <popey> @btlogin
[18:57] <DrummerBoy38> ubuntu-ops or at bt logic
[18:58] <DrummerBoy38> wait so ubuntu
[18:58] <DrummerBoy38> i asked there
[18:58] <popey> this is not a support channel
[18:58] <DrummerBoy38> not even kernel changes?
[18:58] <popey> it looks like ikonia banned you from #ubuntu
[18:58] <DrummerBoy38> let me check
[18:58] <DrummerBoy38> no i don't think i was
[18:59] <DrummerBoy38> last ikonia experience was through this ip address
[18:59] <DrummerBoy38> if ikonia did, then she unbanned already. i only recall being kicked as a warning of some sort
[19:00] <DrummerBoy38> today's updates included a kernel versions ending in 35 rather than 34 i see in bootloader. i didn't checked the boot loader, again but is there a command to show the kernel through the console
[19:00] <popey> again, this is not a support channel, you're better off asking elsewhere
[19:01] <DrummerBoy38> ok
[19:33] <tonyyarusso> bazhang: One -ot op is back from church now if you still need me.
[20:44]  * tonyyarusso sighs
[20:44] <tonyyarusso> Apparently putting /boot on RAID is a bad idea.
[20:46] <ikonia> depends on the type of raid
[20:47] <tonyyarusso> ikonia: md, level 1
[20:47] <ikonia> that's fine
[20:47] <ikonia> I do it all the time
[20:47] <tonyyarusso> It *sometimes* works.
[20:47] <ikonia> /dev/md0              243M   27M  205M  12% /boot
[20:47] <ikonia> never had an issue with it
[20:48] <tonyyarusso> But it will randomly decide to not boot, and I have to use an install disk to reinstall grub, and then it works again.  No idea why.
[20:48] <ikonia> /dev/md0              485M   46M  414M  10% /boot
[20:48] <tonyyarusso> I can get to "Grub loading...", but it just hangs forever.
[20:48] <ikonia> tonyyarusso: ahhh you've not learnt the lessons......
[20:48] <tonyyarusso> which lessons are those?
[20:48] <tonyyarusso> My current theory is that it does this after kernel upgrades, but I haven't looked into it much yet.
[20:49] <ikonia> grub, no matter the raid level needs to be applied to the boot sector if each disk pointing at /boot on the raw, non raid disk
[20:49] <tonyyarusso> I did that.  In fact, the Ubuntu installer installs grub to all of them by default when you use RAID for /boot.
[20:49] <ikonia> eg: the installer installs grub to sda pointing at hd0,0 you need to apply grub to sdb pointing at sdb hd1,0
[20:50] <ikonia> yes, it installs to both, but it still points to one
[20:50] <tonyyarusso> If by "it" you mean the BIOS, yes.
[20:50] <ikonia> eg sda sdb both look at hd0
[20:51] <tonyyarusso> Yes, they do that.
[20:51] <ikonia> this only works if there is a total disk failure and removal
[20:52] <tonyyarusso> Again, I *did* install grub to the boot sector of all 4 drives.  And it still periodically fails to boot, from any of the drives.  (changing the boot order in the BIOS does not fix the problem)
[20:54] <tonyyarusso> ikonia: Any other bright ideas?
[20:55] <ikonia> tonyyarusso: but when you installed it to your drives did you make it point at /boot on it's own disk, or on the master disk
[20:55] <tonyyarusso> ikonia: What do you mean by "it" and "point at"?
[20:56] <ikonia> sorry, when you install grub did you point grub at /boot on it's own disk, or at the primary boot disk
[20:57] <tonyyarusso> I still don't know what you mean.
[20:57] <ikonia> actually it's a little different with grub2 thinking about it
[20:58] <ikonia> when you install grub it needs to know where grub.conf is
[20:58] <ikonia> so grub gets pointed at the partition that contains it
[21:00] <tonyyarusso> That would be /dev/md0
[21:01] <ikonia> ok, so change that to point at the local disk
[21:01] <ikonia> (local to the disk that grub is installed on)
[21:01] <tonyyarusso> What the heck do you mean by "point at"?
[21:01] <tonyyarusso> Not to mention "that".
[21:01] <ikonia> point at -> tell grub where grub.conf is or menu.lst
[21:04] <tonyyarusso> Dude, what step / file are you talking about?  It's not remotely clear.
[21:04] <ikonia> how do you normally install grub ?
[21:08] <tonyyarusso> Well, first off from the installer.
[21:08] <tonyyarusso> Alternate CD.
[21:08] <ikonia> ok,
[21:08] <ikonia> how about if I said to you do it manually ?
[21:08] <tonyyarusso> grub-install /dev/sdb; grub-install /dev/sdc; grub-install /dev/sdd; grub-install /dev/sde
[21:09] <ikonia> ok, so you'll have to cut me a little slack on grub2 as I've not got my head fully around it's internals
[21:10] <ikonia> but with grub when you dropped to a grub shell, you had two core commands "setup" and "root", root told the grub binary that was going to be written to the MBR where to find menu.lst (and a few other files) and then setup told it which mbr to write the binary to
[21:10] <ikonia> so in that situation grub on /dev/sda would look at /dev/sda1 (/boot) for the stage files and menu.lst
[21:11] <tonyyarusso> If it helps, my entries in /boot/grub/grub.cfg include lines like " set root='(md0)' "
[21:12] <ikonia> tonyyarusso: that's fine as that's "post grub boot" references
[21:12] <ikonia> it's the bit that happens before it tries to boot anything that's key
[21:12] <tonyyarusso> And I just successfully booted after restoring with the install CD, so like I said it sometimes works, but at some point in the future it will cease working.
[21:13] <tonyyarusso> and I don't see anything in /etc/default/grub defining where /boot should be, which I assume is what I would need to change.
[21:14] <ikonia> tonyyarusso: it's not in a config file (for grub 1) it's set in the data written to the mbr
[21:14] <tonyyarusso> ikonia: No, I mean what sets what gets written to the MBR when a new kernel is installed?
[21:15] <ikonia> nothing, as that's in grub.conf, that's dynamic
[21:15] <tonyyarusso> ikonia: Because, again, it's working right now, but will stop later, without me manually touching anything grub-related.
[21:16] <ikonia> /dev/md0              485M   46M  414M  10% /boot
[21:16] <tonyyarusso> /dev/md0              457M   33M  400M   8% /boot
[21:16] <tonyyarusso> What's your point?
[21:16] <ikonia> oops, didn't mean to paste that, sorry
[21:17] <ikonia> mouse button stuck
[21:17] <tonyyarusso> ah :)
[21:19] <tonyyarusso> ikonia: So if it works right now, what could possibly change the MBR to not work later?
[21:21] <ikonia> I guess it depends on what was breaking it, the situation you referenced earlier is often caused with grub not being able to see the menu.lst/grub.conf (disk slow to spin up, missing, corrupted etc) hence why I was saying make sure grub looks at it's own disk for that info
[21:23] <tonyyarusso> ikonia: One thing I've heard is that maybe the RAID array isn't available yet when grub goes looking for it - does that sound plausible?
[21:25] <tonyyarusso> Wait, are you saying the grub on /dev/sdb should be looking for /dev/sdb1/grub/grub.cnf rather that /dev/md0/grub/grub.cnf, just ignoring the RAID entirely?
[21:25] <ikonia> tonyyarusso: yes and no, yes, you're right, it's not available as Linux hasn't booted to start it, however it won't look at md0 for the data it needs at that point, it looks at the local physical disk, hence why I'm saying grub at sda should look at sda1 for the info, and sdb look at sdb1
[21:25] <ikonia> tonyyarusso: it will never look at md0
[21:25] <tonyyarusso> oh, hrm
[21:25] <tonyyarusso> How would I know whether it's doing that or not?
[21:25] <ikonia> that's why /boot could never go on a raid0 partition
[21:26] <ikonia> as /boot wouldn't exist until boot, so menu.lst would never be available
[21:26] <ikonia> tonyyarusso: not sure how to check with grub2, not fully got my head around the internals
[21:27] <ikonia> (did I explain it ok this time, it's hard to get across on irc)
[21:27] <tonyyarusso> I think I understand what you're getting at now at least, but not how to implement it.
[21:28] <ikonia> grub1....I'm all over, grub2, not fully understood more so with the odd layout ubuntu uses it with
[21:30] <tonyyarusso> Well, I'll leave that to muddle over for a while and go deal with concrete hardware things for a while :P
[21:30] <ikonia> I'll look into it, it's time I picked it up
[21:35] <rww> ubottu: tell eXistZ|Away about away
[21:57] <DrummerBoy38> happy pro bowl night!
[22:02] <DrummerBoy38> have nice day
[23:59] <bazhang> seems to be tag teaming. identical nonsense