[03:06] <TheMuso> @pilot out
[04:20] <pitti> Godo morning
[04:23] <pitti> ev: apport patch> NB that the data can already be bytes, and in most cases, should be; you seem to have hit a corner case where a string is recognized as binary data
[04:24] <pitti> ev: is this running with py2 or 3? looking at _is_binary() it should work alright with py3
[04:25] <pitti> ev: for the py2 case, it looks like a "if isinstance(string, unicode)" check is missing?
[04:37] <pitti> ev: would it be possible for me to get the .crash file it was trying to reprocess? I'm afraid it's not quite obvious which kind of data caused this
[05:53] <gogo_> Hello, any idea if we will be able to install catalyst legacy drivers in Ubuntu 12.10? There is a thread about this on reddit --> http://www.reddit.com/r/Ubuntu/comments/11743j/ubuntu_developerstesters_please_comment_on_status/
[05:58] <RAOF> gogo_: Short answer -no.
[05:59] <RAOF> gogo_: Although the free drivers for those cards aren't terrible.
[06:02] <gogo_> RAOF: Oh, what happens when a user having these old cards tires to install catalyst driver in Ubuntu 12.10? I think Ubuntu still shows an option to install fglrx for legacy cards, which gives users a broken experience.
[06:02] <gogo_> tries*
[06:04] <RAOF> gogo_: It shouldn't; we (should) only display the proprietary drivers as an option if the proprietary drivers actually support the card they're using.
[06:06] <RAOF> (Also, that thread is somewhat out of date; the free drivers in Quantal should support full acceleration up to < radeon 78xx (and possibly 3D for the 78xx & 79xx cards, although I've not tested that and I'm not sure how well it works).
[06:14] <gogo_> RAOF: Thanks for the info, I am installing Ubuntu 12.10 now; will check out open source drivers.
[06:35] <dholbach> good morning
[06:39] <diwic> infinity, I got a build error email from Launchpad this morning, it says pulseaudio failed building on quantal/armhf, but when I click on the build log I get a "lost something?" page. Is it anything I should do anything about?
[06:45] <cjwatson> diwic: that means it's been retried, and in this case it succeeded, so ignore it
[06:46] <diwic> cjwatson, ok, thanks
[06:46] <alkisg> Hi, 4 out of 5 times this file cannot be found and is breaking firefox upgrade, where can I report a web-server related problem?
[06:46] <alkisg> http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_<IP_ADDRESS>.orig.tar.gz
[06:46] <cjwatson> (assuming this wasn't a PPA - I'm checking the primary archive)
[06:46] <diwic> yep, it was the primary archive
[06:46] <diwic> alkisg, +1, I'm seeing the same problem this morning
[06:47] <alkisg> diwic: to solve it I put wget in a while loop... it succeeded that way :-/
[06:47] <sarnold> alkisg: some mirrors had it, some mirrors didn't?
[06:47] <alkisg> sarnold: yes, for example:
[06:48] <cjwatson> There are only two hosts behind archive.c.c
[06:48] <diwic> @pilot in
[06:48] <alkisg> <IP_ADDRESS> => not found, <IP_ADDRESS> found
[06:49] <cjwatson> right, kudan has it, sadalbari doesn't
[06:49] <cjwatson> I'll ask our sysadmins
[06:50] <alkisg> Thank you cjwatson
[06:50]  * dholbach hugs diwic
[06:51] <diwic> dholbach, thanks, still unsure of what to do with it :-/
[06:53] <i3d> The latest update seem to have changed the behavior of df output
[06:53] <i3d> df does not print root filesystem anymore
[06:55] <dholbach> diwic, I think that even if you can't upload a patch directly, it's still useful to check some of the patches and find somebody who can get them in - basically try to help nudge the patch along
[06:56] <diwic> dholbach, or maybe redo them as SRUs
[06:56] <dholbach> yes
[06:57] <dholbach> many of the people who are submitting patches don't know all the correct procedures yet
[06:57] <dholbach> so whatever helps them get their change in is much appreciated
[06:58] <i3d> http://pastebin.com/AnW9g5zj would some wise minds take a look and see what might be the problem?
[07:06] <cjwatson> i3d: strace -s 1024 please to see full strings.  but isn't /dev/sda5 your root fs?
[07:07] <i3d> cjwatson: ok search on 12.10 bugs and I think I found it... https://bugs.launchpad.net/ubuntu/quantal/+source/mountall/+bug/1060296
[07:07] <i3d> looks like it is a legit issue
[07:08] <i3d> right that is my root fs... but after the latest update, it becomes -
[07:08] <i3d> hopefully will get fixed soon..
[07:10] <cjwatson> i3d: ah, right - yeah, Steve's working on that
[07:13] <i3d> cool thanks cjwatson !
[07:46] <elixey> i'm on ubuntu server 12.04 and running     cat /proc/sys/kernel/random/entropy_avail     will steadily decrease estimated entropy in the system
[07:57] <elixey> btw, that stuff doesn't occur in debian 6.0
[07:57] <elixey> why does it happen?
[07:57] <elixey> what possible use could there be
[07:57] <sarnold> elixey: it doesn't? o_O
[07:57] <elixey> sarnold, have you triedit?
[07:58] <sarnold> elixey: no debian machines around :/
[07:58] <elixey> why wouild it happen in ubuntu sarnold
[08:04] <mvo> cjwatson: sorry if that got answered already, but is someone looking at bug #1064545 - if not I can do that now
[08:06] <seb128> mvo, slangasek fixed that yesterday no?
[08:06] <seb128> mvo, https://launchpad.net/ubuntu/+source/update-notifier/0.125
[08:06] <seb128> https://launchpad.net/ubuntu/+source/update-notifier/0.126 fixes the build
[08:08] <sarnold> btw, elixey's problem answered: http://lkml.indiana.edu/hypermail/linux/kernel/1004.0/01031.html
[08:08] <mvo> seb128: oh, ok, the bug is not closed and no bug references, this is why I was confused, if its done, I will leave it as is
[08:09] <seb128> mvo, sorry for breaking it, "it's just translations updates" ... you tricked me there :p
[08:10] <mvo> seb128: ehhh, sorry !
[08:10]  * seb128 hugs mvo, no worry
[08:10]  * mvo hugs seb128 back
[08:11] <seb128> mvo, on the good side Steve added tests for that issue so it will not happen again ;-)
[08:11] <mvo> seb128: great!
[08:11] <mvo> seb128: if you are certain its the one of the bug, would you mind closing the bug?
[08:11] <seb128> mvo, doing it
[08:12] <mvo> ta
[08:12] <cjwatson> mvo: yeah, what seb128 said :-)
[08:13] <seb128> mvo, it still feel weird that "$package" is marked as a string to translate when the translation should be "$package", it's a translator trap for sure
[08:13] <cjwatson> Yes, it should be untranslatable; if you want to figure out how to make it so, I'm sure slangasek would appreciate it
[08:13] <mvo> seb128: I haven't looked at this at all
[08:18] <seb128> cjwatson: right, I'm pretty sure that if it's done this way it's because there is no trivial solution though :-(
[08:19] <seb128> cjwatson, slangasek: one workaround could be to make the package build hack the pot at the end of the build to drop that string from the template so it wouldn't show on launchpad...
[08:32] <ev> pitti: yeah, I was hopeful to look over a .crash file, but they're surprisingly absent on the retracer boxes.
[08:33] <ev> pitti: I'll see if I can force it to happen again
[08:33] <pitti> ev: oh, doesn't it download the report from somewhere?
[08:34] <cjwatson> seb128: I bet this libgtk2-perl failure is related to https://bugzilla.gnome.org/show_bug.cgi?id=616997
[08:34] <cjwatson> That's the obvious change in Gtk+ 2.24.12
[08:34] <pitti> ev: AFAICS this coudl happen if you have an unicode (py2) / str (py3) object with characters < 32
[08:34] <ev> pitti: apols, my brain is still warming up
[08:34] <pitti> ev: is your retracer using py2 or py3?
[08:34] <ev> I was thinking of the .crash file for apport-retrace itself
[08:34] <ev> py2
[08:35] <pitti> ev: ah, ok; that's relieving, as it really ought to work for py3
[08:35] <seb128> cjwatson, http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=1070c5849e45433ad66c076e0bf692d936813a31 then ?
[08:36] <ev> pitti: I think it's time to switch to py3 on them, once this issue is sorted
[08:37] <cjwatson> seb128: Yeah, I suspect that commit broke it.  I'm having a look round to figure out how to adapt the Perl tests now
[08:37] <cjwatson> (I suspect this is just a test bug)
[08:39] <diwic> @pilot out
[08:39] <diwic> might continue later
[08:39] <cjwatson> Though, I dunno, seems non-ideal that you can't call gtk_recent_chooser_set_current_uri right after gtk_recent_manager_add_item any more
[08:40] <seb128> right...
[08:40] <cjwatson> I guess because reload_recent_items hasn't been called
[08:43] <cjwatson> But I suppose this is kind of the point of that bug fix - don't guarantee that items show up in the chooser immediately, because it's too slow
[08:44] <cjwatson> Could just have the test forcibly emit the changed signal, maybe
[08:45] <seb128> I'm still surprised it was that slow before (looking at the number on the bugzilla comments), even sequential adding for the entries shouldn't take that long... anyway those who fixed it this way know that part of GTK and probably did the right thing
[08:47]  * cjwatson tries adding $manager->signal_emit('changed');
[08:48] <cjwatson> That looks happier
[08:48] <cjwatson> Result: PASS
[08:49] <seb128> cjwatson, \o/
[08:49] <cjwatson> I'll test that a bit more, send to upstream/Debian, upload
[08:50] <seb128> thanks
[09:08] <wmp> hello
[09:08] <wmp> i have problem with linker and boost, i cant compile program. this is linker error and my package list: http://paste.ubuntu.com/1270735/ with: http://paste.ubuntu.com/1270737/
[09:09] <cjwatson> Sweetshark: I've copied libreoffice from quantal-proposed to quantal; based on the changelog, does that mean that bug 1062448 can now be untargeted from quantal (if not closed)?
[09:51] <glatzor> tyhicks, hello
[09:51] <tyhicks> glatzor: Hi
[09:53] <glatzor> tyhicks, I run an ecryptfs protected home dir on my debian wheezy system and run into the corrupted files on disk full error
[09:53] <glatzor> tyhicks, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=+%09690071
[09:54] <glatzor> tyhicks, you mentioned that some patches to fix this problem have been applied in ubuntu. but I still get the problem with the patches applied
[09:54] <glatzor> tyhicks, are there any further patches missing?
[09:56] <tyhicks> glatzor: You applied the 3 patches mentioned at the bottom of that bug?
[09:59] <jibel> jodh, I attached a more complete stack trace to bug 1060249 if it helps. It occurs on every upgrade.
[10:00] <glatzor> tyhicks, right.
[10:00] <jodh> jibel: thanks!
[10:00] <glatzor> tyhicks, with the applied patches the command to fill up the disk failed correctly by a disk full error. I used dd if=/dev/zero of=disk-full bs=1M
[10:01] <glatzor> tyhicks, but without the patches the dd command tries to write for ever
[10:02] <tyhicks> glatzor: With the patches applied, it sounds like things are working correctly. Why do you think there is still a problem?
[10:03] <glatzor> tyhicks, because I still get files of zero size in $HOME/.Private/ that cause problems
[10:08] <tyhicks> glatzor: If you have DEBUG level kernel logging enabled, you'll still see a "Valid eCryptfs headers not found ..." message at times but then those files are properly handled now. Can you confirm that you're actually still getting zero length files and not just seeing that message in the logs?
[10:15] <tyhicks> glatzor: FYI, see https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/957843/comments/22
[10:16] <tyhicks> glatzor: Those two extra patches don't fix the problem that you're seeing, but they're needed if you carry the other three patches
[10:17] <glatzor> tyhicks, Is it ok if I add this conversation to the bug? I will try with the other two patches
[10:18] <tyhicks> glatzor: Sure
[10:18] <tyhicks> glatzor: I'm going to have to step away shortly. If you're sure that you're still seing zero length files, please file an upstream eCryptfs bug at https://bugs.launchpad.net/ecryptfs/+filebug and I'll take a look at it tomorrow.
[10:19] <tyhicks> glatzor: Please include the steps that you're doing to hit the bug and also what you're doing to verify that zero length files are still a problem after those patches are applied
[10:22] <glatzor> tyhicks, thanks!
[10:22] <tyhicks> glatzor: thank you!
[10:25] <diwic> @pilot in
[11:24] <Riddell> pitti: were you not doing to delete the -kde-xx-base packages?  I still see them
[11:31] <diwic> @pilot out
[11:49] <pitti> Riddell: hm, I thought I did
[12:02] <pitti> Riddell: hmm, WTF; I did run that long remove-packages command; digging out the shell command and trying again
[12:04] <cjwatson> pitti: do you think you could take bug 1061924?
[12:05] <pitti> Riddell: do you still have the list of packages that you make? http://paste.kde.org/562928/ timed out
[12:06] <pitti> cjwatson: hm, I guess udev is just about as wrong a package to put that in as any other?
[12:07] <cjwatson> Quite ...
[12:07] <pitti> that could be made a lot more elegant and efficient, but of course that'd need access to the actual hw
[12:08] <cjwatson> I expect it would be very short if a udev rule rather than an upstart job
[12:08] <cjwatson> (which seems to be what they're suggesting)
[12:08] <pitti> the main issue is that these crappy workarounds tend to be sticky
[12:08] <pitti> we'll never really get rid of them any more
[12:09] <cjwatson> mm, if you want to punt it I have no problem with that - it's just on the foundations rls-q-tracking list and I wasn't totally sure what to do with it
[12:10] <pitti> cjwatson: I'll ping jmleddy and see whether we can at least turn it into an udev rule on the PCI device
[12:11] <pitti> that woudl be at least much less hideous than calling dmidecode, lspci, and twice grep
[12:11] <cjwatson> Yeah
[12:24] <pitti> cjwatson: followed up on the bug, subscribed, and pinged jmleddy
[12:24] <cjwatson> thanks
[12:30] <pitti> Riddell: removed for good now; https://launchpad.net/ubuntu/+source/language-pack-kde-aa/+publishinghistory and https://launchpad.net/ubuntu/+source/language-pack-kde-zh-hant-base/+publishinghistory both confirm
[12:33] <pitti> hm, DEB_BUILD_OPTIONS=noopt seems to work for hardly any package these days :(
[12:39] <xnox> pitti: file debbugs =)
[12:40] <cjwatson> I thought that if anything noopt coverage should be improving due to dpkg-buildflags support
[12:40] <pitti> yeah, that's what I thought as well; what does seem to work is CFLAGS="-g -O0" debian/rules build
[12:40] <cjwatson> Using dpkg-buildflags is almost certainly the right fix for packages that fail to handle it
[12:40] <cjwatson> If any such packages already use dpkg-buildflags, that's worth investigating
[12:50] <spartan-11510> Hi
[12:50] <spartan-11510> i've a litlle question on packaging. When you have a java software, do you create a shell for launh the software, because you must write "java -jar archive.jar"
[12:50] <spartan-11510> ?
[12:56] <Riddell> pitti: lovely thanks
[13:03] <Sweetshark> cjwatson: untargeted, not closed for bug 1062448. I still have to investigate, if this still shows up in other more rare scenarios.
[13:06] <dupondje> telepathy-haze types can't be configured in the Online Accounts?
[13:07] <mpt> ev, could you kick off another graph update perhaps?
[13:07] <ev> mpt: sure, though I'm likely to request a deployment of the view that http://poppy-dev.local has tomorrow
[13:09] <cjwatson> Sweetshark: ok
[13:10] <cjwatson> spartan-11510: You can use something like jarwrapper; http://www.debian.org/doc/packaging-manuals/java-policy/x85.html
[13:11] <cjwatson> Or a wrapper script if you prefer, yes
[13:12] <spartan-11510> cjwatson: thank's for your advice. i'll looking for jarwrapper
[13:13] <ev> mpt: I'm getting OOM running the 12.04 variant (I'm also back populating the other graph at the same time), so I'll leave it as just 12.10 for now
[13:14] <mpt> ev, you mean from calculating the "by 12.04 standards" line?
[13:14] <cjwatson> spartan-11510: If you use javahelper, jh_exec can help with this.  See /usr/share/doc/javahelper/tutorial.html for a worked example
[13:14] <ev> oh, are you asking me to update the graph on errors.ubuntu.com or poppy-dev.local?
[13:14] <mpt> ev, e.u.c
[13:15] <ev> right
[13:15] <cjwatson> (I've not done this much myself - I just know where the tools are :-) )
[13:15] <mpt> ev, to see if all mvo's bug fixes made a dent :-)
[13:15] <ev> so then I mean that updating errors.ubuntu.com for 12.04 is using too much memory because I'm already updating poppy-dev.local for days gone past
[13:15] <mpt> ev, you do the errors.ubuntu.com calculations on your own machine?
[13:16] <ev> mpt: yes, because the cron job that would otherwise do them is broken
[13:16] <mpt> I see
[13:16] <ev> and I haven't gotten around to submitting a branch of memento to fix it
[13:19] <cjwatson> Sweetshark: That bug doesn't seem to be untargeted ... you probably need to mark the quantal task won't-fix
[13:20] <cjwatson> (with an explanation of course)
[13:26] <mpt> ev, thanks for the update ... and here I was thinking the line might dip down :-/
[13:46] <cr3> hi folks, are there projects that share common bzr ancestry upstream (lp:project) and downstream (lp:ubuntu/project)?
[13:49] <pitti> I don't know any; for that to work, you'd need to force-overwrite the auto-importer UDD branch with a custom-created branch
[13:49] <pitti> since bzr learned about "import-upstream" this should actually work
[13:49] <pitti> but I'm not aware of anyone doing that yet
[13:49] <pitti> so if someone knows a package that does that, I'm interested as well
[13:51] <cr3> pitti: after every release, I sync checkbox from upstream to downstream by overwriting just about everything except .bzr/ of course. at that point, I was thinking of pushing lp:ubuntu/checkbox to lp:checkbox and use common ancestry from that point onward, at the cost of losing some bzr history
[13:51] <xnox> cr3: no, but you can have your own downstream branch that does that.
[13:52] <xnox> cr3: for a native package, that might actually work.
[13:52] <pitti> cr3: we do use packaging branches derived from lp:project, but so far we have pushed them to e. g. ~ubuntu-desktop/indicator-applet/ubuntu instead of to lp:ubuntu/indicator-applet
[13:52] <pitti> cr3: then you can just do "bzr merge" for updating to a new upstream version, etc.
[13:53] <xnox> cr3: or you can simply request lp:ubuntu/checkbox to point to lp:checkbox. Any reason not to develop directly on the lp:ubuntu/checkbox and abandon the lp:checkbox?
[13:53] <barry> cr3: you might get on #udd and ask there.  many of us have wanted something like this for forever
[13:53] <pitti> if the packaging branch has the pristine-tar data, it should be okay to force-overwrite push it to the UDD branch
[13:53] <pitti> xnox: not if lp:checkbox doesn't have the packaging
[13:53] <pitti> upstream branches usually shouldn't have packaging
[13:53] <cr3> xnox: yes, after FF, we still want to be able to push changes that won't necessarily land in the current development release of ubuntu
[13:54] <xnox> and tags matching all versions ever uploaded in ubuntu/debian.
[13:54] <xnox> pitti: *cough* lp:ubiquity
[13:54] <pitti> xnox: that's native
[13:54] <cr3> pitti: lp:checkbox does have packaging though, how's that a problem?
[13:54] <pitti> well, I guess you could treat checkbox as native, too
[13:55] <pitti> cr3: if it's only used in Ubuntu, and you don't need another packaging branches for PPAs etc., that's fine
[13:55] <pitti> cr3: but "real" upstream projects don't, otherwise you'd have to maintain spec files, Debian, Ubuntu, and whatnot packaging all upstream
[13:56] <xnox> for me the biggest problem was the upstream-tarball when $upstream-tag !=  tarball contents and therefore need for pristine-tar tarball commit on top of the tag and then somewhere down the line I was getting fileid conflicts =/ and I gave up.
[13:56] <cr3> pitti: I think lp:checkbox is special in that it's native (has packaging) and  not native (lp:checkbox != lp:ubuntu/checkbox), which is something I'd like to cleanup at some point
[13:59] <cjwatson> cr3: grub2 is mostly done that way except that I don't have the packaging branch in lp:ubuntu/grub2, but in a nearby branch
[14:00] <cjwatson> cr3: while openssh isn't in bzr upstream, there's an import in lp:openssh and it's bzr all the way down to lp:ubuntu/openssh
[14:01] <cjwatson> so yeah, openssh is pretty much an example of the kind you're looking for
[14:01] <cr3> cjwatson: do you have a non-ubuntu branch somewhere for development that might only land in a daily ppa before going into lp:ubuntu/grub2?
[14:01] <cjwatson> No
[14:01] <cjwatson> I don't bother
[14:02] <cr3> openssh sounds more similar then, I'll have a look at that project first
[14:02] <cjwatson> For openssh, I have a separate tarball branch that I merge each upstream tag into and which corresponds to the various little differences in the released tarball
[14:02] <cjwatson> grub2 is a bit more haphazard because I haven't yet bent the Debian maintenance branch entirely to my will
[14:05] <cr3> cjwatson: I like what I'm seeing in the openssh branches, would it make much difference in my case if the debian/ directory was maintained both upstream and downstream?
[14:06] <cr3> cjwatson: my motivation for maintaining it in both places is to have upstream packages built daily
[14:06] <cjwatson> If you're doing that you're basically talking about a native package with occasional forks
[14:06] <cjwatson> I think if anything that probably simplifies it
[14:06] <cr3> cjwatson: exactly, forks usually happen from FF onwards
[14:06] <cjwatson> Ah, indeed, checkbox *is* native per its versioning
[14:07] <cjwatson> So yeah, as long as you make sure to tag lp:ubuntu/checkbox before each upload the importer probably shouldn't overwrite it
[14:07] <cr3> cjwatson: indeed, but I think I'm doing some things that aren't strictly native. not sure what though
[14:07] <cjwatson> But I would definitely start with the full upstream history rather than throwing it away in favour of the auto-imported package history
[14:07] <cjwatson> Personally
[14:07] <cjwatson> cr3: Not sure how you could be without an orig :-)
[14:09] <cjwatson> cr3: The alternative is that you could do like we do in ubiquity: only use lp:checkbox, and between FF and release occasionally have feature branches or "next" branches or similar, which you can build in a PPA if you want too
[14:09] <cr3> cjwatson: so, once quantal is released and we start with fresh packages for the next release, would that be a good time to talk to someone about replacing lp:ubuntu/checkbox with a fresh branch of lp:checkbox, so that both share the same ancestry from that point onward?
[14:09] <cjwatson> Good time yes, but you don't need to talk to anyone about it - somebody with upload privileges can bzr push --overwrite
[14:09] <cjwatson> OK, you might need to talk to your sponsor
[14:10] <cjwatson> But not an admin or anything
[14:10] <cr3> cjwatson: I think my team likes the separation between lp:checkbox and lp:ubuntu/checkbox, except for the lack of common ancestry that's making patching time consuming and error prone
[14:10] <cjwatson> Yeah
[14:10] <cjwatson> It's simpler for native packages because it's just bzr merge and you don't bother about quilt patching or similar
[14:10] <cr3> cjwatson: ok, roadmr might have upload rights by then but we'll make sure to talk with a sponsor beforehand just to be extra sure
[14:11]  * cr3 should also fill paperwork to have upload rights one of these days
[14:12] <cr3> pitti, xnox, cjwatson: thanks for all the advice, much appreciated!
[14:13] <cr3> barry: I had a python question for you: map() returns a list in python2 and an iterator in python3, so I was wondering if there was a naming convention to make it clear whether a function I write returns a list or an iterator.
[14:14] <barry> cr3: nope :)
[14:14] <cr3> barry: this could easily be mentionned in the docstring of the function, but it's annoying to have to read the docstring every time someone just wants to call something like get_foos
[14:15] <barry> cr3: you could always just treat the return as an iterator, and list()-ify it if you needed a concrete list.  it does some wasted work in py2, but is at least consistent
[14:15] <xnox> cr3: there are ~15 tags missing in lp:checkbox as compared with lp:ubuntu/checkbox probably the "post-ff-mini-forks", so for history/archive I'd push lp:ubuntu/checkbox to lp:~/ubuntu/quantal/checkbox/old-branch or something
[14:16] <xnox> cr3: although, lp:ubuntu/quantal/checkbox will be your history if you do it right after release. so ignore me.
[14:16] <cr3> barry: the problem is that I've seen this degrade into people either always returning lists (return list(map(float, results))) or always calling list() to check for the length (if list(get_foos()))
[14:17] <xnox> barry: did I not see apis .get_iter() .get_items() for such cases?!
[14:17] <cr3> xnox: right but, just for my edification, what tags might I be missing? a tag everytime the version was bumped?
[14:17] <xnox> cr3: http://paste.ubuntu.com/1271221/
[14:17] <cr3> xnox: I would be afraid of falling into hungarian notation that way :(
[14:18] <barry> xnox: well, iter(obj) would be the api for .get_iter() right?
[14:18] <xnox> cr3: '-' missing in the trunk. '+' extra tag in the trunk.
[14:18] <barry> i guess it depends on whether the api really (usually) wants concrete lists or iterators... or both :)
[14:19] <xnox> barry: well, actually to be memory efficient by default i'd do the other way round. call list() for the .get_items() such that my iter api is actually yield statements for performance.
[14:20] <barry> xnox: me too.  i think that's the rationale for python3 by default returning iterators
[14:20] <cr3> xnox: yes, some changes upstream were backported downstream into new versions. does that make sense?
[14:20] <barry> call list() if you need a list (or tuple() etc as the case may be)
[14:20] <cjwatson> I would tend to not bother with a list variant.
[14:20] <doko> infinity, https://launchpadlibrarian.net/119386939/buildlog_ubuntu-quantal-armhf.mercurial-buildpackage_0.9_FAILEDTOBUILD.txt.gz
[14:20] <xnox> barry: i've seen another pattern of returning a single item or list of items. And the code everywhere to check if not isinstance list result = [item] *sigh* to _always_ have lists...
[14:20] <doko> dpkg-shlibdeps: warning: /lib/arm-linux-gnueabihf/ld-linux.so.3 has an unexpected SONAME (ld-linux-armhf.so.3)
[14:20] <doko> dpkg-shlibdeps: error: no dependency information found for /lib/arm-linux-gnueabihf/ld-linux.so.3 (used by debian/mercurial-buildpackage/usr/bin/mercurial-tagversion)
[14:21] <barry> xnox: sigh ;)
[14:21] <cjwatson> I think I looked at that mercurial-buildpackage failure and it went into my WTF bin
[14:22] <infinity> doko: Is it shipping pre-compiled binaries?  That's the only way that can happen.
[14:24] <doko> infinity, no
[14:25] <infinity> doko: Well, it just plain can't be getting any of its own binaries linked with that SONAME if it's all built fresh.  Unless it's using a broken compiler.  Did we fail to fix one? :P
[14:25]  * infinity looks.
[14:25] <doko> infinity, using haxe
[14:25] <infinity> doko: So, yes, we failed to fix a compiler.  Fun.
[14:26] <cjwatson> With one (1) reverse-build-dep.
[14:26] <infinity> Luckily, that's literally the only thing that build-deps on it.
[14:26] <cjwatson> Niche.
[14:26] <infinity> Heh.
[14:27] <infinity> Oh, and it likely doesn't even need patching, just rebuilding.
[14:27] <infinity> I'll give that a quick whirl in a sec too.
[14:27] <infinity> doko: Thanks for the heads-up.
[14:27] <cjwatson> Where's it even getting the linker path from?
[14:28] <cjwatson> No relevant matches for ld- or ld.so anywhere ...
[14:28] <infinity> I don't find it in the source, so I'm guessing it hunts it down during build time, then hardcodes it for future linking.
[14:28] <xnox> cr3: well cherry-picked. yeah =)
[14:29] <infinity> I didn't bother looking too hard, cause I suspect a rebuild will magically fix it.  We'll see.
[14:29] <cjwatson> It might actually be in neko instead.
[14:29] <infinity> Oh, is haxe just a frontend to evil?
[14:30] <infinity> Indeed, it may be.
[14:30] <infinity> dpkg-source: info: applying debian-changes-1.8.1-6ubuntu1
[14:30] <infinity> ^-- We're pro.
[14:30] <cjwatson> Not that I see a linker path in neko either ...
[14:31] <infinity> No, but neko does seem like a more likely candidate for doing real work.
[14:31] <infinity> I'll play with both.
[14:31] <cjwatson> Yeah, maybe it does some godawful build-time thing to work out the linker path.
[15:01] <cr3> barry: is calling list() on something that is already a list a noop until it is modified, copy-on-write, or is a completely new list always created?
[15:01] <barry> cr3: a completely new list object is created
[15:02] <barry> >>> x = list((1, 2, 3))
[15:02] <barry> >>> y = list(x)
[15:02] <barry> >>> x is y
[15:02] <barry> False
[15:02] <barry>
[15:03] <cr3> barry: thanks! I should've tried that myself :)
[15:04] <xnox> barry: hm... if only this would happen to kwargs & dictionaries passed to functions.... so confusing. but I am now used to "abusing" that for fun and profit =)
[15:05] <barry> xnox: right, that's kind of a different effect.  default arguments are evaluated at def time
[15:38] <iainfarrell> kthxbai
[15:40] <slangasek> mvo: ping re bug #1016643
[15:54] <mvo> slangasek: about if that needs a apt-key patch as well? I would appreciate double checking the diff I put in there and welcome feedabck from https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1016643/comments/12 - I would love to be able to disable it in adv as well
[16:03] <slangasek> mvo: right, the question is whether more is needed than the software-properties fix.  I'm coming to this a little cold, I mostly just know that it's on our quantal bug list - how does 'apt-key adv' relate to software-properties?
[16:03] <slangasek> ah, that's how s-p invokes apt-key
[16:04] <slangasek> mvo: so what's insecure about the current behavior?
[16:07] <bdmurray> cjwatson: so using your test on quantal I received the following message from apt 'W: Some index files failed to download. They have been ignored, or old ones used instead.' and then I ran 'chdist apt-get captive-portal update' again but without the proxy and it succeeded
[16:09] <cjwatson> bdmurray: That sounds basically awesome
[16:10] <bdmurray> I'll do some looking at bug reports to see if I can find any recent incidents of the bug too
[16:11] <stokachu> infinity: http://paste.ubuntu.com/1271408/
[16:33] <ev> pitti: finally able to reproduce it on one of the retracer boxes. It's gdb hitting a corrupt stack, as far as I can tell
[16:33] <ev> http://people.canonical.com/~evand/tmp/f269837a-116f-11e2-9d07-2c768aafd08c.crash
[16:34] <ev> pitti: a retrace on my local machine produces http://paste.ubuntu.com/1271445/
[16:34] <ev> but on the retracer we get ?^VQ^H just below __PRETTY_FUNCTION__
[16:34] <pitti> ev: oh, so that works?
[16:34] <pitti> ev: is the errors.u.c. retracer running under LANG=C?
[16:35] <ev> I tried that locally - no such luck (LANG=C)
[16:35] <ev> I even built a precise chroot
[16:35] <ev> but I can only trigger it on the retracers
[16:35] <ev> it's definitely the gdb output though
[16:36] <ev> the quantal version of gdb has a better message:
[16:37] <pitti> ev: I don't see broken strings in that .crash file, I guess that's why it didn't trigger
[16:37] <pitti> ev: anyway, I'll play around with that tomorrow morning, I'm about to run out for today
[16:39] <ev> pitti: "Cannot access memory at address 0x100000007"
[16:39] <ev> pitti: sure thing - thanks!
[16:39] <ev> (which is why I was led to believe it might be a combination of running precise and something else that causes it to surface on the retracer box)
[16:40] <ev> that message appearing just below __PRETTY_FUNCTION__ that is
[16:43] <pitti> good night everyone!
[16:46] <ev> g'night pitti
[16:46] <ion> nighte
[16:47] <ev> mpt: october 5th was the first day we had the separate counters for each problem type
[16:47] <ev> and that landed part way through the day
[16:47] <ev> so I'll just need to go back and redo that day
[17:45] <darkcrow666> Hi !
[17:46] <darkcrow666> What do you have in mind when you still use compiz ?
[17:56] <bdmurray> seb128: could you have a look at bug 1048059?
[18:09] <Kano> hi, where is that gcdx64.efi file mentioned in the grub2 changelog?
[18:31] <Kano> found it, most likely you lost
[18:31] <Kano> chain can load any efi binary
[18:33] <Kano> where is shim
[18:34] <Kano> the signed version of course ;)
[18:34] <stgraber> Kano: apt-get install shim-signed
[18:35] <Kano> good, i guess i have to use kvm to verify what i think, but most likely your system is broken
[18:45] <slangasek> Kano: my understanding is that the load_image call goes through the SB verification chain
[18:46] <Kano> why would you use the linux call?
[18:46] <Kano> i have got no interest in using it. but chainloader
[18:46] <slangasek> I didn't say anything about linux
[18:47] <Kano> ok, why did you patch efilinux in it?
[18:47] <slangasek> sorry, what are you talking about?
[18:47] <slangasek> you were asking about shim and gcdx64.efi
[18:47] <slangasek> that's nothing to do with efilinux
[18:47] <Kano> yes, can that includes chain(loader)
[18:48] <Kano> with chainloader you can start efi binaries on an efi system
[18:48] <slangasek> yes, and chain uses load_image, and load_image fails if the image doesn't verify
[18:49] <Kano> verify against what? do you check now signatures for the kernel?
[18:50] <Kano> at least you could not verify any initrd
[18:52] <slangasek> Kano: if you find an exploit that allows unsigned code to be run in BootServices, please let us know and we'll fix it
[18:53] <Kano> would not help anything if it is a binary that is out now
[18:53] <slangasek> of course it would
[18:54] <Kano> btw, in the ubuntu + debian grub 2.00-7 is a stupid bug
[18:54] <Kano> or better 2 bugs
[18:54] <Kano> http://kanotix.com/files/fix/efi/grub-2.00-7-debian-bugs.txt
[18:55] <Kano> one thing is, it calls efibootmgr even if grub-pc is installed but the system is booted via efi (not necessaryly via grub)
[18:55] <slangasek> Kano: we have a bug tracking system, please report these there
[18:55] <Kano> the other thing is, the use of -w is not needed and absolutely critical when you use a hd with mbr
[18:55] <Kano> it kills the serial
[18:56] <Kano> you can use efi partition with mbr hd as well, it just needs to be a primary one
[18:57] <Kano> with those 2 bugs combined you get directly a system that only boots grub, no win, no other bootloader you specified because the serial of hd is used inside the nvram
[18:57] <Kano> and inside win bootloaders
[18:58] <Kano> as soon as you install that grub
[18:59] <Kano> bbl
[19:37] <seb128> bdmurray, hey, I will have a look, thanks for pointing it
[19:39] <bdmurray> seb128: thanks I've an upgraded system where /media/$username/ doesn't exist if that is any hlep
[19:40] <seb128> bdmurray, well, that's not an issue, they should be created by udisk when needed
[19:40] <seb128> bdmurray, it's rather a pitti's topic (he maintains the udisk stack) but I will check the bug details and see with him
[20:09] <jibel> SpamapS, is bug 1021471 fixed for you with kernel 3.5.0-17.28 ?
[20:09] <SpamapS> jibel: I haven't had a chance to fully test it yet
[20:10] <jibel> I still get it with lxc
[20:10] <SpamapS> jibel: hard because I have to test with b43 instead of wl which is.. less than reliable ;)
[20:10] <SpamapS> jibel: do you have a wl based network connection?
[20:10] <jibel> SpamapS, no, I've a wired connection
[20:11] <SpamapS> jibel: and does refcount == 2 ?
[20:11] <jibel> driver is an r8169 exactly, refcount = 1
[20:11] <SpamapS> jibel: its possible other drivers than wl have the problem. :-/
[20:12] <SpamapS> jibel: only way to tell is to run 3.6 and make sure the problem is gone there
[20:12] <SpamapS> or at least, that is one way
[20:12] <SpamapS> anyway, need to get lunch... starting to hear rumbles
[20:13] <jibel> I'll try on another machine, but on my main desktop I can reproduce it very reliably just by creating an lxc container and shutting it down with poweroff
[20:13] <jibel> SpamapS, ack, I'll try 3.6
[21:10] <slangasek> smoser: hey, so is mountall looking happy for you now?  I'm feeling a little disoriented with no mountall bugs from you in my queue and fear that something is wrong ;)
[21:12] <Daviey> hah
[21:13] <Daviey> slangasek: He understood that for any change he wanted, you mandated a fork removal. :)
[21:13] <slangasek> heh
[21:16] <smoser> i actually havne't tested your latest.
[21:16] <smoser> let me check.
[21:18] <slangasek> heh, ok :)
[21:26] <ScottK> Not testing is the easiest way not to get bugs.
[21:27] <mlankhorst> Testing is the easiest way to get bugs?
[21:32] <ScottK> No, convincing someone else to test is often easier than testing yourself.
[22:08] <Sweetshark> anyone with glib knowledge around?
[23:25] <geofft> Is pesign / sbsign / something Debian-packaged already perchance?
[23:26] <geofft> (I noticed shim was packaged recently.) The packaging is probably trivial, but it'd be nicer to just use Ubuntu's :)
[23:26] <cjwatson> geofft: sbsigntool, yes
[23:27] <geofft> aha, singular, unlike the thing on OBS. Thanks!
[23:29] <cjwatson> the upstream name is singular :)
[23:47] <psusi> cjwatson, you think porting partman to parted3 will happen for 13.04? ;)
[23:47] <cjwatson> psusi: dunno, I guess we should get round to it
[23:47] <cjwatson> but now is the worst time to ask
[23:49] <psusi> it seems I'm going to become co-maintainer of parted
[23:49] <cjwatson> Then perhaps you might like to help with porting partman :)
[23:50] <cjwatson> Not sure where I put that preliminary patch


[00:14] <rww> randomly, I note that lucid goes EOL at the end of this month
[00:14] <rww> prepare your party hats
[00:15] <k1l> end of april. or was it end of march already?
[00:15] <rww> it's april in UTC now :P
[00:15] <rww> Wed Apr  1 00:15:54 UTC 2015
[00:16] <k1l> its already 2:15 in here :)
[00:28] <phunyguy> is it a specific day? or just April Fool's day?
[00:29] <bazhang> the day the music died
[00:29] <rww> phunyguy: April 30th
[00:30] <rww> Today is Sweetmorn, the 18th day of Discord in the YOLD 3181
[00:30] <bazhang> I read that as YOLO
[00:36] <phunyguy> ahh I misunterstood
[00:37] <Unit193> The Moon is Waxing Gibbous (89% of Full)
[00:43] <hggdh> "waxing gibbous" sounds like some sort of illness ("I am sorry to say, you have waxing gibbous", and pandemonium starts)
[00:45] <hggdh> and then you know somebody will be sitting shiva for you very soon...
[09:28] <TrojanFon> Hi i have problem with banned static ip
[09:28] <TrojanFon> Anyone can help me ?
[11:44] <k1l_> bazhang: duckey is the one going rounds with the homosexual bash script thingy trying to stirr up something
[11:45] <bazhang> k1l_, he was banned in ##linux for very good reason, I just scrolled up there
[11:45] <bazhang> offtopic ops should have a heads up for him
[11:46] <k1l_> i can image just from the way he behaved in #u
[11:46] <k1l_> *imagine
[11:46] <bazhang> yep
[11:48] <bazhang> zacwalls , very bad news
[11:49] <k1l_> yeah, that name rings the bells
[11:50] <chu> Thanks bazhang
[11:51] <bazhang> gesundheit!
[11:51] <bazhang> err welcome!
[16:16] <k1l_> hi YungPete, how can we help you?
[16:18] <YungPete> I was trying to contact dpm about the ubuntu translation-s meeting scheduled tomorrow at 4pm UTC. Is this happening ? 'cos I can't contact him ?
[16:19] <k1l_> this is the channel for the ubuntu core channel ops team. maybe you better ask in the translation team channel
[16:20] <k1l_> #ubuntu-translators  should be the channel
[16:21] <YungPete> He's not answering his pings .. You should know whether or ot , this, http://imgur.com/QGSSYMH is confirmed or naye ?
[16:22] <rww> Ubuntu's IRC team doesn't manage #ubuntu-meeting's schedule.
[16:23] <YungPete> Well I dont know if this is bull or not, just sayin'
[16:24] <Pici> YungPete: He was just talking in #ubuntu-community-team about 2 hours ago, and his idle time is about that long, likely he is off doing other things.
[16:25] <genii> Hm, fridge has the meeting listed for 3pm UTC not 4pm
[16:25] <YungPete> So how should I inquire as o; if this is genuine ?
[16:25] <Pici> Send him a PM and wait.
[16:26] <YungPete> k
[16:26] <YungPete> leaves
[17:50]  * elky facepalms
 Any1 need help?


[15:58] <hallyn> o/
[16:00] <adam_g> o/
[16:00] <zul> heylo
[16:00] <smb> \o
[16:00] <arosales> Hello
[16:01] <hallyn> howdie all
[16:01] <jimbaker> hi
[16:01] <hallyn> #startmeeting Ubuntu server meeting
[16:01] <meetingology> Meeting started Tue Nov 20 16:01:27 2012 UTC.  The chair is hallyn. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:01] <hallyn> #topic Review ACTION points from previous meeting
[16:01] <hallyn> none on the agenda
[16:01] <hallyn> #topic Raring Development
[16:02] <hallyn> does someone want to handle the release bugs?
[16:02] <hallyn> #link Raring Development
[16:02] <hallyn> hm
[16:02] <hallyn> #link http://reqorts.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:02] <jamespage> o/
[16:02] <smoser> o/
[16:03] <hallyn> that's not updated for raring, is it relevant?
[16:03] <Daviey> hallyn: Action me to fix it :)
[16:03] <hallyn> #action Daviey to remove release bugs item from agenda
[16:03] <meetingology> ACTION: Daviey to remove release bugs item from agenda
[16:03] <Daviey> (fix the report)
[16:03] <hallyn> oh
[16:03] <hallyn> #action Daviey  to fix the release bugs report
[16:03] <meetingology> ACTION: Daviey  to fix the release bugs report
[16:04] <hallyn> ok, so on to http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server i guess
[16:04] <hallyn> Daviey: do you want to drive that?
[16:04] <Daviey> hallyn: I'm sorry, i cannot.
[16:05] <Daviey> hallyn: (I'm got one foot in irc right now, but my heart on the phone)
[16:05] <hallyn> ok, waht i see is a whole lot of unassigned high priority bugs...
[16:05] <hallyn> bug 1064224 being critical
[16:06] <hallyn> ah, roaxsoax isnt here but seems to be handling it
[16:06] <hallyn> jamespage: you marked it critical, any comment on it, or is it progressing ok?
[16:07] <hallyn> ok, let me just turn this into an action for everyone to go through that list.  bc i see at leaset one that i need to deal with (i.e. remove)
[16:07] <jamespage> hallyn, with regards to the maas bugs; I went through and aligned them to maas upstream in importance
[16:07] <hallyn> #action everyone look through http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server
[16:07] <meetingology> ACTION: everyone look through http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server
[16:07] <jamespage> most are inprogress or committed - so its OK
[16:07] <hallyn> jamespage: ok, thanks
[16:07] <hallyn> arosales: do you want to go through blueprints?
[16:08] <arosales> hallyn: hello :-)
[16:08] <hallyn> howdie :)
[16:08] <arosales> I think the main thing jamespage, smoser, and Daviey were working on was specs in blueprints
[16:08] <arosales> how is that going?
[16:09] <smoser> we made an initial pass through them last week.
[16:09] <Daviey> (Rest still to finish)
[16:09] <smoser> they generally look in good shape (other than the ones I did).
[16:09] <smoser> we made comments in the whiteboard of ones that needed more fleshing out.
[16:10] <arosales> smoser: any to bring up here?
[16:10] <smoser> if you have a blueprint that you are wondering about the status of, please ping jamespage or Daviey
[16:10] <hallyn> does anyone have questions about their blueprints they want to ask here?
[16:10] <smoser> as they are not taking long hiatus for turkey consumption shortly like I am.
[16:11] <jamespage> ta smoser :-)
[16:11] <hallyn> thanks guys, moving on,
[16:11] <hallyn> #topic Ubuntu Server Team Events
[16:11] <hallyn> anything coming up?
[16:11] <hallyn> (3,
[16:11] <hallyn> 2,
[16:11] <smoser> https://reinvent.awsevents.com/ is next week.
[16:11] <hallyn> oh yeah i keep getting emails about that
[16:11] <smoser> jcastro, m_3, smoser, utlemming.
[16:11] <smoser> will be there.
[16:12] <hallyn> that's a big group
[16:12] <hallyn> can we watch an online stream (and giggle)?
[16:13] <hallyn> eh i'll have to look for one, sounds aweseome.  moving on,
[16:13] <hallyn> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:13] <hallyn> hggdh: around?
[16:13] <hallyn> seems not, moving on,
[16:13] <hallyn> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:13] <hallyn> hi smb
[16:13]  * smb takes break
[16:13] <smb> err breath
[16:14] <smb> I went through the review of Xen that adds back qemu-dm with apw. We found a few documentation/packaging improvements and I think could be uploaded soonish. Though probably need to kick out the previous upload still in raring-proposed. Which actually brings up the next topic: Daviey, I think apw talked to you already about the dependency breakage for xen-hypervisor-4.1-<arch> for some nova packages.
[16:14] <smb> One option there may be to depend on the xen-system-<arch> meta-packages which are produced since xen-4.1.3 (though those pull in xen-utils as well).
[16:14] <smb> Otherwise bug 1078926 seems to have some upstream fix. Though its not yet completely clear whether it potentially could change a bit before finally arriving there. I have added some links to test kernels to the report.
[16:14] <smb> ..
[16:15] <hallyn> smb: Daviey is on the phone, let's give him another 30 secs to see the ping
[16:15] <smoser> smb, thanks for your work there.
[16:15] <hallyn> zul: ^ any comment on the xen packaging suggestion?
[16:15] <smoser> on that bug. you were able to reproduce locally ?
[16:15] <smb> smoser, Merely prodding upstream
[16:15] <smb> smb, Yes I was
[16:15] <smb> Actually even with xen 4.2 host
[16:15] <hallyn> smb: do i understand right that the kernel in quantal-proposed should have fixes for all the network namespace refcount bugs?
[16:16] <zul> i dont have a comment yet
[16:16] <hallyn> zul: np, thanks, just checking
[16:16] <smb> hallyn, I think the second fix is still pending to move into updates
[16:16] <hallyn> right, but fix is in proposed at least - phew
[16:17] <hallyn> ok, pls catch Daviey later :)  moving on,
[16:17] <smb> hallyn, Yes it should be
[16:17] <hallyn> thanks smb
[16:17] <hallyn> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:17] <hallyn> rbasak: any news?
[16:17] <rbasak> Nothing to report. Any questions for me?
[16:18] <hallyn> sounds like no,
[16:18] <hallyn> thanks, rbasak.  moving on,
[16:18] <hallyn> #topic Open Discussion
[16:19] <hallyn> we're saving our chatting for turkey day?
[16:19] <hallyn> ok,
[16:19] <hallyn> #topic Announce next meeting date and time
[16:20] <hallyn> next meeting will be next Tuesday, Nov 27, at 16:00 UTC
[16:20] <hallyn> thanks everyone
[16:20] <hallyn> #endmeeting
[16:20] <meetingology> Meeting ended Tue Nov 20 16:20:20 2012 UTC.
[16:20] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-11-20-16.01.moin.txt
[16:20] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-11-20-16.01.html
[16:20] <jamespage> thanks hallyn
[16:20] <zul> thats was quick
[16:21] <zul> hallyn:  turkey was last month try to keep up
[16:21] <arosales> thanks hallyn
[17:00] <meetingology> Meeting started Tue Nov 20 17:00:29 2012 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/raring
[17:00] <herton> o/
[17:00] <apw> o/
[17:00] <ppisati> o/
[17:00] <sforshee> o/
[17:00] <ogasawara> o/
[17:00] <sconklin> o/
[17:01] <smb> \o
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> nothing to report this week.
[17:01] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-raring/canonical-kernel-distro-team-ubuntu-13.04-month-2.html
[17:01] <ogasawara> || apw         || hardware-r-kernel-config-review       || 12 work items ||
[17:01] <ogasawara> ||             || hardware-r-kernel-delta-review        ||  2 work items ||
[17:01] <ogasawara> || cking       || hardware-r-kernel-config-review       ||  1 work item  ||
[17:01] <ogasawara> || ogasawara   || hardware-r-kernel-config-review       ||  4 work items ||
[17:01] <ogasawara> ||             || hardware-r-arm-power-measurement      ||  2 work items ||
[17:02] <ogasawara> || ppisati     || hardware-r-kernel-config-review       ||  1 work item  ||
[17:02] <ogasawara> ||             || hardware-r-kernel-version-and-flavors ||  1 work item  ||
[17:02] <ogasawara> || sconklin    || hardware-r-arm-power-measurement      ||  3 work items ||
[17:02] <ogasawara> || smb         || hardware-r-kernel-delta-review        ||  1 work item  ||
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: Raring Development Kernel (ogasawara)
[17:02] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Raring
[17:02] <ogasawara> We have recently rebased the raring kernel to upstream v3.7-rc6.  I plan
[17:02] <ogasawara> to prep an upload by EOD.
[17:02] <ogasawara> Important upcoming dates:
[17:02] <ogasawara>  * Tues Dec 18 - 13.04 Month 2 Milestone - (~4 weeks)
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: CVE's (henrix)
[17:03] <sconklin> == 2012-11-20 (weekly) ==
[17:03] <sconklin> Currently we have 28 CVEs on our radar, with 2 CVE retired this week.
[17:03] <sconklin> See the CVE matrix for the current list:
[17:03] <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <sconklin> Overall the backlog has decreased slightly this week:
[17:03] <sconklin> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:03] <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:03] <sconklin> ..
[17:03] <sconklin> (for henrix)
[17:03] <sconklin> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Quantal/Precise/Oneiric/Lucid/Hardy (bjf/herton/henrix)
[17:03] <herton> Here is the status for the main kernels, until today (November 20):
[17:03] <herton> * Hardy - In Testing; 1 CVE; (1 commit)
[17:03] <herton> * Lucid - In Testing; 1 CVE; (2 commits)
[17:03] <herton> * Oneiric - Previous cycle released, except for ti-omap4 derivative,
[17:03] <herton>             waiting on regression-testing.
[17:03] <herton>           - In Testing (current cycle); 2 CVEs; 6 upstream updates;
[17:03] <herton>             3 SRUs; 200 commits. Derivatives: lts-backport also on
[17:03] <herton>             testing, ti-omap4 waiting on previous cycle update to be
[17:03] <herton>             uploaded
[17:03] <herton> * Precise - Previous cycle released, except for ti-omap4/armadaxp
[17:03] <herton>             derivatives, waiting on regression-testing.
[17:03] <herton>           - In Verification (current cycle); 1 CVE; 2 upstream updates;
[17:03] <herton>             8 SRUs; 253 commits. Derivatives: ti-omap4/armadaxp waiting
[17:03] <herton>             on previous cycle update, lowlatency not started on yet.
[17:03] <herton> * Quantal - In Verification; 2 CVEs; 7 SRUs; 11 commits.
[17:03] <herton>             Derivatives: lts-quantal also in verification. ti-omap4
[17:03] <herton>             waiting copy to proposed; lowlatency not started on yet;
[17:03] <herton>             armadaxp not started on yet, and waiting on previous cycle
[17:04] <herton>             in regression-testing.
[17:04] <herton> Current opened tracking bugs details:
[17:04] <herton> * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:04] <herton> For SRUs, SRU report is a good source of information:
[17:04] <herton> * http://people.canonical.com/~kernel/reports/sru-report.html
[17:04] <herton> Future stable cadence cycles:
[17:04] <herton> * https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock
[17:04] <herton> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:05] <jsalisbury> Thanks everyone
[17:05] <jsalisbury> #endmeeting
[17:05] <meetingology> Meeting ended Tue Nov 20 17:05:03 2012 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-11-20-17.00.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-11-20-17.00.html
[20:00] <czajkowski> aloha
[20:00] <czajkowski> huats: itnet7 SergioMeneses
[20:00] <itnet7> Hey there!!
[20:00] <itnet7> Uhm....
[20:00] <TadeasParik> hi
[20:01] <czajkowski> hmm we do ned the others
[20:01] <czajkowski> lets just give it a few mins shall we
[20:01] <SergioMeneses> czajkowski, here!
[20:02] <czajkowski> shall we start
[20:03] <czajkowski> #startmeeting
[20:03] <meetingology> Meeting started Tue Nov 20 20:03:07 2012 UTC.  The chair is czajkowski. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[20:03] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[20:03] <czajkowski> Aloha and welcome to the LoCo Council meeting
[20:03] <czajkowski> #link https://wiki.ubuntu.com/LoCoCouncil/Agenda
[20:03] <czajkowski> todays agenda we'll work from the top down for teams
[20:04] <czajkowski> #topic Asturian LoCo reapproval
[20:04] <czajkowski> #link https://wiki.ubuntu.com/AsturianTeam/ReApprovalApplication2012
[20:04] <ivarela> Hi to all. Here, Asturian Team.
[20:05] <czajkowski> ivarela: hi there
[20:05] <ivarela> hi
[20:05] <czajkowski> care to tell us about your loco and how things are going on
[20:05] <SergioMeneses> ivarela, hello!
[20:06] <ivarela> First of all, I'm sorry for my english level... I'd like to speak in another language, because it's difficult for me, but... i'll try it. ;)
[20:06] <czajkowski>  kce
[20:06] <itnet7> Thanks ivarela
[20:06] <czajkowski> ivarela: no worries take your time
[20:06] <czajkowski> lovely wiki page
[20:07] <SergioMeneses> ivarela, take your time ;)
[20:07] <czajkowski> and if there is anyone else here who can help ivarela please just say so
[20:07] <ivarela> As you can see in our ticket, we are a small group...
[20:07] <SergioMeneses> I really like the edubuntu video
[20:07] <SergioMeneses> nice
[20:07] <ivarela> we're asturians, a small territory placed in Spain.
[20:08] <highvoltage> SergioMeneses: which video is that?
[20:08] <ivarela> We began to spreading ubuntu at schools some time ago. Ubuntu it's a very good tool for our language.
[20:08] <czajkowski> nods
[20:08] <SergioMeneses> highvoltage, - http://youtu.be/rqOZ16kCuqw
[20:08] <ivarela> edubuntu is the educational job we do with scholars students.
[20:09] <czajkowski> great work
[20:09] <ivarela> We try to inicializate them in PC's with Free software.
[20:09] <SergioMeneses> ivarela, very interesting
[20:09] <highvoltage> awesome, will share through edubuntu social channels, and sorry for interrupting, I didn't realise this was -meeting
[20:09] <czajkowski> huats: no worries :)
[20:09] <czajkowski> highvoltage: no worries
[20:09] <SergioMeneses> and I see Marcos Costales belongs to ubuntu-ast
[20:10] <ivarela> do you know Costales ? :D
[20:10] <czajkowski> ivarela: great work, so how are things done in the loco ? does everyone help?
[20:10] <SergioMeneses> ivarela, yes... he is a amazing ubuntu member
[20:10] <ivarela> Costales is a well friend of mine.
[20:11] <ivarela> People use to work at LoCo, but unfortunately, not all the people has the same free time, so we try to involve all people in the group
[20:11] <ivarela> This year we had less activity than last year. We tried to open many doors, but we've had less luck.
[20:12] <czajkowski> nods
[20:12] <czajkowski> it does happen
[20:12] <ivarela> For example... We had prepared a summer course with UABRA (Summer University), but in the end we could not do it because of problems with the days
[20:12] <czajkowski> it's hard but at least youre still going and every bit does help and I love the video well done
[20:12] <SergioMeneses> ivarela, maybe if you work with the universities, colleges....
[20:12] <huats> Sorry I am here
[20:13] <ivarela> what you see in the video it was a very good experience for me. It was the first time that children worked with Ubuntu, and the first time that
[20:13] <czajkowski> ivarela: is there anything the loco council can do to help ?
[20:13] <ivarela> the worked in a O.S in their language.
[20:14] <ivarela> czajkowski, do you mean now, here?
[20:14] <czajkowski> well in general
[20:14] <ivarela> in this chat?
[20:14] <czajkowski> ivarela: if you want and it can be disussed in public sure
[20:14] <czajkowski> or you need help after te meeting
[20:15] <ivarela> hmmm I'm sorry. SergioMeneses do you speak spanish?
[20:15] <ivarela> I think I need a help in this moment to understand the question... :S
[20:15] <SergioMeneses> ivarela, yes I do, why?
[20:15] <ivarela> no entiendo la pregunta de czajkowski .. :S
[20:16] <SergioMeneses> ivarela, czajkowski te pregunta si necesitan alguna ayuda por parte del loco council
[20:16] <ayoze> ivarela: czajkowski pregunta si el "loco council" puede hacer algo para ayudar
[20:17] <ivarela> oh, no... we have the people, and we have the tools to do it better, but we need more illusion.
[20:17] <czajkowski> ok well I think we'll be blogging your video after this
[20:17] <SergioMeneses> czajkowski, +1
[20:17] <czajkowski> and see if we can raise the awareness
[20:17] <czajkowski> #voters SergioMeneses czajkowski itnet7 huats
[20:17] <meetingology> Current voters: SergioMeneses czajkowski huats itnet7
[20:18] <ivarela> it would be great :D
[20:18] <czajkowski> #vote please vote on the re approval of the Asturian LoCo
[20:18] <meetingology> Please vote on: please vote on the re approval of the Asturian LoCo
[20:18] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[20:18] <itnet7> +1 Good Job, Thanks for all of the excellent teamwork!!
[20:18] <meetingology> +1 Good Job, Thanks for all of the excellent teamwork!! received from itnet7
[20:18] <czajkowski> +1 amazing work folks!
[20:18] <meetingology> +1 amazing work folks! received from czajkowski
[20:18] <SergioMeneses> +1
[20:18] <meetingology> +1 received from SergioMeneses
[20:18] <ivarela> http://tinyurl.com/btunccx
[20:18] <ivarela> :D
[20:19]  * czajkowski tickles huats
[20:19] <SergioMeneses> ivarela, I wanna know if you have some documentation about your migration process
[20:19] <SergioMeneses> maybe I can help spreading those ideas here or creating a project similar
[20:19] <ivarela> migration process?
[20:20] <huats> +1
[20:20] <meetingology> +1 received from huats
[20:20] <huats> too
[20:20] <SergioMeneses> ivarela, yes with edubuntu
[20:20] <huats> sorry I just need to backlog
[20:20] <ivarela> SergioMeneses,  can I speak with you later (in spanish, :S)
[20:20] <huats> that is a great work really
[20:20] <SergioMeneses> ivarela, sure
[20:20] <czajkowski> #endvote
[20:20] <meetingology> Voting ended on: please vote on the re approval of the Asturian LoCo
[20:20] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[20:20] <meetingology> Motion carried
[20:20] <czajkowski> well done!
[20:20] <itnet7> Congratulations!!
[20:21] <ayoze> ivarela: te pregunta si hay alguna documentación sobre el proceso de migración a edubuntu en las escuelas.
[20:21] <SergioMeneses> congratz ubuntu-ast!!!
[20:21] <ivarela> Thank you!
[20:21] <czajkowski> #action czajkowski update Launchpad with the team information
[20:21] <meetingology> ACTION: czajkowski update Launchpad with the team information
[20:21] <czajkowski> #topic Czech LoCo Re Approval
[20:22] <czajkowski> #link https://wiki.ubuntu.com/CzechTeam/ReApprovalApplication2012
[20:22] <czajkowski> who's here from the czech Loco ?
[20:22] <vojtech_t> hi from the Czech rep.
[20:22] <TadeasParik> czajkowski, hello!
[20:22] <czajkowski> hey there folks thanks for coming
[20:22] <SergioMeneses> hello Czech LoCo !!!
[20:22] <czajkowski> lovely pictures on the applicateion
[20:22] <czajkowski> *application
[20:22] <vojtech_t> thanks
[20:23] <itnet7> Hey there!! TadeasParik, vojtech_t, and team!!
[20:23] <itnet7> They were very nice!
[20:23] <czajkowski> vojtech_t: so tell us about your loco
[20:23] <czajkowski> and the work you guys do
[20:23] <SergioMeneses> it is a great application, congratz
[20:24] <vojtech_t> we are quite small community but we try to do our best, i think we are doing well with localization and community support and also with events organization -- you can see photos from our release parties (we started them in 2011) and also from other events/conferences we took part
[20:25] <itnet7> Very good activity!
[20:25] <vojtech_t> we would like to focus on working with people (we always need more volunteers and acitve members) and also with advocacy (we are trying but it's not as good as we would like to be)
[20:26] <czajkowski> nods
[20:26] <czajkowski> but at leas tyou se ethis and are working towards making this better
[20:26] <czajkowski> so that's good to see
[20:27] <czajkowski> vojtech_t: can you tell us about how you started the materials part of your loco
[20:27] <czajkowski> I see this as a very good thing to be doing in your loco and I know others in different teams have tried similar
[20:27] <vojtech_t> czajkowski: materials?
[20:28] <czajkowski> Recently we started to produce some Ubuntu marketing materials for Ubuntu users in Czechia. Currently we have badges, car stickers and "powered by" stickers for laptopts/computers.
[20:28] <czajkowski> ^^
[20:28] <SergioMeneses> I was thinking to ask about it... they have a ubuntu book in czech
[20:28] <SergioMeneses> very amazing
[20:28] <vojtech_t> oh yes -- many our members asked us for some stickers they could put on their computer etc. and we just thought it's good idea
[20:29] <czajkowski> vojtech_t: would be nice to share them  on http://spreadubuntu.org/
[20:29] <vojtech_t> we have a nonprofit organization and some money so it is not so difficult to make some of those
[20:29] <huats> I really like the book ! looks very promising
[20:30] <vojtech_t> spreadubuntu, yes but for now wee have only buttons (just ubuntu logo, no special graphics) and "standard" power by stickers
[20:30] <czajkowski> it's still great to see
[20:31] <czajkowski> so one thing I'm curuous about is what do you plan fo the future any events, I notice the http://loco.ubuntu.com/teams/ubuntu-cz/events/history lists past events but nothing in the future
[20:31] <vojtech_t> huats: yes the book was great, but the last one is for Ubuntu 10.10 -- we really would like to produce new version, but publishing house is no longer interested and we don't have enough money to produce them on our own
[20:32] <huats> vojtech_t: may be you can try to find a foreign publishing company
[20:32] <huats> I don't know if it is possible
[20:33] <vojtech_t> czajkowski: we don't use loco.ubuntu.com -- we put our events there, but our primary "channel" for events is our forum
[20:33] <itnet7> vojtech_t: perhaps get some donation links on the project pages, and blog about it
[20:33] <czajkowski> vojtech_t: can we encourage you to maybe add them there please
[20:33] <itnet7> for the publishing costs
[20:33] <czajkowski> as that is where all users are directed to to find out about teams
[20:34] <czajkowski> #topic please vote on the reapproval of the Czech LoCo
[20:34] <vojtech_t> czajkowski: ok, we will add all our events on loco.ubuntu.com
[20:34] <itnet7> vojtech_t: you don't have to use LTP to track attending, you can just add the registration url
[20:35] <czajkowski> +1
[20:35] <SergioMeneses> +1
[20:35] <czajkowski> bah
[20:35] <czajkowski> #topic please vote on the reapproval of the Czech LoCo
[20:35] <czajkowski> #topic please vote on the reapproval of the Czech LoCo
[20:35] <SergioMeneses> jaja
[20:35] <czajkowski> #vote please vote on the reapproval of the Czech LoCo
[20:35] <meetingology> Please vote on: please vote on the reapproval of the Czech LoCo
[20:35] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[20:35] <czajkowski> +1
[20:35] <meetingology> +1 received from czajkowski
[20:35] <SergioMeneses> +1
[20:35] <meetingology> +1 received from SergioMeneses
[20:35] <itnet7> +1, really nice work!!!
[20:35] <meetingology> +1, really nice work!!! received from itnet7
[20:35]  * czajkowski shouldnt have dinner and chair at the same time!
[20:35] <huats> +1
[20:35] <meetingology> +1 received from huats
[20:36] <czajkowski> #endvote
[20:36] <meetingology> Voting ended on: please vote on the reapproval of the Czech LoCo
[20:36] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[20:36] <meetingology> Motion carried
[20:36] <huats> really nice job
[20:36] <czajkowski> well done folks!
[20:36] <vojtech_t> thanks
[20:36] <TadeasParik> thanks!
[20:36] <SergioMeneses> congratulations guys!
[20:36] <SergioMeneses> keep working
[20:36] <huats> congrats
[20:36] <czajkowski> #action update Launchpad with Czech expirary date
[20:36] <meetingology> ACTION: update Launchpad with Czech expirary date
[20:36] <czajkowski> well done folks
[20:36] <czajkowski> #topic AOB
[20:36] <czajkowski> council folks any stuff to discuss
[20:37] <huats> nothing in particular
[20:37] <itnet7> czajkowski: nothing that I can think of.... I will do the minutes tonight
[20:37] <itnet7> #action itnet7 will update the minutes
[20:37] <meetingology> ACTION: itnet7 will update the minutes
[20:37] <czajkowski> cool I think we should add them to the blog also
[20:37] <SergioMeneses> czajkowski, sure
[20:37] <czajkowski> with some highlights of the application this was discused in the UDS session
[20:38] <czajkowski> anything else ?
[20:38] <SergioMeneses> czajkowski, and we can share information about the end of the cicle
[20:39] <huats> We haven't started yet I think to create the bugs
[20:39] <huats> for reapproval
[20:39] <huats> it is something that we should
[20:39] <czajkowski> ah I thought we had..
[20:39] <czajkowski> no ?
[20:39] <huats> I could be wrong
[20:40] <czajkowski> SergioMeneses: didnt you create the bugs?
[20:40] <SergioMeneses> czajkowski, yes
[20:40] <SergioMeneses> huats, you can check LP
[20:40] <huats> but I don't remember to have received the email bug in LP
[20:40] <czajkowski> cool so maybe we should follow up on them now and see how things are progressing
[20:40] <huats> that is clearly LP fault ;)
[20:40] <czajkowski> eh no mister it is not :p
[20:40] <SergioMeneses> huats, check your email
[20:40] <czajkowski> are you sure it's not gone to some other folder
[20:40] <SergioMeneses> I have all information here
[20:41] <SergioMeneses> huats, czajkowski https://launchpad.net/ubuntu-locoteams/+milestone/13.04
[20:41] <SergioMeneses> 8 bugs
[20:42] <czajkowski> cool
[20:42] <czajkowski> anything else folks..
[20:42] <SergioMeneses> I did it 3 weeks ago after UDS
[20:42] <czajkowski> cool well lets follow up on these and check in to see how the teams are doing and can we help
[20:43] <itnet7> Nice, Thanks SergioMeneses !
[20:43] <SergioMeneses> czajkowski, sounds good for me
[20:43] <czajkowski> #endmeeting
[20:43] <meetingology> Meeting ended Tue Nov 20 20:43:23 2012 UTC.
[20:43] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-11-20-20.03.moin.txt
[20:43] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-11-20-20.03.html
[20:43] <czajkowski> Thanks for coming folks!
[20:44] <huats> Thanks SergioMeneses
[20:44] <SergioMeneses> czajkowski, huats itnet7 ;)


[13:45] <OdyX> Hi. I am running Debian i386 on my Acer Aspire One and I am considering a switch to Ubuntu lpia. What do you think ?


[06:15] <brobostigon> morning boys and girls.
[06:59] <MooDoo> hello all
[07:04] <brobostigon> morning
[07:22] <MooDoo> :)
[10:25] <knightwise> afternoon peeps
[10:29]  * zmoylan-pi has lights on as it's so gloomy and it's not yet noon...
[10:43] <knightwise> same here , kinda thunderstormy outside
[10:44] <zmoylan-pi> yeah, thunder warnings and rain
[10:50] <MooDoo> nothing here at the moment
[11:23] <zmoylan-pi> a bit damp out there... http://www.accuweather.com/en/ie/dublin/207931/weather-radar/207931
[12:56] <diddledan> "the circle" is on netflix
[12:56] <diddledan> http://www.imdb.com/title/tt4287320/
[12:58] <zmoylan-pi> so... should i get round to watching that? ;-)
[12:59] <diddledan> if you're cynical about facebook yes
[13:00]  * zmoylan-pi fits both those circles on the venn diagram...
[13:01] <MooDoo> i liked it, but it's a big dig and google/facebook/ms everyone lol
[13:39] <smittix> heh, watched that last night.
[13:39] <smittix> I thought it was crap to be honest.
[13:40] <diddledan> it's a good thought experiment IMO
[13:40] <MooDoo> smittix: howdy doody
[13:41] <smittix> I thought it was a little too over the top with the ideas.
[13:41] <smittix> I get what they were trying to achieve in the movie but...
[13:41] <smittix> MooDoo: Hey d00d
[13:41] <MooDoo> although i'm just starting season 2 of Game Of Thrones
[13:42] <smittix> Heh, I started watching that earlier this week.
[13:42] <smittix> I have that and The Wire on the go. Then Netflix kindly informs me Shooter Season 2 has started so I have an episode of that too.
[13:43]  * smittix misses Silicon Valley
[13:48] <MooDoo> diplo: how's the nagios server going?
[14:31] <diplo> I'd already done most of my mine MooDoo, adding newer checks recently like checking raid cards
[14:37] <MooDoo> diplo: just playing about check_nt for network desktop bandwidth :D
[14:41] <diplo> Not used that, will have a tinker
[14:41] <diplo> It's been f'ing manic for the last 2 days, I'm ready to quit!
[14:41] <MooDoo> aw no!
[14:44] <diplo> floods have caused chaos all over SE chaos
[14:47] <MooDoo> yeah got a friend in the lizard that got hit
[14:58] <diplo> I'm honestly close to a melt down today, rarely feel like this, a lot of stuff I'm doing is basic support and I really don't like doing this stuff anymore, I'm paid to much to do it :D
[15:00] <diplo> I recently installed check_mk as well, have you used it Moodoo ?
[15:00] <diplo> ah he's left :D
[15:20] <Azelphur> diplo: I use nagios/checkmk
[15:20] <Azelphur> even wrote a custom check or three :)
[15:24] <diplo> Whats the benefit of it
[15:24] <Azelphur> diplo: you can install the check_mk agent on remote machines and add them to be monitored very easily
[15:25] <Azelphur> and adding a custom check is as simple as dropping a script in a folder
[15:27] <diplo> I use check_by_ssh for that already
[15:27] <diplo> I'll take a look, only reason I installed it was I saw so many posts for it
[15:27] <Azelphur> diplo: yea, honestly I did it that way because I have a friend that knows nagios, and he did it that way too.
[15:28] <diplo> :) - I'm interested though! Will have a looksy when its not so rubbish here
[15:46]  * Dave whispers "prometheus"
[15:56] <diddledan> I'm sorry, Dave, I can't do that
[20:54] <diplo> Anyone alive, if so, do you knowanything about dnscache ?
[20:54] <diplo> Got a server that is hitting 70-80% cpu
[20:54] <diplo> Just need some idea where to investigate
[21:08] <diddledan> this is twisted: https://twitter.com/Lyraull/status/887701316281257986
[21:08] <diddledan> meow!
[21:09] <diddledan> diplo: is your dnscache open to the world? if so you might be being used as an amplifier in a DDoS?
[21:12] <diplo> I'm thinking that, trying to work it out right now
[21:12] <diplo> not a normal server
[21:12] <diplo> SME Server
[21:12] <diplo> Nothing is done normally :)
[21:12] <diddledan> :-)
[21:12] <diddledan> SME. I haven't heard that name in a while
[21:13]  * diddledan goes to check them out to refresh the braincells
[21:16] <diplo> Apparently private
[21:16] <diplo>     access=private
[21:17] <diplo> Not sure what it's being used for on the box, stopping it still allows email to work, if it's on it pegs the cpu and stops dns working
[21:29] <diddledan> hmm
[21:31] <diplo> Well I've got email working, I'll fix it tomorrow when I'm more awake :D
[21:31] <diplo> It's catching up with 24 hours worth ofemails, so is being hammered currently
[21:32] <zmoylan-pi> those nigerian prince communiques must get through!!
[21:32] <diplo> haha, there is ALOT of spam coming through
[21:32] <diplo> The customer doesn't know how to check their spam folder
[21:32] <diddledan> lovespam
[21:33]  * zmoylan-pi always has a few tins in the press
[21:33] <diplo> when I synced it over ( their old box was donkeys years old ) his .junkmail folder had 28ks worth
[21:33] <diddledan> if you're receiving a LOT of email then the spam filter might be killing the DNS
[21:33] <diplo> Maybe
[21:33] <diplo> I'll reenable once it slows down, see if that fixes it
[21:33] <diddledan> for things like SPF records and the like
[21:33] <diplo> The guy who set this up didn't do an overly great job
[21:34] <diplo> First time I've had a chance to look is my own time :/
[21:34] <diddledan> :-(
[21:34] <diddledan> sadface
[21:34] <zmoylan-pi> it's working, at last, sign here, run for the door... :-)
[21:40] <diplo> https://wiki.contribs.org/DB_Variables_Configuration#SpamAssassin
[21:40] <diplo> Want to know what that means
[21:40] <diplo> But finding it hard :)
[22:13] <diplo> And getting there... another issue
[22:13] <diplo> spamassassin couldn't start, needed to run sa-update
[22:13] <diplo> now transaction timeis 4 secs instead of 14
[22:30] <diplo> Right, done. Bed time :) gn all
[22:43] <NET||abuse> hey guys, i've just had to re-install my home server (root / disk failure) so i've just gone from 16.04 to 17.04, i have 4x6TB disks that were btrfs setup, i'm not 100% sure how i had them origionally setup, about 2 years on the go since i set them up.
[22:43] <NET||abuse> so i did blkid /dev/sda  and i set /etc/fstab   as    UUID=5df047bb-72b8-4876-8db6-e5301bcab1ac /mnt/data btrfs defaults  0       0
[22:44] <NET||abuse> so is there anything i should do before i resume using the array of disks?
[22:45] <NET||abuse> i did   btrfs fi show /dev/sda     and it shows the 4 disks with their btrfs usage, which is in line with what i think they should be at, about 30% used
[22:45] <NET||abuse> so remounting them, should i do any updating? from ubuntu 16.04 btrfs  to 17.04 btrfs?


[00:45] <snap-l> http://raghavt.blogspot.com/2012/11/psql-client-can-be-chess-board-now.html <- I <3 PostgreSQL
[01:10] <derekv> I can define functions with parameter binding.
[13:48] <snap-l> Morning
[14:19] <rick_h_> morn
[15:32] <brousch> snap-l: How's the kittay?
[15:51] <snap-l> SHe's sleeping
[15:51] <snap-l> Seems to be a marked improvement over last time.
[15:52] <snap-l> She got out last night from the kitchen (where we can make sure she doesn't jump on anything)
[15:52] <snap-l> JoDee put her on our bed, and she tried like crazy to get comfortable
[15:52] <snap-l> but the dippy cone keeps getting in the way.
[22:29] <snap-l> jcastro_: That GNOME article is pure click-bait
[22:29] <snap-l> was re: https://plus.google.com/113169713749496726739/posts/3Gz32Tvynkp
[23:29] <jcastro_> heh


[00:49] <jono> hey folks
[00:49] <jono> can someone post a blog entry to fridge?
[00:49] <jono> it is a summary of the leadership meeting earlier this week
[00:49] <JoseeAntonioR> jono: I can work on it
[00:49] <jono> JoseeAntonioR, you are a legend, sir
[00:49] <JoseeAntonioR> :)
[00:49] <JoseeAntonioR> thanks
[00:49] <jono> give me five mins to spellcheck
[00:49] <JoseeAntonioR> sure thing
[00:54] <jono> JoseeAntonioR, http://pastebin.ubuntu.com/5638777/
[00:55]  * JoseeAntonioR checks
[00:58] <JoseeAntonioR> jono: I don't think we can embed videos on the fridge, what should I do with it?
[01:00] <jono> JoseeAntonioR, can you just make it a link?
[01:00] <JoseeAntonioR> sure
[01:07] <JoseeAntonioR> jono: I edited some grammar thingies and changed the link, does http://pastebin.ubuntu.com/5638799/ look ok?
[01:20] <jono> JoseeAntonioR, great, thanks!
[01:21] <JoseeAntonioR> now I just need akgraner or pleia2 to review it
[01:41]  * pleia2 takes a look
[01:42] <pleia2> should this go to planet too?
[01:43] <pleia2> adding youtube link
[01:44] <pleia2> published, sending to planet
[01:48] <JoseeAntonioR> oh, right, I forgot that
[01:48] <JoseeAntonioR> thanks!!
[02:35] <jono> thanks pleia2, JoseeAntonioR
[02:35] <jono> sorry I was afk, was putting Jack to bed
[02:35] <JoseeAntonioR> no worries :)


[17:59] <cjohnston> stgraber: ping
[18:02] <stgraber> cjohnston: pong
[18:03] <cjohnston> stgraber: I don't know who the edubuntu project lead is anymore... Are the blueprints for edubuntu all sorted out and good to go for status.ubuntu.com?
[18:04] <stgraber> cjohnston: that'd be highvoltage and me. All of our blueprints should be good and I believe they already all show up on status.u.c
[18:05] <cjohnston> ok.. great.. just making sure.
[18:05] <cjohnston> thanks stgraber
[18:59] <highvoltage> stgraber: I think you pointed me to some ubuntu server product css that you suggested we use as a base for edubuntu server
[18:59] <highvoltage> stgraber: could you point me to that again?
[19:00] <stgraber> highvoltage: that was maas
[19:00] <highvoltage> ah yes that's right
[19:00] <highvoltage> thanks
[19:02] <highvoltage> uuugh... the maas source package contians tarballs with django eggs inside them
[19:02] <highvoltage> ew
[19:05] <highvoltage> stgraber: maas's theme does indeed look nice, the only thing I don't like about it is the AGPL licence, but I guess it could be worse
[19:11] <stgraber> highvoltage: well, I'd like something that looks like it, not necessarily is based on it, so as long as we don't copy the code, we should be fine license-wise
[19:12] <highvoltage> stgraber: ok
[19:12] <highvoltage> looks simple enough to duplicate quite easily, at least
[21:02] <highvoltage> stgraber: will edubuntu server also mount home directories from the server?
[21:02] <highvoltage> I mean, the edubuntu server clients
[21:03] <stgraber> not initially, but a file server role is planned
[21:03] <highvoltage> ok


[01:02] <cjohnston> anyone able to qa https://code.launchpad.net/~chrisjohnston/loco-directory/wording/+merge/65283?
[01:16] <cjohnston> its done! yay
[02:06] <mhall119> approved
[02:07] <mhall119> cjohnston: once it lands, do you want to update the .pot file so the translators can make the necessary changes?
[02:08] <cjohnston> ya
[02:08] <cjohnston> should I add it to production or not worry about it and do a maint release in a week?
[02:09] <cjohnston> there isnt really anything *major* in it
[02:09] <cjohnston> I need a list of noteworthy changes with 0.3.3
[02:09] <cjohnston> * My Teams
[02:09] <cjohnston> * Meetings in Local TZ
[02:09] <cjohnston> * Define a team preferred TZ
[02:10] <cjohnston> * Mothership
[02:10] <cjohnston> * Virtual Events
[02:11] <cjohnston> anything else?
[13:39] <cjohnston> mornin
[13:43] <nigelb> morning cjohnston
[14:15] <mhall119> cjohnston: you bumpted the ubuntu_website version in bzr_apps, right?
[14:15] <cjohnston> in loco_directory? yes
[14:15] <mhall119> cjohnston: Also the "Previously Used" venues
[14:15] <cjohnston> gotcha.. good one
[14:20] <cjohnston> mhall119: http://bazaar.launchpad.net/~loco-directory-dev/loco-directory/0.2/view/head:/loco_directory/settings.py#L186
[14:28] <mhall119> I assume that revision has the mothership?
[14:28] <cjohnston> yup
[14:28] <cjohnston> iirc thats the current revision
[14:28] <mhall119> ok
[16:22] <mhall119> cjohnston: nigelb: relevent to us: http://micknelson.wordpress.com/2011/06/21/develop-and-deploy-with-virtualenv/
[16:25] <nigelb> mhall119: neat!