[00:11] <sil2100> kenvandine: also, another small one: https://code.launchpad.net/~sil2100/libunity-webapps/packaging_review
[00:23] <sil2100> kenvandine: https://code.launchpad.net/~sil2100/libunity-webapps/raring_vcs_switch/+merge/161972 <- this as well!
[15:56] <kenvandine> Mirv, https://code.launchpad.net/~ken-vandine/kubuntu-packaging/qtsensors-opensource-src_arches/+merge/162136
[16:14] <fginther> didrocks, please ping me when you have a minute
[16:23] <sil2100> cyphermox: hi! Since I don't remember if you guys already expained that - what happened to indicators?
[16:24] <cyphermox> sil2100: you mean in head?
[16:24] <cyphermox> sil2100: if so, various bad things
[16:24] <sil2100> cyphermox: yes, I see bamf being red there and many other jobs ;)
[16:25] <cyphermox> some packages are behind because we did land them with the /raring branch; but that didn't get synced with the /trunk branch, and we are missing a saucy pbuilder for bamf, etc.
[16:25] <sil2100> cyphermox: ah, ok, thanks
[16:26] <cyphermox> sil2100: I'm taking care of this
[16:26] <sil2100> We'll poke this probably anyway during daily
[16:26] <sil2100> cyphermox: thanks ;)
[16:26] <cyphermox> I'll give you the details soon
[16:34] <didrocks> Mirv: hey, around?
[16:46] <Mirv> didrocks: yes!
[16:48] <sil2100> cyphermox: can you review some branches then? Since it seems those got missed
[16:48] <sil2100> cyphermox: I'll paste you the links in priv
[16:50] <Mirv> kenvandine: done
[17:00] <ronald_dollar> anyone have a fix for the keyboard only working on reboots? please private message me with help!
[17:15] <ronald_dollar> anyone have a fix for the keyboard only working on reboots? please private message me with help!
[17:28] <sil2100> cyphermox: thanks for the reviews!
[17:51] <kenvandine> sil2100, all redeployed except unity head and raring
[17:51] <kenvandine> because they are still running
[17:53] <sil2100> kenvandine: thanks!
[17:53] <kenvandine> sil2100, np, if you notice the unity jobs finish, ping me
[17:53] <kenvandine> i'll try to watch them too
[17:54] <sil2100> kenvandine: would be good to redeploy unity later on, since it seems to cause problems because of that right now
[17:54] <sil2100> Ok
[18:04] <cyphermox> sil2100: have time for some review?
[18:04] <cyphermox> https://code.launchpad.net/~mathieu-tl/indicator-appmenu/merge-changelog/+merge/162181
[18:08] <sil2100> cyphermox: approved!
[18:15] <cyphermox> robru: kenvandine: reviews? https://code.launchpad.net/~mathieu-tl/indicator-messages/saucy-changes/+merge/162201
[18:18] <cyphermox> robru: also https://code.launchpad.net/~mathieu-tl/indicator-datetime/saucy-changes/+merge/162198
[18:48] <sil2100> kenvandine, cyphermox: https://code.launchpad.net/~sil2100/cupstream2distro-config/add_nux_to_100scopes/+merge/162217 <- can any of you guys review, get it merged and redeploy the experimental/100scopes stack?
[18:49] <kenvandine> sil2100, sure
[18:49] <sil2100> The scopes guys asked us to add that
[18:49] <sil2100> kenvandine: thanks!
[18:53] <cyphermox> sil2100: kenvandine: https://code.launchpad.net/~mathieu-tl/indicator-sound/saucy-changes/+merge/162215
[18:53] <cyphermox> https://code.launchpad.net/~mathieu-tl/indicator-sync/saucy-changes/+merge/162219
[18:53] <cyphermox> https://code.launchpad.net/~mathieu-tl/libappindicator/saucy-changes/+merge/162218
[18:53] <cyphermox> ^ more syncing changelog between 13.04 and trunk branches ^
[18:53] <sil2100> cyphermox: just love those branch names
[18:53] <sil2100> Mmmm saucy changes
[18:53] <cyphermox> yeah ;)
[18:54] <cyphermox> brings a whole new meaning to the kernel team's SAUCE commits ;)
[19:02] <kenvandine> sil2100, approved and deployed
[19:08] <sil2100> cyphermox: piiing!
[19:08] <sil2100> cyphermox: piing!
[19:09] <cyphermox> pong
[19:14] <cyphermox> sil2100: and the last one: https://code.launchpad.net/~mathieu-tl/libindicator/saucy-changes/+merge/162223
[19:21] <sil2100> cyphermox: the libappindicator one after your changes finally looks sane
[19:23] <sil2100> kenvandine: thanks!
[19:23] <sil2100> cyphermox: all good and approved
[20:43] <veebers> sil2100: I notice that the release-job failed again with that error message
[20:44] <veebers> sil2100: who would you suggest we ping about that?
[20:45] <sil2100> veebers: that's a good question
[20:45] <sil2100> veebers: the only thing that I can think of right now is going to the QA guys and asking globally
[20:46] <sil2100> I'll do that in a moment
[20:46] <veebers> sil2100: awesome, thank you. I'm just in a meeting ATM
[20:58] <sil2100> fginther: ping
[20:59] <sil2100> fginther: I'm in the QA room actually asking about the same problem here, but maybe you know something more
[20:59] <mzaza> I have followed the guid in http://unity.ubuntu.com/getinvolved/development/unitynext/ to setup development environment and I am downloading now QTCreator to start developing for Unity Next. However the guid doesn't mention how should I get tasks/bugs from to start working on and how to submit the code.
[20:59] <sil2100> fginther: all the generic jobs for autopilot on jenkins are failing because of an error with installing a kernel package
[20:59] <fginther> sil2100, I know of nothing specific to this issue
[21:00] <sil2100> fginther: ok, thanks, will be poking further
[21:00] <sil2100> ;)
[21:06] <mzaza> If I am a newbie, which is easier project to start working on. Unity or Unity Next?
[21:10] <nik90> mzaza: Unity Next is the future. From Ubuntu 14.04 it will be used as default
[21:11] <nik90> mzaza: so you should be looking to work on Unity Next rather than Unity. Unity Next uses QML so if you are familiar with that you can start right away
[21:13] <veebers> sil2100: ChrisGagnon has seen this issue in the past:
[21:13] <veebers> sil2100: <ChrisGagnon> veebers: let me give you a test, the fix is to move the distupgrade as a test case in the test suite
 veebers: http://10.97.2.10:8080/job/openarena-benchmark-ps-intel-2500-le/configure
[21:14] <veebers> sil2100: I'm not sure how this would work with us as we're not always going a dist-upgrade or we do 2 one at the start, one maybe at the end
[21:15] <veebers> sil2100: that being said, I have seen this issue before, but as I mentioned it aways went away for me
[21:15] <sil2100> veebers: oh, good to know - I've been at the QA guys and one of them actually ran the thing on a different machine to check what's going on
[21:15] <mzaza> nik90: If I am not familiar could you point to me what should I read?
[21:15] <sil2100> veebers: I wonder what's wrong then actually, since theoretically there has been a kernel update today in the morning
[21:15] <sil2100> veebers: so maybe that's related?
[21:16] <nik90> mzaza: I am guessing you mean not familiar with qml..well you can find qml documentation at http://qt-project.org/doc/qt-5.0/qtqml/qtqml-index.html
[21:17] <nik90> mzaza: QML has extensive documentation, and I am sure you can find many videos, tutorials if you search for them in google
[21:17] <sil2100> veebers: actually, I think it was Chris I was talking with ;)
[21:17] <nik90> mzaza: that's how I am learning qml as well
[21:17] <veebers> sil2100: correct me if I'm wrong. The kernel update will be in the next iso to be rolled out?
[21:18] <sil2100> veebers: not sure, I just know it's in -security right now
[21:18] <mzaza> nik90: I prefer reading than watching. How could I push changes I made?
[21:19] <nik90> mzaza: you need to become familiar with Launchpad and bzr. These are the tools which we use for development
[21:20] <mzaza> nik90: I'm still learning little about them, lost in the Ubuntu wiki pages :D
[21:20] <veebers> sil2100: I'm wondering if that's why I've seen it fix itself in the past (an updated iso comes out and hence no need to do an update during install)
[21:20] <mzaza> a PDF would be better though.
[21:21] <nik90> mzaza: agree :)...the best way is to read, try stuff out and then come here to this irc room and ask questions if you are stuck somewhere
[21:21] <nik90> mzaza: I would really recommend you start of with your own project, get acquainted with launchpad and bzr and then start on a big project like Unity next
[21:23] <mzaza> nik90: Right, that would help.
[21:24] <sil2100> veebers: oh, this is certainly a possibility, hm
[21:25] <sil2100> didrocks: when will you be more-or-less free?
[21:45] <didrocks> sil2100: hum, in ~1h I guess
[21:45] <didrocks> sil2100: any emergency?
[21:56] <sil2100> didrocks: no, I think we're resolving it ;)
[21:56] <didrocks> swet ;)
[23:01] <veebers> didrocks, sil2100: are you able to remind me why we have the variable dist-upgrade at the end of the preseed (for the daily-release)?
[23:01] <veebers> didrocks, sil2100: not all of the jobs in the generic job have the dist-upgrade appended to the end of the preseed correct?
[23:03] <fginther> robru, approved!
[23:04] <robru> fginther, excellent!!
[23:06] <sil2100> veebers: no idea
[23:07] <veebers> sil2100: ok thanks. I think it might have something to do with the 'extra packages installed during install' check, will ask didrocks when he's back on
[23:33] <cyphermox> https://code.launchpad.net/~mathieu-tl/appmenu-gtk/saucy-changes/+merge/162273
[23:33] <cyphermox> sil2100: ^
[23:39] <cyphermox> robru: https://code.launchpad.net/~mathieu-tl/appmenu-gtk/saucy-changes/+merge/162273
[23:45] <fginther> mterry, do you still need this approved? https://code.launchpad.net/~mterry/cupstream2distro-config/camera-arches/+merge/161744
[23:46] <mterry> fginther, ye
[23:46] <mterry> yes