[06:00] <DanChapman> morning all
[09:33] <pack_code> How do you publish a .deb app on the software center if license is GPL3?
[10:20] <popey> pack_code: same way you publish with an app of any license
[10:27] <pack_code> popey: I tried that
[10:27] <popey> tried what?
[10:28] <pack_code> to publish that way
[10:28] <pack_code> I go t a message
[10:29] <pack_code> popey: Thank you for submitting a gratis Free Software application through MyApps. At this time we are unable to process this request, as we are working on the implementation of a new app upload process.
[10:29] <pack_code> My app is FOSS
[10:29] <popey> Ah okay. It's a free app?
[10:29] <pack_code> popey: FOSS
[10:29] <popey> It can be FOSS and not free :)
[10:29] <popey> But anyway..
[10:29] <pack_code> yes..
[10:29] <popey> I would recommend you upload your application to Debian.
[10:29] <popey> Well, find a debian developer to assist you with that.
[10:29] <pack_code> but will I see it in ubuntu software center
[10:30] <popey> Not immediately.
[10:30] <pack_code> without having to add ppas
[10:30] <pack_code> how long is the review?
[10:30] <popey> But putting it in Debian means it will come to a future Ubuntu release, and other Debian derivatives benefit too.
[10:30] <popey> I don't know. You'd need to speak to a Debian developer
[10:30] <pack_code> retroactive as well?
[10:30] <pack_code> for trusty?
[10:31] <ogra_> trusty is in final freeze
[10:31] <pack_code> damn!
[10:31] <pack_code> I am on utopic
[10:31] <pack_code> do you have a link to the edbian option you mentioned
[10:31] <pack_code> "edbian" meant debian
[10:32] <popey> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#newpackage
[10:32] <popey> that might be useful
[10:33] <popey> The documentation is comprehensive.
[10:33] <pack_code> it is
[10:33] <pack_code> so there's really no way then, is there?
[10:34] <popey> no way for what?
[10:34] <pack_code> for an app to appear in Ubuntu Software Center
[10:34] <popey> Yes, but not immediately, if it's FOSS
[10:34] <pack_code> I have a launchpad ppa and a bzr recipe
[10:34] <popey> (and free)
[10:34] <pack_code> why is that?
[10:34] <pack_code> I thout Ubuntu was based on free/donations
[10:34] <popey> Long story.
[10:34] <pack_code> 1 sentence
[10:35] <pack_code> any outlook at least?
[10:35] <popey> If you want to appear in the Software Centre, get your package in the Ubuntu archive.
[10:35] <pack_code> how?
[10:35] <popey> to get in the archive, you're better getting in Debian (then everyone benefits)
[10:36] <popey> if you dont want to send to debian, you can submit to Ubuntu, but it won't go to Trusty archive, as that's already shipped.
[10:36] <pack_code> sure
[10:36] <popey> you could get it in W (15.10) when that releases, then request a backport
[10:36] <pack_code> I could live w/o trusty
[10:36] <popey> but honestly, going to debian is better.
[10:36] <pack_code> could work
[10:36] <pack_code> just what is the procedure
[10:36] <popey> s/releases/opens/
[10:36] <pack_code> huh?
[10:36] <popey> Well, the archive for W isn't open yet.
[10:36] <popey> 15.10 hasn't even begun yet.
[10:37] <ahoneybun> soon
[10:37] <pack_code> I see its not that time of April yet
[10:37] <popey> Close to when 15.04 releases, the archive for 15.10 will open.
[10:37] <pack_code> so does the software center automatically pick up debian archives or does one have to configure something like "multiverse"
[10:37] <popey> https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[10:38] <popey> No.
[10:38] <popey> USC shows what's in the archive, main, restricted, universe, multiverse
[10:38] <pack_code> That is very useful....
[10:38] <pack_code> popey: thanks man!
[10:39] <popey> However, I would still urge you to submit to debian, unless it's an Ubuntu specific app.
[10:39] <pack_code> it's actually gnome-shell
[10:39] <pack_code> game
[10:39] <pack_code> wanna see?
[10:39] <popey> sure.
[10:40] <pack_code> https://launchpad.net/puzzl main site
[10:41] <pack_code> popey: https://launchpad.net/~itprojects/+archive/ubuntu/ppa/+files/puzzl_1.0%2Br4%7Eubuntu14.10.1_amd64.deb
[10:43] <pack_code> popey: there was a debian import freeze on feb19
[10:44] <popey> but it could go into the next release
[10:44] <pack_code> popey: that's the boat I missed
[10:44] <popey> bummer
[10:44] <pack_code> I know, maybe on the next time the Titanic makes a stop somewhere
[10:46] <popey> heh
[10:46] <pack_code> popey: thanks for the brainstom
[10:47] <popey> np
[10:47] <pack_code> have a nice day!
[10:47] <popey> you too
[11:15] <zsombi_> nik90: ping
[11:15] <zsombi_> nik90: I'm back on alarm ID
[11:16] <zsombi_> nik90: I managed to launch teh clock app on my vivid :)
[11:18] <nik90> zsombi_: hey
[11:18] <nik90> zsombi_: ooh nice
[11:19] <zsombi_> nik90: so, I managed to crash teh app only ince, and I cannot reprodice it anymore...
[11:19] <zsombi_> once
[11:20] <nik90> zsombi_: I just got a email notification about the alarm-id MP and realized that I mentioned my test results to you on IRC that day but failed to comment on the MP.
[11:21] <nik90> zsombi_: From what I remember, even after switching to the memory backend, I did observe some strange behavior with respect to the bottom edge tab not being aware of the alarm changes..as if a signal wasn't fired
[11:21] <nik90> zsombi_: I couldn't reproduce this on every try, but it happened more or less 6 out of 10 times.
[11:23] <zsombi_> nik90: so th ebottom edge connects to some model signal?
[11:24] <nik90> zsombi_: well the bottom edge periodically (every minute) goes through the alarm model and calculates the time to the next closest active alarm.
[11:24] <nik90> zsombi_: but it seems that the alarm model variable doesn't seem to be updated (I think(
[11:25] <zsombi_> nik90: I cannot repro that... :(
[11:26] <nik90> zsombi_: I will test it once more with the same test conditions as before
[11:26] <zsombi_> nik90: this si weird... the bottom edge label  fetches the alarm model every time o move the window...
[11:27] <zsombi_> nik90: good. I've updated the MR, synced with staging now
[11:27] <nik90> zsombi_: on the phone probably that equates to the app getting focus again
[11:28] <zsombi_> nik90: perhaps...
[11:28] <nik90> zsombi_: the reason we do that is quite important...if an alarm goes off, the indicator-datetime disables it (for one-time alarm cases). However the clock app ui did not update to reflect that. So I had to add the code where when the clock app gets focus, we recheck the alarm model
[11:28] <zsombi_> nik90: but we shoudl do sthing about that
[11:29] <nik90> zsombi_: that was the best solution we could come up with at the time..I remember discussing this UI not updating issue when I implemented the solution.
[11:33] <zsombi_> nik90: right... and that can stay as is
[11:33] <zsombi_> nik90: what we could do is to have some LiveTime{} component which woudl also trigger a signal to give you the next upcomming alarm
[11:35] <nik90> zsombi_: yeah that would be handy..would save the clock app from polling the alarm model unnecessarily
[11:38] <nik90> zsombi_: if this LiveTime{} component lands in 1.3, would that be in vivid or vivid+1 ?
[11:38] <zsombi_> nik90: 1.2 is vivid, 1.3 is v+1 :)
[11:40] <zsombi_> nik90: but I'm affraid we cannot get this alarm ID to 1.2 :(
[11:40] <zsombi_> so it has to go to 1.3
[11:41] <zsombi_> but I'll discuss this today with pmcgowan
[11:42] <nik90> zsombi_: its not critical to land this in 1.2 but the fact that i-dt and EDS landed their required fixes in vivid makes their effort go wasted
[11:42] <nik90> sure, let me know what comes out of it
[11:42] <zsombi_> nik90: exactly...
[11:42] <zsombi_> The MR was ready and I could not find anything, so it should have landed :/
[11:49] <vitimiti> I have followed this guide: https://wiki.ubuntu.com/Touch/CoreApps/Translations to set up the translation options for my project. Now I would like to translate the Spanish part myself, is there a way I can do this or should I just let the Ubuntu team do it?
[12:04] <sverzegnassi> hi all! is it safe to add some custom extension to the manifest.json file (i'm talking about UITK app)? i've seen a few core apps have some.
[12:10] <popey> sverzegnassi: yeah, the core apps have them for autopilot under x-test, and I believe they are just ignored
[12:10] <popey> you might want to run click-reviewer-tools over them though, and you'll probably just get warnings
[12:10] <popey> (also, sverzegnassi you have mail) :D
[12:11]  * nik90 is ecstatic..he just got his insider's BQ Device!
[12:12] <sverzegnassi> popey: yes, i'd like to add some info in the manifest for one of my app just because i'm lazy and i've built an AboutPage that grab the info from there
[12:12] <sverzegnassi> popey: yes, I've seen the mail. at the moment i'm not at home, and I don't remember all the details
[12:13] <Elleo> nik90: awesome :)
[12:13] <DanChapman> nik90: \o/
[12:17] <nik90> :)
[12:30] <popey> sverzegnassi: ok
[14:29] <zsombi_> nik90: http://pastebin.ubuntu.com/10838872/
[14:29] <zsombi_> nik90: sometimes I am getting a crash at the point when I launch the app on desktop
[14:29] <zsombi_> nik90: I have a comment about that so there's some GLib call you have there...
[14:32] <zsombi_> nik90: but still, seems if I do not cache the alarms, then I don't get crashes... though the first crash I got when the cache was taken away... I have to check how to get this more stable
[14:32] <zsombi_> but next week
[14:32] <nik90> zsombi_: hmm strange..I will look through AlarmPage.qml;
[14:33] <nik90> zsombi_: I don't even load anything in alarmpage.qml..just normal qtquick and ubuntu component imports
[14:33] <zsombi_> nik90: there's something after onCompleted...
[14:33] <zsombi_> nik90: do you have anything else which would cause some GLib calls?
[14:34] <nik90> zsombi_: clock app has a c++ plugin which uses Qtdbus to communicate to indicator-datetime..that's about it
[14:34] <zsombi_> aham... well, I'll go off now, I'll check it next week
[14:35] <nik90> zsombi_: ok..I will take the weekend to do some investigation
[14:37] <zsombi_> nik90: ouh! If I run the app with ALARM_BACKEND=memory, it crashes every time!!!
[14:38] <zsombi_> nik90: !!!!! QOrganizerManager::availableManagers().contains(envManager) crashes!!!
[14:38] <zsombi_> renatu: ^
[14:40] <renatu> zsombi_, probably you have a broken qorganizer plugin installed
[14:40] <zsombi_> renatu: hmmm! only me? It used to crash for nik90 as well...
[14:41] <nik90> zsombi_: true but it crashes only once or twice for me and it was a week or two ago?
[14:41] <renatu> zsombi_, I got this when I have a a memory or a eds plugin installed but built with a different qt version
[14:42] <zsombi_> nik90: renatu: if I remove that line of code, I do no longer get any crashes...
[14:42] <zsombi_> renatu: oh, f*k!
[14:44] <zsombi_> WTF??! qtdeclarative5-qtorganizer-plugin:
[14:44] <zsombi_>   Installed: 5.0~git20140515~29475884-0ubuntu9
[14:44] <zsombi_>   Candidate: 5.0~git20140515~29475884-0ubuntu9
[14:44] <zsombi_>   Version table:
[14:44] <zsombi_>  *** 5.0~git20140515~29475884-0ubuntu9 0
[14:44] <zsombi_>         500 http://archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
[14:44] <zsombi_>         100 /var/lib/dpkg/status
[14:44] <zsombi_> renatu: ^ look at that? is it really
[14:45] <zsombi_> renatu: is the plugin still qtdeclarative5-qtorganizer-plugin?
[14:45] <renatu> yes
[14:46] <zsombi_> renatu: and is it true that has not been built with 5.4.1?
[14:46] <zsombi_> renatu: what's yours?
[14:47] <renatu> zsombi_, I build it from source
[14:47] <zsombi_> ok, that's not a ref point then...
[14:53] <renatu> zsombi_, check the files on your: /usr/lib/x86_64-linux-gnu/qt5/plugins/organizer/
[14:53] <renatu> zsombi_, try remove one by one, to see which one is broken
[16:07] <nik90> charles: ping
[16:07] <charles> nik90: pong
[16:08] <nik90> charles: hey, can you get a MP to change the default alarm silence after duration to 10 minutes as specified by mpt?
[16:09] <nik90> charles: I was suppose to change the wording in the clock app side, and I will get a MP for that in my end
[16:09] <charles> nik90, alarm-duration-minutes is already 10 minutes in trunk?
[16:09] <nik90> s/suppose/supposed
[16:10] <nik90> charles: oh..I haven't tested clock app on vivid for sometime ...that's why I may have missed that
[17:00] <charles> nik90, ping me if it's not working for you, but the default should be 10 now
[17:04] <nik90> charles: just flashed latest vivid, and I see the default as 10 mins
[17:04] <charles> nik90, \o/
[17:05] <nik90> :)
[17:28] <TestDeveloper> hello
[17:29] <TestDeveloper> I want to create a new provider for owncloud. Is there a tutorial to do this?
[19:03] <popey> renatu: seen bug 1445586 from alesage ? "error" : "error code from SyncEvolution remote, status 400: REPORT 'meta data': bad HTTP status: <status 1.1, code 400, class 4, Bad Request>"
[19:03] <popey> :(
[19:15] <renatu> popey, are you using the version from silo?
[19:15] <popey> renatu: it wasn't me
[19:16] <renatu> yes the fix did not land yet
[19:16] <alesage> renatu, from a fresh vivid flash, using calendar from the store
[19:17] <renatu> alesage, if you want that working you need to get syncevolution from the silo
[19:17] <popey> ahh
[19:36] <alesage> popey, not sure what the process is here, may need a new silo and/or your advice
[22:53] <DF__> HI
[22:53] <DF__> can some one help me out??
[22:54] <beuno> DF__, what's up?
[22:54] <DF__> i have some problems with a mysql conection
[22:55] <beuno> DF__, on the ubuntu phone?
[22:55] <DF__> yep
[22:55] <DF__> and the development
[22:56] <DF__> bueno, i can't install the lib on my nexus 4
[23:03] <DF__> ...