[01:05] PR snapcraft#968 closed: sources: refactor subversion source into module [01:14] PR snapcraft#977 opened: Prefer in-snap libraries to system libraries [01:32] PR snapcraft#978 opened: Updated cmake uplugin to use get_build_properties() [01:32] PR snapcraft#979 opened: Updated waf plugin to use get_build_properties() [03:09] Bug #1650091 opened: console-conf and getty hang if password is not set and press many enters [03:36] Bug #1650096 opened: 'snap list' does not show devmode property after disable and re-enable a snap === chihchun_afk is now known as chihchun === JanC is now known as Guest52303 === JanC_ is now known as JanC [07:24] PR snapd#2480 closed: many: prepare landing on trusty [07:37] PR snapd#2474 closed: Revert "interfaces: add new boot-config interface" === jamespag` is now known as jamespage [08:04] hey hey [08:07] PR snapd#2488 opened: interaces: add new boot-config interface [08:35] Can I hand back a snap store name I was granted? Someone else is handling the snap. [08:35] Or maybe I can just ignore it, since it will be obvious since I've pushed nothing to that namespace [08:36] Issue snapd#2489 opened: Can't run binary installed via a snap package [08:39] mup: Why did you announce that bug? It's a dead link... [08:39] kalikiana_: In-com-pre-hen-si-ble-ness. [08:39] mup: Bug link is broken [08:39] kalikiana_: Roses are red, violets are blue, and I don't understand what you just said. [08:39] Pffffft [09:17] Bug #1650187 opened: Can't run any snap application on Mint 18 [09:19] Issue snapd#2489 closed: Can't run any snap application [09:27] PR snapd#2485 closed: overlord: apply auto-aliases information from the snap-declaration on install or refresh [09:38] Looks like charms using the Snap layer need to be rebuilt for Snappy 2.17, due to the backwards incompatible change of 'ubuntu-core:slotname' to just ':slotname' [09:39] What time frame are we looking at for backports to trusty? [09:40] stub: Shouldn't both be valid? Or is it documented to be breaking? [09:41] I don't know if it is documented. ubuntu-core:foo is no longer valid. I don't know when :foo started being valid. [09:41] The test cases in snapd still use ubuntu-core: [09:42] Huh. That isn't what I'm seeing here. [09:42] root@ip-172-31-3-170:/var/log/juju# snap connect rocketchat-server:network ubuntu-core:network [09:42] error: cannot perform the following tasks: [09:42] - Connect rocketchat-server:network to ubuntu-core:network (snap "ubuntu-core" has no slot named "network") [09:42] root@ip-172-31-3-170:/var/log/juju# snap connect rocketchat-server:network :network [09:43] (the last works) Or is there a typo in there I can't see? [09:43] hey there [09:44] does anyone know if remote parts can point to a branch [09:44] git repo one [09:44] stub: Normally network autoconnects... are you sure you need to do that at all? [09:44] seb128: yes, I think you specify the branch name in a separate yaml field [09:45] kalikiana_: This is just my test case. I know it is not actually needed. [09:46] (I need a smaller test snap in my test charm) [09:46] stub, like "origin-branch: something"? [09:46] stub, on https://wiki.ubuntu.com/snapcraft/parts [09:48] seb128: yes, but I don't recall exactly what it is or where it is documented [09:49] stub, k, thanks anyway, I'm going to try to figure it out [09:50] seb128: snapcraft/internal/sources.py [09:50] source-type: git [09:50] source-branch: [09:50] stub: For me, using another snap as an example, both of these work: "snap connect arangodb3:network ubuntu-core:network" and "snap connect arangodb3:network :network" [09:50] kalikiana_: Can you confirm you have 2.17 ? [09:51] Maybe it is fixed in 2.18 [09:51] stub, that's what is used in snapcraft.yaml but doesn't match the syntax used on https://wiki.ubuntu.com/snapcraft/parts which uses e.g "origin" or "origin-type" [09:55] stub: I just updated to the latest master and it still works fine [09:56] kalikiana_: ok, I'll assume user error or fixed after 2.17 for now. There are not enough charms using the layer yet to be a major problem. [10:04] stub: What if you used core: instead of ubuntu-core:? [10:05] As the snap was renamed at one point, that could explain the error [10:06] If that's the case it might make sense to explicitly handle that case in the code - currently it doesn't [10:16] PR snapd#2490 opened: many: implement "snap un/alias --auto" using snapstate.ResetAliases [10:19] PR snapd#2410 closed: store: retry resumed downloads on sha3 error [10:29] PR snapd#2483 closed: store: use mocked retry strategy to make store tests faster [10:35] kalikiana_: Oh, you are correct. core:network works [10:36] Bug #1650207 opened: original lsb-release file should be preserved for classic mode [10:37] kalikiana_: At least under 2.17. core: fails under 2.16 :) [10:38] stub: Yeah. As I said, the snap was renamed. You can see it in "snap list" [10:38] If you don't use a name, snap connect will pick one [10:39] So if this affects several existing setups, it may make sense to alias ubuntu-core to core [10:40] PR snapd#2486 closed: tests: fix tests on 17.04 [10:40] Or, if updating all existing cases is good enough, use :foo everywhere and it'll just work [10:40] I could detect the snappy version and rewrite ubuntu-core to core as appropriate (or vice versa) [10:41] stub: It's literally about which snap is installed, the version of the tooling is irrelevant [10:41] :foo doesn't work under 2.16 [10:42] I would need to detect the version, using ubuntu-core:foo under 2.16 or earlier or :foo under 2.17 or later. Or just wait for 2.17 to get backported to trusty. [10:43] Hmm I can't find it in the changelog unfortunately [10:45] I'm going to ignore it for now. I don't think it affects anything live, and a minor glitch to stuff in development (which is targetted at Xenial, so 2.17), and the only thing I'm aware of that will need to support both doesn't use slots (canonical-livepatch) [10:45] well, doesn't need to specify its slots since they autoconnect [11:08] ISTR there is a way to get shell inside snap confinement for troubleshooting purposes but I can't find any docs. Anybody knowns how to do it? [11:11] jacekn: run --shell ¿ [11:11] i.e. snap run --shell mySnap [11:12] tsdgeos: aha that's it! [11:13] glad to be of service :) [11:14] right so next question will be how to bump number of open files, it's tricky because my snap is a deaemon so it uses autogenerated systemd unit file [11:47] hi guys i need help building snap package of my application which i wrote using qt57 installed in my /opt/qt57 now i dont wana use qt57 part cause it download whole qt57 source and then compile it and then fail at middle [11:47] my question is , can i use the system's (/opt/qt57) qmake to build source and build snap package [11:50] launchpad also gives up with my project cause it through errors while compiling qt code :D [11:51] PR snapcraft#980 opened: Add optional "source-checksum" property [11:53] i used qt5.7 cause it has a working qwebengine api :D [11:59] kalikiana_: There is no syntax that works with both 2.16 and 2.17. If I use core instead of ubuntu-core: it fails under 2.16 [12:00] PR snapcraft#959 closed: cli: make plugins be an alias of list-plugins [12:00] PR snapcraft#970 closed: sources: refactor zip source into module [12:00] kalikiana_: (whoops.... backscroll fail) [12:03] PR snapcraft#976 closed: demos: do not force arch for the tomcat demo [12:06] PR snapd#2491 opened: debian: use a packaging branch for 14.04 === arosales_ is now known as arosales === mup_ is now known as mup [12:13] PR snapd#2492 opened: cmd/snap: remove currency switch following UX review [12:33] PR snapcraft#981 opened: Support download and validate on branded stores [12:41] kyrofa, hey, do you know if remote parts can specify a git branch to use? [12:43] sergiusens, ^ [12:46] ppisati, i need an updated kernel snap in edge to have it pick up some initrd changes, what was your exact naming scheme you use for the beta/candidate builds so i can make the edge bzr branch match that ? [12:47] err [12:47] s/naming scheme/versioning scheme/ (indeed) [13:02] ok here's another question i have [13:02] regarding autoupdates [13:03] if my internet is not very good and im in the middle of an online game or downloading something important [13:03] i wouldn't like some program updates hindering my bandwidth [13:03] i would rather update when I want [13:03] i even disabled auto updates in my android phone [13:05] madprops, it is managed by a systemd time that you can turn off but you should really not forget to update regulary then :) especially if you use snaps from the edge channel that can change frequently [13:05] snapd.refresh.timer is the system unity [13:06] ogra_, quick question, I understand that whenever a new core/kernel gets installed, uboot.env gets rebuilt with the right values for snap_core and snap_kernel, correct? [13:06] not re-build, jzust these vars get updated [13:07] ogra_, well, modified :) [13:07] yeah [13:08] abeato, snapd does that through uboot.go, you can check the values with fw_printenv [13:09] ogra_, ah, good to know, thanks [13:25] hi guys i need help building snap package of my application which i wrote using qt57 installed in my /opt/qt57 now i dont wana use qt57 part cause it download whole qt57 source and then compile it and then fail at middle [13:25] my question is , can i use the system's (/opt/qt57) qmake to build source and build snap package [13:25] launchpad also gives up with my project cause it through errors while compiling qt code :D [13:25] ogra_, [13:39] bull, you can probably create a snapcraft part for it and use this during the build of your app ... [13:41] or perhaps you could use ubuntu-app-platform ... i'm not actually sure which Qt version that ships [13:43] ogra_, that does not include qt57 [13:43] ogra_, can i use my system's qt57 ?? [13:43] ah, well, then you likely need to create a part [13:43] ogra_, i have no idea how to do that , i have installed qt57 from ppa [13:44] well yopu would have to include it in your snap [13:44] i want its qmake build my source in snapcraft and turn my code to snap :( [13:44] or create a part that pulls it from the PPA and instalkls it in the snapcraft build env [13:44] ogra i can include everything by staging but idk how to call opt/qt57/bin/qmake [13:45] heh, i dont know either ... perhaps with a make plugin as wrapper or some such ... [13:45] ogra_, i dont know how o do it man :( i been struggling from 3 days :( [13:46] you shoudl ask someone with some more Qt experience ... i did never really get past QML [13:46] i used remote qt57 which downloaded more then 2gb of qt src and chromium src dataand failed twice as it cant build correctly [13:46] perhaps the guys in #ubuntu-app-devel could be of help [13:46] ogra_, let me ask them thanks man [13:48] bull, also https://github.com/snapcore/snapcraft/pull/566 seems to be the snapcraft qmake plugin .. you might need to use it and override some bits to make your bzuild use a custom qmake (not sure about that though) [13:48] PR snapcraft#566: Add qmake plugin [13:51] i uploaded my other application to store check them here https://uappexplorer.com/apps?q=author%3Akeshavbhatt&type=all_types&sort=-points [13:51] ogra_, am looking into it thanks [13:57] kyrofa: thanks for your help the other day; I got it working. Now I'm stuck trying to get a config file deployed for the DNS server, which I have traditionally used a shell script to modify some of the values. Is there any way to do this via a custom plugin? [14:01] niemeyer: hi! https://github.com/snapcore/snapd/pull/1613 still has you as 'requesting changes' in github so no one can merge it. would you mind 'approving changes' and merging it? [14:01] PR snapd#1613: interfaces/builtin: add dbus interface [14:26] sergiusens, recently I found a bug on dragonboard. could you please help to take a look at it? thanks. the bug link is at https://bugs.launchpad.net/snapcraft/+bug/1649181 [14:26] Bug #1649181: 'ascii' codec can't encode character '\u29f8' in position 49: ordinal not in range(128) on ARM 64 platform like dragon board [14:26] PR snapd#2493 opened: overlord/snapstate,daemon: implement GET /v2/aliases handling [14:27] PR snapd#1613 closed: interfaces/builtin: add dbus interface [14:31] yay, dbus [14:42] liuxg, wow, something must be really outdated on your side, that has been fixed ages ago iirc [14:43] liuxg, popey's bug ... bug 1607015 [14:43] Bug #1607015: 'ascii' codec can't encode character '\u29f8' in position 19: ordinal not in range(128) [14:43] ogra_, but it happened now on my board.. I tried to use classic to build a project, and it happened to be like that [14:44] ogra_, it seems that it happens on the arm64 architecture, on 32bit architecture, it does not happen. [14:44] well, read the bug ... fixed long ago if you use the proper component [14:45] i'm pretty sure that char isnt usedd anywhere anymore [14:46] ogra_, the same project can be compiled on pi devices. [14:46] well, no idea then, but i know that the slashes were dropped from all components (or was the char a backslash ? ) [14:47] when we dropped support for the old desktop-* things [14:48] ogra_, let me try again. it is very consistent. [14:49] and your snapcraft yaml uses desktop-*, not desktop/* ? [14:50] (the latter causes the bug and the parts using a slash in the name were all dropped long ago) [14:50] ogra_ well they are not dropped, just deprecated ;-) [14:50] sergiusens, dropped from support ;) [14:51] nobody touched them since [14:51] and for this very reaon [14:51] yeah [14:51] right, that is true [14:51] if you see it with the dash version, there might indeed be a bug though [14:51] ogra_, sergiusens, this is the result http://paste.ubuntu.com/23633817/ [14:52] ... somewhere ... [14:52] now thats a different char [14:52] '\xae' [14:53] ogra_, sergiusens yeah, yes, they both are reported in the bug [14:53] liuxg, and you are sure you are not using a part with a slash in the name in your snapcraft yaml ? [14:54] ogra_, I have changed to use "mqtt-paho-python3" instead, but it is the same. [14:59] you still get complaints about '\u29f8' ? even though you dont have any names with a slash in your snapcraft yaml and have completely cleaned your tree before calling snapcraft ? [15:00] ogra_, I am now trying it again. I remember I did that before. [15:03] PR snapcraft#982 opened: parser - Use the same version method as 'snapcraft' [15:08] ogra_, you are right. after changing to "-", it is OK. I remember I changed that last time. [15:11] what processes the files in /var/lib/snapd/mount ? [15:11] is it snap-confine ? [15:14] roadmr: hi! can you do a store sync for r810. that is just a data update, no code changes [15:14] jdstrand: sure! [15:14] roadmr: thanks! [15:15] PR snapcraft#983 opened: Updated scons plugin to use get_build_properties() [15:16] when i try to register a key for sign a model assertion with "snapcraft register-key" i got error and the msg is "Key registration failed: Failed to save account-key-request assertion for account_id XXXXXX invalid revision: could not add assertion (revision 0 is already the current revision)" [15:17] mvo: any idea ^? [15:18] shuduo: I am not sure, sergiusens may know better but it sounds like the key is already registered maybe? [15:18] Quick question about snapcraft development. I have put forth some PRs, but the autopkgtest is failing for xenial- and yakkety- amd64. Is there a reason why these 2 might fail and the rest pass? [15:20] guys how can we use local part from / part/plugins dir ?? [15:21] mvo, sergiusens, it failed at first time with msg "Key registration failed: Failed to create account-key assertion for account_id XXXXX assertion refused: could not add assertion (account-key assertion for YYYYY has the same name "default" as existing ID ZZZZ. [15:21] i mean what we have to put in snapcraft.yaml file to so that snapcraft can recognize that plugin [15:21] but how i can find exist keys from launchpad to manage them? [15:21] sergiusens, help me please am lost since three days :( [15:23] popey, hi [15:28] mvo, snapd 2.20 is for this week or next week ? [15:32] ondra, I have this for the rpi3 gadget: https://github.com/snapcore/pi3-gadget/pull/4 [15:32] PR pi3-gadget#4: Add support to boot from USB [15:32] ups [15:33] ogra_, ^^ [15:33] abeato, wont work [15:33] alex-abreu: today [15:33] that needs a specific firmware so we need a separate new gadget [15:33] ogra_, well, it does (if you enable first USB booting from raspbian) [15:33] ogra_, the firmware works for both cases === chihchun is now known as chihchun_afk [15:34] I tested that [15:34] abeato, the prob is really that it is irreversible ... on the pi ... so we need more HW [15:34] one to test U(SB, one to test SD where we never switch the rom [15:34] ogra_, well, give it a try in yours :) [15:34] i surely wont [15:34] mvo, thank you, ... also quickly do you have the rights to give me the commit rights in snapweb github? [15:34] since i need to still be able to test SD [15:35] ogra_, both SD and USB work for me :) [15:35] alex-abreu: let me check, I think I don't have the needed privs, only gustavo has. but I will double check [15:35] mvo, ok [15:35] abeato, you mean you can turn it back into an SD obnly device ? [15:35] afaik thats not possible [15:36] if you switch to the other path for the ROM there is no way back [15:36] alex-abreu: actually jamiebennett and elopio have admin [15:36] mvo: that is not enough [15:36] oh, ok [15:36] mvo: you need to be an organisational admin apparently [15:36] alex-abreu: -^ [15:37] mvo: the add user stuff if greyed out for me [15:37] mvo, oh ... [15:37] jamieben_, so who can add users? === jamieben_ is now known as JamieBennett [15:37] I know niemeyer can [15:37] ogra_, don't know, but the PR will not break your rpi, to enable USB you need to do something else [15:38] niemeyer, ^ when you see this, ... adding me as committer to snapweb [15:39] abeato, not the PR, but to test it we need additional HW [15:39] abeato, we still need to be able to test the default setup without the ROM switcvh [15:41] ogra_, you can do that :) I tested with the switch, you can test without it [15:42] abeato, ah, i see you didnt add the config.txt bit by default [15:42] ogra_, correct [15:42] hello there [15:43] abeato, oh, CONFIG_PREBOOT is clever ! [15:44] PR snapd#2494 opened: store: send an explicit X-Ubuntu-Classic header to the store [15:45] abeato, why is the "enable_uart=1" needed ? isnt that initialized by default anyway ? [15:46] ogra_, not with latest firmware, and that caused *lots* of problem until I found the right solution [15:46] ah [15:46] ogra_, https://github.com/RPi-Distro/repo/issues/22 [15:46] yeah, we're a bit behind with the firmware files ... better safe than sorry :P [15:46] indeed lol [15:47] ppisati, would you mind taking a look at https://github.com/snapcore/pi3-gadget/pull/4 as well ? [15:47] PR pi3-gadget#4: Add support to boot from USB [15:47] ppisati, looks all fine from my POV ... but i'd like a second pair of eyes [15:48] help me anyone know how to use local parts/plugin in snapcraft ?? [15:48] ogra_, :( [16:01] sergiusens, ping [16:05] * ogra_ wonders if ppisati ignores #snappy today :P [16:06] ogra_: nope, just juggling some stuff [16:06] ah, k, you were so quiet :) [16:06] ogra_: the days before PTO are always the best... [16:06] go on juggling then ;) [16:09] PR snapcraft#984 opened: parser - Make output better [16:10] ogra_: looks good too [16:10] ppisati, thx ... also see my former ping about the edge kernel [16:10] (no hurry though ... but i'd like it in edge before the weekend ... tomorrow is fione too) [16:12] ogra_: this is the tip of the snapcraft.yaml ATM [16:12] ogra_: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-snap/+git/xenial/tree/snapcraft.yaml?h=pc [16:13] ogra_: kernelversion-abi-uploadnum [16:13] ppisati, ah, so not different from what we have now [16:14] good, thanks [16:18] PR snapcraft#890 closed: cli: implementing '[list-]registered' command [16:46] slangasek, hmm, wheer are the actual snap builds for the gadgets now ? i merged some code for pi3 but no snap shows up in the store ... i find https://launchpad.net/snap-pi3 but there seems to be no related snap buuild anywhere [16:47] bah [16:47] ogra_: we discussed that this was moving to github; where are you merging this code to? [16:47] and after 20min searching /me finds the "show snap packages" link at the very bottom of the page above [16:48] slangasek, on github :) [16:48] so e.g. https://github.com/snapcore/pi3-gadget [16:48] right [16:48] it just didnt get picked up by any auto-build yet [16:48] ok [16:48] and https://code.launchpad.net/~canonical-foundations/snap-pi3/+git/github-mirror/+ref/master doesnt seem to have the last merge [16:49] oh [16:49] ogra_: so you have merged an update that takes a *different* set of undocumented blobs into the pi3 snap? where is the source for the build that's being used? [16:49] https://code.launchpad.net/~canonical-foundations/snap-pi3/+git/github-mirror ... only runs every 5h [16:50] slangasek, theer is no source for the blobs obviously ... for the uboot side this merge adds instructions with pointers to the source in the README.md [16:50] is it possible to connect a locally built snap to the content interface from a snap from another provider (canonical) coming from the store? [16:50] kyrofa, ^ hey, do you know? [16:52] seb128, I _think_ so [16:52] seb128, but that stuff changes fast [16:52] slangasek, we can indeed note that the blobs come from https://github.com/raspberrypi/firmware but we still wont get the source [16:52] ogra_: pointers> ok [16:52] seb128, last I heard, it won't automatically connect since they aren't from the same publisher but you can still connect them [16:52] ogra_: sure; I meant specifically the uboot blob here :P [16:53] seb128, unless the base assertion denies it, that should work [16:53] kyrofa, I wonder if I'm doing something stupid or using the wrong syntax, it gives me a "(cannot connect plug to slot "gnome318-runtime" from snap "gnome318-udt", no such slot)" [16:53] seb128, pastebin snap interfaces for me? [16:55] slangasek, switching to plain-from-soource builds for uboot is on my TODO for early jan. the current blob comes from abeato's disk following the README instructions [16:56] ogra_: er, we should discuss this; as I've said before the uboot builds should come from the archive [16:56] I `dump` some config files with my snap, but I need to modify some values in those files. I typically do this via a shell script running some `sed` commands. Is there a way to run a script after the snap is installed, or do I need to make a custom plugin to do something like this. [16:56] ogra_: so that we can use the same uboot source for classic and snappy images via ubuntu-image [16:56] slangasek, that was my plan (discussing it first with you and ppisati) [16:56] ok [16:57] we need an extra patch and thus extra binaries [16:57] but you know that already :) [16:59] abeato did you talk to penk? he's been also trying to boot from USB [16:59] JamieBennett: is this still the most "up to date" img for downloading? [16:59] http://releases.ubuntu.com/ubuntu-core/16/ [16:59] ondra, should work with the next gadget from edge [16:59] ....i know the proposed channel is being updated...just wondering if someone is just starting fresh...is that the most recent img to get [16:59] kgunn: yes, no new images yet [17:00] thanks [17:00] ogra_ one you blow USB boot fuse, you can still boot from sdcard [17:00] ondra, yes, but you use differenmt ROM code ... [17:01] ondra, rto test the original path you still need a pi that hasnt been changed [17:01] ondra, I saw his post, was a nice way to get started :). But we wanted to remove completely the SD card, with the merges you changed that is possible now [17:01] *you merged [17:01] changes you merged [17:01] lol [17:02] abeato cool [17:06] PR snapcraft#985 opened: Better message for missing snapcraft.yaml in origins