/srv/irclogs.ubuntu.com/2017/06/19/#snappy.txt

mupPR snapd#3477 closed: tests: fix snap create-key by restarting automatically rng-tools <Created by sergiocazzolato> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3477>05:57
zygao/06:04
morphiszyga: hey!06:45
morphiszyga: can you merge https://github.com/snapcore/snapd/pull/3470 ?06:45
mupPR snapd#3470: interfaces/builtin: sync connected slot and permanent slot snippet <Created by morphis> <https://github.com/snapcore/snapd/pull/3470>06:45
mvozyga: hm, the idea of using snap-update-ns to fixup the permissions of /var/lib will unfortunately not work because it looks like we don't run that for the snaps when snapd itself (e.g. fro mthe deb) is updated. context is the incorrect permissions of /var/lib inside the namespace06:48
mvozyga: and good morning :) - and good morning to morphis too!06:48
morphismvo: morning!06:48
mvozyga: I suspect this needs to go into snap-confine itself (the fixup code). slightly sad about this06:50
morphismvo: can you have a look at https://github.com/snapcore/snapd/pull/3449 and merge if it is fine for you?06:51
mupPR snapd#3449: tests/lib: generalize RPM build support <Created by morphis> <https://github.com/snapcore/snapd/pull/3449>06:51
mvomorphis: sure06:51
zygamorphis: done06:52
zygamvo: hey06:52
mupPR snapd#3470 closed: interfaces/builtin: sync connected slot and permanent slot snippet <Created by morphis> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3470>06:52
morphisthanks!06:52
* zyga is sitting amids boxes and unpacked things everywhere06:52
mvomorphis: sure06:52
mvozyga: woah, you are back?06:52
mupPR snapd#3449 closed: tests/lib: generalize RPM build support <Created by morphis> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3449>06:53
zygamvo: I won't be much help this week06:53
mvozyga: no worries06:53
zygamvo: I'm sick (cold) *and* sunburned06:53
mvozyga: have you moved too?06:54
zygamvo: yesterday we had a surprise party from our closest friends06:55
zygamvo: no, I'm moving on Thursday06:55
zygamvo: extra family members are here to help us move06:55
zygamvo: we'll land in Poland on Friday at 1 AM or something like that06:55
mvozyga: woah, good luck07:03
mvozyga: and get well07:03
zygamvo: I'll aks you for a review of the initrd test support soon07:05
* mvo takes a short break07:20
morphismvo, zyga: if you have another min, https://github.com/snapcore/snapd/pull/345007:43
mupPR snapd#3450: packaging/{opensuse,fedora}: allow package build with testkeys included <Created by morphis> <https://github.com/snapcore/snapd/pull/3450>07:43
mupPR snapd#3450 closed: packaging/{opensuse,fedora}: allow package build with testkeys included <Created by morphis> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3450>08:21
morphismvo: thanks!08:21
mvomorphis: yw!08:24
mupPR snapd#3487 closed: tests: reenable help test on ubuntu and debian systems <Created by fgimenez> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3487>08:51
ogramvo, any opinion on bug 1698107 ?08:51
mupBug #1698107: Ubuntu Core images should include ntfs-3g <Snappy:New> <https://launchpad.net/bugs/1698107>08:51
mupPR snapd#3222 closed: many: fix test cases to work with different DistroLibExecDir <Created by morphis> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3222>08:54
mvoogra: sounds reasonable, it seems like its pretty small08:55
mupPR snapd#3391 closed: tests: reboot after upgrading to snapd on the -proposed pocket <Created by fgimenez> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3391>08:56
mvoif someone could have a look at 3482 that would be cool, very straightforward review08:57
morphismvo: yeah!08:57
zygare08:57
morphiszyga: you wont believe it: https://github.com/snapcore/snapd/pull/322208:57
mupPR snapd#3222: many: fix test cases to work with different DistroLibExecDir <Created by morphis> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3222>08:57
mvomorphis: ha! great job for getting it in :)08:58
zygamorphis: nice, very nice08:58
* zyga just got rid of the 1st aquarium08:58
zyganow quick breakfast and back to work08:58
ogramvo, yeah.1.5MB uncompressed08:58
* ogra will add it 08:58
zygamvo: done09:00
mupPR snapd#3482 closed: asserts: support timestamp and optional disabled header on repair <Created by pedronis> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3482>09:00
ograzyga, i see weird "cookie not found" errors on all my core boards since about last week ... is that snap-confine ?09:00
zygaogra: that's the new context thing09:00
zygapstolowski: ^^09:01
zygapstolowski: something you may want to know about09:01
zygaogra: are those actual errors or just messages that are logged but stuff still works?09:01
ograwe should at least fix the error message to have a final newline if we want to chow it all the time :)09:01
mupPR snapd#3467 closed: interfaces/greengrass-support: add support for Amazon Greengrass as a snap <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3467>09:01
ogra*show09:01
zygaogra: oh, indeed09:01
mvozyga: 3441 has a comment from pedronis, do you think you can address it or shall I have a look, looks like a trivial change09:01
ograzyga, it seems to happen if the app actually takes a while to start up ... i can pretty reliably reproduce it by running classic (and initially though it was only there) ... but yesterday i ran htop on a heavy loaded board and saw it for htop as well09:02
ograpstolowski, ^^09:02
zygamvo: I'll do it now09:03
zygamvo: thank you for spotting that09:03
mvozyga: thank you, I think its pretty close09:03
mvozyga: 3464 probably needs an ok from gustavo, wdyt? pr itself looks fine (assuming everything is identical just split up :)09:03
pstolowskizyga, ogra right. we will complain for already installed snaps that don't have the cookie (since we generate cookies only when snap is installed). but it's a warning only, everything should work09:04
ograpstolowski, prefixing it with a "W:" or some such might help ... and the message should really get a final newline/linewrap at the end09:04
zygamvo: yes, I have a informal +1 from jdstrand and once we have formal reviews it should go in09:05
zygapstolowski: can you check about that newline09:05
zygapstolowski: probably error is doing that, error is not used in the code much09:05
ograin classic i always like:09:05
ograogra@sabrelite:~$ sudo classic09:05
ogracannot open cookie file /var/lib/snapd/cookie/snap.classic(classic)ogra@sabrelite:~$09:05
ogra*i always end up like09:05
mvozyga: great, if there is agreement I will try to review today09:06
pstolowskizyga, ogra ok, will add a new line. but i don't think we use 'W:' to signify warnings anywhere?09:06
mvofgimenez: quick question about 3474 - if /etc/gai.conf is not writable on core, why didn't the tests explode on core when it tries to write to /etc/gai.conf ?09:06
zygapstolowski: W: ?09:06
ograwell ... indicate somehow that it isnt an error ... doesnt need to be "W:"09:06
ograelse we'll get bugs about it09:07
mvopstolowski: is this warning helpful in any way to the user? I mean, is there anything that the user can do to get rid of if?09:07
mvopstolowski: I guess what I'm asking is - can we somehow fix things so that we don't have to print this message and explain something to the user?09:07
pstolowskimvo, reinstall affected snap would remove this warning09:07
pstolowskimvo, an alternative would be to generate all the missing cookies (for snaps installed before the feature was introduced) on snapd start09:08
mvopstolowski: if its not too much hassle that sounds much better than to ask all $users to do this manually09:08
* ogra tries ... 09:09
mupPR snapd#3466 closed: tests: extend core-revert test to cover bluez issues <Created by fgimenez> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/3466>09:09
zygapstolowski: I think you just said what has to be done09:09
zygapstolowski: it's ain internal implementation deatail09:09
zygapstolowski: similar in principle to security refresh09:10
pstolowskiogra, if you're trying the reinstall, make sure you don't have any old revisions of that snap installed09:10
ograbah, you tell me now :P09:10
pstolowskizyga, mvo ok, i'll do that09:10
fgimenezhey mvo welcome back! on linode the core system follows a different path than on the external backend, the former starts with a classic system (/etc/gai.conf is writable at that stage) which eventually reboots into a core system, the latter is a core system from the start (with /etc/gai.conf in a read-only partition from the beginning)09:12
ograpopey, hey ... you recently asked abotu that https://github.com/ogra1/nanopi-neo-gadget (and also https://github.com/ogra1/orangepi-zero-gadget) ... still struggling with a kernel atm ... but i have both boards now09:13
ograogra@sabrelite:~$ sudo classic09:14
ogra(classic)ogra@sabrelite:~$09:14
ograpstolowski, confirmed ... ^^^09:14
pstolowskiogra, warning is gone, that is?09:14
ograyeah09:14
mvofgimenez: aha, so this fails when you run it against a real ubuntu-core extrenal device like a pi2?09:14
pstolowskiok. ill fix it09:14
mvopstolowski: thank you!09:14
popeyogra: nice!09:15
ograthe nanopi is soooo cute!09:15
mvozyga: I added one more comment into 3441 (hopefully trivial)09:15
* ogra is in love :)09:15
zygamvo: looking09:16
zygamvo: replied09:16
mvozyga: thank you. and do let me know if I can take any burden of your shoulder, it sounds like you have a bit of a stressful week ahead of you. i.e. I can fixup anything for you in the PRs09:16
fgimenezmvo: yes, exactly09:17
zygamvo: just running tests there09:18
fgimenezmvo: with kvm it should fail too, any core system using the external backend09:18
mvozyga: ta09:18
zygamvo: the encoding is done by the response codec I suspect, I'm not doing that myself09:18
mvofgimenez: thats fine, I was just wondering why we have not seen it in spread09:19
zygamvo: I could just convert it to a string, I think it's not any harm09:19
mupPR snapd#3474 closed: tests: fix ipv6 disable for ubuntu-core <Created by fgimenez> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3474>09:20
mvoif 3317 gets a second review it can go in too - we may need a gustavo review for this though09:21
fgimenezmvo: yes, we need core spread test on actual systems to contrast linode results and prevent the tweaking we do there to mask potential problems, hopefully as soon as we have the jenkins instance up this will be automated09:21
fgimenezmvo: thx! :)09:21
popeyogra: which one did you get?09:22
ogrananopi neo09:22
ograi'm pondering to also get the air09:23
ogramy prob is currently that you cant cross compile our aarch64 kernel and the armhf build doesnt seem to boot09:24
popeythe air is the super tiny one, right?09:24
ograthey are both super tiny .. 2cmx2cm or so09:24
ograthe air is the one with additional wlan ... i think its a tad bit larger09:25
ogra(due to the wifi chip)09:25
popeyyeah, I'm interested in the wifi enabled one09:26
mupPR snapd#3476 closed: snap-confine: validate SNAP_NAME against security tag <Created by stolowski> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3476>09:26
pstolowskimvo, thanks ^ I was waiting for tests to pass but you were faster ;)09:27
mvofgimenez: another silly question - why do we see the issue with 3488 only on opensuse?09:27
mvopstolowski: all the relevant ones passed ;)09:27
ograpopey, https://www.voelkner.de/products/940892/Nanopi-Neo-Allwinner-512-MB-ohne-Betriebssystem.html is the one i got09:27
pstolowskimvo, right. i didn't expect any surprises anyway, the last commit just fixed the comments09:27
mvopstolowski: but yeah, sorry for that, I'm in a bit of ocd mode right now, the queue felt a bit overwhemling and we have a lot of low-hanging fruits09:27
popeyvery cute09:27
ograthats the air https://www.voelkner.de/products/966493/Nanopi-Neo-Air-512-MB-ohne-Betriebssystem-microSD-Bluetooth-Micro-USB-OTG.html09:28
VamsiIs it possible to install snaps on an ubuntu host from my phone?09:28
mvopstolowski: on the bright side, we are down to 27 PRs09:28
ograVamsi, you could install snapweb ... or use a terminal and ssh on your phone09:29
mupPR snapd#3445 closed: tests: add linode-sru backend <Created by fgimenez> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3445>09:29
zygaVamsi: we have a REST API for snapd but it is not yet exposed09:29
pstolowskimvo, good stuff09:30
mupPR snapd#3485 closed: tests: fix nightly suite <Created by fgimenez> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3485>09:31
ograppisati, do you happen to know how i can cross-build an aargh64 kernel ? i get complains about missing stack protector support in the compiler when i try09:32
fgimenezmvo: no idea, it's super strange, here is one of the logs with the failure , http://paste.ubuntu.com/24898301/ "flag provided but not defined: -tags withstagingkeys"09:34
ppisatiogra: sounds like you are trying to compile a recent kernel with an old toolchain09:34
ograppisati, yeah, the nanopi and orangepi are only supported in 4.11 onwards09:35
ograppisati, but i attempted the build inside an artful chroot ... so it should be the latest tootlchain we have (unless there is something in proposed that i'D need)09:35
ppisatiogra: uhm, that should be fine09:36
ppisatiogra: what's the error?09:36
ograsomething about "no support for -fstack-protector-strong"09:37
ograi dont have the exact error handy atm09:37
zygamvo: look at 3441 again please09:39
zygapedronis: ^ as well please09:47
pedronismvo: zyga: thanks for merging the repair PR,  I updated the forum topic to reflect these small tweaks09:56
mupPR snapd#3488 closed: tests: prevent quoting error on opensuse <Created by fgimenez> <Merged by stolowski> <https://github.com/snapcore/snapd/pull/3488>10:00
ograppisati, http://paste.ubuntu.com/24898399/ eher is the exact error10:03
ograppisati, the command i'm running is " ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- fakeroot debian/rules binary-headers binary-generic binary-perarch"10:06
ppisatiogra: but there you are actually compiling an amd64 kernel10:07
ograppisati, huh ?10:07
ograis CROSS_COMPILE not respected anymore ?10:07
ppisatiogra: that's what i usually use10:08
ppisatiogra: 'export ARCH=arm64; export $(dpkg-architecture -aarm64); export CROSS_COMPILE=aarch64-linux-gnu-'10:08
ppisatiand then 'fdrc etcetc'10:08
* ogra slaps forehead ... 10:09
ograexport $(dpkg-architecture -aarm64) ....10:09
ograsorry for the noise ... building now10:09
mvojdstrand: good news, the seccomp-bpf PR is green! but still quite a few comments to address10:09
ppisatiogra: np10:09
mvopedronis: thank you!10:10
ograppisati, oh, and FYI ... i couldnt get armhf generic to boot on my nanopi or orangepi ... (thats why i try arm64 now)10:11
ppisatiogra: 4.11?10:13
ograyep10:13
ppisatiogra: ouch10:13
ograi get "Loading kernel ..." and thats it10:13
ppisatiogra: do you have uboot running? you could dump the location of the printk buffer10:14
ograhow do i do that10:14
ograi have earlyprintk and the right console= arg on the cmdline (verified a thousand times) ... so if it prints anything there it should show up10:15
ppisatiogra: http://elinux.org/Debugging_by_printing10:15
* ogra reads10:16
ppisatiogra: after the conversion do DT, i never got earlyprintk to work10:16
ograah10:16
ograk10:16
ppisatiogra: but i didn't try hard, honestly10:16
ograi'll resort to the printk hacker if arm64 doesnt work either10:17
ogra*hack10:17
ograseemingly the allwinner toolchains are all aarch64 ...  so i have some hope that an arm64 build might work better10:17
mupPR snapd#3441 closed: cmd,daemon: add debug command for displaying the base policy <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3441>10:23
* zyga -> break10:44
ograbah crap ...10:56
ograls unpack/lib/firmware/4.11.0-6-generic/device-tree/allwinner/10:56
ograsun50i-a64-bananapi-m64.dtb  sun50i-a64-pine64.dtb  sun50i-a64-pine64-plus.dtb10:56
ogranot so helpful :/10:56
kalikiana_zyga: Can you confirm if /var/lib/snapd/snaps exists on all snapd systems? Or if there's an API to get that path (analogous to snap-mount-dir)?11:25
Chipacakalikiana_: dirs.SnapBlobDir?11:30
Chipacais that what you mean?11:30
zygakalikiana_: it exists on all systems AFAIK11:31
Chipacakalikiana_: what do you need it for?11:31
Son_Gokuit should exist everywhere11:31
Son_Gokuit's the snap download dir11:31
kalikiana_Chipaca: This doesn't have SnapBlobDir https://github.com/snapcore/snapd/wiki/REST-API11:32
kalikiana_Chipaca: I'm injecting snaps from the host into a LXD container11:32
kalikiana_I'd like to know that this can work on different snapd systems other than Ubuntu11:32
kalikiana_Son_Goku: Is that documented anywhere?11:33
Son_Gokuthe only location that differs is /var/lib/snapd/snap vs /snap11:34
Son_GokuDebian and Ubuntu and openSUSE use /snap11:34
Son_GokuFedora and Arch use /var/lib/snapd/snap11:34
* zyga feels worse and breaks11:35
zygamvo: I may miss standup, tomorrow should be a saner day11:36
ograkoza, how is the humminngboard ?11:36
=== rumble is now known as grumble
morphismvo, zyga: next one is ready: https://github.com/snapcore/snapd/pull/345511:45
mupPR snapd#3455: tests/main: use pkgdb function in more test cases <Created by morphis> <https://github.com/snapcore/snapd/pull/3455>11:45
* Chipaca ~> lunch11:49
niemeyerMorning all12:05
Vamsizyga: Thank you12:06
Vamsiogra: Thank you12:06
=== ahasenac` is now known as ahasenack
=== ahasenack is now known as Guest20728
pstolowskigood morning niemeyer !12:12
pstolowskimvo, to test the new logic for generating cookies on start I may need to write a spread test that stops snapd, removes some data from state.json and starts snapd back, but that sounds a little big ugly... but I can't think of any other way of simulating coming from an old snapd in a test. do you know any tests where we do anything like that?12:16
pedronispstolowski: the upgrade tests should also test it,  but we do have some tests that delete state.json at least12:20
pedronisor play with other /var/lib/snapd stuff12:20
mvopstolowski: was about to suggest the upgrade suite12:20
pstolowskipedronis, ok. if I delete state.json, doesn't this make snapd unaware of installed snaps?12:20
pedronispstolowski: sorry, that wasn't my point, just sayign we do play with state.json sometimes12:21
pedronisdon't remember punctual edits12:21
pstolowskipedronis, ah, I see12:21
pedronisbut probably because we didn't need them12:21
pstolowskipedronis, I see12:21
pedronispstolowski: but as mvo said, the upgrade tests should grow some checks about this as well12:22
pcercueiI have a bug report for Snapcraft on Debian, but it looks like I can't log into launchpad with a newly created Ubuntu One account12:22
pedronispstolowski: tests/upgrade/basic/task.yaml12:22
pcercueiso I guess that means I have two bug reports now :)12:22
cjwatsonpcercuei: what's the error?12:23
cjwatsonpcercuei: (with Launchpad login)12:23
pstolowskipedronis, mvo thanks, looking12:23
pcercueicjwatson: Ubuntu One requests some personal information (my full name + email), I select both and click "Yes, log me in"; back on launchpad.net I get a "Oops" page, error ID  OOPS-72c555d0a37007d571cd18978befd04a12:24
cjwatsonThanks, the OOPS ID was all I needed.12:24
cjwatsonI'll chase that up for you.12:25
pcercueithanks!12:26
pcercueithe actual bug I wanted to report: running latest 'snapcraft' on my Debian ends up with this:12:27
pcercuei"dpkg-query: error: --listfiles needs a valid package name but 'libc6' is not: ambiguous package name 'libc6' with more than one installed instance"12:27
pcercueiand that's because "dpkg -L libc6" is confused, because I have i686 and x86_64 versions12:28
mvopcercuei: this is something for kyrofa - the fix is probably simple, we need to teach snapcraft to always use the dpkg full name (i.e. pkgname:arch)12:31
mvopcercuei: thanks a lot for finding this12:31
pcercueimvo: should I still create a ticket?12:32
mvopcercuei: yes please, this will make tracking easier12:41
kozaogra, hey. still in this pity state. seems that your unit is somewhat special because somebody at Linaro tried other board they had in the office and it just as much as mine that is just a red led.12:42
ograkoza, hmm, well, i didnt do anything to my unit, i got it from madper as is and only stuck the SD in and booted it after creating the image12:43
ograwho at linaro did you talk to (do we have any hummingboard specialist i could ping in #linaro ?)12:44
kozaogra, whatever has been done you might have the only working hummingboard as of today ;-)12:44
ograwell, you should at least get some output on serial12:44
ograkoza, did you try any other image ?12:44
kozaogra, serial is dead silent; yeah I have tried the debian image12:45
ograsame issue ?12:45
kozaogra, just a red led12:46
ograbah12:46
ograkoza, another thing ... are you still responsible for bluetooth ? we need to get the Pi3 stuff going at some point12:47
ogra(first of all hciattach needs to be allowed to talk to the BT device, the gadget is ready, but the bluez package needs adjustments for that i think)12:48
kozaogra, I know, have this still in the back of my head; I will prioritize this so that it does not slip again; so when I'm done with the failing bluez kernel tests I will be on it12:50
ograkoza, ok, no hurry, just wanted to know if thats still in your set of responsibilities (wasnt sure after the re-org)12:52
fgimenezniemeyer: the board at https://github.com/resin-io/autohat-board has been developed with kicad http://kicad-pcb.org/, this site compares prices from pcb manufacturers https://pcbshopper.com/13:38
fgimenezand has a good list of them13:40
niemeyerfgimenez: Yeah, I think that's one of the most well known open source suites for PCB design.. what I wonder is how far along the manufacturing pipeline this is13:40
ograand as a bonus ... we do have a kicad snap in the store ;)13:40
Chipacapopey: why does wethr sometimes take ages to 'detect my location'?13:43
fgimenezniemeyer: from a random search in https://pcbshopper.com/ it seems that the shipping days range from 5 to 43 http://imgur.com/a/brd4h13:45
niemeyerfgimenez: I think we should find out how many boards have been manufactured with those plans so far, and whether they actually work13:45
jdstrandmvo: nice! :)13:46
fgimenezniemeyer: ok, i'll ask around, will keep you posted13:47
niemeyerfgimenez: Thanks!13:47
mupPR snapcraft#1368 opened: cli: get_project_options must not discard kwargs <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1368>13:51
Vamsiogra: snapweb is meant only for Ubuntu right? Is it possible to do so even from an Android phone or iOS phones?13:53
ograVamsi, snapweb is a web UI for the snapd running on the other machine13:56
ograyou just open it in your phone browser13:56
ogra(any browser should work ... https://<ip of the machine running snapd>:4200/13:57
Vamsiogra: So I install snapd on the host and then on the web browser of my android phone I just put the IP address of this host and then install the snaps I need. Is my understanding right?14:00
=== Guest20728 is now known as ahasenack
ograVamsi, scroll down to "Installing snapweb" http://www.lieberbiber.de/2017/02/22/basic-management-of-an-ubuntu-core-installation/  (a little old but still valid for snapweb)14:02
ograand indeed you dont want to go to "localhost:8041/" but to your IP14:04
Gunther_Hello!14:41
mupPR snapd#3490 opened: client, daemon: using oddjobstate, implement service operations <Created by chipaca> <https://github.com/snapcore/snapd/pull/3490>14:42
Gunther_Serious request: Would it be possible to download  https://public.apps.ubuntu.com/anon/download-snap/canonical/generic-amd64.canonical/generic-amd64.canonical_1.4_all.snap from another source.14:42
Gunther_Our build system is broken because of 403 permission denied.14:43
Gunther_Sorry to bother you with this old stuff, but we depend on it14:43
ChipacaGunther_: what's giving you a 403?14:58
Gunther_the link i posted14:59
ChipacaGunther_: but what is it? why do you want to download it?15:00
Gunther_Accessed from ubuntu-device-flash on our jenkins build server. I know this is old and deprecated stuff, but its the way we generate the image for our devices15:00
Gunther_we will have to migrate to 16.04 lts, but we did not have time for it :-/15:01
ograwow, thats a very old kernel... full of security holes i bet15:02
ogra(or was that a gadget ?)15:02
Gunther_I know, but we need a custom kernel module too that only works with this one ....15:03
ChipacaGunther_: I'm afraid I don't know how to help you15:04
* ogra isnt sure that old stuff even exists anymore 15:04
Gunther_it was accessable until 3 days ago ...15:04
ograi definitely cant see it in my packages dashboard (and i see "canonical-pc" and such which was created around the same time (though canonical-pc is also unpublished)15:05
ogramvo, do you still see "generic-amd64" anywhere in the dashboard for the shared store account or is that gone for good ?15:06
ograi actually thinnk that was a gadget15:07
ogra(for 15.04 images )15:07
ChipacaGunther_: what is the thing that's being built with this?15:07
ogralikes some 15.04 image ...15:07
ogragiven ubuntu-device-flash was mentioned above15:07
Chipacaogra: I mean what device15:08
ogra*likely15:08
Gunther_OS image for a measurement system.15:08
Chipacais this something that is going to go onto shelves15:08
Chipacathat is, is this a product?15:08
Gunther_yes15:08
ograugh15:08
ograso you plan a contribution to the next bigger botnet attack ?15:09
ogra:)15:09
Gunther_:-D15:09
ogra(seriously ... if that device is anywhere on a network you will likely be vulnerable)15:09
ChipacaGunther_: does your company have some kind of commercial relationship with canonical?15:09
Gunther_Thats the master plan ;-). No this kind of device is usually not in the internet15:09
ograok, that makes it less awkward15:10
Gunther_Not that I know off.15:10
Chipacarats15:10
Gunther_Ogra, I will forward you warning to my manager15:10
ogra:)15:11
Gunther_Not that I didnt warn him/them before ...15:11
popeyChipaca: good question, I don't know why it takes ages.15:11
popeyChipaca: I find sometimes if I kill it and run it again, it works. Maybe some upstream API issue15:11
popeyemoj shrug15:12
ograopen the window shades ... perhaps it knows your location if it can see where you are ;)15:12
ChipacaGunther_: I'd have to ask somebody that actually knew to be sure, but I *think* ubuntu-device-flash will work less and less as ubuntu's phone backend things are turned off15:12
ChipacaGunther_: unless it's a bug -- I'll ask, in any case15:13
Gunther_It would help a lot if it would work for additional 2 to 3 months to give us a chance to migrate15:13
Gunther_but sometime a hard cut is good too :).15:14
ograi think deadline for the system-image server was july15:14
ograthen it will be shot down15:14
ogra(there was a mail to the phone ML ... nobody bothered about 15.04 snappy because thats unsupported since ages already)15:15
ogra(so nobody informed about the shutdown in that area)15:15
Gunther_Well thanks guys. I think I know what I will do the next weeks .......15:16
Chipacaroadmr: so, Gunther_ here is getting a 403 when trying to get https://public.apps.ubuntu.com/anon/download-snap/canonical/generic-amd64.canonical/generic-amd64.canonical_1.4_all.snap15:17
Chipacaroadmr: AIUI it worked until ~2 days ago15:17
roadmrChipaca: he's just hitting that URL with curl or something?15:17
ChipacaGunther_: ubuntu-device-flash I *think*, but ask him ;-)15:18
Gunther_yes this is. but i also get the 403 ith chrome15:18
Chipacaroadmr: ^ sorry, meant to tell you to ask Gunther_ and got my wires crossed15:18
roadmrok15:18
* ogra notes that Gunther_ opened a forum task too at https://forum.snapcraft.io/t/old-generic-amd64-canonical-image-403-error/104715:23
=== pstolowski is now known as pstolowski|erran
morphismvo: can you merge https://github.com/snapcore/snapd/pull/3455 ?15:49
mupPR snapd#3455: tests/main: use pkgdb function in more test cases <Created by morphis> <https://github.com/snapcore/snapd/pull/3455>15:49
mvomorphis: yes, looking good15:51
mupPR snapd#3455 closed: tests/main: use pkgdb function in more test cases <Created by morphis> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3455>15:51
morphisthanks15:51
mvojdstrand: I addressed all the seccomp-bpf PR comments, thanks a lot for your careful review. please do let me know if there is anything I might have overlooked. if you are happy, you can pass it to gustavo for a second review. we need to backport it to the 2.26 branch too, but I will take care of this (it is probably going to be quite a bit of work :/)15:54
mvothank you morphis15:54
morphiszyga: there?15:55
niemeyermvo: Out of curiosity, why will the 2.26 merge be problematic?15:56
jdstrandmvo: I'll take a look at it after my next meeting15:57
jdstrandmvo: thanks for addressing all that! I saw your comments on the testsuite. I'll give it some more thought15:58
mvoniemeyer: mostly because the branch has a lot of commits by now and probably some conflicts with 2.26, but I have not invesitgated the details yet, will check tomorrow morning16:01
mvojdstrand: thanks a lot, happy about suggestion how to make this tessuite easier to read16:01
=== pstolowski|erran is now known as pstolowski
Chipacaniemeyer: any objection to moving the logic for 'snap tasks --last foo' into the daemon?16:29
pedronisChipaca: any particular reasons?  (though I suppose it's saner)16:33
Chipacapedronis: it's a little saner, and I'm wanting to add --last foo to two other commands (abort and watch)16:33
pedronisah16:34
Chipacausing them in anger for services made it clear to me it's needed16:34
pedronisyes, I think it's saner16:34
pedronis(because of needing to know about task names)16:34
pedronisthough the reverse is true, needing to know about commands, but commands change less than task names I suppose (though even the latter are kind of stable)16:35
ChipacaOTOH... watch itself might not benefit too much from this16:36
Chipacabah, easy enough to fix i guess :-) but need to make it a little chummy16:37
Chipacapedronis: i had thought i'd do the translation from commands to changes on the client though16:37
pedronismmh16:38
ChipacaOTO²H i could just reuse the existing --last impl, and suggest moving it in-server once that is done16:38
Chipacasame work, maybe clearer motiviation this way16:38
niemeyerChipaca: No objections16:45
niemeyerChipaca: snapd#3480 reviewed btw.. just that one suggestion for the package name16:47
mupPR snapd#3480: overlord/oddjobstate: new package for running commands as tasks <Created by chipaca> <https://github.com/snapcore/snapd/pull/3480>16:47
=== Guest24249 is now known as ahayzen
=== ahayzen is now known as Guest14311
=== Guest14311 is now known as ahayzen
mupPR snapd#3491 opened: snapd: generate snap cookies on startup <Created by stolowski> <https://github.com/snapcore/snapd/pull/3491>16:55
pstolowskiogra, ^ this should fix the warning from snap-confine we discussed this morning16:55
* ogra hugs pstolowski 16:55
roadmrGunther_: are you around?16:59
ograroadmr, https://forum.snapcraft.io/t/old-generic-amd64-canonical-image-403-error/1047 (if he isnt anymore)16:59
roadmrogra: thanks16:59
mupPR snapcraft#1369 opened: Handle I/O errors in os.link (LP: #1689956) <Created by evandandrea> <https://github.com/snapcore/snapcraft/pull/1369>17:06
Chipacaniemeyer: two questions for you: any reason we don't make "change" an alias for "tasks" instead of its current hidden snowflakiness? (makes maintenance harder this way)17:12
Chipacaniemeyer: 2. should i just alias search to find17:12
niemeyerChipaca: +1 on both counts17:13
Chipacaok17:13
niemeyerChipaca: I can't possibly see any other meaning for search that isn't the same as find without it being a reason for LOLs17:14
niemeyerChipaca: We could also tell people that the command is find rather than search, but that's the sort of thing that seems unnecessarily pedantic.. if we know what the user means, we can just do it17:15
Chipacaniemeyer: cmdstate seems fine to me17:31
mupPR snapd#3492 opened: `--last` for abort and watch, and aliases (search→find, change→tasks) <Created by chipaca> <https://github.com/snapcore/snapd/pull/3492>17:32
Chipacaruh roh17:43
Chipacaniemeyer: is everything ok in linode-land?17:43
niemeyerChipaca: More auth issues?17:43
Chipacaniemeyer: https://travis-ci.org/snapcore/snapd/builds/24461815217:43
Chipaca(spoiler: yes)17:44
niemeyerThere are no open tickets ATM17:44
niemeyerLet me ping them17:45
Chipacaniemeyer: otoh https://travis-ci.org/snapcore/snapd/builds/244621777 seems to be proceeding fine17:46
niemeyerI've opened a ticket17:47
Chipaca“dear gustavo, plz less hammering of the api, kthxbye”17:47
niemeyerProbably17:48
Chipaca:-p17:48
Chipacaok i'm going to eod about here17:49
Chipacaif i stay i'm going to either (a) melt, or (b) get dragged into working on the go patch thing until it's too late to do anything more17:49
Chipacao/17:49
=== chihchun is now known as chihchun_afk
=== jaggz- is now known as jaggz
=== Beret- is now known as Beret
=== souther_ is now known as souther
=== thomi_ is now known as thomi
=== Tribaal_ is now known as Tribaal
=== cargonza_ is now known as cargonza
=== ulkesh_ is now known as ulkesh
niemeyercachio: They've dropped a suspect IP from their firewall18:32
niemeyercachio: Please drop me a note if you see the auth issue again18:32
cachioniemeyer, ok18:58
cachioniemeyer, could you please take a look through the console to the machine (Spread-26): 45.79.159.108 ?19:15
cachioit did not start anymore after the reboot19:15
niemeyercachio: Looking19:15
niemeyercachio: Spread-26 is powered off and unallocated19:16
cachioniemeyer, is it any way to recover the disk?19:18
cachioniemeyer, it was discarded before I told you19:19
cachioniemeyer, I'll need to use reuse next time19:19
niemeyercachio: Not just the disk.. the issue is also having the system powered off.. the console is gone at that point19:24
cachioniemeyer, ok19:25
mvojdstrand: thanks a bunch for the extra review, when you have a moment, a reply to https://github.com/snapcore/snapd/pull/3431#discussion_r122786010 would be great, I am working through the other comments now (good stuff btw)19:27
mupPR snapd#3431: interfaces: simplify snap-confine by just loading pre-generated bpf code <Created by mvo5> <https://github.com/snapcore/snapd/pull/3431>19:27
azubietaHello Guys! I'm a developer of NXOS  (http://nxos.org/), whish aims to be a fully snap based linux distribution. Currently we are attempting to port some of the kde plasma apps to snaps in order to make them avalable from our "software center". But we are having serious issues with the connections betwen our snaps and the kf5-frameworks snap. We already get in touch with the kf5-frameworks snaps and he comment us that the problem might be a restriction19:28
azubietaimposed by snapd at the time of the connectin. Would you please assist us in this. Thanks19:28
mvohm, 4min ago I got "authentication failed" for all the allocated spread systems19:28
mvofwiw https://travis-ci.org/snapcore/snapd/builds/244657462?utm_source=github_status&utm_medium=notification19:29
mvocachio: -^19:30
cachiomvo, thanks19:36
cachioniemeyer, mvo reported that 13 mins ago https://travis-ci.org/snapcore/snapd/builds/244657462?utm_source=github_status&utm_medium=notification19:36
cachioniemeyer, authentication failed again19:37
niemeyercachio: Thanks19:37
jdstrandmvo: I commented19:52
mvojdstrand: for some reason I don't seen an update for the question about `setpriority 1\n2`. maybe GH is slow today?19:57
niemeyercachio: Can you please add that at the top of our travis.yaml, so we can tell the public IP of the build system?20:03
niemeyercachio: curl -s -o - http://canihazip.com/s20:03
cachioniemeyer, sure20:04
niemeyercachio: Travis provides a pretty unhelpful "hostname" at the top of the log, but I haven't managed to map that to a real IP yet20:04
niemeyerNeed to figure that out so i have some substance to present to Linode20:04
cachioniemeyer, you mean in the script?20:06
cachiosection20:06
niemeyercachio: Or install, I suppose?   What's the first section to run?20:07
jdstrandmvo: gh has been weird with this pr for me too. let me get you the answer20:07
mvojdstrand: it finally appeared20:08
jdstrandmvo: https://github.com/snapcore/snapd/pull/3431#discussion_r12280672420:08
mupPR snapd#3431: interfaces: simplify snap-confine by just loading pre-generated bpf code <Created by mvo5> <https://github.com/snapcore/snapd/pull/3431>20:08
jdstrandheh20:08
mvojdstrand: I think we are driving it to its limits :)20:08
jdstrandmvo: seems so :)20:08
cachioniemeyer, ok20:09
jdstrandmvo: actually I pasted you an answer to something else. anyway, I'm answering stuff :)20:10
cachioniemeyer, PR 349320:12
mupPR snapd#3493 opened: tests: showing the ip in the .travis.yaml <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/3493>20:12
cachioniemeyer, 35.188.99.11320:15
mvojdstrand: I also replied to your question about seccomp/profiles vs seccomp/bpf20:16
niemeyercachio: Oh, already?20:16
niemeyercachio: That's from a failure?20:16
cachiobut, no, for the PR run20:16
cachioare you going to merge it20:16
cachio?20:16
niemeyercachio: Ah, cool.. yeah, let's merge it once it goes green so we can get the IP for a failure case20:17
cachioniemeyer, or we should re_run it until we are able to reproduce the error?20:17
jdstrandmvo: yeah, replaying20:17
jdstrandreplying20:17
niemeyercachio: We should probably have added an || true or something similar so we don't get failures out of that line.. but we can do that later20:17
cachioniemeyer, echo ip: $(curl -s -o - http://canihazip.com/s) || true20:18
cachioI can make the change right now20:18
mvojdstrand: ta20:19
jdstrandmvo: what happens to /var/lib/snapd/seccomp/profiles once the last version of core that uses it is garbage collected?20:19
mvojdstrand: currently nothing, but we can add cleanup code20:19
niemeyercachio: It's okay, let's try to get it in without yet another round20:19
jdstrandI meant the plan going forward20:19
niemeyercachio: We can polish it later20:19
cachioniemeyer,  sure20:20
niemeyerThis one will already take ~30 mins20:20
jdstrandmvo: this makes documentation and auditing icky. 'if you are using snapd < 2.26, then look here, otherwise look there'20:20
jdstrandI was thinking the bpf stuff would fix that, but it only does going forward from 2.2620:21
jdstrandalso, images that start with 2.26+ end up with /var/lib/snapd/seccomp/bpf which doesn't align with /var/lib/snapd/apparmor/profiles20:21
jdstrandmvo: maybe /var/lib/snapd/seccomp/profiles.bpf and don't name the input files with .in but do name the bpf files with .bpf?20:23
mvojdstrand: sounds good20:23
mvojdstrand: I can tweak that, I like that suggestion20:23
jdstrandeg, snap-seccomp /var/lib/snapd/seccomp/profiles.bpf/snap.foo.bar /var/lib/snapd/seccomp/profiles.bpf/snap.foo.bar.bpf20:23
jdstrandat least it feels similar to what we currently have and it is mostly discoverable20:24
mvojdstrand: sounds good, could you please comment in the PR? I will work on that first thing in the morning.20:25
jdstrandmvo: https://github.com/snapcore/snapd/pull/3431#discussion_r12281506420:27
mupPR snapd#3431: interfaces: simplify snap-confine by just loading pre-generated bpf code <Created by mvo5> <https://github.com/snapcore/snapd/pull/3431>20:27
jdstrandmvo: (I was :)20:27
mvojdstrand: great, thanks a lot. I will call it a day now but will read the PR comment in my morning and work on the dir name change then20:30
jdstrandmvo: ok. thanks for getting to all these things! we are getting closer and closer :)20:30
codeplug_Hi, is anyone familiar with using bluez in the Snappy Ubuntu Core environment? I'm trying to understand why this bluez stack doesn't come with gatttool...20:31
mvojdstrand: indeed, it feels good20:34
* mvo waves20:34
mupPR snapd#3493 closed: tests: showing the ip in the .travis.yaml <Created by sergiocazzolato> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/3493>20:43
cachioniemeyer,  the automatic restart of the rng-tools service seems to not be enough21:01
cachioniemeyer, https://travis-ci.org/snapcore/snapd/builds/244673127#L349321:01
cachioentropy = 13821:01
=== JanC_ is now known as JanC
codeplug1???21:28
Chipacacodeplug1: !!!!21:31
Chipacaniemeyer: more auth issues: https://travis-ci.org/snapcore/snapd/builds/24470038921:31
mupPR core-build#14 opened: initramfs/testing: add unit tests for initrd scripts <Created by zyga> <https://github.com/snapcore/core-build/pull/14>21:32
azubietahttps://forum.snapcraft.io/t/issues-building-kde-plasma-applications-snaps-for-nxos/21:41
niemeyerChipaca: Thanks, and this time we have the source IP21:49
niemeyercachio: We'll need to find out what's actually broken there then21:50
cachioniemeyer, yes, working on that21:51
niemeyerI'm running out of ideas.. Linode is apparently getting requests without the key in some cases, but on the Travis end there's no apparent distinction between the calls :(22:52
niemeyerThe failing and the working setup look pretty alike22:53
mupPR snapcraft#1370 opened: integrations: add the snapcraft Dockerfile <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1370>23:01
niemeyerand now everything seems to work fine..23:05
Chipacaniemeyer: so... maybe it's not linode? https://travis-ci.org/snapcore/snapd/builds/24473376523:33
niemeyerChipaca: Yeah, I don't think it is23:34
niemeyerChipaca: It feels like something out of our control is running concurrently with the usual scripts23:34
niemeyerChipaca: Perhaps it's not a coincidence that Travis is working on their images23:34
Chipacaniemeyer: should I switch the 'beta' thing on to see if it improves at all?23:35
Chipaca'group: edge' i think it is actually23:35
niemeyerChipaca: Worth a shot, although it's awkward that it's breaking on what in theory is the old stuff23:35
* Chipaca nods23:35
niemeyerChipaca: But this is software, soooo23:35
Chipacaand not consistently either23:35
ChipacaI'll give it one retry23:36
Chipacaniemeyer: no difference23:44
Chipacareverting the change23:44
* Chipaca gives up and goes back to trying to sleep23:48

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!