[02:20] <cjwatson> pitti: http://d-jenkins.ubuntu-ci:8080/view/Utopic/view/AutoPkgTest/job/utopic-adt-kde-runtime/ARCH=i386,label=adt/45/console - we could really use "apt-get update || { sleep 15; apt-get update; }" or something in the adt setup
[02:32] <hallyn> xnox: hey, late in your tz, so probably not, but...  are you around?
[04:00] <pitti> cjwatson: curious, adt-run is already using that in most places (we talked about it a few months ago); apparently I forgot one place, I'll have a look
[04:00] <pitti> Good morning
[04:24] <pitti> slangasek: hey Steve!
[04:24] <pitti> slangasek: do you think it's ok to upload the sysvinit to -proposed and keep it there with a block-proposed bug? that way we can already run all the testing against it
[04:25] <pitti> slangasek: it's a relatively harmless effective change, after all
[04:34] <pitti> cjwatson: oh -- that log already *does* retry, and the second apt-get update succeeds; the BADSIG is bug 1345877
[04:34] <slangasek> pitti: I'd rather not deliberately put stuff into -proposed that we don't expect to get out immediately
[04:34] <slangasek> pitti: but I guess it's your call
[04:35] <pitti> slangasek: ah, I postponed it as the other day you said that there are some things you didn't like in the new versino, and you wanted to review
[04:35] <pitti> slangasek: also, I don't want to land it in traincon-0
[04:35] <pitti> cjwatson: ah no, the badsig is from the main archive, not from ddebs; so I guess this is a case where apt-get update failed twice in a row :/
[04:35] <slangasek> pitti: correct, I want to review the merge before it goes in, on account of some vexing upstream changes
[04:36] <pitti> slangasek: ok, then I won't upload it for now
[04:36] <slangasek> (and it's easier for me to review it than to give an accounting of all the things that have recently been wrong with sysvinit maintenance in Debian)
[06:08] <doko> pitti, jibel: could you restart the plv8 and pgagent autopkg tests? seem to be qemu issues
[06:08] <pitti> doko: no, pgagent is an actual bug; I just uploaded the transition to 9.4 to Debian, will auto-sync
[06:08] <doko> gwenview did fail before tpp
[06:08] <doko> ahh, ok
[06:08] <pitti> doko: plv8 as well, there's something wrong with the transition (it tries to pull in 9.3)
[06:08] <doko> well, blocking gcc-4.9 ...
[06:08] <pitti> doko: it's on my list for today, too
[06:54] <doko> Riddell, can you or #kubuntu have a look at the gwenview autopkg test failure?
[06:54] <dholbach> good morning
[07:01] <doko> dobey, ubuntu-sso-client ping, could you have a look at the autopkg test failure?
[07:16] <pitti> doko: ah, the fixed plv8 is still stuck in Debian binNEW
[07:16] <pitti> doko: I'll do an Ubuntu upload to unblock
[08:20] <cjwatson> pitti: oh, right, ugh.  ok
[08:22] <cjwatson> doko: I already applied a force-badtest hint to gwenview; no idea why it's still showing there
[08:22] <cjwatson> oh, p-m can only take one hint for any given package
[08:22] <cjwatson> doko: once everything else is fixed, tell me and I'll force-skiptest gcc-4.9
[08:45] <pitti> doko: plv8 is good now; I just removed the NBS, it should promote in the next cycle; (and unblock gcc)
[08:51] <doko> pitti, cjwatson: that leaves gcc-4.9 with pgagent (which will be synced from debian soonish), and gwenview
[08:52] <pitti> as the gwenview regression was introduced with 4:4.13.90-0ubuntu1 in -proposed, we could also just remove that package from -proposed
[08:53] <cjwatson> pitti: no
[08:53] <cjwatson> pitti: we've seen failures with earlier versions too; also please don't do anything to interfere with the megatransition
[08:53] <cjwatson> pitti: ScottK has already forwarded it upstream, and we think the failures are ignorable for now
[08:53] <cjwatson> hence my hint
[08:54] <pitti> ack
[08:54] <pitti> wrt. history, http://d-jenkins.ubuntu-ci:8080/job/utopic-adt-gwenview/20/ was an infrastructure problem, otherwise http://d-jenkins.ubuntu-ci:8080/job/utopic-adt-gwenview/? looks fairly stable (pass/fail)
[08:54] <cjwatson> oh, maybe the alleged failures with earlier versions are just adt-britney being confused
[08:55] <pitti> but override WFM, it's clearly not a gcc regressino in this case
[08:55] <cjwatson> notice how update_excuses says "autopkgtest for gwenview 4:4.13.2-0ubuntu2: Regression" in places
[08:56] <pitti> indeed; looks like it says the release version number there instead of the proposed version?
[08:57] <cjwatson> I guess the cause is wrong in the various control files, but argh that stuff hurts my brain
[08:57] <cjwatson> doko,pitti: ok, so I've hinted "force-skiptest gcc-4.9/4.9.1-3ubuntu2"
[08:57] <pitti> not a biggie right now either way
[08:57] <pitti> cjwatson: thanks
[08:58] <pitti> if it's any urgent, you can also skip the pgagent test; I suppose it'll still be a few hours until it gets imported and synced
[08:58] <cjwatson> "force-skiptest" skips all tests hung off a given upload
[08:58] <cjwatson> "force-badtest" skips just tests for a given failing package
[08:58] <pitti> ah
[08:59] <cjwatson> So in this case I meant to say "everything done, ignorable, or being fixed"
[09:00] <cjwatson> And none of it caused by gcc in any event, as far as I understand it
[09:11] <mlankhorst> cjwatson: fglrx won't be available for some time when I release xorg-server 1.16, in that case could fglrx be temporarily dropped or something?
[09:11] <seb128> shouldn't we hold on 1.16 until all drivers are ready instead?
[09:13] <cjwatson> mlankhorst: that seems questionable given that it's widely-used
[09:14] <cjwatson> mlankhorst: but seems that needs wider discussion rather than just asking me, a non-fglrx user :)
[09:14] <mlankhorst> there's radeon still available as alternative
[09:14] <seb128> -1 for letting users down this way
[09:15] <seb128> we decided some cycle ago to not do that anymore no?
[09:15] <mlankhorst> but we won't receive upgrades for radeon until very near final release :/
[09:23] <mlankhorst> and flipping the whole xorg-server near release sounds like a  bad idea, while some of the other changes are definitely needed
[09:24] <seb128> needed for what?
[09:24] <seb128> well, you should talk to other teams, maybe email ubuntu-devel@ with the plan and why we need the update even if we don't have all drivers
[09:24] <mlankhorst> I have mailed a CFT to ubuntu-devel@
[09:30] <cjwatson> Riddell: Can we slow down the KDE uploads for a bit?  I think libav might just have landed if not for the gwenview upload just now
[09:31] <cjwatson> argh, which is dep-wait
[09:31] <cjwatson> on something not uploaded yet!
[09:31] <cjwatson> tempted to remove that and copy the old one back
[09:34] <xnox> well, anything that would make britney transition things or give us a sensible list of things to fix is good.
[09:36] <cjwatson> xnox: I've got a sensible list and it says "gwenview"
[10:11] <cjwatson> libav migrating!
[10:11] <rbasak> \o/
[10:11] <cjwatson> publisher on manual to ensure that all the copies go in one batch
[10:20] <cjwatson> publisher on auto
[10:39] <mlankhorst> cjwatson: what about a solution where we upload xorg-server and all the packages to -proposed near feature freeze, and keep it there until the next fglrx release, hopefully in a week or 2 later?
[10:40] <cjwatson> I guess that's one option but be careful of things that might end up blocked on that
[10:40] <cjwatson> honestly I'd rather not be the decision-maker here - I'm going to have a lot to do with phone RTM
[10:42] <mlankhorst> well not requiring a FFe for xorg-server would be ok with me too
[10:51] <pitti> mlankhorst: so perhaps testing from a PPA would be better for now? (FWIW, I have no idea how important the fglrx driver is these days -- back then, radon worked just fine for me, but it's been years since I had something non-intel)
[10:51] <pitti> radeon even
[10:52] <mlankhorst> pitti: we have a ppa, but that doesn't get NEARLY as much testing as the archive does..
[10:52] <mlankhorst> I'll be lucky to get 10 people testing..
[10:52] <pitti> xorg-edgers how how that was called?
[10:53] <pitti> mlankhorst: OOI, in which regards is fglrx better than radeon these days?
[10:53] <mlankhorst> no idea, I tend to use radeon more. presumably fglrx has some features radeon lacks
[10:56] <pitti> I mean, if it doesn't work on some hardware, that's a good reason to not break utopic; if it's just marginally slower or eating a bit more power, temporarily dropping it seems just fine to me
[10:57] <pitti> (assuming that it automatically falls back to radeon)
[10:57] <pitti> comparing the vendor/product ID lists might help there?
[11:12] <mlankhorst> not really, mostly newer HW works minus radeon bugs
[11:12] <mlankhorst> it's just that the latest might not, no idea tbh
[11:25] <rbasak> Looking at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752796, it looks like a Perl 5.20 transition is due to hit sid on 12 August.
[11:26] <rbasak> That's before our feature freeze. Are we going to take that?
[11:26] <rbasak> I'm wondering whether to cherry-pick the fix for nginx that is in VCS but not uploaded to unstable yet.
[11:27] <mdeslaur> @pilot in
[11:34] <mlankhorst> pitti: oh and without xorg-server radeon will actually work worse, because it will lack the glamor updates
[11:56] <mvo_> jibel: can you confirm in the lap or on your test vm (when you have a moment) that #1347964 is no longer appearing?
[11:58] <jibel> mvo_, without any specific repo?
[12:01] <rbasak> pitti: the 'current specification' link from http://dep.debian.net/deps/dep8/ is broken.
[12:03] <mvo_> jibel: yeah, it should be fixed in the main repo already
[12:03] <mvo_> jibel: fingers crossed :)
[12:05] <jibel> mvo_, upgrade in progress ...
[12:09] <mvo_> jibel: you rock
[12:20] <juliank> slangasek: Is the patch debian/patches/gcc46-compatibility for gnu-efi still needed (what's the reason for building with gcc 4.6 these days?) or can this be synced from unstable to the new upstream release now?
[12:22] <juliank> If it can be dropped, a "syncpackage -s juliank gnu-efi" would be nice
[12:23] <pitti> rbasak: yeah, I fixed it in svn a few weeks ago and asked for updating it, but that didn't happen yet :/
[12:23] <rbasak> No worries
[12:54] <doko> jamespage, maven fun in proposed ... libcommons-logging-java and tomcat8 ...
[12:54] <jamespage> doko, joy joy
[12:54] <doko> can you have a look? http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[12:55] <doko> objenesis?
[12:55] <jamespage> doko, not right now - dealing with some other things today
[12:55] <jamespage> doko, as we doing tomcat8 for main this cycle?
[12:56] <jamespage> are we rather
[12:56] <doko> jamespage, you tell me ...
[12:56]  * jamespage thinks
[13:01] <doko> zul better should subscribe ubuntu-mir when filing MIR's ...
[13:02] <xnox> doko: should i make 3.5 default for llvm-default on ppc64el only? or should I instead fix powerpc build failure and work out if/when/can we switch to 3.5 by default?
[13:02]  * xnox looks at release schedule.
[13:04] <doko> xnox, I'd say make it the default on all architectures after checking that mesa is fine with it
[13:05] <xnox> doko: ack. this also means fixing powerpc build then.
[13:07] <doko> dholbach, you sponsored python-wsme, hangs now in component mismatches ... please file the 30 MIR which are required, or drop the build deps ...
[13:11] <dholbach> Noskcaj, ^
[13:12] <dholbach> doko, I followed up on the sponsoring bug - thanks - I thought I had checked all the build-deps and verified they were in main
[13:12] <dholbach> I must have missed something
[13:14] <dobey> doko: re: ubuntu-sso-client, do you have a link? i didn't get any e-mail about it failing
[13:15] <doko> dobey, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[13:16] <doko> tvoss|lunch, can you take care about https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/1349834 ?
[13:16] <dholbach> doko, I reopened the bug as well
[13:18] <dobey> sigh, why is squid not starting
[13:24] <apachelogger> mardy: heya, any chance of getting a new signon upload for utopic? we are currently porting kde-accounts and it appears as though the cmake config installed by the current package has a bit of a divergent name from what is in git (namely SignOnQtConfig.cmake vs. SignOnQt5Config.cmake)
[13:35] <jibel> mvo_, upgrade from 12.04.4 desktop + Trusty HWE stack -> Trusty is successful on amd64
[13:36]  * jibel hugs mvo_
[13:43]  * mvo_ hugs jibel
[13:44] <mvo_> thanks for confirming
[13:46] <tvoss> doko, on my list
[13:48] <cjwatson> rbasak: perl 5.20> I'm considering it if the rest of -proposed is quiet enough at that point
[13:50] <rbasak> cjwatson: OK, thanks. I didn't cherry-pick it for now, but the patch (for nginx) is there for us to grab if we need it.
[13:55] <arges> jamespage: hello. I see ceph/nova are in teh trusty review queue. Is it alright if I review these and potentially accept into proposed? I don't want to mess up any plans you already have
[13:56] <dholbach> shadeslayer, ready for the hangout in ~1h?
[13:56] <shadeslayer> yep
[13:56]  * shadeslayer is excited and nervous
[14:13]  * dholbach hugs shadeslayer
[14:13] <dholbach> all will be fine :)
[14:14] <shadeslayer> :D
[14:16] <doko> component-mismatches-proposed is frustrating ...
[14:23] <bzoltan> mitya57:  ping
[14:28] <bzoltan> mitya57:  I would need a friendly licensed maintainer who could review and approve an MR from us against the QtCreator packaging branch: https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtcreator. The patch is rather simple -> https://code.launchpad.net/~zeller-benjamin/kubuntu-packaging/qtcreator-ubuntudevice-qmlprojects/+merge/228665 It enables ubuntu devices to be Run targets for QML apps.
[14:35] <hallyn> pitti: do i understand right that cgmanger will start so long as there is a sysv init job but no systemd job;  and if i create a cgmanager.service disabled by default, then it won't start?
[14:38]  * hallyn tries
[14:44] <doko> apw, infinity, ogasawara: I assume we need a MIR for  linux-exynos5 ?
[14:45] <pitti> hallyn: yes, but the init.d and unit names need to be identical
[14:47] <hallyn> can do - thanks
[14:47] <jamespage> arges, +1 please go ahead
[14:48] <arges> jamespage: ok cool. thanks
[14:48] <infinity> doko: No.
[14:48] <infinity> doko: It shouldn't be in main.
[14:48] <infinity> doko: component-mismatches is lying to you.
[14:50] <arges> tinoco: jamespage : one concern of the nova upload are if bugs 1219658, 1267191 are fixed in the utopic version of nova (its not entirely clear)
[14:50] <jamespage> arges, lemme check
[14:51] <tinoco> arges: checking
[14:54] <hallyn> pitti: sorr, one more q - is there a .target representing "virtual filesystems (i.e. proc and sys) are mounted" ?
[14:55] <hallyn> local-fs is probably too much / too late;  oh, but maybe fine for cgmanager under systemd, as it's not needed for init there, duh
[14:57]  * xnox loves C++11 static_assert
[14:57] <xnox> __linux is not defined, ftw! =)
[15:02] <pitti> hallyn: that's already defined by basic.target, unless you specify DefaultDependencies=no all units can rely on those
[15:04] <tinoco> arges: rbd issue is applied
[15:05] <tinoco> checking other
[15:07] <tinoco> arges: other fix (cpu feature) is included but in a different source file (test_libvirt* changed to test_config)
[15:09] <tinoco> arges: i would say both are already applied to utopic nova-2014.2~2
[15:10] <hallyn> pitti: I want it to start as early as possible
[15:10] <pitti> hallyn: so not depending on anything will do that
[15:10] <pitti> hallyn: see man systemd.special: "Usually this should pull-in all mount points, swap devices, sockets, timers, and path units and other basic
[15:11] <hallyn> pitti: sys and proc will still be mounted?
[15:11] <pitti>            initialization necessary for general purpose daemons."
[15:11] <pitti> hallyn: I suppose you want all those
[15:11] <hallyn> the systemd manpages are hard to find :)  not found on my sid or trusty systems;  /me goes to manapges.ubuntu.com
[15:11] <pitti> err?
[15:11] <hallyn> still not
[15:12] <pitti> "man systemd.special"
[15:12] <pitti> oh, on utopic
[15:12] <hallyn> No manual entry for systemd.special
[15:12] <pitti> yes, we didn't have systemd on trusty
[15:12] <hallyn> yeah my utopic system is dead
[15:12] <hallyn> but also not found on unstable
[15:12] <hallyn> oh no, there it is
[15:13] <hallyn> didn't find dh_systemd_enable though
[15:13] <pitti> that's the dh-systemd build dep
[15:14] <hallyn> ok cool, so now i just need to figure out how to do some scripting before the service starts
[15:15] <pitti> hallyn: you can do stuff in ExecStartPre=
[15:15] <pitti> (man systemd.service for daemons, man systemd.unit for fields which apply to all units)
[15:15] <hallyn> pitti: thx
[15:17] <arges> tinoco: ok
[15:17] <doko> Noskcaj, dholbach: MIR's for jquery needed (or better get rid off this b-d)
[15:17] <dholbach> doko, that's for python-wsme?
[15:18] <doko> dholbach, no, that's a separate sync you sponsored
[15:18] <doko> http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[15:18] <dholbach> doko, sorry, which package was that?
[15:18] <doko> jquery
[15:19] <dholbach> huh?
[15:19] <dholbach> I can't see it here: https://launchpad.net/ubuntu/+source/jquery
[15:20] <doko> dholbach, https://launchpad.net/ubuntu/+source/jquery/1.7.2+dfsg-3ubuntu1
[15:21] <dholbach> ah, I was just surprised, because you said "sync" - let me take a second look
[15:21] <doko> sorry, merge
[15:23] <hallyn> pitti: is there a way for a ExecStartPre to tell systemd to simply skip this service (contingnet on output of the command)?  like exit 2 or something?  I don't see it in the manpage
[15:23] <arges> tinoco: where is the testcase for bug 1219658 ?
[15:25] <tinoco> arges: i changed description for "to be provided". i'll create my own tests. bugs were cloned from fedora. i put them together for a ppa (large install) and relied on real tests (fixed both bugs).
[15:25] <xnox> doko: https://bugs.launchpad.net/ubuntu/+source/gcc-4.9/+bug/1349907
[15:26] <xnox> doko: looks like that's the root cause for llvm-3.5/powerpc build failure, and affects debian and ubuntu. And also looks like complete obscure.
[15:26] <arges> tinoco: can you describe the test case in that SRU section ? it doesn't have to be a script, but some explainination of what steps are required to see the issue
[15:27] <tinoco> arges: will do. gimme some minutes, i'll get back to you on this
[15:27] <doko> xnox, please use __linux__
[15:28] <xnox> doko: sure, but __linux and linux is defined on all other arches, and with a default standard on powerpc.
[15:29] <doko> xnox, and?
[15:29] <xnox> doko: any preference for __linux__ vs __linux preference? I personally see __linux used for the first time.
 xnox, please use __linux__
[15:30] <xnox> doko: and? -> well it causes FTBFS on powerpc of other packages, and it's not clear to me weather gcc-4.9 with C11 standard enabled is backwards incompatible here on powerpc only, or wether all code is wrong.
[15:31] <xnox> doko: why is __linux defined at other standards, and on other arches including C11 standard level?
[15:32] <xnox> right, I found https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28314
[15:32] <xnox> which is good enough reference for me.
[15:33] <xnox> doko: which looks like reported by you =)
[15:33] <mitya57> bzoltan1: approved
[15:34] <xnox> thanks a lot!
[15:34] <doko> xnox, yes, and I won't change it on the package level
[15:34] <xnox> doko: excellent.
[15:39] <doko> xnox, what is problem fixing llvm?
[15:42] <xnox> doko: no problem, wrote a patch, test building and will submit upstream.
[15:42] <xnox> (and upload into ubuntu)
[15:44] <mdeslaur> @pilot out
[15:51] <tinoco> arges: changed 1267191 [testcase]. could you please tell bugs 1319710 and 1303536 they are a duplicate of 1267191 ? I keep getting timeouts to mark them duplicate.
[15:52] <arges> tinoco: technically they aren't targeted to ubuntu/nova, so we don't really need to mark them duplicates
[15:53] <tinoco> arges: ah ok, perfect
[15:53] <tinoco> checking the rbd testcase (it will be the same as the previous bug since it is a fix to a regression patch)
[15:54] <arges> tinoco: ok can you update that too please
[15:54] <tinoco> ok
[15:57] <tinoco> arges: done.
[15:57] <dholbach> doko, followed up on the merge proposal - thanks
[15:57] <tinoco> arges: i think both are ok now, let me know if you need anything else on this. tks!
[16:00] <arges> tinoco: ok one more thing... did you change the urgency= field in the changelog?
[16:00] <tinoco> checking
[16:00] <arges> or rather why did you do it
[16:01] <tinoco> urgency=high
[16:01] <tinoco> there were some outages because of these... P1 bug was created to provide fix
[16:01] <arges> why was it changed from urgency=medium?
[16:01] <tinoco> i had to provide this fix in few hours to avoid outage
[16:04] <arges> tinoco: i don't think that translates to updating the changelog urgency field
[16:07] <rbasak> Is it just me, or has dch's default changed recently or something?
[16:07] <rbasak> I've seen much more variance in the urgency field recently
[16:08] <xnox> default is medium these days.
[16:08] <xnox> used to be low.
[16:08] <xnox> makes zilch of a difference. (like +/- a couple of build score points, in build queuing in ubuntu)
[16:09] <arges> tinoco: anyway yea shouldn't make any difference editing that field. no need to modify it now
[16:09] <tinoco> arges: ok, tks chris
[16:10] <xnox> tinoco: yeah, but that field is not the semantic meaning you are guessing it has =)
[16:10]  * xnox ponders why i like yoda speak
[16:10] <tinoco> xnox: yep. totally agree now. tks guys
[16:11] <arges> tinoco: np thanks for the fix, its been accepted
[16:12] <mpt> ev, any progress on the database migration?
[16:13] <tinoco> arges: great, updating here. tks!
[16:26] <ev> mpt: the priority had to be dropped as IS just had to pick up a big project. We're working to make sure we don't put the existing data at risk as this gets put on hold.
[16:52] <rbasak> caribou or arges: please could you take a look at https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1349031? Is this a botched merge?
[16:54] <arges> rbasak: i know caribou is away on holiday. and i'm trying to remember this one...
[16:56] <arges> rbasak: looking at the diff i don't see 'ping6' or 'ipv6' or anything of that sort
[16:57] <rbasak> arges: http://paste.ubuntu.com/7896530/ is what I see
[16:57] <rbasak> That's debdiff backuppc_3.3.0-1.dsc backuppc_3.3.0-1ubuntu1.dsc|pastebinit
[16:58] <arges> ok i was looking at http://launchpadlibrarian.net/162543633/backuppc_3.2.1-4ubuntu2_3.3.0-1ubuntu1.diff.gz
[16:58] <rbasak> Yeah that diff is against the previous Ubuntu package.
[16:58] <arges> yup yup. ok
[16:59] <arges> so that merge added functionality; why do you think it was botched?
[16:59] <shadeslayer> ev: https://errors.ubuntu.com/?user=kubuntu-bugs&period=month still doesn't work
[16:59] <arges> added the ping6 functionality
[17:00] <ev> shadeslayer: bdmurray just arranged for a deployment containing that change
[17:00] <ev> should be up soon
[17:00] <shadeslayer> thx :)
[17:00] <rbasak> arges: it's not mentioned on the changelog
[17:00] <rbasak> arges: it looks to me (superficially, anyway) that Debian or upstream changed something about it, and what Ubuntu had before got carried forward, instead of taking upstream changes.
[17:01] <arges> rbasak: yup which is why the diff from the previous ubuntu version doesn't show that change. its a specific ubuntu patch somewhere
[17:02] <rbasak> arges: right, but were upstream changes in this area considered for this merge? The missing changelog entry suggests not.
[17:02] <rbasak> arges: are we sure that this cannot just be dropped?
[17:02] <rbasak> arges: because I see no mention of an addition of anything to do with ping6 in the previous changelog.
[17:03] <rbasak> arges: say for example that there was a bug, and upstream fixed it. If we carry forward what we had before, then we'll exclude that.
[17:04] <rbasak> arges: that seems to be the simplest explanation to me (at a cursory glance). Either that or a delta was introduced and I haven't found it documented anywhere.
[17:04] <bdmurray> ev: i think it has landed but the cronjob may not have run yet
[17:04] <arges> rbasak: so I'm not sure with this. I would look at the full changelog to see if this is documented anyway (in the Ubuntu version or Debian version). And if not try dropped it and test to see if we have the same functionality and it fixes that bug
[17:06] <bdmurray> ev, shadeslayer: it runs once a day so should work tomorrow
[17:07] <shadeslayer> bdmurray: thx
[18:05] <sarnold> Trevinho: smells like a duplicate of something else recently: 1349953
[18:06] <sarnold> Trevinho: and another instance of the password going into a previously active client: 1349961
[18:41] <doko> zul, commented on python-keystonemiddleware. there are a lot more missing MIR's
[18:42] <zul> doko:  thanks
[21:59] <Noskcaj> ScottK, Could you help me with python-wsme's component missmatches?
[22:02] <Noskcaj> A few releases ago the debian maintainer added build-depends on a few things in universe, which got dropped without a changelog entry when you merged it. I have since had the package synced, and now i can't get the package to build from source because of some tarball strangeness


[07:07] <dholbach> good morning
[09:53] <JamesTait> Good morning all; happy Friday, and happy Underdog Day! :-D
[09:58] <justCarakas> good morning JamesTait
[09:59] <JamesTait> justCarakas, o/
[12:04] <ahayzen> timp, ping
[12:09] <timp> ahayzen: hello
[12:09] <ahayzen> timp, is it possible in a pure QML app to make it fullscreen? ... i know you can do it in a QML/c++ or webapp
[12:12] <timp> ahayzen: a desktop app?
[12:12] <ahayzen> timp, no on the phone
[12:12] <timp> ahayzen: I'm not sure, but for phone it may be a setting in your desktop file
[12:12] <ahayzen> ah
[12:13] <ahayzen> timp, i can't see anything in the camera apps desktop file...but i assume that does it via c++?
[12:14] <timp> hmm. I may be wrong about the desktop file then
[12:15] <ahayzen> timp, in a webapp you use Window {} instead of MainView {} ? should i just use that for the QML app as well?
[12:15] <ahayzen> ...but then you don't have some of the same properties available
[12:15] <timp> ahayzen: I see that the camera-app indeed does it in cpp.
[12:16] <ahayzen> timp, is there any way of accessing that from QML?
[12:17] <timp> I think we should ask some unity8-dev about these things
[12:17] <ahayzen> i spot in some webapps that they do Window { visibility: Window.FullScreen }
[12:17] <ahayzen> but then i assume you can't use the MainView ?
[12:18] <timp> maybe Saviq or mzanetti are around?
[12:18] <timp> ahayzen: if you have a Window you can put the MainView inside of that
[12:18] <ahayzen> ooo
[12:18] <ahayzen> timp, i suspect that might work :) ... i'll try that after lunch thanks for the help :)
[12:19] <timp> I never explicitly define a Window though.
[12:20] <ahayzen> timp, i'll try it see if it works...
[12:24] <ahayzen> timp, well its fullscreen but its gets confused about rotation or which way around the view is or something and i get "Conflicting properties 'visible' and 'visibility'"
[12:28] <ahayzen> timp, ok managed to get rid of the error and reduced the rotation confusion a little
[12:34] <timp> ahayzen: some of the orientation support that is now in UITK is moving to unity
[12:34] <ahayzen> \o/
[12:34] <ahayzen> oh with the shell rotation?
[12:34] <timp> ahayzen: see the revisions here by Daniel https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging
[12:36] <timp> best ask him, he knows more about it. But I don't see him around now.
[12:37] <ahayzen> looks pretty cool :)
[12:38] <ahayzen> do you know if there is any way to tell if the device you are working with has a particular sensor? eg if it has a tiltsensor?
[12:39] <timp> we don't have that in ui toolkit. Maybe you'd need cpp for that
[12:39] <ahayzen> heh ok :)
[12:41] <dholbach> dpm, davidcalle: we're done with replacing 作用域 :)
[12:41] <dholbach> now for the rest of the links which need fixing :)
[12:44] <davidcalle> dholbach, yay :)
[12:53] <dholbach> jdstrand, https://developer.ubuntu.com/en/apps/platform/guides/app-confinement/ and https://developer.ubuntu.com/zh-cn/apps/platform/guides/app-confinement/ refer to https://bugs.launchpad.net/ubuntu/+source/qtubuntu-sensors/+bug/1227116 - I guess we can remove the link to the bug now?
[12:56] <davidcalle> dholbach, dpm, one interesting/subtle thing to note for page layouts: the number of cols used by an item is relative to the parent one *on a twleve cols base*. eg: <div class="four-col"> inside a "twelve-col" div is the same size as a "six-col" div inside an "eight-col" div.
[12:57] <dholbach> davidcalle, I tried never to touch any of those items
[12:57] <davidcalle> dholbach, you should, it's "fun" ;-)
[12:57] <dholbach> no :)
[12:57] <dholbach> I have enough fun in the area I'm working on :)
[13:00]  * dpm reads that twice
[13:03] <dpm> davidcalle, good to know, thanks! I generally try to have one single twelve-col parent, in which page would you use cols inside an eight-col parent?
[13:03] <davidcalle> dpm, all the text (as requested by you) :p
[13:04] <davidcalle> dpm, jk, images in text. I'm aligning them to the grid
[13:04] <dpm> davidcalle, yeah :) but I mean, in which page have you used columns inside that?
[13:05] <dpm> do you have an example?
[13:05] <davidcalle> dpm, https://developer.ubuntu.com/en/apps/html-5/tutorials/cordova-camera-app-tutorial
[13:06] <davidcalle> dpm, the page is not finished (still waiting on the middle section), but images are four-col
[13:07] <davidcalle> dpm, of course, you can also switch back to twelve for images
[13:07] <dpm> davidcalle, ok, gotcha. But do images not float to the left in any case?
[13:08] <dpm> man, btw, the tutorials and the guides are looking fantastic with the new site
[13:10] <dpm> davidcalle, another thing we could do for long images is to put them on the empty 4-col at the right. This is just a thought, I'm not asking to change it :)
[13:11] <davidcalle> dpm, yes, but with cols, all image sizes are consistent, you can align them, side by side, etc. Which brings back some flexibility to that wonderful editor we will learn to love one day.
[13:11] <dpm> :-)
[13:11] <dpm> ok, makes sense
[13:12] <davidcalle> dpm, indeed, but the android dev site does it and it's not that great in terms of readability (but it works well to introduce a new section or a new theme, though)
[13:12] <dpm> ok
[13:12] <davidcalle> ( a bit like a hero img)
[13:30] <mzanetti> timp: what up?
[13:32] <timp> mzanetti: ahayzen was having some questions about running apps fullscreen on the phone (is that possible from qml, or do you need cpp for that?). I didn't really know the answer so I was looking for a unity8-dev to help out
[13:34] <mzanetti> ah. I'm not sure tbh... I know the gallery app uses it so it must be possible somehow
[13:34] <mzanetti> might well be that it just does QQuickView->showFullscreen()
[13:36] <mzanetti> timp: ahayzen: http://bazaar.launchpad.net/~phablet-team/gallery-app/trunk/view/head:/src/gallery-application.cpp#L242
[13:36] <mzanetti> timp: I guess this means MainView lacks
[13:40] <timp> mzanetti: thanks
[13:41] <timp> mzanetti: MainView is written in qml only and inherits from some other qml components
[13:41] <timp> mzanetti: so it may be a bit tricky to add a "fullscreen" property there
[13:41] <timp> should be possible though.. Not sure if we want that. Do many apps need a fullscreen mode?
[13:42] <jdstrand> dholbach: yes, thjat can be removed
[13:43] <jdstrand> dholbach: is that something you are looking at or shall I?
[13:46] <aquarius> dpm, do you know of any popular apps which use URLDispatcher (that is: they register themselves for handling a "special" URL) other than the clock ("alarm:"), the music app ("album:"), and the messaging app ("message:") ?
[13:49] <ahayzen> timp, mzanetti, thanks :) i've nearly managed to hack window around mainview to work
[13:50] <ahayzen> jdstrand, ping
[13:50] <jdstrand> ahayzen: hey
[13:50] <ahayzen> jdstrand, Hey, i've been writing a game that uses a TiltSensor and have noticed I do not need any apparmor policies? I have checked here http://developer.ubuntu.com/apps/platform/guides/app-confinement/ and it says by the 'sensor' policy 'policy pending due to LP: #1227116', but that bug is now resolved. So should this policy exist and be enforced?
[13:52] <jdstrand> ahayzen: what policy version are you using?
[13:53] <ahayzen> jdstrand, 1.2
[13:54] <jdstrand> ahayzen: you are supposed to get haptic for free, and then get fill access to usensorsd via 'sensors'
[13:55] <jdstrand> s/fill/full/
[13:55] <ahayzen> jdstrand, i seem to be able to run with no policies and can access the TiltSensor readings
[13:55] <jdstrand> oh, and there there is: 'apps may always use the accelerometer and orientation sensor'
[13:55] <jdstrand> /etc/xdg/QtProject/Sensors.conf r,
[13:56] <ahayzen> ah
[13:56] <mzanetti> ahayzen: please let me know how you get it to work in qml only
[13:56] <mzanetti> I'd need that for a bunch of apps too (didn't really investigate)
[13:57] <mzanetti> timp: yes, I'd say many need that. especially games
[13:58] <ahayzen> mzanetti, basically i've done this https://code.launchpad.net/~andrew-hayzen/volleyball2d/fullscreen/+merge/245196
[13:58] <ahayzen> mzanetti, just put the MainView inside the Window as timp said
[13:59] <mzanetti> ahayzen: nice. thanks
[13:59] <ahayzen> mzanetti, i then just had to play about with my detection of when it is in portrait
[13:59] <timp> mzanetti: Should games use MainView? That's there mainly to add the app header, and (currently) automatic orientation
[13:59] <timp> hmm let me check ahayzen's code :)
[14:00] <ahayzen> timp, my game uses Page {} for the settings etc
[14:00] <ahayzen> timp, but yeah most just directly put the Game {} directly instead of MainView IIRC
[14:00] <timp> ahayzen: oh the change is not that big :) nice!
[14:00] <mzanetti> timp: how does that work with applicationId stuff then if you don't use a MainView?
[14:01] <ahayzen> ^^ was my other thought
[14:01] <timp> hmm
[14:01] <timp> mzanetti: that's the applicationName property?
[14:02] <mzanetti> yep
[14:02] <mzanetti> ahayzen: love that game btw
[14:02] <mzanetti> have been playing an hour at least yesterday :D
[14:02] <ahayzen> mzanetti, awesome thanks :) still some stuff to clean up but the basis is there
[14:02] <mzanetti> but man... it's hard!
[14:02] <timp> mzanetti: all that MainView does with that is this: http://pastebin.ubuntu.com/9569973/
[14:03] <mzanetti> didn't win a single time
[14:03] <ahayzen> yeah there is no AI difficulty levels yet
[14:03] <timp> so that can easily be repoduced without the MainView
[14:03] <mzanetti> timp: ah ok, yep, that seems ok
[14:03] <timp> but ahayzen's solution with a MainView inside a fullscreen Window looks like a good solution anyway :)
[14:03] <ahayzen> its just on 'hardest' ... i know a way to *always* win though ;) although i'll patch that soon with some new AI logic hehe
[14:04] <mzanetti> I managed to lose 5:4 at best
[14:04] <ahayzen> hah
[14:08] <dholbach> jdstrand, will do
[14:09] <jdstrand> dholbach: thanks!
[14:13] <dholbach> done :)
[14:15] <jdstrand> cool
[14:15] <dpm> aquarius, reminder does, but I'm not sure that is in trunk yet
[14:28] <mzanetti> jdstrand: hey, when developing apps it's really annoying that the system constantly prints some "Error opening shm" into the app's debug messages. I've looked into the code that prints it and I have a feeling it's denied by apparmor to access that.
[14:29] <mzanetti> what would you say would be way to go to fix that? I guess we won't allow it to access that... but then I don't really know if lttng is even useful without it
[14:33] <aquarius> dpm, ooh, really? who do I ask about details of that?
[14:35] <popey> aquarius: mzanetti ☻
[14:36] <mzanetti> http://bazaar.launchpad.net/~reminders-app-dev/reminders-app/trunk/view/head:/src/app/main.cpp#L60
[14:36] <mzanetti> http://bazaar.launchpad.net/~reminders-app-dev/reminders-app/trunk/view/head:/src/app/qml/reminders.qml#L56
[14:37] <mzanetti> http://bazaar.launchpad.net/~reminders-app-dev/reminders-app/trunk/view/head:/manifest.json.in#L11
[14:37] <mzanetti> and http://bazaar.launchpad.net/~reminders-app-dev/reminders-app/trunk/view/head:/reminders.url-dispatcher
[14:37] <mzanetti> aquarius: ^
[14:37] <aquarius> aha, evernote: URLs.
[14:38]  * aquarius rtfs :)
[14:38] <aquarius> ah, darn, I can't provide the *text* for a note via uridispatcher.
[14:39] <mzanetti> nope... I guess we could add that
[14:39] <aquarius> does the reminders app run on 14.04?
[14:39] <mzanetti> yes
[14:39] <aquarius> (desktop)
[14:39] <mzanetti> it's in apt
[14:39] <mzanetti> although I'm not sure if url-dispatcher does
[14:39] <aquarius> might add it myself. I'll think about it. It's all part of my Current Master Plan :)
[14:40] <mzanetti> its quite straight forward... you just create that json file describing you url, register that in the manifest file
[14:41] <mzanetti> then, if the app is running you'll get calls from UriHandler.onOpened
[14:41] <aquarius> *nod* yep
[14:41] <mzanetti> if not, the app will be started and the uri passed as cmdline arg
[14:43] <aquarius> hrm. Trying to build it in Ubuntu SDK, I get "error: [CMakeFiles/com.ubuntu.reminders.desktop] Error 127"
[14:43] <aquarius> useful, Ubuntu SDK. Not.
[14:44] <aquarius> aha! there is a COmpile Output tab with actual errors in. GOod :)
[14:45]  * aquarius installs intltool
[14:48] <aquarius> mzanetti, how do I run it? I can build it now, but clicking the big Run triangle in Ubuntu SDK says "no executable specified"
[14:48] <aquarius> ah, I need to select "reminders2", do I?
[14:49] <aquarius> hm. "module "QtQuick" version 2.3 is not installed "
[14:52] <aquarius> mzanetti, are you sure this works on 14.04? http://packages.ubuntu.com/search?keywords=reminders-app only has it packaged for 14.10 and vivid
[14:54] <mzanetti> aquarius: hmm... trunk might not. however you should be able to just change the imports to QtQuick 2.2 and it should work
[14:54] <mzanetti> oh, you said 14.04
[14:54] <mzanetti> then you might need QtQuick 2.1 :D
[14:56] <mzanetti> aquarius: but unless you install it with click, I don't think url-dispatcher works on the desktop
[14:56] <aquarius> changing to 2.2 seems to work
[14:56] <mzanetti> ok
[14:56] <aquarius> I'm fine with urldispatcher not working - I can just run the app with the url on the command line
[14:56] <aquarius> and edit the tests
[14:56] <aquarius> but! having changed to 2.2, I still get an error when running
[14:56] <aquarius> qml/components/RtfButton.qml:26:32: Invalid alias location
[14:56] <aquarius>          property alias iconSource: icon.source
[14:57] <aquarius> don't even know what that means
[14:57]  * aquarius googles :)
[15:01] <mzanetti> hmm
[15:01] <mzanetti> aquarius: I guess you can work around that by changing it to: property alias iconSource: icon.iconSource
[15:01] <aquarius> I have temporarily worked around it by making that a string property, which means that I won't get any icons, but I can live with that :)
[15:01] <mzanetti> let me dig out the old docs
[15:01] <mzanetti> ok
[15:02] <aquarius> wtf? Now it's claiming that AccountServiceModel doesn't have an applicationId property, which indeed it does not according to the docs, but then how did it ever work for anyone?
[15:02] <aquarius>              applicationId: "com.ubuntu.reminders_reminders"
[15:02] <aquarius> qml/reminders.qml:248:9: Cannot assign to non-existent property "applicationId"
[15:03] <mzanetti> aquarius: well, it probably does have that in the newer version, no?
[15:03] <aquarius> but you're not *using* a newer version; you're using Ubuntu.Components 1.1.
[15:03] <mzanetti> http://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.OnlineAccounts.AccountServiceModel/
[15:03] <aquarius> unless the SDK makes breaking changes while keeping the same version number?
[15:03] <mzanetti> fair point
[15:04] <mzanetti> mardy: ^
[15:04] <aquarius> what? that's a possibility? I was joking!
[15:04]  * aquarius does the angry look.
[15:04] <aquarius> this is what version numbers are *for*!
[15:04] <mzanetti> aquarius: well, it's in the import of Ubuntu.OnlineAccounts
[15:04] <aquarius> mardy, ping, then :)
[15:04] <mzanetti> and yeah, according to the docs it's still at 0.1
[15:05] <aquarius> ya, if you were using a newer version than I have then I'd have failed on the import
[15:05] <aquarius> which means that new properties got added to Ubuntu.OnlineAccounts 0.1 rather than a new version number
[15:06] <mzanetti> yes
[15:06] <aquarius> and that means it won't run on 14.04 but it's impossible to tell why :(
[15:06]  * aquarius looks sad.
[15:06] <mzanetti> well, not impossible to tell, but yeah, you do have a point
[15:07] <mzanetti> aquarius: in any case, you can just comment that line away and get going
[15:07] <mzanetti> it won't break much iirc
[15:07] <aquarius> yay! now it starts up at least
[15:08] <mzanetti> sooo. now the real online accounts fun :D
[15:08] <mzanetti> you have to add a evernote account in systemsettings (the desktop one)
[15:08] <mzanetti> you can install online-accounts-plugin-evernote for that
[15:08] <aquarius> *nod*
[15:08] <mzanetti> then restart the app and *it should* work
[15:08] <mardy> aquarius, mzanetti: the applicationId was indeed a later addition, let me check when it happened...
[15:08] <aquarius> am just filing an aggravated bug for mardy to read ;)
[15:10] <aquarius> mardy, aha, you're here. I don't mind that new properties were added, that's fine -- I mind that the version number stayed the same, so I can't tell whether the version I have will work or not.
[15:10] <mardy> aquarius: so, it happened in May, and indeed I forgot to bump the version number
[15:10] <aquarius> mardy, http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.OnlineAccounts.AccountServiceModel/ and http://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.OnlineAccounts.AccountServiceModel/ have different API and the same version number :(
[15:11] <aquarius> is it worth me filing a bug about it, or is it now too late?
[15:11] <mardy> aquarius: right, please file a bug, I guess we can bump the version number, then push the new lib to 14.10 and re-update the docs
[15:13] <aquarius> https://bugs.launchpad.net/accounts-qml-module/+bug/1404272 filed :)
[15:14] <aquarius> mzanetti, do I use my existing evernote account, or do I create a new one for the sandbox?
[15:16] <mzanetti> aquarius: however you want. if you want sandbox, you need to install account-plugin-evernote-sandbox and start the app with --sandbox
[15:16] <aquarius> mzanetti, 14.04 only has the sandbox plugin for online accounts, afaict
[15:16] <mzanetti> hmm, really
[15:17] <mzanetti> yeah... could be
[15:17] <aquarius> $ apt-cache search evernote
[15:17] <aquarius> account-plugin-evernote - Allow Ubuntu to access the Evernote developer sandbox
[15:17] <mzanetti> right.. then we created the production one only afterwards
[15:17] <aquarius> ah, using my real account doesn't work, so I'll create a new one :)
[15:17] <mzanetti> I'd like to recommend you to use the offline-mode branch which would allow you to use the app without evernote account
[15:17] <mzanetti> however, I really don't know how that behaves on 14.04
[15:18] <aquarius> I would, but you only handle evernote: URLs, right?
[15:18] <mzanetti> we handle them offline too :)
[15:18] <mzanetti> if you want to try: https://code.launchpad.net/~mzanetti/reminders-app/offline-mode/+merge/244713
[15:18] <aquarius> :-)
[15:19] <mzanetti> I thought before I should probably change it to reminders:// now that we don't have a hard dep on evernote any more
[15:19] <aquarius> indeed :)
[15:21] <mzanetti> aquarius: there are rumors you saw an ubuntu phone :)
[15:21] <mzanetti> exciting times, eh?
[15:21] <aquarius> yes!
[15:21] <aquarius> I got a nice little briefing from cparrino and rupinder
[15:22] <aquarius> I really like the pitch -- not locking your stuff up behind a grid of icons.
[15:23] <aquarius> hm. We now start up OK, but I get the spinner for ever... and a ton of warnings
[15:23] <aquarius> Error fetching username: "Not connected."
[15:23] <aquarius> that seems relevant...
[15:24] <dholbach> dpm, what do we do about http://developer.ubuntu.com/en/apps/qml/cookbook/?
[15:25] <mzanetti> aquarius: that's with trunk or the offline-mode branch?
[15:25] <aquarius> trunk
[15:25] <aquarius> http://paste.ubuntu.com/9570579/
[15:26] <mzanetti> hmm... it should get the account from OA now and then connect
[15:26] <aquarius> line 15 is where userstore.cpp throws the error about not being connected
[15:26] <mzanetti> ah no, it did that
[15:27]  * mzanetti looks up the code
[15:28] <mzanetti> ah right... mismatch in the plugin and the app (as you have the old OA plugin)
[15:28] <mzanetti> aquarius: edit reminders.qml:262
[15:29] <mzanetti> change it to EvernoteConnection.hostname = "http://sandbox.evernote.com"
[15:29] <mzanetti> or actually https://sandbox.evernote.com
[15:30] <aquarius> ok, progress... no more spinner. Now the connection actually fails and the app catches it
[15:30] <mzanetti> hmpf
[15:30] <mzanetti> have a meeting now
[15:31] <aquarius> I don't think that's the right URL. I'll look into it
[15:31] <aquarius> getting Thrift: Fri Dec 19 15:31:06 2014 TSocket::open() getaddrinfo() <Host: http://sandbox.evernote.com Port: 443>Name or service not known
[15:31] <aquarius> for both http and https
[15:32] <aquarius> ahaha!
[15:32] <aquarius> it's a hostname, not a url :)
[15:32] <aquarius> and now I am connected!
[15:32] <mzanetti> ah :)
[15:56] <aquarius> mzanetti, have filed https://bugs.launchpad.net/reminders-app/+bug/1404289 whining about needlessly requiring qtquick 2.3 ;-)
[15:57] <aquarius> mzanetti, also, http://paste.ubuntu.com/9570863/ improves the URL parser a bit, allowing arbitrary query strings, and implements one example: you can specify the title of a newly created note.
[15:58] <aquarius> mzanetti, it's not a proper merge request because I also had to make about a million comment-this-out-so-it-works-on-14.04 changes which should not be merged :)
[15:58] <aquarius> mzanetti, I'd have allowed specifying the body of the new note in the querystring as well, but I don't know how to do that; NotesStore.createNote does not return the note it's just created!
[16:00] <mzanetti> aquarius: thanks for the feedback :)
[16:00] <mzanetti> no worries about the merge proposal, I'll put it in here somewhere.
[16:00] <mzanetti> and yes, currently it's all async, however, now with the offline mode support that could (or probably should) be changed
[16:01] <aquarius> you can probably think of a zillion other parameters that could be passed in, but I'll leave that to you :)
[16:01] <mzanetti> yeah... we just added the ones that would be useful to call from the (upcoming) scope
[16:02] <aquarius> being async is the right thing to do, certainly! NotesStore.createNote(notetitle, null, function(newnote) { console.log("this is the new note:", newnote); });
[16:02] <aquarius> that is, provide a callback
[16:03] <aquarius> better still, return a Promise, but that's probably a bit advanced for QML's slightly noddy JS parser ;)
[16:03] <mzanetti> well, the callback is there NotesStore::noteAdded()
[16:03] <aquarius> oh!
[16:03] <mzanetti> but I guess what I'm going to do is to return the note straight away
[16:04] <aquarius> I should have done that then :)
[16:04] <mzanetti> and then when I get the evernote sync reply I change it's guid
[16:04] <mzanetti> current trunk is quite bad with error handling though
[16:04] <mzanetti> so if it goes wrong you won't get anything atm
[16:05] <mzanetti> which again is a non-issue with offline mode because it'll just try to sync later and keep the note offline for the time being
[16:05] <aquarius> fair enough. I'm not sure if I'd use this (I'm still thinking about how it would fit into my current app plan) but it seemed an easy enough contribution to make :)
[16:08] <jdstrand> mzanetti: I guess you are referring to bug #1260491
[16:08] <jdstrand> mzanetti: "Talking with tedg, these shouldn't be available to confined apps and we can safely explicitly deny the access to silence the errors."
[16:09] <jdstrand> mzanetti: so, apparmor is denying it, but silently. lttng should probably suppress the log message
[16:10] <mzanetti> jdstrand: ah, yeah. but the code is not ours and it doesn't have a possibility to silence things at compile time or so (already checked that).
[16:10] <mzanetti> maybe that could be added
[16:11] <mzanetti> but yes, that seems to be it
[16:12] <mzanetti> thanks
[16:19] <aquarius> anyone got examples of what they'd consider a really nicely visually designed SDK app?
[16:24] <mzanetti> aquarius: I guess the internal ones, like messaging, dialer etc. Some of the core apps look quite good too, like the new music app. And imo nik90_ did a good job with that tv series app (forgot the name)
[16:24] <ahayzen> mzanetti, nik90_ 's 'flashback'?
[16:24] <mzanetti> yep, that's the one
[16:24] <aquarius> aah, yeah, I did like nik90_'s app, indeed
[16:25] <ahayzen> new music app \o/ :)
[16:26] <aquarius> the new music app does look good, but it looks good because it has loads of cool art to choose from, which is not the case for my app :)
[16:26] <mzanetti> very good point
[16:26] <mzanetti> yeah, I'm always struggling with that too
[16:26] <aquarius> nik90_, who did the visual design for Flashback?
[16:27] <ahayzen> hah yeah .. we don't have bottom edge yet though :/
[16:28] <aquarius> ah! there was that little group of people, wasn't there? who were offering designer services
[16:28] <aquarius> torico or something
[16:28]  * aquarius googles.
[16:28] <aquarius> yep! torico. https://plus.google.com/107423272812169770223/posts/HiVAkp1Yn1W
[16:28] <aquarius> wonder if they're still up for it?
[16:29] <aquarius> huh. seems perhaps not; hardly anyone in the channel :)
[16:29] <mzanetti> ahayzen: just opened the music app: http://i.imgur.com/csLySx2.png
[16:29] <ahayzen> hah oh dear
[16:30] <ahayzen> mzanetti, we are still waiting for empty state designs from the designers as well :/ thats just some text we put there but we should probably wrap that lol
[16:30] <mzanetti> yep, wrapping would help :)
[16:30] <ahayzen> mzanetti, the 'tap to shuffle music' is now hidden if you don't have any music as well :)
[16:30] <mzanetti> seems reasonable too :)
[16:30] <aquarius> 'The form [from torico] "Application Ideas " is no longer accepting responses.'
[16:30] <aquarius> oh well :)
[16:31] <mzanetti> ahayzen: actually you probably should just pop the complete stack
[16:31] <ahayzen> mzanetti, the toolbar is a rectangle over the top of everything?
[16:31] <mzanetti> ahayzen: some image that shows a PC and Phone connected by cable and some text would be nice I guess
[16:31] <ahayzen> ..its custom
[16:31] <ahayzen> mzanetti, yeah thats what we wanted
[16:32] <ahayzen> mzanetti, but we need design to design it...we even have a walkthrough prototype somewhere
[16:39] <mzanetti> ahayzen: hah. I just won!
[16:39] <ahayzen> mzanetti, well done :)
[16:39] <mzanetti> ahayzen: while you're waiting on design, you can add multiplayer over bluetooth to it
[16:39] <ahayzen> mzanetti, yeah i've already thought about that... bluetooth vs wlan
[16:39] <ahayzen> mzanetti, as it runs really well on the desktop as well
[16:41] <ahayzen> mzanetti, note the click package is arm only you'll have to branch and run to do it on the desktop a the moment
[18:44] <mhall119> timp: Kaleo: https://plus.google.com/u/0/111980561516715514914/posts/FUrmN5F9uWi what would cause this?
[18:52] <rpadovani> mhall119, different toolkit maybe?
[18:54] <bzoltan_> mhall119:  my quick answer is that the phone is vivid and the desktop is not.
[18:55] <mhall119> bzoltan_: assuming they use the same UITK version in their imports, like Ubuntu.Components 1.0, shouldn't they look the same?
[18:55] <mhall119> or will they still get 1.1 versions of the components if they're available?
[18:55] <mhall119> or 1.2 or whatever is on the phone
[18:56] <bzoltan_> mhall119: we had 1.1 release both on V and on U
[18:57] <bzoltan_> mhall119: anyhow, the first question I would ask is about the image number and the desktop series
[18:57] <mhall119> ok, ignore the specific version numbers, the question is whether it'll use a newer version that what was specified if a newer version exists on the device
[19:00] <rpadovani> mhall119, or maybe is only a bugfix that is landed on vivid, and not on Utopic yet - so the experience is different atm, but at the end Components 1.1 will have the same behavior both on desktop and on phone
[19:01] <rpadovani> mhall119, I think this is a consequence of this bugfix: #1386208
[19:02] <rpadovani> see comment nr 8
[19:02] <rpadovani> bug 1386208
[19:04] <mhall119> thanks rpadovani
[19:49] <Letozaf_> mzanetti, hey
[19:55] <mzanetti> Letozaf_: hi
[19:57] <Letozaf_> mzanetti, I am having some issues running reminders autopilot tests: https://dl.dropboxusercontent.com/u/10083981/Ubuntu%20errors/Evernote-1.png   and http://paste.ubuntu.com/9572868/
[19:57] <Letozaf_> mzanetti, I am running them on vivid with autopilot3
[19:58] <mzanetti> Letozaf_: need to try. gimme a bit
[19:58] <Letozaf_> mzanetti, no problem I can wait :-)
[20:11] <mzanetti> Letozaf_: hmm... I don't get this error here
[20:12] <Letozaf_> mzanetti, you are on vivid like me ?
[20:12] <mzanetti> yes
[20:13] <Letozaf_> mzanetti, I used to write autopilot tests for reminders time ago, could it be I have some directory with old configurations to cancel ?
[20:13] <bzoltan_> rpadovani: no UITK changes will land on Utopic as Utopic is closed.
[20:14] <bzoltan_> rpadovani: mhall119: it is important to note that convergence is between form factors and not between Ubuntu series
[20:16] <mzanetti> Letozaf_: actually now I can reproduce it
[20:16] <mzanetti> Letozaf_: still need to figure how to fix it
[20:16] <Letozaf_> mzanetti, ok
[20:16] <Letozaf_> mzanetti, you can let me know by email if you are busy now... I am not in a hurry
[20:17] <rpadovani> bzoltan_, no, wait, so we could have different behavior on different releases with the same component version? I expect the behavior of , I dunno, Text, it's the same both on vivid and utopic if I imported the same version of Ubuntu.Components (e.g 1.1)
[20:21] <mzanetti> Letozaf_: there seems to be a bug in the autopilot tests
[20:22] <mzanetti> Letozaf_: each time I run them it creates a new account
[20:22] <mzanetti> and then fails to use the newly created account
[20:23] <mzanetti> it still works on jenkins for some reason
[20:24]  * Letozaf_ is looking at the tests
[20:45] <Letozaf_> mzanetti, I am unable to delete the Evernote accounts created by autopilot tests in online accounts I have Permission Denied error
[20:45] <mzanetti> Letozaf_: yeah, I had to delete the accounts.db too
[20:45] <mzanetti> ~./config/libaccounts-glib/accounts.db
[20:45] <mzanetti> warning: it'll drop ALL the accounts
[20:45] <Letozaf_> mzanetti, ok thanks, I was wondering were it was :)
[20:45] <Letozaf_> mzanetti, no matter
[21:03]  * Letozaf_ needs to reboot


[00:04] <mrand> running in a VM probably would take some extra cpu power.  But yeah, do yourself a favor and ebay those cards while you still (hopefully) can.
[00:04] <mrand> Homefront_Office: ^
[00:06] <Homefront_Office> mrand, Trust me I will after what I put my self through to get this up... not doing it again! I will get ion for my bed
[00:06] <Homefront_Office> room
[00:47] <Jonathon> I am trying to install mythbuntu 10.04 on my existing system, just with a different drive (my old system is too old to even consider upgrade). Trouble is that the drive does not show up so I can install onto it, yet if I go into a shell I can see the drive and access it through fdisk etc. Any thoughts?
[00:53] <momelod> The ubuntu installer does not recognize your disk?
[00:54] <Jonathon> momelod: apparently not?!
[00:55] <Jonathon> seems rather strange, as it is a standard 80G IDE like the previous one I replaced to do the new install? Difference here is that 10.04 recognises it (in the shell) as sda and the installer can't seem to see it?
[01:05] <Jonathon> the old install shows it as sdb btw
[01:12] <Jonathon> hdb that should be
[01:23] <patdk-lap> heh, I still like my pvr-350, it works good for recording analog
[01:23] <patdk-lap> I would like to upgrade, to pcie versions, but there are none that are supported :(
[01:24] <patdk-lap> the only option is the pvr-1600, and that is still pci, not really an upgrade
[01:25] <patdk-lap> jon, there should not be any /dev/hd* things at all in 10.04
[01:56] <Jonathon> patdk-lap: that certainly is the case that I am seeing. What used to be /dev/hdb is now showing as /dev/sda, but the installer does not recognise it for some reason?
[02:14] <Jonathon> ok. Downloading 10.10 to give it go and see if that works
[02:17] <patdk-lap> heh
[02:54] <patdk-lap> any better? (me personally doesn't think it would)
[07:28] <MoMo> I have a Dell Inspiron Desktop 570 that I am using at my frontend -- it had HDMI out and when I do a lspci | grep VGA ... i get a ATI Radeon HD 4200 ... my current problem is that I can't get my audio across the HDMI cable.  any ideas where to start?
[12:09] <patdk-lap> Momo, first, does the video card have a built in sound card? or do you need to attach the spdif cable from it to your sound card?
[16:43] <splashd> I would like to re-install a stock mythconverg DB. I am running the mythbuntu-repos  Mythbuntu fixes/.24 so I don't think I can just load the /usr/share/mythtv/sql/mythtv_0.23.0.sql . Any idea where the .24 is?
[16:49] <superm1> just load that one for now and it will upgrade it to 0.24 when you run myth*
[16:50] <superm1> there hasn't been one refreshed for the current schema in 0.24 yet since there hasn't been much of a use case for people doing fresh installs for 0.24 yet
[16:55] <splashd> ok. What is the difference between the  /usr/share/mythtv/sql/mythtv_0.23.0.sql and  /usr/share/mythtv/sql/mc.sql? WHich do I use or do I use both? (I guess I could just look...)
[18:37] <superm1> splashd, the former has more stuff preconfigured
[19:57] <Jonathon> I have tried both 10.04 and 10.10 installers of mythbuntu and both are not seeing my hard drive for some reason? It is visible in the shell and can be accessed and formatted etc, but the installer does not show it up. Any suggestions?
[20:15] <splashd> Jonathon, is it mounted?
[20:16] <Jonathon> splashd: no, should it be? I have tried it partitioned and not partitioned and it shows /dev/sda in the drop down list, but nothing in the partition editor part of the installer?
[20:17] <splashd> Jonathon,  no, it shouldn't just wondering if it might be mounted which could prevent the installer from gaining access
[20:17] <splashd> Jonathon, obviously there is no normaql reason it shoudn't be accessible, but you already know that
[20:18] <Jonathon> nope. It is pretty basic setup based on my existing mythtv setup which I simply removed the drives from and added this new one in for a new install
[23:35] <splashd> I'm getting a weird error and my mythbackend is erroring and shutting down
[23:35] <splashd> from my mythbackend.log: 2010-12-15 17:29:00.421 MythSocket(ffffffffb6006000:40): readStringList: Error, timed out after 30000 ms.
[23:46] <mrand> splashd: many of those are fixed on 0.24... are you running that? Here is an open ticket regarding backend deadlock on 0.24 though: http://code.mythtv.org/trac/ticket/9274