=== chihchun_afk is now known as chihchun [08:01] good morning [09:25] fgimenez: good morning! I will preare another stable release of 15.04 today, anything looking risky here? [09:29] Good morning all; happy Wednesday, and happy International Anti-Corruption Day! 😃 [09:29] hey mvo! not AFAIK, moreover once the image is published a new cloud image would be generated and the suite will be executed in http://162.213.35.179:8080/ [09:29] fgimenez: awsome [09:30] mvo, i'm off this week, anyway if you need anything from my side don't hesitate to ping me, i'll be available from 14:00 CET onwards [09:30] ogra_, ricmm: fwiw, I triggered a new 15.04 build preparing a new stable [09:30] fgimenez: uh, if you are off then enjoy your time off :) I will bother elopio [09:31] mvo, thx, anyway i'm not very afk, so if you need a hand just ping me :) [09:32] fgimenez: thanks! much appreciated [09:35] dholbach, ping [09:37] liuxg, pong [09:38] dholbach, for python package installation, can we put the packages into the setup.py like the way for webcam? [09:38] dholbach, this is the example https://github.com/ubuntu-core/snapcraft/blob/master/examples/webcam-webui/setup.py [09:41] liuxg, I don't understand [09:41] which packages do you want to install? which do you want to add to setup.py? [09:42] dholbach, for example, we can put the django packages into the "install_requires" field in the file if the package is needed for the app. Currently, it is suggested using the requirements.txt file to do it. [09:43] IIRC "install_requires" will make the build/installation fail if the package is not available [09:44] requirements.txt is a mechanism to obtain and install the package [09:44] (I personally would still go for using the archive unless you need a specific version which is not available in the archive, it should be the easiest) [09:44] but maybe zyga, sergiusens and others have an opinion on that too [09:45] dholbach, the problem with the archive one is that we need to use the fileset stuff to choose the files and then combine them into a snap. it is a little more complex in this sense. [09:45] why do you need the filesets? to make the package smaller? [09:45] ... I mean to limit the number of installed files? [09:46] I'll be right back... I need to take care of something else for a few minutes [09:46] dholbach, yeah, that could be the purpose for it. [09:47] dholbach, sure, it is OK:) [09:47] strictly speaking for this example you either don't need the filesets or you would use it as well for the other methods of installing django [09:48] all of them are likely going to install a lot of files you don't strictly need [09:49] dholbach, do you mean if I just simply put " stage-packages: -Django", it will install all of the files for django? [09:57] liuxg, the package name in Ubuntu is python-django, but yes [09:57] and without the '-' [09:58] dholbach, thanks. I will try it later on. [09:59] great === Guest65640 is now known as beowulf === beowulf is now known as Guest86859 === vrruiz_ is now known as rvr [11:43] Hi there! So Im looking at snappy and wonder how I get to tell snappy on how to order the builds and stages for the parts of a package ... [11:43] any hints? === greyback__ is now known as greyback [12:03] does anyone have an experience with snappy vagrant box ? [12:11] elopio: I pushed candidates to alpha, could you trigger the automatic snappy update test when you are online? [12:11] elopio: there is a new released planned :) === verterok is now known as verterok-away [12:25] i get ssh timeout with snappy on vagrant. Does anyone experience the same issue ? === verterok-away is now known as verterok [12:29] oh ok that happens only when i try to set a private network [12:38] what are the default credentials ? [12:41] livcd: ubuntu:ubuntu I believe [12:45] sheesh this is annoying === dholbach_ is now known as dholbach [12:51] so, I try to build something with snapcraft that depends on libxml2. The ./configure is all happy about it, build gcc doesnt find headers like libxml/xpath.h when compiling. libxml2-dev is install on the host system and is listed in the snapcraft.yaml as "build-packages: [... ,"libxml2-dev", ...]". What am I doing wrong? === chihchun is now known as chihchun_afk [13:57] so ... whats the difference between "snap-packages" and "build-packages" in a snapcraft.yaml? === verterok is now known as verterok-away === fginther` is now known as fginther [14:50] mvo: yes! === chihchun_afk is now known as chihchun [15:01] mvo: what's the trick now to flash this? --oem generic-amd64/alpha doesn't seem to work. [15:02] Sweet5hark, where are you getting `snap-packages`? I don't believe such a key exists in the snapcraft.yaml [15:07] Sweet5hark: the build-packages will be installed in the host. You require them to perform the build step and generate the files that will be installed. [15:07] does anyone know how to set a private_network with snappy's vagrant box ? [15:07] it won't let me login [15:08] Sweet5hark: to define the order in which the parts are built, use the after keyword. [15:09] Sweet5hark, in case we're misreading that question, snap packages are what are generated by snapcraft, and build-packages are the .deb dependencies required on the host to build the snap packages [15:09] livcd: I haven't tried vagrant in a long time, sorry. I'll give it a try when I have some free time today. [15:10] elopio: "alpha" isn't a channel [15:10] elopio: generic-amd64/stable should work [15:10] elopio: thanks. :-/ default settings work fine but I want to use nfs and for that i need private network :/ [15:11] Chipaca: ah, I see. [15:11] livcd: what's the name of the ethernet device when in private_network? [15:11] Chipaca: i do not specify that [15:12] livcd: i didn't say you did [15:12] all i do is config.vm.network :private_network, ip: "10.1.0.10" [15:12] livcd: and when you do that, and boot, and log in, what interface name do you find? [15:12] vagrant up shows adapter 1: nat, adapter 2: hostonly [15:12] Chipaca: can't log in [15:13] livcd: you don't even have a serial console? [15:13] nope [15:14] so how do you debug boot issues, for example? [15:15] mmnt i'll run it with debug mode [15:15] livcd: alternatively boot something else with private_network and check the interface names there [15:16] livcd: I'm taking a wild guess that it's naming the interface something non-standard that snappy firstboot doesn't recognise as an ethernet device [15:16] thanks for input [15:16] i'll try that [15:17] so to use private_network you'd need to write an oem snap that specified an interface file, or that installed network-manager [15:17] livcd: but maybe vagrant lets you name interfaces something more standard :-) [15:18] livcd: alternatively it's possible that you're not setting up dhcp on the private network [15:19] in fact, pretty sure that's what you're doing [15:19] as you seem to be specifying a static ip [15:19] to vagrant [15:19] but not to snappy [15:19] so that won't work :-) [15:19] livcd: ^ [15:20] livcd: if you absolutely need a static ip, you can probably: boot snappy with dhcp, so you can log in, then overwrite the interfaces file from the booted system [15:20] livcd: then shutdown, change the vagrant config, and boot again [15:20] livcd: this is assuming you don't want to write an oem snap, which would be the 'right' way to do this [15:21] Chipaca: i am just trying snappy [15:21] Chipaca: ok i'll try dhcp first and report [15:21] livcd: yep, it sounded like you were just tinkering, hence my tinker-y suggestion [15:22] livcd: specifying all this in a snap is the more scalable/robust/production way :-) [15:24] first of all i need to know more about snap :-). I was planning to use snappy as a bare image for docker and orchestrate with terraform [15:25] ok specifying dhcp has the same effect [15:27] livcd: same effect == no network? [15:28] mvo: flashed 19, updated to 20, rolled back, updated to 20 again, and the full suite is running now on that image for kvm amd64. [15:28] mvo: can you push the rpi alpha to try there too? [15:29] Chipaca: yeah [15:30] livcd: and does it work without private_network? [15:30] with the default settings that work there's lo and eth0 [15:30] yeah [15:35] i am somehow dissappointed :/ [15:42] elopio: many thanks, rip2 is also copied [15:42] elopio: eh, not quite [15:42] elopio: but soon [15:42] elopio: now [15:43] I see it, thanks mvo. [15:43] i am out of options...not sure what else should i try [15:44] mvo: should we document the need of /stable when flashing before the new release? Or is that going to be fixed before we release? [16:05] when i try to reboot my raspberry pi, it seem like it doesn't reboot correctly. is this known issue? [16:08] ogra_: jcastro made something for you: http://i.imgur.com/CcwkgN7.jpg :-) [16:13] :D [16:27] dholbach, hah ! cool ! [16:27] thats a really nice pic, i have never seen it [16:28] Chipaca: the private_network setting has lo,eth0 and eth1 adapters [16:39] ogra_: I get choppy output on the serial console of the rpi. Does it have a different rate? I'm using 115200 [16:43] elopio, nope, 115200 is correct [16:43] works fine here [16:43] ogra_: it's not garbage, it's just misaligned. [16:44] maybe the cable. [16:44] what terminal program do you use ? [16:48] ogra_: screen [16:48] hmm, me too [16:49] so yeah, probably the cable === verterok-away is now known as verterok [16:50] what is ubuntu-core-meta and should i care? [16:50] mvo: On rpi, flashed 3, updated to 4, rolled back, updated to 4 again, and the full suite is starting. [16:50] reboot -f does not work either [16:50] mvo: is there something special you would like me to check or explore? [16:51] mvo: is there something special you would like me to check or explore? [16:51] xnox, good question, i didnt think there exists a meta for -core [16:51] sorry, hiccup. [16:51] xnox, -core only uses tasks, we do not have a meta [16:51] s/have/need/ [16:52] xnox, perhaps that meta is from infinitys "ubuntu-core" (not snappy) ? [16:52] probably [16:53] how do i switch channel on the rpi? (stable -> rolling/edge ) [16:57] mariogrip: there is no supported way yet. You can edit /etc/system-image/channel.ini, but for that you have to make the partition writable, and we don't guarantee success [16:58] thanks, I'll give it a try [16:58] but do you know if there is any known issue with reboot on the rpi? [16:59] on version 3 [16:59] sorry i mean version 2 [17:04] mariogrip: not that I know of. Please report a bug if you see something weird. [17:24] elopio: nothing in particular 15.04 has not changed much so we should be mostly fine [18:21] mvo: things look good from here. I'll go and have lunch and can run the tests on bbb. [18:28] elopio: thanks === bschaefer_ is now known as bschaefer [20:18] elopio, I want to make a helper class for my plugin. How should I organize that? Clutter up the plugin file with another class, or is there a sensible place to extract it? [20:36] elopio: amd64/armhf/rpi2 released to stable [20:52] kyrofa, elopio just a tiny hello :-) [20:52] sergiusens, hey, been a while! [20:52] sergiusens, how's it going? [20:53] kyrofa, fine, 7PM and still discussing things here... talking is tiresome :-P [20:53] sergiusens, yeah... exhausting [20:53] kyrofa, how's it going with you? [20:53] sergiusens, I hope you're sleeping alright [20:54] sergiusens, things are going well! Still adding some ROS features, figuring out snapcraft, whining about the lack of a clean build, etc [20:54] kyrofa, yeah, more than ever, but having to follow conversations for 9 hours straight and then do the same during dinner gets you really tired [20:54] sergiusens, definitely [20:54] kyrofa, hah, clean build I can implement on the way back :-) [20:54] sergiusens, :D [20:55] sergiusens, you should relax on the way back though [20:55] kyrofa, I really want to land the new-cli branch into master ASAP, but I haven't had a chance to fix the integration tests [20:55] sergiusens, ah, yeah that'll be nice [20:55] and it has been a laptops closed meeting [20:56] Oh man... so you REALLY have to pay attention [20:57] yeah [20:58] sergiusens, don't worry man, we'll get there. You can slow down a little :) [21:03] hah [21:03] kyrofa, I am suffering from depravation [21:03] ;-) [21:43] I can't get to Universe. Anyone else? [21:45] Rather, I'm getting a hash mismatch of some kind [21:47] Ah, looks like it's working now [22:11] sooo, I have libxml2-dev installed on the host system and have "stage-packages: - libxml2-dev" in my snapcraft.yaml. I see my configure using getting a .../snap/usr/include/stage/usr/include/libxml2 from pkg-config. However that dir does not exist .... [22:12] shouldnt "stage-packages" ummm ... stage packages? [22:12] ... so that they are actually found where pkg-config claims them to be in the snapcraft env? [22:17] kyrofa: if the helpers are only used in your .py, put them in there with _ in front. [22:18] then if we need them in other module, we can discuss if removing the _, or putting them in a different .py, or both.