[05:04] <mborzecki> morning
[05:05] <zyga> good morning
[05:06] <mborzecki> zyga: hey
[05:06] <zyga> how was your weekend?
[05:08] <mborzecki> zyga: good, spent no more than an hour in front of the computer throughout the whole weekend
[05:08] <mborzecki> oh and i bought a bike, finally replacing my old one :)
[05:08] <zyga> mborzecki: I spent a few hours yesterday trying to put some life into and old netbook my mom gave me
[05:08] <zyga> ooh, nice
[05:09] <zyga> we managed to clean the garage to make room for the bikes
[05:09] <zyga> did a "garage sale" and let go some stuff
[05:09] <zyga> the bigger things (old kiddy beds) will likely be picked up this week so we will have all the room available
[05:10] <mborzecki> nice
[05:10] <mborzecki> btw. let me show you something
[05:13] <mborzecki> zyga: https://i.imgur.com/YM0lCsE.jpg
[05:14] <zyga> is that the one with folded keyboard?
[05:14] <zyga> ah
[05:14] <zyga> no
[05:14] <zyga> :)
[05:14] <mborzecki> no, unfortunately not
[05:14] <zyga> I saw one recently
[05:14] <zyga> what's inside?
[05:14] <mborzecki> asking price was ~30eur
[05:14] <zyga> pretty low, the cosmetics are nice
[05:14] <zyga> did you buy it?
[05:15] <mborzecki> nope, bought a road bike instead
[05:15] <zyga> :-)
[05:16] <zyga> I'm using sports tracker for my biking fun
[05:16] <zyga> e.g. this https://www.sports-tracker.com/workout/zygmuntkrynicki/5af879cec3d63959d624fc56
[05:16] <mborzecki> got a used bike for ~540eur, with my frugal spending habits, another 30 felt like too much
[05:18] <mborzecki> zyga: looks like direct competition to endomondo
[05:18] <zyga> yeah, plenty of those apps
[05:18] <zyga> I've been using it for some time
[05:19] <zyga> it was working on my blackberry first :D
[05:19] <zyga> and it integrates with apple health now so I like it (it tracks my biking in the apple health app)
[05:19] <zyga> my wife uses endomodo as well but this one seems like what you get if you pay for endomodo
[05:23] <mborzecki> zyga: wonder if you can see this https://www.endomondo.com/users/20483467/workouts/1119982468
[05:24] <zyga> yes
[05:24] <zyga> nice route :-)
[05:25] <mborzecki> that's the medium loop ;) got a couple of variants between 25-35km, the larger ones are 35-50, but those i can only do on weekends
[05:30] <zyga> do you go alone or with family?
[05:31] <zyga> for us the main limiting factor is how far the kids are willing to go
[05:32] <mborzecki> alone mostly
[05:33] <mborzecki> usually have like 1.5-2h of free time, so i can squeeze 25-35km loop
[05:35] <zyga> nice :)
[05:36] <zyga> we usually go on 20km loops at most, also going around Warsaw is not as fluid as there are many street lights and other choke points
[05:36] <zyga> I started going south from where we live, where there's fewer people and buildings but I haven't found a good route yet
[05:37] <zyga> my plan is to do a longer route along the river and then go back through "lasek kabacki" (a bit off to the west) so that the full loop would be close to 40km but we haven't done that y et
[05:38] <zyga> oh btw, I'm going to be off on Thursday, Friday, (this week) Monday, Tuesday and Wednesday (next week)
[05:38] <zyga> I need to file that
[06:23]  * zyga -> walk the dog
[06:25] <mborzecki> zyga: you entirely sure that the arrow does not go in the opposite direction? :)
[06:25] <zyga> haha
[06:25] <zyga> the truth has come out :)
[06:31] <mup> Bug #1484898 opened: device tarball needs to allow setting sysctl defaults <Snappy:Triaged> <https://launchpad.net/bugs/1484898>
[06:49] <mborzecki> zyga: another look at https://github.com/snapcore/snapd/pull/4504 when you're back?
[06:49] <mup> PR #4504: snap, wrappers: systemd WatchdogSec support <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4504>
[06:49] <zyga> Ack
[06:49] <zyga> Still walking but close to home now
[06:49] <zyga> Or I can just try now
[07:07] <pstolowski> mornings
[07:07] <mborzecki> pstolowski: hey
[07:11] <mborzecki> zyga: https://paste.ubuntu.com/p/XTPx5xJFVY/
[07:11] <zyga> mborzecki: nice :)
[07:12] <zyga> is that the volume broken by your script?
[07:12] <mborzecki> yes
[07:14] <mborzecki> need to read more about the name checksums
[07:32] <mborzecki> github slow today?
[07:37] <zyga> mborzecki: I haven't noticed
[07:37] <zyga> mborzecki: I'm puzzled by something
[07:37] <zyga> I bet it is silly
[07:37] <zyga>     if !(strings.HasPrefix(notifySocket, "/") || strings.HasPrefix(notifySocket, "@")) || strings.ContainsAny(notifySocket, `?*[]{}^"`) {
[07:37] <mborzecki> hm?
[07:37] <zyga> so a string must start with either / or @
[07:37] <zyga> and must not have ? and other guys
[07:37] <zyga> right?
[07:38] <mborzecki> zyga: right
[07:38] <zyga> so
[07:38] <zyga> if s is the string
[07:38] <zyga> and s is "/?"
[07:38] <zyga> the first condition will be true, right?
[07:39] <zyga> so || will short-circuit and won't evaluate the rest
[07:39] <zyga> which is wrong
[07:39] <zyga> am I missing something?
[07:39] <zyga> if you add the test for special chars separately
[07:39] <mborzecki> zyga: the first condition will be false
[07:40] <zyga> wh?
[07:40] <zyga> why?
[07:40] <zyga> strings.HasPrefix(s, "/")
[07:40] <mborzecki> !(..)
[07:40] <zyga> that's separate
[07:41] <zyga> the condition inside the ( ) will be true
[07:41] <zyga> then the ! will negate
[07:41] <zyga> but that's separately evaluated
[07:43] <mborzecki> zyga: not sure what you're aiming at, you have !(true) || true for /?
[07:43] <zyga> oh boy
[07:43] <zyga> I'm blind
[07:43] <zyga> I didn't notice the () around the first two
[07:43] <mborzecki> zyga: or in more detail !(true || false) || true
[07:43] <zyga> I though it was around all three
[07:44] <zyga> I tweaked the code slighttly
[07:44] <mborzecki> maybe i should separate the cheks to make it more legible?
[07:44] <zyga> http://paste.ubuntu.com/p/zYzt3mW46f/
[07:44] <zyga> is this okk?
[07:44] <zyga> I can push it
[07:46] <mborzecki> zyga: maybe s/AARE/illegal characters/ ?
[07:46] <mborzecki> (in the error message)
[07:46] <zyga> meta-characters?
[07:46] <zyga> invalid doesn't say much
[07:47] <zyga> yeaah, wrong but why?
[07:47] <mborzecki> hm
[07:48] <mborzecki> zyga: "cannot use %q as notify socket path: contains meta-characters" vs "...: contains illegal characters"
[07:49] <zyga> contains apparmor meta-characters
[07:49] <zyga> or contains one of "..."
[07:49] <zyga> that would be explicic
[07:49] <mborzecki> oh, the last one
[07:50] <mborzecki> zyga: `cannot use %q as notify socket path: contains one of ?*[]{}^"`
[07:50] <zyga> doing that
[07:50] <mborzecki> zyga: thanks!
[07:59] <Chipaca> moin moin
[08:04] <pstolowski> o/
[08:04] <zyga> hey Chipaca, pstolowski
[08:09] <zyga> mborzecki: question about watchdog
[08:09] <zyga> does systemd enfroce any minimum values
[08:09] <zyga> mborzecki: what's the resolution there? seconds
[08:09] <zyga> ah, I see yes
[08:09] <zyga> is 1 second valid?
[08:10] <mborzecki> yeah, i think so
[08:10] <mborzecki> i mean, why wouldn't it?
[08:10] <zyga> I'm wondering if putting unreasonable value would be harmful to the system
[08:10] <mborzecki> if you feel like pinging every second and risking being restarted due to a missed ping, then so be it ;)
[08:11] <zyga> I just realized we should limit the number of apps in a snap
[08:11] <zyga> if we create a snap with 100M services
[08:12] <zyga> it would harm the system eqaisly
[08:12] <mborzecki> zyga: i think it's self regulating, if you put a value too low and miss it and malfunction you'll have the need to regulate it
[08:12] <mborzecki> zyga: the same with apps, i'd guess you'd bring down systemd if a snap has ridiculously large number of apps
[08:13] <mborzecki> s/apps/services
[08:13] <mup> PR snapd#5154 closed: releases: merge 2.32.8 back into master <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5154>
[08:22] <mwhudson> hmm
[08:22] <mwhudson> when selecting server snaps to install in subiquity, should the snaps actually be installed?
[08:22] <mwhudson> or should subiquity build a seed.yaml for the installed system?
[08:24] <mwhudson> pedronis: hi, this seems like something you would know? :) ^
[08:27] <Chipaca> mwhudson: pedronis might not be with us yet
[08:27] <mwhudson> oh right
[08:28] <mwhudson> timezones how do they even
[08:28] <Chipaca> mwhudson: well, it's 10:30 in his tz
[08:28] <mwhudson> oh
[08:28] <mwhudson> heh
[08:28] <Chipaca> mwhudson: but it's a national holiday in the helvetic confederacy
[08:29] <mwhudson> ah
[08:29] <mwhudson> i guess i should email really
[08:38] <mwhudson> Chipaca: 'interdenominational-counterintelligences' lol
[08:38] <popey> Trips off the tongue.
[08:39] <Chipaca> mwhudson: popey: and that's just unrepresentative-herpetology.~1~, the next version is going to be even better, i hear
[08:41] <Chipaca> I'd tell you what channel to get it from, but it won't fit in this margin
[08:41] <mwhudson> i wonder how badly this would break the snap list view i'm making for subiquity
[08:42] <Chipaca> mwhudson: answering that question is why I made it :-)
[08:43] <Chipaca> mwhudson: to be clear, package name, version, and summary are max length. Revision in particular is not, because I got lazy.
[08:43] <mwhudson> heh
[08:43] <mwhudson> what is the max revision length?
[08:44] <Chipaca> mwhudson: undocumented
[08:44] <mwhudson> len(str(sys.maxint))?
[08:44] <mwhudson> i don't know that the store team would be super happy with you uploading billions of reviions
[08:44] <Chipaca> mwhudson: probably log2((1<<31)-2) or something silly like that
[08:45] <Chipaca> mwhudson: exactly, too lazy to change country again because of being on the run from the store people
[08:45] <mwhudson> hahaha
[08:48] <mwhudson> ok now to make this stuff actually talk to snapd
[08:49] <Chipaca> mwhudson: what're you writing in?
[08:49] <mwhudson> Chipaca: python
[08:50] <mborzecki> anyone seen https://paste.ubuntu.com/p/wRXzv8vJQK/ ?
[08:50] <Chipaca> mwhudson: if you have requests, the http snap uses that + requests-unixsocket
[08:50] <mwhudson> Chipaca: that was what i had found with google
[08:51] <Chipaca> mwhudson: I'm sorry I'm only on par with, and not better than, a multi-billion corporation
[08:51] <mwhudson> Chipaca: i trust your recommendation a lot more!
[08:52]  * Chipaca wonders at the wisdom of that
[08:54] <pedronis> Chipaca: I'm around now, is not a holiday for me (next Monday is)
[08:54] <ryan____> hi!
[08:55] <ryan____> need help understanding prime and stage
[08:56] <Chipaca> pedronis: ah! my bad :-)
[08:56] <Chipaca> pedronis: mwhudson had a question for you about becoming a farmer or something about seeds
[08:57] <Chipaca> ryan____: that's a bit vague :-) what do you need help with?
[08:59] <pedronis> mwhudson: either is fine, depends what you can actually do, to install things the system needs to have been booted from the installed fs
[09:00] <mwhudson> pedronis: i have managed to 'boot' the installed system in a container
[09:01] <mwhudson> and then install snaps, even
[09:01] <ryan____> understanding whats the difference in purpose between prime and stage.
[09:03] <Chipaca> ryan____: 'prime' is what the snap ends up as
[09:03] <pedronis> mwhudson: so  that boot seeds the real system I suppose, the issue there is at also starts the holding period for refreshes which we might want or not
[09:03] <Chipaca> ryan____: you can even install it using 'snap try'
[09:03] <om26er> What could cause snap build process to change the signature of a repackaged binary ?
[09:03] <om26er> case: https://github.com/snapcrafters/sublime-text/issues/16
[09:03] <Chipaca> ryan____: it gets populated from 'stage', which is where parts install to
[09:03] <mwhudson> pedronis: hmm yes
[09:04] <pedronis> mwhudson: I think both approaches are workable, it's a bit of a matter of what's the speed of one or the other and details like that one
[09:04] <pedronis> also the speed of the first boot after install
[09:05] <Chipaca> om26er: differ from what?
[09:05] <ryan____> it sounds like a small step from build to prime
[09:05] <om26er> Chipaca: from the tarball downloaded from the official release channel
[09:06] <mborzecki> zyga: any idea what's the status of https://github.com/snapcore/snapd/pull/4369 ? do you still plan to introduce the attribute? (i can look into that if needed)
[09:06] <mup> PR #4369: add write permission to optical-drive interface <Decaying> <Created by diddledan> <https://github.com/snapcore/snapd/pull/4369>
[09:06] <om26er> the binary sublime_text under this tar https://download.sublimetext.com/sublime_text_3_build_3176_x64.tar.bz2 is different from what we have in the snap, even though the source is the same. The upstream is concerned chipaca
[09:07] <Chipaca> om26er: snapcraft is probably patching the binary using patchelf
[09:07] <Chipaca> om26er: is this a classic snap?
[09:07] <om26er> Chipaca: yes, that's true
[09:07] <Chipaca> om26er: which is true
[09:07] <om26er> hmm, would need to add https://github.com/snapcrafters/android-studio/blob/master/snap/snapcraft.yaml#L31 ?
[09:08] <om26er> Chipaca: we need some kind of articulated response to the upstream on that one.
[09:08] <Chipaca> om26er: who is creating the snap?
[09:08] <om26er> Chipaca: we (snapcrafters)
[09:09] <Chipaca> om26er: so, you need to figure out what you're doing to the binary, and explain it to them
[09:09] <om26er> Wimpress: ^
[09:11] <popey> Wassup?
[09:11] <om26er> I kind of was not expecting the signature to change, so someone with more knowledge of why and how that is happening could produce a better response :)
[09:11] <om26er> popey: https://github.com/snapcrafters/sublime-text/issues/16
[09:11] <Chipaca> om26er: if it's running patchelf, it's changing the binary; if it's changing the binary, its signature will change
[09:12] <Chipaca> and if patchelf is causing crashes on linux, it's doing it wrong
[09:12] <popey> you can disable patchelf
[09:13] <zyga> mborzecki: that is blocked on a decision by gustavo
[09:13] <popey> om26er: use the build-attributes -no-patchelf
[09:13] <zyga> sorry, I was afk for a moment, we're giving away baby gear and a friend came over for a summer kiddy bed
[09:13] <popey> om26er: see android-studio
[09:13] <om26er> popey: sure, we did that for Android Studio a bit ago, it was not starting at all.
[09:13] <om26er> yeah
[09:14] <om26er> I will do a PR but would be better if you could write on that issue popey
[09:20] <mup> PR snapd#5134 closed: Shrink image generated with snap prepare <Created by kubiko> <Closed by kubiko> <https://github.com/snapcore/snapd/pull/5134>
[09:26] <popey> om26er: ok leave it with me
[09:28] <Chipaca> popey: resurrecting #1739097 if you could give it a read
[09:28] <mup> Bug #1739097: "This leaves <snap> tracking edge." <snapd:In Progress> <https://launchpad.net/bugs/1739097>
[09:28] <om26er> I do have a PR though https://github.com/snapcrafters/sublime-text/pull/17 but I still am not able to build it because snapcraft eats 100 cpu during build and never gets further.
[09:28] <mup> PR snapcrafters/sublime-text#17: Dont use patchelf <Created by om26er> <https://github.com/snapcrafters/sublime-text/pull/17>
[09:30] <Chipaca> om26er: I'd suggest checksumming that before declaring it fixed
[09:30] <Chipaca> om26er: also, dude, if you don't explain _why_ you're doing a change, how do you remember why you did things a year from now?
[09:33] <popey> om26er: hang fire for now. I'm building and testing locally
[09:33] <popey> I'll respond to upstream
[09:34] <om26er> popey: yep, that would make sense.
[09:35] <om26er> Chipaca: I added some description now, thanks for the reminder.
[09:40] <mup> PR snapd#5134 opened: Shrink image generated with snap prepare <Created by kubiko> <https://github.com/snapcore/snapd/pull/5134>
[09:51] <mborzecki> pstolowski: is https://github.com/snapcore/snapd/pull/4968 still blocked?
[09:51] <mup> PR #4968: ifacemgr: remove stale connections on startup <Created by stolowski> <https://github.com/snapcore/snapd/pull/4968>
[09:52] <pstolowski> mborzecki: nope, let me merge master back
[09:52] <mborzecki> ok
[09:53] <mborzecki> looks like google:ubuntu-16.04-32:project is failing, is the image broken? i'm suspecting the apt lock file was left behind
[10:07] <mborzecki> heh, when starting manually project prepare on ubuntu-16.04-32 works just fine
[10:53] <zyga> mborzecki: maybe unattended updates?
[10:59]  * zyga needs more coffee 
[11:09] <Son_Goku> zyga, did cachio finally get the f28 google images up?
[11:09] <zyga> I haven't touched that, I will ask cachio when he shows up
[11:09] <Son_Goku> I had to spin new packages yesterday due to failing scriptlet: https://copr.fedorainfracloud.org/coprs/ngompa/gce-oslogin/build/753629/
[11:09] <zyga> thank you again for preparing that package
[11:10] <zyga> my main focus this week is to go through the reviews
[11:11] <Son_Goku> gce-oslogin was a crappy package
[11:11] <Son_Goku> but I fixed it: https://copr-be.cloud.fedoraproject.org/results/ngompa/gce-oslogin/fedora-rawhide-x86_64/00753629-google-compute-engine-oslogin/google-compute-engine-oslogin.spec
[11:12] <zyga> Son_Goku: I'm not sure how google handles that, can you send your improvements back?
[11:12] <Son_Goku> they require a CLA
[11:12] <Son_Goku> and I hate signing those
[11:13] <Son_Goku> I actually more or less rewrote the spec
[11:13] <Son_Goku> so I should have dropped the ASL license header in the file
[11:14] <Son_Goku> I probably will drop it actually
[11:14] <Son_Goku> since my spec file shares ~2-4 lines with the original
[11:14] <Son_Goku> and that's it
[11:23] <kjackal> Hi snappy people, I have a deb that I should plave in a snap. Normaly that would go into the staged-packages but that specific deb is from a non-bleshed repository, what can I do?
[11:24] <kjackal> *place
[11:29] <popey> kjackal: you could add it as a part, plugin type dump, source, url to the deb.
[11:30] <kjackal> thanks popey, do you happen to have an example yaml for that?
[11:33] <kjackal> popey: something like this: https://github.com/snapcrafters/mattermost-desktop/blob/master/snap/snapcraft.yaml I guess
[11:33] <popey> not off the top of my head, no.
[11:48] <zyga> hmm
[11:48]  * zyga is stuck with a test failure on code he is hacking 
[11:51]  * cachio afk
[11:55]  * Chipaca lunch
[11:57] <pedronis> pstolowski: I asked a question about #4767 in your latest forum topic
[11:57] <mup> PR #4767: interfaces: disconnect hooks <Critical> <Squash-merge> <Created by stolowski> <https://github.com/snapcore/snapd/pull/4767>
[11:57] <pstolowski> pedronis: i saw it, thanks
[12:33] <mborzecki> zyga: https://paste.ubuntu.com/p/ydn2KZBTHV/
[12:34] <zyga> nice
[12:34] <zyga> so that's exactly what we tarballed
[12:34] <zyga> but created programmatically, right?
[12:35] <mborzecki> -rwxr-xr-x 1 root root 8 2018-05-14  ﻿uboot.env
[12:35] <mborzecki> -rwxr-xr-x 1 root root 8 2018-05-14  uboot.env
[12:35] <mborzecki> yes
[12:36] <mborzecki> zyga: i think that core fssck is to blame
[12:37] <zyga> I afgree
[12:37] <zyga> it looks like a bug, clearly, there
[12:37] <mborzecki> when i use fsck.vfat from host the entries are looking good
[12:38] <zyga> hmm
[12:38] <zyga> hold on, and which fsck are we using?
[12:39] <mborzecki> dang, hsot fsck does the same too
[12:40] <mborzecki> zyga: well, the one from core right?
[12:41] <Chipaca> mborzecki: zyga: that's what mvo's patch to dosfstools fixes
[12:41] <Chipaca> https://github.com/dosfstools/dosfstools/pull/83
[12:41] <mup> PR dosfstools/dosfstools#83: [RFS] check.c: do lfn_remove  on auto_rename() <Created by mvo5> <https://github.com/dosfstools/dosfstools/pull/83>
[12:41] <mborzecki> anyways, fsck 4.1 and 3.0.28 (from core snap) appear to do the same, i end up with 2 entries, one has only shortname (uboot.env) and the other shortname (fsck0000.000) and lfn (uboot.env)
[12:42] <mborzecki> Chipaca: right
[12:42] <Chipaca> if upstream had at least ACKed the issue we could distropatch it
[12:42] <Chipaca> if they don't, we'd have to be a lot more sure about it fixing the core issue
[12:42] <mborzecki> once mounted this appears as 2 files with identical names ;)
[12:42] <mborzecki> (should kernel at least display it differently?)
[12:43] <Chipaca> mborzecki: there are options to mount to control that
[12:43] <Chipaca> mborzecki: i think the one mvo suggested was win95
[12:43] <Chipaca> (if you look for win95 in man mount you'll see the options)
[12:43] <mborzecki> aah, it was in mvo's change, let me try that, i'm using check=s right now
[12:43] <zyga> try dosbox
[12:44] <mborzecki> -rwxr-xr-x 1 root root 8 2018-05-14  ﻿uboot.env
[12:44] <mborzecki> -rwxr-xr-x 1 root root 8 2018-05-14  UBOOT.ENV
[12:45] <mborzecki> all ups is the one without lfn
[12:45] <Chipaca> this way at least we can point to one or t'other :-)
[12:51] <mup> PR snapd#5155 opened: interfaces/apparmor: use strict template on openSUSE tumbleweed <Created by zyga> <https://github.com/snapcore/snapd/pull/5155>
[12:51] <zyga> mborzecki: so on dosbox things work better?
[12:52] <mborzecki> zyga: you can tell which file is which
[12:52] <zyga> hmm
[12:52] <zyga> can we mount things like that in linux?
[12:52] <zyga> mborzecki, Chipaca: can we land https://github.com/snapcore/snapd/pull/5142 ?
[12:52] <mup> PR #5142: many: add "snap debug sandbox-features" and needed bits <Squash-merge> <Created by zyga> <https://github.com/snapcore/snapd/pull/5142>
[12:53] <Chipaca> zyga: why squash-merge?
[12:53] <zyga> junk in history
[12:53] <Chipaca> zyga: that usually means you want to backport it
[12:53] <Chipaca> and that concerns me :-)
[12:53] <Chipaca> s/backport/cherrypick/
[12:53] <zyga> no, I don't need that :")
[12:54] <zyga> my main motivation is to use that branch
[12:54] <zyga> to filter tests better once we do the opensuse experiment
[12:54] <zyga> cachio: would it be hard to add opensuse tumbleweed to CI?
[12:55] <zyga> cachio: even as a manually used image
[12:55] <zyga> I could definitely use it
[12:58] <mborzecki> yup TW makes sense
[12:59] <mborzecki> sort of early upgrade of the image is there for arch already, tw could do the same
[12:59] <mborzecki> although iirc opensuse can do more than 1 kernel installed
[13:03] <niemeyer> Chipaca, cachio: Coming?
[13:03] <Chipaca> niemeyer: trying to
[13:03] <niemeyer> :)
[13:07] <Son_Goku> mborzecki, Fedora and openSUSE support multiversioned kernel packages
[13:07] <mborzecki> Son_Goku: thanks, fedora i know about, but i didn't remember how suse does it
[13:07] <Son_Goku> same exact way
[13:08] <mborzecki> well, at least some drstros as sane ;)
[13:08] <Son_Goku> pretty much all RPM-based distributions use multiversion/slotted kernel packages
[13:31] <zyga> pstolowski: feedback con 5032
[13:33] <pstolowski> zyga: thanks, looking
[13:34] <pstolowski> zyga: ouch, thanks, mistake in conflict resolution
[13:34] <zyga> W: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list.d/google-cloud-sdk.list:1 and /etc/apt/sources.list.d/google-cloud-sdk.list:2
[13:34] <zyga> apart from apt lock being held
[13:35]  * zyga -> lunch 
[13:35] <zyga> https://www.youtube.com/watch?time_continue=1&v=F8nrpe0XWRg <- interesting, so far watched about 1/3rd though
[14:03] <mborzecki> off to pick up the kids
[14:08] <pedronis> pstolowski: I did a first pass on #4767 , have also some questions there
[14:08] <mup> PR #4767: interfaces: disconnect hooks <Critical> <Squash-merge> <Created by stolowski> <https://github.com/snapcore/snapd/pull/4767>
[14:09] <pstolowski> pedronis: ty, checking
[15:05] <pedronis> zyga: #4889 needs a j-dstrand review ?
[15:05] <mup> PR #4889: cmd/snap-update-ns: don't trespass on host filesystem <Created by zyga> <https://github.com/snapcore/snapd/pull/4889>
[15:46] <zyga> pedronis: not sure, I think it doesn't but we can add one
[15:46] <zyga> pedronis: jamie is a bit busy lately so I think I will wait for a +1 from gustavo first
[15:54] <cachio> zyga, pedronis FYI issue on xenial 32bits fixed
[16:13] <zyga> cachio: what was the issue?
[16:17] <cachio> zyga, sometimes when the execution was done from a fast machine
[16:17] <cachio> zyga, the system tried to do a release upgrade because it is a new lts
[16:18] <cachio> zyga, and it was locking
[16:18] <cachio> I updated the file /etc/update-manager/release-upgrades
[16:18] <cachio> and the problem is gone
[16:20] <zyga> thanks!
[16:20] <zyga>  that is great
[16:21] <cachio> I could reproduce it from canonistack
[16:21] <cachio> zyga, imposible from here
[16:34] <kenvandine> is there a way to unrelease a revision from a specific track using the command line?
[16:35] <kenvandine> we can't use the web UI because the track in question doesn't appear in the web UI
[16:35] <noise][> kenvandine: you can either release a different revision to the channel or close it
[16:39] <kenvandine> noise][, ah, then they can release a revision to that track again later?
[16:41] <kenvandine> this is for the esr channel from mozilla, they want to test releasing the snap to esr60/stable then unpublish it until they are sure
[16:42] <kenvandine> noise][, although i'm not sure why :)
[16:50] <noise][> kenvandine: yes, they can release to that track/risk and then close it again
[16:52] <kenvandine> noise][, thx
[16:54]  * cachio afk
[16:59] <Chipaca> ttfn peeps
[17:08] <zyga> rain!
[17:11] <ogra_> butter!
[17:12] <mup> PR snapcraft#2119 closed: repo: automatically prune unneeded stage-packages <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2119>
[17:16] <thresh> me dances
[17:16] <thresh> or rather
[17:16]  * thresh dances
[17:23] <popey> :)
[17:50] <zyga> mborzecki: there?
[18:02] <mborzecki> mborzecki: yeah
[18:02] <mborzecki> pfff 5080 failed because master changed :(
[18:02] <zyga> ah
[18:02] <zyga> I re-ran tests on nearly all failing branches
[18:02] <zyga> and we have very very green set of PRs
[18:03] <mborzecki> 'merge material'
[18:04] <zyga> mborzecki: but I wanted to ask about https://github.com/snapcore/snapd/pull/5142
[18:04] <mup> PR #5142: many: add "snap debug sandbox-features" and needed bits <Squash-merge> <Created by zyga> <https://github.com/snapcore/snapd/pull/5142>
[18:05] <zyga> it's got one +1 and is green
[18:05] <mborzecki> ah, forgot to +1 it
[18:05] <mborzecki> btw. updated #5080
[18:05] <mup> PR #5080: many: support 'system' nickname in interfaces <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/5080>
[18:06] <zyga> thanks, looking
[18:08] <zyga> thanks!
[18:08] <mup> PR snapd#5142 closed: many: add "snap debug sandbox-features" and needed bits <Squash-merge> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5142>
[18:37] <zyga> it's raining again
[18:37] <zyga> no bike today
[18:39] <zyga> it's raining again
[18:39] <zyga> ah, I'm online now :)
[18:41] <sveinse> I'm having problems using docker under snap. When trying to run docker build, I get "unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /var/lib/snapd/void/Dockerfile: no such file or directory"
[18:42] <zyga> sveinse: ha, that's pretty interesting
[18:42] <zyga> notice the path
[18:42] <sveinse> it is
[18:42] <zyga> the "void" directory is used when the path you were in cannot be represented in snap context
[18:43] <zyga_> sveinse: note the path of the Dockerfile, the "void" directory is used when your original path cannot be represented inside the snap
[18:43] <zyga> ping pong
[18:44] <zyga_> (my network is flaky on my laptop)
[18:44] <sveinse> Still here :D
[18:44] <zyga_> what was your working directory when you ran the command?
[18:46] <sveinse> zyga_: My directory containing the Dockerfile. I ran "docker build -t ubuntu:myimage ."
[18:46] <sveinse> Just the way I'd use "normal" docker
[18:46] <zyga_> right... but was it?
[18:46] <zyga_> *what was it
[18:47] <thresh> is there a prebuilt snapcraft package built from git?
[18:47] <zyga_> snapcraft in the edge channel?
[18:48] <thresh> ...except from snapped version :)
[18:48] <thresh> I meant ubuntu/debian .deb packages, sorry.
[18:48] <zyga_> ah, I see
[18:48] <zyga_> well, soon it would work
[18:48] <zyga_> (the new snapcraft with virtualization)
[18:48] <zyga_> but that's WIP
[18:49] <thresh> the reason is I build my snap in a docker container, and this one does not come with systemd as init, etc, which makes snapd unpossible to run
[18:49] <zyga_> ah, I see
[18:49] <zyga_> sergiusens: ^ is there a ppa with snapcraft deb?
[18:50] <sergiusens> zyga: no, we don't do PPAs
[18:51] <sergiusens> thresh: you could use snapcore/snapcraft:edge (or look at the docker file for it and adapt yours)
[18:52] <thresh> righto
[18:52] <sveinse> zyga_: this is the Dockerfile: https://bpaste.net/show/cd8aed8faf03
[18:53] <thresh> thanks!
[18:53] <zyga_> sveinse rather than the contents of the docker file I was asking about its location
[18:53] <zyga_> sveinse the "void" directory shows up whenever you are in a directory that doesn't exists from the point of view of the snap's filesystem
[18:53] <zyga_> sveinse for example
[18:53] <zyga_> sveinse mkdir /foo
[18:53] <zyga_> sveinse cd /foo
[18:54] <zyga_> sveinse snap run --shell hello-world
[18:54] <sveinse> zyga_: /home/sveinse/sp/build/ubuntu/ubuntu-14.04-docker/tmp.docker/
[18:54] <zyga_> hmm
[18:54] <zyga_> that directory should exist just fine
[18:55] <zyga_> can you export SNAP_CONFINE_DEBUG=yes and run the command again?
[18:55] <sveinse> I even run "cd $(realpath "$PWD")" prior to calling docker to ensure I'm in a symlink-free path
[18:58] <sveinse> zyga_: https://bpaste.net/show/d6e3b95f6276
[18:59] <zyga_> ha
[18:59] <zyga_> DEBUG: cannot remain in /srv/home/common/sp/build/ubuntu/ubuntu-14.04-docker/tmp.docker, moving to the void directory
[18:59] <zyga_> your home directory is not /home, it's really /srv/home/common
[18:59] <zyga_> is this a NFS mount?
[19:00] <sveinse> no, its another partition. I dualbooted between 18.04 pre-release and 17.10, so I had a common partition for all non-distro related home files
[19:00] <zyga_> please use a bind mount, this will resolve the issue
[19:01] <zyga_> that is, make your home directory really appear in /home, using a bind mount
[19:01] <zyga_> that's mount --bind /old /new
[19:01] <zyga_> or mount --rbind /old /new if you need recursive
[19:01] <zyga_> you can also put this into /etc/fstab
[19:01] <sveinse> is *is* a bindmount. I just don't want it at /home or /home/user
[19:01] <zyga_> brb
[19:01] <zyga_> sveinse it must be in your $HOME
[19:02] <sveinse> ok, then, sorry, I won't change that now. So I'll revert to the apt based docker then.
[19:04] <zyga_> sveinse may I ask why you don't want that to appear as /home/$LOGNAME?
[19:05] <zyga_> it's not easy to support arbitrary locations for us
[19:05] <zyga_> so I want to know the motivation better
[19:08] <sveinse> zyga_: sure, here's my use-case: As said, I have multiple distros running. And my experience with sharing /home between these have failed miserably in the past, so each distro has its own individual /home. So all I have which is worked on from both distros is put in /home/common, which is a bind-mount to a third partition. Everything is then simply symlinked from my to the common dir, which takes 3
[19:08] <sveinse> minutes to setup.
[19:08] <zyga_> sveinse so if you use /home/$LOGNAME as your home (separate home for each distribution) and use /home/common as a bind mount from /srv/whatever it would work again
[19:09] <zyga_> do you see what I mean?
[19:10] <sveinse> Actually the real mount for the /home/common bind mount is actually /srv, so testing that wouldn't be too hard
[19:10] <zyga_> you can just bind mount now (without touching your fstab)
[19:13] <sveinse> zyga_: wait, I was wrong. I have it oposite. /home/ is bind mount to /srv/home-18.04 and then /home/common being a symlink to /srv/home/common
[19:14]  * zyga_ has IRL interrupt
[19:17] <sveinse> zyga_: I gotta go, my time box for this is up, so I have to revert to the other docker. Thanks for your help.
[19:25] <zyga_> sveinse o/
[19:35] <popeycore> gnnnnnnn
[19:35] <popeycore> installing a snap made my x session explode. *again*
[19:36] <jhobbs> How do I set a proxy for snapd, and only snapd, to use? I don't want to set a system wide proxy
[19:36] <jhobbs> do I use "snap set core proxy.https=http://my.proxy" ?
[19:47] <Pharaoh_Atem> jhobbs: you can't in Ubuntu
[19:47] <Pharaoh_Atem> since it uses /etc/environment for environment variables
[19:50] <jhobbs> Pharaoh_Atem: that doesn't preclude applications from having their own proxy settings
[21:51] <mwhudson> jhobbs: i think the snap set thing yes, although i haven't tried to use it, only read the code :)
[21:55] <jhobbs> mwhudson: ok, it didn't seem to work for me, and i don't know enough to get any feedback from snapd about whether it's using it or not, so I found a way to do it via environment variables instead - thanks for looking into it
[21:55] <jhobbs> reading the code is the one thing i didn't do
[21:55] <mwhudson> heh
[21:55] <mwhudson> i hope to use it soon so well
[21:56] <mwhudson> there's always a systemd drop-in i guess
[21:56] <jhobbs> yes, that's what i used
[21:56] <jhobbs> http://paste.ubuntu.com/p/K8VncJv4vp/
[21:57] <mwhudson> uh by looking at this code calling snap set core proxy.http=... *writes* to /etc/environment
[21:59] <mwhudson> but i suspect it does not actually update the proxies used by snapd
[22:00] <mwhudson> ?
[22:00] <mwhudson> so you need to snap set ... and then restart it to get snapd to notice...
[23:35] <mwhudson> jhobbs: oh heh the snap set core proxy.* is only supported on core systems it seems