[04:28] <Dresk> Hm, I just installed sshd, and I've got no idea how it keeps getting executed (sshd -D); I kill the process and it comes right back.  It's not in init.d, and having just switched to Ubuntu, I don't know of Upstarts file structure (or a proper GUI program to manage it.)  Plus, though I'm not sure, I think some stuff is launching via init.d or systemd or something else
[04:31] <ianorlin> Dresk maybe try stopping the service with sudo service ssh stop
[04:31] <Unit193> Dresk: sudo service sshd (ssh?) stop, upstart is made so if the unit crashes, it'll restart it.  Kill it 5 times will also "fix" the problem.  You can make an override file to disable it without editing the main file.
[04:31] <Dresk> Where does Upstart keep this config?
[04:32] <Dresk> The man seems to say it references shell scripts in init.d for SysV stuff
[04:32] <Unit193> /etc/init/ssh.override  and use the 'manual' option.
[04:32] <Unit193> sysv compat is /etc/init.d/ but upstart units go in /etc/init/
[04:34] <Dresk> So, why don't I see a dnsmasq.conf in /etc/init ?  It's another service I installed and rely on
[04:36] <Dresk> Infact it's scary because I have 2 dnsmasq processes running now that I check
[04:36] <Unit193> One is because of resolvconf.
[04:36] <Unit193> And that's an init script, IIRC.
[11:06] <testdr> Unit193: about dnsmasq started in (L)Ubunut - it is started from the network-manager and the starting with its option is hardcoded into this program. I had to create a shell-wrapper for it to make it cache dns-query because its started with a cache of zero entries
[11:36] <Junka> i get a default keyring msg upon saving a network password
[11:36] <Junka> why
[11:36] <Junka> i never experinced it before with ubuntu
[11:36] <Junka> or xubuntu]
[11:36] <Junka> or even lubuntu before
[11:36] <Junka> using 14.10
[11:37] <testdr> Junka: check the program used - some use libs to store those things in the user-keyring-manager (?seahorse)
[11:38] <Junka> lubuntu has no seahorse by default
[11:38] <Junka> it has gnome-keyring though
[11:38] <Junka> shouldn't it be unlocked upon login?
[11:39] <testdr> Junka: should? should not? - can only speak for Lubuntu-14.04 and there it is not un-locked on login (you may call it a bug)
[11:41] <Junka> :(
[11:42] <testdr> Junka: as far i know - the development for the windowmanager in lubuntu may go to more qt-based libs and then gnome-based things are always a bit overseen
[11:44] <Junka> hmm
[11:45] <Junka> LXsession configuration has for security (keyring): ssh-agent
[11:45] <Junka> should i switch it to gnome-keyring?
[11:49] <Junka> gtg
[16:14] <SuperLag> Anyone have the torrent for 14.10 i386?
[16:14] <SuperLag> the link on cdimages.ubuntu.com doesn't work
[16:23] <holstein> SuperLag: the one from http://cdimage.ubuntu.com/lubuntu/releases/14.10/release/ "doesnt work" ?
[16:23] <holstein> what happens?
[16:24] <SuperLag> http://paste.ubuntu.com/9821463/
[16:26] <holstein> SuperLag: got it here, no problem
[16:26] <holstein> SuperLag: try just clicking on it in a browser
[16:30] <SuperLag> tried that already
[16:30] <SuperLag> it doens't work
[16:30] <holstein> SuperLag: tried what?
[16:30] <SuperLag> 08:26 < holstein> SuperLag: try just clicking on it in a browser
[16:30] <holstein> SuperLag: you tried to click on it? when i click on it, it comes in, no problem.. would you like me to email it to you?
[16:30] <holstein> SuperLag: i have it right here..
[16:31] <holstein> http://cdimage.ubuntu.com/lubuntu/releases/14.10/release/lubuntu-14.10-desktop-i386.iso.torrent is the one i grabbed..
[16:33] <holstein> SuperLag: here is from my dropbox https://www.dropbox.com/s/yesqjwliapcodns/lubuntu-14.10-desktop-i386.iso.torrent?dl=0
[16:33] <holstein> i suggest, when doing that, you confirm the md5 from the original site
[16:34] <SuperLag> https://www.dropbox.com/s/tfon2pjnjun9ik6/broken_torrent_link.png?dl=0
[16:35] <holstein> SuperLag: https://www.dropbox.com/s/yesqjwliapcodns/lubuntu-14.10-desktop-i386.iso.torrent?dl=0 is where i go
[16:35] <holstein> SuperLag: i open it in an incognito browser window, i click the "download" button, and i get another one of the torrents downloaded that you are trying to get
[16:37] <SuperLag> Okay. I understand it works for you. Thank you for the torrent.
[16:37] <SuperLag> but that doesn't address the fact that it's not working from here
[16:38] <SuperLag> I've tried this from two different machines, on two different networks. Same results.
[16:38] <holstein> https://dl.dropboxusercontent.com/u/1172535/temp/lubuntu-14.10-desktop-i386.iso.torrent
[16:38] <holstein> SuperLag: i cant seem to get it to fail..
[16:40] <holstein> you can try your wget there.. wget https://dl.dropboxusercontent.com/u/1172535/temp/lubuntu-14.10-desktop-i386.iso.torrent
[16:42] <SuperLag> that link works fine
[16:42] <SuperLag> it's the mirror links that fail
[16:42] <holstein> SuperLag: no.. *thats* where i got that file, friend
[16:42] <SuperLag> and that's exactly my point
[16:42] <holstein> SuperLag: if you have what you need, check the md5, and confirm its correct.. and enjoy
[20:35] <SonikkuAmerica> What's the blueprint for LXQt now?
[21:20] <slaveworx> hi guys!
[21:21] <slaveworx> I've made a script for Lubuntu that easily creates shortcuts
[21:21] <slaveworx> it is written in python
[21:21] <slaveworx> where should I upload it in order to make it useful for people?
[21:48] <testdr> slaveworx: you can upload it to the pastebin http://paste.ubuntu.com and poste the link to it here and in the ubuntu-forum
[21:55] <slaveworx> http://paste.ubuntu.com/9825409/
[21:59] <slaveworx> I hope that this script can help begginers


[03:23] <Unit193> Jordan_U: Yep, just hit ##windows too.  kbanned there also.
[03:24] <tachibana> um yes, i was just banned
[03:24] <tachibana> for being offtopic
[03:25] <Jordan_U> tachibana: That was one of the reasons, yes.
[03:25] <tachibana> i presume it's because someone thought they were being trolled
[03:25] <tachibana> D:
[03:26] <tachibana> they called unfriendly towards families
[03:26] <tachibana> i am very hurt and feel i should seek legal reparations for my resulting pyschological trauma
[03:26] <tachibana> called me*
[03:27] <tachibana> they were very elitist, and swift to getting angry and flustered
[03:27] <tachibana> very power hungry, very trigger happy with the ban button
[03:27] <tachibana> i would like to file a formal complaint
[03:28] <tachibana> who is the manager here
[03:28] <Jordan_U> !appeal | tachibana
[03:28] <tachibana> hows this for an appeal process
[03:29] <k1l_> tachibana: dont waste volunteers time. if you just want to troll this is not the right place.
[03:29] <tachibana> u mad?
[03:29] <tachibana> 1v1 me fgt
[03:30] <k1l_> if you carry on with that sort of "funny speak" and attitude one must asume you are just trolling
[03:30] <tachibana> zzzzzzzz
[03:31] <tachibana> i bet you cant even swap out a motherboard on your own computer


[00:05] <log123> ARM
[00:05] <roxfan> LEG
[01:25] <log123> FOOT
[01:25] <log123> flanges :O
[01:26] <log123> *filangies*
[06:45] <jordan> Hey guys, what's the status of Ubuntu arm? Are there certain ARM platforms that will 'just work', or is it all still in development
[06:45] <jordan> ?
[08:39] <savuporo> hi, anyone know how to get at kernel command line on lange51 ? whats the magic for fconfig -d /dev/sda1 ?
[17:11] <john85> anyone please help me to install ubuntu to sd card
[17:12] <john85> anybody there???


[04:51] <pitti> Good morning
[07:21] <dholbach> good morning
[10:25] <mlankhorst> morning
[13:33] <manuel___> hi
[13:42] <manuel___> HI, How can I start with the development from Ubuntu?
[13:44] <diwic> manuel___, hi, more specifically, what do you want to do?
[13:46] <manuel___> I have no plan, about the development from Ubuntu. So, I look then. What is a good get to in?
[13:49] <diwic> manuel___, do you mean you want to help developing Ubuntu itself, or developing your own software that runs on Ubuntu?
[13:49] <manuel___> Sorry, my last sentence is bad. "What is a good get to in?" should be called "So, what is a good way to get in?"
[13:49] <manuel___> sorry for my bad english
[13:49] <manuel___> first point
[13:50] <diwic> manuel___, no worries about the English, we have many nationalities here - you'll learn gradually just like the rest of us
[13:50] <diwic> manuel___, so are you interested in coding, testing, writing documentation, advocating Ubuntu, etc...?
[13:50] <diwic> manuel___, there are many things you can help out with
[13:52] <manuel___> I am much interested as programming treiber, but that is to high for me now. Right? So, what are other ways.
[13:52] <manuel___> ?
[13:53] <manuel___> sorry treiber is german for driver. so I mean driver
[13:53] <diwic> manuel___, then maybe contacting the German LoCo team could be a good start?
[13:54] <diwic> manuel___, http://loco.ubuntu.com/teams/ubuntu-de-locoteam/ - they seem to have interesting activities in German
[13:56] <diwic> manuel___, or, if you're interesting in programming drivers (I assume drivers for hardware?), start with a driver that needs testing or fixing and try to contact people that are already working on that driver
[13:58] <manuel___> that heard it better.
[13:58] <diwic> manuel___, often driver developers don't have all hardware themselves, and need people that can test their new drivers. That could be a way to get involved.
[13:58] <manuel___> Is there a tutorial to learn the basics of driver programming.
[14:00] <diwic> manuel___, it depends on how much you can code already, but http://lwn.net/Kernel/LDD3/ can be a good start
[14:01] <manuel___> thanks
[14:01] <manuel___> And bye. I log me now out.
[14:12] <ogra_> oh !
[14:12] <ogra_> mail to the ubuntu-backports list ...
[14:12] <ogra_> that only happens once a decade !
[14:16] <Laney> I don't think anyone other than me ever mails that list :(
[14:17] <mlankhorst> must find doko..
[14:19] <ogra_> Laney, well, i read it at least ... :)
[14:36] <pitti> hey stgraber, how are you?
[14:36] <pitti> stgraber: do you still plan a new LXC upstream version for utopic, or might it be better at this point to cherry-pick the systemd unit fixes, or do you want to postpone them to V altogether?
[14:37] <pitti> (I'm happy to provide an updated package, but don't want to step on your toes)
[14:38] <stgraber> pitti: so my current plan is (but we'll see if the release team agrees) to finish the systemd changes upstream this week (still resolving some problems), release alpha-2 ideally by EOW and then get that into utopic
[14:38] <stgraber> I also have 1.0.6 that's around the corner and aimed at trusty
[14:38] <pitti> stgraber: ah, great, thanks; please tell me if/when you need assistance with the dh_systemd_* bits
[15:56] <ScottK> If there's a u-d-a ML moderator around, I just put one in queue for review.
[17:51] <mdeslaur> cjwatson: FYI, I'm stealing your nginx merge
[19:28] <Logan_> hallyn: would you mind prepping/uploading the SRU for vde2 (including the fixes for Bug 804647, Bug 629349, and Bug 781411)? I'm kinda tied up with stuff at the moment
[19:28] <hallyn> Logan_: ok, will do
[19:29] <Logan_> er, second one should've been Bug 629439
[19:29] <Logan_> ideally a new version should be uploaded to lucid
[19:29] <Logan_> and then it can be copied up to precise
[19:42] <hallyn> Logan_: oh feh.
[19:42] <hallyn> i was only looking at one bug.  missed the multiple bugs you quoted
[19:43] <hallyn> arges: are you around?  could you quickly reject the two vde2 packages i uploaded (to lucid-proposed and precise-proposed)
[19:43] <hallyn> i got ahead of myself
[19:43] <arges> hallyn: hey
[19:43] <arges> sure
[19:43] <hallyn> thx!
[19:43] <Logan_> heh
[19:44] <arges> hallyn: ok done
[19:45] <hallyn> Logan_: though, for https://bugs.launchpad.net/ubuntu/+source/vde2/+bug/781411  i never ws able to reproduce it.  so can't really write a sru justification.  i'd vote for calling it invalid
[19:45] <Logan_> incomplete, at least
[20:04] <Noskcaj> ScottK, Can you look at my last comment on 1372224
[20:04] <Noskcaj> * bug 1372224
[20:05] <ScottK> Commented
[20:10] <Noskcaj> ScottK, So are you going to sync it?
[20:10] <ScottK> No.  Please subscribe sponsors.
[20:10] <ScottK> Busy with $work.
[20:14] <Noskcaj> ok


[04:05] <cjwatson> mcphail: snapcraft's README.md refers to the Launchpad one
[05:06] <mborzecki> morning
[05:34] <mborzecki> mvo: hey, how are things?
[05:45] <zyga> Good morning
[05:45] <mborzecki> zyga: hey
[05:46] <mborzecki> zyga: i see we made it to 2.32.6
[05:50] <mvo> hey zyga and mborzecki !
[05:50] <mborzecki> mvo: morning
[05:51] <mborzecki> mvo: how was the sprint?
[05:52]  * zyga -> walk
[05:52] <mvo> mborzecki: it was good
[05:52] <mvo> mborzecki: no surprises, focus for the next couple of weeks is making core18 bootable and working on the upgrade path
[05:52] <mborzecki> mvo: any updates to the roadmap then?
[05:52] <mvo> mborzecki: but we knew that :)
[05:53] <mvo> mborzecki: nothing new in the roadmap I think
[05:54] <mvo> mborzecki: we will need to do a .7 to fix an important usecase (two PRs up for that already)
[05:54] <mvo> mborzecki: and then we are hopefully fully back to 2.33
[05:54] <zyga> Oh
[05:54] <zyga> What is for .7?
[05:54] <mborzecki> hm and i thought we were done with .6 :)
[05:54] <mvo> zyga: a systemd target for when the system is fully seeded
[05:54] <mvo> zyga: and a way for snaps to declare an "after: snapd.seeded"
[05:55] <mvo> zyga: it is important for some 18.04 cloud image use-cases
[05:55] <mvo> mborzecki: I thought so too :) but then reality disagreeded
[05:55] <mvo> I think its pretty straightforward, it will need a design ACK from gustavo though
[05:56] <zyga> I See
[05:57] <mborzecki> mvo: a target taget? as in snapd.seeded.target?
[05:57] <mvo> mborzecki: correct
[05:57] <mvo> mborzecki: so that a unit can say "after=snapd.seeded.service"
[05:59] <mvo> mborzecki: there is a PR up for this (5124) but it was written during the sprint so an extra careful review is needed :)
[05:59] <mvo> the other one is 5132 and we will need 5133 for cosmic
[06:09] <mup> PR snapd#5136 opened: tests: ubuntu 18.04 or higher does not need linux-image-extra- <Created by mvo5> <https://github.com/snapcore/snapd/pull/5136>
[06:26] <mup> PR snapd#5128 closed: Revert "Skip test lp-1721518 for arch, snapd is failing to start afte… <Simple> <Created by sergiocazzolato> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5128>
[06:29] <mup> PR snapd#5121 closed: interfaces:minor autoconnect cleanup <Simple> <Created by stolowski> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5121>
[06:36] <mup> PR snapd#5069 closed: configcore: validate experimental.layouts option <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5069>
[06:44]  * zyga is back home and working now
[06:44] <zyga> my whole desk was covered with yellow powder
[06:45] <zyga> something must be blooming nearby
[06:45] <zyga> yuck
[06:48]  * zyga catches up with email
[06:49] <zyga> mvo: please ping me if something urgent is needed, I will start hacking at around noon, I need to get my inbox under control
[06:54] <mvo> zyga: I will focus on .7 this morning and trying to make sure autopkgtests and spread is happy
[06:55] <mvo> zyga: 5131 needs a second review but its pretty trivial and can probably go in with a single review even
[06:55] <mvo> zyga: I got this error in one of my PRs so it might be a prereq for landing the 2.32 ones
[06:58] <zyga> mvo: FYI, I think there's a real error that affects debian
[06:58] <zyga> mvo: but it's rare
[06:58] <zyga> mvo: if you see a network-bind or network test fail there, that's it
[06:58] <zyga> it looks like we become unconfined in some situations
[06:59] <mup> PR snapd#5136 closed: tests: ubuntu 18.04 or higher does not need linux-image-extra- <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5136>
[07:00] <zyga> mvo: btw, do you know what is cosmic?
[07:00] <zyga> cosmic ... c-what?
[07:00] <mvo> zyga: I don't
[07:00] <mborzecki> zyga: canimal?
[07:00] <mvo> zyga: cockroach maybe
[07:01] <zyga> mborzecki: no :)
[07:01] <mvo> or maybe canibal
[07:01] <mborzecki> haha
[07:01] <mborzecki> canibal cockroach
[07:01] <mborzecki> sounds like a great name for a death metal band ;)
[07:02] <mvo> lol
[07:02] <zyga> cosmic cosmonaut would be nice
[07:02] <zyga> humans are animals too
[07:02] <mvo> I like cosmonaut!
[07:04] <pstolowski> mornings!
[07:04] <mvo> hey pstolowski good morning and welcome back
[07:04] <pstolowski> how was the sprint?
[07:05] <mborzecki> pstolowski: morning
[07:05] <zyga> good morning pawel
[07:05] <mvo> pstolowski: good, no surprises, roadmap is pretty much what we discussed already
[07:12] <mborzecki> arch package bumped to 2.32.6
[07:13] <mborzecki> and wow, we have quite a lot of open PRs
[07:14] <mup> PR snapd#5135 closed: Docs moved to forum <Created by abitrolly> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5135>
[07:15] <mborzecki> need coffee
[07:15] <mup> PR snapd#5133 closed: spread.yaml: add cosmic (18.10) to autopkgtest/qemu <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5133>
[07:28] <mborzecki> zyga: regarding #1769203, haven't we looked at auto mounting snaps via .automount unit files?
[07:28] <mup> Bug #1769203: every revision of snaps are mounted <amd64> <apport-bug> <bionic> <wayland-session> <snapd (Ubuntu):Invalid> <https://launchpad.net/bugs/1769203>
[07:29] <zyga> mborzecki: I mentioned this and I think gustavo was sceptical about it
[07:33] <mborzecki> zyga: do you recall what was his reasoning?
[07:37] <mvo> mborzecki: we did use automount a long time ago, it may even be in the git history (a looooong time ago, very early days of the project)
[07:37] <zyga> mborzecki: that it is not fully transparent
[07:37] <zyga> mborzecki: you can observe automount points
[07:37] <zyga> mborzecki: you can unmount them to break them
[07:38] <mvo> zyga: hm, unmount them to break them is also true for .mount services, no?
[07:40] <mup> PR snapd#5131 closed: tests: fix interfaces-network test for systems with partial confinement <Created by sergiocazzolato> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5131>
[08:06] <zyga> mvo: are we pushing .6 to stable
[08:25] <pstolowski> zyga: is there any concern still about https://github.com/snapcore/snapd/pull/5075 ?
[08:25] <mup> PR #5075: snap/env: fix env duplication logic <Simple> <Created by didrocks> <https://github.com/snapcore/snapd/pull/5075>
[08:30] <mvo> zyga: yes, today when cachio is around (probably after the standup
[08:30] <zyga> mvo: brilliant
[08:32] <mvo> zyga: is there any work to make 2.32 tested again that I can build upon? or just go over the master PRs and cherry-pick the right stuff?
[08:35] <mvo> btw, a review for 5132 would be great. it need a final +1 from niemeyer to ensure he is happy with the language but beside that it should be ready for review
[08:42] <zyga> doing
[08:43] <mvo> ta
[08:52] <zyga> mvo: done
[08:56] <mvo> ta
[09:06] <mup> PR snapd#5137 opened: tests: cherry-pick commits to move spread to google backend <Created by mvo5> <https://github.com/snapcore/snapd/pull/5137>
[09:14] <zyga> hmmmmm
[09:14] <zyga> mvo: I have a debian 10 vm with two snaps but no core
[09:14]  * zyga wonders how that happened
[09:15] <zyga> snap changes from debian 10 https://www.irccloud.com/pastebin/oU28h1jS/
[09:15]  * mvo hugs mborzecki and zyga for the excellent review in 5131
[09:16] <mvo> zyga: strange, what version of snapd is running?
[09:22] <zyga> 2.30
[09:23] <zyga> 3.30-5+b1
[09:38] <zyga> mwhudson: hey
[09:38] <zyga> mwhudson: not super urgent but it would be good to update snapd in debian to 2.32.6 or .7
[09:39] <zyga> mwhudson: also (as before) not sure how to maintain this package
[09:40] <zyga> mwhudson: what is the process for doing a new release? merge upstream and massage?
[09:43] <mvo> we should also check if re-exec is enabled
[09:44] <mvo> yay, cosmic autopkgtest for ppc64/s390x is green
[09:55] <zyga> mborzecki: are you running arch or ubuntu now
[09:55] <zyga> mborzecki: I may need your help
[09:55] <mborzecki> arch
[09:56] <mborzecki> zyga: what do you need help with?
[09:56] <mup> Bug #1593141 changed: Each run of a snap app leak directories in /tmp <snapd:Fix Released> <https://launchpad.net/bugs/1593141>
[09:57] <zyga> mborzecki: there's a bug, I cannot find it now
[09:57] <zyga> maybe on the forum, maybe on laucnhpad
[09:57] <zyga> it relates to this call
[09:57] <mup> PR snapd#5137 closed: tests: cherry-pick commits to move spread to google backend <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5137>
[09:58] <zyga> https://www.irccloud.com/pastebin/Wygky688/
[09:58] <zyga> someone got a denial on that
[09:58] <zyga> I wonder if the "none" is significant
[09:58] <zyga> can you see if you got that denial?
[09:58]  * zyga boots 18.04 live usb to test something else
[10:00] <zyga> wow, I didn't know there are so many snaps on the live ISO
[10:00] <mborzecki> zyga: ok, let me sync some stuff first
[10:01] <zyga> mborzecki: thanks
[10:01] <zyga> snap list truncates "tracking" too much
[10:03] <mup> PR snapd#5129 closed: cmd/snap-confine: allow any base snap to provide /etc/alternatives <Simple> <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5129>
[10:03] <zyga> mvo: thank you
[10:03] <zyga> mvo: I was working on a new base snap last weekend
[10:03] <zyga> mvo: I ran into a serious bug, I didn't manage to debug it yet though
[10:04] <mvo> zyga: oh? ok - anything you can share?
[10:04] <mvo> zyga: what was the error etc?
[10:04] <zyga> mvo: snaps based on that snap didn't start at all, something wrong in the deep guts of snap-confine
[10:04] <zyga> I didn't get to the bottom of it, I can share later today if you want to play
[10:07] <zyga> some issues from the live ISO
[10:08] <zyga> failed refresh on live iso https://www.irccloud.com/pastebin/bLhbMBWf/
[10:08] <zyga> failed mount on live iso (curious) https://www.irccloud.com/pastebin/h2R6g2mI/
[10:09] <pedronis> afaik refreshes are not working on the live image, that's why they asked us how to turn them off
[10:09] <zyga> ureadahead is creazy on the live iso, spamming with errors
[10:09] <zyga> pedronis: they work on 2nd try
[10:10] <pedronis> what I mean, afaik they are not expected to work
[10:10] <zyga> I see
[10:11] <pedronis> I don't know the details, but they didn't ask to help fix them, but how to turn off auto-refreshes
[10:11] <pedronis> I think there's a basic space problem as well
[10:15] <mup> Bug #1443612 changed: please set /run/shm/snaps/@{APP_PKGNAME}/@{APP_VERSION}/ for apps <Snappy:Won't Fix> <https://launchpad.net/bugs/1443612>
[10:18] <mup> Bug #1650389 changed: Installing snapd on 14.04.5 desktop downgrades xorg et al. <14.04> <Snappy:Invalid> <systemd (Ubuntu):Fix Committed by thomas-voss> <systemd (Ubuntu Trusty):Fix Committed by thomas-voss> <https://launchpad.net/bugs/1650389>
[10:21] <mup> Bug #1659924 changed: Snap failures in 16.04 <Snappy:Fix Released> <https://launchpad.net/bugs/1659924>
[10:30] <mborzecki> mvo: damn, that template is tricky
[10:30] <mup> Bug #1458866 changed: hangs in uboot boot prompt if dtbs dir is missing <Snappy:Won't Fix> <https://launchpad.net/bugs/1458866>
[10:33] <mcphail> cjwatson: thanks. that's the one i've used
[10:33] <mup> Bug #1464396 changed: "sudo: unable to resolve host ..." when custom hostname is used. <Snappy:Won't Fix> <https://launchpad.net/bugs/1464396>
[10:36] <mup> Bug #1471868 changed: automatic reboot fails with non executable empty systemd <snappy-robustness> <Snappy:Won't Fix> <https://launchpad.net/bugs/1471868>
[10:36] <mup> Bug #1473465 changed: kvm/generic-amd64: system got in a broken state in the second boot <Snappy:Won't Fix> <Snappy 15.04:Won't Fix> <Snappy trunk:Won't Fix> <https://launchpad.net/bugs/1473465>
[10:36] <mup> Bug #1650671 changed: Content sharing from snap common is broken <Snappy:Fix Released by zyga> <https://launchpad.net/bugs/1650671>
[10:39] <mborzecki> pedronis: can you take a look at https://github.com/snapcore/snapd/pull/4844#issuecomment-384969859 ?
[10:39] <mup> PR #4844: overlord/snapstate: allow core defaults configuration via 'system' key <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4844>
[10:39] <mup> Bug #1641132 changed: no way to include devmode snaps in snap prepare-image? <personal> <Snappy:Won't Fix by mvo> <Ubuntu Image:Expired> <https://launchpad.net/bugs/1641132>
[10:39] <mup> Bug #1666074 changed: Can't update "snapweb' snap <snapweb:Fix Released by abreu-alexandre> <https://launchpad.net/bugs/1666074>
[10:39] <mup> Bug #1752031 changed: core `service.ssh.disable` key not taken into account <Snappy:Fix Released> <https://launchpad.net/bugs/1752031>
[10:41] <mborzecki-ubuntu> zyga: any particular revision you'd want to me check?
[10:42] <mup> Bug #1467553 changed: automatic reboot fails with zero size kernel, no watchdog in grub <snappy-robustness> <snapd:Triaged> <https://launchpad.net/bugs/1467553>
[10:42] <mup> Bug #1588192 changed: GL interfaces seem wedged for Krita on nvidia <patch> <Snappy:Fix Released> <nvidia-graphics-drivers-304 (Ubuntu):In Progress by albertomilone> <nvidia-graphics-drivers-340 (Ubuntu):Won't Fix by albertomilone> <nvidia-graphics-drivers-361 (Ubuntu):Won't Fix by albertomilone>
[10:42] <mup> <nvidia-graphics-drivers-304 (Ubuntu Xenial):In Progress by albertomilone> <nvidia-graphics-drivers-340 (Ubuntu Xenial):Won't Fix by albertomilone> <nvidia-graphics-drivers-361 (Ubuntu Xenial):Won't Fix by albertomilone> <https://launchpad.net/bugs/1588192>
[10:45] <mup> Bug #1484898 changed: device tarball needs to allow setting sysctl defaults <Snappy:Won't Fix> <https://launchpad.net/bugs/1484898>
[10:46] <mborzecki> mvo: https://play.golang.org/p/QERhAshfyMC
[10:46] <mborzecki> best i could come up with
[10:46] <zyga> mborzecki-ubuntu: nope
[10:46] <zyga> mborzecki-ubuntu: just anything
[10:46] <zyga> mborzecki-ubuntu: maybe try latest stable + krita
[10:48] <mborzecki-ubuntu> zyga: stable is 2.32.5+18.04 (distro package)
[10:48] <mup> Bug #1507693 changed: please add gdb, strace, ltrace, etc to snappy-debug <Snappy:Invalid> <https://launchpad.net/bugs/1507693>
[10:48] <mup> Bug #1668738 changed: core snap with configure hook fails for some people <Snappy:Fix Released> <https://launchpad.net/bugs/1668738>
[10:51] <zyga> ogra_: do you know if this is still an issue in practice? https://bugs.launchpad.net/snappy/+bug/1496141
[10:51] <mup> Bug #1496141: /etc/adduser.conf should default to use extra_users <Snappy:Confirmed for ogra> <https://launchpad.net/bugs/1496141>
[10:51] <mup> Bug #1474463 changed: a networking service snap like xkcd doesn't wait for the server to be listening <Snappy:Won't Fix> <https://launchpad.net/bugs/1474463>
[10:53] <ogra_> zyga, well, the tools we use all use the --extrausers option ... switching that default would allow to avoid this
[10:53] <mwhudson> zyga: yes it would, wouldn't it
[10:53] <ogra_> so nothing has changed but if you want to close it ...
[10:53] <mwhudson> zyga: yes, merge + massage i think, we need to move it salsa too...
[10:53] <zyga> mwhudson: I'm sooo out of date on this process
[10:53] <mwhudson> zyga: i think there are some new deps that need to be packaged?
[10:53] <zyga> mwhudson: I can merge and push my tree somewhere after some basic massaging
[10:53] <zyga> mwhudson: I bet
[10:54] <mwhudson> zyga: go for it!
[10:55] <mup> Bug #1543764 changed: snappy classic must use officially supported lxd images from simplestream; not unsupported ones from linux-containers.org <Snappy:Invalid by mvo> <https://launchpad.net/bugs/1543764>
[10:55] <mvo> mborzecki thank you!
[10:55] <mwhudson> zyga: it's probably easier for me to do the new packages as a DD i guess
[10:56] <zyga> mwhudson: yeah, for sure
[10:56] <zyga> mwhudson: I'll merge and see what comes out, I'm very out of touch with that aspect, I'll send you a mail with the updates (or forum thread)
[10:56] <mwhudson> zyga: +1
[10:56] <mborzecki-ubuntu> zyga: i don't see any denials
[10:56]  * mwhudson makes a thing in a trello
[10:57] <mwhudson> need to zzz now
[10:57] <zyga> o/
[10:57] <zyga> mvo: who maintains the classic snap
[10:57] <zyga> mvo: and what should it do since we now have 18 looming
[10:57] <ogra_> zyga, mvo and me ... kind of
[10:57] <zyga> should it be magic smart and follow the booted base?
[10:57] <zyga> or ... what?
[10:57] <ogra_> we should have a classic-18 snap i guess
[10:58] <mup> Bug #1551747 changed: ubuntu-fan causes issues during network configuration <verification-done> <cloud-init:Invalid> <Snappy:Invalid> <ubuntu-fan (Ubuntu):Fix
[10:58] <mup> Released by apw> <ubuntu-fan (Ubuntu Xenial):Fix Released by apw> <ubuntu-fan (Ubuntu Yakkety):Fix Released by apw> <https://launchpad.net/bugs/1551747>
[10:58] <zyga> ogra_: but you cannot install arbitrary classic on arbitrary system, can you?
[10:58] <ogra_> if it is suppsed do that magically we'd have to ship both chroots
[10:58] <ogra_> (and have it pik the right one at runtime)
[10:59] <ogra_> s/ship both/ship support for both/
[10:59] <ogra_> i suspect 18 looks a litte different to 16 :)
[11:04] <mborzecki-ubuntu> zyga: tried with "none" and NULL, no denials in either case
[11:11] <zyga> Thanks
[11:14] <zyga> hm, snapcraft still doesn't support license?
[11:14] <zyga> kalikiana: is this fixed or am I using it wrongly?
[11:16] <zyga> popey: offtopic
[11:16] <zyga> popey: I have https://github.com/snaphub
[11:16] <zyga> feels like something you should have instead
[11:22] <mup> PR core#87 closed: snapcraft.yaml: update stage-packages during build <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/core/pull/87>
[11:24] <mvo> I updated 5132 based on the excellent feedback I got
[11:27] <zyga> looking
[11:29] <popey> zyga: looks empty?
[11:30] <popey> What is it (intended to be)?
[11:35] <zyga> I think it is very old
[11:35] <zyga> popey: it was supposed to be a place for snaps under shared maintenance
[11:35] <zyga> like snapcrafters today
[11:38] <Son_Goku> mvo, I'm looking forward to seeing a dnf plugin for snapd from you :P
[11:38] <pedronis> mborzecki: I'm not sure merging them would be useful, I would suspect people putting a copy or more stuff under system
[11:40] <mborzecki> pedronis: hm sounds fair, very well, i'll push a change replacing error with the log
[11:46] <popey> Zyga feel free to delete if it's not used
[11:48] <zyga> popey: ack
[11:57] <pedronis> mvo: zyga: any PR I should prioritize vs starting to look at the full queue?
[11:58] <zyga> pedronis: maybe pass through all simple first
[11:58] <zyga> to allow them to land
[11:58] <zyga> mborzecki, mvo: I will fix master as arch moved to a more restrictive compiler now
[12:01] <mup> PR snapd#5138 opened: cmd/libsnap: fix compile error on more restrictive gcc <Critical> <Simple> <Created by zyga> <https://github.com/snapcore/snapd/pull/5138>
[12:01] <zyga> https://github.com/snapcore/snapd/pull/5138
[12:01] <mup> PR #5138: cmd/libsnap: fix compile error on more restrictive gcc <Critical> <Simple> <Created by zyga> <https://github.com/snapcore/snapd/pull/5138>
[12:01]  * zyga -> walk dog
[12:08] <cachio_> mborzecki, hey, build fail on arch
[12:08] <cachio_>  failing
[12:08] <cachio_> here https://api.travis-ci.org/v3/job/375775038/log.txt
[12:08] <mborzecki> cachio_: yes, zyga is working on it
[12:08] <cachio_> mborzecki, great, thanks
[12:08] <mborzecki> i've updated to gcc 8.1 just now :)
[12:09] <zyga> Fixed above :-)
[12:09] <mborzecki> off to pick up my daughter
[12:09] <mborzecki> pedronis: pushed an update to #4844
[12:09] <mup> PR #4844: overlord/snapstate: allow core defaults configuration via 'system' key <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4844>
[12:12] <mup> PR snapd#5130 closed: interfaces/apparmor: allow bash and dash to be in /usr/bin/ <Simple> <Created by zyga> <Merged by jdstrand> <https://github.com/snapcore/snapd/pull/5130>
[12:20] <Son_Goku> zyga, you waited until Arch had it too until you'd fix the problem I've had in Fedora 28 since February?
[12:20] <Son_Goku> I'm hurt :(
[12:20] <zyga> That is the problem?
[12:21] <zyga> It broke master :/)
[12:21] <Son_Goku> yes
[12:21] <zyga> Hey jdstrand
[12:21] <Son_Goku> you promised me you'd fix it back then, and you didn't :(
[12:22] <Son_Goku> and you guys keep disabling the Fedora CI instead of fixing it, so I have nothing left to make you guys notice these things
[12:23] <zyga> Hmmm? We only disabled it when golang was broken
[12:23] <Son_Goku> zyga, I've been forced to modify the autofoo to drop -Werror since February so that snapd releases would even build
[12:24] <zyga> I lost track of that
[12:24] <Son_Goku> :'(
[12:24] <zyga> We should have f28 in CI
[12:24] <Son_Goku> you should have Rawhide in CI too
[12:24] <Son_Goku> I distinctly remember help setting that up at the last sprint
[12:31] <mvo> Son_Goku: heh, will look into that once the fires are out
[12:32] <mvo> pedronis: the 2.32 ones would be great
[12:32] <mvo> yay, cosmic autopkgtests are all green now
[12:32] <zyga> Son_Goku: so to recap (I was afk)
[12:32] <zyga> Son_Goku: it would be great if we had the error in CI so that it gets fixed instantly and not forgotten
[12:33] <zyga> Son_Goku: I'll ask if we can move to F28 testing
[12:33] <mvo> zyga: aha, the arch failure(s) I see right now are known and you take care of them
[12:33] <mvo> ?
[12:33] <zyga> mvo: correct
[12:33] <zyga> Son_Goku: I encourage you to nag us more if there's a known issue
[12:33] <Son_Goku> I gave up after three weeks
[12:33] <mvo> zyga: ta, approved
[12:34] <Son_Goku> that's why I keep doing this: https://src.fedoraproject.org/rpms/snapd/blob/master/f/snapd-2.32.4-Drop-Werror.patch
[12:34] <Son_Goku> that started in 2.31.1
[12:34] <zyga> Son_Goku: also the patch is pretty trivial, we could have merged it long ago
[12:34] <zyga> sorry for dropping it
[12:34] <Son_Goku> yes, but you didn't want to
[12:34] <Son_Goku> you said you'd rather fix the bugs
[12:35] <zyga> I mean the patch for fixing this, not dropping -Werror
[12:35] <zyga> cachio_: do we have a f28 image?
[12:35] <Son_Goku> and of course, I keep this little bugger alive: https://src.fedoraproject.org/rpms/snapd/blob/master/f/0001-cmd-use-libtool-for-the-internal-library.patch :)
[12:35] <zyga> I would swap f26 for f28 (26 is about to EOL)
[12:37] <zyga> mvo: where shall we track bugs for classic snap?
[12:37] <mvo> zyga: hm, gut-feeling is lp:snapd
[12:37] <zyga> ah, I'm blind
[12:37] <zyga> https://launchpad.net/classic-snap
[12:37] <mvo> zyga: aha, even better
[12:38] <thresh> kyrofa, oh wow, many thanks for the investigation which led to https://github.com/snapcore/snapcraft/pull/2119
[12:38] <mup> PR snapcraft#2119: repo: automatically prune unneeded stage-packages <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/2119>
[12:38] <thresh> kyrofa, \o/
[12:38] <zyga> mvo: we should probably rename the project a little
[12:38] <zyga> is this "classic dimension"
[12:38] <zyga> (reword)
[12:39] <zyga> what is the proper name for that?
[12:40] <zyga> hmm, github imports are failing
[12:40] <zyga> https://code.launchpad.net/~snappy-dev/classic-snap/master
[12:41] <zyga> and have failed since 2017
[12:41] <zyga> ouch
[12:41] <mup> Bug #1653648 changed: classic does not properly unmount /dev/pts on exist <Classic dimension for snappy:New for ogra> <https://launchpad.net/bugs/1653648>
[12:41] <ogra_> that has been fixed ages ago
[12:41] <zyga> retried now
[12:42] <ogra_> (the bug i mean, havent looked at your import above)
[12:45] <zyga> ogra_: can you triage https://bugs.launchpad.net/classic-snap/+bug/1653648 please
[12:45] <mup> Bug #1653648: classic does not properly unmount /dev/pts on exist <Classic dimension for snappy:Fix Released by ogra> <https://launchpad.net/bugs/1653648>
[12:46] <ogra_> zyga, i obviously did 5min ago
[12:46] <zyga> cjwatson: hey, would you mind helping me understand why this git import is failing https://code.launchpad.net/~snappy-dev/classic-snap/master
[12:46] <ogra_> zyga, laos https://github.com/snapcore/classic-snap/commit/4ec9dec90c555c4c26995ca83b23a48cd61d6743
[12:46] <ogra_> err
[12:46] <ogra_> zyga, also https://code.launchpad.net/%7Esnappy-dev/classic-snap/+git/classic-snap/+ref/master
[12:47] <ogra_> (sorry bad paste in the first one=
[12:47] <ogra_> the imports work fine
[12:47] <zyga> ogra_: ?
[12:47] <cjwatson> zyga: missing trailing ".git" in the URL, which is needed for git-to-bzr imports.  But why do you need a git-to-bzr import in the first place?
[12:47] <zyga> ogra_: I clicked retry and it failed once again
[12:47] <cjwatson> zyga: (I've fixed the URL)
[12:47] <zyga> thanks!
[12:47] <zyga> I wanted a git->git mirror
[12:47] <zyga> not a bzr import
[12:47] <cjwatson> then you did it wrong
[12:47] <cjwatson> zyga: https://help.launchpad.net/Code/Git#Mirroring_repositories_from_other_sites
[12:47] <zyga> ah, sorry than, let me remove that and start over
[12:48] <ogra_> zyga, the mirrored tree is at https://code.launchpad.net/%7Esnappy-dev/classic-snap/+git/classic-snap/+ref/master
[12:48] <ogra_> there is no bzr involved
[12:49] <cjwatson> ah, right, so just remove the git->bzr import and then there's nothing else to do
[12:49] <cjwatson> oh, and you should configure https://launchpad.net/classic-snap to have git as its default VCS
[12:49] <ogra_> yeah, not sure where that bzr stuff comes from, the snap has worked fine for the last years
[12:49] <zyga> cjwatson: thanks!
[12:49] <zyga> done :)
[12:49] <ogra_> (including the mirroring)
[12:50] <cjwatson> ogra_: "Created by Oliver Grawert on 2017-07-29 and last modified on 2017-07-29" is where it comes from :)
[12:50] <ogra_> hmm
[12:50] <cjwatson> (anyway, I see it's gone now, so you probably just made a mistake and then forgot about it)
[12:50] <ogra_> yeah
[12:50] <zyga> yeah, I just removed it
[12:50] <zyga> everything is fine now, no dead links
[12:50] <ogra_> it didnt interfere with anything though
[12:51] <ogra_> (and the GH README clearly points to the right urls
[12:51] <ogra_> )
[12:52] <zyga> I wonder how to clean up https://code.launchpad.net/classic-snap
[12:53] <ogra_> why do you think thats needed ?
[12:53] <zyga> well, it's a bit messy
[12:53] <zyga> why is lp:classic-snap in "other"?
[12:53] <zyga> what does it even mean
[12:54] <pedronis> mborzecki: lgtm, small comment about the message,  also  "core snap-id"   vs "core-snap-id"
[12:54] <mborzecki> pedronis: thanks, i'll push a fix in a minute
[12:55] <cjwatson> zyga: that's a bug
[12:55] <cjwatson> but it's not something you can clean up (unless you want to fix the LP UI there)
[12:57] <cjwatson> zyga: not as simple as just filtering that out of the list though; the default repository does still need to be linked to somewhere, as there's useful information on https://code.launchpad.net/~snappy-dev/classic-snap/+git/classic-snap that's not on https://code.launchpad.net/classic-snap
[12:57] <cjwatson> I'm not totally sure whether the fix is to make that information available on https://code.launchpad.net/classic-snap (maybe in a more compact form), or to make the presentation of the link less confusing, or some combination
[12:58] <cjwatson> slightly inclined towards the former
[12:58] <niemeyer> Heya
[12:59] <mup> Bug #1586248 changed: 96boards-kernel need change name <Snapcraft:Invalid> <Snappy:Fix Released> <https://launchpad.net/bugs/1586248>
[12:59] <niemeyer> Can someone please send me an invite for the standup? The Android Hangouts app is somewhat broken still
[13:00] <jdstrand> hey zyga :)
[13:06] <zyga> jdstrand: hey, I'm sure you have plenty of things to catch up on, I will ask you for some reviews as you have the time (you are usually subscribed as a reviewer). How was your trip home?
[13:07] <jdstrand> zyga: I have a fairly long list of things that you asked for last week (and others). I plan to get to them this week, hopefully by tomorrow
[13:07] <jdstrand> zyga: trip home was fine, thanks. uneventful, which is just what you want :)
[13:08] <zyga> jdstrand: sounds good
[13:08] <zyga> jdstrand: just take your time to re-adjust, nothing urgent on my side
[13:10] <pstolowski> jdstrand: hey, i hope you've recovered from the sprint! will you find some time to take a look at my interface hooks PR? as i said it was reviewed a few times already, so you can probably focus on the policy aspect
[13:27] <sitter> Wimpress: heya, did you forget to schedule a new meeting or did it get lost in my inbox?
[13:41] <mup> Bug #1738197 changed: Daemons do not have an /run/user/* dir created <snapd:Confirmed> <https://launchpad.net/bugs/1738197>
[13:42] <nodeman> Does anyone know an easy way to provision an Ubuntu Core machine with use of vSphere?
[13:44] <mborzecki> zyga: there's a couple more errors that need to be fixed in #5138
[13:44] <mup> PR #5138: cmd/libsnap: fix compile error on more restrictive gcc <Critical> <Simple> <Created by zyga> <https://github.com/snapcore/snapd/pull/5138>
[13:45] <mborzecki> zyga: https://paste.ubuntu.com/p/ztx9NMCSQ3/
[13:45] <mborzecki> zyga: i can take over the pr in case you want to focus on something else
[13:47] <zyga> mborzecki: yeah, push away
[13:47] <zyga> I don't have the env available
[13:47] <mborzecki> ok
[13:47] <zyga> thanks
[13:48] <mborzecki> zyga: we should really rewrite snap-confine in go
[13:48] <mborzecki> ;)
[13:49] <zyga> mborzecki: it's not doable
[13:49] <zyga> mborzecki: unless you mean go + big C chunk that runs before main ;-)
[13:49] <mvo> cachio_: from my side all clear for the .6 release, we just need to ensure the store is happy and then it can go out I think
[13:49] <zyga> mborzecki: we can shrinkg the C parts for sure but there's no workaround otherwise
[13:50] <jdstrand> pstolowski: yes, I hope to get caught up on reviews by eod tomorrow
[13:50] <cachio_> mvo, ok, I'll talk to the store team
[13:50] <mborzecki> zyga: iirc we discussed this a bit, i recall taking a look at libcontainer
[13:51] <zyga> mborzecki: really ;)
[13:51] <zyga> mborzecki: not doable
[13:51] <zyga> mborzecki: not everything can be done, I read what libcontainer does
[13:52] <pstolowski> jdstrand: thanks. we were just discussing about landing that PR now to have it in early (before next release); any comments you might have would be addressed in a followup
[13:52] <zyga> mborzecki: I think we should really work on removing most of the hard-coded features to profiles
[13:54] <mup> Bug #1769669 opened: Snapd causes corruption on upgrade  <Snappy:New> <https://launchpad.net/bugs/1769669>
[13:54] <mvo> cachio_: thank you
[14:05] <Wimpress> sitter: Oversight on my part and public holiday in the UK today. I send an invite when I'm back to work
[14:07] <mvo> zyga: the arch fix PR has more failures
[14:07] <mvo> I can paste if you want
[14:09] <zyga> mvo: mborzecki is fixing those
[14:09] <zyga> I only fixed the first one from the log
[14:09] <cachio_> mvo, it is done
[14:09] <cachio_> 32.6 in stable
[14:10] <zyga> woot
[14:10] <zyga> thank you cachio_
[14:10] <mvo> cachio_: !!! thanks
[14:10] <cachio_> np
[14:17] <mvo> zyga, mborzecki out of curiosity, what version of gcc is causing these issues?
[14:17] <mborzecki> mvo: 8.0 and up
[14:18] <mborzecki> mvo: https://gcc.gnu.org/gcc-8/changes.html
[14:20] <mvo> mborzecki: thanks. I can reproduce with the gcc-snapshot package. but I assume you have it all under control? or want a hand?
[14:21] <mborzecki> mvo: i'll be pushing patches in a minute
[14:21] <mvo> mborzecki: cool
[14:22] <zyga> mborzecki: hey, are you handling 5138
[14:22] <zyga> I can pick it up now
[14:23] <mborzecki> zyga: i have all the changes now, just rerunning make check
[14:32] <mborzecki> zyga: mvo: pushed
[14:32] <zyga> I saw
[14:32] <mborzecki> builds cleanly now
[14:33] <mborzecki> the last one was funny, had to run the test to check if it's actually testing the right thing
[14:34] <mvo> mborzecki: ta
[14:34] <zyga> mborzecki: was the change from * to [] needed?
[14:35] <mvo> mborzecki: works fine here with gcc-snapshot, thanks for the fix
[14:35] <mborzecki> zyga: yes, it's the least effort fix
[14:35] <zyga> mborzecki: can you explain it?
[14:37] <mvo> zyga: you mean in snap-test.c ?
[14:37] <zyga> yes
[14:37] <mborzecki> zyga: i didn't want to hardcode the size to 41, but to avoid the check for truncation i had to switch to memcpy, if someone changed the length of good_bad_name this may break the tests
[14:37]  * cachio_ afk
[14:37] <zyga> I don't mean that
[14:37] <zyga> I mean this specifically:
[14:38] <zyga> - const char *good_bad_name = "u-94903713687486543234157734673284536758";
[14:38] <zyga> +	const char good_bad_name[] = "u-94903713687486543234157734673284536758";
[14:38] <zyga> is that for the sizeof to work?
[14:38] <mborzecki> zyga: this is to be able to do char varname[sizeof good_bad_name] = { 0 };
[14:38] <mborzecki> zyga: yes
[14:38] <zyga> ok
[14:38] <zyga> thanks
[14:38] <zyga> +1
[14:38] <mborzecki> didn't want to do alloca(strlen(good_bad..)+1)
[14:50] <mvo> mborzecki: I pushed a tiny extra commit as it was breaking on ubuntu with the gcc8 fixes, but now it should work everywhere
[14:51] <mborzecki> mvo: yup, works here too
[14:55] <mvo> yay
[14:55] <pedronis> pstolowski: once interface hooks lands it seems it will open up a lot of its follow ups to review
[14:56] <pstolowski> pedronis: yes
[14:58]  * zyga needs to break now; I will be back in 3 hours to work on more things
[15:00] <zyga> mvo: gcc warns about unused result of those two?
[15:01] <mvo> zyga: chdir only, I did the rmdir for symetry
[15:01] <mborzecki> zyga: didn't warn here, but maybe there's something turned on by default in gcc-snapshot or ubuntu glibc
[15:05] <mvo> zyga: I think we use -Wunused-result or something, let me look
[15:05] <zyga> no worries, I was just curious
[15:05] <zyga> the patches look good
[15:05] <mvo> zyga: http://paste.ubuntu.com/p/B9TBshVG2n/
[15:05] <mvo> zyga: just fyi
[15:12] <mborzecki> mvo: looks like something in libc then
[15:15] <mborzecki> mvo: zyga: extern int chdir (const char *__path) __THROW __nonnull ((1)) __wur; where __wur sets warn_unused_result but only if FORTIFY_LEVEL is > 0
[15:19] <mup> Bug #1769669 changed: Snapd causes corruption on upgrade  <snapd:Confirmed> <https://launchpad.net/bugs/1769669>
[15:19] <mvo> mborzecki: ok
[15:35]  * zyga is really off now
[15:35] <pstolowski> pedronis: you're going to make one more pass over interface hooks PR (Gustavo's comments), right?
[15:37] <mvo> grr, now ubuntu-18.04-64 fails in spread-shellcheck with a pip install --user error
[15:37] <mvo> (i.e. pip fails)
[15:37] <mvo> mborzecki, zyga just fyi (pr 5138)
[15:37] <mup> PR #5138: cmd/libsnap: fix compile error on more restrictive gcc <Critical> <Simple> <Created by zyga> <https://github.com/snapcore/snapd/pull/5138>
[15:52] <pedronis> pstolowski: did something change since I last looked?
[15:54] <kyrofa> sergiusens, https://forum.snapcraft.io/t/proposal-snapcraft-provides/5275
[15:55] <pstolowski> pedronis: i've addressed the comments from Gustavo that I missed from his earlier review; and refresh was moved into separate PR. that's about it
[15:56] <pedronis> pstolowski: ok, I will look tomorrow morning at this point, also github is giving me unicorns
[15:56] <pstolowski> pedronis: sure
[16:01] <sergiusens> kyrofa: https://github.com/snapcore/snapcraft/blob/master/TESTING.md#testing-arm
[16:35] <sergiusens> kyrofa: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_errors
[16:37] <sergiusens> kyrofa: from http.client import responses
[16:38] <sergiusens> kyrofa: requests.status_codes.codes
[18:09] <mup> PR snapcraft#2123 closed: file_utils: don't let FileNotFoundError escape <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2123>
[18:20] <jdstrand> noise][: hey, I've been getting 504's on https://dashboard.snapcraft.io/reviewer/ubuntu/. https://status.snapcraft.io/ looks ok
[18:49] <kyrofa> sergiusens, I just realized the sentry Always PR got rid of the environment variable with the same functionality-- how do you anticipate making this work in CI?
[18:49] <kyrofa> I'm getting some tracebacks in CI, I'd like to set it up to automatically submit those
[18:49] <kyrofa> I suspect LP will want to do the same at some point
[18:52] <sergiusens> kyrofa: yeah, I got rid of the environment to force us into the workflow. For now you could just create the appropriate config
[18:55] <kyrofa> sergiusens, sure, just curious what the long-term plan is. Adding something like that back?
[18:56] <sergiusens> an env var is something we can add back, but I'd prefer something closer to a setting, that involves a larger/longer discussion though
[19:25] <magicalt1out> out of curiosity hows this snap delay/schedule stuff coming along? Because with Gimp being a snap recommended at install time, if I was doing some design stuff (I can't design, we're talking hypothetics here) it'd be rather annoying if it suddenly stopped working or went a bit wacky cause Gimp got upgraded from under me.
[19:25] <magicalt1out> thats the one that springs to mind, i'm sure you could say the same for a lot of apps
[19:25] <magicalt1out> or maybe its a non issue
[19:25] <magicalt1out> hence my curiosity :)
[19:30] <kyrofa> Hey magicalt1out, I think most of the snapd team is EOD already, but there is a bit of info in the forum, and you can always ask there if you need async communication
[19:41] <mcphail> magicaltrout: "snap revert" is supposed to be the solution to that problem. I don't 100% agree
[19:50] <magicaltrout> interesting mcphail... I 100% agree with your not 100% agreeing
[19:53] <mcphail> magicaltrout: it'll maybe be better when people start using tracks as standard. that way there might be a persistent 2.8 track
[19:57] <kyrofa> mcphail, I don't think that's what magicaltrout was asking (correct me if I'm wrong magicaltrout). The concern is that, when a snap updates, if an app is already running, it may run into issues accessing the underlying data directories with the confinement
[19:58] <kyrofa> magicaltrout, you can schedule updates today, but that ^ is still an issue for when an update _does_ happen as far as I'm aware
[19:58] <kyrofa> Unless the snap in question is classically confined
[19:58] <mcphail> yes, that's a particularly annoying problem
[20:00] <mcphail> although i don't know if it is such an issue for snaps with the home plug
[20:03] <om26er> BUG: wrong emphasis of headings on this page https://docs.snapcraft.io/build-snaps/scriptlets
[20:06] <kyrofa> om26er, what are you talking about? That's obviously on purpose. Your eyes are drawn to the emphasis, no?
[20:06] <kyrofa> *cough*
[20:07] <kyrofa> om26er, mind logging an issue here? https://github.com/canonical-docs/snappy-docs
[20:07] <om26er> wonder if we have a new design language ;-)
[20:07] <magicaltrout> kyrofa is correct i'm curious about stuff that is up and running
[20:07] <kyrofa> Heh
[20:08] <magicaltrout> kyrofa: whats this schedule stuff you speak of?
[20:08] <kyrofa> magicaltrout, let me go forum diving,  hold on a sec
[20:08] <magicaltrout> snap set core refresh.schedule?
[20:10] <kyrofa> magicaltrout, yeah https://forum.snapcraft.io/t/refresh-scheduling-on-specific-days-of-the-month/1239 is the first one I find
[20:12] <magicaltrout> ah yeah thats cool, I'm really coming at it from a Charm angle. Because I want to ship Analytics tools and it'll be really sad for users if it updates mid workday mid month end
[20:12] <magicaltrout> for example
[20:12] <magicaltrout> thats cool though, i can try and set that during the install hook
[20:12] <kyrofa> Yeah I hear ya
[20:22] <mcphail> magicaltrout: i'm poking the devs about this :) https://forum.snapcraft.io/t/bug-saves-are-blocked-to-snap-user-data-if-snap-updates-when-it-is-already-running/3226
[20:24] <kyrofa> mcphail, ah,  yes
[20:25]  * mcphail feels it is his role to be an annoyance ;)
[20:40] <magicaltrout> annoyances ensure the useful stuff not just the fun stuff gets implemented ;)
[21:34] <mup> PR snapcraft#2115 closed: storeapi: ensure snap ID is sane before using it <Created by kyrofa> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/2115>
[23:36] <popey> pbek: just noticed you have old versions in beta/candidate/edge of qownnotes
[23:37] <popey> pbek: you can 'snapcraft close beta' for example to nudge people towards stable (and thus the latest build)
[23:37] <popey> (same for the other channels)


[00:33] <ubptgbot> <Gabriel Horevicht> Nobody knows?
[00:33] <ubptgbot> <Gabriel Horevicht> No one knows, like queen of stone age song
 Hmmm
 @Gabriel Horevicht [Nobody knows?], sounds like a good plan maybe
 @UniversalSuperBox [No, just run the installer], not with the "community" ports, no?
 @Gabriel Horevicht [Does have any problem to install with the "old" boot.img and then update to xeni …], you should theoretically be able to do the "manual" install and use the 16.04 rootfs tarball instead of the old 15.04 one, i guess
[02:28] <ubptgbot> <Sebastien Vienneau> Would you guys ever think of doing like and Android TV genre or is and call it like "UbunTVu" and something that puts your back in control of your TV experience something that has the words "Ubuntu + TV + You" in some cool form?
[02:29] <ubptgbot> <Sebastien Vienneau> [Edit] Would you guys ever think of doing like and Android TV genre of OS and call it like "UbunTVu" and something that puts your back in control of your TV experience something that has the words "Ubuntu + TV + You" in some cool form?
 UbuntuTV was a thin but it was based in Unity 7 so I don't think it'll be easy to ttansition to Unity 8 and I don't it's a goof investment if time and effort 😄
 In theory one could build a ubuntu tv device using a raspberrypi, raspbian, and unity, but I think the big hurdle atm is unity
[02:35] <ubptgbot> <Sebastien Vienneau> @Javacookies [UbuntuTV was a thin but it was based in Unity 7 so I don't think it'll be easy t …], What if you guys got "AnBox" fully working or do what Chromebooks/ChromeBoxes and Chromium based Distros like FydeOS does with running Linux apps in a container and run Android apps on Ubuntu touch can't you guys study what Chromi
[02:35] <ubptgbot> um projects have done and reverse engineer it?
[02:36] <ubptgbot> <Sebastien Vienneau> @Javacookies [UbuntuTV was a thin but it was based in Unity 7 so I don't think it'll be easy t …], [Edit] @Shakendo  … What if you guys got "AnBox" fully working or do what Chromebooks/ChromeBoxes and Chromium based Distros like FydeOS does with running Linux apps in a container and run Android apps on Ubuntu touch can't you gu
[02:36] <ubptgbot> ys study what Chromium projects have done and reverse engineer it?
 Anbox is basically android in a container
[02:37] <ubptgbot> <Sebastien Vienneau> @Shakendo [Anbox is basically android in a container], Then why is it so complicated and not simple like what Chromium has done?
 Cause its more complicated than how I put it, I dumbed it down a bit
[02:39] <ubptgbot> <Sebastien Vienneau> @Shakendo [Cause its more complicated than how I put it, I dumbed it down a bit], Then reverse engineer what Chromium has done to get Linux apps on itself...
 Well we are all volunteers here, so feel free to do that
 @Sebastien Vienneau [Then reverse engineer what Chromium has done to get Linux apps on itself...], Um, set up a whole significant infrastructure for running containers, one that is still not feature-complete? What Chromium has done isn't simple!
 It is if your just a end user, but the developers prob went through programming hell to make it all work
 Hi there, I have a question about the Anbox installation process
 When doing the following... … adb shell … sudo mount -o rw,remount / … sudo apt update … ...apt tells me there are updates available for some of the installed packages.  I was tempted do the upgrades like on my other linux systems: … sudo apt upgrage … but then I thought I should be cautious and not upgrade the packages.  Could I possibl
[04:47] <ubptgbot> e do damage to my existing, working system if I were to do the upgrade?  I'm on OTA-10 RC, btw. … Thanks!
 (oops, typo:  "sudo apt upgrade")
 Yes, you will break UT and have to do a full reinstall if you do apt upgrade
 UT doesnt do updates with apt, it does updates through the openstore
 Thanks!
 My spidy-sense started tingling when I was considering doing the apt upgrade. 🙈
 I had a feeling it would be a bad idea, but I was wondering what the official recommendation was.  Thanks, again.
[05:17] <ubptgbot> <Yann Escarbassiere> @Shakendo [Yes, you will break UT and have to do a full reinstall if you do apt upgrade], Yay .... I broke my fist time my UT ... X)
[05:22] <ubptgbot> <Gabriel Horevicht> oh well
[05:22] <ubptgbot> <Gabriel Horevicht> I'm at bluestacks at PC
[05:22] <ubptgbot> <Gabriel Horevicht> Managed to install UT xenial just by terminal and ubuntu-device-flash install
[05:23] <ubptgbot> <Gabriel Horevicht> But, lots of bugs, and can't find whatsapp kkkk any help with openstore?
[05:23] <ubptgbot> <Gabriel Horevicht> Besides all of that, can feel the UT freedom, just great, love the animations and sliding <3 tnx developers
 @Gabriel Horevicht [But, lots of bugs, and can't find whatsapp kkkk any help with openstore?], What do you need?
 @Gabriel Horevicht [But, lots of bugs, and can't find whatsapp kkkk any help with openstore?], There is no whatsapp man
[06:17] <ubptgbot> <Martin Menzel> (Sticker, 512x512) https://irc.ubports.com/lvjjvllw.webp
[08:18] <ubptgbot> EmilSMN was added by: EmilSMN
 Good day! Please tell me how to install Ubuntu Touch on the smartphone LG Magna h502f (my90ds), and I looked, but the normal user is not present.
 [Edit] Good day! Please tell me how to install Ubuntu Touch on the smartphone LG Magna h502f (my90ds) Not found as establish.
 @EmilSMN [Good day! Please tell me how to install Ubuntu Touch on the smartphone LG Magna …], You cannot currently, sorry.
[14:44] <ubptgbot> <mark alexa> Guys, sometimes Nexus 5 reboots itself after finishing a phone call. Anyone have experienced the same ?
 you get the black splash screen, or just the "ubuntu..." animation?
 oh cool, search in the app drawer is now as functional as the app scope … you can now search with wildcards and tags/search words
 typing is still stuttering though … app drawer = faster search results, slower typing … app scope = slower search results, faster typing 😅
 Lol
[15:17] <ubptgbot> <Gabriel Horevicht> anbox works on titan?
 Probably not
 [Edit] Probably not currently
[15:28] <ubptgbot> <Gabriel Horevicht> when i get to install UT on titan... oh well, i`ll be damned
[15:28] <ubptgbot> <Gabriel Horevicht> a dream had come true for like, 30 minutes
 Anbox is very experimental atm eitherway
 @Javacookies [typing is still stuttering though … app drawer = faster search results, slower typ …], I noticed the same trying
 @Javacookies [typing is still stuttering though … app drawer = faster search results, slower typ …], [Edit] I noticed the same thing
 @mark alexa [Guys, sometimes Nexus 5 reboots itself after finishing a phone call. Anyone have …], It's not normal. I have it before but only like 1-2 times
 Maybe a ram issue?
[15:41] <ubptgbot> <mark alexa> @dohbee [you get the black splash screen, or just the "ubuntu..." animation?], Both. But before that it freezes for about 30s.
 Freezes turns black and shows the ubuntu animation?
 Or freezes turns black, shows the nexus logo before showing the ubuntu animation
[15:44] <ubptgbot> <Gabriel Horevicht> so, in other words, i`m not able to use whatsapp on UT? neither anbox? how to daily use, then?
 @Gabriel Horevicht [so, in other words, i`m not able to use whatsapp on UT? neither anbox? how to da …], If you depend on using Whatsapp then UT is not for you.
 You will need to adapt yourself
[15:51] <ubptgbot> <Gabriel Horevicht> not my fault, the people on brazil only use that fckin app in university
[15:52] <ubptgbot> <Gabriel Horevicht> oh well, thanks guys for all help … going back to lineage, unfortunately
[15:52] <ubptgbot> <Gabriel Horevicht> keep going that awesome work
 👍👍👍
 Boa sorte
[15:53] <ubptgbot> <Gabriel Horevicht> é nóis bro hehe
 You could do it with whatsapp web
 Or well you could ask whatsapp about UT support
 in theory it could be possible to write UBPorts UI for yowsup Python library
 but it is never-ending battle of WhatsApp trying to ban alternative clients and them to evade
 Yeah unless we somehow get in contact with them somehow
 probably too small for them to even care
 @Fuseteam [You could do it with whatsapp web], well, no, you still need a device with proper whatsapp running to use the web site
 I suppose
 it can be Android VM on desktop for example
 theoretically yes
 @NotKit [probably too small for them to even care], They supported the old nokia's? And windows phone even untill it went down
 @dohbee [https://ubuntu-touch.io is the site for the OS. UBports is the foundation.], Rodney, thanks, but....  That simply changes the question.  Where on the site https://ubuntu-touch.io , does a person learn what is the current stable version?  I can't find it shown anywhere on that site, either.
 @dln949 [Rodney, thanks, but....  That simply changes the question.  Where on the site ht …], I guess I don't know what you're asking to find then. The current stable version is what you get when you install to a device from the "stable" channel
 it is currently based on ubuntu 16.04
 Well, there is no place where that's announced...  If so, it doesn't seem to work. (I noticed using the brilliant Stellarium port.)
 it does have one
 So: It appears it does not work with UT.
 or you have one with defective hardware: https://www.reddit.com/r/Nexus5/comments/2xsad2/how_can_i_reset_compass_data_on_the_nexus_5/cpbfx74/
 Possibly. Could someone with a Nexus 5   check with the "SensorStatus" app?
 (Photo, 1080x1920) https://irc.ubports.com/ULzKH4Jn.png
 It may be related to the gps?
 Yep. Looks the same for my N5. Does anyone have it working?
 I don't think it is related to FPS, they are different sensors. Magnetic sensors usually exploit the Hall effect, which is actually much simpler than measuring GPS.
 [Edit] I don't think it is related to GPS, they are different sensors. Magnetic sensors usually exploit the Hall effect, which is actually much simpler than measuring GPS.
 Should I file an issue? With which component?
 If you think it worth doing it, I think the safe bet is to do it here: https://github.com/ubports/ubuntu-touch/issues
 @dohbee [or you have one with defective hardware: https://www.reddit.com/r/Nexus5/comment …], The link deals with compass readings that are off. But it appears UT does not report compass readings at all.
 @ruedigerkupper [The link deals with compass readings that are off. But it appears UT does not re …], well the link doesn't know about UT at all. i don't know if compass works on any devices currently. if not perhaps it's an issue for libhybris. does compass work in sailfish for example?
 otherwise if it's only on nexus 5, it's harder to say. and if for some people it does work, then perhaps it is a hardware issue.
 but a sample size of 2 i think is not enough to say that it's not a hardware issue
 Agreed. Anyone listening: would you mind testing your compass redings with "SensorStatus" on UT or on other OS?
 Iirc compass doesn't work in stellarium
 Hi! Sorry, what is lirc compass?
 Haha ignore the iirc
 It stands for 'if i recall correctly'
 All right! Thanks :-). What device are you running? Does it report in SensorStatus?
 I'm running on a E5 and uh it was mentioned once
 I did not run sensor status at the time i wrote that :p
 there is a compass app `Xompass` in the Open Store but it only works with a few devices.  It might work on Nexus 5 - worth a test.
 Can you check if it works in xompass?
 ...... Dang steve'd :p
 @Fuseteam [...... Dang steve'd :p], brilliant minds think alike 😉
 Maybe :p
 @Fuseteam [Maybe :p], I will admit that you are smarter than me though ☺
 In my case xompass kinda works even tho sensorstatus does not report it
 Checked: Not working for me. Hitting the Calibrate button does nothing at all.
 @TotalSonic [I will admit that you are smarter than me though ☺], I wouldn't say that
 Guys, you're so charming...
 @Fuseteam [I wouldn't say that], well, I have zero clue how to code a flik keyboard, that's for sure
 Lol
 i think stellarium doesn't use Qt, so it can't use compass via QtSensors, indeed
 @TotalSonic [well, I have zero clue how to code a flik keyboard, that's for sure], Copy paste and modify
 Stole it from the japanese layout and adapted it :p
 @Fuseteam [Stole it from the japanese layout and adapted it :p], "mediocre composers borrow, genius ones steal" - Igor Stravinsky
 Ehhh
 But yeah neither sensorstatus nor stellarium appear to be good benchmark for compass readings
 sensorstatus should work at least for all the sensors that work
 Xompass works for me yet sensorstatus doesn't report it
 @Fuseteam [It stands for 'if i recall correctly'], Fun part: I misread it for LIRC and googled LIRC=Linux Remote Control. It instantly set me off wondering how an infra red compass could work 😝.
 Unless xompass is doing some magic
 @ruedigerkupper [Fun part: I misread it for LIRC and googled LIRC=Linux Remote Control. It instan …], Ha! Should have known that you read I as l
 @ruedigerkupper [Fun part: I misread it for LIRC and googled LIRC=Linux Remote Control. It instan …], [Edit] Ha! Should have known that you read I as l 🙈
 It's actually conceivable: Measure direction of strongest IR activity (sun), calculate against clock time and get orientation. It only works in daytime, though.
 That's how you get your orientation using an (analog) wrist watch...
 It is?
 i usually look around when trying to orient myself, rather than at my wrist :P
 anyway, getting off topic :P
 I look for the sun too but yeah we are :P
 Right. So what is the best way checking if the compass works? I thought SensorStatus was, but it seems Xompass can work while Sensorstatus doesn't. Getting confused.
 I'd say xompass atm
 @ruedigerkupper [Right. So what is the best way checking if the compass works? I thought SensorSt …], execut test_compass if there is any
 But i digress i have no idea how xompass works
 Or is it in cluded in test_sensors?
 At least it should be listed there
 I get 9 sensors
 But only 1 listed
 (Photo, 720x1280) https://irc.ubports.com/bKEjRNc1.png
 (Document) https://irc.ubports.com/sDdZq0RH.null
 looks quite different for me:
 @Fuseteam [<reply to media>], Thats a known problem with libhybris, as soon as it should print float values it segfaults lol
 Ah lol
 No compass reading in test_sensors.
 (for me)
 Hmm
 It aborts for me, too. No reason reported.
 @Flohack [Thats a known problem with libhybris, as soon as it should print float values it …], Appearently a known bug
 Observe the message "library sensors.oem.so not found". Could it be related?
 @ruedigerkupper [Agreed. Anyone listening: would you mind testing your compass redings with "Sens …], Sensor status in UT on my Nexus 5 shows no reading from my compass.
 Xompass is stuck at azimuth -1 no matter which way I turn it. Calibrate button does nothing on mine either.
 test_sensors says I have 7 but aborts testing after showing 6 because of invalid pointer error.
 I am not sure if compass ever worked on any device ^^
 @Flohack [I am not sure if compass ever worked on any device ^^], according to the Xompass Open Store info it says it should work on BQ E4.5, and might work on BQ E5
 Makes me wonder too
 Works on E5
 not always the most accurate
 Okay. That seems compass is work in progress in UT. Since we have such beautiful apps like Stellarium (or geocaching apps) which use the campass, I suggest filing it as a feature request.
 Feel free if it isn't already
 (Voice, 0s) https://irc.ubports.com/D2kMFmWz.oga
 @ruedigerkupper [Okay. That seems compass is work in progress in UT. Since we have such beautiful …], even if compass sensor works on devices, i'm not sure stellarium can use it, if it's not using Qt
 Right, but that is a secondary problem. I feel prioroties are: … 1. Make compass readings available on UT for all devices. (This affects UBPorts in general.) … 2. Implement its usage in apps (this affects individual apps like Stellarium or Geocaching).
 Right now, we should go for 1.
 Well feel free to debug libhybris then ^^
 [Edit] Right, but that is a secondary problem. I feel priorities are: … 1. Make compass readings available on UT for all devices. (This affects UBPorts in general.) … 2. Implement its usage in apps (this affects individual apps like Stellarium or Geocaching).
 And see here: https://github.com/ubports/ubuntu-touch/issues/38
 So there is a bug report
 Now what socery is xompass doing
 Hi Florian, I can't, I'm lacking the skills for doing so. Sorry, but that's how it is. Meanwhile (I try improving) I hope I can help reporting bugs as secifically as possible.
 @Fuseteam [Now what socery is xompass doing], not working
 Works on the E5.........
 so you think it does
 @Flohack [And see here: https://github.com/ubports/ubuntu-touch/issues/38], Okay, so #38 is the place, thank you.
 i think magnetic field sensor is just not handled
 @dohbee [i think magnetic field sensor is just not handled], Not handled where?
 @Flohack [Not handled where?], i'm not sure if hybris does enough, but in qtubuntu-sensors we only have accelerometer and orientation supported
 But then it shouldn't work on any device. But apparently it is on BQ E5.
 [Edit] But then it shouldn't work on any device. But apparently it does on BQ E5.
 @ruedigerkupper [But then it shouldn't work on any device. But apparently it does on BQ E5.], no, it doesn't
 @Fuseteam [Works on the E5.........], See above.
 @ruedigerkupper [See above.], This is not using QtSensors
 looks like it's a hacky thing that's hard-coded to poke at `/sys/devices/` files, and probably only "works" on MTK devices
 `        ifstream myfile ("/sys/devices/platform/msensor/driver/sensordata", ios::in );`
 in fact, it says it only works on e4.5, and might work on e5, and doesn't work on pretty much every other device
 That seems to correspond to the above reports.
 omg direct sensor access how nice
 not nice
 it was sarcastic
 but anyway, sensors seems to be another thing where we need a lot of work. also looks like orientation "sensor" is not actually using orientation sensor from hybris, but is just wrapping accelerometer
 @dohbee [looks like it's a hacky thing that's hard-coded to poke at /sys/devices/ files, …], There we go the magic unveiled


[09:46] <cjwatson> Ian_Corne: perl UUID> that doesn't stop the upgrade, right?  it's known and harmless
[09:48] <cjwatson> Ian_Corne: doc-base ends up running in between the upgrade of perl-base and libuuid-perl, but it's been fixed to fall back and cope
[11:10] <MechanisM> hello ppl where to download testing iso for 12.04?
[12:12] <bazhang> !daily
[12:12] <bazhang> whoops
[12:19] <sagaci> that's correct
[12:24] <bazhang> sagaci, yeah, but he quit :)
[14:23] <BluesKaj> Hey folks
[15:03] <FernandoMiguel> g'afternoon
[19:01] <BluesKaj> BBL, stuff to do
[19:50] <xsinick> hello all
[19:50] <xsinick> can I talk about  the new ubuntu desktop here?
[19:52] <xsinick> how  many of you actually use  the new unity desktop
[19:52] <xsinick> if so do you still need  10.10 as a power user
[19:52] <bazhang> xsinick, this is for 12.04
[19:52] <bjsnider> if you want to start a flame war over unity, this isn't the place
[19:53] <xsinick> I see
[19:53] <bazhang> xsinick, just chat in #ubuntu-offtopic
[19:53] <xsinick> ok thanks guys
[19:53] <bazhang> np
[19:53] <xsinick> I must say  unity is getting better
[19:53] <xsinick> slow but sure
[19:53] <xsinick> :)
[19:54] <xsinick> I totally se why gnome was droped
[19:55] <xsinick> have  a good day to all
[22:08] <FernandoMiguel> inception: win7 on a VB with raw disk access running ubuntu 11.10,  all hosted on Ubuntu 12.04


[13:26] <ubuD104> Is there a way to get rid of or replace systemd?
[13:28] <ubuD104> Is this thing working?
[13:28] <JanC> not a supported way
[13:29] <ubuD104> you know anything about systemd and how to get rid of it?


[11:45] <dguerri> this might not be the right channel… but.. is there some docs about the juju RAPI?
[11:52] <teknico> dguerri, hi
[11:54] <dguerri> hi, teknico
[11:55] <teknico> dguerri, not that I know of
[11:58] <frankban> dguerri: you could find some info on setting up the rapi-rollup agent in the documentation included in juju-gui: http://bazaar.launchpad.net/~juju-gui/juju-gui/trunk/view/head:/HACKING
[12:03] <dguerri> thanks frankban but I'm thinking about writing a ruby binding for the juju restful API
[12:09] <frankban> dguerri: it's a websocket API, it makes use of good rest principles, but still it's not a rest API. Unfortunately, my I am not aware of a place where the stream is documented.
[12:10] <dguerri> mmmh, so it might not be the right interface for a lang binding …
[12:12] <bac> morning frankban.  how goes the effort?
[12:19] <frankban> bac: it's under review, you can glance at https://codereview.appspot.com/6977043/ . Tests results are different based on who runs the suite.
[12:20] <bac> frankban: oh, that's good.  keeps people on their toes
[12:20] <frankban> dguerri: I guess it depends on what you want to achieve
[12:20] <frankban> bac: :-)
[12:23] <bac> frankban: is lp2kanban busted?  i see your defect in done-done has a bug but it isn't populated
[12:23] <frankban> bac: it seems so
[12:25] <frankban> bac: the same for other two cards in "ready to code"
[12:25] <bac> yep.  i'll look into it
[12:38]  * frankban lunches
[13:06] <bac> frankban: lp2kanban is undead again
[13:11] <gary_poster> hey benji.  I thought a fun improvement I could tackle today in very limited time might be to update the release docs a bit.  if that sounds ok to you and you are available to talk through things with me so I can pick your brain sometime, lemme know
[13:11] <benji> gary_poster: sounds like a plan
[13:11] <gary_poster> cool
[13:12] <gary_poster> ty
[13:16] <gary_poster> bcsaller, did you see what I meant about the rietveld review?  In a bit I'll make my own diff
[13:17] <frankban> bac: cool thanks
[13:17] <bac> it is not very robust wrt ill configured boards and projects
[13:18] <gary_poster> bac, what cam we improve for poor configuration
[13:18] <gary_poster> thank you for fixing btw
[13:18] <bac> gary_poster: i just added some exception handling around the call to the board processing.  so if someone (<cough> green) isn't configured their processing stops but other boards continue
[13:19] <gary_poster> heh
[13:19] <gary_poster> ok cool thanks bac.  you shot a note to gmb too?
[13:19] <bac> i've pinged him, waiting for him to return from lunch
[13:19] <gary_poster> cool
[13:20] <bac> brits and their ill-timed lunches
[13:20] <gary_poster> Europeans and their ill-timed lunches!  Americans and their ill-timed desire to sleep through till the morning!
[13:20] <gary_poster> :-)
[13:24] <benji> Humans and their ill-timed biological needs.
[13:54] <bcsaller> gary_poster: I was able to fix it, still don't know why it happened before
[13:54] <gary_poster> bcsaller, cool, reviewing, thanks.
[14:01] <gary_poster> teknico, you are going to start bug 1074413, I'm guessing
[14:01] <_mup_> Bug #1074413: GUI charm should require HTTPS connections to the environment by default <deploy-story> <juju-gui:Triaged> < https://launchpad.net/bugs/1074413 >
[14:02] <gary_poster> bac, I made room for you on secondary story to start tests ofthe pan/zoom module, based on bcsaller
[14:02] <gary_poster> 's branch in review
[14:02] <gary_poster> hazmat if you could land your branch that would really help us keep the flow moving
[14:04] <hazmat> gary_poster, eta 1hr
[14:04] <gary_poster> thanks
[14:09] <teknico> gary_poster, yep
[14:10] <bac> gary_poster: ok
[14:18] <bac> gary_poster: there is a card for bug 1083935 but it is blocked by 1077050 and 1077051.  only the latter seems to be fixed.  unblock it and carry on?
[14:18] <_mup_> Bug #1083935: Environment pan/zoom code is not tested sufficiently <juju-gui:Triaged> < https://launchpad.net/bugs/1083935 >
[14:34] <gary_poster> bac, yes, that's based on plans that have been superceded.  You are still blocked on Ben's branch, but since you are working from it, it's ok
[14:34] <gary_poster> bcsaller, quick checkin?
[14:34] <bcsaller> yeah
[14:45] <bac> hi bcsaller, i just grabbed your current branch.  when i try to run the tests i get a time out on the first test and it stops.  anything different about running tests with your new work?
[14:47] <bcsaller> bac; left a .only on one of the test that _is_ having issues, reproposed the branch w/o that , sorry
[14:48] <bac> bcsaller: np, will grab new version
[14:50] <bac> bcsaller: cool, it now works except for that one test failure
[15:11] <frankban> gary_poster: hum... it seems that our debug server does not contain everything needed. I see this in the js console after switching to staging in a deployed charm: http://pastebin.ubuntu.com/1452506/
[15:12] <gary_poster> frankban, ack on call will look soon
[15:16] <frankban> gary_poster: thanks, and... problems also in the production server: http://pastebin.ubuntu.com/1452512/
[15:16] <gary_poster> teknico, ^^^ ?
[15:17] <gary_poster> will look asap
[15:17] <teknico> gary_poster, looking
[15:20] <teknico> frankban, so, what files are missing?
[15:24] <frankban> teknico: I don't know, my understanding is that https, refusing to load external insecure resources, exposes a problem we have: our releases don't contain everything required by the GUI, and the YUI loader tries to fetch libraries from the net (e.g. ellipsis, markdown, timer)
[15:24] <teknico> ah, I see
[15:25] <gary_poster> sorry I didn't QA enough to catch that
[15:25] <gary_poster> teknico, previous call ran over, sorry.  talk after standup?
[15:25] <teknico> gary_poster, sure
[15:25] <gary_poster> frankban, teknico we may need to revert the https code to let frankban proceed :-/
[15:26] <teknico> gary_poster, right. I still did not manage to see tests complete successfully :-/
[15:28] <gary_poster> teknico, I am afraid that this is going to be a very serious problem
[15:28] <gary_poster> bac bcsaller benji frankban goodspud hazmat Makyo teknico call ni 2
[15:28] <frankban> gary_poster: I am not blocked, and I already merged trunk and resolved conflicts. And, AFAICT, this is a bug of the GUI, not of the charm. However, is uistage broken?
[15:28] <gary_poster> frankban, ui stage is not broken
[15:29] <gary_poster> because not served from charm, or from httos
[15:29] <gary_poster> https
[15:29] <gary_poster> but this means that the charm is now unusable
[15:29] <frankban> gary_poster: yes
[15:30] <gary_poster> yes the bugfix goes in the gui
[15:30] <gary_poster> but meanwhile the charm is broken
[15:30] <gary_poster> frankban, bcsaller starting at X:31 :-)
[15:30] <frankban> gary_poster: so you are right, better to revert the changes. Even better if someone can confirm what I see.
[15:40] <hazmat> teknico, http://bazaar.launchpad.net/~hazmat/juju/rapi-rollup/view/head:/juju/agents/api.py#L153
[15:41] <teknico> hazmat, great, thanks
[15:54] <Makyo> bcsaller, I think I figured out the resize thing.
[15:54] <bcsaller> Makyo: ha, sweet
[15:55] <Makyo> bcsaller, it's a little unfortunate :|  Resize events are only fired when bound using Y.on(), which we're not doing with the module event binding because of publish.  If I bind it in initializer in mega.js how it used to be bound, it works.
[15:56] <bcsaller> Makyo: look at the change in the yui bindings in d3-comp though, it should cover that case, thats where I was getting stuck
[15:59] <Makyo> bcsaller, Ah, I see it now.  Passing window as context gets the event to fire, at least, but then this is set to the YUI window node, rather than the module.  Is that the problem?
[15:59] <bcsaller> the handler won't be able to pull the state it needs to run I think
[16:01] <goodspud> hazmat, let me know when you are free to talk about PPAs, login, etc
[16:01] <hazmat> goodspud, ack, 5m max
[16:01] <hazmat> eta
[16:01] <goodspud> cool
[16:09] <hazmat> goodspud, juju-ui hangout
[16:10] <Makyo> bcsaller, after target = Y;, add handler.context = null; and it works.
[16:10] <Makyo> Not...sure why it doesn't like the context in there.
[16:11] <bcsaller> Makyo: changing the context on a window event breaks it maybe... that is odd
[16:16] <gary_poster> teknico, would you like to have a call, or postpone to tomorrow, or...?
[16:18] <Makyo> bcsaller, does that get us closer to where we need to be?
[16:18] <bcsaller> Makyo: I think, let me finish testing it
[16:19] <teknico> gary_poster, a call today would be better, I'll get back to you in a few minutes, thanks
[16:19] <bcsaller> Makyo: yes, thanks alot, that working
[16:19] <Makyo> Whew
[16:20] <bcsaller> Makyo: the test is still failing, but I can track that down now that the event is properly handled
[16:22] <bcsaller> Makyo: got it, going to push again :)
[16:22] <frankban> gary_poster: re tls, e have another problem: we want, in the GUI to fetch data from http://jujucharms.com/
[16:24] <bcsaller> gary_poster: makyo found the issue and I've pushed the updates, should I go ahead and land it now?
[16:37] <teknico> frankban, I guess we can ask webops to enable https://jujucharms.com/ :-)
[16:46] <teknico> gary_poster, re: call, main thing would be making tests work, if you could help me there it'd be great, otherwise we can postpone
[16:55] <gary_poster> bcsaller, please land, yes
[16:55] <gary_poster> thank you
[16:56] <gary_poster> frankban, :-( hazmat do you have control over jujucharms.com?  Can you set up a cert and give us https access?
[16:57] <bcsaller> gary_poster: woot :)
[16:58] <gary_poster> bcsaller, reminder to please make the bug/card to fix the initial prod test run, or ask me to (happy to)  :-)
[16:59] <gary_poster> teknico, https://codereview.appspot.com/6977043/#msg5 has Francesco's charm debug notes.  They are very good.
[17:00] <teknico> gary_poster, yes, I read that email and saved it for future reference :-)
[17:00] <gary_poster> :-)
[17:00] <teknico> gary_poster, at first sight it did not help with my problem though, I'll have another look
[17:01] <gary_poster> teknico, pair for a few minutes?
[17:01] <gary_poster> up to you, only if you want to
[17:01] <hazmat> gary_poster, i do .. what do you need?
[17:01] <teknico> gary_poster, sure
[17:01] <hazmat> gary_poster, i'm  a little confused
[17:01] <hazmat> gary_poster, g+ for  a few minutes ;-)
[17:01] <gary_poster> hazmat, GUI over https needs to talk to jujucharms
[17:01] <gary_poster> ok :-)
[17:01] <hazmat> hmm
[17:02] <hazmat> it would be good to do so.. yes
[17:02] <hazmat> but required.. not sure..
[17:02] <hazmat> does the browser toss up any thing for async ajax request
[17:02] <hazmat> if its not https from an https page?
[17:02] <hazmat> well not required atm is the questoin
[17:02] <gary_poster> don't think so, in Chrome anyway.  frankban, ^^ ?
[17:03] <hazmat> if not then its more a pending task that we can toss in the kanban .. just trying to determine immediacy of action
[17:03] <gary_poster> I mean, I think it fails silently.  frankban has immediate experience
[17:03] <hazmat> hmm.. i guess the websocket is a subresource that fails .. so its similiar
[17:04] <gary_poster> right
[17:04] <hazmat> but thats still a bit different since that what's we wanted encrypted
[17:04] <frankban> hazmat: each request to connect to jujucharms is blocked by the browser, including charm info (e.g. one of the service detail tabs).
[17:04] <gary_poster> frankban, silently blocked, yeah? in chrome?
[17:05] <gary_poster> I see silent blocks in chrome, generally, and warnings you can bypass in FF
[17:05] <hazmat> the issue with the websocket was its encrypted but with an non user auth'd cert
[17:05] <hazmat> hmm
[17:05] <frankban> gary_poster: in chrome yes, errors can be seen only in the js console
[17:05] <hazmat> frankban, what's the error msg in the console?
[17:06] <frankban> hazmat: similar to this one, but pointing to jujucharms.com: http://pastebin.ubuntu.com/1452506/
[17:06] <hazmat> we're sending cors headers but their use case is the reverse..
[17:07] <hazmat> frankban, gotcha
[17:07] <hazmat> ok so its immediate. checking cert prices
[17:09] <frankban> gary_poster: commented the code enabling TLS in the charm, last test run and then I'll land the branch
[17:09] <gary_poster> thanks frankban
[17:18] <teknico> gary_poster, progress! I see machines running already :-)
[17:18] <gary_poster> teknico, excellent :-)
[17:46] <gary_poster> frankban, do you have a plan for attacking the gui https bits we talked about?I might be able to push it forward after your EoD if you do.  If not, no worries
[17:48] <frankban> gary_poster: I think a plan could be to found a way to configure the YUI loader so that it never tries to download dependencies from the outside world
[17:48] <frankban> s/to found/to find/
[17:48] <gary_poster> frankban, right.  That's what thiago tried at one point.  That's probably the thing to try first
[17:53] <bac> bcsaller i started reading your code to understand what you did and then ended up doing a review.
[17:53] <bcsaller> bac: thanks, its submitted, but I can make changes in the next branch if need be
[17:53]  * gary_poster restarts then lunches
[17:53] <bac> bcsaller: ok, that's be good
[17:56] <goodspud> Happy Yule Time Hugs everyone. Enjoy your holidays. I'm out of here.
[18:45] <gary_poster> benji, when you have a quick sec to explain/remind what the expected release pattern is, please lemme know
[19:04] <frankban> gary_poster: the branch finally landed \o/ . It seems to me that some modules (like gallery-ellipsis or gallery-timer) are not included just because they cannot be found under node_modules/yui.
[19:04] <gary_poster> yay frankban
[19:04] <gary_poster> hm
[19:05] <gary_poster> frankban, so they are not in the compressed file either
[19:05] <gary_poster> so perhaps we just copy them over and serve them
[19:05] <gary_poster> I'll try that :-)
[19:05] <gary_poster> if I have time
[19:06] <gary_poster> thanks and have a good evening frankban
[19:07] <frankban> gary_poster: it seems so (they are not in all-yui.js). you too
[19:19] <benji> gary_poster: I am back from lunch and available at any time.
[19:21] <gary_poster> thanks benji.  ony 9 min till next call, so maybe later :-)
[19:21] <benji> gary_poster: k
[20:26] <gary_poster> bcsaller, ping
[20:27] <bcsaller> gary_poster: hey, whats up?
[20:28] <gary_poster> hey bcsaller.  I am doing exploration on the https issues and messing around with things.  modules-debug.js gives this warning, which I vaguely recall:
[20:28] <gary_poster> / The "requires" property should not be used here because the javascript
[20:28] <gary_poster> / minimizer will not parse it.
[20:29] <gary_poster> juju-topology requires files here, and then dupes those in its own definition
[20:29] <gary_poster> Is it OK with you to rip out the ones in modules-debug, since AFAICT they are a dupe, and can't be used?
[20:29] <gary_poster> (when compressed)
[20:31] <bcsaller> gary_poster: yeah
[20:31] <gary_poster> cool thanks bcsaller
[20:31] <bcsaller> thank you
[23:52]  * hazmat gary_poster fingers crossed
[23:52] <hazmat> whhops
[23:52] <hazmat> happy holidays folks