[03:24] <slangasek> kees: woohoo
[05:57] <pitti> Good morning
[08:13] <dholbach> good morning
[09:04] <Laney> @pilot in
[09:04] <Laney> rawr
[09:04] <doko> shadeslayer_, no, unfortunately not
[09:06]  * dholbach hugs Laney
[09:11] <seb128> Laney, enjoy the piloting!
[09:11]  * Laney salutes
[09:12]  * xnox ponders what/where/how intel graphics are screwed up on my desktop.
[09:15] <seb128> how screwed?
[09:15] <mpt> Laney, coincidentally I have just learned what a Patch Pilot is, while wondering what to do with a patch in a bug report
[09:17] <mpt> Is there a simple how-to somewhere for turning a patch into a Bazaar branch proposed for merging? The closest I’ve found is <http://shallowsky.com/blog/linux/making-an-ubuntu-diff.html>, which is discouraging.
[09:17] <mpt> (And not entirely relevant to an upstream project.)
[09:20] <Laney> You can just subscribe ubuntu-sponsors if you like
[09:20] <Laney> It's not hard to do for someone who knows how
[09:20] <Laney> dholbach: how do I get to the packaging guide from http://developer.ubuntu.com/ ?
[09:21] <mpt> Laney, ok, I subscribed ubuntu-sopnsors to bug 965953. Thanks.
[09:21] <Laney> ta
[09:21] <dholbach> Laney, the page is currently broken and we're talking with IS to get it off of there and on to packaging.ubuntu.com so we also don't to keep the packaging guide css and the developer.u.c style in sync, etc
[09:22] <dholbach> Laney, I'll ping IS about it again
[09:22] <Laney> dholbach: oh ok
[09:23] <Laney> I googled for it and got the old wiki at number 1, then a pdf of the guide at number 2 (removing the filename from the url took me to a page about click packaging), then some other random stuff
[09:25] <dholbach> yeah, I know - something in the new wp deployment (and some links) broke
[09:26] <Laney> ah well
[09:26] <Laney> thanks for following up
[09:34] <xnox> seb128: i think it was a lockup "reboot" fixed it. but i do have a few crash files to upload.
[09:38] <cjwatson> stgraber: ltsp/ldm> not a problem, thanks
[10:06] <Laney> Mirv: want to take care of https://code.launchpad.net/~dandrader/ubuntu/trusty/qtdeclarative-opensource-src/backport_fix_qtbug_32004/+merge/195761 with your new powers ?
[10:07] <Laney> Wait, you don't have them yet
[10:08]  * Laney fixes that
[10:10] <Mirv> might do at some point, although as pointed out it's a bit slow process since I'd need to build it for armhf first and then run all AP:s
[10:12] <Mirv> it's in the 5.2 PPA builds now
[10:12] <Mirv> so if the patch needs modifications, it's good to know
[10:15] <Laney> Well, it's right near the top of the sponsorship queue now
[10:15] <Laney> So if it's good to get in then it'd be nice to help that, otherwise reject it
[10:15] <Laney> No good letting it sit there really
[10:16] <Mirv> right, makes sense. I'll raise it on my todo list.
[10:17] <Laney> ty
[10:18] <Laney> cjwatson: do you have launchpad.Edit? could you add ubuntu-qt5-dev to the qt5 packageset uploaders please?
[10:20] <cjwatson> Laney: launchpad.Edit on what object?
[10:21] <Laney> (<Archive at 0x16beb610>, 'newPackagesetUploader', 'launchpad.Edit')
[10:23] <cjwatson> Laney: nope, launchpad.Edit on the primary archive => techboard
[10:23] <cjwatson> Laney: you could ask a webop to do it though ...
[10:23] <Laney> ah, I thought ~launchpad gave you that
[10:23] <cjwatson> ~launchpad doesn't give me admin, no
[10:23] <Laney> ok
[10:23] <cjwatson> it gives some magic things but not that :)
[10:24] <cjwatson> launchpad.<PermissionName> is always contextual - depends on the object it's operating on
[10:24] <Laney> yeah, I just overestimated the power of that team
[10:30] <Laney> done
[10:30] <Laney> Mirv: you should be good to go
[10:30] <Laney> Riddell: ScottK: also kubuntu-dev can now upload qt5 stuff FYI
[10:41] <Riddell> thanks Laney
[10:43] <Mirv> thanks Laney
[10:59] <dholbach> Laney, http://packaging.ubuntu.com/ is up and running, mthaddon is putting up rewrite-rules and the landing page will be maintained in a branch (and made a bit prettier)
[11:18] <tedg> jodh, Could we have the upstart logs for stuff put a generic timestamp in for start and stop?
[11:18] <tedg> jodh, I could do it for my jobs in a pre-start type script, but it seems more generic.
[11:21] <jodh> tedg: https://bugs.launchpad.net/upstart/+bug/1154207. Not a priority for trusty, but patches welcome :)
[11:22] <jodh> tedg: oh wait, you're talking about upstarts output itself? if so, feel free to raise a bug as that's different :)
[11:23] <tedg> jodh, I was thinking a single timestamp "started at 23245345" type of thing, more than per message.
[11:23] <tedg> per message would mostly implicitly add that though.
[11:26] <xnox> tedg: what would be more interesting, is to record events in the job log which job is sensitive to "232122456 event: desktop-started SESSION_TYPE=Ubuntu" "Starting" ...... "Started"......"Stopping"....."Stopped"
[11:26] <xnox> (that way one sees lifecycle of a single job, and it's stages)
[11:29] <shadeslayer_> doko: drat :(
[11:34] <knocte> Cimi: ping
[12:39] <dobey> anyone know why the "show-hud" keybinding in dconf would keep getting reset, after i changed it?
[12:55] <Cimi> knocte, pong
[12:56] <Cimi> knocte, you ok in one hour?
[12:56] <Laney> doko: looks like pcre3 has done Bad Things
[12:56] <knocte> Cimi: in 1hr I don't think I'll be here; anyway I sent you a review-request for a merge, just try to ping me if you have any thing to discuss
[12:57] <doko> Laney, ?
[12:57] <Laney> doko: e.g. https://launchpadlibrarian.net/158171405/buildlog_ubuntu-trusty-i386.msva-perl_0.9.2-1ubuntu1_CHROOTWAIT.txt.gz
[12:57] <Laney> http://paste.ubuntu.com/6514370/
[12:58] <wgrant> Yeah
[12:58] <wgrant> Someone probably wants to delete that from -proposed :)
[12:59] <doko> wondering why ... https://launchpadlibrarian.net/158168960/buildlog_ubuntu-trusty-i386.pcre3_1%3A8.31-2ubuntu1_UPLOADING.txt.gz
[12:59] <doko> looks ok
[12:59] <Laney> blocked until someone can delete it
[12:59] <Laney> @pilot out
[12:59] <wgrant> doko: The file list at the end of that log looks pretty wrong
[13:00] <wgrant> -rw-r--r-- root/root<PHONE_NUMBER>-12-03 12:12 ./lib/i386-linux-gnu/libpcre.so.1.0.1
[13:00] <doko> ugh, soname change?
[13:01] <wgrant> doko: Heh
[13:01] <wgrant> doko: The soname is patched into configure by quilt
[13:01] <wgrant> So your dh-autoreconf will just clobber it
[13:01] <doko> wtf?
[13:01] <wgrant> Yep.
[13:02] <Laney> yeah ...
[13:02] <doko> ok removing the binaries
[13:02] <doko> and will add a symbols file to catch that
[13:03] <cjwatson> Yeah, this is why I said to check the patches :)
[13:03] <cjwatson> and why people patching only generated files should be Taught The Error Of Their Ways
[13:04] <wgrant> s/patching only generated files/including generated files in source tarballs/? :)
[13:04] <cjwatson> I'm fine with that personally
[13:04] <xnox> wgrant++
[13:04] <xnox> it's embedded copies of source, not preferred form of modification.
[13:05] <xnox> we force regenerate valac, strip out included java libraries, yet somehow configure/config.guess/config.sub are all fine =/
[13:05] <xnox> (i understand there is no licensing issues with configure/config.guess/config.sub but still)
[13:06] <cjwatson> I'm a big fan of regenerating them in the packaging, but it makes sense for upstream to include them IMO
[13:06] <xnox> quite.
[13:07] <xnox> i wish it would be RC bug if autoreconf -f -i fails for example. Because, in practice it means inability to modify sources in the preffered form.
[13:07] <doko> ok, binaries removed
[13:10] <pitti> doko: ^ that's for the broken pcre, right?
[13:10] <doko> pitti, yes
[13:10] <pitti> (causing nice havoc in jenkins)
[13:10] <pitti> doko: danke
[13:11] <doko> every day you find some worse packaging bits, it doesn't stop ...
[13:12] <mdeslaur> So, I've just rebooted saucy, and every time I start xchat from the message indicator, it comes up without global menus
[13:12] <mdeslaur> tedg: is there a race with upstart user sessions or something that could result in that? ^
[13:14] <tedg> mdeslaur, Not sure if saucy got the upstart restart patch for env vars?
[13:14] <xnox> mdeslaur: cat /proc/`pidof xchat`/environ | grep -a unity-gtk-module ?
[13:14] <xnox> mdeslaur: GTK_MODULES should have "overlay-scrollbar:unity-gtk-module"
[13:15]  * xnox is still confused why GTK_MODULES are *opt-in* instead of *opt-out*
[13:15] <mdeslaur> xnox: nope, not there
[13:15] <mdeslaur> GTK_MODULES=overlay-scrollbar
[13:15] <xnox> mdeslaur: then you will not have global menuabar.
[13:16] <mdeslaur> xnox: looks like the messaging indicator managed to start without it
[13:16] <xnox> mine starts with.
[13:16] <mdeslaur> xnox: mine starts with it 99% of the time
[13:16] <mdeslaur> xnox: once in a while, it doesn't
[13:17] <xnox> mdeslaur: I see that overlay-scrollbar is reliable added in /etc/X11/Xsession.d/.... let's check unity module
[13:17] <mdeslaur> xnox: could the indicator have started before /etc/X11/Xsession.d/81overlay-scrollbar got run?
[13:18] <xnox> no, but that script doesn't set unity-gtk-module.
[13:18] <mdeslaur> oh, duh -NEEDCOFFEE
[13:18] <xnox> so unity-gtk-module should be set in Xsession.d to be reliable and I don't see it set.
[13:19] <xnox> seb128: Laney: where is unity-gtk-module added to GTK_MODULES?
[13:21] <seb128> xnox, Xsession.d
[13:22] <seb128> hum, I though
[13:22] <xnox> $ grep unity-gtk-module -r /etc/X11/Xsession.d/ || echo fail
[13:22] <xnox> fail
[13:22] <xnox> =/
[13:22] <mdeslaur> heh
[13:22] <seb128> xnox, oh, upstart job
[13:22] <xnox> seb128: maybe there is some-wrapper or some-such side-effect.... if it's not set there, it's not guaranteed that all processes in the user session will inherit it.
[13:23] <xnox> right, i see.
[13:23] <seb128> I think ted suggested that (unsure though)
[13:24] <xnox> well it can't be because of touch right?
[13:25] <seb128> the upstart job should be reliable no?
[13:25] <seb128> what do you mean "because of touch"?
[13:25] <xnox> sure, for everything that is start on started dbus, but not before.
[13:25] <seb128> I guess people though using upstart job was a more modern way that using Xsession.d
[13:25] <mdeslaur> where are user session upstart jobs?
[13:26] <seb128> indicators shouldn't start before dbus is started...
[13:26] <xnox> mdeslaur: /usr/share/upstart/session; XDG_CONFIG_DIRS/upstart (array); XDG_CONFIG_HOME/upstart (single)
[13:26] <mdeslaur> xnox: ah! thanks
[13:26] <xnox> mdeslaur: i gave it in the order of last one wins, and overrides from the last one wins
[13:26] <xnox> mdeslaur: so you can e.g. drop an override into ~/.config/upstart/
[13:27] <mdeslaur> so...unity-gtk-module.conf may not get launched before the other jobs
[13:30] <xnox> so, it's doing "start on starting dbus" which we know is racy in saucy (fixed in trusty), as in dbus started event is emitted before dbus actually is available and therefore extra dbus gets autolaunched by indicators without enheriting the variable.
[13:31] <xnox> Laney: what's odd about the unity-gtk-module & overllay-scrollbars is that they are loaded unconditionally, regardless of the Desktop ENvironment.
[13:31] <mdeslaur> xnox: what ensures unity-gtk-module.conf gets loaded before, say, gnome-session.conf?
[13:31] <xnox> mdeslaur: when that happens, you should note that $ status dbus, doesn't match the dbus that is actually in use by the indicators.
[13:32] <brainwash> speaking of overlay scrollbars, can maybe anyone here explain why bug 1239014 happens? trace log included
[13:32] <xnox> mdeslaur: "started on dbus" in the gnome-session.conf. "started dbus" is not emitted until all tasks/jobs that are "start on starting dbus" are complete.
[13:32] <xnox> but the buggy dbus job (in saucy) means that "started dbus" is emitted before it has completed (too early).
[13:33] <xnox> mdeslaur: if you want to fix it for yourself, drop a file into XDG_CONFIG_DIRS after overlay-scrollbar, to add unity-gtk-module to the GTK_MODULES. that is guaranteed to be enherited by all processes in the user session.
[13:34] <xnox> (upstart and non-upstart managed and children of thereoff)
[13:34] <mdeslaur> xnox: ah! I see starting dbus vs started dbus
[13:34] <mdeslaur> xnox: I understand now, thanks
[13:34] <xnox> yeap =))))
[13:34] <mdeslaur> xnox: so this should be fixed in trusty?
[13:34] <xnox> yes, i believe it is.
[13:34] <mdeslaur> xnox: awesome, thanks
[13:35] <xnox> i don't find it important enough to fix in saucy =))))
[13:35] <seb128> mdeslaur, you are not running trusty?
[13:35] <mdeslaur> xnox: yeah, that's ok...I just wanted to make sure we were aware of this
[13:35] <mdeslaur> seb128: I have to wait until the desktop team stops breaking it first :)
[13:36] <mdeslaur> jk :)
[13:37] <seb128> mdeslaur, I'm going to show you what we can do :p
[13:37] <xnox> mdeslaur: well. I think it's a side-effect, of the same root cause which has been rectified.... =)
[14:03] <smoser> any one using trusty and finding 'apt-get dist-upgrade' to just be painfully slow ?
[14:04] <pitti> I find de.archive.u.c. to be painfully slow, but apt-get itself seems fine to me
[14:05] <smoser> well, this is the 'dist-upgrade' part itself which is painfully slow.
[14:05] <smoser> when it finishes, i'll pick the timestamps out of the log
[14:08] <seb128> tseliot, hey, why did you set the xrandr/optimus/g-s-d issue back to triaged on g-s-d? is g-s-d doing anything wrong? (it seems like an issue in the nvidia xrand handling)
[14:08] <tseliot> seb128: I was about to write the explanation. There's an error we should trap in libgnome-desktop
[14:08] <seb128> ok, good
[14:09] <tseliot> seb128: and I have a simple patch for that
[14:09] <tseliot> seb128: also worth SRUing
[14:09] <seb128> tseliot, sorry, just checked email after lunch and that one was in the batch ;-)
[14:09] <tseliot> :)
[14:09] <seb128> tseliot, great, it would be nice it you could upstream it as well (if it still applies to trunk)
[14:10] <tseliot> seb128: yes, things seem to have changed quite a bit but if they're still doing that, I will
[14:10] <seb128> tseliot, thanks
[14:10] <tseliot> seb128: yw
[14:11] <smoser> ugh.  there is a major lack of information here. i know that the dkms build was slow as I watched it, but for example /var/lib/dkms/virtualbox/kernel-3.12.0-5-generic-x86_64/log/make.log has only a start time
[14:11] <smoser> not a stop time.
[14:15] <Laney> xnox: I never set that stuff up
[14:15] <Laney> Xsession.d was working fine as far as I was concerned
[14:15] <xnox> ok.
[14:16] <Laney> you probably want to talk to ted
[14:28] <smoser> well, not very scientific numbers, but http://paste.ubuntu.com/6514743/
[14:29] <smoser> pitti ^. generally i do think that 'apt-get dist-upgrade' is much less performant than it was in say saucy. not sure what would have caused this, but 17 minutes for ~ 45 packages is pretty bad (even though one was kernel)
[14:32] <smoser> anyone else have non-scientific feelings that something in the path excercised by a genera 'apt-get dist-upgrade' is slower ?
[14:34] <mlankhorst> ok does anyone want to test mesa 10 before I upload it? it passed all tests I threw at it locally :P
[14:36] <xnox> smoser: is that amd64? or more specifically are there any foreign architectures defined?
[14:37] <xnox> (e.g. on amd64, by default i386 is enabled. and the only big features in trusty so far is to switch to using python:any dependency....)
[14:37] <smoser> xnox,
[14:37] <smoser> $ x=$(dpkg --print-foreign-architectures); echo "arches: $x"
[14:37] <smoser> arches:
[14:37] <xnox> horum.
[14:37] <smoser> it really feels like general IO to me.
[14:38] <xnox> very odd, indeed.
[14:38] <tseliot> seb128: so, shall I upload the quilt patch in gnome-desktop-3 in trusty and SRU the same package in precise? How do you suggest that I do it?
[14:38] <smoser> i admit to not having cutting edge hardware here.  T400 with spinning disk (2009 era thinkpad). but really...
[14:38] <seb128> tseliot, can you merge request it or put the diff up for review on the bug?
[14:40] <tseliot> seb128: a merge request using bazaar? (svn is listed in the control file)
[14:41] <seb128> tseliot, oh, we don't have a vcs ... I just want a diff/peer review
[14:41] <seb128> tseliot, can you put the debdiff on the bug?
[14:41] <tseliot> seb128: sure
[14:41] <seb128> thanks
[15:06] <spy6> cheers!
[15:07] <spy6> is there a way to request a merge for a package from debian?
[15:08] <spy6> #1244713 smells fishy and there arrived also a duplicate today
[15:09] <mlankhorst> spy6: requestsync ?
[15:09] <mlankhorst> although i guess that is a copy
[15:10] <cjwatson> xnox is touched-it-last for that package
[15:16] <spy6> mlankhorst: that is for pacakges without modifications ... nagios-plugins has ubuntu specific changes
[15:21] <tseliot> seb128: the debdiff for trusty is there now
[15:30] <seb128> tseliot, looks good to me ... could you upstream it and include the bug reference in the patch? then feel free to upload
[15:33] <tseliot> seb128: isn't this enough as a reference? http://paste.ubuntu.com/6515056/
[15:33] <tseliot> I'll try to upstream it too
[15:34] <seb128> tseliot, upstream bug reference is nice because it tells us it has been upstreamed
[15:34] <seb128> so we don't have to look for the info through logs and launchpad next time we merge
[15:34] <tseliot> seb128: oh, so you mean the upstream bug number. Ok, good
[15:35] <seb128> tseliot, right, sorry the upstreaming and bug references parts there were supposed to be one item ;-) thanks
[15:35] <tseliot> ok :)
[15:45] <mdeslaur> infinity: hrm, ruby-ffi needs some arm64 love
[15:46] <mdeslaur> infinity: I'm guessing lib/ffi/platform needs a new platform definition
[15:48] <tseliot> seb128: after a quick look I'm convinced that my patch is not upstreamable, as they moved all the RandR logic into Mutter: http://paste.ubuntu.com/6515114/
[15:49] <tseliot> seb128: and while I can try to contribute to mutter, it will be irrelevant to the bug report on launchpad
[15:49] <infinity> mdeslaur: Be my guest. :P
[15:50] <mdeslaur> infinity: ah geez, I asked nicely didn't I? :)
[15:50] <seb128> tseliot, it's still worth filling it in case they want to commit to 3.8, I think e.g the new RHEL might be based on GNOME 3.8
[15:50] <seb128> tseliot, just write that it applies for 3.8 and can be wontfixed if they don't want it there
[15:50] <tseliot> seb128: fair enough
[15:54] <mdeslaur> infinity: do I have access to a porting box somewhere?
[15:55] <infinity> mdeslaur: Sort of.
[15:56] <Laney> qemu seems to work
[16:00] <mdeslaur> infinity: oh, wait a sec...it compiled successfully before
[16:02] <mdeslaur> infinity: ignore me for now
[16:05] <mdeslaur> infinity: is DEB_HOST_ARCH still set to "arm64"?
[16:06] <mdeslaur> infinity: sorry, I mean dpkg-architecture
[16:09] <mdeslaur> infinity: ignore me again, I'm looking at the wrong issue
[16:12] <xnox> mdeslaur: $ mk-sbuild --arch arm64 trusty should actually work now. I fixed up last hurdles it was having.
[16:13] <mdeslaur> xnox: oh, cool, i'll give that try, thanks
[16:16] <xnox> rbasak: do you know if anyone can steal nagios-plugins merge away from me? i did it for a transition, but the 1.5.x is non-trivial.
[16:16] <xnox> alternatively i'll cherrypick fix for bug #1244713
[16:33] <bdmurray> seb128: a few weeks ago you'd asked about the discrepancy between bucket numbers on the landing page and on the problem page.  I have some information for you regarding that.
[16:34] <seb128> bdmurray, hey, I read your comment on "asana" (received those by email)
[16:34] <bdmurray> seb128: ah, okay then I won't repeat myself ;-)
[16:34] <seb128> bdmurray, thanks for investigating ;-)
[16:35] <bdmurray> seb128: no problem
[16:37] <tseliot> seb128: ok, the upstream report and reference are there, and I've also filed an SRU for Saucy and Precise
[16:40] <seb128> tseliot, thanks!
[16:40] <tseliot> seb128: you're welcome
[16:58] <doko> xnox, ping about demoting gccxml (split the boost python package)
[17:10] <plars> slangasek: hi, is there someone that can help us with https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1256695
[17:15] <cjwatson> plars: I was going to look at that
[17:16] <cjwatson> plars: (p.s. slangasek is on holiday)
[17:16] <plars> cjwatson: ack, thanks
[17:17] <cjwatson> plars: however, I have to fetch a current image first, so it probably won't be until tomorrow
[17:17] <jdstrand> @pilot in
[18:25] <bdmurray> seb128: you set bug 1024590 to In Progress for Saucy.  Do you plan on uploading an SRU for it?
[18:28] <seb128> bdmurray, I was discussing it with mvo this morning, he did merge it in http://bazaar.launchpad.net/~aptdaemon-developers/aptdaemon/ubuntu-trusty/revision/308
[18:28] <seb128> bdmurray, not sure if he was going to upload or if he would welcome somebody else to deal with those bits though
[18:28] <seb128> mvo, ^^?
[18:28] <seb128> sorry for the double ^, that key stopped doing what it should somewhat for me
[18:29] <bdmurray> seb128: I saw the branch, thanks for chasing that
[18:29] <seb128> yw
[18:30] <bdmurray> mvo: I can do the SRU
[18:30] <seb128> I had enough to see that topping e.u.c, just tried to come with some sort of solution, mvo was nice enough to pick it up, improve a bit and get it commited ;-)
[18:30]  * seb128 hugs mvo
[18:31]  * ogra_ hugs mvo
[18:37]  * xnox hugs mvo
[19:05] <infinity> mdeslaur: It compiled fine both times, didn't it?  It's the testsuite that fails.
[19:05] <mdeslaur> infinity: yeah, it's gem2deb that's broken, I uploaded a fix now
[19:08] <infinity> mdeslaur: Oh, shiny.
[19:09] <infinity> mdeslaur: Oh, "fixed".  I see.  Not quite as fixed as actually passing tests. :)
[19:09] <mdeslaur> infinity: oh, hehe, no :)
[19:09] <mdeslaur> infinity: it still needs love, but at least it won't be stuck in proposed :P
[19:42] <mdeslaur> infinity: oh, hehe, that last changelog was a bit misleading...I'm not the one who disabled the tests
[19:51] <vood> Hello, I have a question about myapps.developer.ubuntu.com, does somebody know, why application still apears in a Draft state even after ppa-info.txt upload ?
[19:52] <sarnold> vood: #ubuntu-app-dev might be a better place to ask
[19:52] <vood> thanks a lot!
[19:53] <mdeslaur> doko: mind if I merge ruby-mocha?
[20:16] <mdeslaur> doko: too late
[21:24] <jdstrand> @pilot out
[21:31] <chiluk> are there any pilots left?
[21:31] <chiluk> can I get some upload lovin for bug 560839 ... at this point I think it only pertinent that the fix be applied to trusty
[21:32] <chiluk> once it bakes there, I'll submit an sru for p,q,r,s
[21:34] <xnox> stgraber: in mountall, you added /sys/fs/cgroup with size=1024. Why 1024? it appears to be by default mounted with size=4k
[21:39] <infinity> chiluk: We don't need two copies of the same binary in the package, surely?
[21:39] <infinity>  	install -D -m644 memtest.bin debian/$(PACKAGE)/boot/$(PACKAGE).bin
[21:39] <infinity> +	install -D -m644 memtest debian/$(PACKAGE)/boot/$(PACKAGE).elf
[21:39] <infinity>  	install -D -m644 memtest debian/$(PACKAGE)/usr/lib/$(PACKAGE)/$(PACKAGE).elf
[21:40] <infinity> chiluk: If that second one is a well-known location we're afraid users might need a migration path for, install it as a symlink to the one you just put in /boot perhaps?
[21:41] <stgraber> xnox: well, maybe 4K is fine, I don't really care, I just wanted the smallest quota possible which will still let us create directories
[21:42] <xnox> i see.
[21:42] <xnox> ack.
[21:50] <chiluk> infinity, hmm good point.
[21:53] <chiluk> infinity ... Is there  a special way to "install a link" or would just calling ln from the rules file be sufficient.
[21:54] <xnox> chiluk: $ man dh_link ?
[21:54] <chiluk> thanks...
[21:55] <xnox> (just add "src dest" pairs in debian/$pkg.links)
[21:55] <xnox> chiluk: for added bonus it corrects the links to be policy compliant (relative/abolute as needed)
[21:56] <doko> xnox, ping about demoting gccxml (split the boost python package)
[21:58] <xnox> doko: you need it now?
[21:59] <xnox> i don't mind, it was demoted to Recommends in debian, but I guess we need it down to suggests.
[21:59] <doko> xnox, no, but please still this year
[21:59] <xnox> doko: ok.
[21:59] <doko> well, split it out, then you don't need to recommend it
[22:00] <xnox> doko: please elaborate, how are you suggesting to split it?
[22:00] <doko> xnox, move the pyste module into a separate package
[22:02] <xnox> ack.
[22:02] <xnox> doko: thanks, that will simplify a few things.
[22:10] <infinity> chiluk: As xnox says (or just do it in debian/rules with ln, given that there's variable exansion going on there)
[22:10] <infinity> chiluk: And make it an absolute link, since /boot and /usr can be different filesystems.
[22:14] <chiluk> infinity, trusty debdiff uploaded in bug..
[22:14] <chiluk> infinity how do you feel about specifying elf vs not specifying it in the menu-entry titles?
[22:15] <chiluk> I lean towards not doing so..
[22:15] <chiluk> but the original fix for this had elfs all over
[22:20] <infinity> chiluk: I don't see any reason for the GRUB entry to tell people things they don't need to know and won't understand.
[22:20] <chiluk> ok .. one sec.. I'll revert that bit as well.
[22:20] <infinity> chiluk: We don't tell people what sort of vmlinu{z,x,x.coff,etc} they're booting either.
[22:20] <chiluk> i tend to agree with you.
[22:24] <chiluk> infinity ... alright... it's all yours..
[22:29] <infinity> chiluk: Oh, if you're doing dh_link in debian/rules like that, you really should probably just use 'ln' directly, so you're not accidentally creating links in packages you didn't mean to (if it's a multi-binary package), etc.
[22:30] <infinity> chiluk: The correct way to use dh_link is with a debian/package.links file, but that would make the variable substitution bit hard, so I'd just use ln in rules with the install calls there.
[22:30] <chiluk> all I know is what I have there worked when I tested it...
[22:30] <infinity> chiluk: ie: "ln -s /boot/$(PACKAGE).elf debian/$(PACKAGE)/boot/$(PACKAGE).elf"
[22:31] <infinity> chiluk: Sure, but it could have surprising and unexpected results if there's a bit of a packagin reorg or someone adds another binary package to the source, etc.
[22:31] <chiluk> yeah that would work too
[22:31] <doko> pitti, jibel: please could you let tcl8.5 migrate? python-imaging is removed, and it's the only test failing
[22:31] <doko> infinity, or you: ^^^
[22:31] <chiluk> infinity,  so you want me to change it back to ln ?
[22:31] <infinity> chiluk: Yeah.
[22:32] <infinity> doko: You want release team for that, yeah, and I can do it.
[22:33] <infinity> doko: Done.
[22:33] <doko> thanks
[22:34] <infinity> doko: I'm confused by the python-imaging removal...
[22:34] <chiluk> alright last times a charm right?
[22:34] <infinity> doko: The comment you made was "NBS", but how can a source package be NBS? :P
[22:34] <doko> infinity, called pillow now
[22:35] <doko> hmm, maybe I should have written, removed from the archive ...
[22:35] <infinity> doko: Ahh, the binaries moved to another source, and the source had no binaries?
[22:35] <doko> yes
[22:35] <infinity> doko: Kay, cool.
[22:36] <infinity> pitti: Can you remove python-imaging tests from jenkins, or does that happen automatically (eventually) when sources are removed from the archive?
[22:42] <xnox> infinity: it has to be done manually, as typically packages drop tests by accident and that's considered a regression. Last time jibel removed it for me, I think.
[22:42] <chiluk> infinity new debdiff is attached... any more suggestions?
[22:44] <infinity> xnox: This isn't a package that dropped tests, it's a package that stopped existing.
[22:44] <infinity> xnox: But, indeed, the "dropped tests" case is what made me think maybe the "dropped package" case would be manual too.
[22:44] <xnox> infinity: i guess that's cruft, and britney will not request / consider that package anymore?
[22:45] <xnox> anyway, i don't actually know, so i should shut up.
[22:48] <infinity> chiluk: If I was nitpicking, I'd say that my "ln -s" paste probably should have been "ln -sf", so subsequent runs of the same target don't fail.  Of course, that might fail anyway if the directory wasn't yet created.  Let's see.
[22:49] <chiluk> I was going to suggest the f...
[22:49] <chiluk> apparently I have too much faith in you.
[22:49] <infinity> chiluk: I tend to talk more in pseudocode than actual copy-and-waste snippets.  I expect review and thought before application. :)
[22:49] <chiluk> hah...
[22:50] <chiluk> if you knew what i'm on you wouldn't expect much out of me at the moment... *(back surgery)
[22:50] <infinity> chiluk: Anyhow, let me apply this, look at it in context, fix if necessary, and upload.  More back and forth is probably a waste of time.
[22:50] <chiluk> agreed.
[22:50] <chiluk> the basic fix is there.
[22:51] <chiluk> but you have more experience with what I consider to be packaging issues..
[22:52] <chiluk> infinity do you want to upload for pqrs as well?
[22:52] <infinity> chiluk: Nope!
[22:52] <chiluk> just checking.
[22:52] <chiluk> I'll backport and create debdiffs
[22:52] <infinity> chiluk: But you should subscribe to bugs on the package and watch how the trusty upload fares for a month or so to see if this was a Bad Idea for any reason.
[22:52] <chiluk> and follow regular sru process
[22:52] <chiluk> will do.
[23:07] <doko> infinity, cjwatson: do you have an idea how dh-autoreconf should be called with cdbs?
[23:13] <infinity> doko: I thought cdbs had its own weird equivalent, but I'm fuzzy on that.
[23:13] <infinity> doko: seb128 or one of the GNOMEy people who use cdbs heavily might be best to ask.
[23:14] <infinity> doko: cdbs does have an autoreconf.mk, though, so I'm guessing that's the way to go.
[23:15] <tseliot> infinity: please approve bug #1255583 when you can, I'd like to upload a new nvidia-prime with the correct dependencies


[00:08] <wallyworld> katco: good evening, not that you should be still be working now, but i've commented on your PR. so you have something to look forward to when you wake up tomorrow :-)
[01:07] <axw> wallyworld: would you be satisfied if I just doc commented syncToolsAPI? i.e. say that it's a subset of state/api/Client?
[01:07] <axw> (thanks for review btw)
[01:07] <wallyworld> axw: yep, sure
[01:07] <wallyworld> just to assist the casual reader
[01:07] <axw> cool
[01:07] <axw> yup
[01:39] <davecheney> thumper: http://paste.ubuntu.com/8174218/
[01:39] <thumper> my fix at the end was very like that
[01:40] <davecheney> ok, let me see if I can make a repro out of it
[01:47] <thumper> wallyworld: that is a long email, will read it fully later, but... good effort
[01:47] <wallyworld> thumper: yeah, it is long, sorry
[01:47] <thumper> don't be sorry
[01:48] <wallyworld> i'm not, well, that's what i say to the girls
[01:48] <davecheney> wallyworld: that's a yello card mate
[01:48] <bodie_> davecheney, any word on pr 617?
[01:48] <bodie_> just when you have a minute
[01:48] <davecheney> lets keep the induendo below the audible level
[01:48] <davecheney> bodie_: i haven't looked at it
[01:48] <davecheney> i'm not the on call reviewer today
[01:49] <wallyworld> it's friday, gotta have a little fun
[01:49] <bodie_> gotcha -- can you leave a comment or something to the effect that it's cool if someone else has a look then?  I don't want this thing to get trapped in limbo
[01:49] <bodie_> I just have a bunch of stuff depending on it https://github.com/juju/juju/pull/617#discussion_r16817826
[01:50] <bodie_> just since you'd left a negative comment
[01:51] <thumper> wallyworld: I have to agree with davecheney on this...
[01:51] <wallyworld> sigh
[01:51] <thumper> sorry dude
[01:51] <bodie_> and since we're on totally different timezones, and nobody else will respond to it since you'd left a comment
[01:51] <thumper> there is a time and place, but this isn't it
[01:52] <wallyworld> thumper: it's not like you haven't been "guilty" before :-P
[01:52] <thumper> wallyworld: doesn't make it right
[01:52] <thumper> I'm happy to be called out on it
[01:53] <bigjools> I have to agree, wallyworld should be more careful
[01:54] <bigjools> I mean, if you're going to try and make someone take offence, do it properly
[01:54]  * bodie_ furiously scribbles notes
[01:54]  * wallyworld makes a mental note who has a thin skin for next time
[01:55] <davecheney> wallyworld: casual sexium isn't about having a thin skin
[01:55]  * bodie_ compares notes with wallyworld and rebases his changelist
[01:55] <wallyworld> it wasn't sexism, but anyway
[01:56] <wallyworld> define sexism: prejudice, stereotyping, or discrimination, typically against women, on the basis of sex.
[01:56] <wallyworld> anyways, let's move on
[01:57] <bodie_> well, where were we.  oh yes.  so, I've noticed that when a core member on a 12 hour offset timezone comments on something, other team members are hesitant to add their two cents to discussion, and thus my review gets trapped in the equivalent of a HTTP syn timeout on a 12 hour latency window
[01:57] <bodie_> I chatted about the PR with TheMue and alexis today and both indicated they wanted davecheney to be the one to respond to that comment on 617
[01:58] <davecheney> thumper: http://paste.ubuntu.com/8174325/
[01:58] <davecheney> repro for the gccgo bug
[01:58] <davecheney> filing an issue upstream now
[01:59] <bodie_> if someone could at least acknowledge what I'm saying, maybe I wouldn't wonder as much whether the cold shoulder has anything to do with wanting to keep us out of the loop
[01:59] <thumper> I'd say more casual sexual harassment rather than sexism... however... moving along
[02:00] <davecheney> https://code.google.com/p/go/issues/detail?id=8612
[02:00] <bodie_> or, you know, you could post a three word reply on that pr, such as "someone else take this" and it would be totally cool
[02:00] <bodie_> oops, that was 4...
[02:00] <thumper> davecheney: cool, ta
[02:01] <perrito666> cool email wallyworld, thanks for taking the time
[02:01] <wallyworld> np
[02:07] <bodie_> so I'm taking that as a "no, your PR is going to sit in limbo until I'm the next on call reviewer, and/or you're on my ignore list now"
[02:07] <perrito666> I really need to go live a few weeks to the countries where you guys are from so I get to learn local english
[02:08]  * perrito666 feels like the hispanic comic relief on an adam sandler movie half the time
[02:08] <bodie_> LMAO
[02:09] <bodie_> perrito666, you're cool by me, I never notice your accent ;)
[02:10] <perrito666> bodie_: trust me I sound terrible when speaking for long periods of time, I am really bad at managing my air and I get really exasperated when trying to speak in english at the same speed than spanish
[02:10] <davecheney> bodie_: nope, that's not it
[02:10] <davecheney> i was pulled off onto another crash this morning
[02:10] <davecheney> the OCR reviewer rotates daily to avoid anyone being on the critical path
[02:11] <bodie_> I just don't like feeling like I'm talking into thin air at timse
[02:12] <bodie_> but I understand you guys are totally slammed
[02:12] <bodie_> just frustrating trying to push our stuff through when nobody will respond to a thread because someone who's only online when it's 10pm where I live owns the review
[02:13] <bodie_> perrito666, english was invented for people who mutter under their breath :P
[02:13] <davecheney> bodie_: i think you need to raise that with alexis
[02:13] <bodie_> yeah, I did this morning
[02:13] <davecheney> bodie_: i've said the same to her in the past
[02:13] <davecheney> i'm not sure what I can do
[02:13] <bodie_> davecheney, she and TheMue both said they wanted the response on that thread to come from you
[02:14] <davecheney> nah, that can't be how it works
[02:14] <bodie_> you could just say something like "I'm content for someone else to look at this" or "bodie_, I'll be able to review it next thursday" or something other than... ya know, nothing
[02:14] <davecheney> he told me that martin is reponsible for landing your stuff
[02:14] <davecheney> so, all i know is eveyrone knows a different story
[02:14] <bodie_> TheMue has replaced martin for working with the actions team
[02:15] <bodie_> I'm just trying to make things work, man :)
[02:15] <bodie_> if we have a blocker, I need to figure out how to get around it
[02:15] <davecheney> bodie_: yup, i hear you
[02:16] <perrito666> ok, lets do this I have a decent overlap with all of you guys, mostly because I have no life and I hardly sleep, bodie_ could you privmsg me with a brief on what you need? davecheney could you tell me what alexis told you so I can try to unlock it tomorrow?
[02:16] <bodie_> maybe you could either respond to that comment, or make a mention to them in #jujuskunkworks, either of which will take no more than 20 seconds
[02:16] <bodie_> that way they won't feel like you own the thread
[02:17] <bodie_> or, I can pass it along tomorrow, or I can wait for your response when you're able
[02:17] <bodie_> I just want to know what to expect so I can be effective here
[02:23] <bodie_> lol
[02:47] <davecheney> thumper: good news
[02:47] <davecheney> upstream have a fix for the gccgo crash
[02:47] <davecheney> now comes the hard part ...
[02:47] <thumper> getting it into ubuntu?
[02:47] <davecheney> :P
[03:08] <davecheney> thumper: https://code.google.com/p/gofrontend/source/detail?r=75739d377426
[03:08] <davecheney> we have a fix
[03:08] <davecheney> what's the best way to report this ?
[03:08] <davecheney> an issue on ubuntu/gccgo ?
[03:09] <thumper> I guess
[03:09] <davecheney> right-o
[03:09] <davecheney> i'll try that
[03:10] <davecheney> might need you and sinzui to ride shotgun on this one
[03:10] <thumper> who is in charge of gccgo?
[03:10] <thumper> inside canonical?
[03:11] <davecheney> dokku maybe ?
[03:12] <davecheney> the lack of an owner probably explains why the last fix hasn't landed for 5 months
[03:32] <mwhudson> thumper, davecheney: i have some gccgo patches i want in ubuntu too
[03:32] <mwhudson> thumper, davecheney: i think the official process is "hound doko relentlessly"
[03:32] <thumper> mwhudson: I suggest we push through alexisb to pat
[03:32] <thumper> mwhudson: who does doku report to?
[03:32] <mwhudson> thumper: slangasek i think
[03:33] <mwhudson> btw, there is already a newer gccgo in trusty-proposed
[03:33] <mwhudson> have you guys tried that?
[03:34] <mwhudson> (it obviously doesn't fix this problem that just got fixed, but doko will probably ask...)
[03:34] <davecheney> mwhudson: thumper `https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1362906
[03:34] <mup> Bug #1362906:  internal compiler error: in comparison, at go/gofrontend/expressions.cc:6508 <gccgo-4.9 (Ubuntu):New> <https://launchpad.net/bugs/1362906>
[03:35] <davecheney> mwhudson: nope, wasn't fixed until 30 minutes ago
[03:35] <davecheney> mwhudson: pls mail thumper and I with your bug numbers
[03:35] <davecheney> i'll add mine
[03:35] <davecheney> and it'll be another thing on alexisb 's plate
[03:35] <mwhudson> https://bugs.launchpad.net/ubuntu/+source/gcc-4.9/+bug/1361940
[03:36] <mup> Bug #1361940: patches for cgo on arm64 <patch> <gcc-4.9 (Ubuntu):New> <https://launchpad.net/bugs/1361940>
[03:36] <mwhudson> davecheney: this is all for cgo though, that probably shouldn't be on alexisb's plate?
[03:36] <davecheney> if it doesn't affect juju or other canonilcal developed products
[03:36] <davecheney> probably not
[03:37] <mwhudson> docker docker docker
[03:39] <davecheney> docker docker docker malkovich docker
[04:08] <ericsnow> axw: do you mind if I add another 10 files and 500 lines to that backups PR <wink>
[04:09] <bodie_> lol
[04:09] <ericsnow> axw: but seriously, thanks (to you, davecheney, and waigani) for the reviews
[04:10] <ericsnow> the rest of my backups patches are *much* smaller
[04:11] <waigani> ericsnow: welcome
[04:14] <ericsnow> who controls the juju account on github?
[04:15] <axw> ericsnow: :)
[04:15] <axw> nps
[04:16] <axw> ericsnow: all the team leads are owners I believe
[04:16] <ericsnow> axw: okay
[04:16] <ericsnow> axw: I'll bug nate about it tomorrow
[04:17] <ericsnow> axw: nps?
[04:26] <axw> ericsnow: no problems
[04:26] <ericsnow> axw: I figured as much
[04:46] <wallyworld> axw: thanks, i was wondering about wording of that message. i wanted to explicitly call out that there could be an instance running; but as you say, i think mentioning destroy --force will be enough
[04:47] <axw> cool
[06:25] <wallyworld> axw: i think testing failure bug 1202039 is either fixed, or will be with your current work?
[06:25] <mup> Bug #1202039: Provider tests are architecture-specific <arm64> <feature> <i386> <ppc64el> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1202039>
[06:27] <axw> wallyworld: I think they're already working on i386 on ppc64 right? so it's fixed already?
[06:28] <axw> CI runs the tests on i386 and ppc64 I'm pretty sure
[06:28] <wallyworld> axw: yeah, that was my thinking too, i'll mark as fix committed
[06:28] <wallyworld> just wanted to double check
[07:36] <mattyw> morning all
[08:00] <TheMue> morning
[08:58] <TheMue> dimitern: ping
[09:00] <dimitern> TheMue, hey
[09:01] <TheMue> dimitern: as I as OCR cannot review myself would you mind to take a look at https://github.com/juju/juju/pull/626 ;)
[09:01] <TheMue> dimitern: and morning btw :D
[09:01] <dimitern> TheMue, sure :)
[09:02] <TheMue> dimitern: thx
[09:04] <axw> wallyworld: just noticed I cannot edit the bugs doc
[09:04] <axw> would like to strike out a line
[09:34] <wwitzel3> fwereade: ping
[09:46] <wwitzel3> wallyworld: got time to chat about a test I want to try and fix?
[09:47] <rogpeppe1> anyone know how to get a list of all charms? i used to use http://manage.jujucharms.com/api/2/charms?text= but it doesn't seem to produce many results now
[09:51] <wwitzel3> rogpeppe1: manage.jujucharms.com is still how I know how to get a list of them
[09:51] <rogpeppe1> wwitzel3: do you have a better URL than that?
[09:51] <rogpeppe1> wwitzel3: i only get about 34 out of that
[09:52] <wwitzel3> rogpeppe1: sounds like you're getting trusty only
[09:52] <rogpeppe1> wwitzel3: actually 20 only
[09:53] <wwitzel3> oh .. hrmm
[09:53] <wwitzel3> there are 38 charms for trusty .. so if you're only getting 20
[09:53] <rogpeppe1> wwitzel3: it looks like there's a limit kicking in, but adding limit=100, for example, doesn't give me any more
[09:54] <rogpeppe1> wwitzel3: have you actually got a current-ish list, by any chance?
[09:54] <wwitzel3> rogpeppe1: https://manage.jujucharms.com/charms/trusty
[09:55] <wwitzel3> rogpeppe1: that's the HTML version if that helps anyway
[09:55] <rogpeppe1> wwitzel3: it's a hassle (i'll have to manually scrape the html) but better than nowt
[09:56] <wwitzel3> rogpeppe1: sadly it doesn't do an ajax request (that I can see) to get the results
[09:56] <wwitzel3> rogpeppe1: was hoping it might be using the API to render that list
[09:56] <rogpeppe1> wwitzel3: yeah
[09:57] <rogpeppe1> wwitzel3: it's annoying because it *did* work once. i even wrote a little program to automate getting all charms.
[10:04] <wwitzel3> rogpeppe1: yeah, according to the lp repo for that API it hasn't changed since 2013-10
[10:05] <wwitzel3> rogpeppe1: but something must have :/
[10:06] <rogpeppe1> wwitzel3: well, the last-modified time on my getcharms.go file is 2013-08, so the 2013-10 change might've broken it i guess
[10:06] <rogpeppe1> wwitzel3: which lp repo is it, BTW?
[10:08] <wwitzel3> rogpeppe1: also doest his give you better results http://manage.jujucharms.com/api/3/search ? that isn't techincally an unstable API, but if 2 stopped working for you
[10:08] <wwitzel3> rogpeppe1: https://code.launchpad.net/charmworld
[10:08] <rogpeppe1> wwitzel3: i only see 41 results there
[10:09] <rogpeppe1> wwitzel3: (assessed by searching for "files": in the JSON :-))
[10:23] <wwitzel3> rogpeppe1: http://bazaar.launchpad.net/~juju-gui-bot/charmworld/trunk/view/head:/charmworld/search.py#L141
[10:24] <wwitzel3> rogpeppe1: I feel like someone else was running in to this 20 limit thing recently
[10:25] <rogpeppe1> wwitzel3: i tried using limit=9999
[10:32] <dimitern> TheMue, reviewed
[10:32] <dimitern> TheMue, ping me if something is not clear please :)
[10:32] <TheMue> dimitern: yeah, seen a lot of it (and commented some back). thanks a lot, will mark it as wip and continue
[10:33] <dimitern> TheMue, cheers!
[10:33] <wwitzel3> rogpeppe1: yeah, sorry I couldn't get it working, the code itself seems to respect limit, but then overrides it somewhere with that default
[10:35] <rogpeppe1> wwitzel3: yeah, i couldn't see where that happens.
[10:35] <rogpeppe1> wwitzel3: and the limit doesn't always appear to be 20 though
[10:35] <dimitern> TheMue, about the dummy provider running "unsafe" networker - it certainly makes sense to use "safe" by default, but there should be a way to test the "unsafe" one if needed - we can isolate what the networker does from the system (config, interfaces), so it's fine
[10:36] <TheMue> dimitern: is it ok to do this in a second, follow-up PR? this one already grows and grows. ;)
[10:37] <wwitzel3> rogpeppe1: yeah, if you leave it off all together, it seems to be 41
[10:38] <dimitern> TheMue, i'm not saying to add more tests, just to tweak the dummy provider a bit so RequiresSafeNetworker can return true or false, just by adding a useSafeNetworker bool in the dummy provider struct and a SetUseSafeNetworker(bool) method on the dummy provider to set that flag
[10:39] <dimitern> TheMue, it's like 5-6 more lines :)
[10:39] <rogpeppe1> wwitzel3: actually no, with a more accurate count, it always seems to be 20
[10:40] <rogpeppe1> wwitzel3: (counted with http://paste.ubuntu.com/8177535/)
[10:41] <TheMue> dimitern: ah, ok, haven't been sure that in this case the "unsafe" (/me still not really happy with that term) doesn't make any harm to the own system
[10:46] <dimitern> TheMue, should we do a quick standup?
[10:46] <TheMue> dimitern: yes, already comming
[12:37] <perrito666> wallyworld: is there any assigning system for the tests that need rework?
[12:38] <wallyworld> perrito666: raise a bug and assign yourself to it. cross out the item in the doc so others can see there that that one is taken
[12:39] <wallyworld> many failing tests already have bugs
[12:39] <wallyworld> so if you go to raise a bug, it should tell you if there is one already
[12:39] <wallyworld> include the test name in the bug description
[12:40] <wallyworld> so that it has a better chance of finding any dupe
[12:41] <perrito666> I guess that created bugs are more important than the ones not yet there
[12:42] <wallyworld> no necessarily
[12:42] <wallyworld> there's failures that people haven't created bugs for
[12:42] <wallyworld> and i found today that bugs i looked at had already been fixed
[12:42] <wallyworld> but the bugs were still open
[12:43] <wallyworld> so pick a failure that you think you can fix - all fixes are good
[12:43] <katco> wallyworld: interesting, i can't add an event to the team calendar =/
[12:44] <wallyworld> katco: that's no good, that means you are not allowed to have the holiday
[12:44] <katco> wallyworld: you are  afunny one ;)
[12:44] <wallyworld> oh, you think i was joking
[12:44] <wallyworld> :-P
[12:44] <katco> wallyworld: we're planning on going to our botanical garden's japanese festival :)
[12:44] <wallyworld> cool, sounds fun
[12:44] <katco> oldest and largest in the country!
[12:45] <wallyworld> well, that's something i didn;t know
[12:45] <katco> http://www.missouribotanicalgarden.org/things-to-do/events/signature-events/japanese-festival.aspx
[12:45] <katco> oops, says "one of" the oldest/largest
[12:46] <wallyworld> ah, you americans always exaggerate
[12:46] <wallyworld> world series baseball = usa plus canada
[12:46] <perrito666> I am amazed on how US people actually measure things in order to be able to have "the largest" for almost anything :p
[12:46] <katco> hey we are THE BEST at exaggerating. no one is better, anywhere.
[12:46] <perrito666> wallyworld: its like in columbus times "the known world"
[12:47] <katco> and me? i'm the most humble person alive.
[12:47] <wallyworld> you too?
[12:47] <wallyworld> we can't both be
[12:47] <katco> hey i'm WAY more humble
[12:47] <wallyworld> of course
[12:47] <katco> lol
[12:47] <wallyworld> you have reason to be
[12:47] <katco> LOL
[12:47] <katco> so nice to work with people who appreciate a dry sense of humor :)
[12:47] <wallyworld> don't know what you mean
[12:48] <perrito666> lets say each of you is the humblest in his/her timezone
[12:48] <katco> what did you ask me yesterday? have i told you today?
[12:48] <wallyworld> lol
[12:48] <wallyworld> no you haven't
[12:48] <katco> fark off! haha
[12:48] <wallyworld> :-( you hate me
[12:49] <perrito666> wallyworld: dont be like that, we all hate you, its because you are a manager
[12:49] <wallyworld> perrito666: oh, that's a low blow
[12:49] <katco> haha
[12:50] <wallyworld> way to hurt a guy
[12:50] <katco> no, wallyworld, i definitely don't hate you. i quite like working with you, axw, and everyone i've had the pleasure to work with so far
[12:50] <katco> with the exception of mgz_, traitor!
[12:50] <wallyworld> katco:  i was joking :-)
[12:51] <perrito666> katco: nahh, dont piss off the guy that can lock your commits
[12:51] <mgz_> ;_;
[12:51] <katco> haha
[12:51] <katco> mgz_: i kid, i kid!
[12:52]  * perrito666 accidentally spills yerba all over his kb
[12:56] <wallyworld> wwitzel3: sorry i missed your ping before, i was at soccer. did you still have a question?
[13:05] <katco> need to cycle my server, brb
[13:12] <perrito666> wallyworld: I cant write the doc either
[13:13] <wallyworld> perrito666: i changed the permissions, have you tried refeshing?
[13:14] <perrito666> tx
[13:33] <natefinch> perrito666: you around?
[13:33] <wwitzel3> wallyworld: yeah, I was going to try to fixup a test from the list
[13:33] <perrito666> natefinch: I am I though you where not here
[13:33] <natefinch> perrito666: yeah, sorry, busy morning.  I'm in the hangout on the calendar event
[13:34] <wallyworld> wwitzel3: ok, or it can be any other one you may have come across that isn't there
[13:34] <wallyworld> or it can be improving the cmd/juju tests to use mocks
[13:35] <mattyw_> dimitern, do you have 10 minutes spare for a quick question, possible via a hangout
[13:36] <dimitern> mattyw_, sure, just give me 15m
[13:44] <mattyw> dimitern, great, just ping when it's a good time
[13:52] <perrito666> natefinch: interesting fact, cold medicine hinders my already low spoken english skills :p
[13:53] <natefinch> perrito666: haha
[13:53] <natefinch> perrito666: btw, it's "beats around the bush"
[13:53] <perrito666> ahh well close enough
[13:53] <natefinch> yeah, I knew what you meant
[13:54] <perrito666> natefinch: it is hard to translate those, the spanish one is nothing like it
[13:54] <natefinch> yeah... those kind of sayings are kind of crazy, because the actual words don't make any sense
[13:54] <perrito666> literal translation of spanish one is "dodges the lump"
[13:54] <perrito666> to give you an idea
[13:54] <natefinch> rofl
[13:54] <perrito666> of how far it is
[13:58] <perrito666> omg, even though its not ergonomic I must say, thinkpad keyboard that emulates the one in the laptop is awesome
[13:58] <perrito666> I wish I had found a newer one, I actually got one ibm branded :p
[13:59] <natefinch> haha
[14:01] <perrito666> I also with it was bt, this one actually has a 2.5M cable :p
[14:14] <katco> is there a place we could put consts representing config key-strings? seems silly and error-prone to repeat them all over the codebase.
[14:16] <dimitern> katco, how about in environs/config ?
[14:17] <katco> dimitern: that seems like a fine place
[14:17] <katco> dimitern: could probably even put it in environs/config/config.go
[14:18] <katco> dimitern: is this a small enough shift that i can just introduce this concept? :)
[14:19] <dimitern> katco, go for it :)
[14:19] <katco> dimitern: awesome, thanks for the input! :)
[14:20] <marcoceppi_> hook execution question
[14:21] <marcoceppi_> do hooks in a service group execute serially or is that only on the unit level?
[14:23] <katco> boy documenting all public values seems silly sometimes
[14:23] <katco> 	// ProvisionerHarvestModeKey stores the key for this setting.
[14:23] <katco> 	ProvisionerHarvestModeKey = "provisioner-harvest-mode"
[14:23] <perrito666> ahh tautological comments
[14:24] <perrito666> katco: you could expand on what exactly does that key means
[14:24] <katco> i know... i understand wanting good documentation, but an absolute rule doesn't make sense
[14:24] <katco> perrito666: that's already covered in the actual setting
[14:24] <katco> perrito666: this is literally the key to get the setting in the map
[14:25] <katco> i especially dislike repeating the name of the thing in the comment. hungarian notation all over again.
[14:47] <bac> hi marcoceppi_
[14:47] <marcoceppi_> hey bac
[14:48] <bac> marcoceppi_: lazyPower_ has filed a bug regarding supporting tags as a constraint for MAAS.  you've seen it i think.
[14:48] <marcoceppi_> bac: yup
[14:49] <bac> marcoceppi_: in the definition tags are a comma-separated list.  until now we've marked bundles with constraints listed as a comma-separated as deprecated.  clean implementation of tags will require us to reject those deprecated bundles.
[14:50] <bac> i.e. constraints: 'k1=v1 k2=v2 tags=a,b,c' is valid bug 'k1=v1,k2=v2' is not
[14:51] <marcoceppi_> bac: the error we're getting is tags is not a valid constraint
[14:51]  * marcoceppi_ checks the bundle file
[14:52] <bac> marcoceppi_: yes.  i'm trying to fix that.
[14:52] <marcoceppi_> oh, I see
[14:52] <marcoceppi_> one sec
[14:52] <bac> marcoceppi_: to properly support tags will require not allowing comma-separation in the other constraint key value pairs
[14:53] <marcoceppi_> bac: maybe constraints are all wrong
[14:53] <bac> is it possible to run charm-proof against the set of all bundles to see if it is even an issue?
[14:53] <marcoceppi_> maybe they should be a YAML list
[14:53] <marcoceppi_> bac: I can download them all and see
[14:53] <bac> marcoceppi_: that would be great
[14:53] <marcoceppi_> constraints:
[14:53] <marcoceppi_>   - key: v1
[14:53] <marcoceppi_>   - key1: v2
[14:53] <marcoceppi_> hazmat: ^^
[14:54] <bac> marcoceppi_: that may be the best long term solution but i thought you needed a fix now.
[14:55] <marcoceppi_> well, I'll look at all the bundles we have
[14:55] <marcoceppi_> and see what each is doing for constraints
[14:55] <bac> changing proof rules already touches way too many parts...
[15:01] <TheMue> oh, bugfix by accident, nice. field of a struct has been prepared but never been set. now I deeded it.
[15:01] <perrito666> TheMue: lol
[15:02] <TheMue> perrito666: yeah, gave me a panic during tests :D
[15:04] <perrito666> TheMue: which one (bug)? just in case
[15:05] <TheMue> perrito666: it never has been filed. it has been a field for checking the authorization of reading a machine
[15:06] <TheMue> perrito666: the function (it's a function type) has been created, but the field never set
[15:06] <TheMue> perrito666: and I now wanted to check if I can read => *bang*
[15:06] <perrito666> ouch, I wonder if its there on the bugs ian added to the doc which are not all reported
[15:09] <TheMue> have to check
[15:57] <natefinch> Anyone up for reviewing my log rotation change?  It's pretty small: https://github.com/juju/juju/pull/512
[16:18] <mattyw> natefinch, I'll take a look
[16:25] <perrito666> mattyw: what is a vanity url?
[16:26] <mattyw> github.com/perrito666/projectname
[16:26] <mattyw> perrito666, A url with someones name in it
[16:26] <mattyw> perrito666, I'm not happy with the name vanity url either :)
[16:27] <mattyw> but that's what they're called in the mailing list
[16:27] <mattyw> and who am I to go against consensus?
[16:27] <perrito666> I would think a vanity url is something like beautifulpopleonly.com/perrito666/thewonderfulwonderfulman/
[16:27] <perrito666> :p
[16:28] <perrito666> now that is a vanity url
[16:32] <jcw4> perrito666: can you get me one like that too?
[16:32] <perrito666> :p
[16:32] <mattyw> perrito666, I'd be happy with that one - at least make it obvious
[16:33] <mattyw> perrito666, what I'm happy and not happy with is inconsistent and changes daily
[16:33] <perrito666> we might want to rething our mentor policy to not be 12 hours distance with our reviewers
[16:34] <jcw4> perrito666: quit complaining... you're on here 24/7 anyway
[16:34] <perrito666> jcw4: Id say around 20
[16:34] <perrito666> but yes
[16:34] <jcw4> :)
[16:35] <perrito666> its the corners of the week which are a problem, my mentor will not be here until sunday (my sunday)
[16:35] <jcw4> yeah, that's a bummer.
[16:35] <mattyw> perrito666, how many corners does a week have? I thought they were circular?
[16:35] <mattyw> they feel circular sometimes
[16:35] <jcw4> I have to say though, working with folks all over the globe make it more than worth it for me :)
[16:36] <perrito666> if weeks where circular in two days it would be last monday
[16:36] <jcw4> spiral then
[16:37] <perrito666> uff, this bug is a heavy thing to pinpoint, I am pretty sure I know what is going on, I am not so sure on the how part
[16:38] <bodie_> my weeks have no corners, only hills and valleys
[16:43] <natefinch> perrito666, mattyw: a vanity url, in the context of Go is a url which is not the same as the url to the repo.  So, for example, the package that gets imported when you do import "labix.org/v2/mgo"  is actually hosted on launchpad, so the real url is launchpad.net/mgo (or something like that).
[16:46] <mattyw> natefinch, I didn't know that - thanks very much
[16:46] <natefinch> mattyw, perrito666: Go supports this through the go tool which, if it doesn't recognize the url of the import path, will fall back to trying to get a web page from that URL, and it'll look for a header that looks something like <meta name="go-import" content="labix.org/v2/mgo bzr https://launchpad.net/mgo">
[16:47] <natefinch> It's pretty nice because it means that if you control the domain, you can move your code from one host to another and not break anyone else's code that imports using the vanity url.
[16:51] <mattyw> natefinch, now I know the proper definition of vanity url my comment probably makes no sense
[16:52] <mattyw> natefinch, I was just wondering if accepting a number of dependencies that had team members names in was ok
[16:53] <mattyw> has anyone else seen this error using the local provider on tip? http://paste.ubuntu.com/8180167/
[16:58] <perrito666> mattyw: are you sure your code is up to date?
[16:59] <mattyw> perrito666, it was tip
[17:00] <perrito666> mattyw: looks a lot like someone made one of those automatic changes on the code and forgot to change a return somewhere
[17:01] <mattyw> perrito666, I was trying to recreate this https://bugs.launchpad.net/juju-core/+bug/1363143 but I can't even get that far
[17:01] <mup> Bug #1363143: local lxc deployments fail to create machines <ci> <local-provider> <lxc> <precise> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1363143>
[17:01] <perrito666> mattyw: checking
[17:01] <alexisb> perrito666, the mentorship matching is my fault, we did the best we could but most of the mature skills on the team are in +12 timezone, you are one of the few with potential overlap
[17:02] <perrito666> alexisb: sorry didnt meant to make you feel bad
[17:02] <perrito666> mattyw: and this blows running bootstrap right?
[17:02] <mattyw> perrito666, yeah
[17:02]  * jcw4 wonders about relocating to UTC+12
[17:02] <jcw4> ;
[17:02] <jcw4> )
[17:02] <jcw4> ;) even
[17:02] <perrito666> mattyw: rm /pkg/* on your go path and then recompile
[17:03] <alexisb> yes perrito666 I feel terrible, I may never recover from your slam ;)
[17:03] <wwitzel3> lol
[17:03] <natefinch> mattyw: btw, your comment is actually correct - gopkg.in/natefinch/lumberjack.v2 *is* a vanity url.  It redirects to github.com/natefinch/lumberjack at the v2 branch.
[17:03] <perrito666> this will so cost me beer on the next sprint
[17:03] <alexisb> perrito666, you should feel tremendously guilty on my behalf
[17:03] <alexisb> lol totally
[17:03] <alexisb> o wait
[17:04] <alexisb> not thumber buys the beer remember
[17:04] <mattyw> perrito666, same problem
[17:04] <alexisb> no, thumber buys the beer, remember?
[17:04] <natefinch> close
[17:04] <natefinch> one more try?
[17:04] <perrito666> we can levenstein from there
[17:04] <natefinch> lol
[17:04] <mattyw> perrito666, I'm about to EOD to be honest, maybe we can take a look at it on monday?
[17:04] <alexisb> :)
[17:05] <perrito666> mattyw: sure, ping me, honestly looks like a red herring
[17:05] <natefinch> mattyw: btw, the reason it's not under juju is because it's my personal code written during off hours.  Otherwise, yes, absolutely, anything written during hours is Canonical's and belongs under github.com/juju
[17:06] <mattyw> perrito666, ok cool
[17:06] <natefinch> mattyw: in theory, the code is MIT licensed and anyone could just fork my repo to put the code under github.com/juju
[17:06] <natefinch> but some might consider that rude
[17:07] <perrito666> that would remind me the early days of google chrome
[17:07] <perrito666> absolutely all of the deps from the project had been imported into the project svn
[17:07] <perrito666> from here it was a 3 or 4 hs checkout
[17:08] <natefinch> ouch
[17:08] <natefinch> good old SVN
[17:08] <mattyw> perrito666, I like red herrings
[17:08] <natefinch> tasty with a little lemon and butter
[17:08] <mattyw> perrito666, I might be able to work it out for myself once I've slept :)
[17:09] <perrito666> I only ate herring once in my life, in amsterdam, there was this kiosk next to the canal that made raw herring sandwitches
[17:09] <perrito666> mattyw: try coffee, has pretty much the same effect
[17:10] <mattyw> natefinch, my point is probably pretty academic as all the code is on github anyway
[17:10] <natefinch> mattyw: it's a valid point... if it were canonical's code, it should be represented as such, and under canonical's control.  But it's not, so it's not :)
[17:11] <mattyw> natefinch, I just don't want to end up in the situation where core relies on changes landing in your project but you want to take the project in another direction
[17:11] <mattyw> natefinch, but we can cross that bridge if it comes - and there are many ways of fixing it
[17:11] <natefinch> mattyw: that would be a perfectly valid reason to fork the project, and like I said, it's MIT, you can just do that.
[17:11] <natefinch> mattyw: exactly
[17:11] <natefinch> mattyw: especially for a package that's used in exactly one file... it's trivial to change.
[17:17] <mattyw> folks - it's time for me to call it a day
[17:18] <mattyw> have a good weekend all and I'll speak to you on monday
[17:19] <wwitzel3> see ya mattyw
[17:24] <TheMue> so, off for today, have a nice weekend
[17:26] <perrito666> TheMue: likewise
[17:58] <perrito666> I might be wrong here, but does this sounds like a huge isolation bug to anyone else? https://github.com/juju/juju/blob/master/juju/testing/conn.go#L426
[18:01] <natefinch> perrito666: certainly seems like something that should be exposed by MgoServer not something the suite is figuring out.
[18:02] <perrito666> natefinch: I am a bit worried about the shared nature of the mongo server also
[18:02] <perrito666> https://github.com/juju/testing/blob/master/mgo.go#L35
[18:02] <natefinch> perrito666: yeah
[18:02] <natefinch> perrito666: that very well could be why some of our tests are failing... they're running at the same time and then the streams cross and boom
[18:03] <perrito666> The failure I am looking at (only have a few logs) seems to be triggered by the test assuming the server is alive and trying to connect but it gets auth fails, which makes me think its hitting someone else's server
[18:03] <natefinch> hmm could be
[18:06] <natefinch> perrito666: this may actually not be that bad
[18:07] <natefinch> perrito666: each package runs tests as an independent process
[18:07] <ericsnow> anyone have a little time to give a follow-up review?
[18:07] <ericsnow> https://github.com/juju/juju/pull/606
[18:10] <natefinch> ericsnow: is there a reason you need to hide the fields of the archive?
[18:11] <ericsnow> natefinch: I guess not...I've been trying to make things private by default and avoid exposing them if possible
[18:12] <natefinch> ericsnow: for things that are just data... don't bother.... and this is definitely just data
[18:12] <natefinch> ericsnow: I'm used to the same pattern from past experience, too.  But honestly, if someone wants to change the filename after the make a new Archive.... who cares?
[18:13] <natefinch> it simplifies the code a bunch not to hide the values - you don't need a constructor and don't need the getters
[18:14] <ericsnow> natefinch: Archive is one of the types that I actually think might be used outside of juju, so I wanted to be extra careful there to keep the interface clear
[18:14] <ericsnow> natefinch: those fields are just implementation details
[18:15] <ericsnow> natefinch: it's the getters that expose the structure of the archive file
[18:17] <natefinch> ericsnow: it's not really an implementation detail if you're just returning what you got passed in.  It's just data
[18:18] <natefinch> ericsnow: unless you need the functions to fulfill an interface
[18:19] <ericsnow> natefinch: yeah, the fields are not part of the interface I care about here.
[18:20] <ericsnow> natefinch: so you make a good point
[18:23] <natefinch> ericsnow: it's not that the way you have it is wrong, it's just somewhat more complicated that necessary.  Not that it's actually complicated at all, of course - the functions are trivial.
[18:25] <ericsnow> natefinch: yeah, I've run into that several times and it's always tempting to just make fields/types public because it simplifies things to much
[18:25] <ericsnow> natefinch: in some cases I did so because keeping them private wasn't worth it
[18:27] <natefinch> ericsnow: I've come to the conclusion that the only time I need to make fields private is when there are interactions between different fields that would be invalidated if the fields were updated after construction.... like if you were generating the DBDumpDir just one time in the constructor.
[18:27] <ericsnow> natefinch: yeah, the caching case
[18:31] <bac> ping lazyPower_
[18:31] <lazyPower_> hey bac
[18:31] <lazyPower_> sorry i saw teh pings while i was out and about checking on my phone
[18:31] <lazyPower_> you're looking for an example bundle with tags as constraints yes?
[18:31] <bac> yes i am
[18:31] <bac> lazyPower_: any that are blocked
[18:33] <lazyPower_> bac: i edited the bundles for promulgation
[18:34] <bac> lazyPower_: so you took the tags out?
[18:35] <lazyPower_> sure did. I pointed the resource to the charm store, and removed the tags as constraints - and left a note in the bzr log + MP that i had done so for promulgation.
[18:35] <lazyPower_> https://code.launchpad.net/~kirkland/charms/bundles/transcode-cluster/bundle
[18:36] <lazyPower_> this was the hottest culprit, as the orange-box bundle has tags to denote NFS and TRANSCODE should go on hardware / physical nodes
[18:36] <bac> lazyPower_: ok.  i mean it is trivial for me to come up with test bundles but i thought i'd run my charm proof against the real ones.
[18:36] <lazyPower_> bac: well that submission would be a great one to look at
[18:37] <bac> oh, the famous transcoder...
[18:37] <lazyPower_> famous? :D
[18:40] <bac> lazyPower_: minimally.  :)
[18:40] <bac> lazyPower_: that bundle is actually trivial wrt constraints.
[18:41] <lazyPower_> indeed. very minor set of constraints - it was throwing the charmworld proofer through loops though
[18:41] <bac> lazyPower_: i've got a charmworldlib fix that i'll put up for review soon.  it'll require a small code change to charmworld and a redeploy, which cannot happen until monday
[18:41] <lazyPower_> when i run charm proof --offline  it passes.
[18:41] <bac> lazyPower_: you're not currently blocked so monday should be fine, correct?
[18:55] <perrito666> natefinch: yes, but that still leaves a whole package to race against
[18:55] <perrito666> I mean, you cannot guarantee that a mgo server died properly in the last test
[18:57] <natefinch> perrito666: well, the tests are run in series, not in parallel, so there's no concern as long as the setup and teardown do the right thing
[19:08] <perrito666> natefinch: I believe the tear down might be failing
[19:09] <perrito666> this is a heisembug so I might try to make sure this is isolated and hope for the best
[19:29] <bodie_> https://github.com/juju/juju/pull/617 should be done now
[19:31] <bac> hi marcoceppi_, when you get a chance could you look at this charmworldlib branch for the constraints issue: https://codereview.appspot.com/131710044/ ?
[19:39] <marcoceppi_> bac: I wonder if there's a limit to characters that can be in a tag/constraint
[19:39] <marcoceppi_> nvm
[19:39] <marcoceppi_> ignore what I'm saying
[19:39]  * bac ignores you
[19:40]  * bac listens again
[19:50] <natefinch> ericsnow: is backups.create actually used anywhere?
[19:50] <ericsnow> natefinch: not until the next patch
[19:50] <natefinch> ericsnow: ahh ok
[19:51] <ericsnow> natefinch: I linked it in the PR summary
[19:57] <natefinch> ericsnow: aww... reading?! :/
[20:55] <perrito666> aghhh I believe I foundiiiiiittttt
[20:55] <natefinch> huzzah!
[20:59] <perrito666> ish, someone might be re-setting the mgoserver but I cannot find who yet :p


[02:21] <LinDol> hi all
[05:53] <wfio> Has anyone experienced Ubuntu Software center font completely washing out and no longer visible in Ubuntu Gnome (14.10)?Just did a fresh install and I can no longer see the font in the Software Center -- it's really annoying
[05:54] <darkxst> wfio, yes its probably an issue with the GNOME theme
[05:55] <wfio> Oh you think so? I had to turn on high-control in Accessibility just to be able to see it
[05:55] <wfio> Blowing my eyes out now ha
[05:56] <wfio> I didn't have this problem when I did Ubuntu and then installed Gnome overtop of it -- but I decided to try a straight up Ubuntu Gnome install and it went wozzy
[05:57] <wfio> Any recommendations?
[06:00] <darkxst> wfio, we are probably dumping USC this cycle ;)
[06:03] <wfio> What's that?
[06:03] <wfio> Sorry I'm new to this world
[06:03] <darkxst> Ubuntu Software Center
[06:03] <wfio> Synaptics?
[06:03] <darkxst> no, http://imgur.com/B8mj9Lb
[06:03] <darkxst> then we will eventually switch to gnome software but that might be a couple of cycles away
[06:04] <wfio> nice
[06:04] <wfio> How long is a cycle?
[06:04] <darkxst> 6 months
[06:05] <wfio> cray
[06:05] <wfio> i love the gnome vibe
[20:18] <x00e> Hello ppl
[20:20] <x00e> quick question: is there any way i can display in message tray other info besides notifications? I`m thinking about some ls-sensors output and stuff like that. maybe some cup info, etc.
[20:20] <eliasps> Hi x00e
[20:21] <eliasps> I believe that you would have to tweak this extension to do that: https://extensions.gnome.org/extension/9/systemmonitor/ but this requires coding skills
[20:22] <eliasps> There is also this, which is awesome, but it is for the panel, not the message tray area: https://extensions.gnome.org/extension/120/system-monitor/
[20:23] <x00e> tried both of them :)
[20:24] <x00e> system-monitor looks nice, but I cant figure how I can display more than one temp / fan RPM
[20:25] <x00e> also, it would have been nice something more un-intrusive. hence the message tray. quick enough to be shown with a key shortcut, but otherwise not getting in the way
[20:26] <x00e> well .. thanks anyway :)(
[20:27] <eliasps> I could tweak the code of the one on the message tray to check how is it possible to display other stuff too, but I cannot do that immediately.
[20:27] <eliasps> I mean I need time.
[20:28] <x00e> neah, that`s ok :)
[20:28] <x00e> i don't want to give you stuff to do
[20:28] <x00e> i was just asking around, just in case
[20:31] <eliasps> Nah, it's no problem, I'm interested into it after all. Stick around a couple more days on the channel. When I'm on my computer I'm also on IRC, so I'll let you know if I have any news on the extension
[20:31] <x00e> heh
[20:31] <x00e> will do :)


[02:19] <mamari> .04
[02:20] <kernal> .22
[02:21] <TaZeR> .50 deagle
[02:21] <kernal> :x
[02:22] <kernal> OK lets go
[06:08] <mantar> Regarding the mouse-jumping-to-the-text-cursor problem I had earlier -- I never did figure out what was causing it, but logging out and back in fixed it. So that's something at least.
[07:05] <crytolyfe> Hey there ive just downloaded ubuntu mate and everything i try to download including from the boutique and it tells mePackage does not exist
[07:05] <crytolyfe> Check the spelling of the package name, and that the appropriate repository is enabled.
[07:06] <diogenes_> crytolyfe, try with synaptic
[07:08] <crytolyfe> where would i find synaptic
[07:09] <crytolyfe> actully ive tried to download synaptic but the same error comes up
[07:11] <diogenes_> crytolyfe, open term
[07:11] <crytolyfe> okay
[07:12] <diogenes_> type: sudo apt install synaptic
[07:12] <kernal> what does 'sudo apt update' yield?
[07:12] <diogenes_> kernal, what?
[07:13] <crytolyfe> This is what came up crytolyfe@Waldoworld:~$ sudo apt-get install synaptic
[07:13] <crytolyfe> [sudo] password for crytolyfe:
[07:13] <crytolyfe> Reading package lists... Done
[07:13] <crytolyfe> Building dependency tree
[07:13] <crytolyfe> Reading state information... Done
[07:13] <crytolyfe> Package synaptic is not available, but is referred to by another package.
[07:13] <crytolyfe> This may mean that the package is missing, has been obsoleted, or
[07:13] <kernal> does he get any errors updating the package lists?
[07:13] <crytolyfe> is only available from another source
[07:13] <crytolyfe> E: Package 'synaptic' has no installation candidate
[07:13] <crytolyfe> crytolyfe@Waldoworld:~$
[07:14] <diogenes_> crytolyfe, no apt-get
[07:14] <diogenes_> just apt
[07:14] <kernal> @crytolyfe, do you get any errors updating your package lists? 'sudo apt update''
[07:16] <crytolyfe> ahh its working thank you
[07:17] <crytolyfe> i did not get any errors updating
[07:17] <kernal> so now you can install programs?
[07:30] <crytolyfe> yeah i can thanks
[07:31] <kernal> sweet
[07:32] <crytolyfe> But im still confused if a package i downloaded from my browser doesnt come up when i search on ubuntus website for the list of packages what can i do to install them
[07:33] <crytolyfe> i was reading there is some third party applications i can use?
[07:33] <kernal> you might need to add that repository to your sources list
[07:34] <crytolyfe> how would i go about doing that
[07:35] <kernal> link to the website you're talking about?
[07:35] <crytolyfe> https://www.dash.org/get-dash/
[07:36] <kernal> that website only lists a windows/64 installer?
[07:37] <kernal> is there a linux version of this software?
[07:37] <crytolyfe> this is it https://github-production-release-asset-2e65be.s3.amazonaws.com/19352450/8322ab66-f72b-11e7-9b57-cb48dbc9d3b7?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180129%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180129T072050Z&X-Amz-Expires=300&X-Amz-Signature=6c9b2c04ff8c74a3791a96f57daef61b61cef7a705e7aed7589188f14857d837&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=at
[07:37] <crytolyfe> tachment%3B%20filename%3Ddashcore-<IP_ADDRESS>-linux64.tar.gz&response-content-type=application%2Foctet-stream
[07:38] <crytolyfe> dashcore-<IP_ADDRESS>-linux64.tar.gz
[07:39] <kernal> https://www.dash.org/forum/threads/linux-wallet-download-installation-guide.3901/
[07:39] <crytolyfe> dayum how did i not see that thanks kernal
[07:40] <kernal> :D
[07:51] <crytolyfe> how do i become root in term?
[07:51] <crytolyfe> this is coming up
[07:51] <crytolyfe> x����?�),�PyH�qFcrytolyfe@Waldoworld:~/Desktop$ sha256 dashcore-<IP_ADDRESS>-linux64.tar.gz
[07:51] <crytolyfe> mlockall: Cannot allocate memory
[07:51] <crytolyfe> Warning: couldn't lock memory, are you root?
[07:51] <kernal> sudo su
[07:54] <crytolyfe> then sha256 dashcore-<IP_ADDRESS>-linux64.tar.gz
[07:54] <crytolyfe> ?
[07:54] <crytolyfe> nvm lmao
[07:56] <kernal> see ya'll later!
[08:15] <schueler> rno
[08:15] <schueler> www.pornhub.de
[08:38] <Faults> I suppose that link is not work safe
[08:40] <ircfan> no idea, could be a virus
[09:11] <Falpha> Does anyone know how to increase the visual size of everything in ubuntu-mate?
[09:11] <Falpha> All of the programs have a very small font size.  it's very frustrating.
[09:36] <Falpha> anyone know how to increase the cursor size?
[09:37] <ircfan> Fonts can be tweaked in the System menu, Preferences, Look and Feel
[09:38] <ircfan> (in Appearance)
[09:39] <Falpha> oh man way better
[09:39] <Falpha> way way way way better
[09:39] <Falpha> i don't know why os's make these stupid, ridiculously small fonts
[09:40] <ircfan> hehe
[09:40] <ircfan> the cursor seems a bit more complicated thats why i post a link: https://askubuntu.com/questions/126491/how-do-i-change-the-cursor-and-its-size
[09:41] <Falpha> they should set it in installers
[15:43] <doge-doge> is having multicasting enabled useful for anything other than "discovering" devices on the home network?
[18:08] <jbrown419> hi all
[18:09] <jbrown419> i need some help, all ubuntu will do i bring up the command line black screen after grub
[18:10] <jbrown419> while on this command screen is randomly says [ 190.056149] ERROR @wl_notify_scan_status :
[18:10] <jbrown419> it will not let me complete any commands though cause it says its read-only
[18:11] <jbrown419> any ideas?
[18:11] <nemo> jbrown419: I'd start by suggesting booting with quiet and splash off...
[18:11] <nemo> jbrown419: also. if you did a kernel update recently, falling back to an old one
[18:11] <jbrown419> i tried the kernel and its the same outcome
[18:12] <jbrown419> ill try the removing quiet and splash
[18:12] <nemo> jbrown419: also since this is almost definitely ubuntu generic, #ubuntu is more likely to be more help
[18:12] <nemo> jbrown419: there's been report problems of boot issues after applying intel's recent microcode
[18:12] <nemo> this has impacted both linux and windows
[18:12] <nemo> could be related? dunno
[18:12] <jbrown419> yep
[18:12] <nemo> I'm on AMD @ home
[18:12] <jbrown419> thats exactly the last thing i did
[18:12] <nemo> + one old not-impacted Intel
[18:13] <nemo> spectre is an issue too obv, although the microcode probs seem more intel
[18:13] <nemo> and meltdown is a bigger immediate perf impact on them
[18:14] <jbrown419> i just have 2 mini mac 2009 servers that i want to use to host a local website
[18:14] <nemo> mm
[18:14] <nemo> well. if load is modest that's probably not a problem
[18:15] <nemo> hell. a raspberry pi would work just fine
[18:15] <jbrown419> yah its my small businesses HVAC site
[18:15] <nemo> has more memory than many machines a few years ago
[18:26] <mate|32881> Hi
[18:27] <mate|32881> I have recently experimented some error on my ubuntu looking like : script/chrome /messenger
[18:28] <mate|32881> How can I fix it please (my distrib is up to date from update manager yesterday)
[18:28] <mate|32881> I have  a printscreen if you want
[18:29] <urs> Hallo ich habe eine Frage: Welche Version ist für mich besser die 32 bit oder die 64 bit. Für einen HP Pavillion dv6699ez/ Intel core 2 Duo processor T7500 (2.2Ghz) / 250GB Hard Drive / 2GB RAM DDR2 . Vielen Dank für den Tipp.
[18:30] <sixwheeledbeast> !de
[18:31] <mate|32881> ?
[18:31] <nemo> mate|32881: yeah. a bit more text would be good
[18:31] <nemo> screenshot if you might
[18:32] <nemo> I have no idea what that is in context but it kinda reads like a browser error
[18:32] <nemo> s/might/must/
[18:33] <sixwheeledbeast> yeah need a bit more information on that one. Stabbing in the dark without at least the full error message.
[18:33] <nemo> jbrown419: I don't want to distract #ubuntu by something I might have missed, but did you by any chance share a screenshot of how far the boot gets with quiet and splash disabled?
[18:33] <nemo> jbrown419: could be useful info
[18:33] <nemo> jbrown419: also... disabling acpi and hardware probing sometimes helps w/ booting ubuntu on random hardware
[18:34] <nemo> also... personally I've given up on all ubuntu past 14.04 😝
[18:34] <nemo> whether that helps or not in your particular case..
[18:34] <nemo> did help w/ a few laptops over here
[18:34] <mate|32881> I'm trying to send a file (Pscreen) but when I click on the buttons here is the message i got : App: AisMDMMInTAOji478kuNxz exceeds the limit.
[18:34] <mate|32881> :/
[18:35] <mate|32881> on chromium
[18:35] <nemo> ah
[18:35] <nemo> I have very little chromium familiarity personally
[18:35] <nemo> I use it as little as possible
[18:35] <nemo> mate|32881: if you can copy the errors, try pastebinning them
[18:35] <nemo> better than images anyway
[18:35] <nemo> mate|32881: also consider starting your browser from a terminal so you can see what is on stderr
[18:36] <nemo> assuming the error is reproducible on restart
[18:37] <mate|32881> same on ffx
[18:38] <mate|32881> oki, I'll try to do that - thanks anyway
[18:38] <mate|32881> I hve to leave
[19:01] <jbrown419> anyone have any idea why my fs is read-only and cannot be used
[19:01] <diogenes_> jbrown419, what do you mean?
[19:02] <teward> jbrown419: you need patience
[19:02] <teward> !crosspost
[19:02] <jbrown419> ubuntu mate will not start desktop, and from command line, i cannot apt anything
[19:02] <teward> jbrown419: does it give you an *error* when you try and startup?
[19:02] <teward> does it say you have a RO system or no?
[19:03] <jbrown419> no error, just dumps me into login black screen
[19:03] <teward> it lets you login, I assume?
[19:03] <jbrown419> and the guy that was helping me just up and left lol, im not trying to crosspost
[19:03] <teward> no, he didn't 'up and leave'
[19:03] <teward> you just have zero patience
[19:03] <jbrown419> yes, but no desktop gui
[19:03] <teward> jbrown419: when you try and do something, does it complain about a read-only system?
[19:03] <jbrown419> yes
[19:04] <teward> jbrown419: check your syslog and dmesg for any filesystem error messages.
[19:04] <Akuli> did this problem just appear by itself?
[19:04] <teward> i'll bet you that the system is set to go read-only on disk errors.
[19:04] <Akuli> did things work before?
[19:04] <jbrown419> yes, i used update center, restarted, and this happened
[19:04] <jbrown419> let me check syslog
[19:05] <Akuli> $ sudo mount -o remount /
[19:05] <Akuli> now you have read-write
[19:05] <teward> Akuli: no, not necessarily
[19:05] <teward> Akuli: sudo mount -o remount,rw /
[19:05] <Akuli> ok :D
[19:05] <teward> but that will *only* work if there wasn't a problem with the filesystem or mounting that needs fixed
[19:06] <teward> and that's why I said he should check syslog and dmesg
[19:06] <Akuli> backing up files might be a good idea, maybe this is a hard drive problem?
[19:06] <teward> because if there *was* and it's just an 'unclean' filesystem or something he can fsck the thing.  if it's an I/O issue, then he's got a bigger problem
[19:06] <jbrown419> no need, there is nothing i want on it
[19:06] <teward> jbrown419: let us know if you see anything in the syslogs or dmesg output
[19:06] <teward> because if it failed to mount for some reason that'd be important to know.
[19:06] <jbrown419> ive ran fsck to no avail
[19:07] <Akuli> $ dmesg | grep mount
[19:07] <jbrown419> ok one sec
[19:09] <jbrown419> ext4-fs (sda2) mounted filesystem with ordered data mode Opts: (null)
[19:09] <jbrown419> EXT4-fs (sda2): Unrecognized mount option
[19:10] <jbrown419> "notime.errors=remount-ro" missing value
[19:11] <jbrown419> audit: type=1400 audit(1517252825.363:9): apparmor="STATUS" operation="profile_load"
[19:13] <jbrown419> i dont understand why MATE would make this happen. It's one thing for a distro not to work, but for it to make it so i cannot use my computer period is absurd
[19:13] <jbrown419> removing my ability to boot from usb is weird
[21:25] <G33kDad> hello. i have a question. is it possible to change the default keybinding to launch the brisk menu? how about the icon that appears in the panel for brisk menu? Thanks!


[00:36] <BenC> mjg59: well it stops if I kill acpid (and it happens even at the terminal without X running)
[00:37] <BenC> mjg59: Actually, I should have answered "no" since I get two actual keyboard events if acpid is running
[00:38] <BenC> mjg59: noticed by running showkeys
[03:24] <cathyal> Hi
[03:24] <cathyal> is the ubuntu kernel based off the debian kernel
[03:45] <TheMuso> cathyal: No.
[03:47] <cathyal> figures
[06:25] <CarlFK> I can cause a kernel panic - what's the app I run to help with the bug report?
[13:07] <Kano> hi, did you know about the new ndiswrapper problem<EMAIL_ADDRESS>[13:08] <Kano> i see no fix for that in 8.17, or do i miss something?
[13:18] <rtg> Kano: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=commit;h=fb54a3e61f44d37b07426f2e7a86d7ca0a99e90a
[13:23] <Kano> ok, thanks
[13:44] <NCommander> smb_tp, thanks! (I saw your email)
[13:44] <Kano> rtg: will you do a 2.6.28 test git soon?
[13:46] <rtg> Kano: soon, being sometime in the next few weeks.
[14:54] <CarlFK> "kerneloops is a daemon that collects kernel crash information..."  does that include panic ?
[14:55] <rtg> an oops is a panic.
[14:55] <CarlFK> neat.  it's magic. :)
[14:56] <CarlFK> I am guessing I have to do something?  kerneloops.org is not loading
[14:57] <rtg> amitk is out kerneloops expert
[14:57] <rtg> s/out/our/
[15:05] <amitk> CarlFK: once you isntalled kerneloops, a gnome applet should be running in the background
[15:05] <CarlFK> amitk: what if I am runing on u-server?
[15:05] <amitk> CarlFK: no UI?
[15:05] <CarlFK> right
[15:05] <CarlFK> well, no gui :)
[15:06] <amitk> CarlFK: ps aux | grep kerneloops
[15:06] <CarlFK> if it is a huge problem running it without X, I can load it up - this box is just to hack on this
[15:06] <CarlFK> ps aux | grep kerneloops = nothing but the grep...
[15:07] <amitk> just run it manually then
[15:08] <amitk> with --nodaemon
[15:08] <amitk> if you want to know what it is doing
[15:11] <CarlFK> gah - "Connection to cp666 closed by remote host."
[15:11] <amitk> CarlFK: I guess it was designed mostly for desktop users.
[15:11] <amitk> cp666?
[15:11] <CarlFK> I am working with a memory leak, and it kills processes
[15:11] <CarlFK> compaq 666mhz
[15:11] <CarlFK> hostname
[15:12] <amitk> CarlFK: run it manually and let me know what happens.
[15:12]  * amitk -> steps out for 30mins
[15:44] <rtg> amitk: what do we have to do to prep the Jaunty kernel to be  a good kerneloops citizen?
[15:52] <amitk> rtg: add something in the VERSION to identify it as Ubuntu
[15:53] <amitk> rtg: and info d-i and buildd folks about the same
[15:54] <rtg> amitk: lets make sure it gets done early, cause its gonna break some stuff, right?
[15:54] <amitk> rtg: right
[15:54] <amitk> rtg: who is preparing the tree? you on BenC ?
[15:54] <amitk> s/on/or
[15:55] <rtg> haven't started yet. isn't pgraner keeping a list of UDS topics somewhere?
[15:57] <BenC> amitk, rtg: I'm doing the rebase for jaunty this weekend
[16:42] <CarlFK> amitk: as memory gets used, processes are being killed.  I bet kerneloops gets killed.  is there some way to prevent that?  (I am guessing best to disable the killing processes process...
[16:45] <CarlFK> how can I set 80x50 to get more lines on the console ?
[17:29] <nxvl> hi!
[17:29] <nxvl> is there any way i can have my own branch in kernel.ubuntu.com?
[17:29] <nxvl> and how can i create one
[17:30] <NCommander> nxvl, you need a kernel.ubuntu.com (aka zinc) account
[17:30] <nxvl> oh
[18:20] <amitk> CarlFK: use sysctl to write '2' to /proc/sys/vm/overcommit_memory to turn off overcommit. That should keep OOM killer at bay.
[18:30] <CarlFK> amitk: given I have to keep rebooting the box, what's the kernel param to do it?
[18:30] <amitk> CarlFK: shove it into /etc/sysctl.conf
[18:41] <CarlFK> amitk: didn't help: juser@cp666:~$ cat /proc/sys/vm/overcommit_memory ; 2
[18:41] <CarlFK> still killed lots of processes before the panic
[18:43] <amitk> CarlFK: how do you it kills processes?
[18:44] <CarlFK> amitk: on the console: "out of memory, kill process (123)..."
[18:46] <CarlFK> I am about to run it in a vm, so I should be abele get screen shots
[18:56] <amitk> CarlFK: is this a custom app leaking memory?
[18:57] <CarlFK> amitk: I think it is the vivi v4l2 driver (that is part of vanilla kernel)
[18:57] <CarlFK> the app I use is the V4L2 sample: caputre.c
[18:57] <amitk> CarlFK: ohh.. a kernel driver
[18:57] <CarlFK> yes
[18:57] <NCommander> amitk, https://launchpad.net/bugs/290153 - do you know if anyone been working on this?
[19:00] <amitk> NCommander: not that I know of. Make sure ogasawara knows about it. She is our task master.
[19:00] <amitk> CarlFK: so running the capture app causes the oops?
[19:00] <NCommander> ogasawara, https://launchpad.net/bugs/290153 - mind taking a look, I know a few people who are having this one
[19:01] <CarlFK> amitk: yep
[19:01] <CarlFK> amitk: I am building up docs on it: http://linuxtv.org/v4lwiki/index.php/Test_Suite#memory_leak_2
[19:02] <amitk> CarlFK: you might try running ulimit on the capture process to limit its memory
[19:02] <amitk> man bash -> grep ulimit
[19:02] <CarlFK> amitk: will that help fix the bug, or just prevent it?
[19:03] <amitk> CarlFK: prevent the capture process from exceeding its size. If it is the one leaking memory, it should crash first, not other processes.
[19:04] <CarlFK> amitk: given the memory isn't freed when the app exites, will ulimit help?
[19:05] <amitk> CarlFK: the app exits correctly?
[19:06] <CarlFK> amitk:  exit(EXIT_FAILURE);   line 54 http://linuxtv.org/hg/v4l-dvb/file/b45ffc93fb82/v4l2-apps/test/capture_example.c
[19:07] <CarlFK> if i run the app 8-12 times (depending on box) I get various flavors of crash that require a reboot
[19:08] <amitk> CarlFK: can't get into it right now (9pm here). Could you please file a bug with all the info consolidated and how to reproduce it.
[19:11] <CarlFK> amitk: on lp, right?
[19:11] <CarlFK> what package?
[19:13] <amitk> CarlFK: yeah. File it against 'linux' now since you suspect the kernel is oopsing
[19:13] <CarlFK> amitk: I have a few screen shots of the console - wana see?
[19:13] <CarlFK> http://dev.personnelware.com/carl/a/qemu_2.png
[19:14] <CarlFK> 0-4 are the whole sequence
[19:14] <CarlFK> er, stops at 3.  4 is this chat window... opps.
[19:28] <amitk> CarlFK: I find it very surprising that turning off overcommit_memory still triggers OOM
[19:29] <amitk> CarlFK: what is the line you put in sysctl.conf?
[19:33] <CarlFK> for that I ran sysctl
[19:34] <CarlFK> amitk: oh hell... I forgot to sudo
[19:35] <amitk> CarlFK: you don't need sudo there. Just add vm.overcommit_memory = 2 to a new line in the file
[19:35] <amitk> and reboot
[19:36] <CarlFK> well... takes a while for qemu to reboot
[19:36] <CarlFK> so I need to sudo for kerneloops --nodaemon ?
[19:36] <CarlFK> do I... ?
[19:38] <amitk> CarlFK: you shouldn't need to. But no harm in it.
[19:42] <CarlFK> amitk: kerneloops --nodaemon means if the shell is killed,  kerneloops goes too, right?
[19:44] <amitk> CarlFK: yeah
[19:47] <amitk> CarlFK: kerneloops isn't really a solution to your current problem. If you are able to reproduce this in a VM, then see if you can get a serial console going there.
[19:48] <CarlFK> amitk: ok.  I have done it, but will take a while to figure that out, so get out of here while you have a chance :)
[19:51] <amitk> heh
[20:35] <ogasawara_> NCommander: thanks for the note about bug 290153
[21:47] <CarlFK> Is this the OOM killer, or something else? [  289.211607] Out of memory: kill process 3980 (sshd) score 2809 or a child [  289.215599] Killed process 3982 (bash)
[21:55] <soren> CarlFK: Yes, that's the OOM killer doing its thing.
[21:55] <CarlFK> thanks.
[21:56] <soren> CarlFK: It sees you're out of memory and using a set of heuristics, it selects a process and kills it to free memory.
[21:58] <CarlFK> any idea how to turn it off?
[21:58] <soren> Stop running out of memory.
[21:58] <CarlFK> I am trying to gather info about a kernel panic,
[21:58] <CarlFK> heh - good plan.