[00:00] <miconfrink> I could patch the source manually each time I want to rebuild but I'd like to find a way to automate the process a bit
[00:04] <miconfrink> There seems to be two guides out there. One that tells you how to build Ubuntu Kernels and one that tells you how to make packages with make-kpkg for a bastardized patched vanilla kernels
[00:05] <miconfrink> There is nothing about making a clean debian package with patches from a vanilla kernel
[00:05] <miconfrink> I've been searching this for weeks!
[00:08] <bjf> miconfrink we have a script that can help, let me see if i can find it
[00:09] <miconfrink> great!!
[00:13] <bjf> miconfrink: start with "git clone git://kernel.ubuntu.com/ubuntu/kteam-tools"
[00:13] <miconfrink> k one sec
[00:13] <bjf> miconfrink: you want to then look at kteam-tools/mainline-build/README
[00:14] <bjf> miconfrink: essentially, you have your upstream kernel, a reference to one of our kernels and you run the script and it will debian-ize it and build it
[00:15] <bjf> miconfrink: i don't think this will pull our ubuntu-specific patches into your code tree however
[00:16] <miconfrink> I'm more concerned about how to put Molnar's patches into my tree
[00:17] <miconfrink> I'm looking at the README now. Thanks bjf
[00:26] <miconfrink> bjf: So if I understand the README and the scriptfile this will basically give me a Debianized vanilla kernel
[00:27] <bjf> yes
[00:27] <bjf> miconfrink: ^
[00:27] <miconfrink> THen I can deconstruct the deb - I guess
[00:28] <miconfrink> and add Molnar's patch
[00:28] <bjf> miconfrink: have you tried to start with our kernel tree and add the realtime patch to it?
[00:29] <miconfrink> No I've not tried that but it's a pretty extensive patch
[00:29] <miconfrink> I know that someone used to keep a Molnar RT kernel in the Ubuntu repo but it got abandoned
[00:29] <bjf> miconfrink: the delta between our kernel and the upstream mainline kernel really isn't that large, it might be worth giving it a try
[00:30] <miconfrink> okay
[00:30] <miconfrink> I'll look into it
[00:30] <miconfrink> my understanding is that debian patches use quilt
[00:30] <miconfrink> whereas Molnar uses patch
[00:31] <miconfrink> Is there an easy way to convert between formats?
[00:31] <bjf> miconfrink: we just use git, no quilt
[00:31] <miconfrink> I thought debian packages use quilt for patching
[00:32] <bjf> miconfrink: they do, but the kernel team package is different, we need to be as compatible with Linus' tree as possible
[00:32] <miconfrink> I see
[00:32] <miconfrink> that makes sense
[00:33] <miconfrink> so how does the kernel team do things differently
[00:33] <bjf> miconfrink: take one of our trees, do a "git am <molnar patch>" and see what happens. worse case you've wasted some bandwidth and a little time
[00:33] <bjf> miconfrink: but if it works, you'll be way ahead
[00:33] <miconfrink> I see
[00:34] <miconfrink> I've never used git to patch
[00:35] <bjf> miconfrink: you can just use patch if you want
[00:36] <miconfrink> cool
[00:37] <miconfrink> How can I tell what vanilla version the git is based on?
[00:37] <bjf> miconfrink: which version do you want? Precise is 3.2 based
[00:39] <miconfrink> 3.2.16 is the last 3.2 based Molnar patch
[00:39] <miconfrink> http://www.kernel.org/pub/linux/kernel/projects/rt/3.2/
[00:40] <bjf> miconfrink: then precise is the one you want, if you do a git log on the master branch you will see we are patched up to 3.2.14
[00:41] <bjf> miconfrink: if you look at the master-next branch we are patched up to 3.2.16
[00:42] <miconfrink> thanks
[00:44] <miconfrink> can you give me the git path?
[00:44] <bjf> miconfrink: what git patch?
[00:45] <miconfrink> For either branch
[00:45] <miconfrink> I'm not quite getting it right
[00:45] <bjf> miconfrink: sorry, i misread what you typed
[00:46] <bjf> miconfrink: "git clone git://kernel.ubuntu.com/ubuntu/ubuntu-precise"
[00:46] <miconfrink> gotcha thanks a billion!
[00:46] <bjf> miconfrink: in that repo there are both the "master" and "master-next" branch
[05:51] <ppisati> good rainy day to everyone :)
[07:28] <smb> ppisati, Not right now, but good morning anyway. :)
[07:28] <ppisati> smb: a thunderstorm woke me up thus morning, i love when that happens :)
[07:30] <smb> ppisati, Isn't the relative safety of so many other houses around you to hit something to enjoy? ;)
[07:31] <ppisati> smb: when i'm in bed, under a mountain of blanket, i don't really care about other's house safety :D
[08:29] <ensignkim> hi i've got a question about dkms...
[08:30] <ensignkim> i'm currently using 10.04 netbook remix with 2.6.32-41-generic
[08:30] <ensignkim> my netbook has a realtek wireless card
[08:30] <ensignkim> i have to use this ppa to get drivers which work with my wireless card
[08:31] <ensignkim> http://www.todoleo.com/2011/01/how-to-get-wifi-working-on-dell-mini.html
[08:31] <ensignkim> every time the kernel updates, it breaks my wifi
[08:31] <ensignkim> and i have to apt-get --reinstall the ppa packages
[08:32] <ensignkim> i'm not sure why i have to do that... shouldn't dkms fix things automagically (or have i misunderstood its purpose)?
[08:34] <diwic> kengyu, ^ that's your ppa
[08:34] <kengyu__> ahh, yeah, is my ppa.
[08:36] <kengyu__> ensignkim, rtl8192ce is supposed to to be in mainline already. Did you try to fully uninstall the dkms deb and see if the wifi works?
[08:37] <diwic> kengyu__, he's using 10.04
[08:37] <diwic> kengyu__, was it in mainline there as well?
[08:37] <ensignkim> yep, i'm currently on lucid still but will upgrade to 12.04 soon
[08:40] <ensignkim> kengyu_: i'm not sure :) wifi breaks every time there is a kernel upgrade, and i do something to fix it but can't remember what - i think i may do an "apt-get purge"
[08:42] <kengyu_> ensignkim, then could be my badly packaged dkms. :-( I haven't look at it for a while. the deb could be of low quality since it sees no hope to get in the main archive or so (already one in mainline).
[08:44] <infinity> ppisati: *poke*
[08:44] <infinity> ppisati: Andy tells me that you'd love to have a closer look at https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/986713
[08:44] <ubot2> Launchpad bug 986713 in linux-ti-omap4 "boot on panda shows kernel oops" [Undecided,New]
[08:45] <ensignkim> kengyu_: so, hopefully wifi should work for me out of the box when i upgrade to 12.04? thanks for the ppa btw, without it my netbook would have been somewhat useless :)
[08:48] <kengyu_> ensignkim, Realtek engineer worked on upstreaming the driver, so it is supposed to work as well as the one in my ppa.
[08:54] <ppisati> infinity: we had these WARNs() since... natty?
[08:54] <ppisati> infinity: but ack, i'll take a look
[08:54] <apw> ppisati, be good to confirm its the known ones at least :)
[08:54] <infinity> ppisati: Nothing wildly urgent, but Andy implied that you have *nothing* to do. ;)
[08:54] <apw> :)
[08:55] <ppisati> infinity: he's kind of right... :)
[08:56] <ppisati> at least someone i know someone is testing it... :)
[08:57] <ppisati> -ETOOMANYSOMEONE
[11:26]  * ppisati -> lunch
[11:45] <apw> smb, is this something you have a test environment to confirm: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987715
[11:45] <ubot2> Launchpad bug 987715 in linux "In KVM In a virtual machine, system crashes if vmvga video card is used" [Undecided,Confirmed]
[11:46] <smb> apw, Without looking into the whole description it sounds like any kvm host/guest could do when changing the graphics card (the emulated)
[11:47]  * cking reboots his AP
[11:48] <smb> apw, I might need to reinstall kubuntu... just checking with vmvga and normal ubuntu install
[11:51] <smb> apw, Unity-2d seems not to crash. Interestingly the default resolution picked is 2360x1770...
[12:11] <apw> smb, woh that is pretty big
[12:12] <smb> apw, Yeah, it made hitting things a bit hard when scaling down into my resolution... :)
[12:13] <smb> Right now installing kubuntu on the vm
[12:19] <apw> diwic, https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/987650 <-- might be of interest
[12:19] <ubot2> Launchpad bug 987650 in linux "Audio Realtek ALC889, Green/Black/Yellow Line Out, rear jacks: no sound when front jack plugged into headphones" [Undecided,Confirmed]
[12:23] <diwic> apw, sure, is there anything that makes it more or less interesting than all the other audio bugs?
[12:42] <smb> apw, I cannot confirm a crash, but rendering not being optimal (sometimes large areas not redrawn, splash not being rendered) with the vmvga setting. For this test the host gfx was ati (not sure about the report)
[13:40] <smb> apw, For the kvm-vmvga bug I think the main problem could be in the host part (which is Natty) and I am not sure whether I still have a host running that around.
[14:10] <apw> cking, yo ... we have an HP failing to suspend, leading to hang.  this is triggering from echo "mem" >...
[14:10] <apw> cking, whats the next step :)
[14:10] <cking> apw, hey, is this a regression or not?
[14:11] <apw> cking, i believe its 'always' been this way
[14:11] <cking> apw, https://wiki.ubuntu.com/DebuggingKernelSuspend
[14:12] <cking> https://wiki.ubuntu.com/Kernel/Reference/S3SystemTapDebug
[14:13] <cking> apw, the latter may provide more info, but takes a while to set up - it was working for precise last month, so I suspect it still should work OK
[14:15] <apw> cking, sounds good.  will get psivaa on the case :)
[14:16] <cking> I suggest they file a bug, follow the systemtap instructions and attach the logs generated by the debugging tool into the bug
[14:16] <cking> apw, BTW, what kind of HP is it?
[14:16] <psivaa> cking, already done it
[14:17] <psivaa> cking, 987840
[14:17] <apw> cking, a pavillion g6
[14:18] <jsalisbury> **
[14:18] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[14:18] <jsalisbury> **
[14:22] <cking> psivaa, so can you see if you get any logs when following the instructions in: https://wiki.ubuntu.com/Kernel/Reference/S3SystemTapDebug
[14:22] <psivaa> cking, just following the debugging information
[14:22] <cking> psivaa, thanks!
[14:23] <psivaa> cking, will let you know once i get the longs
[14:23] <psivaa> * logs
[14:23] <cking> ack
[14:26] <matttbe> Hello
[14:26] <matttbe> I've opened an upstream bug report at bugzilla.kernel.org [1] but they want that I test a patch.
[14:26] <matttbe> 1: https://bugzilla.kernel.org/show_bug.cgi?id=43155
[14:26] <matttbe> It's not a problem except that I don't find the .dsc file linked to the version 3.4-rc4-precise => http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc4-precise/
[14:26] <ubot2> bugzilla.kernel.org bug 43155 in Sound(ALSA) "hda-intel: Sound card takes time to be initialised" [Normal,New]
[14:26] <matttbe> Where can I find this .dsc file? :)
[14:35] <dileks> matttbe: I have not tested by myself, but I guess you have to apply those 3 patches against vanilla 3.4-rc4 sources
[14:36] <dileks> [10:17:03] <ohsix> https://wiki.ubuntu.com/Kernel/MainlineBuilds
[14:37] <dileks> matttbe: ^^
[14:42] <matttbe> dileks: yes I already test the 3.4-rc4 version by installing packages from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc4-precise/
[14:42] <matttbe> dileks: now I just want to test a patch. Should I've to download tarball from kernel.org and apply patches from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc4-precise/
[14:44] <dileks> whoever is responsible for the wiki: airlied pulls from danvet's GIT tree (drm-intel-next)
[14:44] <dileks> http://cgit.freedesktop.org/~danvet/drm-intel/log/?h=drm-intel-next
[14:44] <dileks> 3. the tip of the drm-intel-next head of Keith Packard's linux repository daily,
[14:54]  * ogasawara back in 20
[14:55] <matttbe> dileks: thank you but  I just want to easily recompile the kernel with a patch which is not in any git repos mentioned on the wiki
[14:56] <dileks> make deb-pkg
[14:57] <dileks> matttbe: http://paste.ubuntu.com/944190/
[14:57] <matttbe> dileks: thank you :)
[15:07] <psivaa> cking:  Magic: 11:330:749 maps to hash: b664bb followed by Hash matches: oops_enter() (address: 0)
[15:07] <psivaa> cking: is the output of the debug
[15:08] <cking> psivaa, there may be some logs created, can you attach them to the bug report please
[15:08] <psivaa> cking: ack
[15:21] <hggdh> jsalisbury: re bug 987052 -- happened with lbm-cw-3.3, added a comment and a pic (FWIW)
[15:21] <ubot2> Launchpad bug 987052 in linux "WARNING: at /build/buildd/linux-3.2.0/kernel/softirq.c:159 local_bh_enable_ip+0x7a/0xa0()" [High,Confirmed] https://launchpad.net/bugs/987052
[15:34] <cking> psivaa, I've added some more instructions to the bug report.
[15:36] <psivaa> cking: ok ill have a look and follow
[16:00] <tgardner> apw, cking, if not built into the kernel, how do cpufreq modules like powernow-k8 get loaded? I don't see anything in initramfs-tools that will do it.
[16:04] <cking> tgardner, it's not clear to me either
[16:04] <smb> I see some x86cpu id tables
[16:06] <smb> MODULE_DEVICE_TABLE(x86cpu, ...
[16:10] <tgardner> cking, bug #353552 ?
[16:10] <ubot2> Launchpad bug 353552 in jockey "nvidia driver crashes on login after fisrt install (dup-of: 349419)" [Undecided,New] https://launchpad.net/bugs/353552
[16:10] <ubot2> Launchpad bug 349419 in python-qt4 "jockey-kde crashed with SIGSEGV in QWidget::metric() on kubuntu 9.04 startup" [Medium,Fix released] https://launchpad.net/bugs/349419
[16:10] <cking> 355232
[16:10] <tgardner> bug #355232
[16:10] <ubot2> Launchpad bug 355232 in linux "acpi-cpufreq/powernow-k8 should not be built-in into the kernel image" [Low,In progress] https://launchpad.net/bugs/355232
[16:21] <apw> tgardner, they have to be manually specified, i thought that they were all builtin for that reason
[16:21] <tgardner> apw, yep, I'm just coming around to that.
[16:22] <apw> tgardner, iirc there is an annotation to that effevt in the config comparitor
[16:23] <tgardner> apw, I wonder if we could add a kernel command line parameter to no load these cpufreq drivers, ala https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355232/comments/15
[16:23] <ubot2> Launchpad bug 355232 in linux "acpi-cpufreq/powernow-k8 should not be built-in into the kernel image" [Low,In progress]
[16:24] <psivaa> cking: i have updated the bug report to the effect the suspend on the console mode seems working but every reboot requires pressing of the brightness adjustment key
[16:24] <smb> tgardner, commit 22ee5756cd21063ba8405598060b0f1ef8d81a6d
[16:24] <smb> Author: Konrad Rzeszutek Wilk<EMAIL_ADDRESS>[16:24] <smb> Date:   Tue Mar 13 19:18:39 2012 -0400
[16:24] <smb>     provide disable_cpufreq() function to disable the API.
[16:25] <tgardner> smb, 448c8b1d07d5342922567e138a4b0108a42c24fb
[16:26] <smb> Though this looks a bit like one could not use the framework then...
[16:26] <smb> tgardner, Yep, sorry that was picking up the sha1 of my tree
[16:27] <tgardner> smb, yeah, I think what we really want is for the built-in drivers to not register, but leave the infrastructure intact.
[16:27] <smb> Yeah, agree
[16:28] <smb> this one is overshooting, ok for Xen since they then use something completely outside the framework
[16:28] <tgardner> smb, we can likely manage to do both.
[16:43] <cking> brendand, bug 926136 - can I get access to this machine so I can do some hands on debugging?
[16:43] <ubot2> Launchpad bug 926136 in linux "CPU1 on Dell PowerEdge M610, R715 and IBM X3500 M3 goes offline after exercising frequency governors" [Medium,Triaged] https://launchpad.net/bugs/926136
[17:11]  * henrix back in 30
[17:12]  * cking --> EOD and going to fix his washing machine
[17:24] <slangasek> tgardner: heya - I've come to argue with you over the wontfixing of bug #942846 :)
[17:24] <ubot2> Launchpad bug 942846 in grub2 "encrypted install fails to boot as long as vt.handoff=7 is used" [Undecided,Fix released] https://launchpad.net/bugs/942846
[17:24] <tgardner> slangasek, you should likely argue with apw since the vt.handoff patch is his.
[17:24] <slangasek> tgardner: I'm not sure if the remaining issue is a kernel bug or not, but I think it's pretty important, UX-wise, that users not be dropped to a black screen instead of an encryption prompt
[17:24] <slangasek> well, you wontfixeded it
[17:25] <slangasek> apw: I've been redirected to you
[17:25] <tgardner> slangasek, well, its pretty low on our list of priorities given some of the other issues we're dealing with.
[17:25] <apw> slangasek, what the issue ?  i thought we didn't pass it anymore from grub
[17:26] <apw> slangasek, and that we should be saying we wouldn't for encrypted installs
[17:26] <slangasek> apw: tgardner says he still encounters a black screen which he works around by pressing Esc
[17:26] <slangasek> hmm?
[17:26] <slangasek> encrypted installs most certainly still get vt.handoff
[17:26] <slangasek> and it works for most of us
[17:27] <slangasek> I understand it's not at the top of the todo list, but it's still an important bug (whoever's it actually is)
[17:27] <apw> then his machine is broken and should be added as broken to the blacklist right?
[17:28] <apw> so that it doesn't use handoff, as it doesn't work appropriatly in this situation
[17:28] <tgardner> apw, where is the blacklist ? grub2 ?
[17:28] <slangasek> grub-gfxpayload-lists
[17:28] <slangasek> e.g., /usr/share/grub-gfxpayload-lists/blacklist/20_radeon_hd6800
[17:29] <apw> yeah ... i think that was the basic plan :)
[17:29] <slangasek> ok - I don't think that plan was handed off :)
[17:30] <tgardner> slangasek, ok, I'll see if blacklisting works, but I still don't think there is gonna be a kernel fix.
[17:30] <slangasek> tgardner: can you get us PCI ID for your affected machine on that bug, then?  And I'll open a task for grub-gfxpayload-lists
[17:30] <apw> slangasek, i think we are a little confused indeed.  i think we tried to fix most of them and those that we couldn't we ensured that the blacklist would do the right thing
[17:30] <tgardner> slangasek, yep, gimme a bit
[17:31] <slangasek> apw: the blacklist is approximately empty by default
[17:31] <apw> slangasek, and then we needed to find the exclusions and drop them in the blacklist
[17:31] <apw> slangasek, indeed very much so
[17:31] <slangasek> we do additional blacklisting if you install the non-free, non-KMS drivers
[17:31] <slangasek> tgardner: do you think it's not a kernel bug, or just not one that will get fixed any time soon?
[17:32] <tgardner> slangasek, I've no idea to be honest.
[17:32] <tgardner> I just know that I'm not gonna work on it.
[17:32]  * slangasek nods
[17:33] <slangasek> hmm, I should probably take another pass over the plymouth bug list now that RAOF has blacklisted the HD 6800
[17:35] <apw> slangasek, i assume its a bug in the initialiseation from 'not the default text mode' in the graphics driver
[17:35] <slangasek> that was my approximate thought as well
[17:36] <tgardner> slangasek, hmm, apport-collect is giving me shit about not being the bug owner (or some such crap)
[17:37] <slangasek> bah
[17:37] <sharms_> In Ubuntu 12.04, I installed linux-tools-base, and then tried to install linux-base.  /usr/bin/perf is in both of these packages, making this impossible.  Is this a known issue?
[17:37] <slangasek> tgardner: attach lspci -vvnn by hand?
[17:37] <tgardner> slangasek, yeah
[17:38] <sharms_> rather specifically linux-tools-common conflicts with linux-base
[17:38] <slangasek> RAOF: hey, so bug #975931 is the same issue as bug #971204, but with an incremented PCI ID
[17:39] <ubot2> Launchpad bug 975931 in plymouth "purple screen freeze with AMD 6850" [Undecided,New] https://launchpad.net/bugs/975931
[17:39] <ubot2> Launchpad bug 971204 in linux "graphics fails with setgfxpayload=keep, AMD Radeon" [Medium,Confirmed] https://launchpad.net/bugs/971204
[17:39] <slangasek> (1002:6738 vs. 1002:6739)
[17:53] <bjf> jsalisbury: any reason to have a kernel meeting before uds ?
[17:54] <jsalisbury> bjf, hmm, probably not, unless there is a specific reason?
[17:54] <jsalisbury> bjf, I can change the next meeting to after UDS?
[17:57] <bjf> +1
[18:06] <ogasawara> woot, day-0 uploaded
[18:06] <jsalisbury> Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues May 15th, 2012 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
[18:20]  * _ruben wonders if that was an attempt to alter the /topic :)
[18:25] <bjf> jsalisbury: you didn't get the topic changed :-)
[19:15] <bjf> cnd: https://blueprints.launchpad.net/ubuntu/+spec/other-q-arsenal-report-enhancements
[19:16] <cnd> bjf, ahh, oops
[19:17] <cnd> I think I'll just remove my blueprint then
[19:17] <cnd> and subscribe to this one
[19:17] <bjf> cnd, good plan. add anything to the whiteboard you feel needs to be discussed
[19:18] <cnd> yep
[19:18] <cnd> thanks!
[19:48] <dileks> thought this is a kernel problem but seems to be a nm issue
[19:48] <dileks> https://bugzilla.redhat.com/show_bug.cgi?id=785772
[19:49] <ubot2> bugzilla.redhat.com bug 785772 in NetworkManager "Logs filled by ICMPv6 RA: ndisc_router_discovery() failed to add default route" [Unspecified,On_qa]
[19:54] <bjf> cnd, we were editing the whiteboard at the same time, there doesn't seem to be any locking so my changes were lost
[19:56] <bjf> cnd, i just re-added my text
[19:59] <cnd> bjf, oh, sorry :(
[19:59] <jono> hey
[20:00] <jono> do you folks know if Intel Centrino Ultimate-N 6300 AGN is well supported in 12.04?
[20:00] <jono> I am looking to buy a new laptop
[20:01] <bjf> cnd, not your fault, stupid LP
[20:02] <bjf> jono, tgardner or sforshee would know best but I believe it is
[20:02] <jono> tgardner, sforshee, any thoughts on this?
[20:03] <tgardner> jono, I came in on the tail end of this conversation, but I assume its about wifi ?
[20:03] <sforshee> jono, it's supported but I also believe it's one that's had some persistent issues
[20:03] <jono> tgardner, yeah, I am looking to buy a new laptop, and I have a few options, I want to figure out the best driver support
[20:04] <jono> my options are:
[20:04] <jono> ThinkPad 1x1 b/g/n
[20:04] <jono> Intel WiFi Link 1000
[20:04] <jono> Intel Centrino Advanced-N 6205 AGN
[20:04] <jono> Intel Centrino Ultimate-N 6300 AGN
[20:04] <jono> Intel CA-N+WiMAX 6250 MOW
[20:04] <jono> any feedback on which of those is best supported in 12.04?
[20:04] <jono> sforshee, I see
[20:04] <tgardner> jono, Intel is well supported, but there _are_ folks complaining about throughput in certain scenarios
[20:05] <tgardner> jono, I've tested all of these models and found them to perform OK.
[20:05] <jono> thanks tgardner
[20:05] <jono> I will get the Ultimate-N and see how I get on
[20:06] <tgardner> jono, good luck
[20:06] <jono> thanks tg
[20:06] <vanhoof> jono: 6205 has worked quite well for me
[20:06] <jono> thanks tgardner
[20:06] <jono> vanhoof, oh yeah?
[20:06]  * tgardner reboots for cpufreq patch testing
[20:06] <sforshee> jono, I have a 6205 too and have had good luck with it
[20:06] <jono> vanhoof, is it working well in 12.04?
[20:06] <vanhoof> jono: yup, Lenovo x220
[20:06] <jono> ok, I am going to do that then :-)
[20:06] <jono> thanks sforshee, vanhoof
[20:07] <vanhoof> jono: np
[20:09] <jono> I am also going with 	Intel HD Graphics 3000 graphics
[20:09] <jono> seems to be generally pretty decent
[20:09] <vanhoof> jono: which machine are you after?
[20:09] <jono> vanhoof, T520
[20:11] <vanhoof> jono: just integrated graphics or nvidia as well?
[20:11] <jono> vanhoof, just integrated graphics
[20:11] <vanhoof> jono: ok, you'll be good then
[20:11] <jono> do you know if Intel HD Graphics 3000 is certified?
[20:11] <vanhoof> the other is switchable
[20:11] <jono> right
[20:11] <vanhoof> oh yeah, its sandybridge
[20:11] <jono> cool
[20:11] <vanhoof> the machine itself is also ubuntu certified
[20:12] <jono> vanhoof, do you know if SATA solid state discs are OK?
[20:12] <vanhoof> was enabled on 10.10, certified on stock 11.04, 11.10, and 12.04 is in progress
[20:12] <vanhoof> jono: oh yeah :)
[20:12] <jono> cool thanks vanhoof
[20:12] <vanhoof> jono: but you'd likely want to purchase one off of amazon
[20:12]  * jono buys
[20:12] <jono> a thinkpad?
[20:12] <vanhoof> they charge a pretty hefty premium
[20:12] <vanhoof> for the SSD
[20:12] <jono> oh really?
[20:13] <vanhoof> jono: http://www.amazon.com/Intel-Series-2-5-Inch-Solid-State-Retail/dp/B004T0DNQ0/ref=sr_1_2?s=electronics&ie=UTF8&qid=1335298379&sr=1-2
[20:13] <jono> looks about the same price...this machine I am getting is in an employee pricing sale
[20:14] <vanhoof> ah ok
[20:34]  * tgardner -> EOD
[23:33] <uzf> glad to see my kernel changes were picked upstream :D


[03:53] <ravi> hi
[03:53] <ravi> how to download edubuntu? the link is not working which is given in the website


[00:30] <robert_ancell> thumper, so is it normal for all my unity icons to have disappeared?
[00:37] <jbicha> chrisccoulson: I like the new "restart firefox" button, but...
[00:38] <jbicha> it doesn't stay on my screen very long, and I want to at least finish my apt-get upgrade first before restarting Firefox
[00:38] <jbicha> once it disappears, I don't see any way to get it back
[01:21] <thumper> robert_ancell: no
[02:14] <ceti331> can ubuntu's global-menu be made to show permanently
[02:14] <ceti331> instead of only when mouse hovers
[03:47] <ceti331> i'm trying to use kwin under ubuntu - nearly ok, but having trouble enabling desktops etc..
[03:48] <ceti331> should CCSM work, or is can KWin's native configuration editor be used
[03:53] <RAOF> You'd need kwin.
[03:54] <RAOF> But I'm not entirely sure why you wouldn't just install kubuntu-desktop; almost all the Ubuntu session is in compiz, anyway.
[03:59] <ceti331> ok doing so. for some reason i thought KDE was no longer supported in ubuntu repositories.i was surprised i could even install kwin
[03:59] <ceti331> i didn't really want to clutter menus with kde+gnome apps... but its not a bit problem
[03:59] <ceti331> i had kwin running fine.. i just couldn't change any options like desktops
[04:09] <hyperair> kubuntu's no longer funded by canonical, but that doesn't mean it's no longer supported.
[04:21] <pitti> Good morning
[04:29] <RAOF> Ah. I see that the amd64 buildds have a little bit of work to do :)
[04:29] <RAOF> pitti: Good morning!
[04:30] <pitti> hey RAOF, how are you?
[04:30] <RAOF> I'm pretty good!
[04:30] <RAOF> The system compositor's now ready for your testing enjoyment*
[04:30] <RAOF> *: As long as you're on i386; amd64 is waiting to build
[04:31] <RAOF> Hows about your fine self?
[04:38] <pitti> RAOF: I'm quite fine, thanks! I hurt myself a little in yesterday's TKD training, but I hope that just reinforces the "don't do that then" learning process :)
[04:39] <RAOF> :)
[04:39] <pitti> (hitting my partner's elbow with my foot, not TKD at large, of course
[04:40] <RAOF> Ow. Hitting the hard bit :)
[04:40] <pitti> RAOF: do you need some build prio bumps?
[04:40] <RAOF> pitti: That'd be grand, thank you.
[04:40] <RAOF> https://launchpad.net/~ubuntu-desktop/+archive/system-compositor/+build/3650161
[04:42] <pitti> "Start in 35 seconds "
[04:42] <pitti> RAOF: right, I assumed so; it's just weston, right?
[04:42] <RAOF> Yup
[04:42] <RAOF> Oh? Last time I looked at it it was "start in 5 hours"
[04:43] <Sarvatt> RAOF: thank you so freaking much for getting mesa 8.1 in a somewhat buildable state btw :)
[04:44] <Sarvatt> i went through the diff and pilfered it for xorg-edgers
[04:44] <Sarvatt> also urgency=critical skips the queues :)
[04:44] <pitti> RAOF: 5 hours> that was before I bumped the score :)
[04:44] <RAOF> Heh.
[04:46] <TheMuso> RAOF: I saw your changes to the blueprint, but is radeon actually testable atm as well as nouveau?
[04:47] <RAOF> TheMuso: Depends on what you mean by ‘testable’. It *should* load; you may or may not get a wonderful pink screen, though. :)
[04:48] <TheMuso> RAOF: Ok, I'll make some time to test the hardware I have access to in the next few days.
[04:49] <RAOF> It will be a particularly fetching shade of fuscia if you get the all-pink version :)
[04:50] <TheMuso> Heh ok.
[05:04] <ceti331> is it possible to setup compiz 'rotate-cube' on a laptop to be triggeredby 'pivot' gesture (e.g. a 2finger rotate gesture distinct from scrolling gestures)
[05:06] <RAOF> Yes*
[05:06] <RAOF> *As long as you implement that
[05:08] <ceti331> "can you do this" "yes YOU can" ? :)
[05:09] <ceti331> really miss the 3 finger gestures on the mac... but it should be possible to extend linux to behave not too dis-similar
[05:10] <RAOF> ceti331: utouch is what you're after; Unity already implement some 3- and 4-finger gestures.
[05:10] <RAOF> Of course, you *also* need multitouch hardware, and basically only macs have decent multitouch hardware.
[05:10] <pitti> RAOF: all built and published; want me to try the new love again?
[05:10] <ceti331> thats what i'm begining to discover
[05:10] <ceti331> i think my hardware is 2finger
[05:11] <RAOF> pitti: Yeah, give it a whirl.
[05:11] <ceti331> thats why i thought rotate gesture would be nice ... i never rotate/zoom photos, but perhaps those gestures could be used to rotate/zoom the desktop :)
[05:12] <RAOF> ceti331: Hah! You think that "two finger" means that the hardware reports two independent touch points! How amusingly naieve :/.  No, your hardware probably doesn't report enough information to do that.
[05:12] <ceti331> <need to mod my laptop...embed an ipod touch...>
[05:12] <ceti331> RAOF- "device touches:2"
[05:13] <ceti331> RAOF: it does support2 finger scroll
[05:13] <RAOF> Probably means "I report 1 touch point, plus the fact that you have two fingers down"
[05:13] <ceti331> iss there a commandline debug app
[05:13] <RAOF> Because touchpads all uniformly suck.
[05:13] <ceti331> a commandline app that spews out raw info
[05:13] <RAOF> evtest
[05:14] <pitti> RAOF: btw, you might want to update the description for "dist-upgrade", otherwise it'll hold back lightdm and xserver-xorg-core
[05:14] <ceti331> is this a doomed quest
[05:14] <RAOF> pitti: Oh?  I habitually do dist-upgrade rather than upgrade, so I mustn't have noticed :)
[05:15] <pitti> RAOF: ok, I'll change it then :)
[05:15] <ceti331> heh oh well.. there's things in linux that i do like such as focus-follows-mouse and edge-warp
[05:15] <RAOF> pitti: I've just done it.
[05:15] <pitti> RAOF: yeah, upgrade is really not all that useful
[05:17] <ceti331> http://www.synaptics.com/solutions/technology/touchpad-linux
[05:18] <ceti331> maybe some hope... this synaptics page (i have a synaptics trackpad) does talk about 3fingers ... however, geisview says "2"
[05:23] <ceti331> evtest: its telling me the xserver has the device
[05:23] <ceti331> no its telling me "This device is grabbed by another process
[05:24] <ceti331> interestingly, it DOES say "event-code 333 BTL_TOOL_DOUBLETAP" and "Event Code 334 BTL_TOOL_TRIPPLETAP"
[05:28] <jbicha> RAOF: I got the pretty fuschia fun on Intel
[05:29] <RAOF> jbicha: Ooh, how much fuchsia? All fuchsia, or just down the right hand side?
[05:30] <jbicha> it's broke enough that I wasn't able to log into Unity, I did get gnome-classic-no-effects to work
[05:31] <jbicha> http://paste.ubuntu.com/1087377
[05:33] <jbicha> also, when I switch between a virtual terminal back to the GUI, a bunch of ~~~~~ is emitted
[05:35] <jbicha> maybe the fuschia I saw is that washed-out-unity-greeter bug since my wallpaper is just the Ubuntu default
[05:35] <ceti331> RAOF: ok, your pessimism is justified. It appears it reports 2,3 finger taps, but can't report 3 finger swipe. it can only report 1 or 2 fingers with movement
[05:35] <ceti331> it CAN however report 2 independant positions... thats something
[05:38] <pitti> RAOF: "go to town"?
[05:38]  * pitti googles English phrases
[05:38] <pitti> ah, http://www.urbandictionary.com/define.php?term=go%20to%20town :)
[05:39] <ceti331> i must stop obsessing about this, i have a numerc keypad on this laptop.. pgup/pgdn, home,end
[05:52] <pitti> RAOF: I never considered myself being overly picky about visual design, but I do have some minor complaints about http://people.canonical.com/~pitti/tmp/weston.jpg
[05:53] <pitti> RAOF: I can't actually change the user there, and launching a guest session paints a barely noticeable and heavily condensed dark panel on top of lightdm
[05:53] <RAOF> pitti: Good, good. What driver's that?
[05:53] <pitti> RAOF: intel (Arrandale)
[05:53] <pitti> on a 1280x1024 DVI
[05:53] <RAOF> Hm. Ok.
[05:54] <pitti> did you see this before?
[05:54] <RAOF> No.
[05:54] <RAOF> Well, not exactly that.
[05:55] <RAOF> It looks like everything's in the wrong place, basically.
[05:55] <RAOF> Interesting logs are /var/log/lightdm/{weston.log,x-0.log}
[05:57] <pitti> hm, the recent x.logs there are from the run after stop lightdm/start lightdm which just left X completely broken
[05:57] <pitti> ah, X: ../../intel/intel_bufmgr_gem.c:2870: drm_intel_bufmgr_gem_init: Assertion `0' failed.
[05:57] <pitti> but that's not the one with the weird looking graphics
[05:58] <pitti> weston.log has a nice "caught segv" stack trace, though
[05:58] <pitti> RAOF: ok, I'll start it again and get you recent logs
[05:58] <RAOF> Well, *that's* not supposed to happen :)
[05:58] <didrocks> good morning
[05:58] <pitti> bonjour didrocks, ca va?
[05:58] <didrocks> hey pitti, RAOF
[05:58] <RAOF> pitti: Ta muchly.
[05:58] <didrocks> pitti: ça va bien, et toi?
[06:01] <pitti> didrocks: je vais bien, merci!
[06:01] <pitti> didrocks: I love how unity has become a lot more efficient
[06:02] <didrocks> pitti: yeah, feeling the difference? :)
[06:02] <TheMuso> Same here, particularly the startup.
[06:02] <pitti> now that the launcher is behind all other windows anyway, it does away with the icons and just shows some small triangle on an otherwise pitch black launcher
[06:02] <didrocks> thanks to duflu :)
[06:02] <pitti> I guess that makes it quite a bit faster :)
[06:02] <didrocks> pitti: hum, the launcher behing all other windows?
[06:03] <pitti> ah, now it decided to come to the front
[06:03] <pitti> still empty, though
[06:03] <didrocks> no icon at all?
[06:03] <pitti> i. e. no icons nor icon containers
[06:03] <didrocks> urgh
[06:03] <pitti> just a semitransparent grey area with the triangles
[06:03] <didrocks> pitti: popey's team is taking care of unity, please ping him on #ubuntu-unity
[06:03] <didrocks> when he's here
[06:04] <didrocks> I saw someone else complaining about it on a bug mail
[06:04] <didrocks> so you are not alone :/
[06:04] <didrocks> didn't reproduce though
[06:04] <didrocks> still having a happy launcher with all its teeth/icons here
[06:05] <pitti> RAOF: to my untrained eye, http://people.canonical.com/~pitti/tmp/weston.log looks fairly reasonable
[06:05] <pitti> RAOF: 1280x800 is the internal LVDS, and 1280x1024 the external DVI
[06:05] <pitti> RAOF: http://people.canonical.com/~pitti/tmp/x-0.log, too
[06:07] <RAOF> pitti: It does indeed look sane; I guess that it's the multi-monitor bit that's confusing it.
[06:08] <pitti> if I can tell it somehow to ignore LVDS -- I don't care about this at all while it's docked, and my session startup script even xrandrs it off
[06:09] <RAOF> Not trivially, no.
[06:09] <RAOF> This needs fixing.
[07:42] <Nathan_S> Does anyone knows what modules do you need to import to make the clipboard work in gtk?
[07:42] <rickspencer3> pitti, any thoughts? he's using Python ^
[07:43] <rickspencer3> and please don't say "use pygtk ;)"
[07:45] <rickspencer3> didrocks, anyone?
[07:46] <didrocks> hey rickspencer3
[07:46] <rickspencer3> hey didrocks
[07:46] <rickspencer3> we're finding zero documentation on how to port clipboard code to gio :(
[07:47] <didrocks> http://python-gtk-3-tutorial.readthedocs.org/en/latest/clipboard.html
[07:47] <didrocks> a pygi example ^
[07:48] <rickspencer3> Nathan_S, http://www.scribd.com/doc/99516129/66/Clipboard-Objects
[07:48] <didrocks> rickspencer3: it's the same content :p
[07:48] <rickspencer3> thanks didrocks
[07:48] <rickspencer3> you beat me to it :)
[07:48] <didrocks> http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html is a really good reference
[07:49] <didrocks> less good than pygtk tutorial, but already contains a lot, and is up to date :)
[07:49] <rickspencer3> oh my, it doesn't use any of the callbacks :(
[07:49] <rickspencer3> weak
[07:50] <pitti> Nathan_S: do you have a more concrete example what is not working?
[07:50] <didrocks> rickspencer3: you mean, callback from ClipboardWindow?
[07:50] <rickspencer3> didrocks, well, in C you can set_with_data, where you tell the clipboard "hey, I can give other apps this list of types of things to paste"
[07:50] <rickspencer3> and you give it a callback function
[07:51] <pitti> Gtk.Clipboard is supposed to be introspectable; it's not unlikely that there are bugs there, of course
[07:51] <rickspencer3> then when another app asks to paste, it calls your callback function and you figure out what kind of data the other app wants and paste it what it wants
[07:51] <rickspencer3> hey pitti
[07:51] <pitti> rickspencer3: so, no off-hand idea, I never tried using the clipboard (in any language)
[07:53] <didrocks> rickspencer3: doesn't seem to have any example of gtk_clipboard_request_image in pygi world. Should work like any other introspectable data as pitti tells (so clipboard.request_image()…) but not sure if Nathan_S can convert it himself :)
[07:54] <rickspencer3> didrocks, well, not all the functions are on the clipboard object
[07:55] <rickspencer3> notably,  set_with_data is missing
[07:57] <didrocks> rickspencer3: set_data ?
[07:58] <rickspencer3> didrocks, nope, that function is for setting the data that will get pasted
[07:58] <rickspencer3> it has set_text, set_image, and set_data
[07:58] <rickspencer3> set_text and set_image are just conveniences for set_data, set_data is flexible, you can put in whatever string you want
[07:59] <didrocks> weird, there are set_text and set_image, but not set_data in the gtk3 C documentation
[08:01] <didrocks> <method name="set_with_data"
[08:01] <didrocks>               c:identifier="gtk_clipboard_set_with_data"
[08:02] <didrocks>               introspectable="0">
[08:02] <didrocks> that's why it's not in ^
[08:02] <rickspencer3> wtf
[08:02] <rickspencer3> *sigh*
[08:02] <rickspencer3> thanks didrocks
[08:02] <seb128> hey
[08:03] <rickspencer3> didrocks, that's too bad, because it really limits the copy functionality for an app
[08:04] <didrocks> http://git.gnome.org/browse/gtk+/commit/gtk/gtkclipboard.c?id=374e76a19dac87676995356f6daacb10f4bb6e36
[08:04] <didrocks> that's the commit limiting it ^
[08:04] <didrocks> hey seb128
[08:04] <rickspencer3> didrocks, thanks a million for pointing to those Python gi tutorials
[08:04] <seb128> lut didrocks, ca va ?
[08:05] <didrocks> rickspencer3: yw ;) /me goes back to writing tests ;)
[08:05] <didrocks> seb128: ça va bien, et toi?
[08:05] <seb128> didrocks, ca va bien !
[08:12] <rickspencer3> wow, that was really annoying, on that note
[08:12]  * rickspencer3 gets some exercise
[09:47] <seb128> pitti, hey, do you remember who had the versions' script credential?
[09:47] <seb128> pitti, Robert sent me an email "
[09:47] <seb128> The versions script seems to have lost authorization to access LP - was
[09:47] <seb128> there a trick we did to give it access to a particular user?"
[09:48] <pitti> seb128: we can just delete and recreate it, I guess
[09:48] <pitti> but I wonder why it wouldn't work with anonymous
[09:48] <pitti> oh, for accessing the upload queue, I think
[09:49] <seb128> pitti, I don't remember the details now, but at some point we did hit an acl issue IIRC
[09:49] <seb128> pitti, recreate it ... do you remember what account we used? was that the same as the retracer ones? I think you did put the acl in place by then
[09:49] <pitti> seb128: I just used mine
[09:50] <seb128> pitti, ok, I guess I can do that as well ... I guess you need to run versions on your box and copy a file over, do you remember which one?
[09:50] <pitti> seb128: no, I run it on the remote box, and then just clicked on the link that lplib prints
[09:50] <pitti> auth in firefox
[09:50] <pitti> and then it should just work
[09:55] <seb128> pitti, ok
[09:55] <seb128> pitti, thanks
[09:58] <mhr3> seb128, do all of ubuntu's binaries have buildid?
[10:02] <Sweetshark> hi there
[10:02] <seb128> mhr3, what do you call "buildid"?
[10:02] <seb128> hey Sweetshark
[10:03] <mhr3> seb128, $ file `which gedit`
[10:03] <mhr3> /usr/bin/gedit: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=0x7253aee73f4f50cdf9331f1585c605b68ad6fe40, stripped
[10:03] <pitti> mhr3: I doubt it; it was introduced not too long ago, I figure many binaries don't yet
[10:04] <pitti> but I guess everything we actually care about (because we upload it often) does
[10:04] <mhr3> pitti, i see, and is there a simple-ish way to go from the buildid to package+version?
[10:05] <pitti> none that is known to me
[10:05] <mhr3> would be swell
[10:05] <pitti> we don't keep a record of package+version -> buildid
[10:05] <mhr3> building such db shouldn't be too big of an issue though
[10:05] <seb128> mhr3, what problem do you try to solve?
[10:06] <mhr3> but i'm just thinking out loud :)
[10:07]  * Sweetshark gets a hanging build on amd64 since of late, but I am not seeing that on my local pbuilder -- any hints what might be different?
[10:08] <seb128> not really...
[10:17]  * Sweetshark loves ddwrt.
[10:19] <seb128> Sweetshark, how is lo 3.6 to quantal going?
[10:22] <Sweetshark> seb128: i have this build hanging on amd64 in the subsequentcheck, which is new and only happens on the buildd. other than that its looking fine.
[10:23] <Sweetshark> seb128: the i386 build of beta3 finished in https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-quantaltest-20120601/+build/3648270 and I will test upgrade to that one in a VM today.
[10:24] <seb128> Sweetshark, ok, great
[10:24] <Sweetshark> seb128: locally I am right now building 3.6.0~rc1 which was tagged yesterday.
[10:35] <jp_wanN> hey there, I recently read this document https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-system-compositor and now I want to try out using the new system compositor
[10:36] <jp_wanN> I've got nouveau, so that shouldn't be the problem. but could I get problems with the X-edgers ppa?
[10:41] <jp_wanN> I'll just try it, I'll reinstall my system in a few days anyway
[10:41] <jp_wanN> bye
[11:23] <didrocks> ok, session migration tool done, tests written for all modes \o/
[11:23] <didrocks> just need packaging now
[11:42] <seb128> didrocks, \o/
[12:47] <dobey> mvo: hey. why is software-center packaged without the "-0Ubuntu1" or even a "-1" but just the plain upstream version #?
[12:49] <Laney> it's a native package
[12:56] <dobey> Laney: right. but why is it built that way?
[12:57] <Laney> becaue an upstream release is a release into ubuntu, presumably
[13:00] <seb128> dobey, http://wiki.debian.org/DebianMentorsFaq#What_is_the_difference_between_a_native_Debian_package_and_a_non-native_package.3F
[13:00] <mlankhorst> getting a lot of practice with debian packaging now
[13:01] <seb128> dobey, but usually native packages are used for distro specific tools where people don't want to bother rolling upstream tarball (think ubiquity for example)
[13:01] <Laney> fakeroot mlankhorst clean
[13:04] <mterry> chrisccoulson, w000 congrats on the baby
[13:07] <seb128> Laney, btw I reconsidered a bit my position for the g-s-d and g-c-c updates I think
[13:08] <seb128> Laney, it seems easy enough to copy the ubuntu precise's code for the keyboard indicator to make an appindicator, I did a prototype in an hour yesterday, I didn't try to do a proper system indicator but it was working
[13:08] <desrt> hihi
[13:09] <seb128> Laney, so I think we can just get away with that
[13:09] <Laney> in a separate source?
[13:09] <seb128> Laney, I'm still unsure about the ibus GNOME crap though
[13:09] <seb128> and desrt "hihi" makes me want to reconsider :p
[13:09] <desrt> =)
[13:09] <seb128> I'm tired of GNOME being regression happy, I might jut suggest we stay one cycle behind starting next cycle in fact
[13:09] <Laney> why don't you start a discussion on the ml and see?
[13:10] <seb128> Laney, yeah, I'm trying to get a good view of where we stand before starting the discussion to help directing it ;-)
[13:10] <seb128> Laney, @separate source, no
[13:10] <desrt> seb128: i already told you the solution to this problem
[13:10] <seb128> desrt, hire 50 peoples to fix GNOME bugs
[13:11] <seb128> desrt, I'm not in charge of HR though :p
[13:11] <desrt> seb128: go on vacation
[13:11] <desrt> seb128: it'll be fixed when you get back :p
[13:11] <jbicha> lol
[13:11] <seb128> desrt, I doubt it
[13:11] <desrt> i don't
[13:11]  * desrt doesn't expect gnome .0 release that doesn't compile
[13:11] <seb128> desrt, there are still GNOME 3.4 annoying bugs and segfaults nobody care about, that quality issue is not going to magically solve itself
[13:12] <seb128> desrt, there are several aspect about that problem
[13:12] <seb128> desrt, they confirmed yesterday that 3.6 might have regression for some users
[13:12] <desrt> who are they?
[13:12] <seb128> desrt, the usual "let's rewrite, get 75% done, regress for 25%, and deal with those later"
[13:12] <seb128> desrt, release-team
[13:12] <desrt> cool
[13:12] <seb128> desrt, they had their meeting yesterday
[13:13] <seb128> desrt, btw they skept the nautilus discussion and the "what is GNOME"
[13:13] <mlankhorst> Laney: well I don't use fakeroot directly, just updating all the X packages for x 1.13
[13:13] <seb128> desrt, I'm very disappointed :-(
[13:13] <desrt> seb128: skipped?
[13:13] <seb128> yes
[13:13] <seb128> sorry :p
[13:13] <desrt> as in, they'll have it next meeting?
[13:13] <seb128> desrt, they just went through the non controversial features
[13:13] <seb128> desrt, they said "let's discuss it on the lists"
[13:14] <desrt> lovely
[13:14] <seb128> desrt, let's see how that goes, everybody loves list discussions :p
[13:14]  * desrt will have some interesting talks today, surely
[13:14] <desrt> seb128: where do they publish the minutes?
[13:14] <seb128> desrt, I don't know, I joined the channel to follow the meeting since I was interested in it
[13:14] <desrt> oh
[13:14] <desrt> i didn't know that was permitted
[13:15] <desrt> do you have a log?
[13:15] <seb128> desrt, people.canonical.com/~seb128/GimpNet-%23release-team.log
[13:16] <seb128> you can add http:// in front
[13:16] <desrt> seb128: this is in french!
[13:16] <Laney> https://mail.gnome.org/archives/release-team/2012-July/msg00030.html
[13:16] <desrt> seb128: in any case, i'm not too surprised
[13:16] <desrt> seb128: the release team is not a political organisation
[13:17] <desrt> i want them to be more political, but the fact is that they're not
[13:18] <seb128> right, the minutes have
[13:18] <seb128> "
[13:18] <seb128> Recent discussions about Nautilus
[13:18] <seb128> [13:18] <seb128> We'll talk about it on the mailing list. jjardon will send an email."
[13:18] <seb128> they don't mention the "what is GNOME"
[13:19] <seb128> they also didn't tool an official stance on gstreamer1 one, shrug :-(
[13:26] <seb128> desrt, shrug, that's another thing I don't like about GNOME atm
[13:27] <seb128> desrt, cf #gnome-hackers, nobody is able to tell you if GNOME 3.6 will use gstreamer0.10 or 1.0 or both
[13:27] <seb128> desrt, it's like "whatever we will ship whatever we get"
[13:27] <desrt> seb128: seems that the answer is 1.0
[13:27] <desrt> 09:23 < fredp> all signs indicate they will be ported.
[13:27] <desrt> yes, there is a possibility that it won't happen on time
[13:27] <desrt> but what do you expect?
[13:28] <desrt> this is software -- and much of it developed by volunteers, no less
[13:29] <desrt> and all of it with loose coordination
[13:29] <desrt> you're not going to get a better answer than "we'll try our best"
[13:29] <seb128> desrt, it would help to state intentions clearly, rather than waving hands and seeing "yeah, it looks like it might happen"
[13:29] <desrt> it seems like you want "it will happen, or we will punish those who are at fault"
[13:29] <seb128> desrt, nobody is saying "we will try", people just say "it seems people are working on that"
[13:30] <desrt> seb128: it's a gnome goal and they're sending an announcement to ask people to port their modules
[13:30] <seb128> desrt, like Ubuntu stated python3 only for this cycle, we might not get to it but we made it a clear public stated goal for the cycle
[13:30] <desrt> i'm not sure what else they could do?
[13:31] <seb128> desrt, let's not start on a such discussion today ;-)
[13:31] <desrt> i keep my statements about your vacation :)
[13:32] <seb128> desrt, I'm leaning on the "we should stay one release behind because there is just too much flux an bugs and uncertainty in GNOME unstable cycles"
[13:32] <desrt> there is not enough here to be getting stressed over
[13:32] <seb128> desrt, but I will push for that next cycle
[13:32] <seb128> so we have time for discussion
[13:32] <desrt> seb128: i will be there to fight you, of course :)
[13:32] <seb128> good ;-)
[13:33] <seb128> desrt, but I don't think you have strong arguments, you most summarized it "this is software -- and much of it developed by volunteers, no less and all of it with loose coordination"
[13:33] <seb128> desrt, which seems incompatible with our goals in Ubuntu about no regression, quality, etc
[13:33] <seb128> like for what we want I think it really makes sense to be one cycle behind and focus on fixing bugs
[13:33] <desrt> seb128: it seems that every cycle you're having worries and in the end things work out mostly okay
[13:34] <seb128> desrt, no they don't, we have a nightmare unstable cycle trying to keep up with regression to just reach "ok" quality at the end of the cycle
[13:34] <desrt> i don't think the quality of precise substantially suffered as a result of gnome upstream not taking quality seriously
[13:34] <seb128> desrt, when we don't finish with big revert patches and breaking gnome-shell
[13:34] <desrt> seb128: those big-revert patches are hardly gnome's fault
[13:35] <seb128> desrt, I'm not saying there is only GNOME at fault, but keeping up with the bugs and regression from the unstable cycle let us no time to deal with the integration issues like that
[13:35] <desrt> it's my understanding that compiz will be properly up to snuff this cycle
[13:35] <desrt> so we can stop mega-reverting all the gsettings stuff
[13:38] <seb128> desrt, I'm about the mega reverting the ibus stuff :-(
[13:38] <desrt> you're right.  we should stop talking about this :)
[13:45] <chrisccoulson> mterry, thanks :)
[13:49] <desrt> seb128: i went and did some research on the ibus issue
[13:49] <desrt> seb128: the patch is 2 lines and upstream has already agreed to take it
[13:50] <desrt> the maintainer was on vacation until yesterday which is why it seemed like there was no progress
[13:50] <seb128> desrt, what patch, the new minimal approch, or the "let's do dbus activation and async calls"
[13:50] <desrt> the one allowing for dbus activation
[13:51] <desrt> it's just one function call: ibus now acquires a bus name on startup
[13:51] <desrt> so now it can be bus-activated on that name (and gnome provides the service file)
[13:51] <desrt> it's a bit weird that the service file gets to be separate...
[13:51] <seb128> desrt, GimpNet-#control-center.log:juil. 11 18:51:40 <rtcm>	hadess: yes, the ibus maintainer didn't like the patches much, although I'm still going to try and convince him because it really is the most elegant way
[13:51] <seb128> desrt, that was the discussion from yesterday
[13:52] <seb128> desrt, I think you just looked at the "let's do it in hackish way until the reach patches get reviewed" ones
[13:52] <desrt> seb128: i'm looking at http://code.google.com/p/ibus/issues/detail?id=1476#c5
[13:52] <desrt> looks like everyone gets what they need
[13:53] <seb128> desrt, anyway it's not really revelant to the discussion
[13:53] <seb128> it's one of the things on the list and the one that concerns me least
[13:53] <desrt> i thought you were worried about ibus
[13:53] <desrt> well, it's one more thing you can take off your list
[13:54] <seb128> desrt, I'm worried that they dropped the gtkstatusicon and regressed for non gnome-shell session in 3.5.2 (and probably gnome-shell) as well before getting anything in place
[13:54] <seb128> desrt, I'm worried that they said they might not have time this cycle to bring back a solution for non shell sessions
[13:54] <desrt> seb128: maybe we could help
[13:55] <seb128> desrt, I'm worried that the ibus way has feature regressions or lacks we don't know about because none of us use those input methods
[13:55] <desrt> seb128: afaik this is only about configuration... we're not actually changing how the input methods work
[13:55] <seb128> desrt, and that we (desktop team, unity team) will get in trouble because it turns to be an issue for $oem at release time that we didn't detect
[13:55] <seb128> desrt, well, libgnomekbd and libxklavier got dropped, and ibus is used for keyboard layout and input methods at the same time
[13:56] <seb128> desrt, some people on d-d-l seems concerned that this integration also means you can't anymore use other input framework and it seems in some cases it's needed because ibus doesn't cover everything
[13:57] <desrt> seb128: the feature page mentions that you could disable the g-s-d backend in that case
[13:57] <seb128> desrt, there is just lot of uncertainty there and I've not enough clue about the domain to guaranty we will not regress in something that is important
[13:58] <seb128> desrt, right, mclasen pointed to rtcm that disabling the plugin would disable any keyboard integration, including stuff like compose key handling, numlock status, delay, sticky keys, etc
[13:58] <seb128> desrt, so that's far from ideal
[14:03] <bcurtiswx> is it just me or are the repos slow lately
[14:03] <bcurtiswx> my apt-get upgrade is taking a long time
[14:05] <seb128> bcurtiswx, try another mirror?
[14:06] <micahg> seb128: about the indicator-session bug, I"m not sure how to debug
[14:06] <bcurtiswx> seb128, us and main have been slow lately
[14:06] <micahg> it seems like I have a 50/50 chance of hitting it on reboot
[14:07] <seb128> micahg, printfs in the code? ;-)
[14:07] <micahg> seb128: ah, you mean programmer level debugging :)
[14:08] <micahg> seb128: ok, will try to get to it at some point
[14:08] <seb128> micahg, thanks
[14:09] <micahg> seb128: it's annoying because it causes lightdm to delay when the screen is locked by about a minute
[14:11] <seb128> micahg, there must be something special about your setup
[14:11] <seb128> micahg, we got a bug like that in the past when there was > 8 users but that got fixed
[14:11] <seb128> micahg, do you have a crazy number of users or something?
[14:12] <micahg> well, it was a system76 preinstall upgraded from maverick -> natty -> oneiric -> precise
[14:12] <micahg> which should certainly be supported, the other weird thing is I have xubuntu-desktop and kubuntu-desktop installed as well, but I'm running in unity-2d
[14:12] <bcurtiswx> micahg, theres no way anything went wrong with those upgrades! ;)
[14:15] <micahg> bcurtiswx: of course not, our release upgrades are perfect, that's why everyone can upgrade to the LTS at release...oh..wait a minute :), what's this 12.04.1 :)
[14:20] <micahg> seb128: when is 12.04.1 freeze?
[14:21] <seb128> micahg, end of july
[14:21] <micahg> seb128: as in Jul 26 or Jul 31 :)
[14:22] <Laney> https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock
[14:22] <Laney> has the dates
[14:23] <micahg> ah,was looking at the release schedule page, right, the interlock
[14:24] <micahg> ooh, even better, final freeze is Aug 16
[14:24] <seb128> micahg, like august 3
[14:24] <seb128> micahg, oh, sorry, yeah I was speaking about "desktop freeze", like for unity, libs, etc
[14:25] <seb128> micahg, the first half of august will be to get everything to settle down
[14:25] <micahg> seb128: well, I'm hoping this is bug fix level though, but yeah, I can hopefully find time before the end of the month to poke a little (don't know if that'll be enough though)
[14:44] <seb128> didrocks, mterry: is bug #949575 good to go? i.e just waiting on something to pull the package in main?
[14:44] <ubot2> Launchpad bug 949575 in gtest "[MIR] gtest" [Undecided,In progress] https://launchpad.net/bugs/949575
[14:45] <mterry> seb128, yeah it just had the wrong status
[14:45] <seb128> mterry, ok, thanks
[14:46] <didrocks> I had concerned about the "well maintained in debian" as we needed newer version and last time I checked, we were not in sync
[14:46] <didrocks> but I think it's ok for a testing tool :)
[14:51] <mpt> didrocks, hey, got a few minutes to talk about the upgrading user configuration again?
[14:55] <didrocks> mpt: hum, I'm about to have a hangout right now for an hour. I'm free afterwards
[14:55] <mpt> didrocks, ok, let's do it tomorrow
[14:57] <didrocks> mpt: sure
[17:01] <dupondje> seb128, or anyone else knowing this: the slider issue (do to hack removed in GTK+) is still affecting volume slider in g-c-c, this will get fixed soon or? :)
[17:05] <seb128> dupondje, that seems a pretty minor issue, it will be solved, the g-c-c update is blocked on compiz-gsettings to land and a few other things
[17:06] <dupondje> it is :) just needs to get fixed before october :D
[17:06] <bcurtiswx> how do most of you setup, Precise installed, Quantal VM? Quantal Installed, Precise VM? etc..?
[17:08] <seb128> bcurtiswx, multiple machines and pbuilders
[17:08] <dupondje> I'm just running quantal on my laptop :)
[17:09] <seb128> I'm working on the LTS .1 so still on precise atm
[17:09] <seb128> but usually I upgrade my work machine to the current unstable serie
[17:09] <seb128> and let my old laptop to stable
[17:09] <seb128> and I've a netbook I use for test installs and other stuff
[17:09] <seb128> vms work as well though ;-)
[17:10] <bcurtiswx> hmm, i have a 32GB flash drive USB3 that i'm buying. Is that enough to test Quantal builds on? or not recommended
[17:27] <didrocks> waow, my tests are failing when building the package, I can see no link with what is happening :)
[17:32] <didrocks> ok got it
[17:32]  * didrocks huges his testsuite
[17:33] <didrocks> so, the gboolean, when building manually (even using cmake) the source is always set to "FALSE" by default
[17:33] <didrocks> but, in the packaging environment (bzr bd), it's TRUE
[18:00]  * didrocks waves good evening
[18:58] <micahg> hi kenvandine, just wondering how you got a source package for chromium :)
[18:58] <kenvandine> a slight fix/hack for chromium-translation-tools from alex-abreu_
[18:59] <kenvandine> he is still fixing it, but will propose a branch soon
[18:59] <micahg> kenvandine: ok, great
[18:59] <kenvandine> the problem was upstream changed the xml a bit
[19:00] <micahg> kenvandine: BTW, we can't use libvpx-dev in the stable releases FWIW, so that should be reverted in the future, also why is subversion a build dep?
[19:00] <micahg> kenvandine: BTW, thanks for getting this all sorted
[19:00] <kenvandine> micahg, something in the build process runs svnversion
[19:00] <kenvandine> debian added that too
[19:01] <kenvandine> ok, we'll have to figure out how we can remove libvpx-dev
[19:01] <micahg> kenvandine: orly?  that sounds wrong...but ok, about libvpx-dev, there's a flag that was set in debian/rules to use the bundled version
[19:02] <kenvandine> ok, i'll investigate that
[19:02] <micahg> kenvandine: I'll merge everything in next week either when I pilot or later
[19:02] <kenvandine> cool
[19:02] <micahg> kenvandine: please propose merges with the changes
[19:02] <kenvandine> micahg, i did :)
[19:02] <micahg> kenvandine: thanks, I saw one, maybe my e-mail is just behind
[19:02] <kenvandine> micahg, no... it's the same branch so the MP just updated
[19:03] <micahg> ah, ok
[19:03] <kenvandine> at least we are current now :)
[19:03] <kenvandine> and it builds on all arches :-D
[19:03] <micahg> kenvandine: powerpc too?
[19:03] <kenvandine> oh... not sure about that
[19:03] <kenvandine> the PPA i was using didn't have powerpc
[19:03] <kenvandine> but armel and armhf :-p
[19:03] <micahg> ok, well, don't worry about that, it doesn't work in Debian either
[19:04] <micahg> that's great news, awesome work
[19:07] <kenvandine> micahg, thx
[19:26] <seb128> mterry, still there?
[19:27] <mterry> seb128, yup
[19:27] <seb128> mterry, bug #981062
[19:27] <ubot2> Launchpad bug 981062 in libgphoto2 "gphoto fails to download image from camera" [Undecided,Fix released] https://launchpad.net/bugs/981062
[19:27] <seb128> mterry, the changelog lacks a # between "lp: " and the bug number
[19:28] <mterry> seb128, guh, didn't notice
[19:28] <seb128> mterry, which means the bug is not listed as fixed which will screw the SRU tracking
[19:28] <seb128> mterry, can you fix it or do you want me to do it?
[19:28] <mterry> seb128, I can.  I believe that I don't have to bump the version, right?
[19:28] <seb128> mterry, just reupload, I'm rejecting the one in the queue
[19:29] <seb128> mterry, so yeah, you can reuse the same number, the queue doesn't care, you can have the same version uploaded 5 times
[19:29] <mterry> fancy
[19:29] <seb128> mterry, which is a bit annoying because it means that during freeze times you might not notice a conflict in uploads
[19:31] <seb128> mterry, btw in case you are not totally done with sponsoring, https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1022497 seems easy and is coming from the hw-enablement guys
[19:31] <ubot2> Ubuntu bug 1022497 in udisks "udisks does not support Realtek rts5992 SD/MMC card readers." [Undecided,New]
[19:32] <mterry> seb128, fixed, thanks
[19:32] <seb128> mterry, thanks ;-)
[19:32] <mterry> seb128, oh, OK.  I can pick it up
[19:32] <seb128> mterry, thanks a lot ;-)
[19:32] <mterry> seb128, thanks for the catch
[19:32] <seb128> no worry
[19:32] <seb128> I will not push my luck further but annoy the next pilot :p
[19:33] <seb128> RAOF, hey, I see you pilot tomorrow, bug #1014460 might be nice to get it, pitti acked it as a good solution for a SRU and the hw-enablement guys care about it
[19:33] <ubot2> Launchpad bug 1014460 in udev "Touchpad sometimes not working upon system startup" [High,Fix released] https://launchpad.net/bugs/1014460
[19:34] <seb128> kenvandine, if you ever get to upload chromium again please look at https://code.launchpad.net/~matttbe/chromium-browser/lp1013171/+merge/113055
[19:35] <seb128> kenvandine, it's a python3 fix for the apport hook
[19:35] <kenvandine> ok
[19:35] <kenvandine> :)
[19:35] <seb128> kenvandine, shame we missed that upload you just did ;-)
[19:36] <kenvandine> i'll probably do another one soon dropping the libvpx deb
[19:36] <kenvandine> s/deb/dep
[19:39] <seb128> kenvandine, great ;-)
[19:53] <dobey> is "screen blanking" on quantal supposed to just show a big grey rectangle as my screen?
[19:54] <mterry> pitti, is udisks going to be updated again for quantal?
[19:55] <seb128> dobey, no, what gnome-screensaver version do you use?
[19:55] <seb128> mterry, he's likely after eod, I'm sure he will be happy to get a fix in debian so we can sync if that's the question
[19:55] <seb128> mterry, especially that the coming debian release will use udisk1
[19:56] <mterry> seb128, yeah, just curious what the eta was
[19:56] <dobey> seb128: 3.4.1-0ubuntu3 is what is installed
[19:56] <seb128> mterry, likely "when there is a change requiring an upload"
[19:56] <seb128> dobey, hum, k, 3.4.2 has issues like that with our theme but didn't get uploaded, so your issue is not known
[19:57] <mterry> seb128, uploaded, with comment in bug
[19:57] <seb128> mterry, thanks!
[19:58] <dobey> seb128: hrmm. this  is a clean quantal install (i just installed it yesterday), though i copied my home directory back in from the previous install. and right now updating it is hosed due to python3 postinst breakage
[20:03] <jbicha> dobey: I get the grey/white screen-blank on screen lock too for a second or two before it shows the normal lock screen
[20:03] <jbicha> on quantal
[20:03] <dobey> jbicha: by normal lock screen you mean the unlock dialog?
[20:04] <jbicha> yeah, so it's more than a second or two
[20:05] <dobey> jbicha: this is showing me the grey when unlock dialog isn't shown (and shouldn't be). if it times out, it just goes all grey
[20:06] <jbicha> right, same here
[20:15] <dobey> jbicha: and you have the 3.4.1 package, not 3.4.2 right?
[20:18] <ricotz> dobey, this seems to be problem related to gnome-shell which gets fixed with gnome-screensaver 3.4.2
[20:18] <dobey> ricotz: this is under unity, not gnome-shell, where i'm seeing the problem
[20:20] <ricotz> dobey, ok, this is actually gnome-screensaver issue using gtk3 wrong
[20:20] <dobey> ok
[20:20] <dobey> well as long as i'm not the only one seeing it :)
[20:21] <ricotz> dobey, you can update to 3.4.2, but it is suppose to create issues with unity/light-themes afaik
[20:22] <dobey> ricotz: well i can't really update anything right now
[20:22] <dobey> python3 has foobared apt
[20:23] <dobey> anyway
[20:23] <ricotz> huh, apt isnt using python
[20:24] <mdeslaur> my quantal VM broke while updating also...the python3 package won't configure
[20:24] <jbicha> dobey: yeah 3.4.1-0ubuntu4
[20:24] <dobey> ricotz: no, it's failing to install it
[20:25] <dobey> ricotz: the postinst is broken, so lots of packages are left unconfigured at the moment as a result
[20:25] <ricotz> hmm, didnt notice anything failing to install here
[20:26] <ricotz> dobey, python3 3.2.3-2 ?
[20:26] <dobey> ricotz: yes
[20:26] <ricotz> is installed fine here
[20:26] <dobey> well lucky you then :)
[20:27] <ricotz> is probably triggered by some other python package
[20:28] <dobey> rtupdate postinst for python3 seems to be calling py3clean with wrong args


[00:17] <abentley> intellectronica: I think it would be nice if windmill tests just pushed a config value that made canonical_url return the correct port and scheme.
[00:17] <intellectronica> abentley: yeah, or they could even just decorate canonical_url to do the transformation
[00:19] <abentley> That could work too.
[00:19] <intellectronica> abentley: actually, i think the best solution is to simply have another canonical_url in the testing package, and just import it from there. that's a bit more explicit than modifying the behaviour behind the user's back
[00:20] <abentley> intellectronica: The behaviour of canonical_url is already customized in a testing context-- I think it's not surprising.
[00:21] <intellectronica> you're right, i didn't consider that it's already modified
[00:21] <intellectronica> anyway, add that to the bug. it's too late for me to fix it now but i prolly will tomorrow morning
[02:32] <thumper> mwhudson: feel like reviewing my branch?
[02:33] <mwhudson> thumper: sure
[02:34]  * thumper sends it in
[02:48] <intellectronica> who wants to review a windmill fix? it's a very easy review
[02:49] <intellectronica> gmb: awake?
[02:51] <intellectronica> mwhudson: review? it's pretty much just moving code around without change
[02:51] <mwhudson> intellectronica: ok
[02:52] <intellectronica> mwhudson: https://code.edge.launchpad.net/~intellectronica/launchpad/fix-test-mark-duplicate/+merge/13682
[02:53] <intellectronica> mwhudson: http://pastebin.ubuntu.com/297931/ if you don't want to wait for the diff to generate
[02:55] <mwhudson> looking
[02:55] <intellectronica> mwhudson: all the patch does is take the test, move it to the directory up one level, and make the test function a method of a new proper test suite
[02:57] <mwhudson> intellectronica: done
[02:58] <intellectronica> mwhudson: danke
[03:35] <mwhudson> thumper: what's the difference between test_linked_to_development_package and test_linked_to_dev_package ?
[03:35] <thumper> ?
[03:35] <thumper> where?
[03:37] <mwhudson> thumper: in your branch, lib/lp/code/model/tests/test_branch.py
[03:37] <thumper> line number?
[03:37] <mwhudson> 489 & 506
[03:38] <mwhudson> they look like different ways (yay, sigh) of saying the same thing
[03:38] <thumper> not quite
[03:38] <thumper> one uses the RELEASE pocket
[03:38] <thumper> so it is the dev focus
[03:38] <thumper> the other uses the backports pocket
[03:38] <thumper> so it definitely isn't
[03:39] <mwhudson> thumper: not that test
[03:41] <thumper> arse
[03:41] <thumper> it is
[03:41] <thumper> I thought I looked for a test that said that
[03:41] <thumper> grr
[03:41] <thumper> I can remove the duplicate
[03:42] <mwhudson> soyuz's confusatron field creeps into code :(
[03:42] <mwhudson> thumper: thanks
[04:22] <mwhudson> thumper: branch reviewed
[04:22] <thumper> thansk
[04:24] <thumper> aaaaaaaaaaaaaaaaaaaarrrrrrrrrrrrrrrrgggggggggggggggghhhhhhhhhhhhhhhhh
[04:24]  * thumper was reading wrong class
[04:24] <mwhudson> thumper: ?
[04:26] <thumper> lazr-js TextAreaEditorWidget
[04:28] <thumper> mwhudson: I've fixed the accept_empty bit
[04:28] <thumper> mwhudson: and I can live with the style id as we don't yet have descriptions for merge proposals
[04:46] <thumper> ohh
[04:48] <thumper> bugger
[04:49] <mwhudson> thumper: it sounds like you're js hacking!
[04:49] <thumper> mwhudson: look at the priv msg
[04:49] <thumper> mwhudson: that is public
[04:49] <mwhudson> hm?
[04:50] <mwhudson> thumper: oh
[04:50] <mwhudson> bugger
[04:50] <thumper> yeah
[04:50]  * thumper is fixing
[05:01] <thumper> mwhudson: there is a branch that simply moves the bmp registant ready :)
[05:02] <mwhudson> will loading the page do nasty things to my browser?
[05:02] <thumper> no
[05:03] <mwhudson> thumper: inline reviewing seems to have gone away
[05:03] <thumper> sometimes, and I don't know why
[05:04] <mwhudson> "yay"
[05:29] <thumper> mwhudson: any idea why this test doesn't fail? https://pastebin.canonical.com/23598/
[05:32] <mwhudson> thumper: wouldn't that only fail after you've fixed the bug?
[05:32] <thumper> mwhudson: which I have
[05:32] <mwhudson> thumper: oh
[05:32] <mwhudson> then i don't know
[05:32] <thumper> mwhudson: I was changing the test to show that it is fixed
[05:33] <thumper> bum
[05:33] <mwhudson> maybe extract_text is full of crack?
[05:33] <thumper> mwhudson: the web ui shows the right thing
[05:33] <thumper> it shouldn't be
[05:33] <thumper> I wrote it :)
[05:34] <mwhudson> heh heh
[05:34] <thumper> mwhudson: I found it
[05:34] <thumper> mwhudson: I'm editing the wrong buffer
[05:34] <thumper> right file
[05:34] <thumper> wrong branch
[05:34] <thumper> D'oh
[05:34] <mwhudson> lolz
[05:41] <thumper> just did it again for the fix :(
[05:46] <thumper> mwhudson: want to review the v.small fix?
[05:47] <mwhudson> thumper: sure
[05:49] <thumper> mwhudson: just waiting on the diff
[05:51] <thumper> mwhudson: you should have it now
[05:52] <mwhudson> thumper: please get spm to cowboy the template fix?
[09:47] <allenap> Morning jtv :)
[09:47] <jtv> allenap: morning!
[09:47] <jtv> allenap: oh, I already did danilo's.  All the other ones on the queue were for me.  :-)
[09:50] <allenap> jtv: Okay, I'll do yours then. There's one from jelmer too, for launchpad-cscvs, but I think I might leave that for someone who's more familiar with vcs stuff than me.
[09:50] <jtv> allenap: I can try that one then.  Hadn't seen it appear.
[10:18] <adeuring> jtv: may I bother you with an MP having an overly long diff? 1000 lines, but mostly mechanical changes. Only ~130 lines are "real" changes.
[10:19] <jtv> adeuring: ok
[10:19] <adeuring> jtv: thanks!
[10:20] <jtv> adeuring: it's the new-attempt one?
[10:21] <adeuring> jtv: no, this branch: lp:~adeuring/launchpad/hwdb-build-udev-device-list-2 . Need to write the mp
[10:33] <adeuring> jtv: https://code.edge.launchpad.net/~adeuring/launchpad/hwdb-build-udev-device-list-2/+merge/13695/comments/35227/+reply
[10:34] <adeuring> erm, scrap that "+reply"; want to add the test command and the "make lint" output
[10:34] <jtv> adeuring: ok
[10:37] <adeuring> jtv: https://code.edge.launchpad.net/~adeuring/launchpad/hwdb-build-udev-device-list-2/+merge/13695 , that's what i menat.
[10:37] <jtv> adeuring: I had arrived there yes, thank you :)
[10:43] <jtv> adeuring: I do think it's a bit ugly to do self.devices = devices = {}
[10:43] <adeuring> jt: why?
[10:43] <jtv> The "shorthand" of saying devices instead of self.devices doesn't even save you much here.
[10:44] <adeuring> well it saves one word -- "self" ;) But I'll remove the local variable
[10:44] <jtv> When I read that line, I have to worry: do you really mean two references to the same dict, or is it a mistake?
[10:44] <jtv> Thanks.
[10:48] <jtv> adeuring: in the hwdb_submission_processing test, SubmissionParserFakedBuildDeviceList is a bit long as a name.  How about MockSubmissionParser?
[10:48] <adeuring> jtv: Sure
[10:49] <jtv> Good testing technique, btw.  I sometimes use the real object and just inject a callable mock object in place of a method, but if you can get away with something short and sweet like this, great.
[10:51] <adeuring> jtv: the problem with mock ojbects here is that it such data would probably look quite ugly and convoluted. The test file has many examples of this ;)
[10:53] <jtv> adeuring: in test_processSubmission_buildDeviceList_failing it might be useful though.
[10:53] <adeuring> jtwhy?
[10:53] <jtv> def no(*args, **kwargs):
[10:53] <jtv>     return False
[10:53] <jtv> #...
[10:53] <jtv> parser.buildDeviceList = no
[10:54] <jtv> adeuring: that saves you a lot of long identifiers (though "no" may be a bit too short :-)
[10:55] <adeuring> jtv:  question is what sort of test styles we prefer. I another review I got the recommendation to avoid monkey-patching ;)
[10:56] <adeuring> jtv: personally, I don't mind much, btu we should be consistent ;)
[10:56] <jtv> adeuring: IMHO, only when there's a clear winner among the options.  :-)
[10:57] <adeuring> jtv: well, as I said, I really don't mind. So, you think I should use a method like "nyet(...)"?
[10:57] <adeuring> ...oder "nein()"
[10:58] <jtv> adeuring: in this case I think it's justified.
[11:00] <adeuring> jtv: OK, changed.....
[11:02] <jtv> adeuring: approved
[11:02] <adeuring> jtv: thanks!
[11:02] <jtv> macht nix
[12:08] <leonardr> jtv, allenap: https://code.edge.launchpad.net/~leonardr/lazr.restfulclient/264098-eq-ne/+merge/13697
[12:10] <allenap> leonardr, jtv: I can take that.
[12:24] <jtv> allenap: thanks, some very nice suggestions there.  And the one hard-to-document parameter turned out to be unused.  :)
[12:25] <allenap> jtv: Woohoo :)
[12:38] <allenap> leonardr: You have tests for recipe.__hash__(), but there is nothing in the diff that defines the __hash__ method.
[12:39] <leonardr> allenap: i'm using the default python object implementation
[12:39] <leonardr> it was the only way i could think of to show that these two python objects were different
[12:39] <leonardr> but i'm probably missing something obvious
[12:39] <allenap> leonardr: Okay. You could say recipe is recipe2 and expect False.
[12:39] <leonardr> ok
[12:39] <leonardr> that's nice and obvious
[12:40] <danilos> jtv: got another one for you ;) https://code.edge.launchpad.net/~danilo/launchpad/bug-455771/+merge/13699 (diff should be regenerated any minute now)
[12:40] <jtv> give them a finger and they want the whole hand...
[12:46] <danilos> jtv: that's how it works :)
[12:46] <danilos> jtv: anyway, the diff is there now
[12:46] <jtv> sigh.  Coming...
[12:46] <jtv> (for the public record: not serious :)
[12:50] <jtv> danilos: I'm too lazy to look it up, but you have a conditional top-portlet now.  Won't that upset your layout when the div is not shown?
[13:06] <danilos> jtv: nope
[13:07] <jtv> danilos: too late; it's already in the mp.  :-P
[13:16] <leonardr> jtv, allenap: and now, https://code.edge.launchpad.net/~leonardr/lazr.restfulclient/verbose-http-error/+merge/13702
[13:16] <jtv> leonardr: sorry, I'm just eod'ing (and in standup)
[13:17] <leonardr> np
[13:20] <jtv> allenap: bowing out.  Have a good one!
[13:50] <leonardr> allenap, can you look at the branch i linked above?
[15:00] <allenap> jtv: Cheerio :) I'll review your bug #417968 branch now.
[15:00] <mup> Bug #417968: Auto-approver: pathless template with unique name <import-queue> <Launchpad Translations:In Progress by jtv> <https://launchpad.net/bugs/417968>
[15:57] <leonardr> allenap, edwin: please review https://code.edge.launchpad.net/~leonardr/lazr.restful/fix-media-type-misspelling/+merge/13711
[15:59] <allenap> leonardr: I'm on it.
[16:07] <allenap> leonardr: r=me
[16:44] <leonardr> allenap: and the follow-up: https://code.edge.launchpad.net/~leonardr/lazr.restfulclient/fix-media-type-misspelling/+merge/13715
[16:44] <allenap> leonardr: Okay.
[16:46] <allenap> EdwinGrubbs: Do you have much VCS-fu? There's a proposal from Jelmer for launchpad-cscvs, https://code.edge.launchpad.net/~jelmer/launchpad-cscvs/converted-from/+merge/13542
[16:51] <jml> allenap, Were I you I'd politely ask abentley to review that one.
[16:52] <allenap> jml: Okay.
[16:53] <allenap> abentley: Please can you have a look at Jelmer's launchpad-cscvs proposal, https://code.edge.launchpad.net/~jelmer/launchpad-cscvs/converted-from/+merge/13542 :)
[16:53] <abentley> jml, allenap: rockstar volunteers.
[16:53] <rockstar> allenap, I can take it.  I'm one of the few who have actually braved cscvs.
[16:53] <rockstar> And I like abentley too much to expose him to that.
[16:53] <allenap> rockstar: Awesome :)
[16:54] <jml> rockstar, yay
[16:59] <allenap> leonardr: r=me, with a question/suggestion.
[17:00] <leonardr> that's not a bad suggestion
[17:15] <EdwinGrubbs> allenap: I don't think I'm qualified to review that.
[17:17] <allenap> EdwinGrubbs: Sorry, rockstar took it already, shortly after I asked you.
[17:17] <allenap> EdwinGrubbs: I should have said something :(
[17:17] <EdwinGrubbs> allenap: well, I was having networking issues anyway.
[17:57] <leonardr> jml, are you around?
[17:58] <jml> leonardr, yes.
[17:58] <jml> leonardr, how can I help?
[17:58] <leonardr> i'd like your opinion on a branch i've written to address bug 319432
[17:58] <mup> Bug #319432: RelativeURIError when trying to access an redacted object <api> <tech-debt> <launchpadlib :Triaged by leonardr> <https://launchpad.net/bugs/319432>
[17:59] <leonardr> i'm writing an mp now
[18:00] <jml> leonardr, my opinion is always available :)
[18:03] <leonardr> jml: https://code.edge.launchpad.net/~leonardr/lazr.restfulclient/319432-redacted/+merge/13716
[19:06] <leonardr> edwin, would you look at https://code.edge.launchpad.net/~leonardr/lazr.restfulclient/319432-redacted/+merge/13716 ?
[19:52] <bac`> beuno: you around for some ui questions?
[19:53] <beuno> bac`, sure
[19:53] <bac`> beuno:  great.  i'm working on bug 419742.  (hey i like my jaunty little reverse grave.)
[19:53] <mup> Bug #419742: downloads page should include some data about the releases <post-3-ui-cleanup> <Launchpad Registry:In Progress by bac> <https://launchpad.net/bugs/419742>
[19:54] <bac`> salgado had made some changes coming up with http://launchpadlibrarian.net/30906325/download.png
[19:55] <bac`> i've been trying to work in poolie's other comments and have gotten this:
[19:55] <bac`> http://people.canonical.com/~bac/download.png
[19:55] <bac`> beuno: i was hoping you could give me some ideas if i'm on the right track
[19:56]  * beuno looks
[19:57] <bac`> beuno: i've made the 'release notes' optional, added 'changelog' and made it optional and collapsible,  and moved the date out there to the right.
[19:57] <bac`> oh, added more vertical separation between the sections
[19:58] <beuno> vertical separation == awesome
[19:58] <bac`> unbolded "Release notes:"
[19:58] <beuno> the label/value there is unclear
[19:58] <bac`> for RN?
[19:58] <beuno> yes
[19:58] <bac`> you mean you want the bold back?
[19:59] <bac`> what do you think about the twisty hanging out to the side of changlog?
[19:59] <beuno> well, it seems to be the standard everywhere else, so yes for the bold
[19:59] <bac`> ok, <b>RN and CL
[20:00] <beuno> so, I like the idea
[20:00] <bac`> it used to say "There are no release notes" but i just got rid of the section if they aren't there
[20:00] <beuno> that's great
[20:00] <bac`> cool
[20:00] <beuno> the changelog, we don't show any of it, right?
[20:00] <bac`> not unless they twist
[20:00] <bac`> then it slithers in
[20:01] <bac`> and you're ok with the release date hanging out to the side of the h2?
[20:01] <beuno> ok, so it's not really "the full changelog" as much as the "the changelog"
[20:02] <beuno> I like what you did there in the h2, yes. I'd like to see it in staging with real data, but it's nice
[20:02] <bac`> beuno: oh, right.  i c-n-p that part.  didn't notice the text
[20:02] <bac`> beuno: great.  i'll ask poolie later if this meets his concerns
[20:03] <beuno> bac`, I'd just say "> Changelog"
[20:03] <bac> ok
[20:04] <beuno> I don't know about the date on the right though
[20:04] <beuno> seems too disconnected
[20:04] <beuno> and
[20:04] <beuno> infally
[20:04] <beuno> the "add download for release" is odd
[20:04] <beuno> why not just below each release?
[20:05] <bac> ok a '(+) Add download file' to the right below the table
[20:05] <beuno> yes, right-aligned
[20:05] <beuno> and you win
[20:06] <bac> great!  thanks for the suggestions
[20:12] <bac> beuno: what would you think about putting each release into a portlet to give them more separation from one another?
[20:13] <beuno> bac, it sounds good. Can you mock it up cheaply so we can look at it?
[20:13] <bac> done.  let me snap it and scp
[20:14] <bac> http://people.canonical.com/~bac/download2.png
[20:14]  * beuno waits
[20:15] <bac> this does not have the first one marked as 'top-portlet' as that will require some reorganization of the template
[20:18] <sinzui> EdwinGrubbs: do you have time to review https://code.launchpad.net/~sinzui/launchpad/package-link-validation-2/+merge/13727
[20:18] <EdwinGrubbs> sinzui: sure
[20:37] <EdwinGrubbs> sinzui: I don't understand what it means that "the distroseries should also be linked". Is that a link on the page, or should the distroseries be linked with the productseries in the db?
[20:54] <EdwinGrubbs> sinzui: I get an error when I try to link "mozilla-firefox" on this page https://launchpad.dev/firefox/trunk/+ubuntupkg
[20:55] <EdwinGrubbs> sinzui: Even if the error is correct, the message should be on the field instead of having two errors above the form.
[21:03] <sinzui> ha
[21:03] <sinzui> EdwinGrubbs: I bet the example is bad sample data
[21:04] <sinzui> EdwinGrubbs: on edge +ubuntupkg has a table listing the distroseries and sourcepackage, but they are not linked. You need to hack the URL to see the object that the series is linked too
[21:06] <sinzui> EdwinGrubbs: https://launchpad.dev/firefox/+packages
[21:06] <sinzui> ^ See, that is why this view is broken, you just tried to create a duplicate link. Another series (0.9)  is already the source pacakge
[21:08] <sinzui> EdwinGrubbs: did you notice that the error message had a link to the package: https://launchpad.dev/ubuntu/hoary/+source/mozilla-firefox
[21:08] <sinzui> ^ That shows that 1.0 is in fact the upstream for mozilla-firefox
[21:10] <sinzui> EdwinGrubbs: So for trunk cannot be the upstream for warty or hoary because those SPs are already linked. You can make grumpy Frozen there by making it the currentseries, then you can try to link trunk to mozilla-firefox
[21:17] <EdwinGrubbs> sinzui: It still seems like PackagingAddView.validate() should use setFieldError() instead addError(), or the separate "There is 1 error" message shouldn't appear.
[21:18] <sinzui> EdwinGrubbs: I think you are right
[21:20] <sinzui> EdwinGrubbs: my last addition to the base class does use setFieldError. The original code did not. I can quickly fix the whole class
[21:21] <sinzui> EdwinGrubbs: oh I see
[21:21] <sinzui> EdwinGrubbs: This is a bit tricky
[21:22] <sinzui> EdwinGrubbs: In the base class we do not know if there error is the series or the sourcepackage. In the new class, we know for certain that the error is sourcepackage.
[21:23] <sinzui> EdwinGrubbs: I could verify if the default_distroseries is not None and choose setFieldError()
[21:25] <EdwinGrubbs> ok
[21:27] <EdwinGrubbs> sinzui: It also seems strange to me to call packaging_util.packagingEntryExists(), when a single call to Packaging.selectOneBy() would allow you to make both checks, and it would allow you to say which productseries is already linked to the source package.
[21:27] <sinzui> It is not
[21:27] <sinzui> There are two issues and one is easier to fix than the oser
[21:27] <sinzui> other
[21:28] <EdwinGrubbs> sinzui: can there be multiple packaging entries for the same sourcepackagename and distroseries?
[21:29] <sinzui> The specific match probably means the *you* made a mistakes and you can fix it. The other error is someone else and you may want to investigate before making the chage
[21:29] <sinzui> No, but there are 81 in production
[21:30] <sinzui> Users trying to fix the data from the dsp, sp, p, or ps views are getting oopes as they struggle to fix the data
[21:31] <sinzui> EdwinGrubbs: a hack was put in place two years ago where we recognised this happens, but we only show the last one. this compounded the error because you cannot see the shadowed link to know it exists. the user is trying to add the link when he should be deleting the one he is seeing
[21:31] <sinzui> Except we never wrote code to delete a link to an SP
[21:32] <sinzui> There are a lot of oops that revolve around the the root cause that we let multiple links be created
[21:33] <sinzui> EdwinGrubbs: when this branch lands, it will not be possible to create a duplicate link, We can then fix the schema to not allow it to happen. My next branch is to allow the deletion on links to SPs
[21:34] <EdwinGrubbs> sinzui: is there a bug open to add a unique constraint on (distroseries, sourcepackagename) on the packaging table?
[21:34] <sinzui> Yes, it is on our list of bugs in progress that we review every morning
[21:35] <sinzui> https://bugs.edge.launchpad.net/bugs/196774
[21:35] <mup> Bug #196774: It shouldn't be possible to link multiple productseries to a sourcepackage in a given distroseries <package-link> <Launchpad Registry:In Progress by sinzui> <https://launchpad.net/bugs/196774>
[21:35] <EdwinGrubbs> doh
[21:35] <EdwinGrubbs> sinzui: ok, that answers my questions. I'll send off the review in a sec. There are just minor style issues.
[21:36] <sinzui> okay.
[22:16] <sidnei> alright!
[22:16] <sidnei> Edwin-food: add https://code.edge.launchpad.net/~sidnei/lazr-js/yui-3.0.0/+merge/13737 to your queue when you get back
[22:18] <sidnei> uhm. i don't know how to get a proper diff i fear.
[23:01] <sidnei> EdwinGrubbs: ok, ignore that mp, take this one: https://code.edge.launchpad.net/~sidnei/lazr-js/yui-3.0.0-redux/+merge/13743
[23:02] <EdwinGrubbs> sidnei: what happened?
[23:02] <sidnei> EdwinGrubbs: the order i merged the two base branches made it hard to generate a meaningful diff
[23:02] <sidnei> EdwinGrubbs: this one has a link to a paste with the right diff.
[23:12] <EdwinGrubbs> sidnei: how did you create the diff? I would like one that ignores whitespace changes, so I can focus on what really changed.
[23:13] <sidnei> EdwinGrubbs: bzr diff -rancestor:../jstestdriver-support
[23:13] <sidnei> EdwinGrubbs: and then prune the 10k lines of the new YUI :)
[23:14] <sidnei> and the yui-patch.js file, which is copied verbatim from upstream jstestdriver
[23:14] <sidnei> i guess i need --diff-options
[23:22] <EdwinGrubbs> ugh
[23:25] <sidnei> yeah, ugh :(
[23:34] <EdwinGrubbs> sidnei: don't worry about getting a new diff, I see why diff was showing me more lines than I thought it should. You moved some javascript from the top of the file to the bottom. I'll handle that change.
[23:34] <sidnei> ok, thanks!
[23:39] <sidnei> EdwinGrubbs: i need to go to a funeral, but will be back in a bit. have fun!
[23:39] <EdwinGrubbs> sidnei: I'm sorry to hear that.
[23:40] <sidnei> EdwinGrubbs: yeah. not a close person, but it sucks anyway. im happy as long as isn't mine *wink*


[03:31] <UbuntNOOB> Enter text here...
[03:31] <UbuntNOOB> Hello
[03:31] <UbuntNOOB> I could use some help...
[03:31] <bazhang> hi
[03:31] <bazhang> UbuntNOOB, with what
[03:32] <UbuntNOOB> Well, I just got a dual boot XP-Ubuntu set up this afternoon
[03:32] <UbuntNOOB> Everything is working fine except...
[03:32] <UbuntNOOB> THE INTERNET
[03:32] <bazhang> #ubuntu for support
[03:32] <UbuntNOOB> *Dramatic music*
[03:32] <UbuntNOOB> Oh...
[03:32] <UbuntNOOB> I see...
[03:32] <UbuntNOOB> So you dont love me?
[03:32] <UbuntNOOB> :(
[03:32] <UbuntNOOB> Ta ta then, ol' chaps
[11:21] <fahadsadah> mirek is being abusive in #ubuntu
[11:21] <fahadsadah> Has just quit
[13:45] <c0p3rn1c> are there stats recorded on how many users there where in #ubuntu ?
[13:46] <Tm_T> all-time highs might be up somewhere
[14:08] <ninnnu> A question about OperatorGuidelines... "When to kick/ban people". Is "kick" used as in /kick or as a synonym of remove? I know the difference between kick/remove isn't very significiant, but I'd like to have a clarification.
[14:14] <ziroday> ninnnu: its up to the operator mainly, most use /remove as that tends to outwit the auto-rejoin scripts
[14:15] <ninnnu> So it's just "just remove from channel without ban", k
[21:17] <mesula> popey thinks I'm Scott.
[21:17] <popey> i kick/banned mesula because I believe mesula to be Scott-NotAFK who has a long standing ban in numerous channels, including -uk
[22:47] <Ddorda> i want to change mail address to all the ubuntu mailing lists, is it possible?
[22:57] <popey> yes
[22:58] <popey> to go lists.ubuntu.com and choose any mailing list you're on, logon with your email address and password
[22:58] <popey> there is an option to change email address, and do it globally


[11:44]  * gary_poster having bluetooth mouse trouble
[11:45] <benji> sounds like a disney character; mickey's pirate cousin
[11:50] <gary_poster> :-)
[11:53]  * gary_poster going to try a restart
[11:57] <gary_poster> all bettah
[12:00] <gary_poster> hey benji, congrats on moving the translations card!  Are you going to follow through with danilos' review suggestion, or just file another bug?
[12:01] <benji> gary_poster: I was going to leave that to you.
[12:01] <benji> I've spent so much time on this, I'm hesitant to keep going, but Danilo has a good point.
[12:02] <gary_poster> benji, you're the dev, your call.  :-)  I'm happy to try to formulate an opinion though.  If you wanted me to, my first question would be "how much more time will it be?"
[12:02] <benji> Don't tell anyone, but right now a flight from here to Boston for the middle of september is $53.
[12:02] <gary_poster> bah :-)
[12:02] <benji> (round trip)
[12:02] <gary_poster> I CAN'T HEAR YOU
[12:02] <danilos> benji, I wouldn't be complaining if this was one of the rare interfaces that we actually put an effort to clean up in the former Translations team
[12:03] <danilos> s/this was/this wasn't/
[12:03] <benji> wait, I was wrong, that's the first leg, it's about $120 total
[12:03] <benji> heh
[12:04] <danilos> benji, so that's the only reason I am remarking this :) not too big a deal, though
[12:04] <benji> re. "how much more time will it be?": I've struggled enough to get this "side" of the query right that realistically I'd say 2 days.
[12:05] <benji> danilos: yep, I definately see your point
[12:05] <danilos> benji, it's not my say, but I'd say you shouldn't worry about it then :)
[12:05] <danilos> (re 2 days estimate)
[12:05] <gary_poster> benji, danilos, @ two days I don't think it is worth the cost, but I repeat that it is your call benji
[12:05] <gary_poster> (@two weeks I'll make the call ;-) )
[12:06] <danilos> heh :)
[12:06] <benji> Sold, American!  (i.e., I'll file a bug and move on)
[12:08] <gary_poster> :-)
[12:16] <gmb> gary_poster: Thanks for fixing lazr.restful. v 0.19 is now released and in the download-cache; a branch to make LP depend on it is in EC2.
[12:21] <gary_poster> gmb yw.  Odd that it hadn't been caught before, but an easy fix once I understood it.
[12:27] <bac> benji: was that a Kinky Friedman reference?  ^^
[12:29] <benji> bac: not quite, he was referencing (obliquely) the old Lucky Strike radio show which featured a tobacco auctioneer which ended the show with "Sold, American!" which is what real auctioneers said when the American Tobacco Company won a tobacco auction
[12:30] <benji> (the American Tobacco Company made Lucky Strike cigarettes)
[12:30] <bac> ah, i never knew where that song title came from
[12:31] <bac> i was just looking forward to more KF quotes here.  darn.
[12:32] <benji> heh
[12:32] <gary_poster> oh bah
[12:33] <gary_poster> bac benji danilos gmb: sorry, was helping henninge.  call now-ish
[12:43] <bac> danilos: did you see the messages left here for you after your EOD yesterday?
[12:43] <bac> didn't know if that was effective or if i should send email
[12:46]  * bac -> feeds stupid neighbor's dumb cat
[12:47] <gary_poster> heh
[12:52] <bac> gary_poster: you'll be missing the final TriZPUG at CCC tonight
[12:52] <gary_poster> bac, why final?
[12:52] <danilos> bac, I did, yes, I took care of a bunch of translations-related questions
[12:53] <bac> CCC goes out of business soonish
[12:53] <bac> maybe more soonish than he thinks
[12:53] <danilos> bac, some which need further investigation are only assigned to me, but I hope to get to them tomorrow
[12:53] <gary_poster> bac :-( :-( :-(
[12:53] <gary_poster> bac, just not making enough money?
[12:53] <bac> danilos: ok.  i just wanted to know that was an effective way to leave you messages after you EOD-ed
[12:53] <bac> gary_poster: yep
[12:53] <gary_poster> I see
[12:53] <gary_poster> dang
[12:53] <danilos> bac, yep, it works, especially on the #yellow channel which doesn't see much traffic
[12:54] <gary_poster> I was hoping that coworking locations would get more traction, not less
[13:00]  * danilos -> food
[13:20] <gmb> gary_poster: CHR run done (some open questions about which I'm pinging peopel)
[13:21] <gary_poster> gmb, cool, thanks for ping.  I'll switch to it after our call then.
[13:30] <gary_poster> gmb, ready when you are.    Hadn't forgotten; trying to wrap something up.  another min or two then ready
[14:34] <danilos> ack
[15:09] <gary_poster> danilos, on https://translations.launchpad.net/+imports/+index?field.filter_target=[PRODUCT]&field.filter_status=NEEDS_REVIEW&field.filter_extension=pot I see three translations from 07-25 that are still in needs review.  does that mean that somethng manual needs to happen?  If so, can I do it, whatever it is?
[15:09] <danilos> gary_poster, mrevell asked me to leave those in so he can make a screenshot for the announcement
[15:09] <gary_poster> danilos, heh ok :-)
[15:10] <danilos> gary_poster, he also promised to do them when he is done, I'll check up with him :)
[15:10] <gary_poster> danilos cool :-)
[15:12] <gary_poster> danilos, do I assign requests for a new language (crazy professors with their made up languages :-) ) to the launchpad-translations-coordinators?
[15:13] <danilos> gary_poster, nope, we used to have a FAQ about new languages, but in short, we create all languages which have a proper ISO 639 (-1, -2 or -3) code in
[15:14] <gary_poster> danilos, "Its ISO 639-3 code is lfn."
[15:14] <gary_poster> danilos, assign to you? :-P
[15:15] <gary_poster> danilos, also going to assign "French translation does not export properly for miro due to launchpad corruption" to you
[15:15] <danilos> I thought I responded to that :/
[15:16] <danilos> gary_poster, for the languages, https://answers.launchpad.net/launchpad/+faq/619, useful for non-rosetta LP developers
[15:17] <gary_poster> danilos, looks good, looking further.  For question: they replied with more info.  You can look at it tomorry.
[15:18] <danilos> ah, ok
[15:34] <gary_poster> bac we have a private proprietary project from Canonical Hardware Enablement Team  in the project review queue.  Can I just mark it as reviewed and move on?
[15:35] <bac> gary_poster: do they need to be voucherized?
[15:35] <bac> pass me an url and i'll take care of it
[15:35] <bac> though they usually make a request to feedback
[15:35] <gary_poster> bac https://launchpad.net/hwe-merge thanks
[15:49]  * gary_poster going to take lunch with very patient younger son
[17:32] <benji> gary_poster: coordination time
[17:32] <gary_poster> thanks benji.  one sec, lemme finish up what I'm up to.
[17:38] <bac> CHRs
[17:44] <bac> benji: projects registered with "I don't know yet" should get an email automatically from LP-proper.  no script.
[17:45] <benji> bac: did that one I wrote on the whiteboard ever get an email?  or is it done at registration time and for some reason that one didn't get one?
[17:46] <bac> benji: unknown.  i wonder if they registered and then later changed to IDK, which may not send an email
[17:46] <benji> I'd wondered the same thing.
[17:46] <bac> not a common use case i should think
[17:46] <bac> i'd say if there was not auto-generated whiteboard message then there was no email sent
[17:46] <benji> Murphy's law and all that
[17:47] <gary_poster> benji, 15 min is longer than a sec.  I'm going to try and do it.  If it runs past 2:30, I'll pass it to you.  Sound OK?
[17:47] <benji> gary_poster: sure; it may bleed into my CHR time, but that's not a big deal
[17:47] <gary_poster> ack benji
[18:00] <bac> chr done.  woo.
[18:02] <benji> nice
[18:30] <gary_poster> bac, ready whenever you are
[18:30] <bac> ok
[18:30] <gary_poster> (so Skype me when you want)
[19:00] <benji> CHR time for me
[19:05] <benji> I'm going to leave that RT reply for Graham to look at because he knows what's going on.
[19:23] <benji> done with CHR
[19:28] <gary_poster> yay!
[19:28] <gary_poster> ("done with CHR")
[19:35] <gary_poster> benji, just saw this when trawling about: "ConjoinedMaster = ClassAlias(BugTask, 'ConjoinedMaster')"
[19:35] <gary_poster> I think that's how you use the same class multiple times in the same Storm query
[19:35] <gary_poster> (ClassAlias)
[19:35] <benji> gary_poster: yeah, I've been meaning to tell you that Danilo pointed me at ClassAlias, it was exactly what I needed.
[19:36] <gary_poster> ah cool
[20:04] <gary_poster> benji ready whenever you are
[20:19] <gary_poster> https://chinstrap.canonical.com/~orefai/lp-prod-arch-2011-04-19.png