[00:07] <danialbehzadi> Hi
[00:07] <danialbehzadi> I get error every time sdk tries to initialize a bootstrap with packages, and so I can not create a kit. Is there a way to manually do this?
[00:07] <danialbehzadi> The sample error is like:
[00:07] <danialbehzadi> E: Failed to fetch http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-push/ubuntu-push-client_0.68+15.04.20160114-0ubuntu1_i386.deb Hash Sum mismatch E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
[00:07] <danialbehzadi> Command returned 100: schroot -u root -c source:click-ubuntu-sdk-15.04-i386 -- /finish.sh
[00:07] <danialbehzadi> Traceback (most recent call last): File "/usr/bin/click", line 110, in sys.exit(main()) File "/usr/bin/click", line 106, in main return mod.run(args) File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 266, in run return args.func(parser, args) File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 68, in create return chroot.create(args.keep_broken_chroot) File
[00:07] <danialbehzadi> "/usr/lib/python3/dist-packages/click/chroot.py", line 599, in create self.full_name, ret_code)) click.chroot.ClickChrootException: Failed to create chroot 'click-ubuntu-sdk-15.04-i386' (exit status 100)
[11:48] <haasn> Is there an easier way to make debian packages have the right permissions other than logging in as root and manually fixing up the directory before calling dpkg-deb?
[11:48] <haasn> Coming from the RPM world it seems a bit awkward to not be specifying the file list + their permissions in the control file
[11:48] <haasn> s/debian/ubuntu/
[12:20] <dpm> hi kalikiana, could you remind me how we manage in clicks for i18n.tr() to load translations shipped within a click, instead of looking them up in the system locations?
[12:27] <kalikiana> dpm: APP_DIR is used if set to locate the folder http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/view/head:/src/Ubuntu/Components/plugin/i18n.cpp#L116
[12:28] <dpm> kalikiana, awesome, thanks. So APP_DIR is essentially the root of the installed click, right?
[12:29] <kalikiana> dpm: Yes
[12:30] <kalikiana> APP_DIR/share/locale is where your mo files should live
[12:30] <dpm> kalikiana, I've been asked a question about handling locales in snaps, and I've had the issue myself whereby in the test calculator snap translations are not found. What sets "APP_DIR", and can I set it manually when I call a script that loads the app?
[12:31] <zsombi> nik90: http://bazaar.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/trunk/view/head:/app/components/AlarmBottomEdge.qml#L39
[12:31] <zsombi> nik90: this is bad... why is that property set there?
[12:33] <kalikiana> dpm: Probably ubuntu-app-launch, that's the one setting the XDG variables
[12:33] <dpm> ok, thanks
[12:33] <nik90> zsombi, you meant status: BottomEdgeHint.Active ?
[12:33] <zsombi> nik90: yes, the link points there :)
[12:35] <nik90> zsombi, I can't remember .. brain freeze
[12:36] <zsombi> nik90: ok... if you copied eventually from messaging or calendar, they do it wrong as well
[12:37] <nik90> why is it that bad that it caught your attention? I did grab the implementation from calendar, but made some minor changes to when we show the hint
[12:37] <nik90> we show the hint only after the alarm model has loaded on app startup
[12:37] <nik90> also we hide the hint at 3 secs
[12:39] <zsombi> nik90: rechecking the API, actually shoudl be working, but again, you should not show it, if your spec states that, revisit with design, as that is against the specs
[12:39] <zsombi> UX specs
[12:40] <nik90> Well our design specs only show ^ icon
[12:40] <nik90> and never the hint text
[12:40] <zsombi> nik90: seems tat caught us in a baaaad bug for BottomEdge
[12:41] <zsombi> the hint shoudl be shown - according to the UI specs - when you start swiping or when the mouse is plugged
[12:41] <nik90> however even if dont set hint text, I see the rectangle which holds the hint text.
[12:41] <nik90> ok
[12:41] <zsombi> you should be able to set an action to the hint, so mouse click will also work
[12:41] <zsombi> or you can then reuse the same action in the header
[12:43] <nik90> ok
[12:46] <nik90> zsombi, the purpose of the timer which shows the bottom edge hint for 3 seconds, is to notify the user that the bottom edge houses the alarm page. The bottom edge ^ icon is not noticeable at all. So the hint is shown for 3 seconds to help discoverability.
[12:46] <nik90> I will remove the offending line of code, and add a Action{} to the bottom hint as you suggested
[12:46] <zsombi> nik90: then this should be communicated to UX as this hasn't been encoded for the component and they don't deal with this at all
[12:47] <nik90> with the OTA-10 SDK Silo, I see that the ^ icon style has improved and is a bit more noticeable now.
[12:47] <zsombi> nik90: don't do that yet
[12:47] <nik90> ack.
[12:47] <zsombi> nik90: check if without the status force the bottom edge swipe is more reliable
[12:48] <zsombi> nik90: also, OTA11 will bring you preloaded bottomedge content, so you don't need to do those ugly tricks yourself anymore
[12:48] <nik90> yup I saw that branch land in staging
[12:48] <nik90> wait OTA-11?
[12:49] <nik90> can't it be squeezed into the OTA-10 Silo-50?
[12:49] <zsombi> nope
[12:49] <zsombi> nik90: that is tooooo big to touch it now
[12:49] <nik90> bummer
[12:49] <zsombi> sorry
[12:50] <nik90> np
[12:50] <zsombi> eventually we can squeeze one more landing next week then you'll have it
[12:50] <zsombi> but I doubth
[13:47] <zzarr> hello! does anyone know how I could make a kit for Qt Creator to compile for arm64/Ubuntu?
[13:50] <ogra_> i think the kits use pre-made tarballs ... bzoltan_ or zsombi might be able to tell you more
[13:50] <ogra_> (i doubt there is such a tarball for arm64 yet)
[13:54] <zzarr> thanks for the answer ogra_
[13:55] <zzarr> ogra_, do you know if a 64bit arm can run 32bit armhf binaries?
[13:55] <ogra_> if you use a 32bit rootfs it should be able to
[13:56] <zzarr> hmm.... okey
[13:58] <zzarr> I don't know if it does and I can't ssh in to my Dragonboard since it have a bug in the WiFi driver that prevents it (and all other connections from the outside)
[14:00] <ogra_> yeah, we fixed that in snappy
[14:00] <ogra_> (known bug)
[14:00] <zzarr> ogra_, yepp it's known
[14:01] <zzarr> can I fix it without installing snappy?
[14:01] <zzarr> (apply the patch)
[16:44] <popey> \o/ new docviewer in the store
[16:44] <popey> davmor2: you might want to try it on tablet :)
[16:45] <davmor2> popey: I might not :P
[16:45] <popey> Be like that!
[16:45]  * davmor2 goes off being like that :D
[16:47] <popey> That's the spirit!
[16:52] <ahayzen> timp, o/ have you been working on the new silo 050 UITK stuff? If you have, have you tried launching the music-app ?
[16:52] <timp> ahayzen: silo 50 has so many changes, everybody has been working on it
[16:53] <ahayzen> at startup, the splash is the dark colour...then it goes all to white..then as the components are loaded they are set to the correct dark colour
[16:53] <timp> ahayzen: no, not recently.
[16:53] <ahayzen> timp, it is like components assume the bg is white/light as it flickers horribly :-/
[16:53] <timp> oh, that sounds bad.
[16:53] <ahayzen> timp, do you mind launching it and just letting me know if you think we can do anything about it, or is on your side?
[16:53] <timp> we have a whole new palette there
[16:53] <timp> let me pull zsombi in, he is the palette expert
[16:54] <timp> zsombi: ^ is this something you saw before?
[16:54] <timp> I guess it is past eod for zsombi, and I am also about to leave
[16:54] <ahayzen> ah :-/
[16:55] <ahayzen> i think Victor was going to try creating a mini app with a dark bg to see if the same happens
[16:55] <timp> could be a UITK bug
[16:56] <ahayzen> yeah that is our current thought, unless we are doing something badly wrong
[16:57] <timp> I just re-installed my system with xenial, so I can configure everything in the weekend. So I don't have the dev environment and no music-app branch at hand right now...
[16:57] <timp> I think there will be a blog post about the new palette beginning of next week.
[16:57] <timp> zsombi and jamie are working on that
[16:58] <ahayzen> timp, you not got a device ;-) i don't run on the desktop atm as i'm on Wily
[16:58] <ahayzen> and cool, i'll look out for it
[16:58] <ahayzen> timp, if we can create a mini-app, we'll report a bug for sure
[16:59] <timp> yes, I have a device, but I don't find that handy for reading code ;)
[16:59] <ahayzen> :-) for testing though :-)
[16:59] <timp> I just installed xenial because I was on wily as well
[17:00] <timp> ahayzen: yes, I see the bug with silo 50
[17:00] <timp> I wonder why I didn't notice before
[17:00] <ahayzen> \o/
[17:01] <timp> on the nexus 4 it all happens quite fast though
[17:01] <ahayzen> timp, does it look like something on your side? or something on ours
[17:01] <timp> maybe that's why I didn't notice
[17:01] <ahayzen> timp, with the new PageHeader branch...like that appears before the otherstuff..with white around it
[17:02] <timp> difficult to say what it is. Can be that you do something unexpected with the theme, or it broke with updates to the palette, or the pageheader, or adaptivepagelayout (if you use that)
[17:03] <ahayzen> timp, our 'theming' hasn't changed in *ages* so we may just need to update things
[17:03] <ahayzen> and we only use PageHeader not APL yet
[17:04] <ahayzen> timp, basically we do MainView { theme.name: "Ubuntu.Components.Themes.SuruDark"; backgroundColor: "#somehex" } for the main bg
[17:05] <davmor2> popey: hmmmmmm I didn't think the zoom % was meant to show on LO docs maybe I'm mixing them up
[17:06] <timp> ahayzen: that should work.
[17:06] <timp> ahayzen: if you can reproduce it with a small test program and report the bug, that would be very helpful.
[17:06] <ahayzen> timp, OK :-) i'll try creating a mini-app after meetings...
[17:06] <ahayzen> the only problem i see with mini-app is it may be super fast at loading
[17:07] <timp> ahayzen: ok, thanks
[17:07] <timp> ahayzen: yeah, we need slower devices >;-)
[17:07] <timp> if it is drawing twice you should be able to see it I guess
[17:08] <ahayzen> yeah i guess, i'll try in a bit
[18:33] <sverzegnassi> popey, it takes too much space though... https://imgur.com/a/V2NIa
[19:29] <popey> sverzegnassi: make the font smaller :)
[19:29] <popey> sverzegnassi: nicely done though :)
[20:07] <popey> balloons: see the mail from barry on -devel about porting samba to python 3? :)
[20:08] <balloons> interesting . . .
[20:08] <balloons> It's been going on since precise cycle I swear ;-)
[20:09] <popey> yeah
[20:09] <popey> he may fix it for us :)
[20:13] <balloons> going to drop a sly note that armhf is also very important in this discussion? :-)
[20:16] <balloons> ahayzen, want to top-approve the rest of the 'add jenkins to readme' mp's? :-)
[20:17] <ahayzen> balloons, i can only do docviewer, weather, music IIRC
[20:17] <balloons> working on fixing music now. third time is the charm
[20:17] <balloons> well, approval is helpful nonetheless
[20:17] <ahayzen> :-)
[20:18] <ahayzen> docviewer, weather done
[20:21] <sverzegnassi> terminal-app done ;)
[20:23] <balloons> ahayzen, I think I give on music app, lol
[20:26] <balloons> finally, got it
[20:26] <ahayzen> haha you deleted the branch!
[20:27] <balloons> I deleted 2 branches and 2 mp's
[20:27] <balloons> the fourth branch i submitted
[20:27] <ahayzen> that's cheating ;-)
[20:27] <balloons> https://code.launchpad.net/~nskaggs/music-app/add-jenkins-info3/+merge/288171
[20:27] <ahayzen> on it
[20:27] <balloons> yea, well, it didn't go so well before doing that :-
[20:27] <ahayzen> :')