[20:43] <stochastic> Hi there, I'm looking into kernel stuff for the Ubuntu Studio team and was wondering what the exact patches are that go into the LowLatency Kernel.  I don't see it listed at https://wiki.ubuntu.com/Kernel/Dev/Flavours
[20:43] <zequence> stochastic: You could just ask me, since I'm the maintainer :)
[20:44] <zequence> stochastic: In the past, there was only one patch - one which made threadirqs default. But now, since linux-lowlatency is "merged" with the master branch, making threadirqs default is done with a config
[20:44] <zequence> so, no patches at all. The only diff is the config
[20:45] <zequence> stochastic: You can find the kernel sources for stable releases at https://github.com/ubuntustudio-kernel
[20:46] <zequence> stochastic: From trusty, and beyond, linux-lowlatency is maintained by the Canonical kernel team - while the ubuntustudio-kernel team still maintains the config diff
[20:47] <stochastic> Ahh, thanks zequence, I should have just checked with you. :P
[20:49] <infinity> (The config diff is 3 things)
[20:50] <infinity> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=blob;f=debian.master/config/amd64/config.flavour.lowlatency;h=23a8a6513fc580bd5364fbacdcc758ef87dc2071;hb=refs/heads/master


[19:45] <DomasoFan> hi all.
[19:46] <jticket> Hi.
[20:17] <DomasoFan> anyone knows if ubiquity is still having the crashing issues? i tried a daily from a few days ago and it crashed after selecting the language.
[20:19] <DomasoFan> well actually it doesn't crash. orca just says install inaccessible. is there a workaround currently?


[09:45] <mvo> is there something wrong with the ppa builders currently? I uploaded two packages into the ~ubuntu-foundations-team/ubuntu-core-system-image PPA and they says since ~2h that they will start building in some minutes (but don't). both amd64 and i386
[09:48] <cjwatson> mvo: That's a devirtualised PPA, so it'll build on the bare-metal build farm, not the virtualised one
[09:49] <cjwatson> I think
[09:49] <mvo> hm, ok
[09:50] <mvo> thanks, I will just try to be patient
[09:50] <cjwatson> Yeah, it is.  So it's blocked on the big pile of chromium-browser builds at the moment, essentially.
[09:50] <cjwatson> I wonder if aatxe is recoverable
[09:52] <cjwatson> It's not in Landscape for some reason, so I can't tell directly.  Let's try turning it on and seeing
[09:52] <mvo> ok, thanks
[09:53] <mvo> https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+build/6464024 does not look encouraging - build time 14h and the last few lines say  dpkg-buildpackage: error: debian/rules build gave error exit status 2
[09:53]  * mvo needs to run and will check back later
[09:56] <cjwatson> Nope, aatxe is still dead.  Oh well.
[09:56] <cjwatson> mvo: There are some other builds that should clear out more quickly.
[09:56] <cjwatson> But yeah, some of those might be busted
[09:57] <cjwatson> mvo: I'll cancel some of those
[10:01] <cjwatson> Now it's building a batch of security uploads I can't see, so no idea :)
[10:13] <mvo> cjwatson: heh :) thanks for your help!
[10:31] <cjwatson> mvo: queue looks to have cleared now
[10:31] <cjwatson> ish
[10:33] <mvo> cjwatson: yes, my packages are build now \o/
[17:20] <popey> wgrant: if you get a moment could you please https://answers.launchpad.net/launchpad/+question/255823 - as it's misleading people.
[17:28] <dobey> popey: done
[17:29] <dobey> popey: well, the project isn't deleted, but is marked inactive, which means its only visible to people with permissions to see it, i think (i can't see it in a private window in ffox anyway)
[17:29] <popey> magic, thanks dobey
[17:29] <popey> thats perfect


[20:29]  * mwhudson_ just caught sight of abentley's hair
[20:29] <abentley> mwhudson: My hair isn't that special at the moment.
[20:30] <mwhudson> abentley: i know, but it's still quite distinctive :-)
[22:45] <thumper> mwhudson, jml: meeting in the foyer of the west plaza at 1pm


[11:00] <rgl> hi
[11:01] <rgl> hi
[11:01] <rgl> is there a way to completly reset a PPA? that is, nuke everything in it, and start over? or really delete it and create again?
[11:02] <rgl> I've made some mistakes while publishing a package ... so I want to start over.
[11:02] <rgl> I known about https://answers.launchpad.net/launchpad/+faq/661 and  https://bugs.launchpad.net/launchpad/+bug/392887 but it still does not work as expected :/
[11:02] <wgrant> rgl: You can't easily delete a PPA and then reuse the name just yet.
[11:03] <wgrant> rgl: What's the problem?
[11:04] <rgl> wgrant, I've deleted https://launchpad.net/~rgl/+archive/elasticsearch and later I tried to reenable it by adding /+edit in the url. but now I have to fuzz with the url to edit it because the top right menu does not show the edit links.
[11:05] <wgrant> rgl: Ah, you can't really undelete it like that...
[11:05] <wgrant> It shouldn't have let you reenable it.
[11:05] <rgl> oh it did.
[11:06] <rgl> anyways, to "enable" it I've just checked the two checkboxes: Enabled and Publish.
[11:06] <rgl> so I really should remove then?
[11:07] <wgrant> Well. It should mostly work now. But it's not really supported yet.
[11:08] <wgrant> Does it accept uploads?
[11:08] <wgrant> I suspect it will.
[11:08] <rgl> what do you mean by "now"?
[11:08] <rgl> I didn't try
[11:08] <wgrant> "now" being after you've checked those two flags.
[11:09] <rgl> should I be afraid that it will break on the future?
[11:11] <wgrant> PPA deletion was only implemented to allow people to rename their accounts (that's not possible if you have PPAs). So it was only taken far enough to permit that; it's not really finished.
[11:12] <wgrant> I'd go ahead and use the PPA for now. We'll hopefully make all this a bit less messy soonish.
[11:12] <wgrant> All that's special about a deleted PPA is that the links are gone, basically.
[11:12] <wgrant> (once you enable it and set the publish flag again)
[11:13] <rgl> the top-right menu links?
[11:13] <wgrant> Yes.
[11:14] <rgl> humm I enabled the flags, but only the "View package details" link is there.
[11:14] <rgl> the PPA seems to accept uploads.
[11:14] <wgrant> Right, those links will stay gone for now because part of the system still thinks it's deleted. There's no way you can unset that, but the only thing that respects that partial deletion state is the "Change details" etc. links.
[11:17] <rgl> alright :)
[11:17] <rgl> another things that bother me, if I delete all packages from the PPA, it still leaves "trash" in the PPA :|
[11:17] <rgl> for example, I cannot upload the same package version again.
[11:18] <wgrant> Right. That's deliberate.
[11:18] <rgl> I mean, the same version that was supposedly deleted.
[11:18] <wgrant> apt and Launchpad will get a little confused if you use the same version twice. Why do you want to?
[11:19] <rgl> just because I made noob mistakes the first time =)
[11:19] <wgrant> It's non-trivial to permit that, and it would be an exceptional case in which version reuse was justified.
[11:19] <wgrant> What's wrong with incrementing the version?
[11:19] <rgl> so to fix them I had to add another entry in the package changelog.
[11:20] <rgl> technically, nothing wrong. but the package history now has "trash" in it.
[11:21] <rgl> humm it seems to build the package correctly now, but when I expand the package, this appears:  Note: Some binary packages for this source are not yet published in the repository.
[11:22] <rgl> oh nm. it disapeared!
[11:22] <wgrant> rgl: Give it a couple of minutes.
[11:22] <wgrant> Things are only published by a cron job that runs every 5 minutes.
[11:22] <rgl> I see. thx :)
[13:52] <web_knows> hi
[15:32] <dan4dm> hi - this build appears to have got 'stuck'. any way to cancel-and-retry? https://launchpad.net/~puredyne-team/+archive/ppa/+buildjob/2497810
[15:33] <tumbleweed> dan4dm: seems to be making progress
[15:39] <psusi> is there a launchpad.net/~psusi/+something to refer to my bazaar branches?
[15:40] <tumbleweed> code.launchpad.net/~psusi ?
[15:43] <psusi> ahh, I got it... launchpad.net/~psusi/+branch/name/of/branch... was trying to not use the code. prefix since the wiki Launchpad: link doesn't want to use it... oddly though, if you just use /+branch/, you get an OOPS
[15:45] <dan4dm> tumbleweed: oh yes you're right. thanks. (it's going much slower than other similar builds - must just be low-priority or suchlike. anyway fine.)
[15:46]  * maxb suspects that URL form is an accident of zope traversal and not an intentional feature
[17:13] <fta> https://answers.launchpad.net/launchpad/+question/152715  :(
[17:34] <mainerror> hello
[17:35] <mainerror> does anyone know when a project is considered inactive?
[17:37] <jcsackett> do you mean in the sense of when a project will be deactivated?
[17:37] <mainerror> in the sense of after what amount of time
[17:39] <jcsackett> mainerror: There isn't a distinct time limit to my knowledge.  But sinzui may be able to correct me if i am wrong.
[17:39] <sinzui> mainerror: There is no definition but...
[17:40] <sinzui> mainerror: we have discusses 365 days without karmic activity and not linked to a community.
[17:41] <sinzui> mainerror: This rule is fundementally flawed because Lp does not award karma for most project activity and we have discussed removing karma
[17:41] <mainerror> I see, so basically if someone created a project and lost interest in it, it is up to me to contact the owner and ask him to either ask for deactivation or to assign someone else as owner
[17:42] <sinzui> mainerror: yes. He cannot deactivate the project. Someone must ask for a new owner or ask for it to be removed
[17:43] <mainerror> ok thanks, both of you
[17:43] <sinzui> mainerror: if you cannot reach the owner, as a question at https://answers.launchpad.net/launchpad where an admin can help make the needed changes
[17:43] <sinzui> s/as a/ask a/
[17:44] <mainerror> got you, thanks. I have mailed the owner today, lets see if I can get the issue resolved that way
[20:33] <TheEvilPhoenix> is anyone having issues loading pages?  i'm getting timeouts :/
[20:33] <TheEvilPhoenix> esp. on answers.launchpad.net pages
[20:48] <sinzui> answers represents 80% of timeout origins now
[20:48] <sinzui> TheEvilPhoenix: We are rewriting email and answer contact listing code to address this in the next 4 weeks
[20:59] <fta> please re-open https://answers.launchpad.net/launchpad/+question/152715
[21:02] <lifeless> fta: its a bug, I'll ping the sysadmins to bounce the service
[21:03] <lifeless> fta: are you encountering that right now?
[21:05] <lifeless> fta: and what host are you loading to when this happens?
[21:07] <fta> lifeless, as i said in the question, all my dailies are impacted (ppa)
[21:07] <fta> lifeless, i've implemented a workaround in my bot, but the issue still needs to be fixed
[21:08] <lifeless> fta: of course, its a critical bug
[21:10] <fta> also, i'd appreciate if someone could have a look at bug 767258
[21:20] <geser> wgrant: do you have some time to fix the ownership of some package sets? the ones affected by bug 740892 (see also http://irclogs.ubuntu.com/2011/03/23/%23ubuntu-motu.html#t11:02)
[21:22] <lifeless> fta: we're currently fighting down a bunch of criticals
[21:22] <lifeless> fta: I suspect that that high bug will sit fallow for a bit
[21:23] <fta> lifeless, just telling which part of the stats is bogus would already be helpful
[21:28] <lifeless> fta: yes, it would
[21:28] <lifeless> fta: thats going to require some hours of analysis
[21:29] <fta> :P
[21:35] <lifeless> (which is fine, but as its a high not a critical, that analysis will come after we get through the criticals - or if it gets bumped to critical because, for instance, you detect more anomalies)
[21:50] <facundobatista> Hello!
[21:50] <facundobatista> I'm working in the bug #767466
[21:50] <facundobatista> and I have it assigned to two different projects
[21:50] <facundobatista> with "Target to series" link, I was able to target the bug to project A's trunk and stable version
[21:50] <facundobatista> but how can I do the same with project B?
[21:55] <sinzui> facundobatista: You must be a driver of that project to target to a series
[21:56] <sinzui> facundobatista: since you cannot undo a mistake when targeting to a series, you should not do it unless you are certain you will meet to goal. In general, land a fix in trunk, then target to a series to do backports
[21:56] <lifeless> facundobatista: try this url - https://bugs.launchpad.net/ubuntuone-storage-protocol/+bug/767466
[21:56] <lifeless> facundobatista: just for kicks
[21:56] <sinzui> targeting to a series is a bug. you should not be able to do it
[21:56] <facundobatista> sinzui, yes, doing that
[22:06] <facundobatista> lifeless, awesome trick, it worked flawlessly, thanks!
[22:09] <lifeless> ok, so this is a UI bug.
[22:09] <lifeless> we're not showing all series, only the current-context-series
[22:09] <lifeless> someone filed a bug about this recently I think
[22:20] <azop> Does Launchpad support virtual domain names for commercial projects?
[22:21] <beuno> azop, it doesn't, no
[22:21] <lifeless> Do you mean like $projectname.launchpad.net ?
[22:21] <lifeless> If so, no, sorry.
[22:21] <azop> lifeless: no, like improve.bluecherrydvr.com for example
[22:22] <azop> lifeless: beuno: okay thanks
[22:22] <lifeless> azop: we don
[22:22] <lifeless> bah
[22:22] <lifeless> azop: theres no reason you couldn't have a trivial config (many DNS hosts will do this for you) that redirects traffic to improve.bluecherrydvr.com -> launchpad.net/bluecherrydvr
[22:23] <azop> lifeless: yea, I could set that up
[22:23] <lifeless> azop: however, due in large part to the web framework we have, every page has an 'official' url
[22:23] <lifeless> and all the links generated go to that ur
[22:23] <lifeless> url
[22:23] <azop> lifeless: I'd just rather have it show up as improve.bluecherrydvr.com in the URL bar, instead of being redirected
[22:23] <lifeless> so it would be pretty hard for us to keep the url bar to stay on a different domain than the main lp one.
[22:23] <azop> yea
[22:24] <azop> is there a maximum attachment size for LP?
[22:24] <lifeless> yes, I think its 2GB or something
[22:24] <azop> okay
[22:24] <lifeless> we have technical limits around that at the moment - it will use a lot of memory on the appserver while it uploads
[22:24] <lifeless> downloading is fine
[22:25] <azop> are you aware of anyone who has imported issues from redmine?
[22:26] <lifeless> yeah
[22:27] <lifeless> https://answers.launchpad.net/launchpad/+question/104299 was a ticket from one such migration
[22:27] <lifeless> azop: please ignore the poor responsiveness in there - we've reorganised the team now to handle such things better.
[22:28] <TheEvilPhoenix> out of curiosity, do you know if its possible to have bug tracking point to a bugzilla setup?  or how to import bugs from bugzilla to launchpad?
[22:29] <azop> okay, I was hoping there would be some priority for a commercial launchpad account
[22:30] <lifeless> azop: certainly thats a factor - the previous issue we had was that the team doing lp bugtracker development was also the one doing the customer support, and you probably know how focused devs get
[22:30] <azop> yap
[22:30] <lifeless> azop: now we rotate between doing development and doing customer support, so there is less opportunity to get adsorbed in a problem and ignore our users.
[22:31] <azop> lifeless: I have a couple more questions if you have a moment
[22:31] <lifeless> TheEvilPhoenix: its possible in two ways - we can bidirectional sync with a bugzilla *for named bugs only*, or you can do a bulk import
[22:31] <lifeless> TheEvilPhoenix: the latter being just to migrate
[22:31] <lifeless> azop: shoot
[22:32] <azop> lifeless: We used to have a commercial account but never used it so it expired.  If we renew it, would we get access to 'Answers' for our project?
[22:32] <TheEvilPhoenix> lifeless:  "we" as in the launchpad admins?
[22:32] <TheEvilPhoenix> or "we" as in the launchpad framework?
[22:32] <lifeless> TheEvilPhoenix: the latter
[22:33] <lifeless> TheEvilPhoenix: we got https://launchpad.net/bugzilla-launchpad written initially, and its now part of bugzilla 3
[22:33] <lifeless> TheEvilPhoenix: so the two bugtrackers can chatter to each other quite happily.
[22:33] <lifeless> azop: do you mean a private answers area?
[22:33] <lifeless> azop: or do you mean 'can use answers at all' ?
[22:34] <lifeless> I don't believe we have implemented a private answers module yet. - sinzui ?
[22:34] <azop> lifeless: basically, answers.launchpad.net/bluecherry where customers can ask questions specific to our software and we can create bug reports if needed
[22:34] <lifeless> azop: certainly you can use it
[22:34] <lifeless> azop: but like I say I don't think it has privacy / disclosure features yet, which may impact its usefulness to you.
[22:35] <sinzui> We have not planned to implement private answers
[22:35] <azop> okay
[22:35] <sinzui> No stake holder has listed it as desirable given other choices. Contributors are welcome to implement it
[22:35] <azop> is the translation service open to commercial accounts also?
[22:36] <lifeless> commercial accounts can use all the feature of LP
[22:36] <azop> okay, that answers that
[22:36] <lifeless> the parts we haven't added privacy support to may not be suitable for some commercial users.
[22:36] <TheEvilPhoenix> lifeless:  anything there to support Bugzilla 4?
[22:36] <lifeless> I am sure that translations doesn't have privacy support either.
[22:37] <lifeless> TheEvilPhoenix: built in still AIUI.
[22:38] <TheEvilPhoenix> lifeless:  AIUI = As I Understand It?
[22:38] <lifeless> TheEvilPhoenix: exactly
[22:40] <TheEvilPhoenix> lifeless:  aj00200 (who just joined) maintains the bugzilla setup for a project I'm affiliated with, aj00200 also owns the project on launchpad, hence the questions about getting bugzilla and launchpad to communicate smoothly
[22:40] <TheEvilPhoenix> even though my question was out of curiosity, it led to a sort of support question :P
[22:45] <thopiekar> hi.. there seem to be something wrong with the launchpad builders.. this build-log says kdelibs5-dev is installed but cmake fails while FindNepomuk.cmake isn't available, but http://ns2.canonical.com/de/natty/i386/kdelibs5-dev/filelist says that it is part of that package..
[22:45] <thopiekar> building it on my home pc works.. https://launchpadlibrarian.net/70379053/buildlog_ubuntu-natty-amd64.plasma-mobile_0.0-1~git20110425%2Btablet-ppa0_FAILEDTOBUILD.txt.gz
[22:46] <aj00200> Is there any documentation on setting up a bugzilla-launchpad connection?
[22:47] <thopiekar> connecting a project on launchpad to bugzilla? , aj00200
[22:47] <aj00200> thopiekar: yes
[22:48] <thopiekar> check out https://bugs.launchpad.net/[your-project]/+configure-bugtracker (replace [your-project] with the name of your project)
[22:49] <aj00200> yes, I have filled that out, but bugs don't seem to sync in any way
[22:49] <thopiekar> << Bugs are tracked in: "In a registered bug tracker:" >>
[22:49] <thopiekar> hmm
[22:49] <lifeless> aj00200: theres stuff on help.launchpad.net too; basically we can federate bugs that have been explicitly registered
[22:49] <lifeless> we don't federate all bugs
[22:50] <lifeless> you need an account for LP in bugzilla *if* you want LP to push comments to bugzilla
[22:50] <thopiekar> lifeless: any idea about my problem?
[22:50] <aj00200> lifeless: ok. Is this account setup explained on help.launchpad.net?
[22:52] <lifeless> aj00200: looking
[22:53] <lifeless> thopiekar: I don't think its a builder issue
[22:53] <lifeless> thopiekar: nothing I see there looks suspicious
[22:53] <lifeless> thopiekar: perhaps a cmake path issue or something; can you build it in pbuilder/sbuilder locally?
[22:54] <TheEvilPhoenix> lifeless:  <thopiekar> building it on my home pc works.. https://launchpadlibrarian.net/70379053/buildlog_ubuntu-natty-amd64.plasma-mobile_0.0-1~git20110425%2Btablet-ppa0_FAILEDTOBUILD.txt.gz
[22:54] <lifeless> sinzui: re aj00200's question, do you know where the docs are ?
[22:54] <TheEvilPhoenix> lifeless:  RE: thopiekar's issue here
[22:54] <lifeless> TheEvilPhoenix: that doesn't say /how/
[22:54] <lifeless> TheEvilPhoenix: which is why I asked the followup question :)
[22:54] <TheEvilPhoenix> lifeless:  true...
[22:54] <TheEvilPhoenix> :P
[22:54] <thopiekar> I used dpkg-buildpackage -rfakeroot
[22:54] <sinzui> I can look
[22:55] <lifeless> thopiekar: so, you need to build it in a chroot or a vm with only build-essential + named dependencies to be sure that its not a dependency/package version issue
[22:55] <lifeless> thopiekar: pbuilder is pretty good at that
[22:55] <sinzui> aj00200: This is all that is documented https://help.launchpad.net/Bugs/BugzillaPlugin
[22:56] <aj00200> sinzui: ok, thanks. Hopefully I can get it to work with that
[22:56] <lifeless> aj00200: if it doesn't, please file a question at https://answers.launchpad.net/launchpad, and we'll get the developer that wrote the lp side to improve the docs :)
[22:56] <aj00200> ok
[22:57] <sinzui> aj00200: There are no reported against the code https://bugs.launchpad.net/bugzilla-launchpad
[22:58] <lifeless> sinzui: that code base is obsolete now, it was just for < 3.0 bugzilla instances
[22:59] <sinzui> I know. That is what we have though
[23:00] <lifeless> sinzui: I guess I mean that we should configure that project as having a remote bugtracker and point it at bugzilla.bugzilla.com or whatever the url is
[23:00] <lifeless> sinzui: and tell it where the upstream bugzilla forum etc is.
[23:00] <sinzui> Okay, except that you cannot do that latter
[23:15] <lifeless> sinzui: welcome back
[23:15] <lifeless> https://bugzilla.mozilla.org/query.cgi?resolution=---&resolution=DUPLICATE&product=Bugzilla
[23:15] <lifeless> sinzui: is the upstream location for that code now
[23:16] <lifeless> https://bugzilla.mozilla.org/buglist.cgi?resolution=---&resolution=DUPLICATE&component=WebService&product=Bugzilla
[23:16] <sinzui> I do not understand what you are saying. Is that url to a bug tracker?
[23:16] <lifeless> sinzui: its a component in the master bugzilla bugzilla instance
[23:17] <sinzui> Thanks, that is what I was looking for, a component
[23:17] <lifeless> I'm 95% sure. I will mail max-kat alexander
[23:17] <lifeless> I will cc you
[23:18] <sinzui> Well I just remember that we never implemented lp<->components
[23:18] <lifeless>  bryce has a patch :(
[23:19] <sinzui> Well bugwatches will work now
[23:19] <lifeless> mail sent
[23:28] <aj00200> I think I have it figured out. https://help.launchpad.net/Bugs/RemoteTrackerCoverage It is only possible to link bugs which already exist in launchpad which isn't really a problem for us because we don't have any bugs in launchpad. We were lookng for the bug-import feature which isn't implemented in launchpad
[23:29] <lifeless> aj00200: right, thats what I referred to by saying we don't do federation of unregistered bugs
[23:29] <lifeless> aj00200: if you want to do a migration, we can do that :)
[23:29] <TheEvilPhoenix> and again as I asked, who does the migration?
[23:29] <TheEvilPhoenix> :/
[23:29] <TheEvilPhoenix> :P
[23:30] <aj00200> Hmm, I like launchpad's bug tracker, but I like bugzilla as well. EEk, conflict
[23:30] <lifeless> TheEvilPhoenix: the project wanting to migrate generates an export in the lp format
[23:30] <TheEvilPhoenix> aj00200:  EEK lol
[23:30] <TheEvilPhoenix> lifeless:  oic
[23:30] <lifeless> TheEvilPhoenix: then the lp admins import it to staging for you, you review etc and loop till happy
[23:30] <lifeless> TheEvilPhoenix: then once happy they import it to production for you
[23:32] <TheEvilPhoenix> lifeless:  i see


[08:41] <Linuxephus> Can someone here explain how Ubottu works and what triggers it? Is it user controlled or scripted to "act" based upon keywords or situations?
[08:48] <topyli> !ubottu
[08:52] <Linuxephus> topyli: Actually, I've been at several of those links for roughly five minutes or so after a private message was initiated. Thank you nonetheless though. By the way, the one question I have remaining that documentation doesn't answer; Does an "administrator" here have the ability to create a reply through Ubottu?
[08:53] <topyli> yes. and if a non-privileged user tries to, it triggers a notification in #ubuntu-ops so that an operator may add it
[08:58] <Linuxephus> Right, I thought as much after recieving a rather unique reply from Ubottu that I as of yet couldn't find in it's average "scripting". Suffice it to say it was "just too human".
[09:01] <topyli> yes we're all fearfully awaiting the day she becomes sentient
[09:06] <Tm_T> topyli: oh, so you don't know^W^W^W^W^W
[09:06]  * Tm_T hides
[09:06] <Linuxephus> Artificial intelligence with an occasional "helping hand" from the one who administers to "here".
[09:07]  * Linuxephus hides in the opposite direction.
[09:17] <Tm_T> wonk!
[14:08]  * genii-around prepares a large pot of coffee
[14:11] <genii-around> I might end up drinking the whole thing by the time I finish reading the entirety of "New roles in the Ubuntu IRC team" ....


[01:52] <RAOF> tjaalton: If I push the mesa 17.0.7 SRU to -proposed, will you test this one? :)
[04:30] <tjaalton> RAOF: yes, I promised that to sil2100 buy he was off and never replied :)
[04:30] <tjaalton> *but
[04:30] <tjaalton> also, i guess it was you who asked about the mesa git push, sheesh
[04:31] <tjaalton> and that egl platform thing I missed
[04:31] <tjaalton> hope to see those in 17.2 ;)