[00:23] <mup> PR snapd#4471 closed: cmd/snap-update-ns: refactor and improve Change.Perform to handle EROFS <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4471>
[00:32] <mup> PR snapcraft#1897 closed: docker: user proper tags in Readme.md <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1897>
[00:50] <mup> PR snapcraft#1898 opened: docker: don't rely on snapcraft-classic <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/1898>
[00:53] <zyga> kyrofa: the fixes are merged, please try edge and report any weird stuff
[00:53] <zyga> kyrofa: rc2 tomorrow
[00:53] <zyga> kyrofa: (early morning)
[00:53] <zyga> so you can be on beta to see it
[00:57] <mup> PR snapd#4561 closed: tests: generic detection of gadget and kernel snaps <Created by plars> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4561>
[00:58] <kyrofa> zyga, you got it, thanks man :)
[00:59] <kyrofa> Yeah looks like RC1 now, when I see RC2 I'll give it a shot
[01:04] <zyga> kyrofa: tomorrow morning
[01:04] <zyga> I'm baby sitting the last PR
[01:05] <mup> PR snapd#4559 closed: snap-confine/nvidia: Support legacy biarch trees for GLVND systems <Created by ikeydoherty> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4559>
[01:49] <mup> PR snapd#4342 closed: userd: add support for a simple UI that can be used from userd <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4342>
[01:52] <mwhudson> i wonder what's going on here https://launchpadlibrarian.net/355232767/buildlog_snap_ubuntu_xenial_armhf_go-tip_BUILDING.txt.gz
[01:52] <mwhudson> i bet it's made an arm64 binary for some reason
[02:00] <zyga> mwhudson: hey
[02:00] <mup> PR snapcraft#1898 closed: docker: don't rely on snapcraft-classic <bug> <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1898>
[02:00] <mwhudson> zyga: hello
[02:00] <zyga> exec format error, never saw that one
[02:00] <zyga> yeah, feels like wrong arch
[02:00] <zyga> (but how?)
[02:00] <mwhudson> no idea
[02:00] <zyga> mwhudson: offtopic, can you please look at https://bugs.launchpad.net/snapd/+bug/1745584 - maybe it's just a missing policykit file in packaging?
[02:00] <mup> Bug #1745584: pkexec dialog doesn't appear for 'snap install' on Debian <snapd:New> <https://launchpad.net/bugs/1745584>
[02:01]  * zyga should go to sleep
[02:02] <mwhudson> zyga: mmm could be
[02:02] <Son_Goku> mwhudson, i dunno, it doesn't work in centos even with the polkit file installed
[02:03] <mwhudson> yeah, looks like the polkit file is installed in debian too
[02:03] <mwhudson> data/polkit/io.snapcraft.snapd.policy /usr/share/polkit-1/actions/
[02:03] <Son_Goku> same goes for Fedora
[02:03] <Son_Goku> I've been installing it for a while, no effect
[02:04] <Son_Goku> mwhudson: wait, this bug is about "snap install"?
[02:04] <Son_Goku> snap install doesn't query polkit at all
[02:04] <Son_Goku> like, zilch
[02:04] <Son_Goku> only GNOME Software does
[02:04] <Son_Goku> if that's supposed to work with "snap install" too, then this is horrifically broken
[02:07] <kyrofa> Hey tyhicks, if you're around, what is the status of using errno instead of kill for seccomp denials?
[02:07] <Son_Goku> mwhudson: https://src.fedoraproject.org/rpms/snapd/c/98b119302ae0d8d502f20877e0ecbf76a64ac1c9
[02:07] <Son_Goku> yeah, I've been installing it and it doesn't have effect :/
[02:09] <tyhicks> kyrofa: hey - it sounds like it is stuck waiting for a libseccomp-golang release and for other distros to include that release :(
[02:09] <tyhicks> kyrofa: https://github.com/snapcore/snapd/pull/3998/#issuecomment-358028579
[02:10] <mup> PR #3998: snap-confine, snap-seccomp: utilize new seccomp logging features <Decaying> <Created by tyhicks> <https://github.com/snapcore/snapd/pull/3998>
[02:10] <tyhicks> kyrofa: I haven't had a chance to look into falling back to KILL if the available libseccomp-golang isn't new enough
[02:10] <tyhicks> all underlying work upstream and in Ubuntu is done
[02:11] <kyrofa> tyhicks, excellent, thank you very much :)
[02:11] <tyhicks> no problem
[02:12] <tyhicks> I wish it was already working but there were a lot of moving parts
[02:12] <kyrofa> Oh totally, glad to see it moving along though
[02:13] <kyrofa> We were just chatting about it at the sprint and none of us knew where the work stood. So now we do!
[02:22] <Son_Goku> kyrofa: either you or zyga could poke the maintainers of libseccomp and golang-github-seccomp-libseccomp-golang about backporting these things to current Fedora releases if it's ready to go
[02:22] <Son_Goku> (since both of you have FAS accounts, you're also able to do PRs against the packaging repos for both of these
[02:22] <Son_Goku> )
[03:00] <mup> PR snapcraft#1899 opened: elf: readelf dependency <bug> <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1899>
[06:15] <mborzecki> morning
[06:52] <Chipaca> mborzecki: morning
[06:52] <mborzecki> Chipaca: hey
[07:57] <mborzecki> Chipaca: sorry :)
[07:59] <zyga> o/
[07:59] <zyga> drat
[07:59] <zyga> I wanted to sleep
[08:00] <Chipaca> mborzecki: :-)
[08:00] <mborzecki> Chipaca: fwiw will looking at ProcessState be enough?
[08:00] <zyga> last night tests were utterly broken on networking
[08:01] <zyga> let's see how if today they fare better
[08:01] <Chipaca> mborzecki: not really, i think using a flag variable is the only way
[08:02] <Chipaca> mborzecki: the command just knows it was killed, not by whom
[08:02] <mborzecki> Chipaca: right
[08:02] <mborzecki> Chipaca: otoh maybe it's not worth it, unless the caller does something silly with the error the way it's now should be fine
[08:03]  * zyga has zero PRs open, that's ... new
[08:04] <Chipaca> mborzecki: that was what I thought when I wrote it, but then I thought maybe we want to behave differently if the Run error is context.Canceled
[08:04] <mborzecki> Chipaca: imo adding a comment instead of a flag will be ok too :)
[08:04] <pstolowski> good morning
[08:04] <zyga> hey paweł!
[08:04] <mborzecki> zyga: pstolowski: morning
[08:05] <doko> https://launchpad.net/ubuntu/+source/snapd/2.30+18.04 ftbfs on most archs
[08:08] <Chipaca> mborzecki: it'd look like https://pastebin.ubuntu.com/26493696/
[08:08] <zyga> doko: thank you for the heads up, we'll look into it
[08:11] <kalikiana> mornin'
[08:11] <zyga> hey kalikiana
[08:12] <doko> zyga: now given back. but seriously, hit the uploader for each day and one arch that this wasn't given back ...
[08:17] <mborzecki> Chipaca: right, so there's still a race but at least you'll get ctx.Err() if cancel was called or timeout was hit
[08:18] <Chipaca> mborzecki: I _could_ check that if the flag is set, the exec error looks like a 'killed' error
[08:18]  * Chipaca bbiab
[09:00] <mup> PR snapd#4570 opened: release: snapd 2.31~rc2 <Created by mvo5> <https://github.com/snapcore/snapd/pull/4570>
[09:40]  * Chipaca grins as he writes TestRunRace
[09:41] <pedronis> mvo: Chipaca: hi, what's the status of #4459
[09:41] <mup> PR #4459: snap: add support for `snap advise-snap pkgName` <Created by mvo5> <https://github.com/snapcore/snapd/pull/4459>
[09:41] <Chipaca> pedronis: what do you mean?
[09:42]  * Chipaca looks
[09:42] <pedronis> it seems to be sitting there
[09:42] <pedronis> since a while
[09:42] <pedronis> but is not blocked
[09:42] <Chipaca> huh, i thought this was merged
[09:42] <pedronis> see
[09:43] <Chipaca> pedronis: the status is it only has one +1
[09:43] <mvo> Chipaca, pedronis I think it should get a ack/nack from gustavo
[09:43] <Chipaca> i guess :-)
[09:43] <pedronis> mvo: it was not marked as such though
[09:43] <pedronis> I suppose I cand do that
[09:44] <mvo> Chipaca, pedronis it might be considered as redundant functionality. thanks, if you mark it that would be great, otherwise I will do it
[09:44] <pedronis> mvo: I requested a Gustavo reivew on it
[09:44] <Chipaca> mvo: redundant with what?
[09:44] <pedronis> probably needs a poke also
[09:46] <mvo> Chipaca: redundant with snap advice-snap --comand
[09:47] <mvo> Chipaca: oh, hold on a sec
[09:47] <mvo> Chipaca: I'm looking at the wrong PR, I think this one is uncontroversial mostly
[09:47] <pedronis> heh
[09:47] <pedronis> too many PRs
[09:47] <mvo> sorry, I was looking at the `snap run` one that advises on available commands
[09:47] <mvo> pedronis: yes :(
[09:48] <pedronis> mvo: I still recommend(very gently) trying to be a bit more agressive about closing PRs, otherwise it gets confusing
[09:48] <mvo> pedronis: agreed, let me start right now!
[09:49] <pedronis> close as in get merged or close as in close, whatever makes sense
[09:49] <mup> PR snapd#4424 closed: corecfg: pam_env can only handle 1024 byte <Blocked> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/4424>
[09:49] <pedronis> to be clear
[09:50] <mvo> :+1:
[09:50]  * Chipaca hugs mvo
[09:50] <mup> PR snapd#4477 closed: snapenv: add SNAP_ARCH_TRIPLET <Blocked> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/4477>
[09:52] <zyga> o.
[09:53] <zyga> (which is like o/ but with me being more sleepy)
[09:53] <zyga> mvo: so I woke up at 7 ... and ... yeah
[09:53] <zyga> man
[09:53] <mvo> 4521 needs a second review probably an easy win
[09:53] <Chipaca> zyga: I woke at 4
[09:53] <Chipaca> zyga: neener neener
[09:53] <mvo> zyga: good morning (and you looked at this already)
[09:53] <mvo> zyga: good morning
[09:53] <zyga> haha :)
[09:53] <mvo> zyga: rc2 is branched and uploaded to the ppa, waiting for the build
[09:53] <Chipaca> that's what peeking into scary finances does to you
[09:54] <zyga> excellent
[09:54] <mvo> I wonder if openoffice is building right now, build slots are in short supply it seems :/
[09:54] <zyga> Chipaca: I was merging things at 3am
[09:54] <mvo> Chipaca: :( that sounds scary
[09:55] <Chipaca> zyga: i saw you restarting things at my 1am, so yeah :-)
[09:55] <zyga> Chipaca: yeah, travis and spread didn't love each other last night
[09:56] <mvo> very ironc that 2.31~rc2 is only build on powerpc yet (which used to be one of the slowest arches)
[09:56] <zyga> ;D
[09:56] <Chipaca> mvo: no spectre for ppc
[09:56] <mvo> heh, yeah
[09:56] <mvo> i was wondering if it is build on a 32bit chroot on ppc64el or something, that would also explain it
[09:56] <mvo> anyway
[09:57] <zyga> mvo: someone just pressed the "turbo" button
[09:58] <mvo> haha
[09:59]  * zyga remebmers his 386 now
[10:01]  * Chipaca -> physio
[10:01] <mwhudson> mvo: yes, pretty sure powerpc builds in a chroot on a 64 bit box now
[10:01] <mvo> ha!
[10:01] <mvo> thanks mwhudson
[10:03] <mwhudson> Kernel version: Linux bos02-powerpc-008 4.4.0-103-powerpc64-smp #126-Ubuntu SMP Mon Dec 4 16:57:45 UTC 2017 ppc64
[10:03] <mup> PR #126: Ensure squashfs snaps keep all uid/gid and permissions on build <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/126>
[10:04] <ogra_> ogra@localhost:~$ htop
[10:04] <ogra_> snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks
[10:04] <ogra_> hmm
[10:04]  * ogra_ reboots the board
[10:04] <zyga> hmmm?
[10:05] <ogra_> edge ... not sure if i tinkered the istall to death here or if there is actually a prob in the core snap from tonight
[10:05] <zyga> ogra_: let me know if it happens, I can look at my boards
[10:05] <mvo> Chipaca: hm, silly question. when we run command-not-found (snap advise-snap --command echo) - should we return test-snapd-tools because we have echo in there as a command? even though its not a toplevel?
[10:07] <zyga> mvo: btw, doko said that snapd 2.30 builds are failing
[10:07] <zyga> 09:05 < doko> https://launchpad.net/ubuntu/+source/snapd/2.30+18.04 ftbfs on
[10:07] <zyga>               most archs
[10:07] <mvo> zyga: checking
[10:08] <Chipaca> mvo: no, i don't think so, not unless it's got an alias
[10:08] <mvo> zyga: fwiw https://launchpad.net/ubuntu/+source/snapd/2.30+18.04 is all green afaict
[10:09] <zyga> indeed
[10:09] <zyga> no idea, not very helpful today
[10:09] <zyga> (yet)
[10:10] <doko> mvo, zyga: yes, given back.  you should not upload and run away, but read your build failure messages
[10:11] <doko> but maybe snaps don't have those anymore ...
[10:12]  * mvo wonders why he did not get those
[10:12] <Chipaca> mborzecki: pushed a tweak to RunWithContext, including a test for the race
[10:13] <Chipaca> and now yes, to physio
[10:15] <mborzecki> Chipaca: thanks, will take a look
[10:17] <mup> PR snapd#4571 opened: data, cmd, packaging: use autotools to generate artifacts under data <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4571>
[10:17] <mborzecki> zyga: ^^
[10:17] <ogra_> zyga, i had temporary disabled the apparmor init script on that device (because apparmor stalls the boot for ~1min), apparently snapd doesnt create the snap-confine (i think on core it simply should do that)
[10:17] <ogra_> *doesnt create the profile for ...
[10:18] <ogra_> that actually seems the only thing this init script is needed for
[10:19] <zyga> ogra_: it does and that thing you disabled loads it
[10:20] <ogra_> zyga, well, it seems to be the only profile this is needed for ... IMHO snapd could simply invoke the parser directly on core installs
[10:21] <ogra_> core does not have any other profiles outside of snap apps ... where snapd already takes care correctly
[10:21] <zyga> ogra_: it has to be done on boot
[10:21] <zyga> ogra_: by that script
[10:21] <zyga> that script compiles and loads all the profiles (including snapd generated ones)
[10:21] <ogra_> i understand that it has to be done o boot for classic installs ...
[10:21] <zyga> no
[10:21] <zyga> on all installs
[10:22] <zyga> I mean, snapd doesn't handle that at all
[10:22] <ogra_> but on core there is only one profile that gets generated
[10:22] <ogra_> which is the snap-confine one
[10:22] <zyga> no, all the per-snap profiles are handled by that guy
[10:22] <zyga> we could remove it but it's ... already doing it
[10:22] <ogra_> hmm, i dont see it doig that
[10:22] <zyga> and there's no clear reason why that would help
[10:22] <zyga> (look at /var/lib/snapd/apparmor
[10:22] <zyga> that's also loaded by the script
[10:23] <ogra_> well, the profiles are generated during snap install
[10:23] <ogra_> just not for snap-confine
[10:23] <zyga> yes but on reboot they are not loaded
[10:23] <zyga> ogra_: I'm telling you the script does useful work on boot, if we drop that script we have to put some thing on early boot, before _any_ snap can start
[10:24] <zyga> ogra_: I'm not sure that should be snapd; it could be but I don't see a clear advantage
[10:24] <zyga> ogra_: not on boot speed for sure
[10:24] <ogra_> well, thats different to what i see :) but i belive you :)
[10:24] <zyga> ogra_: there's a variable somewhere that makes it look at /var/lib/snapd/apparmor/profiles
[10:24] <zyga> ogra_: we also load profiles on startup if they _changed_
[10:24] <ogra_> (all snaps functioned fine for the last week while the script was off ... only a core refresh made snap-confine fail then)
[10:25] <ogra_> ... but probably the profiles simply never changed in that time despite me randomly installing/removing7refreshing apps
[10:26] <ogra_> anyway, re-enabling the script gets me 3min boots back but also makes snap-confine work again ... so its a user error
[10:26] <zyga> ogra_: how slow is it btw?
[10:26] <cjwatson> Chipaca: ppc does suffer from Spectre, FWIW (maybe not the actual 32-bit-only chips, I'm not sure, but certainly more modern ones)
[10:26] <zyga> maybe there is something wrong?
[10:26] <zyga> cjwatson: hey, I still _run_ one :)
[10:26] <ogra_> zyga, lol ... yes ... thats what i'm trying to find :P
[10:27] <zyga> ogra_: maybe add a echo to the script (or something like that)
[10:27] <zyga> ogra_: so that we know when it starts and when it stops
[10:27] <zyga> ogra_: not sure if that's clearly readable from logs
[10:27] <ogra_> (it is a 200-500MHz 256M ram board ... but 3mins are definitely to long even for that)
[10:27] <zyga> ogra_: so, there's a cache thing there but maybe it's broken and not used
[10:27] <ogra_> systemd-analyze is usually pretty correct in its timings
[10:27] <zyga> ogra_: normally apparmor should read the profile, check with the cache and insert a cached compiled blob if one is recent
[10:28] <ogra_> yeah, the cache is definitely empty on all my boards
[10:28] <zyga> ogra_: otherwise it would compile the profile, which is slow, save the cache and load it in the kernel
[10:28] <ogra_> jamie pointed that out before
[10:28] <zyga> ogra_: not sure how much of that is done in intrd
[10:28] <zyga> ogra_: and how much in early systemd
[10:28] <ogra_> (seems there is some general issue with the cache )
[10:28] <zyga> ogra_: oh?
[10:28] <ogra_> initrd doesnt do any apparmor stuff
[10:28] <ogra_> only the mounting
[10:28] <zyga> there are two cache locations
[10:28] <zyga> for some historic reason AFAIR
[10:28] <zyga> did you check both?
[10:28] <ogra_> well, jamie pointed me to /etc
[10:29] <zyga> look at /var/cache/apparmor
[10:29] <ogra_> and that one is definitely empty on all boards i have
[10:29] <ogra_> yeah, there are files
[10:29] <zyga> see if it makes any difference
[10:29] <zyga> even with a hand watch
[10:29] <zyga> if you remove them
[10:29] <zyga> if so then the cache works
[10:29] <zyga> if not ... well, slow boards are slow
[10:29] <ogra_> well
[10:30] <ogra_> snapd probing mmcblk1rpmb devces for assertions takes quite some time too ;)
[10:30] <ogra_> there are some obvious issues (like this one) ... but they are not enough to get me to a sane boot speed yet
[10:30] <zyga> how much?
[10:31] <ogra_> dunno, several tens of seconds
[10:31] <ogra_> 15-20 i'D say ... thats sadly a service that doesnt log anything ...
[10:31] <zyga> is that blocking boot or does it happen in parallle?
[10:31] <zyga> *parallel
[10:31] <ogra_> (i havent debugged that one yet, its an obvious one)
[10:32] <ogra_> others are 30sec for mounting loop devices
[10:32] <ogra_> thats more worrying
[10:32] <ogra_> console-setup 20sec ... keyboard-setup 15sec ...
[10:33] <ogra_> the device probing is blocking boot
[10:34] <mvo> ogra_: could you run systemd-analyize plot and copy the output somewhere?
[10:35] <ogra_> well, the system is havily modified atm ... i'll do that once i flashed it freshly ... here is a top list of blame though https://paste.ubuntu.com/26494246/
[10:35] <zyga> ogra_: the probing issue
[10:35] <zyga> ogra_: I honestly think it should not be a toggle
[10:35] <zyga> ogra_: but there should be a way to tweak this in the gadget
[10:35] <ogra_> zyga, ?
[10:36] <zyga> ogra_: so that you can use udev tagging to blacklist media
[10:36] <ogra_> ah
[10:36] <ogra_> yeah
[10:36] <zyga> ogra_: so that certain internal devices are just skipped
[10:36] <zyga> ogra_: it's a simple system, extensible to devices and makes sense as a design IMO
[10:36] <ogra_> well, you never ever want to probe mmcblkXrpmb or mmcblkXbootX
[10:37] <zyga> ogra_: I don't think that's true, that's absolute and those rarely turn out true
[10:37] <ogra_> but thats also something systemd needs to learn, not only snapd
[10:37] <mvo> ogra_: thanks, the plot would be nice at some point but not urgent
[10:37] <mup> PR snapd#4572 opened: mir: software clients need access to shared memory /dev/shm/#* <Created by gerboland> <https://github.com/snapcore/snapd/pull/4572>
[10:37] <zyga> ogra_: as long as you can set an attribute that makes it skip probing and you can express that in the gadget it feels sufficient
[10:38] <ogra_> zyga, right ... systemd doesnt have such a flag yet ... which is why i ignored that bit for now for snapd as well
[10:38] <ogra_> i'll get to that later ...
[10:38] <ogra_> thats one of the bits that are understood :)
[10:38] <zyga> ogra_: it's not a systemd flag
[10:38] <zyga> ogra_: it's an udev attribute
[10:38] <ogra_> (i have many in this particular boot process that arent :) )
[10:38] <zyga> ogra_: like MM_SKIP_PROBING (or whatever it was called)
[10:41] <ogra_> zyga, hmm, i only know UDISKS_IGNORE ... but that wouldnt help with systemd fsck or snapd autoimport
[10:41] <zyga> ogra_: fsck I cannot speak of, those are separate issues
[10:41] <zyga> ogra_: but the job that tries to look for assertions is under our control
[10:41] <zyga> ogra_: so it could just skip devics with a given attribute
[10:43] <ogra_> zyga, would be helpful if the autoimport udev rule could mention the variable in the comment somehow ... how would porters know about it ?
[10:44] <ogra_> (without reading snapd's source)
[10:44] <zyga> ogra_: sure that's documentation; I'm describing a feature that doesn't exist
[10:44] <ogra_> oh
[10:44] <zyga> ogra_: it's just something that we would doucment in device maker's book or similar
[10:45] <ogra_> i thought you said there is "MM_SKIP_PROBING"
[10:45] <zyga> ogra_: I'm saying that such an attribute, IMO, makes more sense than a big bool flag for _users_
[10:45] <ogra_> well
[10:45] <zyga> ogra_: that was a reference to existing similar attribute for modem manager and serial ports
[10:45] <ogra_> that flag will only make the udev rule skip
[10:45] <ogra_> it wont prevent the unit fro running
[10:45] <ogra_> *from
[10:46] <zyga> yes but we could make that unit run the prober with a device, so that control is reversed
[10:46] <zyga> systemd picks the devices, prober probes one
[10:46] <ogra_> most customers i worked with til now want that stuff completely off so people cant tinker with USB sticks
[10:46] <zyga> those could then even run faster as they would happen in parllel
[10:46] <zyga> ogra_: that's okay, but it should be a gadget decision, not a toggle for users
[10:46] <ogra_> it simply wastes cycles, even if it is a no-op
[10:47] <ogra_> yeah
[10:47] <ogra_> indeed it should be a gadget thing
[10:47] <ogra_> (like rsyslog or disabling ssh access)
[10:49] <ogra_> though here the issue is more of a subsequent thing ... i want the deices to be hidden completely during boot so fsck will ignore them too ...
[10:50] <ogra_> (autoimport is just the next thing in the chain here ... )
[10:57]  * zyga -> physical activities
[10:57] <zyga> ogra_: I'm so mentally tired I will do some house chores to vent my mind
[10:57] <zyga> ogra_: I agree on fsck
[10:58] <zyga> ogra_: though I would discuss it separately
[11:07] <mvo> cachio: good morning! 2.31~rc2 for armhf/arm64 is ready, the other ones are still building
[11:11] <cachio> mvo, good morning, already downloading images
[11:11] <mvo> cachio: great, I publish the other ones as soon as I can
[11:11] <cachio> mvo, great
[11:17]  * zyga hopes for one smooth release
[11:17] <mvo> 2.30 was not too bad
[11:18] <zyga> mvo: going out with rc2 would be awesome :)
[11:19] <mvo> cachio: i386/amd64 ready now as well
[11:25]  * zyga refreshes to beta
[11:25] <zyga> mvo: oh
[11:25] <zyga> mvo: we didn't do one thing
[11:26] <zyga> that piece of code that wrote the snap.mount unit (under proper name
[11:26] <zyga> we don't have that
[11:26] <zyga> for reexec
[11:26] <zyga> but I guess it's okay for now, as long as packages are coming out, not a regression in any way
[11:27] <mvo> zyga: yeah, it will only be fixed in lxd hosts with the right snapd version
[11:27] <mvo> zyga: eh deb/rpm
[11:27] <mvo> zyga, pstolowski there is a bugreport that we should document that hooks use dash - I wonder if we should just switch them to bash. wdyt?
[11:28] <ogra_> oh, please dont
[11:28] <mvo> pstolowski: do you think you could check 1745015?
[11:28] <mvo> ogra_: why not?
[11:28] <ogra_> (dealing with a 200MHz 256M single core device here ... such a switch would have some impact)
[11:28] <zyga> mvo: is there any mandate for the hooks to be anything? they are just executables, could be dash, python or elf
[11:29] <ogra_> bash eats about 5Mb while dash lives in the kilobyte range
[11:29] <ogra_> (and used to be massively slower as well, back when debian did the research ... that might have changed since 2007 though)
[11:30] <mvo> zyga: there is no mandate for this
[11:30] <ogra_> mvo, assuming you dont mean live-build hooks here but app hooks
[11:31] <pstolowski> mvo, interesting. will look into 1745015
[11:31] <mvo> ogra_: snap hooks, yes. well, fair enough.
[11:31] <ogra_> mvo, most upcoming ubuntu core customers in the near future will be in a similar HW range, every byte of ram counts here
[11:32] <pstolowski> mvo, I agree with zyga; i think documenting is enough
[11:32] <mvo> pstolowski: ok
[11:32] <ogra_> (and on single core-low-speed cpus also every herz :) )
[11:32] <ogra_> s/herz/hertz/
[11:39] <ogra_> mvo, oh, during my debugging i noticed that "systemctl list-dependencies" on core devices shows quite a bunch of red dots, i wonder if we need to handle some units more gracefully or need to disable them
[11:40] <ogra_> i.e. "systemd-machine-id-commit.service" ... completely useless since we set the machine-id from the initrd ... but it gets run nontheless
[11:41] <ogra_> or systemd-hwdb-update.service ... (the hwdb is readonly)
[11:41] <cjwatson> mvo: I think the thing that bug reporter is missing is that /bin/sh is the default in normal Ubuntu too
[11:41] <cjwatson> mvo: err /bin/sh -> dash
[11:42] <cjwatson> they've obviously just configured it differently
[11:46] <Chipaca> cjwatson: wrt spectre on ppc, I was thinking exclusively of the pre-2006 chips (have there been 32-bit ppc chips since then?)
[11:47] <Chipaca> also I thought powerpc meant 32 bits, and the newer ones were ppc64le or w/e
[11:48] <cjwatson> yeah but you said ppc which is a bit ambiguous
[11:49] <Chipaca> ah, my bad then (i meant powerpc i think)
[11:49] <Chipaca> in my defence my only powerpc machine was a nubus-ppc one
[11:49] <cjwatson> there've certainly been embedded 32-bit chips since then, and e.g. the e600 has out-of-order execution, branch prediction, and such; wouldn't surprise me if you could get something like Spectre to work but I don't know if anyone's bothered
[11:51]  * zyga starts to see the light at the end of the tunnel :)
[11:52] <zyga> my office gets messy quickly
[11:52] <Chipaca> somebody's got to be trying to get spectre to work on a router
[11:52] <Chipaca> mborzecki: you around?
[11:53] <mborzecki> Chipaca: yeah, trying to go through #4551
[11:53] <mup> PR #4551: ifacestate: do not auto-connect manually disconnected interfaces <Created by stolowski> <https://github.com/snapcore/snapd/pull/4551>
[11:53] <Chipaca> mborzecki: just a quick Q: your version of the if in #4569 implies two class assertions, right?
[11:53] <mup> PR #4569: osutil: add ContextWriter and RunWithContext helpers <Created by chipaca> <https://github.com/snapcore/snapd/pull/4569>
[11:54] <mborzecki> Chipaca: sadly yes
[11:54] <Chipaca> ie one to get a ExitError, one to get a WaitStatus; that's why you said more verbose
[11:54] <Chipaca> mborzecki: fair enough. I'll rewrite it that way. i had it like that (except I didn't know about Signal() which makes it more readable, and probably worthwhile)
[11:55] <mborzecki> Chipaca: didn't know about it either, actually read through the exec code in stdlib :)
[11:55] <pstolowski> mborzecki, thanks!
[12:02] <mup> PR snapd#4557 closed: osutil: add DirExists and IsDirNotExist <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/4557>
[12:05] <zyga> ok, one last power strip
[12:05] <zyga> and I should be ready
[12:08] <niemeyer> Hey hey
[12:09]  * ogra_ puts a dollar in zyga's waistband for that power strip ...
[12:09] <Chipaca> ogra_: I did _not_ need that image
[12:10] <ogra_> lol
[12:10]  * zyga googles waistband
[12:10] <zyga> oho
[12:10] <zyga> *gulp*
[12:11]  * zyga hugs ogra_ and Chipaca *together*
[12:11] <ogra_> no, no ... we didnt order that lapdance !!!s
[12:11]  * Chipaca steals the dollar and goes to get lunch
[12:12] <zyga> the dollar is actually a beer bottle cap
[12:22]  * zyga looks at unit tests again
[12:32] <Chipaca> zyga: guess lunch is roaches then
[12:32] <zyga> Chipaca: fry slowly
[12:33]  * Chipaca squints at Failed tasks: 1
[12:33] <Chipaca>     - linode:ubuntu-14.04-64:tests/main/server-snap:pythonServer
[12:34] <zyga> what's the failure?
[12:45] <ogra_> oh
[12:45] <ogra_> is bpf a hard kernel requirement nowadays ?
[12:48] <zyga> ogra_: yes, I think so
[12:49] <ogra_> aha
[12:49] <ogra_> ppisati, seems our default configs in the sample kernels do not enforce bpf ^^^
[12:50] <mup> PR snapd#4573 opened: tests: enable content sharing test for $SNAP <Created by zyga> <https://github.com/snapcore/snapd/pull/4573>
[12:53] <zyga> mvo: if this passes please drop it into final release
[12:54] <zyga> I forgot about it yesterday
[12:54]  * zyga is very excited about content sharing getting a huge boost in 2.31
[12:54] <zyga> but first let's drop those unit tests :)
[12:57] <mvo> zyga: which one, 4573?
[12:57] <zyga> yep
[12:57] <zyga> it just enables a test that I wrote ahead of time
[12:57] <zyga> and rigged to skip one case
[12:57] <zyga> now it should all pass
[12:59] <mup> PR snapd#4570 closed: release: snapd 2.31~rc2 <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4570>
[13:02] <mup> PR snapd#4569 closed: osutil: add ContextWriter and RunWithContext helpers <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/4569>
[13:21] <ppisati> ogra_: i'm going to add it to the list of configs in the snapcraft/kernel_plugin
[13:24] <zyga> mvo: please merge https://github.com/snapcore/snapd/pull/4573
[13:24] <mup> PR #4573: tests: enable content sharing test for $SNAP <Created by zyga> <https://github.com/snapcore/snapd/pull/4573>
[13:24] <zyga> it's green now
[13:26] <ppisati> ogra_: which BPF options? i guess the BPF_SYSCALL filtering option
[13:27] <ogra_> ppisati, yeah, i guess so ... all i justz noticed is that on a misbehaving device /proc/filesystems doesnt list bpf ... mnot sure what options are exactly needed ... i know the pi kernels have all of them though
[13:28] <ppisati> ogra_: well, when you figure it out, add it to the list of required options here and send a pull req
[13:28] <ppisati> ogra_: https://github.com/snapcore/snapcraft/blob/master/snapcraft/plugins/kernel.py
[13:28] <ppisati> 'required_snappy' i guess
[13:32] <mup> PR snapcraft#1900 opened: Parent relative symlinks <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1900>
[13:51] <zyga> jjohansen: o/
[13:51] <jjohansen> hey zyga
[13:51] <zyga> jjohansen: long time no see, how are you doing
[13:51] <jjohansen> zyga: well I was doing well, but I have a feeling that is about to change
[13:51] <jjohansen> :)
[13:51] <pstolowski> mvo, so my spread test for that install hook bug just produced 'mesg: ttyname failed: Inappropriate ioctl for device' and hung; waiting to see if the hook gets aborted as it should.
[13:52] <zyga> oh? what's going on?
[13:52] <mvo> pstolowski: aha, interessting
[13:52] <jjohansen> zyga: oh I was just assuming you pinged me because you have a bug for me :)
[13:52] <zyga> ah, no :)
[13:54] <jjohansen> zyga: ah, well then I am good :D
[13:55] <mup> PR snapd#4573 closed: tests: enable content sharing test for $SNAP <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4573>
[13:55] <zyga> thank you
[13:57] <pstolowski> mvo, ok. puzzling. install hook got killed eventually, install was aborted. all as expected.
[13:58] <cachio> mvo, https://paste.ubuntu.com/26495194/
[13:58] <pstolowski> mvo, ah wait, he is not installing, he is using snap try
[13:58] <cachio> this is what Ii see in the pi21
[13:58] <cachio> mvo, there is no /snap/core/current
[13:58] <cachio> mvo, and many tests failing because of that
[13:58]  * kalikiana lunch
[13:59] <cachio> mvo, also the test-snapd-tools snap is not in /snap
[13:59] <mvo> cachio: that is strange, what does your state.json look like? i.e. python3 -m json.tool /var/lib/snapd/state.json
[13:59] <mvo> mborzecki: just to double check, the license for local snaps is displayed if these snaps have a "license:" field in their snap.yaml?
[14:00] <cachio> mvo, https://paste.ubuntu.com/26495214/
[14:03] <mvo> cachio: strange, looks like state.json and content is toally out of sync
[14:04] <mvo> cachio: I wonder if this is a fluke or if we somehow broke the testsuite
[14:04] <zyga> mvo: maybe backup/restore is messed up
[14:04] <zyga> we sometimes see that the state was modified while it was being saved
[14:04] <mvo> zyga: yeah, something along these lines
[14:04] <cachio> mvo, not sure yet, something similar is happening in dragonboard
[14:04] <cachio> pi3 is working fine
[14:04] <mvo> strange
[14:05] <zyga> it's a race
[14:05] <zyga> it doesn't matter where it failed
[14:05] <cachio> mvo, same issue with test-snapd-tools
[14:05] <mvo> Chipaca: does https://github.com/snapcore/snapd/pull/4531#pullrequestreview-92931228 capture the discussion during the standup? if so I will merge the PR and cherry-pick for 2.31
[14:05] <mup> PR #4531: cmd/snap: display snap license information <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4531>
[14:06] <mvo> cachio: and its also in the state I assume? so the same out-of-sync issue(?)
[14:06] <Chipaca> mvo: except for the very last commit, i think
[14:06] <cachio> mvo, checking
[14:06] <mborzecki> mvo: it should, there's a /v2/snaps/<name>, as long as the response contains the license it will be shown, i can try and add a quick test case for it
[14:07] <mvo> Chipaca: commit or comment?
[14:08] <mvo> mborzecki: yeah, I think if we could have a test case that would be best
[14:08] <Chipaca> mvo: commit
[14:08] <Chipaca> mvo: ie the one that removed the “license: unknown”
[14:09] <mvo> mborzecki, Chipaca: indeed, sorry for this. lets just revert 60074f0 and the following one now that we have agreement on that it should be part of the snap
[14:10] <cachio> mvo, yes
[14:11] <cachio> mvo, also I see in the syslog many of these errors ---> Jan 31 11:15:58 localhost snapd[1369]: 2018/01/31 11:15:58.355309 stateengine.go:101: state ensure error: devicemgr: snap "core" has "install-snap" change in progress
[14:11] <mborzecki> mvo: just to be clear, revert the last 2 commits right?
[14:12] <mvo> mborzecki: yes
[14:12] <mvo> mborzecki: sorry for the confusion about this one, I was under the (wrong) impression that the store should be the authority and I'm happy that its the snap
[14:12] <mborzecki> mvo: also the text that was shown there is `(undefined)`, should I change it to unknown instead?
[14:13] <mvo> mborzecki: yeah, I think "unkown" is slightly better
[14:14] <mvo> niemeyer: for unknown licenses, "license: unknown" in `snap info` output? sounds reasonable?
[14:15] <doko> mvo, zyga: snapd has autopkg test regressions
[14:17] <zyga> where can we see them?
[14:18] <mvo> zyga: I think we have this problem that the store categories changed :( so the searching test fails now
[14:23]  * ogra_ scratches head about unlogical kernel config naming
[14:23] <ogra_> # CONFIG_BPF_JIT is not set
[14:23] <ogra_> CONFIG_HAVE_BPF_JIT=y
[14:24] <ogra_> how can the second one be true if the first one is false ...
[14:24] <zyga> you have it (it's supported in arch) but not enabled
[14:24] <zyga> that's how I see it
[14:24] <ogra_> hmm
[14:24] <ogra_> so that would mean userspace you think ?
[14:25] <zyga> no, I mean the kernel has code to emit jit for bpf on this architecture (that's the HAVE part does)
[14:25] <zyga> (just guessing though)
[14:25] <ogra_> ah
[14:25] <ogra_> ok
[14:25]  * ogra_ gets it
[14:25] <zyga> but the config option to enable it is off
[14:25] <ogra_> anyway ... just curious ... i'll just enable it anyway
[14:30] <Chipaca> pstolowski: I got a panic in config, suspect I'm doing something wrong :-) do you have a moment to take a look?
[14:31] <pstolowski> Chipaca, what is it?
[14:32] <Chipaca> pstolowski: I'm doing : tr.Set(aSnap, "", aConfig)
[14:33] <Chipaca> pstolowski: and overlord/configstate/config/helpers.go:80 throws an 'index out of range'
[14:33] <niemeyer> mvo: Yeah, sounds good
[14:33] <niemeyer> mvo: I'm half-way through typing out a proposal for custom licenses too
[14:34] <mvo> mborzecki: -^ so "license: unknown" is fine, very happy that this gets pulled in :)
[14:35] <pstolowski> Chipaca, key cannot be "", I'm sure we prevent it in snap/snapctl set, but apparently not at this level
[14:35] <mborzecki> mvo: pushing update in a short while, turns out the biggest issue is forging the data that snapd returns
[14:35] <Chipaca> pstolowski: then how do I set the whole config? (because key is "" for get to get the whole config)
[14:41] <pstolowski> Chipaca, well, I've implemented "" on the get side for convienience to make it easy to discover config keys. but we don't have an equivalent for setting all at once
[14:41] <pstolowski> Chipaca, I mean - not for transaction.Set at least
[14:43] <pstolowski> Chipaca, you can of course workaround that by iterating over root elements and calling tr.Set(..) for them manually
[14:43] <Chipaca> pstolowski: that sounds very additive
[14:43] <pstolowski> Chipaca, or just make tr.Set smarter :}
[14:43] <pedronis> well you need also to remove all them
[14:44] <pedronis> which we don't quite support either
[14:44] <Chipaca> I need to set the config to the thing in the snapshot, not add to it
[14:44] <Chipaca> if the config is empty, empty it
[14:44] <pedronis> seems you need to bypass transactions
[14:44] <pedronis> or teach Set about "" or something like that
[14:44] <Chipaca> I don't mind bypassing transactions :-D
[14:45] <pedronis> replacing the whole thing is not quite the use case for transaction
[14:45] <pedronis> s
[14:45] <pedronis> then it's more  matter of not breaking too many abstractions
[14:45] <pstolowski> ah, I see, yes it's additive that way
[14:45] <pedronis> Chipaca: sounds we need configstate.Set or something
[14:46] <Chipaca> augh
[14:46] <pedronis> for your use case
[14:46] <Chipaca> I need to step away for a bit
[14:46] <pedronis> well configstate/config.Set
[14:46] <pedronis> maybe
[14:46] <pstolowski> yes, that should be very straightforward
[14:47]  * pedronis doesn't remember the how the code org looks like exactly
[14:47] <mup> PR snapcraft#1896 closed: elf: do not strip rpaths that contain $ORIGIN <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1896>
[14:47] <mvo> mborzecki: oh, a spread test is fine, just adding "license: ..:" to one of the test snaps
[14:48] <mborzecki> mvo: well, i've updated the unit tests anyway :)
[14:48] <mvo> mborzecki: .) ok
[14:49] <niemeyer> mvo, mborzecki: https://forum.snapcraft.io/t/support-for-custom-license-text/3671/16
[14:49] <niemeyer> Chipaca: ^
[15:07] <kalikiana> re
[15:12] <greyback> it possible for one snap app to call another snap app? Something like a poor-man's socket activation?
[15:13] <zyga> greyback: not without an interface
[15:14] <greyback> zyga: even inside the same snap?
[15:14] <greyback> i.e. appA & appB in the snap, I want appB to call appA
[15:15] <zyga> greyback: that's more subtle: if you want to go through the activator then you won't be able to
[15:15] <zyga> greyback: if you call the same command as that activator then sure
[15:15] <zyga> greyback: but you won't get the permissions of the other app
[15:16] <greyback> zyga: yeah, it was the permissions I was hoping to keep separate
[15:16] <greyback> so xwayland has tight security, and then my x app has more freedom
[15:17] <greyback> guess I'll give that up for now
[15:19] <zyga> 10 failures left
[15:20] <zyga> 7 failures :)
[15:22] <mup> PR snapd#4531 closed: cmd/snap: display snap license information <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4531>
[15:23] <mvo> thanks mborzecki
[15:50] <zyga> libreoffice 6.0 is out, will the snap be refreshed?
[16:04] <zyga> hhh
[16:04] <zyga> ah :)
[16:04] <zyga> man that was silly
[16:04] <zyga> 3 errors left, will be done in a moment
[16:15] <Chipaca> pstolowski: pedronis: I think I'm going to add a helper to do just this set/unset to config; should I add it to config, or to configstate?
[16:15] <Chipaca> it'll be a separate pr
[16:16] <pedronis> Chipaca: config
[16:16] <Chipaca> ok
[16:16] <Chipaca> pedronis: is config sorta-kinda the 'backend' of configstate?
[16:16] <pedronis> otherwise it cannot be used from snapstate
[16:16] <Chipaca> this is for use from snapshotstate, but ok
[16:17] <pedronis> Chipaca: no, it's mostly the accessor that can be used by any other *state
[16:17] <pstolowski> +1 (config)
[16:17] <Chipaca> k
[16:17] <pedronis> Chipaca: confistate itself imports a bunch of *state
[16:17] <pedronis> so that's why config exists
[16:17] <pedronis> otherwise circular imports
[16:18] <Chipaca> is there any reason a snapshot should save a revision-config?
[16:18] <Chipaca> the "what happens if you restore a revision that isn't current" question comes to mind
[16:18] <pedronis> those are used one revert I think
[16:18] <pedronis> no?
[16:19] <pedronis> are you snapshotting a revision? or all of them?
[16:19] <Chipaca> pedronis: a single one
[16:19] <Chipaca> the current one
[16:19] <pedronis> and you restore the current one?
[16:20] <pedronis> in that case I don't think revision-config is relevant
[16:20] <Chipaca> no, restore restores whatever was snapshot
[16:20] <pedronis> but puts it backa as current?
[16:20] <Chipaca> no
[16:20] <pedronis> then it's complicated
[16:20] <Chipaca> yes
[16:20] <pstolowski> in that case i think you should restore your snapshot into whatever is current rev
[16:20] <pedronis> you need to care about about revision-config
[16:20] <pedronis> I think
[16:20] <pstolowski> (so,just config)
[16:20] <Chipaca> maybe restore should block restore unless the revision is current
[16:21] <Chipaca> then the problem goes away :-)
[16:21] <Chipaca> at least for now
[16:22] <Chipaca> maybe in a followup it can restore to current always, but doing that to a 'live' snap makes me nervous
[16:23] <Chipaca> anyway, going with "config" for now
[16:28] <mup> PR snapd#4574 opened: tests: add integration for local snap licenses <Created by mvo5> <https://github.com/snapcore/snapd/pull/4574>
[16:37] <mup> PR snapd#4575 opened: config: add (Get|Set)SnapConfig to do bulk config e.g. from snapshots <Created by chipaca> <https://github.com/snapcore/snapd/pull/4575>
[16:37] <Chipaca> pedronis: pstolowski: ^ a quickie  (i hope)
[16:37] <pstolowski> looking
[16:39] <zyga> 2 lef
[16:39] <zyga> 2 left :)
[16:41] <Chipaca> zyga: 2 leffe?
[16:42] <zyga> Chipaca: two tests failing; almost done :)
[16:42] <zyga> 0!
[16:43] <pstolowski> Chipaca, +1
[16:44] <Chipaca> why can i edit your review summary
[16:48] <mup> PR snapd#4576 opened: cmd/snap-update-ns: large refactor / update of unit tests <Created by zyga> <https://github.com/snapcore/snapd/pull/4576>
[16:48] <zyga> big n boring
[16:48] <zyga> but had to be done
[16:48] <zyga> now I feel good about that code :)
[16:49] <zyga> I also tweaked a few strings based on one more patch I had, the error messages are nicer
[16:50] <zyga> mvo: ok, I think I can close that chapter for today, I can do code reviews or I can write about the content interface improvements
[16:50] <mup> PR snapcraft#1901 opened: elf: check if file exists before checking if ELF <bug> <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1901>
[16:51] <mvo> zyga: writing sounds good
[16:52] <zyga> mvo: okay, let's get that done :)
[16:53] <zyga> if you include that PR in ~rc3 (if there is one) that's okay but it's not mandatory, I only added a load of unit tests and tweaked some error strings
[16:53] <mvo> zyga: yeah, just looking at it
[16:57]  * zyga tries to recall why x.snapd.symlink=foo is not conveyed through Entry.Name, hmm hmm
[16:57] <zyga> maybe it would be nicer to read
[16:57] <zyga> but I did that for *some* reason, I remember that much
[16:57] <zyga> well, did it the way it is now
[16:57] <zyga> those tests took about two days to write in this final form
[17:02]  * kalikiana going to wrap up for the day
[17:02] <zyga> o/
[17:04] <zyga> Chipaca: question on 4575
[17:05] <Chipaca> zyga: or is there
[17:05] <Chipaca> zyga: (i don't see a question)
[17:05] <zyga> Chipaca: hmmmm
[17:05] <zyga> it got eaten
[17:05] <Chipaca> github is hungry today
[17:05] <ogra_> omnomnom
[17:05] <zyga> I was asking why are we returning json.RawMessage by value
[17:06] <Chipaca> zyga: it's a []byte; it's already a pointer
[17:06] <zyga> and if that is safe actually (shallow copy)
[17:06] <zyga> ah, perfect
[17:06] <zyga> thanks! LGTM
[17:06] <Chipaca> I don't know why config uses *json.RawMessage (and it might, because it does some funky stuff), but these two functions are un-funky
[17:07] <Chipaca> might need to*
[17:07] <ogra_> sigh ...
[17:08] <zyga> Chipaca: was that related to some bug in json
[17:08] <zyga> where you need the pointer to get some methods right
[17:08] <zyga> something like that echoes in my head
[17:08] <Chipaca> it might be; if it is, pedronis will know :-)
[17:08] <zyga> + snap install test-snapd-control-consumer
[17:08] <zyga> error: cannot install "test-snapd-control-consumer": cannot get nonce from
[17:08] <zyga>        store: store server returned status 418
[17:08] <zyga> 418?
[17:08] <Chipaca> aw, so close to 419
[17:08] <zyga> is that my bus home? :)
[17:09] <Chipaca> ah no
[17:09] <Chipaca> 418 is the one
[17:09] <zyga> what is it?
[17:09] <zyga> should we retry that?
[17:09] <Chipaca> 418 I'm a teapot
[17:09] <ogra_> jdstrand,  (or any other securiteer ) ... looking at different core kernels i see "bpf" in /proc/filesystems ... the kernel i'm currently working on does not show it and i cant find what Kconfig option would enable the bpf filesystem, do you happen to have any hint (google isnt helpful either)
[17:09] <Chipaca> zyga: which in our tests means it is (hopefuly!) not talking to an actual server
[17:10] <zyga> haha, cute :)
[17:10] <pedronis> it's talking to the fakestore and trying to setup a device session
[17:10] <pedronis> or something like that
[17:10] <pedronis> why is it doing that though?
[17:10] <pedronis> only now
[17:12] <zyga> it is in here https://api.travis-ci.org/v3/job/335552657/log.txt
[17:12] <zyga> in this PR https://github.com/snapcore/snapd/pull/4562
[17:12] <mup> PR #4562: debian: add a zenity|kdialog suggests <Created by mvo5> <https://github.com/snapcore/snapd/pull/4562>
[17:15] <pedronis> it is using the fakestore
[17:15] <pedronis> wondering why we never got this kind of error
[17:16] <pedronis> it's a while since the situation in which we might try to create a device session have increased
[17:28] <ogra_> mvo, hmm, did the service disabling in the core config hook regress ? (seems to not mask aymore but just disable)
[17:28] <ogra_> lrwxrwxrwx 1 root root   35 Jan 28 11:50 syslog.service -> /lib/systemd/system/rsyslog.service
[17:28] <ogra_> ogra@localhost:~$ snap get core service.rsyslog.disabled
[17:28] <ogra_> true
[17:28] <ogra_> ogra@localhost:~$ ps ax|grep syslog
[17:28] <ogra_>  2195 ?        Ssl    0:00 /usr/sbin/rsyslogd -n
[17:31] <zyga> mvo: do we need https://github.com/snapcore/snapd/pull/4562 for the final release?
[17:31] <mup> PR #4562: debian: add a zenity|kdialog suggests <Created by mvo5> <https://github.com/snapcore/snapd/pull/4562>
[17:34] <cachio_> mvo, well I discovered the problem in dradonboard and pi2
[17:34] <cachio_> mvo, old core snaps
[17:34] <cachio_> it is weird because I  created the images after the cores were uploaded to the store
[17:50]  * Chipaca afk for a while
[18:01] <mup> Bug #1746564 opened: snapd should not allow --classic installation for snaps with strict confinment mode <Snappy:New> <https://launchpad.net/bugs/1746564>
[18:11] <cachio_> mvo, this seems to be an issue
[18:11] <cachio_> https://paste.ubuntu.com/26496402/
[18:11] <cachio_> mvo, it happens in the refresh scenario
[18:11] <cachio_> when we refresh from stable (factory release)
[18:11] <cachio_> I'll debug it once the execution finishes
[18:11] <zyga> hmm
[18:11] <zyga> in test-snapd-tools expected to have a key 'license'
[18:11] <zyga> that looks like the recently added thing
[18:12] <cachio_> mvo, it failed in both 32 and 64 bits
[18:12] <zyga> yes, it's not something that's arch dependent
[18:13] <cachio_> zyga, ok, I'll take a look in that case
[18:21] <zyga> cachio_: look at the newly merged patches
[18:22] <cachio_> zyga, yes, this issue was not happening in rc1
[18:22] <cachio_> it is quite new
[18:22] <cachio_> I am debuging
[18:22] <cachio_> zyga, any idea which PR was included the code that could be causing that?
[18:33] <mvo> ogra_: hm, I remember code to mask it but I will double check in the morning
[18:33] <ogra_> cyphermox, slangasek, am i correct assuming that the only reason for not using signing for the initrd in secure boot is that we dynamically re-generate it ? or is there any grub-sided restriction as well ?
[18:34] <mup> PR snapd#4575 closed: config: add (Get|Set)SnapConfig to do bulk config e.g. from snapshots <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/4575>
[18:34] <mvo> zyga: 4562 is not super urgent, suggests are weak and in most cases where we will use the UI one of the two (zenity or kdialog) will be installed
[18:34] <slangasek> ogra_: what does signing an initrd mean to you?
[18:34] <ogra_> slangasek, well, having a signed img file
[18:34] <ogra_> and grub verifying that
[18:35] <mvo> cachio_: meh, I think its my fault :/
[18:35] <mvo> cachio_: I cherry-picked the license display PR into 2.31
[18:35] <mvo> cachio_: so there is a test for it in git
[18:35] <mvo> cachio_: but this cherry-pick is not included in ~rc2
[18:35] <mvo> cachio_: that explains the failure
[18:36] <slangasek> ogra_: grub verifying it using what code?
[18:37] <ogra_> slangasek, dunno, thats why i ask :) would that be a kernel thing ?
[18:37] <slangasek> ogra_: possibly.  in practice verification of initrds has consistently been punted to "that's a TPM thing"
[18:37] <ogra_> i assume there is a way to have a signed initrd too ... along with a signed kernel
[18:39] <ogra_> slangasek, the issue is ... we wanted to use u-boot.FIT for secure boot on arm for a project, but it turned out that this only allows a giant blob that contains kernel. initrd and dtb in a single file ... that doesnt go so well with snaps, so i'm looking into the possibility to instead use grub-uboot for that
[18:39] <ogra_> ... in the hope it allows me to have single files i can load
[18:40] <ogra_> (but still keep a secure chain of verified images)
[18:47] <ogra_> aha
[18:48]  * ogra_ finds https://ruderich.org/simon/notes/secure-boot-with-grub-and-signed-linux-and-initrd
[18:54] <cachio_> mvo, I noteced that :)
[18:54] <cachio_> np
[18:56] <slangasek> ogra_: right, so initrd is difficult because it's generated outside the archive, and the UEFI signing keys are quite intentionally only in the archive
[18:56] <ogra_> slangasek, right, but thats not the case in snap-land :)
[18:58] <slangasek> ogra_: it's still not generated in the Ubuntu archive, AFAIK?
[18:58] <cachio_> mvo, also we need a strace-static snap for i386
[18:58] <cachio_> mvo, could you please share it to me?
[18:59] <ogra_> slangasek, yeah, but thats the x86 UEFI world ... here we'll have a customer with his own key that gets burned into the trust zone on the arm board ... so all i need to care about is that the snaps get signed with the right key when the customer builds them in-house
[19:00] <ogra_> so no archive key involved
[19:02] <slangasek> ogra_: ah, I see. so, then the problem is, the initrd is not a PE object, which means the usual secureboot signature verification code can't do anything with it
[19:02] <ogra_> s/that the snaps/that the binaries in the snaps/
[19:02] <ogra_> right, but i the case of a custom key that wont matter ... great ...
[19:08]  * zyga dinner
[19:42] <jdstrand> ogra_: otoh, I don't... tyhicks *may*, but jjohansen probably would (though he is traveling and may not be available)
[19:42] <jdstrand> tyhicks, jjohansen: question from ogra is when does "bpf" show up in /proc/filesystems?
[19:44] <zyga> hey jdstrand o/
[19:45] <jamesh> zyga: hi.  Is there any particular reason why snap-update-ns only logs failures to mount/unmount file systems rather than treating it as a failure?
[19:48] <mup> PR snapcraft#1901 closed: elf: check if file exists before checking if ELF <bug> <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1901>
[19:48] <tyhicks> ogra_, jdstrand: is there more context? (I don't have backscroll handy)
[19:49] <tyhicks> ogra_, jdstrand: filesystem types show up in /proc/filesystems when filesystems of that type are available in the kernel (I doubt that answers your question and that you already know that)
[19:49] <tyhicks> s/and that you already know that/and suspect that you already know that/
[19:49] <mvo> cachio_: sure thing, let me fix the strace-static thing
[19:49] <jdstrand> hey zyga
[19:50] <jdstrand> tyhicks: right. let me give the whole question
[19:50] <zyga> jamesh: that's a good question, I think it was decided long ago
[19:50] <zyga> jamesh: I'm not super fond of it as we probably don't do things correctly then
[19:50] <jdstrand> tyhicks: 11:09 < ogra_> jdstrand,  (or any other securiteer ) ... looking at different core kernels i see "bpf" in /proc/filesystems ... the kernel i'm currently working on does not show it and i cant find what Kconfig option would enable the bpf filesystem, do you happen to have any hint (google isnt helpful either)
[19:51] <tyhicks> aha
[19:51] <tyhicks> I can answer that with some investigation
[19:52] <jdstrand> zyga: considering that snap-update-ns tries to do things in order, failing somewhere along the way and continuing as if it succeeded seems incorrect
[19:53] <jdstrand> ogra_ (cc zyga): I just looked at 3 different core systems, and none of them have a populated /etc/apparmor.d/cache
[19:53] <tyhicks> ogra_: the bpf filesystem was first added in kernel 4.4 with this commit: https://git.kernel.org/linus/b2197755b2633e164a439682fb05a9b5ea48f706
[19:54] <jdstrand> ogra_ (cc zyga): /var/cache/apparmor is correctly populated with snap cache (and nothing else)
[19:54] <tyhicks> ogra_: from what I can tell, it is only hidden behind CONFIG_BPF_SYSCALL
[19:56] <jdstrand> ogra_ (cc zyga): /etc/apparmor.d/cache is a writable path, so for giggles I unmounted it and /etc/apparmor.d/cache was also empty. if I were to guess, I would say that the ordering of the apparmor unit and the writable-path is wrong and that /etc/apparmor.d/cache is still readonly at the time that the parser is run
[19:57] <zyga> jdstrand: oho
[19:57] <zyga> jdstrand: nice find
[19:58] <mvo> jdstrand: with me "empty-etc" hat on> why is etc used to write a cache?
[19:58] <jdstrand> ogra_ (cc zyga): iirc this used to work. I don't know when it would have regressed. we should probably have a spread test to make sure
[19:58] <zyga> mvo: your question is spot on
[19:58] <jdstrand> mvo: hi! terribly longtime historical reasons
[19:59] <mvo> jdstrand: fair enough, just like 80% of etc
[19:59] <jdstrand> mvo: right
[19:59] <jdstrand> mvo: it predates me. afaik, it was there because alternatives weren't guaranteed to be mounted during early boot (eg, /var)
[20:00] <zyga> mvo: you probably know better than I do that /etc used to hold *binaries*
[20:00] <jdstrand> mvo: and other places were not lsb compliant (not that /etc/apparmor.d/cache is)
[20:02] <jdstrand> mvo: it comes up from time to time on the mailing list. there is a general desire to move it, but it gets complicated wrt to early boot, distros, etc. however for core, there is no reason we couldn't put it somewhere else, but we'd have to be careful about early boot
[20:02] <jdstrand> mvo: it comes up from time to time on the mailing list. there is a general desire to move it, but it gets complicated wrt to early boot, distros, etc. however for core, there is no reason we couldn't put it somewhere else, but we'd have to be careful about early boot
[20:02] <mvo> jdstrand: ok
[20:03] <jdstrand> mvo: I'm not sure how much you saw before you dropped off...
[20:03] <mvo> jdstrand: I missed this, thanks for pasting
[20:03] <mvo> jdstrand: my machine is a bit unstable recently, I wonder if I need to purge the intel-microcode package :(
[20:03] <jdstrand> mvo: here are two more:
[20:04] <jdstrand> mvo: it predates me. afaik, it was there because alternatives weren't guaranteed to be mounted during early boot (eg, /var)
[20:04] <jdstrand> mvo: and other places were not lsb compliant (not that /etc/apparmor.d/cache is)
[20:04] <mvo> jdstrand: ta
[20:04] <jdstrand> mvo: maybe-- mine made suspend not work at all
[20:04] <jdstrand> well, it would suspend. it wouldn't come out ;)
[20:05] <jdstrand> I'm hopeful new microcode will be available
[20:05] <mvo> jdstrand: thanks for the apparmor, for core18 we may need to tweak this, but its only one of many potential things we need to tweak :)
[20:05] <mvo> jdstrand: I will purge it for now :(
[20:06] <jdstrand> mvo: can you think of what might've caused the cache to not be populated?
[20:06] <jdstrand> mvo: do you also recall this used to work?
[20:06] <mvo> cachio_: I create a proper lp:~snappy-dev/strace-static-snap/trunk project with an auto snap build
[20:06] <cachio_> mvo, awesome, tx
[20:07] <jdstrand> ogra_: can you file a bug for /etc/apparmor.d/cache and we can contineu there?
[20:07] <mvo> jdstrand: I don't recall this used to work and I think the most plausible is what you said, if this run very early the location might still be read-only
[20:07] <mvo> jdstrand: fwiw, I hope we won't have writable-paths for core18 just a plain writable etc
[20:07] <jdstrand> it certainly is meant to work, otherwise those poor arm devices are grumpy
[20:07]  * jdstrand -> gotta run. bbiab
[20:18] <mup> PR snapd#4574 closed: tests: add integration for local snap licenses <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4574>
[20:33] <mup> PR core#80 opened: hooks: c-n-f is expected in /usr/lib/command-not-found <Created by mvo5> <https://github.com/snapcore/core/pull/80>
[20:36] <zyga> mvo: +1
[20:47] <mvo> zyga: ta
[20:47] <mup> PR core#80 closed: hooks: c-n-f is expected in /usr/lib/command-not-found <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/core/pull/80>
[20:47] <mup> PR snapd#4577 opened: snap: fix command-not-found on core devices <Created by mvo5> <https://github.com/snapcore/snapd/pull/4577>
[20:49] <zyga> mvo: so... it wasn't tested in practice before?
[20:50] <zyga> mvo: hmm
[20:50] <zyga> mvo: why
[20:50] <zyga>  +cmd.Positionals.CommandOrPkg = os.Args[2]
[20:50] <zyga> I don't get it
[20:50] <zyga> you iterate over all args except 0th
[20:51] <zyga> and then you can have a chain of --
[20:51] <zyga> and the first one that doesn't will set a _fixed_ answer
[20:51] <zyga> is that correct?
[20:51] <mvo> zyga: meh, incomplete push
[20:51] <mvo> zyga: sorry
[20:52] <mvo> zyga: please reload
[20:52] <mvo> zyga: originally I wanted to just hardcode os.Args[2]
[20:52] <mvo> zyga: but then though checking for "--" would be more robust if the handler that calls c-n-f ever changes
[20:53] <mvo> zyga: I guess it shows that I should stop for today :)
[20:53] <mvo> zyga: the integration on a real shell on a core device was not tested until today :/ many moving parts
[21:02] <geekgonecrazy> Greetings guys.  Back with more snap/snapcraft related issues. :)
[21:02] <geekgonecrazy> In the rocketchat-server snap we do an npm install.  One of the packages seems to always have issues getting properly snapped up
[21:03] <geekgonecrazy> So most of the time we can explicitely install it and it'll make it through.  But we're running into the issue again.  It seems as if for some reason snapcraft decides that the binaries don't need to be included so skips them
[21:03] <geekgonecrazy> > Unable to determine library dependencies for b'/build/stable/prime/programs/server/npm/node_modules/grpc/src/node/extension_binary/node-v57-linux-x64-glibc/grpc_node.node'
[21:04] <geekgonecrazy> we see this ^ and that exact same file is then complained about being missing when we try to start it
[21:04] <geekgonecrazy> does "Unable to determine library dependencies" really mean... "Can't figure out what to do with this so skipping" ?
[21:12] <zyga> geekgonecrazy: this is something for sergiusens, kyrofa and kalikiana
[21:13] <zyga> though they are sprinting this week so conditions apply
[21:17] <geekgonecrazy> zyga: ok fair enough.  I'll roll back our armhf build.  Typically if there is an error building it errors out.  But seems that the skipping of the files isn't an error just a silent thing :(
[21:18] <geekgonecrazy> i'd keep digging tonight, but gotta prep to head out to fosdem tomorrow.  Do you know if any of the snap/snapcraft team will be attending?
[21:23] <zyga> geekgonecrazy: I don't know, sorry
[21:24] <zyga> geekgonecrazy: they have a sprint now in US so probably not
[21:24] <zyga> though maybe someone else is going
[21:35] <geekgonecrazy> zyga: no biggie.  Just figured someone around might know :D
[21:45] <mup> PR snapcraft#1902 opened: many: use in-snap unsquashfs and readelf if running from snap <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/1902>
[23:05] <ogra_> jdstrand, thanks for the investigation, will file it ...
[23:07] <ogra_> tyhicks, thanks for the research ! i have the BPF_SYSCALL option set here but still dont see it in /proc/filesystems ... will dig further myself ...
[23:20] <tyhicks> ogra_: kernel version?
[23:52] <jdstrand> greyback: hey, you probably saw but I approved your /dev/shm/# pr, but can you add the requested comment?


[02:43] <Rcart> broder: o/
[02:46] <Rcart> when do we get this kind of failures? bug 778571
[02:54] <ScottK> Rcart: Given that "daemon: could not create pid file "/var/run/mpd/pid": Permission denied" is in the terminal log on the bug, I'd guess permissions (or existence) issue with the pid file.
[02:57] <lfaraone> ScottK: how familiar are you with duplicity? ISTR seeing you talk about using it.
[02:57] <ScottK> No.  Not me.
[02:57] <lfaraone> ScottK: ah, okay. what do you use for backups, then?
[02:58] <ScottK> rsync and shell.
[02:58] <ScottK> sometimes kbackup.
[02:59] <Rcart> ScottK: So, that bug is due a configuration problem, right? (maybe user field in /etc/mpd.conf)
[02:59] <ScottK> Rcart: No.  Probably not.
[03:04] <Rcart> ScottK: how can I track those bugs when trying to fix them? I've fixed typos and I'd like to change the topic
[03:05] <ScottK> Since /var/run is on a tempfs in Ubuntu (but not Debian) one common source of bugs like this is that the init doesn't ensure /var/run/mpd exists.  It needs to check and create it if it's misisng.
[03:05] <ScottK> I'd check that first.
[03:09] <Rcart> great, that's a good starting point
[03:09] <Rcart> ScottK: I'll take a look. Thanks
[03:10] <ScottK> You're welcome.
[06:19] <vibhav> Is any mentor available here?
[06:26] <vibhav> Can anybody help in finding dependencies of http://git.xfce.org/bindings/xfce4-vala/ ?
[07:35] <vibhav> Is any MOTU available?
[08:06] <dholbach> good morning
[08:07] <valdur55> Morning :)
[08:10] <vibhav> dholbach: Hi
[08:10] <vibhav> dholbach: Could you review my upload at http://revu.ubuntuwire.com/p/indicator-sensors
[08:10] <dholbach> hi vibhav
[08:13] <vibhav> Also, I fixed the errors mentioned in those comments
[08:35] <vibhav> Can anybody help me in packaging a promgram?
[08:36] <tumbleweed> vibhav: there are lots of people here who can help, but you haven't asked a qustion we can answer yet
[08:38] <vibhav> Ok, here it goes
[08:38] <vibhav> I am packaging shc (http://www.datsi.fi.upm.es/~frosal/sources/shc-3.8.7.tgz)
[08:38] <vibhav> And the program doesnt have a 'configure' script
[08:39] <vibhav> And dh_make returns : You should also
[08:39] <vibhav> check that the shc Makefiles install into $DESTDIR and not in /
[08:39] <vibhav> how do I do this?
[08:39] <tumbleweed> you read the Makefile
[08:40] <tumbleweed> this is quite a simple makefile, so it's fairly easy to follow
[08:40] <vibhav> The Makefile INSTALL_PATH = /usr/local
[08:41] <vibhav> It seems then its correct
[08:41] <vibhav> Alrighty!
[08:41] <vibhav> thanks tumbleweed
[08:41] <tumbleweed> right, but the GNU coding standards expect that to be called DESTDIR not INSTALL_PATH
[08:41] <vibhav> should I changei it to DESTDIR?
[08:41] <vibhav> change*
[08:42] <tumbleweed> you could, or you could just pass INSTALL_PATH=debian/shc when you call make install
[08:42] <vibhav> I changed it to DESTDIR
[08:42] <vibhav> Will it do any harm then?
[08:42] <tumbleweed> no
[08:43] <vibhav> thanks then
[08:43] <tumbleweed> there's another issue I see in the Makefile
[08:43] <tumbleweed>     @echo -n '***   ¿Do you want to continue? '; read ANS; case "$$ANS" in y|Y|yes|Yes|YES) ;; *) exit 1;; esac;
[08:43] <tumbleweed> you'll probably want to remove that :)
[08:44] <vibhav> why?
[08:45] <vibhav> oh
[08:45] <vibhav> I see
[08:45]  * ajmitch should really remember to dist-upgrade more often, 1.5GB to download & install
[08:48]  * tumbleweed is in a new flat, on 3G while I wait for a phone line. No dist-upgrades for me for a couple of weeks
[09:02] <ajmitch> that's a bit painful, i suppose you've got a tiny data cap as well?
[09:07] <tumbleweed> yup (well, pay-per-MB. Paid R350 - ~35 EUR for 2GB. I'll see how long it lasts...)
[09:08] <micahg> tumbleweed: I just uploaded a 280MB chromium tarball :)
[09:09] <ajmitch> micahg: am I allowed to hate you now?
[09:09] <ajmitch> I've got a 20GB monthly cap :)
[09:09] <tumbleweed> micahg: I miss ia32-libs
[09:09] <micahg> tumbleweed: not sure why it's still broke
[09:09] <micahg> ajmitch: I think I have a mandatory minimum 20GB usage :)
[09:10] <ajmitch> micahg: yeah, I've found that not all data is tracked, so my average monthly usage is possibly several times that amount :)
[09:10]  * micahg switch Cable providers when his last one instituted BW caps
[09:10]  * ajmitch doesn't have that option in NZ
[09:11] <micahg> tumbleweed: I'm happy to sponsor stuff for you while you're in slow mode
[09:11] <tumbleweed> "uncapped" is a fairly new feature around here, but the quality tends to be far worse
[09:12] <tumbleweed> micahg: I'm mostly alright, I have a colo box I can build on and upload from
[09:13] <ajmitch> FTTH plans are coming out in NZ, one of the larger ISPs just released pricing today
[09:13]  * ajmitch wouldn't mind a 100/50 Mbps connection
[09:14]  * micahg has 25/2 ATM
[09:14]  * ajmitch is on approx 20/1 ADSL2+, generally fast enough
[09:15] <ajmitch> it's just downloading from archive.ubuntu.com on the other side of the world is a bit slow
[09:15] <tumbleweed> no local mirrors?
[09:15] <ajmitch> apart from the mirror on my desktop machine? :)
[09:15] <tumbleweed> :P
[09:15] <ajmitch> NZ mirrors have a habit of getting badly out of date
[09:16] <micahg> ajmitch: university of canterbury shows as up to date
[09:16]  * tumbleweed is in almost continual e-mail conversation with my upstream mirror. They are getting better, but I think I'm the closest they have to automated monitoring
[09:16] <ajmitch> micahg: the mirrors seem to take turns in having update failures
[09:17]  * ajmitch isn't too worried
[09:28] <dholbach> huats, warp10, broder: Bhavani also wants to join the team - I didn't think this would get that much interest :)
[09:29] <warp10> dholbach: it's the coolest team ever!
[09:29]  * micahg is curious which team this is
[09:29] <dholbach> the Developer Advisory Team
[09:29]  * micahg wonders if he should get in on this
[09:30] <dholbach> warp10, now I need to generate similar interest in the Dev News team :)
[09:30] <dholbach> warp10, and a Developer Initiatives/Events (Fix-It Friday, UDW, etc.) team
[09:31] <dholbach> https://wiki.ubuntu.com/DeveloperAdvisoryTeam has a very brief explanation of what the d-a-t does
[09:31] <warp10> dholbach: uh, Events Team, nice one. You need creative minds there
[09:32] <dholbach> for events like UDW and Fix-It Friday we already have patterns of how we normally do them, but it still involves a bit of work getting everything in place, announcing it and so on
[09:33] <dholbach> for example for next Friday, I'd like a few of us to get together on Thursday to put together a list of bugs which might be good targets for new contributors
[09:33] <dholbach> so that they don't have to go fishing around and not finding anything
[09:33] <dholbach> and it's also nice to be able to say "Friday morning we had 50 bugs, Saturday morning we had 0 of them left" :)
[09:33] <dholbach> we'll get there :)
[09:34] <warp10> dholbach: good idea. Finding easy bugs is probably the hardest and most boring part for new contributors. And the bitesize tag on LP is not that helpful, unfortunately
[09:34] <dholbach> no it isn't
[09:35] <dholbach> but on the rcbugs list or the resolved-upstream list we should be able to find 50 bugs easily if 4-5 of us spend a couple of minutes on it
[09:35] <dholbach> let's do that tomorrow
[09:35] <warp10> dholbach: Yeah
[09:35] <dholbach> also I want to do a public G+ Hangout tomorrow to invite newcomers to ask all their questions
[09:35] <dholbach> maybe that's less daunting than hopping on a "developer irc channel"
[09:36] <ajmitch> rcbugs list is always just possible bugs, half the fun there is seeing which ones don't apply to ubuntu
[09:36] <warp10> dholbach: oh, nice idea. I heard that public hangouts from android developers gathered tens of people and lot of excitement
[09:36] <ajmitch> dholbach: how many people can you have in one of those hangouts anyway?
[09:37] <dholbach> ajmitch, sure - and if they go through the process just to find out we got packages in sync again, then that was a good learning experience already ;-)
[09:37]  * ajmitch would join in but it'll be at some crazy time :)
[09:37] <dholbach> ajmitch, no idea
[09:37] <dholbach> ajmitch, but I could try to do a few of them on Thursday to cater to different timezones
[09:38] <warp10> ajmitch: I joined a ~20 person hangout (but just a couple with video too) without any glitch a few weeks ago.
[09:38] <ajmitch> warp10: ok, I thought it was limited to 10
[09:38] <ajmitch> though you'd often have fewer active people than that at irc sessions
[09:39] <warp10> ajmitch: oh, really? Don't know, it was hosted by Google itself (gmail guys, IIRC), maybe they tweaked the limit :)
[10:40] <vibhav> Is there any GUI program to write man pages?
[10:40] <valdur55> vibhav, use usual text editors, man pages are normal text files
[10:42] <vibhav> valdur55: They have a specific syntax which I find hard to follow
[10:42] <valdur55> vibhav, yes, but you can use other programs man pages ;)
[10:43] <valdur55> and then make notes... and use your notes
[10:43] <vibhav> valdur55: Thanks
[10:44] <valdur55> vibhav, no problem, you need find out how can you help yourshelf. Use free software power!
[10:48] <vibhav> Where is the man page located in the debian folder?
[10:52] <tumbleweed> wherever you want to
[10:53] <vibhav> I mean what do these .ex files do?
[10:53] <vibhav> I usually delete them
[10:55] <tumbleweed> they are examples
[10:59] <vibhav> so what will be the file name of the man page then?
[10:59] <vibhav> manpage.1
[10:59] <vibhav> or manpage.1.ex ?
[10:59] <valdur55> vibhav, simply look on some package source code.
[11:00] <vibhav> valdur55: My internet connection is really slow right now
[11:00] <vibhav> 1 kbps :(
[11:07] <geser> vibhav: manpage.1 (as you probably intend to write a real manpage and not an example)
[11:07] <vibhav> geser: thanks
[11:10] <hrw> dholbach: fix it fridays are nice initiative but for next cycle can we move them to other day?
[11:10] <dholbach> let's discuss it on the mailing list after this cycle :)
[11:10] <hrw> dholbach: sure
[11:10] <dholbach> I'm not bound to any day
[11:11] <dholbach> it came just up as an idea
[11:11] <vibhav> fix it Sundays might be better
[11:11] <vibhav> Since people have more free time on sundays
[11:11] <hrw> dholbach: the reason is that you hack/fix, provide debdiffs and then next day sponsors have suggestions for you.
[11:11] <hrw> vibhav: I do not work during weekend
[11:12] <dholbach> vibhav, some do, some don't :)
[11:12] <hrw> dholbach: when next day == monday it is harder to remind which machine this was done on etc
[11:12] <hrw> dholbach: last friday I used 3 computers at same time for fixes
[11:27] <Adri2000> friday vs. sunday is about whether people contribute as part of their job or on their free time :)
[11:33] <geser> simple solution: Fix-It-Week
[11:33] <vibhav> ^
[11:33] <vibhav> There is no upstream URL for shc. What do I put in control?
[11:34] <vibhav> and copyright?
[11:34] <geser> in copyright: the location where you downloaded the upstream tarball
[11:35] <geser> in control: if the software has no homepage than you can leave out the Homepage: field
[11:57] <vibhav> What does the rules file do?
[11:58] <jalcine> It's like a Makefile for Debian packages.
[11:58] <jalcine> afaik.
[11:58] <jalcine> If you used debuilder and don't have any special needs, you could leave it as is.
[12:17] <vibhav> Alrighty!
[12:17]  * vibhav debuild's
[12:27] <vibhav> Which is the best way to ask for reviewers on this channel?
[12:34] <nigelb> 5/ws 34
[12:34] <nigelb> ugh
[12:35] <vibhav> ?
[12:49] <arand> vibhav: Is it a new package? Shouldn't it go into Debian? Particular since Ubuntu is in FF..?
[13:05] <ScottK> arand: It's a Unity specific package he's after, so via Debian is a little harder than normal.
[13:07] <arand> ScottK: vibhav: Oh, I must've misread, I though you were packaging shc.
[13:07] <ScottK> It might be me too.
[17:35] <PaoloRotolo> Hi all!
[17:42] <jalcine> Hey PaoloRotolo
[17:42] <PaoloRotolo> jalcine, hi!
[18:29] <pabelanger> Is ubuntu-motu the best place to talk about openstack (nova) packaging issue or should I be in another channel?
[18:31] <ScottK> pabelanger: I suspect #ubuntu-server would be better.
[18:31] <pabelanger> ack'd
[19:04] <thibaud-ecarot> hi all
[20:55] <goddard> when i have finished making my changes to a project on launchpad and i have made my last commits do I click the propose for mergeing button?
[20:57] <sladen> goddard: yes
[20:58] <goddard> ok thanks
[20:59] <sladen> goddard: what's the project, is it something that needs sponsoring?
[21:02] <goddard> umm just the ubuntu packaging guide.. I'm new to ubuntu development and i was trying to learn how to package and in the process I found out the packaging guide was broken haha
[21:02] <ScottK> That puts you in a perfect position to fix it.
[21:02] <goddard> https://code.launchpad.net/~kinggoddard/ubuntu-packaging-guide/913934-fix
[21:02] <goddard> exactly
[21:02] <ScottK> Those of us who know what we're doing can't appreciate what's wrong with it.
[21:02] <goddard> it was kqrcode so i changed it to gnu hello
[21:05] <goddard> do you use virtual box to build stuff and test?
[21:12] <jtaylor> pbuilder or something equivalent is often more convinient
[21:14] <Rcart> goddard: take a look at: http://developer.ubuntu.com/packaging/html/getting-set-up.html#set-up-pbuilder
[21:14] <goddard> i click propose merge and it just shows the little loading gif .... how long does it usually take?
[21:15] <jtaylor> not long, but launchpad often lags
[21:16] <goddard> ahh
[21:16] <goddard> Rcart: thanks
[21:52] <jalcine> Okay, so there's this library from a package (libxdo from xdotool) that causes a build issue when I use C++.
[21:52] <jalcine> I've apt-get source'd it, but what would I do from there to consider getting it patched?
[21:53] <broder> jalcine: you mean the library works if you build c code using it, but not if you use c++?
[21:54] <jalcine> precisely.
[21:58] <broder> that usually means you need to change the headers so that the declarations in the headers are wrapped in extern "C" { /* prototypes go here */ }
[21:58] <broder> http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html#faq-32.4 shows how you can do it
[21:58] <broder> (you need an #ifdef so those only get included when you're building on C++)
[21:59] <broder> unlike what that FAQ says, i think you usually just put the extern "C" around the prototypes (not, e.g., #includes of other headers)
[21:59] <broder> but i'm not positive
[22:49] <jalcine> broder: the situation I have is a bit different than that.
[22:49] <jalcine> The C header has a function whose parameter's name is 'class'
[22:49] <jalcine> and that causes a compile-time error with C++ code.
[22:50] <broder> hmm, i don't know what the best practice is there
[22:51] <jalcine> The only real way to get around that would be to edit the header, but that'd need a patching of the code. And it's just for one line (it's the only function in the whole library that has that).
[22:52] <jtaylor> you can declare that functions needed yourself
[22:52] <jtaylor> not nice but would work
[22:52] <jtaylor> you should report that to upstream
[22:52] <jtaylor> parameter names are not needed in headers
[22:53] <ajmitch> http://code.google.com/p/semicomplete/issues/detail?id=60 has it already
[22:54] <jalcine> >_< should have google'd it first.
[22:54]  * ajmitch just went to the home page from the debian PTS
[22:55] <ajmitch> looks like a useful tool, I wonder what the unity developers are using for similar automated testing
[22:55] <jtaylor> its quite nice
[22:56] <jtaylor> but very unreliable for non us keyboard layouts
[22:56] <jtaylor> or even configured with more than one layout
[22:56] <ajmitch> which is quite a lot of the world
[22:58] <jalcine> No dice, it keeps expecting a class declaration.
[22:58] <jtaylor> yes you have to skip that header and forward declare the functions you need
[22:59] <jalcine> Thanks, I'll try it.
[22:59] <jtaylor> might be an easy fix to do in the package
[23:00] <jtaylor> unless upstream intentionally does not want c++ to link with it :)
[23:03] <jalcine> That's what I was thinking, lol.
[23:04] <jtaylor> can you define a macro named class in C++?
[23:04] <jtaylor> that might work to if allowed
[23:06] <jalcine> Don't think so, but I'm using C++0x
[23:08] <jtaylor> its c++11 now
[23:08] <jtaylor> oh 4.6 does not accept that yet :(
[23:11] <jalcine> nope :/
[23:11] <jalcine> I'm going to patch it, this is ridiculous..
[23:11] <jalcine> Thanks for the help guys.
[23:25] <Rcart> broder: I've add a apport hook for mpd, and you merged a branch that fixed a typo a few days ago
[23:25] <Rcart> an*
[23:26] <Rcart> I think that it would be better to include this hook and the same revision as the typo, and merge it
[23:29] <jtaylor> jalcine: ftw I have reported the bug to the debian package
[23:31] <broder> Rcart: i've already uploaded the typo fix, so any other changes would be a new revision. i don't think i'll have time to review the change in the next few days, so the best thing to do would be just open a merge proposal against lp:ubuntu/mpd and that will put it in the sponsorship queue
[23:31] <jalcine> Thanks jtaylor! I'm kind of behind a SSL block (tethering), I was going to wait until tomorrow to report such a bug.
[23:31] <broder> Rcart: but i do have one thing that you should think about
[23:32] <Rcart> broder: tell me
[23:32] <broder> which is this: ubuntu has patched debian's package fora while, but we are getting the package from debian, so ideally at some point in the future we could revert to just using their package without any modifications
[23:32] <broder> does the apport hook deliver valuable enough information that it's worth maintaining that diff indefinitely?
[23:32] <broder> (the answer may be yes)
[23:33] <Rcart> Yes, I guess
[23:33] <broder> ok
[23:33] <broder> that's a fine answer
[23:34] <Rcart> the hook includes the user configuration file, so when reporting bugs against mpd we'll get that file (without passwords), but not the system configuration (/etc/mpd.conf)
[23:35] <Rcart> bug 947551
[23:36] <broder> does anybody else know if we take apport hooks in universe packages in general?
[23:36] <Rcart> bdmurray: should the script be included? I mean, is ready to be included?
[23:37] <micahg> broder: sure, why not?
[23:37]  * broder shrugs
[23:38] <micahg> ideally, we wouldn't want to keep it as the only diff with Debian, but many Debian maintainers will include hooks
[23:40] <ajmitch> the problems come when you need to build-depend on dh-apport
[23:42] <broder> sure. in practice, dh_apport and dh_apparmor do little enough that you might as well just do it by hand in many cases
[23:43] <micahg> well, at least apparmor is in Debian, apport isnt' yet
[23:44]  * ajmitch knows there was an RFP for it at least, didn't take it much further than that
[23:44] <ajmitch> since for debian it'd ideally submit to the BTS
[23:45] <micahg> the thing is Debian already has the equivalent of apport for non crash stuff in reportbug
[23:45] <broder> that doesn't seem too hard - the bugtracker stuff in apport is pluggable
[23:45] <ajmitch> broder: right, someone just has to do it :)
[23:46] <ajmitch> it didn't quite bug me enough for me to jump into it & maintain apport in debian
[23:46] <micahg> hehe
[23:46] <broder> it's not clear how much utility there is in practice without ddebs
[23:47] <ajmitch> broder: I'm biased, I mostly want it with python packages that can just get a traceback
[23:47] <broder> ajmitch: heh, fair enough
[23:48]  * ajmitch wonders how ddebs are coming along in debian
[23:48]  * broder was just looking into that
[23:48] <broder> the proposal involves modifying dak, though, so i'm guessing "poorly"
[23:48] <ajmitch> 'here be dragons'
[23:48] <broder> making changes to dak seems to be where every interesting debian workflow change gets stuck
[23:49] <broder> see also the binaryful-uploads-but-ignore-the-binary-and-rebuild-it proposal
[23:49] <ajmitch> yeah, something that sounds simple
[23:49] <ajmitch> it's not like ubuntu never blocks on LP changes though
[23:50] <broder> true. /me grumbles about backports and build-deps
[23:50] <ajmitch> like backports build-depending on each other
[23:51] <broder> oh, eww. the proposal uses build-ids and requires their solution to a hash collision is "switch hashes"
[23:52] <ajmitch> not pretty


[16:17] <highvoltage> stgraber: I'm going to decline the confirmed JZ Software deployment submissions
[16:17] <highvoltage> stgraber: they seem incomplete / not useful
[16:18] <stgraber> highvoltage: agreed
[16:33] <highvoltage> stgraber: someone also emailed and said that they couldn't authenticate with the nx client - same problem I seem to have had
[16:33] <highvoltage> I didn't figure out why it didn't work for me in the end
[16:33] <stgraber> highvoltage: yeah, I saw that one. Not very high on my priority list though. I still think something's broken in the Drupal plugin, possibly related to the aggressive caching we do.
[16:34] <stgraber> anyway, moving forward we'll drop NX and just provide an x2go session file and link to the client for all platforms
[16:39] <highvoltage> stgraber: is it perhaps a good idea to disable weblive with a message for a bit? especially considering that our servers will probably dissappear soon?
[16:40] <stgraber> highvoltage: well, weblive still appears to have worked fine for a few hundred users and the software-center integration is still fine for < 13.04
[16:41] <highvoltage> stgraber: ah good
[17:11] <alkisg> highvoltage: hi - could you remove me from the<EMAIL_ADDRESS>list? I don't think I can help in any of those mails, and I don't even have access to the pages in edubuntu.org where it links, to add sites etc
[17:15] <highvoltage> alk<tab>
[17:16] <highvoltage> stgraber: ^^^ alkisg wants to be removed from the list, not sure what he means by the edubuntu.org links, I'm pretty sure he can access all of them, but otherwise I think he could just get edit rights if that would help
[17:21] <stgraber> highvoltage: actually, he's not in the ~edubuntu-website team so doesn't have website access ;)
[17:23] <highvoltage> stgraber: I meant... he can access the website just like any other person can, so there's no reason why he couldn't paste links
[17:23] <highvoltage> :)
[17:23] <stgraber> highvoltage: ah, sure, he might be pretty confused by the deployments e-mails
[17:23] <stgraber> as those he can't do anything about it
[17:23] <highvoltage> aaah, right
[17:23] <highvoltage> did he even get those?
[17:24] <stgraber> yep, they're being sent to contact
[17:24] <highvoltage> well, I'll talk to him about it when he's online again then
[18:39] <prp-e> HI


[16:01] <yamokidzu-it> please can you tell me the web-stite where get the wicd FULL installer from the web
[16:01] <yamokidzu-it> *sorry the web site
[16:02] <yamokidzu-it> I need a full wicd installer that doesn't propt for connection
[16:02] <yamokidzu-it> help please no answer in help channell...
[16:12] <yamokidzu-it> very sorry wrong channel ;-)


[12:26] <mirqui> bom dia :)
[13:09] <mirqui> bom dia 2 :)
[16:24] <mirqui> boa tarde :)
[18:56] <mirqui> boa tarde 2 :)