/srv/irclogs.ubuntu.com/2015/09/23/#snappy.txt

dholbachgood morning06:13
clobranogood morning dholbach, good morning to all ;)06:14
dholbachhey clobrano06:15
clobrano:)06:47
fgimenezgood morning07:05
davidcalleMorning o/07:24
dholbachmvo, hum... I get the following when I try to run the autopkgtest of snappy:07:44
dholbachPackage gudev-1.0 was not found in the pkg-config search path.07:44
dholbachPerhaps you should add the directory containing `gudev-1.0.pc'07:44
dholbachmaybe build-tools is still required?07:44
dholbachor does libgudev-1.0-dev need to be added to the test depends?07:44
dholbachfgimenez, ^07:44
dholbachI used the following to run the test:07:45
dholbachadt-run --setup-commands="apt-get update" --source ../snapcraft_0.2.dsc --- qemu ~/vm/adt-wily-amd64-cloud.img07:45
=== chihchun_afk is now known as chihchun
fgimenezdholbach, i'll try to reproduce, give me a second07:49
dholbachno worries, take your time07:50
longsleepGood morning snappy :)08:06
Chipacalongsleep: o/08:09
Chipacamvo: o/08:25
mvohey Chipaca08:28
Chipacamvo: mo'in! What's the plan with trunk vs 15.04?08:28
Chipacaclobrano: would you mind signing the CLA, so I can review & land your branch?08:29
mvoChipaca: I would say lets keep them in sync for now, until the next huge change (the os/kernel snap/squashfs work)08:29
mvoChipaca: or how do you feel about it?08:30
Chipacamvo: i ask because we have some branches aimed at one, and some aimed at the other :)08:30
mvoclobrano: here is the link (in case you do not have it yet) http://www.ubuntu.com/legal/contributors08:32
mvoChipaca: yeah08:32
* Chipaca just wants to land all the good stuff08:34
mvoChipaca: ok, lets land it all in trunk08:35
dholbachlool, asac, mvo, ogra, davidcalle, can we move the community sync half an hour earlier today? UE Personal has an Allhands call at the same time08:36
ogra_fine with me08:36
Chipacamvo: that means resubmitting your untar perms fix08:36
Chipacamvo: so i agree ;)08:36
Chipaca(it's the smallest resubmission, compared to landing everything in 15.04, or >shudder< landing in both and two-way-merging08:36
Chipaca)08:36
Chipacahusk retargeted08:38
mvoChipaca: thanks, retargeted08:40
looldholbach: fine with me too08:42
Chipacamvo: did you have a chance to look at fgimenez's comment & error & patch on https://code.launchpad.net/~mvo/snappy/lp1480248-test-reenable/+merge/269176 ?08:49
JamesTaitGood morning all; happy Wednesday, and happy Restless Legs Awareness Day! ☺08:50
ChipacaJamesTait: are you ever not aware of restless legs? isn't that the whole problem?08:50
fgimenezChipaca, mvo lot's of things have change since then, let me check again08:51
JamesTaitChipaca, for those who suffer from the condition, yes.  I think the point is for those who don't even know it exists, to know it exists.08:52
dholbachmvo, asac, davidcalle: fine to move community sync today half an hour earlier?09:19
mvodholbach: fine with me09:23
fgimenezdholbach, i can confirm the problem but can't find a proper solution from the test side, it keeps trying to find the seemingly unexisting gudev-1.0 package, maybe mvo can help09:30
dholbachok09:31
davidcalledholbach, not sure I'll be able to make it, but that's fine :)09:31
dholbachok davidcalle, no worries09:32
dholbachfgimenez, thanks a lot for checking09:32
mvofgimenez: what command should I run to reproduce the issue?09:34
dholbachmvo,09:34
dholbachadt-run --setup-commands="apt-get update" --source ../snapcraft_0.2.dsc --- qemu ~/vm/adt-wily-amd64-cloud.img09:34
mvota09:34
=== ogra2 is now known as ogra-snappy-test
mvodholbach, fgimenez sorry that this took forever, but I know now why the godd example fails, it looks like "go get" already runs pkgconfig (for gudev)  which is a bit odd and breaks snapcraft that only installs it in the build stage10:48
dholbachdon't worry - thanks a lot for looking into it10:48
mvodholbach: I'm trying to fix it no10:50
mvow10:50
* dholbach hugs mvo10:50
fgimenezdholbach, ok thanks a lot :)10:53
fgimenezmvo,  ^^ :)10:55
mvofgimenez, dholbach: do we have a bug for this autopkgtest failure already?10:59
dholbachno, I don't think11:00
sergiusensmvo, dholbach that is strange, stage-packages are downloaded and unpacked during 'pull'11:04
mvosergiusens: yeah, I think I found the issue11:05
sergiusensmvo, ted has a branch to fix paths from pkg-config fwiw11:05
sergiusensbut it is failing its tests :-)11:05
mvosergiusens: give me 5min to verify, it seems like its downloading and building when it really should just download11:05
mvosergiusens: I push a branch11:05
sergiusensmvo, okie dokie11:05
sergiusensmvo, btw, wrt pkg-config https://code.launchpad.net/~ted/snapcraft/pkg-config-sysroot/+merge/27175111:15
mvosergiusens: yeah, this one is missing11:15
=== chihchun is now known as chihchun_afk
sergiusensdholbach, want to look at this one https://code.launchpad.net/~sergiusens/snapcraft/pull-python-projects/+merge/272057 ?11:57
dholbachsergiusens, I'm a but busy with something else right now12:04
dholbachasac, around?12:04
Chipacasergiusens: what was it you wanted me to review?12:09
Chipacaelopio: fgimenez: could you guys not be shy with "needs fixing" in reviews? makes finding things needing reviews a lot easier12:10
Chipacae.g. https://code.launchpad.net/~fgimenez/snappy/1504_validation/+merge/27177712:11
Chipacathat's a needs fixing, if i'm reading elopio's comments right12:11
Chipacasame as https://code.launchpad.net/~elopio/snappy/new_kernel_file_name/+merge/271901 wrt fgimenez's comment12:11
sergiusensChipaca, https://code.launchpad.net/~sergiusens/snapcraft/pull-python-projects/+merge/27205712:13
Chipacafgimenez: mvo: also what's up with https://code.launchpad.net/~mvo/snappy/lp1480248-test-reenable/+merge/26917612:13
sergiusensfgimenez, all plainbox changes are missing in snapcraft now :-P12:14
Chipacait's nearly a month old, and i don't know12:14
fgimenezChipaca: wrt https://code.launchpad.net/~elopio/snappy/new_kernel_file_name/+merge/271901 i'm asking for confirmation, not sure if my results are reproducible, anyway you are right, i'll try to be more explicit12:16
clobranoChipaca, mvo: sorry I was out of office, I'll look at it as soon as possible12:17
mvono worries :)12:17
fgimenezChipaca, i'll take a look at test-reenable branch, iirc there's other disabled test that we should be able to reenable12:19
fgimenezsergiusens, "missing" sounds bad... :)12:21
sergiusensfgimenez, it seems to work now... not sure if it was a plainbox thing, as I got a huge message saying it was analyzing stuff and then exited12:22
clobranomvo: what's "Project Contact" in CLA?12:23
Chipacaclobrano: Alexander Sack, afaik12:23
clobranoChipaca: ok, thanks12:24
Chipacaasac: right?12:24
dholbachmvo, ogra, lool: I haven't heard back from asac about the call, but didn't have too much to bring up apart from a clinic date - I can talk now, but can't in 30m - what do we do?12:26
loolclinic?12:27
looldholbach: I dont have much either12:27
looldholbach: I wonder: should we pull in davidcalle in these calls in the future? he's been working on the public facing docs too IIUC12:27
dholbachlool, snappy clinic12:27
looloh right12:27
dholbachlool, yes, he's invited12:27
dholbachbut he couldn't attend today12:27
loolah ok12:27
looldholbach: well I dont mind if we skip today, albeit I have missed last week so perhaps you want to sync real quick12:28
dholbachsure12:28
looldholbach: asac is often triple-booked, so I wouldn't worry about his avail as much12:28
* lool joins HO12:28
loollet me grab a headset of some sort12:28
ogra_one sec, gimme 3min12:29
mvodholbach: sure, joining now12:29
mvodholbach: hm, ff crashed, one sec12:32
clobranoChipaca: CLA signed, thank you ;)12:45
sergiusensdholbach, btw, is there a calendar entry for the snappy clinic?12:46
sergiusensor am I meddling :-)12:46
sergiusens?12:46
ogra_sergiusens, there isnt12:47
ogra_(we were just searching)12:47
dholbachsergiusens, no - I have no idea -- we just thought about it and asked if we shouldn't do it on Friday or are you flying there?=12:48
asacdholbach: for me that comm call is at 3 :)12:48
tedgsergiusens: were you able to get the pkgconfig tests to fail locally?12:49
dholbachasac, I have a call at the same time12:49
sergiusenstedg, hah, dholbach has12:50
sergiusenstedg, well he added the exact cause to the MP12:50
sergiusensdholbach, I am out Friday12:50
* tedg looks12:50
dholbachsergiusens, ok.....12:50
tedgHmm, mail still syncing12:50
sergiusenstedg, that's not a problem with webmail12:52
sergiusens:12:52
sergiusens:-P12:52
tedgsergiusens: Yes, but *everything* else is :-)12:54
sergiusensfgimenez, should we make tarmac run the examples?12:55
dholbachsergiusens, lool suggested tomorrow 12:30 UTC - would that work for a clinic for you?12:58
sergiusensdholbach, perfect12:58
lool13:30 UTC actually12:58
looloh sorry12:58
tedgsergiusens: dholbach: I'm not seeing it... where was it?12:58
* tedg can't beleive that LP didn't send him e-mail about something12:59
dholbachtedg, it's a new suggestion12:59
loolhalf an hour ago, tomorrow12:59
sergiusenstedg, look it up on the web, don't be lazy ;-)12:59
loolin 23h3012:59
fgimenezsergiusens not sure, i think that elopio and dholbach talked about that a few days ago12:59
dholbachtedg, it never was in the calendar :)13:00
tedgAh, on the MR.13:01
Chipacaclobrano: did you get an email or something when signing the CLA?13:03
Chipacaclobrano: trying to figure out why the person that does the paperwork at our end hasn't received the email yet13:03
clobranoChipaca: nope13:03
clobranono emails13:04
sergiusensChipaca, clobrano if it is showing up on launchpad I think it should be fine13:04
Chipacasergiusens: it isn't13:04
Chipacasergiusens: that step is manual, unless i'm very mistaken13:04
Chipacathat is: there is a person at canonical that receives a particular email, and adds people to a particular laucnhpad group13:04
clobranomaybe I'm missing the GPG key..13:05
Chipacabut maybe the email goes to asac?13:05
sergiusensyeah, that cn do it13:05
clobranoopenPGP13:05
sergiusensgpg missing means there is nothing to sign with13:05
sergiusensfgimenez, super simple one https://code.launchpad.net/~sergiusens/snapcraft/no-test-print/+merge/27209913:05
=== dholbach_ is now known as dholbach
rickspencer3hi all13:16
rickspencer3I'd like to upgrade my rpi2 to the latest and greatest with rolling13:16
rickspencer3can anyone easily give me the right commands to get and build the correct image?13:16
ogra_rickspencer3, wily you mean ?13:20
fgimenezsergiusens ok done, if needed the tests could use the logging module13:21
rickspencer3ogra_, I dunno, I'd like to get daily updates13:22
rickspencer3I assumed that I would get on "rolling" for that13:22
ogra_rickspencer3, well, we do daily builds in 15.04/edge and in rolling/endge13:22
ogra_the latter is wily based13:23
rickspencer3ogra_, I think rolling/edge13:23
ogra_ok ... not sure if it works, i doubt anyone ever tried booting that on a rpi ....13:23
rickspencer3ogra_, ok, nm13:24
rickspencer3I'll take 15.04/edge, then :)13:24
ogra_sudo ubuntu-device-flash core rolling --channel edge --developer-mode --oem pi2 --device-part  device-pi2-0.15.tar.xz -o pi2-rolling-edge.img13:24
ogra_that would be the line for rolling13:24
ogra_and indeed you need the device tarball13:24
ogra_from http://people.canonical.com/~platform/snappy/raspberrypi2/13:24
rickspencer3ogra_, right, but if it is not even tested to boot on the rpi2 yet, I think I would be better off with 15.04, I guess13:24
ogra_then you just replace the "rolling" in that line with 15.0413:25
sergiusensrickspencer3, we don't guarantee a boot on edge though13:25
ogra_i'm waiting for the kernel package to land in the archive (stuck in -proposed) and will then provide an upgraded device tarball13:26
rickspencer3ogra_, so I should wait until later today?13:26
ogra_right, what sergiusens said ... but i booted edge the last days13:26
rickspencer3I kind of sorta am desperate for pwm support13:26
ogra_rickspencer3, depends on how fast the archive admins and rtg are13:27
ogra_there is a packaging bug he needs to fix13:27
rickspencer3ok13:27
tedgsergiusens: Adding PKG_CONFIG_PATH, can't really remove GLib on my system to test it though. I still doesn't fail here :-)13:27
ogra_i wouldnt hold my breath for "landing today"13:27
ogra_but there is always hope indeed :)13:27
sergiusensChipaca or mvo mind looking at https://code.launchpad.net/~sergiusens/snapcraft/printless/+merge/272101 ?13:27
rickspencer3ogra_, well, if I won't get pwm today, there is no point to upgrade, I'll stick with what I have for now13:27
ogra_by end of week i hope we'll have an auot-built rolling/edge image ... if that works i'll move that to 15.04 next week13:28
ogra_*auto-built13:28
sergiusenstedg, run in lxc/lxd or apt remove glib13:28
sergiusenstedg, no one builds with glib these days anyways ;-)13:29
ogra_inbetween i might do a release of 15.04 #5 for the RPi13:29
tedgDoesn't systemd use glib?13:29
tedgOh, I guess this is only the dev package.13:30
sergiusenstedg, yeah :-)13:30
sergiusenstedg, or chose a different -dev pkg with pkg-config support :-)13:30
ogra_the binary only uses the "c" version of glib13:31
ogra_:P13:31
tedgIt seemed like the others would all pull in glib.13:35
tedgSure there's some13:35
mvosergiusens: I got some extra homework, I'm not sure I can get to it13:42
sergiusensmvo, ok, I'll bug Chipaca or maybe tedg :-)13:43
clobranoChipaca: the CLA seems signed now13:46
rickspencer3ogra_, I guess I should ask .. does the rpi2 current support spi?13:48
* rickspencer3 asks after having fully wired it together with his MCP300813:48
ogra_rickspencer3, find /sys -name '*spi*'13:51
ogra_;)13:51
* rickspencer3 hopes that is a "yes" :)13:52
ogra_i see devices when i do that but i have no idea if the default devicetree enables any of them13:52
ogra_you might need to apply an overlay for it13:52
rickspencer3arg13:56
rickspencer3ok, I'll have to wait a bit to try it out13:56
rickspencer3will see later13:56
ogra_(RaspberryPi2)ubuntu@localhost:~$ cat  /sys/firmware/devicetree/base/soc/spi@7e2004000/status13:57
ogra_disabled13:57
ogra_yeah, as expected13:57
sergiusenstedg, any luck with pkg-config?14:23
tedgsergiusens: Still building the lxc image14:23
=== ogra2 is now known as ogra-snappy-test
tedgsergiusens: I'm now getting this, no clue what to do with it: http://paste.ubuntu.com/12531319/14:33
sergiusenstedg, oh nice,14:45
sergiusenstedg, merge trunk; the run test rework reverted a change to only mccabe check or project14:45
sergiusensshould be fixed in trunk again; this most likely happened after pulling in external sources14:46
=== ogra2 is now known as ogra-snappy-test
tedgsergiusens: Merged trunk, still got the same error15:06
clobranoQUESTION: what is snappy update --automatic-reboot? How it is triggered?15:19
=== chihchun_afk is now known as chihchun
Chipacaclobrano: what do you mean how is it triggered?15:26
=== chihchun is now known as chihchun_afk
tedgsergiusens: Thinking let's just let tarmac give it another try.15:27
mvoclobrano: we have a systemd unit that runs it every N hours15:27
mvotedg: at what point in the build do you get that?15:27
sergiusenstedg, sure; did you fix anything already?15:27
mvotedg: do you use LC_ALL=C in your environment? could you try LC_ALL=C.UTF-8 instead?15:28
tedgmvo: When doing "./runtests.sh"15:28
tedgsergiusens: Yeah, I added the environment variable and cleaned up the long lines.15:28
clobranomvo, Chipaca: I was testing snappy, and I got a message like "another snappy is running". Does it really do an automatic reboot from time to time?15:29
elopiosergiusens: tedg: what I know is that I got the same error in testtools because my locale is EO https://github.com/testing-cabal/testtools/issues/7615:29
tedgmvo: Cool, that moved forward. New error :-)15:29
Chipacaclobrano: unless you've disabled that, yes15:29
tedgWe need a release so that apt-get build-dep works again :-)15:29
sergiusenstedg, hah :-)15:30
Chipacaclobrano: if you're logged in when it happens, you'll get a message plus given a way to cancel the reboot15:30
clobranooh ok, I didn't see that message, yet15:31
elopioogra_: is it safe to assume that sectors will be 512 bytes?15:42
ogra_elopio, i think sergiusens hardcoded that recently, so yes15:42
elopioyay for sergiusens!15:42
sergiusensogra_, that's such a stron word :-P15:44
tedgsergiusens: Okay, verified it works :-)15:44
sergiusenstedg, \o/15:44
ogra_elopio, i think sergiusens polished the code to support that recently, so yes15:45
ogra_sergiusens, sounds better ?15:45
ogra_:)15:45
elopioit's configurable, but only one option is supported at the moment :)15:46
sergiusenselopio, choose wisely!15:46
sergiusenstedg, your mixing of " and ' will disturb elopio :-P15:47
elopiotedg: oh yes. No beers for you on our next sprint!15:48
ogra_tedg, just switch to » and «15:49
* tedg uses all the quotes15:50
bjfi'm trying to use the doc @ developer.ubuntu.com for the rpi2 regarding "building your own image". neither example actually works15:51
tedgsergiusens: I think that " is only used for shell strings...15:51
bjf1. can we clean up the examples to ones that work and 2. is there other documentation that is more up-to-date?15:51
sergiusenstedg,         env.append("PKG_CONFIG_PATH=" + ':'.join([15:51
sergiusenstedg, in PKG_CONFIG_PATH ;-)15:51
sergiusenstedg, I can build godd again, so I don't care ... mvo and his project names ;-)15:52
sergiusenstedg, building a couple of c based projects to triple check15:53
elopiofinally, the resize test passed again!15:54
elopiobjf: can you please report bugs for the issues you are getting?15:54
bjfelopio, against which package/project?15:54
elopiobjf: ogra_ here is working on rpi, so he can tell you more.15:54
longsleepbjf: Take a look at https://github.com/longsleep/snappy-odroidc - thats how i build my images if you want to look at working examples15:55
tedgAh, found one. Fixed it.15:55
elopiobjf: https://bugs.launchpad.net/developer-ubuntu-com/15:55
ogra_bjf, hmm, what exactly isnt working ?15:55
ogra_(i know they did once mention versions, but we replaced that by * )15:56
bjfogra_, https://pastebin.canonical.com/140433/15:56
bjfogra_, there is a link there "from Paolo Pisati's binary build" that says it's to a device tarball but pulls down a .deb15:58
ogra_bjf, well, i'm in the process to make official images, that whole section will be obsolete in a week or so15:59
ogra_hmm, your paste looks like someone reverted my changes16:00
elopiosergiusens: I think that on your release notes you should mention more clearly that yamls with the previous format won't work, and need to be updated.16:00
sergiusenselopio, sure, feel free to write that down16:01
ogra_bjf, "On this page, you will find pre-built bits to bootstrap your Raspberry Pi 2 with a Snappy image." ... there is a link in that line16:09
ogra_i dont think it is wrong to mention that the device tarball includes palos kernel16:09
bjfogra_, yup and that works. i get an image that i can dd and the rpi2 will boot16:09
ogra_(or to link to it)16:09
ogra_could surely be phrased better16:10
ogra_but as i said, will be obsolete very soon16:10
ogra_we'll soon have all bits properly on the server once the linux-raspi2 package migrates out of -proposed16:10
bjfogra_, i am trying to build my own image and the instructions for doing so don't work. do you suggest i wait for a couple of weeks and try again?16:11
elopioChipaca: the 15.04 we want to release is in edge now?16:11
Chipacaelopio: at this stage, i don't know16:11
Chipacaelopio: it's on trunk16:11
Chipacaelopio: is edge getting built from trunk?16:12
Chipacaelopio: I don't know16:12
Chipacaogra_: do you?16:12
elopioshould be, but that something fails. Chipaca, but lp:snappy/15.04 right, not lp:snappy ?16:13
ogra_bjf, didnt you just say it works ?16:13
bjfogra_, i just read it all a couple more times, maybe i see my mistake16:13
Chipacaelopio: lp:snappy16:13
Chipacaelopio: which should be in sync with 15.0416:13
Chipacalet me just doublecheck that16:13
ogra_edge is getting built from the PPA16:13
ogra_wether your trunk change ends up in the PPA snappy package by default i dont know16:14
Chipacaogra_: 15.04 edge16:14
ogra_yes16:14
Chipacaok16:14
elopioChipaca: right, I see the latest merge. But now I'm confused, why do we have the 15.04 branch?16:14
Chipacaelopio: because they're in sync only because disruptive changes haven't landed yet16:14
Chipacaelopio: and because mvo is in pre-sprint-rush so is less tidy than usual16:15
elopioright. Not complaining here :)16:15
Chipacanor here16:15
Chipacaelopio: trunk has two revs that are not in 15.0416:15
Chipacaelopio: and we want them in the release16:15
Chipacaas they're both small but nasty bugs16:15
* Chipaca hugs 'bzr missing'16:16
elopioif I understand correctly, the recipe for lp:snappy/15.04 puts the vivid version on the ppa, which is used to build 15.04 edge. The recipe for lp:snappy puts the wily version on the ppa, which is used to build rolling edge.16:20
ogra_elopio, right, someone needs to move the commits over16:21
elopioChipaca: if so, we need your update-qualified-name backported to the lp:snappy/15.04, rerun the recipe, and ask somebody to trigger and edge build.16:21
ogra_and we need to decide if we should just drop lp:snappy/15.0416:21
ogra_and simply use lp:snappy for both16:21
Chipacaelopio: ahead of you :)16:21
* ogra_ would actually prefer if we did all developmennt in 15.04 16:21
ogra_saves all the backporting :)16:22
Chipacaelopio: https://code.launchpad.net/~chipaca/snappy/trunk-to-15.04/+merge/27214016:22
bjfogra_, i think i'm closer. i downloaded all the files "this page" pointed me at of pre-built bits. https://pastebin.canonical.com/140436/16:23
ogra_bjf, hmm, is your ubuntu-device-flash outdated ?16:24
bjfogra_, ubuntu-device-flash          0.31-0ubuntu116:24
elopiowow, launchpad is really crazy16:25
bjfogra_, does it look in the current directory for what is specified by the --oem flag ?16:25
ogra_it shoudl16:25
ogra_bjf, the 0.15 pi2 sanp is in the store though, "--oem pi2" should work as well16:26
elopioChipaca: take a look at the recent revisions in https://code.launchpad.net/~snappy-dev/snappy/snappy16:29
elopiowhat it shows as merged branches don't match with the rev.16:29
elopiosomebody will have to calm William's wrath for breaking launchpad.16:29
bjfogra_, similar error trying just "--oem pi2": pi2 failed to install: snappy package not found16:32
ogra_bjf, very weird16:33
bjfogra_, indeed. feels like i have some basic misconfiguration which i don't understand16:34
ogra_well, the official image was created exactly the same way16:34
ogra_bjf, i'm super busy with some customer stuff, i'll take a look later and try to roll an image here16:41
bjfogra_, ack16:41
ogra_(if you dont find a solution before)16:41
ogra_bjf, any reason why you dont use the pre-built image ?16:41
bjfogra_, that does work... i'm trying to come up to speed so i can start testing rpi2 kernels16:42
ogra_bjf, ah16:42
ogra_well, you can just cp the binaries in place over the ones in /boot/uboot/b and /system-b/lib/modules as a quick fix ... then run: sudo fw_setenv snappy_ab b ... and reboot16:45
ogra_(that will boot into the b system, and should reboot back into a if something fails16:45
ogra_)16:45
elopioChipaca: snappy 15.04 failed to build for arm64. We don't care about that one, right?17:39
ogra_nope17:39
ogra_definitely not on 15.0417:39
elopioogra_: can you kick 15.04 edge to pull this version?17:39
ogra_not yet17:39
ogra_waiting for a few other changes before i can build an image17:40
ogra_but yeah, as soon as i can17:40
elopioogra_: cool. Let me know.17:40
elopiosergiusens: what you want to release is snapcraft from trunk, or snapcraft from the tools-proposed ppa?17:41
* Chipaca hugs elopio 17:42
elopio:D17:43
ogra_Chipaca, elopio, image build kicked off17:45
elopiodholbach: I think you send the wrong date on your clinic invitation.17:56
elopiodholbach: really cool idea btw, thanks.17:56
dholbachelopio, sent an update17:57
dholbachJeff Lane noticed the same17:57
dholbachsorry, mail was in the moderation queue17:59
sergiusenselopio, snapcraft - 0.2-0~207~ubuntu.* which is building now18:03
sergiusenselopio, build is done; I'm doing a test build of all the example packages18:24
raynhello there. Cant find a way to edit files, like in nano. Is there an editor?18:49
plarsogra_: does the boot process on rpi2 read snappy-system.txt at any point? I'm not seeing where it does, but if not, I'm confused how it knows whether to use snappy-a or snappy-b18:49
ogra_plars, out of uboot.env18:50
ogra_snappy-system.txt is obsolete18:50
ogra_rayn, there is vi18:50
plarsogra_: oh! that could mess me up I guess18:50
plarsogra_: so if I'm booting snappy from a usb stick, is it going to rewrite the one on the mmc or on the usb stick?18:51
ogra_plars, it is like that since the 15.04 #4 release ... i.e. like 8 weeks ago (or was it more) for all arm boards18:51
plarsogra_: It just recently started mattering for me, due to looking at how to automate rpi218:51
ogra_it is going to rewrite the one in /boot/uboot/a|b18:51
ogra_the rewriting happens from a systemd job18:52
plarsogra_: ok, so it's going to rewrite the one on usb, which is safer, but I'm not going to be able to see those changes18:52
raynogra_ thanks18:52
ogra_fw_printenv will show them18:52
ogra_we ship it18:52
ogra_(and you can modify them with fw_setenv if needed)18:53
plarsogra_: I'm not sure how that will help me unfortunately :(18:53
plarsbut thanks18:53
plarsthis may just be a limitation on rpi for now18:53
ogra_it is like that on all arm installs now18:54
elopiosergiusens: I've verified all the points on your release notes. I'm happy with this release.18:54
plarsogra_: well, on bbb we have two places to boot from, so it's fine18:54
elopioand tomorrow we'll get many new eyes to catch interesting bugs for 0.318:54
plarsogra_: but on rpi2 we have to fake it18:54
sergiusenselopio, yup; ok now I need confirmation from asac ;-)18:54
sergiusenswell I guess he already knew :-P18:54
elopiosergiusens: we can blame him when things are on fire because he missed the stand up ;)18:56
asacsergiusens: whats the one line summary of what i knew? :)19:06
sergiusensasac, looking good (is that a valid summary?)19:07
elopiosergiusens: could you push a new version to the store for a package with no alias?19:27
sergiusenselopio, which package?19:45
elopiosergiusens: anyone from our examples.19:45
elopiobut please tell me before you do it so I can check.19:45
sergiusenselopio, examples from snapcraft?19:46
elopiosergiusens: no, like hello-world and those. I'm not sure which have alias.19:46
elopioI just need one with no alias to show me an update.19:46
sergiusenselopio, oh, it is easy to check19:46
sergiusenselopio, but why not upload hello-world to your own account?19:47
sergiusenselopio, unless you are talking about an automated tests19:47
elopiosergiusens: no, I think that will work.19:47
elopiolet me play with my own account.19:47
sergiusenselopio, it should :-)19:48
elopioChipaca: I installed 15.04 alpha #179 and it seems to lad the ppp service properly. But after updating #178 to #179, it shows the same bug.19:49
elopios/lad/load19:49
Chipacagrmbl19:50
elopiohum, what's the command to update one snap?20:01
elopioI think I've never tried that.20:02
Chipacaelopio: there isn't one20:03
Chipacaelopio: not from the commandline20:03
sergiusenselopio, I don't think you can20:04
sergiusenselopio, well, you can try and install it again20:04
Chipacaelopio: you can via the REST API though :)20:04
elopioyeah, the problem is that if I'm in #178 and do snappy update, it will go to #179 instead of updating the snap.20:05
Chipacaelopio: rest api rest api20:05
elopioso I can't confirm the problem. But I could update hello-world on #179. Is that good enough Chipaca?20:05
Chipacano20:05
Chipacabecause hello-world has an alias20:05
Chipaca:)20:06
Chipacaor :-(20:06
elopioChipaca: not the one I'm using. hello-world.elopio.20:06
Chipacaah, ok :)20:06
Chipacathen yes :)20:06
Chipacaelopio: "list -u" is also broken before20:06
Chipacaelopio: ie it doesn't show an update for a non-aliased package20:07
Chipacaelopio: and the broken part is the same between that and update20:07
elopiook, let me try that.20:07
Chipacaelopio: otherwise echo '{"action":"update"}' | uPOST /1.0/packages/hello-world.elopio20:08
Chipacafor funky values of uPOST20:08
elopio#178 doesn't show the update. #180 shows it. All good.20:10
elopioso, the two bugs are fixed. But for the ppp one, it will remain failing if you are updating from our previous stable.20:11
Chipacaelopio: is that even if you haven't touched the config?20:13
elopioChipaca: the only thing I did was systemctl status.20:14
elopioI restarted the service in #180 and now it seems fine.20:26
jdstrandwhoever implemented 'snappy service', kudos!20:28
jdstrandasac: feel free to pass that along :) ^20:28
jdstrandit works great and is super helpful20:28
sergiusensChipaca, ^20:30
Chipacajdstrand: and it's not finished yet!20:31
jdstrandI can't wait to see the new stuff :)20:31
Chipacajdstrand: it should give you service and security logs20:31
jdstrandoh, nice indeed20:31
jdstrandI think it has service logs already, no?20:31
jdstrandor is that different?20:32
Chipacaah, yes, just not in 'status'20:32
Chipacaoriginal request was to have all that in status output20:32
jdstrandI see20:32
Chipacabut i think it'd be messy unless you're asking about a particular service20:32
Chipacaanyway, thanks :)20:33
jdstrandChipaca: re messy: fwiw, I like the separate logs command for that reason. status is different than logs imho20:37
Chipacaoh, it wouldn't replace the separate logs, just give you a snippet if you've got space20:39
Chipaca*handwaving intensifies*20:39

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