[02:59] <ctcb> Hi all...
[03:10] <pitti> Good morning
[03:15] <mfisch> hey mhall119 you around?
[03:15] <mhall119> kinda
[03:15] <mhall119> what's up?
[03:16] <mfisch> mhall119: I was looking at the popcon merge, is the server still non-functional?
[03:19] <mhall119> mfisch: if you look at the table at the bottom of http://popcon.ubuntu.com/
[03:19] <mhall119> there are non-architectures in the architectures statistics
[03:19] <mfisch> like dpkg
[03:19] <mfisch> and "Here" ;)
[03:19] <mhall119> yeah
[03:20] <mhall119> I have 1.21 GHz Here processor :)
[03:20] <mfisch> okay, but it's not 100% non-functional, just a bit screwed up
[03:20] <mhall119> I think so, I'm not to familiar with what is supposed to be there
[03:20] <mfisch> ok
[03:20] <mfisch> I'll test out the new version
[03:20] <mhall119> but pabs from debian pings me about it, because evidently they use the data for something
[03:20] <mfisch> I think it reports 1 extra field and so I'll see what happens when I use it
[03:22] <mhall119> thanks
[03:23] <mhall119> hey mfisch, I may need to write an online-accounts provider in the next couple weeks, can I ping you if I need help?
[03:24] <mfisch> sure, but I Think cwayne did that not me
[03:24] <mfisch> for fitbit
[03:24] <mhall119> I thought you guys did it together
[03:24] <mfisch> he did the accounts thingy and I wrote the piece that used it
[03:24] <mhall119> ah, ok
[03:24] <mfisch> but its part of our team charter to support stuff like that so please ping us
[03:24]  * mhall119 goes to work for lead developer cwayne
[03:25] <mfisch> oh hey mhall119 when is the dash going to work on the phone?
[03:25] <mhall119> it does, kinda
[03:25] <mhall119> search on the Home lens is disabled intentionally, I was told, because it'd be too slow right now if you tried to use it on a device
[03:26] <mhall119> Saviq can tell you more though
[03:27] <mfisch> thanks
[03:28] <mfisch> mhall119: how can I tell that pop-con uploaded successfully?
[03:28] <mfisch> do you have logs there or would there be an obvious failure
[03:28] <mhall119> I have no idea, sorry
[03:33] <mhall119> mfisch: man, I make a personal introduction and he sends you to a mailing list, that's cold
[03:33] <mfisch> yeah, oh well ;)
[03:33] <mfisch> thanks
[03:34] <mfisch> This feature was "Suggested by Paul Wise."
[03:34] <mfisch> I just want to make sure it doesn't break your server
[03:35] <mhall119> my server?
[03:35] <mfisch> I mean popcon.ubuntu.com
[03:35] <mhall119> ah, ok
[03:36] <mhall119> really, I only cared about it because folks in debian did
[03:36] <mhall119> and I was working to help them
[03:36] <mfisch> well I told seb that I didn't want to merge this until I knew it was safe
[03:36] <mfisch> but it's becoming more trouble that it's probably worth
[03:37] <mhall119> :/
[05:06] <didrocks> good morning
[05:43] <Mirv> didrocks: I added a new item to our task list, a largish precise SRU needed
[05:44] <didrocks> Mirv: excellent, do you have time to handle it or need someone else to do it?
[05:45] <Mirv> didrocks: I'm trying to handle it to an extend today/tomorrow, but whatever is left undone will need to be handled by eg. sil2100 then
[05:45] <Mirv> didrocks: I'm again in a situation that I've tons of stuff to do, and I'm unsure of the ordering :)
[05:45] <Mirv> didrocks: in good news, I solved armhf build failures with switchin to g++-4.7 for armhf temporarily
[05:46] <Mirv> didrocks: so qtwebkit is ready to upload (soon, with mitya57's changes merged)
[05:46] <Mirv> didrocks: and I should ping you about Qt Creator as well (hey I just did that), it should be ready for your eyes as well
[05:46] <Mirv> since it also failed on armhf, but succeeded now during the night with g++-4.7
[05:46] <didrocks> Mirv: ah, great! please copy the link in the spreadsheet :)
[05:47] <didrocks> Mirv: can you quiclky do (it should take few minutes) the publication of the day for your stacks?
[05:47] <didrocks> so that it's in latest phone imag?
[05:47] <didrocks> image*
[05:47] <Mirv> didrocks: ah yes that, doing that now, then trying to put all the needed links and branches in and then I'll ping you again, and then continue with the precise SRU
[05:49] <didrocks> Mirv: perfect, thanks!
[05:49]  * didrocks cleans the spreadsheet at the same time
[05:51] <Mirv> didrocks: as platform is in manual publishing mode, I'd need an ack from you for that. the packaging changes seem fine for me. location-service change was done by you so I guess that's an 'ack', and then there's powerd.
[05:52] <didrocks> Mirv: indeed, I did that change, so I can only +1 I think :p powerd is looking good (less hacks \o/)
[05:54] <didrocks> Mirv: can you send an email then to the SRU team for the xim support in precise? I think they would prefer to open the discussion before the raring upload
[05:54] <didrocks> precise*
[05:58] <Mirv> stacks published
[05:58] <Mirv> didrocks: ok
[05:59] <didrocks> Mirv: thanks!
[05:59]  * didrocks is handling the raring SRU quickly
[06:25] <veebers> didrocks: ping
[06:25] <didrocks> veebers: pong
[06:26] <veebers> didrocks: how's things going? o/ Hey I'm interesting in using otto in a similar jenkins jobs setup to what the Unity autopilot or Autopilot daily jobs are doing to replace an old non-working job of mine
[06:26] <veebers> didrocks: I'm hoping you can point me in the right direction
[06:26] <veebers> didrocks: specifically the job should grab an unity branch, build the packages and install them then run the unity autopilot tests over them (where the branch that is built and installed is a parameter)
[06:27] <veebers> didrocks: although, initially the branch doesn't have to be a param, I can hardcode it as I'm more interested in the one off right now
[06:28] <didrocks> veebers: what are you trying to do with this? I'm wondering why we would need to yet build another time the same sources we have instead of using validated version?
[06:29] <veebers> didrocks: the reason is I had this job [1] that built a 'custom' version of unity so that a developer could test their changes. (http://10.97.2.10:8080/job/autopilot-run-custom-branch-saucy)
[06:29] <veebers> but It's been unmaintained and so doesn't work at the moment
[06:29] <didrocks> veebers: shouldn't that rather be a feature branch?
[06:30] <didrocks> veebers: and so having daily release to a ppa and so on
[06:30] <didrocks> I'm afraid that we have: 1. too many ppas and people are lost in versions
[06:30] <didrocks> 2. too many methods to build sources and packages
[06:30] <didrocks> (mir itself has 3 different ways to build itself used by upstream, 2 of them being hackish script and demanding updating the build-deps in various places)
[06:30] <veebers> didrocks: this one instance is a developer want's to test his changes before proposing a MP
[06:31] <didrocks> veebers: I would say then, for building, it would be better to use something similar than the upstream merger
[06:31] <didrocks> then, grab the deb, create a local repo
[06:31] <didrocks> and using that with an otto job that is similar to ours
[06:32] <didrocks> Mirv: I think you didn't update the version on debian/changelog compared to the tarball, right? Trying that
[06:32] <veebers> didrocks: sure alright makes sense. Can you link me to where I can see/learn about the otto job so that I can steal err borrow it's config?
[06:33] <didrocks> Mirv: hum, the patches are then rejected, are you sure you pushed your qtpim branch to latest?
[06:33] <didrocks> veebers: oh, sure, look at http://10.97.0.1:8080/job/autopilot-saucy-daily_release/
[06:33] <didrocks> veebers: and tell me if anything doesn't make sense :)
[06:33] <didrocks> the runs are tagged with stacks it's built
[06:34] <didrocks> veebers: and you can see, almost no red in the runs! :-)
[06:34] <veebers> didrocks: awesome cheers, I've just been called to tea but will be back to probably ask more questions :-)
[06:34] <veebers> ^_^
[06:34] <didrocks> veebers: and the red are missing package in list, so wanted failures ;)
[06:34] <didrocks> veebers: enjoy your tea!
[06:42] <Mirv> didrocks: just a moment
[06:42] <Mirv> didrocks: hey, some push is very much missing, yes
[06:43] <didrocks> Mirv: thx
[06:43] <Mirv> didrocks: ok, qtpim pushed again
[06:43] <didrocks> will review :)
[06:43] <Mirv> didrocks: the licenses went upstream so that patch was removed then
[06:43] <didrocks> excellent :)
[06:46] <Mirv> didrocks: Qt Creator links in the spreadsheet now
[06:47] <Mirv> that's a big one
[06:47] <Mirv> I'll have the qtwebkit saucy update later today
[06:48] <didrocks> sponsoring day for me I guess :)
[06:56] <didrocks> Mirv: qtpim sponsored
[06:57] <Mirv> nice, I'll let Bill and Renato know
[06:57] <didrocks> great!
[06:57] <didrocks> qtcreator now
[06:59] <didrocks> Mirv: the plugins for qtcreator are still as distro patch in the branch, right?
[07:00] <veebers> didrocks: uh, first silly question; What does `$HOME/bin/run_otto_job` expand to so I can see the script?
[07:02] <didrocks> veebers: it's just in the otto source (see the jenkins/ directory)
[07:02] <veebers> didrocks: ah ok, cheers
[07:02] <didrocks> yw ;)
[07:05] <Mirv> didrocks: yes, still like that, the qtcreator-dev is not here yet
[07:05] <didrocks> ok
[07:06] <rickspencer3> woah, lots of new desktop stuff today
[07:07] <didrocks> hey rickspencer3!
[07:07] <rickspencer3> ey didrocks
[07:07] <rickspencer3> no, I'm not hear to harp on daily quality ;)
[07:08] <didrocks> Mirv: heh :)
[07:09] <didrocks> rickspencer3: you don't need to ;)
[07:09] <jibel> good morning
[07:09] <didrocks> Mirv: hum, you added a build-dep on libqt5-help5
[07:09] <rickspencer3> hi jibel
[07:09] <didrocks> Mirv: in the end, we have twice this build-deps now, can you remove one please?
[07:09] <didrocks> hey jibel!
[07:09] <jibel> Hi rickspencer3
[07:09] <jibel> bonjour didrocks
[07:11] <Mirv> didrocks: removed and pushed
[07:11] <didrocks> Mirv: thanks!
[07:28] <didrocks> Mirv: hum, I'm seeing on one patch:
[07:28] <didrocks> --desktop_file_hint=/home/phablet/…
[07:28] <didrocks> rev 75
[07:28] <didrocks> that doesn't seem scalable and adapting to other env, do you have some background on that?
[07:28] <Mirv> didrocks: it's on the device, I'd think. ie commands run there
[07:28] <Mirv> and there the home dir is that always
[07:29] <didrocks> Mirv: yeah, that's a pity it's harcoded, I think one day, we have the potential to change the name
[07:29] <Mirv> yep, it even runs the app on device for you
[07:29] <didrocks> Mirv: mind putting something on the top description of the patch?
[07:29] <didrocks> so that if one day we change the user
[07:29] <didrocks> we can find that more easily :)
[07:31] <Mirv> didrocks: added and pushed
[07:34] <didrocks> trying building
[07:37] <seb128> hey desktopers
[07:37] <didrocks> salut seb128!
[07:38] <seb128> didrocks, lut ;-)
[07:42] <tjaalton> is it known that U1 is broken on saucy?
[07:42] <tjaalton> client crashes with "ipcerror"
[07:43] <tjaalton> found it
[07:45] <seb128> tjaalton, that one is not known to me, it asserting due to the new python-configglue is known though
[07:45] <seb128> slangasek just uploaded a revert for that
[07:45] <tjaalton> oh
[07:45] <tjaalton> yeah that's the bug I found
[07:45] <tjaalton> I'll check out the upload queue, thanks
[07:47] <tjaalton> yep, fixed it for me too
[07:47] <tjaalton> syncing again, *phew*
[07:48] <pitti> bonjour seb128 !
[08:03] <Laney> hey
[08:06] <seb128> Laney, good morning, how are you?
[08:07] <Laney> seb128: not bad thanks, got a working indicator-applet again!
[08:07] <Laney> you?
[08:08] <seb128> Laney, I'm good thank
[08:08] <seb128> s
[08:08] <seb128> Laney, you should use unity!
[08:08] <Laney> I do on my main machine :P
[08:10] <Laney> not sure what would happen to my brain if my sexy xmonad configuration went away on the laptop
[08:11] <didrocks> hey Laney!
[08:11] <Laney> greetings didrocks!
[08:35] <seb128> sil2100, hey, how are you?
[08:36] <seb128> sil2100, I noticed that the indicator stack is not published yet, is there anything blocking it?
[08:39] <sil2100> seb128: looking, will need an packaging ACK
[08:39] <sil2100> http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_libusermetrics_1.0.6+13.10.20130711-0ubuntu1.diff
[08:39] <sil2100> seb128: just to be sure... google-mock 1.6.0+svn437 is available in distro?
[08:41] <seb128> sil2100, euh, I can think about half a dozen way for you to get that information
[08:41] <seb128> sil2100, launchpad, apt, rmadison
[08:41] <seb128> sil2100,
[08:41] <seb128> $ rmadison -S google-mock -s saucy
[08:41] <seb128> google-mock | 1.6.0+svn437-0ubuntu1 |         saucy | source, amd64, armhf, i386, powerpc
[08:41] <sil2100> seb128: I was asking because apt says differently
[08:41] <seb128> use rmadison
[08:41] <seb128> that's checking at the source
[08:41] <sil2100> apt-cache policy google-mock
[08:41] <sil2100>  *** 1.6.0-0ubuntu3 0
[08:41] <sil2100> Ok
[08:42] <seb128> did you run apt-get update?
[08:42] <sil2100> Yes, just a moment ago
[08:42] <seb128> do you use the main archive or a mirror?
[08:42] <sil2100> http://pl.archive.ubuntu.com/ubuntu/ <- maybe that's why?
[08:42] <seb128> yep
[08:42] <seb128> mirrors are often outdated
[08:42] <sil2100> Stupid polish mirror
[08:42] <seb128> in any case use rmadison when you need to know that
[08:43] <sil2100> Right, now I know it's more reliable ;) Anyway, I think it's ok for publishing, yes?
[08:43] <seb128> sil2100, also is there anything we can do have those easy diffs reviewed a bit earlier in the day so the update is available early for those who wait on it?
[08:43] <seb128> sil2100, seems ok to me yes ;-)
[08:44] <sil2100> seb128: I'll try to do that much earlier ;p I usually tend to wake up and start with what I didn't finish the last day
[08:44] <sil2100> While I probably should do the stacks first
[08:44]  * didrocks really thinks that publication should be the first thing we do in the morning :)
[08:44] <didrocks> Mirv: sil2100 ^
[08:44] <didrocks> (IIRC, I've repeated that a lot :p)
[08:45] <sil2100> didrocks: sorry guys ;p I know I know, it's just when you're irritated about something not working from yesterday, you want to fix it as soon as possible ;p
[08:46] <didrocks> Mirv: qtcreator sponsored
[08:47] <sil2100> didrocks: just so you know - the Apps stack is blocked until Florian fixes the toolkit regression
[08:47] <sil2100> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1199662
[08:47] <ubot2`> Ubuntu bug 1199662 in Ubuntu UI Toolkit "New easing causes animations not to reach their target values" [Critical,Confirmed]
[08:48] <didrocks> sil2100: can we work with them to run some apps autopilot tests with their stack?
[08:48] <didrocks> sil2100: to ensure they don't regress
[08:49] <sil2100> I guess, but changes like these should actually be tested by the UI toolkit, maybe unit-tested or something
[08:49] <didrocks> sil2100: ah, not sure for that one in particular, but in general?
[08:49] <sil2100> Since sometimes, well, the UI toolkit changes something and breaks the Apps on purpose
[08:49] <didrocks> sil2100: not the first time the toolkit is breaking apps
[08:49] <sil2100> This would maybe create a bit of a deadlock then
[08:50] <didrocks> well, they need to ensure that apps are adapted first
[08:50] <didrocks> if they don't want backward compatibility
[08:50] <sil2100> didrocks: I'll have a talk with kaleo and others today about that then, might be a good idea to have something more
[08:51] <didrocks> sil2100: thanks!
[08:51] <didrocks> sil2100: I'll add the missing autopilot tests today
[08:51] <didrocks> sil2100: the remaining things to look for is unity, right?
[08:51] <didrocks> sil2100: I've published the raring oif SRU (the libgrip fix) which was waiting for a week FYI
[08:52] <sil2100> didrocks: awesome, right - I forgot that now 'publishing' the raring stack means pushing to the SRU PPA ;/
[08:52] <sil2100> didrocks: thanks!
[08:53] <sil2100> didrocks: I already poked Wellark and waiting for him to pop up, also we need Ted to resolve unity issues
[08:53] <didrocks> sil2100: yw ;)
[08:53] <didrocks> ok, good!
[08:54] <Laney> mlankhorst: can you help find the right way to fix omap4 images please? :(
[08:55] <Laney> I don't know where to add the reverted xorg
[08:56] <mlankhorst> Laney: erm what is the build recipe it is using atm?
[08:57] <Laney> well part of my problem is that I'm not entirely sure which seeds it's using
[08:57] <seb128> ogra_ probably knows
[08:58] <ogra_> mlankhorst, whats the reason you didnt just add it as dependency to pvr ?
[08:58] <Laney> it depends on the abi but nothing which provides that is pulled in
[08:58] <mlankhorst> lack of upload rights, I guess :)
[08:58] <seb128> Mirv, did you see my debug comment ont he qtsystems bug? can you fwd to the upstream tracker? (I don't have a login there)
[08:59] <mlankhorst> but I'll make the change and then ask someone to sponsor it
[08:59] <seb128> Laney, we should just do what ogra suggests, add a direct depends on the server to pvr
[08:59] <ogra_> Laney, pvr just needs a dep added, you dont want to sered that package (that would break all other arm desktop installs since it uses the normal ubuntu-desktop seed
[08:59] <ogra_> )
[09:00] <ogra_> s/sered/seed/
[09:00] <Laney> yeah?
[09:01] <xclaesse> wow, .cache/friends/avatars contains 12k files for almost 500Mb
[09:03] <Laney> mlankhorst: ogra_: like this: http://paste.ubuntu.com/5864264/ ?
[09:03] <Laney> I'm curious as to where pvr-omap4 gets pulled in though
[09:04] <ogra_> Laney, perfect
[09:04] <Laney> ah via supported-hardware-desktop
[09:06] <mlankhorst> yeah something like that :)
[09:06] <Mirv> didrocks: awesome! (qtcreator)
[09:06] <mlankhorst> actually the xserver-xorg-dev dependency could be dropped entirely afaict
[09:07] <didrocks> Mirv: nice work!
[09:07] <Mirv> seb128: I saw, I can mention it at the upstream tracker as well
[09:07] <Laney> I'll leave it
[09:07] <Laney> don't fancy doing another test build
[09:10] <seb128> Mirv, thanks
[09:11] <Mirv> (mentioned)
[10:00] <didrocks> sil2100: ah great! so all the things I listed on column E9 are DONE (apart qtvideo-node)?
[10:02] <didrocks> sil2100: btw: https://code.launchpad.net/~didrocks/cupstream2distro-config/share-app/+merge/174149
[10:04] <didrocks> sil2100: FYI, the thing that will never daily release, they need to be moved to "online" release (that we should "$ bzr mv online merge-only" I think)
[10:29] <Laney> yay, sorting works
[10:32] <seb128> Laney, \o/
[10:52] <sil2100> ACK
[10:52] <sil2100> didrocks: yes
[11:14] <Mirv> 11 apport collection processes at the same time slows down machine a bit..
[11:42] <didrocks> sil2100: I'm relaunching tha app stack for the tests only
[11:53] <sil2100> didrocks: ok, was the toolkit issue fixed or just to check shared-app?
[11:54] <didrocks> sil2100: just to check share-app
[11:54] <didrocks> for the toolkit and the new packages, I'll let you deal with those, right?
[11:54] <sil2100> Yessss
[12:25] <mlankhorst> Laney: oh btw did adding that to powervr help?
[12:25] <mlankhorst> hm guess you didn't try
[12:25] <Laney> mlankhorst: we'll find out when the next image build happens tomorrow morning
[12:26] <mlankhorst> oh sure
[12:34] <Mirv> didrocks: https://code.launchpad.net/~timo-jyrinki/ubuntu/saucy/qtwebkit-opensource-src/arm-fix-and-docs-packages/+merge/174184
[12:34] <Mirv> that would be the webkit thing from mitya57, my arm fix and your ubuntu3 patch
[12:35] <Mirv> didrocks: if you want, I could do one more PPA build for tomorrow. a 5.0.2 build finished successfully also for arm, but since the DPR is broken on 5.0.2 I asked mitya57 to do the docs thing for 5.0.1 and now the delta is smaller.. it does compile on amd64 and the g++-4.7 should take care of the ARM like it did now so far with Qt 5.1.0 and 5.0.2
[12:38] <didrocks> Mirv: yeah, that would appreciated :)
[12:38] <didrocks> there is no urgency for today, right?
[12:39] <Mirv> didrocks: ok. yeah no urgency.
[12:39] <didrocks> ok :)
[13:49] <kenvandine> sil2100, thanks for fixing the build failures in qtvideo-node
[13:50] <sil2100> kenvandine: no problem :)
[13:50] <kenvandine> sil2100, i merged the rest of my changes in my old failing branch into a new one that depends on your's
[13:50] <sil2100> kenvandine: hmmm! Since you're around!
[13:50] <kenvandine> can you review?
[13:50] <kenvandine> https://code.launchpad.net/~ken-vandine/qtvideo-node/run_tests/+merge/174204
[13:50] <sil2100> kenvandine: sure ;)
[13:50] <sil2100> kenvandine: could you tell me what's up with webaccounts-browser-extension ?
[13:50] <kenvandine> the most important part is adding the check target, so it actually runs the tests :)
[13:50] <kenvandine> sil2100, yeah... we didn't want to autoland it without any integration tests
[13:51] <sil2100> kenvandine: any luck with that?
[13:51] <kenvandine> not yet... i still need to figure out how to run otto and fix up those autopilot tests :)
[13:51] <kenvandine> didrocks, got time to walk me through setting up otto?
[13:52] <didrocks> kenvandine: we are going to write what it takes to set it up tomorrow on the phone, so maybe it will be a better time, wdyt?
[13:52] <sil2100> kenvandine: hmm, but I saw the unit-test being run during build I think
[13:52] <didrocks> kenvandine: as I think you want first to install/run it on the phone?
[13:52] <kenvandine> nope
[13:52] <kenvandine> :)
[13:53] <kenvandine> it builds unittests
[13:53] <kenvandine> doesn't run them
[13:53] <sil2100> make[3]: Wejście do katalogu `/opt/tmp/canonical/stacks/review/build-area/qtvideo-node-0.2.1daily13.06.07/unittests/shadervideonode'
[13:53] <sil2100> LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}  ./tst_shadervideonode
[13:53] <sil2100> ********* Start testing of tst_ShaderVideoNode *********
[13:53] <sil2100> Config: Using QTest library 5.0.2, Qt 5.0.2
[13:53] <sil2100> PASS   : tst_ShaderVideoNode::initTestCase()
[13:53] <kenvandine> i didn't get that!
[13:53] <sil2100> QWARN  : tst_ShaderVideoNode::testCameraSetCurrentFrame() No camera control or media player control instance included in video frame
[13:53] <sil2100> PASS   : tst_ShaderVideoNode::testCameraSetCurrentFrame()
[13:53] <kenvandine> without adding the check target
[13:53] <sil2100> QWARN  : tst_ShaderVideoNode::testMediaPlayerSetCurrentFrame() No camera control or media player control instance included in video frame
[13:53] <kenvandine> weird
[13:53] <sil2100> PASS   : tst_ShaderVideoNode::testMediaPlayerSetCurrentFrame()
[13:53] <sil2100> PASS   : tst_ShaderVideoNode::cleanupTestCase()
[13:53] <sil2100> Totals: 4 passed, 0 failed, 0 skipped
[13:53] <sil2100> Since that's what the testcase CONFIG does I guess
[13:53] <sil2100> ********* Finished testing of tst_ShaderVideoNode *********
[13:53] <sil2100> Here it runs?
[13:53] <sil2100> This is output from bzr bd
[13:53] <kenvandine> that is what i did too...
[13:54] <kenvandine> weird
[13:54] <sil2100> kenvandine: btw2. is it safe to change existing changelog contents? ;)
[13:55] <sil2100> kenvandine: since I have overriden the lintian warning, because I thought that existing changelog entries should stay intact, since those are released already
[13:55] <sil2100> didrocks: ^ what's the rule with that?
[13:55] <kenvandine> sil2100, i'd rather fix it
[13:55] <kenvandine> it's safe
[13:56] <didrocks> sil2100: yeah, I agree with kenvandine
[13:56] <didrocks> if it's for fixing a lintian warning, better to fix the changelog
[13:56] <didrocks> (even if already released)
[13:56] <kenvandine> especially since we know his email address :)
[13:56] <didrocks> they even rewrote the history in latest doctor who (spoiler), so we can do as well :)
[13:56] <kenvandine> haha
[13:56] <kenvandine> didrocks, no spoilers!
[13:57] <kenvandine> i'm a whole season behind
[13:57] <kenvandine> :-D
[13:57] <didrocks> kenvandine: I won't go further! :p
[13:57] <didrocks> kenvandine: just though to tell you that…
[13:57]  * didrocks runs away
[13:57] <didrocks> :)
[13:57] <kenvandine> :)
[13:57] <kenvandine> tomorrow is fine
[13:57] <didrocks> whole season in a day?
[13:57] <kenvandine> i'm feeling a bit behind anyway, i'd rather work on something else that i haven't even started
[13:57] <didrocks> or you are speaking about otto? :p
[13:57] <kenvandine> didrocks, haha
[13:57] <kenvandine> otto
[13:57] <kenvandine> :-D
[13:57] <didrocks> ;)
[13:58] <kenvandine> larsu, speaking of tasks i really need to get started on... want to step through the new indicators-client stuff?
[13:58] <kenvandine> for messaging menu?
[13:58] <sil2100> kenvandine: could you remove the lintian-overrides then ;)?
[13:58] <kenvandine> sil2100, sure
[13:59] <kenvandine> sil2100, ok... your branch does run the tests for me in pbuilder
[13:59] <kenvandine> but it didn't in bzr bd
[13:59] <kenvandine> weird
[13:59] <kenvandine> i'll remove that change in my branch
[13:59] <larsu> kenvandine: well, I haven't started on messaging menu yet, because somebody noticed we have indicators in the greeter :)
[13:59] <larsu> kenvandine: but sure, what do you want to do?
[14:00] <kenvandine> i need to turn back on adding facebook stuff in messaging menu
[14:00] <kenvandine> and do the inline replies
[14:00] <kenvandine> like we do for SMS
[14:00] <kenvandine> remember you said i would be surprised how easy it is?
[14:00] <larsu> I do!
[14:00] <larsu> and you will be!
[14:01] <larsu> are you going to be using this from c++?
[14:01] <kenvandine> well... adding the entry should be from vala
[14:02] <kenvandine> not sure what the code will be like for replying
[14:02] <kenvandine> i think that is what you said would be easy :)
[14:02] <larsu> ya that's fine as well, libmessaging-menu has gir
[14:03] <larsu> so the biggest problem is that you need the branch of libmessaging-menu that we're using on the phone
[14:03] <larsu> I have no idea where that is packaged, the upstream is lp:indicator-messages/phablet
[14:04] <larsu> like I said, I'll be working on consolidating these branches very soon
[14:04] <larsu> but I haven't gottent around to it yet
[14:06] <kenvandine> sil2100, i updated that branch
[14:06] <kenvandine> larsu, that is fine, i can do the development on the phone
[14:07] <sil2100> kenvandine: will review in a moment :)
[14:08] <larsu> kenvandine: awesome. I'm trying to find an example, but I can't ...
[14:08] <kenvandine> great :-D
[14:08] <kenvandine> larsu, you should include examples in the source :)
[14:08] <kenvandine> like tedg always did
[14:08] <kenvandine> :-D
[14:09] <larsu> kenvandine: well, there are, but not for the new stuff that I hacked for the demo
[14:09] <larsu> kenvandine: I'll write one, but the gist is this:
[14:09]  * tedg wipes a tear and thinks: "kenvandine misses me"
[14:09] <larsu> in addition to sources, you can now also add MessagingMenu.MessageS to an MessagingMenuApp
[14:09] <kenvandine> tedg, every once in a while i do :)
[14:09] <larsu> http://bazaar.launchpad.net/~indicator-applet-developers/indicator-messages/phablet/view/head:/libmessaging-menu/messaging-menu-message.h
[14:10] <larsu> that represents one of those "hero items"
[14:10] <larsu> and it can take an arbitrary amount of actions with parameters
[14:11] <larsu> if there's one action with one string parameter, it will be rendered as a text entry field
[14:12] <larsu> kenvandine: messaging_menu_message_add_action (msg, "id", "Reply", G_VARIANT_TYPE_STRING, NULL)
[14:12] <larsu> and then connect to the "activate" signal of that message, which gives you the parameter in a variant
[14:12]  * larsu cooks up an example real quick
[14:13] <kenvandine> i think i understand
[14:29] <Laney> phwoar, super hot & nice outside
[14:33] <desrt> Laney: did the g-c-c stuff get settled?
[14:34] <Laney> desrt: settled how?
[14:34] <desrt> landed, no more infinite loops and no regressions?
[14:34] <Laney> well it's in saucy
[14:35] <desrt> so yes, i guess, otherwise i would have heard about it? :)
[14:35] <Laney> Can't see any new bug reports
[14:35] <Laney> and nobody has complained to me
[14:35] <desrt> cool!
[14:35] <Laney> so ... seems ok so far
[14:35] <desrt> thanks
[14:35] <Laney> that u-p-s job race is annoying though
[14:37] <larsu> kenvandine: something like this should work: http://paste.debian.net/15543/
[14:38] <kenvandine> larsu, thanks!
[14:39] <larsu> kenvandine: there are also docsrings in the source, so making the docs yourself might help a bit too. Sorry about the state of all this right now
[14:39] <larsu> kenvandine: at least I'm working on gsettings-qt model support today :)
[14:41] <kenvandine> larsu, that's awesome too :)
[14:48] <kgunn_> mlankhorst: ping
[14:48] <mlankhorst> pong
[14:57] <jbicha> mpt: setting "Log on without a password" breaks sudo and any admin authentication prompts
[14:57] <jbicha> you can try it for yourself by going into User Accounts Settings, click Unlock, click Password
[14:58] <jbicha> for Action, set Log in without a password
[14:58] <jbicha> then try re-locking User Accounts and unlocking
[14:58] <jbicha> it won't work until you first click Password again and set a password
[14:59] <mdeslaur> jbicha: why is it breaking everything? it should just add you to a group
[15:00] <jbicha> it actually blanks your password, not adds you to a group
[15:00] <mdeslaur> well, that's broken
[15:01] <jbicha> oh I see that I'm in the nopasswdlogin group
[15:01] <mdeslaur> it should simply add you to the nopasswdlogin group
[15:01] <mdeslaur> but not disable your password
[15:01] <mdeslaur> hrm, accountsservice is doing both for some reason
[15:02] <jbicha> then I guess it's an accountsservice bug, I'm using http://www.valadoc.org/#!api=accountsservice/Act.User.set_password_mode
[15:03] <mdeslaur> hrm, using the nopasswdlogin group is a ubuntu-specific patch apparently
[15:03] <mdeslaur> well, ubuntu/debian specific
[15:03] <mdeslaur> what a mess
[15:07] <mdeslaur> hrm, ok, so both removing the password, and adding to the group should be ok
[15:07] <jbicha> oh? let me log out
[15:08] <mdeslaur> not sure why polkit isn't handling it...pam module config seems ok
[15:08] <didrocks> kenvandine: sil2100: Mirv: FYI, we fixed otto dependency detection, so expect some dependency adjustement tomorrow
[15:09] <didrocks> sil2100: then, for looking at what packages are not needed for listing anymore, just look at the "new packages to install" and you will have the list I guess ;)
[15:09] <jbicha> mdeslaur: yeah logging out didn't help (I'm using gdm)
[15:10] <sil2100> didrocks: well, my cleanup branch is waiting for approval all the time ;p
[15:10] <didrocks> sil2100: did you made the list from the logs?
[15:11] <sil2100> didrocks: manually actually!
[15:11] <mdeslaur> jbicha: hrm, does in fact seem broken with sudo and policykit
[15:12] <jbicha> it would be cool if that patch were upstream because once that bug is fixed, I believe the User Accounts panel still won't be designed to handle "log in without a password" correctly
[15:13] <mdeslaur> jbicha: we could just rename all these options "Break my computer" and be done with it
[15:14] <mdeslaur> :)
[15:15] <jbicha> you're right, we don't make the "break my computer" feature of Linux obvious enough ;)
[15:16] <jbicha> a lot of users have to install random stuff from ppa's to get that effect
[15:16] <mdeslaur> haha
[15:17] <mdeslaur> jbicha: so, is that option only when running under unity?
[15:17] <didrocks> sil2100: do you want that we merge? Then, we can redeploy
[15:17] <didrocks> and run only the tests?
[15:17] <jbicha> mdeslaur: I've only been using gnome-shell today; it's a GNOME feature too
[15:17] <didrocks> sil2100: or even better, maybe we can do that stack per stack?
[15:17] <didrocks> sil2100: like, you deploy (without merging)
[15:18] <didrocks> run the stack
[15:18] <mdeslaur> jbicha: I mean, are you implementing mpt's design just for unity sessions, or will it be for gnome too?
[15:18] <didrocks> (with foo)
[15:18] <didrocks> sil2100: and see the result right away?
[15:18] <didrocks> sil2100: want that we do one together?
[15:18] <mdeslaur> jbicha: because just being in the nopasswdlogin should be enough for lightdm, without necessarily disabling the user password and breaking sudo and policykit
[15:19] <sil2100> didrocks: ok, wait one moment, I'll re-merge with trunk and try to re-deploy some smaller stack ;)
[15:19] <mdeslaur> but, I guess that would mean extending accountsservice
[15:19] <mdeslaur> meh
[15:19] <didrocks> sil2100: sure!
[15:19] <jbicha> mdeslaur: my thought was that the Security tab should be Unity only since it duplicates GNOME 3.8's Privacy panel
[15:22] <mdeslaur> jbicha, mpt: ok, I think we don't have the proper infrastructure at the moment to handle a "Log in without a password" option
[15:22] <mdeslaur> jbicha, mpt: ideally, it would just allow logging in a the greeter without disabling the user password completely
[15:22] <mdeslaur> jbicha, mpt: but that would require adding some new apis to accountsservice
[15:23] <mdeslaur> jbicha, mpt: perhaps we should postpone that checkbox for now?
[15:25] <sil2100> didrocks: ok, will re-deploy the media stack, will re-run it for testing (with foo) once done
[15:25] <didrocks> sil2100: ok, looking as well :)
[15:30] <mdeslaur> jbicha: ok, sudo and policykit break because we use "nullok_secure" in our pam config instead of just "nullok"
[15:30] <sil2100> hmmm
[15:30] <sil2100> didrocks: http://10.97.0.1:8080/view/cu2d/view/Head/view/Media/job/cu2d-media-head-2.2check/88/ <- why?
[15:30] <mdeslaur> jbicha: perhaps a bug could be filed to see if it makes sense to change that
[15:31] <sil2100> didrocks: it didn't fire the autopilot-saucy-daily_release job, strangely?
[15:31] <didrocks> sil2100: ah, nothing to publish ;)
[15:31] <sil2100> But but but but
[15:31] <sil2100> ;p
[15:31] <didrocks> sil2100: in fact, you should run manually the jobs, it's even better :)
[15:31] <didrocks> sil2100: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/build?delay=0sec
[15:32] <didrocks> release, put "test"
[15:32] <didrocks> stack: name of the stack (it's just for printing)
[15:32] <didrocks> series -> change to saucy :)
[15:32] <sil2100> didrocks: let me check the standard parameters from media then
[15:32] <didrocks> ppa -> the syntax is http://10.97.0.1:8080/job/autopilot-saucy-daily_release/build?delay=0sec
[15:32] <didrocks> grrr
[15:32] <didrocks> ubuntu-unity/daily-build
[15:33] <didrocks> sil2100: yeah, just use your "packages" and "testspackages"
[15:33] <sil2100> Aaaactually
[15:33] <sil2100> Didn't think about it, but I can test everything like this, heh...
[15:33]  * sil2100 stupid
[15:35] <jbicha> mdeslaur: which package should that bug be for?
[15:35] <didrocks> sil2100: no worry, sometimes, it's easier to go straight to pushing buttons directly :)
[15:35] <sil2100> Ok, I see I have some missing packages, probably deps
[15:36] <mdeslaur> jbicha: pam
[15:36] <sil2100> Fixing!
[15:38] <sil2100> didrocks: hope you don't mind I'll use the autopilot job for my purposes?
[15:39] <didrocks> sil2100: you can even abuse it! nothing needs to run right now :)
[15:43] <didrocks> sil2100: don't add them bindly pleae
[15:43] <didrocks> please*
[15:43] <sil2100> What do you mean?
[15:44] <sil2100> didrocks: with the packages lists, yes?
[15:44] <didrocks> sil2100: yep ;)
[15:45] <sil2100> didrocks: how does the 'extra packages need to be isntalled' work now ;)?
[15:45] <didrocks> sil2100: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/404/label=autopilot-ati/console
[15:45] <didrocks> it's the same than before
[15:45] <didrocks> /var/log/upstart/otto-setup.log: E: The following additional packages will be installed:
[15:45] <didrocks> and then, you have the diff
[15:45] <sil2100> I know, but this means that without those in the list, it won't work, right?
[15:46] <sil2100> (as long as those make sense)
[15:46] <didrocks> sil2100: right, we juts need to spot if some parts are in universe (for components in main), or if it makes sense to have all those new deps
[15:47] <sil2100> Indeed!
[17:14] <didrocks> good evening everyone :)