[07:55] <nerochiaro> oSoMoN: good morning, I think when you have time we should have a bit of catch up
[08:04] <oSoMoN> nerochiaro: yeah, how about in an hour or so? I’m pretty busy atm
[08:06] <nerochiaro> oSoMoN: sure, no problem. just one question: are we supposed to be all working from saucy at the moment ?
[08:10] <oSoMoN> nerochiaro: the builds have switched to saucy, so it would be better yes (although I have to admit I haven’t done the switch myself yet)
[08:10] <oSoMoN> nerochiaro: I’d say no urgency, but something to consider doing soonish
[08:11] <nerochiaro> oSoMoN: ok
[08:52] <nik90|Office> mehow: good morning
[09:17] <mehow> nik90: hello
[09:18] <nik90|Office> mehow: how is it going?
[09:18] <mehow> all good :) how about you ?
[09:18] <JamesTait> Good morning all, happy Pi Approximation Day! :-D
[09:19] <lazowik> haha
[09:19] <nik90|Office> mehow: good
[09:19] <nik90|Office> mehow: just wanted to ask about the progress on the "add timer preset" designs
[09:23] <BT> hello
[09:23] <BT> Hello
[09:23] <BT> I am very new to this
[09:24] <BT> and want to learn
[09:24] <BT> I need to learn
[09:29] <oSoMoN> nerochiaro: ping
[09:37] <nerochiaro> oSoMoN: hey
[09:38] <oSoMoN> nerochiaro: wanna have a quick chat now?
[09:38] <nerochiaro> oSoMoN: ok, let me grab a mic and move to a quiet room
[09:41] <nerochiaro> oSoMoN: ok, connecting
[14:58] <_5m0k3> I've been following the hackfest, but I haven't yet had time to contribute.  It seems I may be able to this week.  How can I get started?
[16:48] <mrqtros> balloons, Hi!
[16:49] <balloons> mrqtros, hello!
[16:49] <mrqtros> balloons, can you help me? :)
[16:49] <balloons> mrqtros, I can certainly try my best, what's up?
[16:49] <mrqtros> balloons, look please this merge request: https://code.launchpad.net/~mrqtros/ubuntu-rssreader-app/stable-trunk-prepare2/+merge/175731
[16:50] <mrqtros> balloons, we have errors, in some *.qml files we have something like that
[16:50] <mrqtros> import "feeds"
[16:50] <balloons> mm.. ok,
[16:50] <mrqtros> where "feeds" is a directory with *.qml files
[16:51] <mrqtros> But as you can see on server's side testing system can't find/create this folder
[16:51] <balloons> mrqtros, this is a big merge, I'll need a moment. So can I see what your talking about by running the testsa?
[16:53] <mrqtros> Sorry for big merge, it's our mistake :(
[16:54] <mrqtros> I think yes, first test failed: http://91.189.93.70:8080/job/generic-mediumtests/116
[16:57] <balloons> mrqtros, no worries.. ok, I'm branching your code now ;-)
[17:05] <balloons> mrqtros, hmm.. why am I getting conflicts :-(
[17:06] <mrqtros> Which? :)
[17:06] <balloons> I can't merge what you have to trunk at the moment
[17:06] <balloons> 9 conflicts encountered
[17:07] <balloons> mostly with the Article*.qml files
[17:08] <mrqtros> Hmm... trunk was changed since I've proposed merge
[17:09] <balloons> mrqtros, ahh.. can you rebase and then I'll pull again?
, what should I do? Get trunk, then merge with my stable-trunk-prepare2 and then push again?  Or there is simpler way? :)
[17:11] <mrqtros> I'am newbie in bzr :)
[17:12] <balloons> mrqtros, ahh yes.. I can resolve the conflicts perhaps but then I couldn't push the changes to your branch.. so, bzr update should rebase your branch
[17:12] <balloons> bzr update
[17:12] <balloons> resolve conflicts
[17:12] <balloons> bzr commit
[17:14] <mrqtros> bzr update in my branch says that nothing changed :(
[17:15] <balloons> mrqtros, well, hmm
[17:15] <balloons> does bzr pull do anything for you?
[17:15] <balloons> if not, you can checkout trunk, then issue a merge against your branch
[17:15] <mrqtros> w8 a moment
[17:16] <mrqtros> Yep, 9 conflicts :) w8, I'll check them
[17:17] <balloons> mrqtros, kk.. :-)
[17:21] <mrqtros> balloons, ok, I've  merged trunk with my version, committed it, what now? :)
[17:21] <balloons> now push it, and it will update.. so when I pull, I'll get no coflicts and we can fix the tests :-)
[17:22] <mrqtros> I should push in stable-bla-bla-bla branch? :)
[17:22] <mrqtros> to*
[17:22] <balloons> yes, push to your same branch ;-)
[17:22] <balloons> it'll just update the merge proposal, etc
[17:25] <mrqtros> balloons, ok, try now,
[17:25] <balloons> awesome, got it
[17:26] <balloons> mrqtros, ok, so I only see one test in here and it does run
[17:26] <balloons> it's just a placeholder test looks like
[17:28] <mrqtros> How can we trigger rebuild on merge request? :)
[17:28] <balloons> http://91.189.93.70:8080/job/ubuntu-rssreader-app-ci/12/
[17:30] <mrqtros> balloons, I think I have no rules to relaunch :)
[17:30] <balloons> mrqtros, hmm, let me give it a try
[17:30] <balloons> after every merge it should automatically retry anyway
[17:33] <mrqtros> Diff changed, but nothing happens :)
[17:38] <balloons> fginther, can you help us kick off a new build for https://code.launchpad.net/~mrqtros/ubuntu-rssreader-app/stable-trunk-prepare2/+merge/175731?
[17:42] <zedtux> Hi everyone, I'm developing an application for Ubuntu that include a kernle module. My project is (as of now) half open source and the kernel module is in the closed source part of the project. The application and its kernel module are working fine, but I'm now wondering about the way of publishing my app.
[17:44] <zedtux> If I have understood well the way to go, I have to upload a single archive containing the whole application. In my case I would like to provide different packages per kernel compiled modules.
[17:44] <zedtux> For example a package for kernel version 3.9 and another one for kernel version 3.10
[17:44] <zedtux> So how could I do that?
[17:49] <mrqtros> zedtux, I think this question is not actual now :) And nobody can't answer correctly yet ... Platform is under development as you know
[17:50] <balloons> zedtux, you do that by using the debian/control file and specifying dependencies
[17:50] <balloons> but imho you would need seperate packages.. someone else might be able to tell you more
[17:51] <zedtux> Thank @ballons for confirmation
[17:51] <zedtux> But then @mrqtros I'm not sure to follow you.
[17:51] <zedtux> Can you please give me more information ?
[17:52] <mrqtros> zedtux, I am core app developer, not from Canonical :)
[17:53] <zedtux> mrqtros, okay
[17:56] <zedtux> Let me give you more information, maybe you will understand better the sense of my question: As I would like to sell my application on the Ubuntu Software Center (to surf on the wave of the App stores ;)) then I'm wondering how to do that.
[17:56] <zedtux> For all the open source part, I did a PPA and it's fine.
[17:56] <mrqtros> zedtux, so I can only advice you :) And now my opinion is that you shall not rely on things, which can easily be changed in near future
[17:56] <zedtux> But for the part "To be sell" then I'm not sure how to proceed.
[17:56] <mrqtros> balloons, any news? :)
[17:57] <zedtux> mrqtros, alright understood.
[17:58] <balloons> zedtux, http://developer.ubuntu.com/publish/
[17:59] <balloons> mrqtros, it ran again
[17:59] <balloons> the toolbar test failed everything else passed.. So, I would gut the autopilot test completely
[17:59] <zedtux> balloons, thanks but I already had a look at everything from that link... Or I didn't understood.
[17:59] <balloons> edit the file and remove the test_toolbar_shows function
[18:00] <balloons> zedtux, well if you have something more specific mhall119 is the guy to talk to.
[18:01] <balloons> he can speak about it more clearly than I can
[18:01] <zedtux> balloons, "Please create a tarball of the source package" make me thinking that I have to provide 1 .tar.gz file but tomorrow a new version of kernel is available and I have to publish the compiled kernel module...
[18:01] <zedtux> ballons, thank you! I will contact him.
[18:01] <balloons> zedtux, well is the kernel changing that much each time you need a new package to support it?
[18:02] <balloons> that said ubuntu release tend to target a specific kernel
[18:03] <mrqtros> very specific app... Can you explain reasons? :)
[18:03] <balloons> mrqtros, did you see my note? make sense?
[18:04] <zedtux> balloons, to be honest I'm confuse right now. My kernel module contains some "LINUX_VERSION_CODE >= KERNEL_VERSION" for version 3.6, 3.7 and 3.9. I was expecting to just have to compile for those versions but giving some tries in VMs showed me that my kernel module compiled against the version 3.9 doesn't worked on kernel 3.10
[18:04] <balloons> mrqtros, basically the ap tests were failing because of the huge changes to rss reader and were more or less removed. I would just remove the last one as it is a placeholder anway
[18:04] <balloons> kernel 3.9 and 3.10 changed things
[18:04] <balloons> :-)
[18:04] <zedtux> with the error message "Exec format error"
[18:05] <zedtux> and in dmesg I had "disagrees about version of symbol module_layout".
[18:05] <mrqtros> balloons, ok, I'm awaiting now :)
[18:05] <zedtux> Using "modprobe --dump-modversions" I saw that addresses are completely different for many of the methods I'm using.
[18:05] <balloons> ok, you committed and pushed it?
[18:08] <mrqtros> balloons, sorry, I thought you want to remove it yourself :) W8 plz :)
[18:09] <balloons> mrqtros, I would, but I can't push to your branch :-)
[18:09] <balloons> mrqtros, anyways I think that will solve everything, so yay
[18:09] <fginther> balloons, rebuilidng
[18:09] <zedtux> balloons, my app is in 3 parts: the kernel module, a daemon and a config tool. The config tool is open source and in a PPA, what do you think if I publish the kernel module packages into the PPA (as closed source) but upload the daemon to the Ubuntu Software Center ?
[18:10] <zedtux> Then if a new kernel is released I just push to the PPA and that's it.
[18:10] <balloons> fginther, just a moment mrqtros has one more tiny commit to push.. but they should autoland after every commit right?
[18:10] <zedtux> For the daemon it's not changing so much.
[18:10] <fginther> balloons, yep, that would automatically kick off a new build
[18:10] <balloons> fginther, sorry I mean to say the bot should run after every commit
[18:10] <balloons> fginther, right, ty :-)
[18:11] <mrqtros> I should remove "test_toolbar_shows", yep?
[18:11] <balloons> zedtux, well I think you have many options, but you should start the process via the myapps submission
[18:11] <balloons> if you've started it, the review team can make specific recommendations
[18:11] <balloons> mrqtros, yes
[18:12] <zedtux> ballons, ok I will do so and cross fingers...
[18:13] <mrqtros> balloons, python ... And what if I'll remove one test-method? They are called via reflection? :) Or I should remove all usages too?
[18:14] <balloons> mrqtros, the goal is to remove all autopilot tests so everything will pass just fine
[18:14] <balloons> we'll fix and submit new ones in a seperate commit
[18:14] <mrqtros> Wow ... Ok :)
[18:14] <balloons> all the old ones changed and rather than fixing them, they got left to stagnate.. so for now, let's just gut them :-)
[18:15] <balloons> NORMALLY a commit shouldn't go in that would break them, but they've already been removed in trunk
[18:15] <balloons> may as well remove them in your branch too
[18:16] <mrqtros> How can I remove them? Remove methods? Classes? Files? :)
[18:17] <mrqtros> I am new in python and in autopilot test :)
[18:17] <mrqtros> So forgive me for dummy questions :)))
[18:18] <balloons> in test_rssreader.py in the tests directory under autopilot, remove the     def test_toolbar_shows(self) function
[18:24] <mrqtros> sec
[18:25] <mrqtros> ok now!
[18:32] <balloons> mrqtros,
[18:32] <balloons> mrqtros, awesome.. so fingers crossed the bot will like everything now
[18:32] <mrqtros> balloons, ahah, ok )))
[18:33] <mrqtros> Failure :(
[18:37] <mrqtros> "None of the test reports contained any result
[18:37] <mrqtros> "
[18:43] <balloons> mrqtros, :-( boo well then
[18:44] <balloons> fginther, can you do me one final favor and drop rss reader from running ap tests.. there are none left to run anyways
[18:44] <fginther> balloons, sure
[18:44] <balloons> mrqtros, this is the sledgehammer approach.. it'll definitely work now :-)
[18:45] <balloons> fginther, then kick off the autolanding for mrqtros so he can get his merge in ;-) ty ty ty!
[18:45] <mrqtros> balloons, :) Lol)))
[18:45] <avoine> Hello
[18:45] <avoine> I wanted to know if there is a way to enable the arm architecture in a ppa?
[18:46] <avoine> I'm trying to port the evopedia app on the ubuntu phone: https://code.launchpad.net/~patrick-hetu/+junk/evopedia-app
[18:46] <avoine> and I wanted to compile it without cross-compiling the whole qt5 stack
[18:58] <mrqtros> balloons, how can we trigger rebuild now? :)
[18:59] <balloons> mrqtros, fginther will trigger the rebuild once everything is ready to pass
[18:59] <mrqtros> Ok, thanks ;)
[19:10] <fginther> mrqtros, the jenkins jobs for ubuntu-rssreader-app have been updated, feel free to trigger that autolanding now by approving the merge proposal
[19:11] <balloons> mrqtros, ohh perfe
[19:12] <mrqtros> fginther, I approved :)
[19:14] <mrqtros> But seems that nothing happened
[19:42] <mrqtros> balloons, thanks! :)
[19:42] <mrqtros> It works now :)
[19:44] <balloons> mrqtros, excellent
[19:44] <balloons> I'm glad the rss changes are in, we can get back to writing some test for the new stuff :-)
[19:44] <mrqtros> balloons, thanks for your patience :)
[19:45] <balloons> same to you.. I know that was probably cubersome
[19:49] <mrqtros> balloons, next merge we will have no any problems? :)
[19:49] <balloons> mrqtros, yes, no problems
[19:56] <mrqtros> balloons, what a good new :) Now we will use short updates, I promise :)
[19:56] <balloons> mrqtros, :-) It makes it easier for everyone to review