[10:30] <caribou> mhcerri: hi, I'm puzzled by the 4.15 panic so I'm going to bisect this one as well
[12:28] <caribou> ok, bisection confirms that it is the same commit :
[12:28] <caribou> https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=091554e4a5b2a7647830a1c7beea781148b51509
[12:39] <mhcerri> caribou, thanks a lot for confirming it and bisecting it


[00:01] <ckontros> ScottL: I'm slowly but surely figuring out how to set things in XFCE. (hacking on xubuntu-settings) I hope to upload something in two weekends.
[00:52] <ckontros> PM if ya need me.
[01:48] <ScottL> another strange lockup :|
[06:29] <Kokito> howdy
[06:55] <holstein> jerry_l: o/
[06:55] <holstein> hey Kokito
[06:55] <jerry_l> hello room i have to go to bed. sorry...
[06:55] <Kokito> good night jerry_l
[06:55] <Kokito> hi holstein
[06:56] <Kokito> will not be here long. they are about to kick me out of the the coffee shop :)
[06:56]  * holstein checking in on the mailing list
[06:56] <holstein> Kokito: lots of activity
[06:56] <holstein> i think thats good
[06:56] <Kokito> yep
[06:57] <Kokito> I'm liking it
[06:59] <Kokito> gotta go
[06:59] <Kokito> ciao!
[06:59] <holstein> Kokito: laterx
[13:01] <ScottL> just got done with the linux outlaws interview...i *think* it went well, didn't focus too much on unity which is good
[14:28] <astraljava> ScottL: Well done! :)
[16:10] <scott-work> hi Kokito :)
[16:10] <scott-work> i answered one of those emails and included your questions on the timeline wiki
[16:10] <Kokito> good morning scott-work
[16:11] <Kokito> yes, thank you!
[16:11] <scott-work> Kokito: you are east coast US, correct?
[16:11] <Kokito> scott-work: I am in CA
[16:11] <scott-work> Kokito: i should have answered before, but there is so much going on that it's easy to move onto something new before completing the current task and then forget about it
[16:11] <scott-work> Kokito: so it really is morning for you :)
[16:12] <Kokito> no worries about the timing of the reply
[16:12] <Kokito> and, yes, it's morning here :)
[16:24] <scott-work> Kokito: the "blob" i was talking about was the banner being used for the new website
[16:24] <scott-work> do you have a link to your demo again...i'll look on the mailing list for it
[16:25] <Kokito> scott-work: the banner being the header where the logo is?
[16:25] <Kokito> http://myhaiku.org
[16:25] <scott-work> aye, all the orange, blue stuff up there
[16:26] <scott-work> granted, that does look MUCH better than the other stuff that we used to have
[16:27] <Kokito> that is very likely to change, but I want to see how the desktop theme turns out before I can tell to see if it will
[16:28] <Kokito> either way, I have a hard time visualizing a granite backgorund there
[16:29] <scott-work> Kokito: but i was wondering if we replaced "ubuntu studio    linux for digital creaters" and the image with a grey or green stone background with "ubuntu studio" etched into it, how it would look
[16:30] <scott-work> like the last image  http://imageshack.us/m/683/6924/ubuntustudiowallpaperdr.jpg
[16:30] <Kokito> the etching would look nice, but I don' think a stone surface would fit (regardless of the color)
[16:30] <scott-work> but with the words "ubuntu studio" etched into the stone
[16:30] <scott-work> maybe not "stone" but slate looking
[16:30] <Kokito> ok, I see wnat you mean now :)
[16:31] <Kokito> yeah, that's a possibility
[16:32] <Kokito> although I wanted to keep the existing dotted grid, as a way to subtly align with the Ubuntu official theme
[16:32] <Kokito> but this is something we can try
[16:33] <Kokito> I would like to wait for Izo's mockups before I make any moves, though
[16:35] <Kokito> bbl
[16:38] <scott-work> oh yeah, defintely wait...i was just throwing out an idea and hopefully it sparks someone else to make a brilliant suggestion or concept
[16:39]  * scott-work doesn't usually have brilliant ideas
[17:03]  * astraljava thinks scott-work has a sense of sarcasm at the very least...
[17:37] <scott-work> astraljava: lol, i do employ sarcasm from time to time
[17:37] <scott-work> holstein: you made a wiki page a few weeks ago, something that had /ubuntustudio/oneiric/*  as the link, do you remember what it was?
[17:37] <scott-work> i wanted to duplicate this structure and move some information using it
[17:40] <scott-work> someone had a good idea, i wonder if we couldn't disable pulse audio with a postinstall file
[17:53] <astraljava> scott-work: In general, there's pretty much anything that you can do in a postinstall file, as it's a script that is being run in root privileges. I guess the question is whether QA lets it slip past. But that's politics, then, and you'll do fine in that area. :D
[18:09] <scott-work> astraljava: i'm less worried about QA than i am about logistics and functionality
[18:09] <scott-work> i'll explain that a bit
[18:09] <scott-work> if you mean QA as in Ubuntu QA, then, yes, I am less worried about that because the changes we make will only affect our users and not the general user base for Ubuntu
[18:10] <scott-work> but if we did stop pulse audio we still need to make sure everything else works
[18:11] <scott-work> and some stuff might not...like skype which is currently built with only pulse audio support, you can't select jack like you used to
[18:12] <holstein> scott-work: im pretty sure is was https://wiki.ubuntu.com/UbuntuStudio/Oneiric/Timeline/
[18:12] <scott-work> heh, i think you are right and i already knew about it :P
[18:12] <holstein> i started it, and you made it really nice with the table and all that
[18:12] <holstein> i remember throwing a couple of options out though at the time
[18:35] <scott-work> i'm not feeling well and going home now :/
[18:50] <astraljava> ScottL: My referring to QA was mostly the Power That Be, who review these sort of things. I'm fairly confident we can't cover all the scenarios with one script, which leads to finding out as many as possible during testing, and then documenting the failing ones in release notes or some tech docs, so that users _who read those_ won't be baffled.
[18:51] <astraljava> ScottL: Of course that means like 6% of the installers, so we'll have a lot of explaining to do if we release with such settings. But then that's what wiki is for, right?
[18:51] <astraljava> ;)
[18:51] <astraljava> ScottL: Also, hope you feel better soon!
[20:38] <saidinesh5> hmm........ finally got Ubuntu Studio (read: what use is the "College Work" partition after graduating....)
[20:38] <astraljava> I don't know... nostalgia?
[20:39] <saidinesh5> well i really can't notice (m)any changes from what i ve tried 2-3 years ago
[20:39] <saidinesh5> didn't the apps or anything change at all?
[20:40] <astraljava> I think most of the progress happens under the hood. But shouldn't ardour at least have progressed muchly?
[20:40] <astraljava> Visually, not much has changed.
[20:40] <saidinesh5> also i noticed that there is no real time kernel this time
[20:40] <astraljava> The theme is pretty much the same.
[20:41] <saidinesh5> back when i tried it, i remember screwing things up after installing nvidia drivers
[20:41] <astraljava> saidinesh5: That's because the -rt patchset isn't being implemented on all kernel revisions.
[20:41] <saidinesh5> ah that reminds me, compiz isn't working for me :-/
[20:41] <astraljava> I can't imagine you wanting to use compiz anyway for recording or the like.
[20:41] <astraljava> Why waste any cycles for that?
[20:42] <saidinesh5> astraljava: lol have been coming from KDE... but compiz anyway taxes the GPU, which would otherwise be sitting idle
[20:43] <saidinesh5> also if compiz is running it kinda gives the "Ah well i have the graphics card working too" feel :P
[20:44] <saidinesh5> but ya, my first over all impression is the thing is screaming for lots of polishing....... at least with the apps and there definitely is a need for a better launcher...
[20:44] <saidinesh5> is there some road map or soemthing
[20:45] <saidinesh5> which would help me pick where to contribute?
[21:25] <astraljava> saidinesh5: Okay, cycles was a wrong term. Eating more resources woulda been better, but granted, at the moment I'm not very well educated how much more it would take.
[21:25] <astraljava> But in some cases, everything matters.
[21:26] <astraljava> saidinesh5: Currently I'm not so sure about this just started devel cycle. I believe the guys had one meeting in April, but nothing during May.
[21:27] <astraljava> I'd suggest sticking on the channel for staying up-to-date.
[21:39] <persia> astraljava, My concern is that it's really hard to distinguish Ubuntu Studio users from users of other flavours on a running system, for cases like "Upgrade from Vanilla".
[21:42] <saidinesh5> oh sorry was away (had to bid goodbye to friends)
[21:43] <saidinesh5> persia: ++
[22:53]  * ckontros waves
[23:02] <persia> evening ckontros
[23:04] <ckontros> Hi Emmet. It's been a bit. I was wondering if you felt any impact from all the quake/tsunami/reactor mess?
[23:05] <persia> Oh, heaps, although it's over now.  Although my house was a wreck, nobody was hurt, and there wasn't that much damage (and no structural damage).
[23:06] <persia> The most amusing bit about the reactor mess is that when I went to UDS everyone wondered how I could live with all the radiation, and were a bit shocked when I told them that the radiation they were experiencing at UDS was higher than that in Tokyo at the time.
[23:06] <ckontros> Oh wow. Sorry to hear. But good that it's over now. I have family in Okinawa but they are way far away from where things happened I gather.
[23:07] <persia> Oh, yeah, Okinawa is very far away.
[23:07] <ckontros> hahaha. :) We've had alot of news here 'bout how it compared to Chernobyl.
[23:08] <ckontros> Was another today about how the radiation is worse than thought since the rods melted.
[23:08] <persia> No comparison.  When you put a reactor in several layers of shields, you have a chance.  When you put it in a pit in the ground, you have a problem waiting to happen.
[23:09] <ckontros> Gotcha
[23:09] <persia> Yeah, radiation inside the shielding is way worse than expected, making it hard to deal with recovery.  Radiation levels outside the plant are well known, and (aside from very close), less than the background radiation in many cities around the globe.
[23:11] <ckontros> With the Chernobyl stories, they've talked again about what actually happens there. Its actually pretty neat. There's a wide zone that closed off but there's still folks that live inside it. Not at ground zero but still live with a higher level of rads that normal. Totally on their own. Was pretty cool.
[23:12] <persia> Yeah.  The stories from the Chernobyl exclusion zone are fairly interesting.
[23:13] <persia> It's not precisely "safe", but it's one of the few frontiers available these days.
[23:13] <ckontros> ScottL: We gotta talk about the seed work. As per the latest Xubuntu meeting they will not be using GTK3. I'd like you to get a bit involved with them. It would only make our efforts stronger.
[23:13] <ckontros> persia: Was also pretty neat what the rads are doing to nature.
[23:14] <ckontros> Weird trees. Odd birds. Freaky. :)
[23:16] <persia> Oh, very much so.  All kinds of oddities.  Did you see the picture set from the woman who did the biking tour a few years ago?
[23:17] <ckontros> persia: Oh yeah. That was great. I have that bookmarked somewhere.
[23:25]  * saidinesh5 waves back to ckontros


[16:19] <pbox> hello, hope everyone is OK! I am having trouble with the lubuntu installer - I can boot fine from the USB but when I try to partition the hard drives the installer crashes
[16:20] <pbox> I wonder if there's a way of starting it from the command line and see if there are error messages along the way - or other forms of troubleshooting
[16:21] <pbox> image checksum matches and the initial filesystem tests do not return any errors
[16:33] <LimeOn> you have problem to create the "/", "/home" partitions or you cant give space to linux from your hard drive?
[16:34] <pbox> the installer allows me to select replace partition
[16:34] <pbox> but once i do it it crashes
[16:34] <LimeOn> you have something else in that partition?
[16:34] <LimeOn> like windows for example
[16:34] <pbox> yes, it's a dual boot machine
[16:35] <pbox> but im replacing a previous lubuntu artition
[16:35] <pbox> partition
[16:35] <LimeOn> oh, i see
[16:35] <pbox> which boots fine
[16:35] <LimeOn> have you tried to delete those and re-make them?
[16:35] <LimeOn> i mean, dont relplace, but make them from "free space"
[16:35] <LimeOn> dont replace*
[16:36] <LimeOn> something like: delete old lubuntu partitions and then create them again
[16:36] <pbox> I thought about doing it with fdisk but decided that i should check before deleting the working system
[16:36] <pbox> ok
[16:36] <LimeOn> yes, thats the problem
[16:36] <LimeOn> you will delete the working one during the process
[16:36] <pbox> anyways, I will give it a try
[16:36] <LimeOn> i remember do what you want and dont have problem
[16:37] <LimeOn> i mean, re-install lubuntu
[16:37] <LimeOn> but you could try that
[16:37] <pbox> yes I find it strainge as well, thats why I was wondering if I could check the error logs
[16:37] <pbox> if there are any
[16:37] <LimeOn> i really dont know that, im sorry
[16:37] <pbox> or if it crashes silently.
[16:38] <pbox> no problem
[16:42] <LimeOn> i suggest you to search in askubuntu
[16:42] <LimeOn> maybe the answer is there
[16:43] <pbox> thanks
[17:58] <alex_> :)
[23:29] <MrCollins> Hello! Can anyone point me at a link for setting up lubuntu without a gui, but easy to configure BIND or DNS server for my home network?
[23:29] <MrCollins> Or perhaps an ISO that has a streamlined linux os that is setup with BIND or another DNS server?
[23:31] <MrCollins> I guess I should state my goal. I have about 7 or 8 old boxes sitting around, and I wanted to make use of a few of them.
[23:36] <tomreyn> MrCollins: you could install ubuntu-server on them, then the software you want.
[23:37] <tomreyn> that's basically like any ubuntu flavour just without the graphical interface
[23:38] <MrCollins> ok 10-4.
[23:38] <MrCollins> does lubuntu havea  server or its just ubuntu itself?
[23:38] <tomreyn> network management works differently on the server than on the desktop by default (can be changed, if needed)
[23:39] <tomreyn> there's just ubuntu-server, which also has an irc channel here
[23:39] <MrCollins> OK. Thank you for your help. Its going to be on older hardware but should be sufficient for my local home network needs.
[23:39] <MrCollins> just DNS serv, thats all I want it to do.


[03:12] <Rlyeh> Yesterday, I Downloaded Snappy from "http://releases.ubuntu.com/15.04/ubuntu-15.04-snappy-armhf-bbb.img.xz"for BBB
[03:12] <Rlyeh> But the system didn't boot
[03:12] <Rlyeh> I checked the "system-boot partition, the "uenv.txt" was empty
[03:13] <Rlyeh> "system-boot" partition
[03:14] <Rlyeh> And there was a install.yaml! It was not available in the version 1!
[03:14] <Rlyeh> Well, do you know how can I boot the new snappy on my BBB?
[03:16] <Rlyeh> Should I have to copy the uenv.txt content from version 1 to this new version? or the boot mechanism is totally changed in new version?
[03:18] <Rlyeh> Here is the uenv.txt in version 1, 2 and 3 -> "http://paste.ubuntu.com/12720512/"
[03:18] <Rlyeh> It's same
[05:49] <Rlyeh> No solution for boot problem?!!!
[06:11] <biezpal> Rlyeh, afaik, uEnv.txt should be empty. There is snappy-system.txt with all required variables
[06:17] <Rlyeh> It's not booting :(
[06:23] <Rlyeh> BBB jumps to debian on emmc
[06:33] <tbr> Rlyeh: did you hold down S2 before connecting power to the BBB?
[06:48] <clobrano> Buongiorno :)
[07:12] <fgimenez> good morning
[07:24] <davidcalle> Good morning
[07:28] <dholbach> good morning
[08:08] <longsleep> good morning snappy
[08:09] <longsleep> biezpal: it is normal that uEnv.txt is empty. Snappy uses uboot.env for booting
[08:10] <longsleep> biezpal: Do you have a serial console, to check what u-boot is doing?
[08:11] <longsleep> biezpal: ah sorry, it was Rlyeh who asked that question
[08:14] <biezpal> longsleep, np :)
[08:22] <ogra_> well, Ryleh most likely didnt press S2
[08:43] <longsleep> ogra_: i should probably get a BBB for testing - S2 is a button?
[08:44] <ogra_> yeah ... also called "user button"
[08:44] <longsleep> ok - and that controls what to boot or why does one have to press it?
[08:44] <ogra_> you have to hold it down for the first time you want to boot from external media (subsequent boots from SD dont need it)
[08:45] <longsleep> ahh - the bbb only boots from nand by default - i get it thanks
[08:45] <ogra_> well, eMMC
[08:45] <longsleep> is the eMMC removable ?
[08:45] <ogra_> nope
[08:46] <longsleep> i see - can snappy also boot when put on the eMMC then?
[08:46] <ogra_> never tried :)
[08:46] <tbr> longsleep: you can nuke the MLO on eMMC, then it will default to SD
[08:46] <longsleep> tbr: right, but would be nice to avoid using an external media or have the sd available for storage
[08:46] <ogra_> buut given we boot based on labels i wouldnt see why not
[08:47] <ogra_> as long as you can name the partitions correctly on the MMC
[08:47] <longsleep> it works fine for the odroid, though the eMCC is removable there and we do not use it because of the cost
[08:47] <tbr> ogra_: I offered a while ago to look into the install script that debian uses and how that could be adapted, but then some handwaving ensued
[08:48] <longsleep> how do you flash the eMMC - is there some boot loader / fastboot thing?
[08:48] <longsleep> i mean if you cannot put it into your pc
[08:48] <tbr> longsleep: you could flash it over USB or UART, but usually you just boot from an SD and write from the booted system to the eMMC
[08:49] <ogra_> there is work going on to create a recovery img we ship in all installs ...
[08:49] <ogra_> that would have a dd like installer i guess
[08:49] <ogra_> and factory reset etc
[08:50] <longsleep> yeah that would be nice
[08:53] <longsleep> tbr: i just read the docs about it, thanks
[08:54] <longsleep> ogra_: do you have an idea what happens if you have partitions with the same label on eMMC and SD ?
[08:54]  * longsleep wonders which one is used
[08:54] <ogra_> nope
[08:54] <ogra_> havent tried
[08:54] <JamesTait> Good morning all; happy Friday, and happy Curious Events Day! 😃
[08:56] <tbr> https://github.com/RobertCNelson/tools/tree/master/scripts - if someone wants to take a look how to adapt
[09:57] <Chipaca> elopio: fgimenez: you around?
[10:18] <fgimenez> Chipaca, yep
[10:18] <Chipaca> fgimenez: i have a branch up for review that probably breaks stuff
[10:19] <Chipaca> fgimenez: could you / would you take a look?
[10:19] <Chipaca> fgimenez: https://code.launchpad.net/~chipaca/snappy/auth/+merge/273684
[10:19] <fgimenez> Chipaca, sure, which one?
[10:19] <fgimenez> Chipaca, ok thanks :)
[10:19] <Chipaca> fgimenez: basically all non-GET rest api tests will fail
[10:20] <Chipaca> fgimenez: or should :D
[10:20] <Chipaca> need to add something to first boot to set a default password
[10:20] <fgimenez> Chipaca, ok, thx i'll check :) we are currently testing post to packages
[10:20] <Chipaca> neat
[11:19] <fgimenez> Chipaca, it fails \o/
[11:19] <Chipaca> heh
[11:20] <Chipaca> fgimenez: thanks
[11:20] <Chipaca> now we need to decide how to un-fail it :)
[11:20] <fgimenez> Chipaca, ok, the tests need some adjustments though, it was passing at first :)
[11:20] <Chipaca> fgimenez: oh? how?
[11:21] <fgimenez> Chipaca, they was using /usr/bin/snapd instead of the compiled one
[11:21] <Chipaca> lel
[11:23] <fgimenez> Chipaca, also, we were checking for a 405 method not allowed response in unhandled verbs
[11:23] <Chipaca> that is correct
[11:23] <Chipaca> but now you'd get a 401 before that
[11:23] <fgimenez> Chipaca, yes, we need to change that in the test
[11:23] <Chipaca> you'd still want to check for the 405 once you're sending in credentials
[11:23] <fgimenez> Chipaca, ah, ok, then that's ok
[12:17] <Chipaca> ogra_: you around perchance?
[12:17] <ogra_> no, not perchance ...
[12:17] <ogra_> ... just regular
[12:18] <Chipaca> :)
[12:18] <ogra_> :)
[12:18] <Chipaca> ogra_: so, REST API now needs creds to do stuff
[12:18] <ogra_> whee
[12:18] <Chipaca> ogra_: including things like, um, setting up creds
[12:18] <ogra_> lol
[12:18] <Chipaca> (nothing of this is landed yet ;)
[12:19] <ogra_> so i guess we should have some snappy config way to set this to a sane default (i.e. if --developer-mode enable ubuntu/ubuntu)
[12:19] <Chipaca> that, and/or "snappy passwd"
[12:20] <ogra_> ah, thats new ?
[12:20] <Chipaca> that's non-existent
[12:20] <Chipaca> that's what i'm asking :)
[12:20] <ogra_> can we also enforce updating of the  pw ?
[12:20] <Chipaca> ogra_: you mean, pw age policy?
[12:21] <ogra_> so that we could ship with a default on the images but enforce the update on first login via the REST api ?
[12:21] <ogra_> yeah, something like the pw age policy
[12:21] <ogra_> but if i dont have ssh enabled i need to be able to get in once to set a new one
[12:22] <Chipaca> that's a good point, we probably want that
[12:22] <Chipaca> but it's a chunk of work :)
[12:22] <ogra_> yeah, i guess
[12:23] <Chipaca> and not sure of the details of it
[12:24] <Chipaca> ogra_: snappy config such that the oem can set default pw was what i was thinking, with it defaulting to ubuntu/ubuntu if in dev mode
[12:24] <Chipaca> ogra_: and i didn't know if we'd also need a snapp passwd thing
[12:24] <Chipaca> ogra_: password aging, and password policy in general, wasn't in what i'd been thinking of doing
[12:24] <ogra_> well, we dont use --developer-mode on the official images we offer
[12:24] <ogra_> only --enable-ssh
[12:25] <Chipaca> so the cmd is a must
[12:26] <Chipaca> with a nice-to-have of accepting config (just to set passwd in core) if no passwd set
[12:26] <ogra_> also do we have a way to have passwords hidden in the snappy config output yet ?
[12:27] <ogra_> so only *** is shown
[12:27] <Chipaca> ogra_: i was thinking of doing it for coreconfig
[12:27] <ogra_> yeah
[12:28] <ogra_> though with a fixed lenght string so the actual PW lenght isnt guessable
[12:28] <Chipaca> ogra_: was thinking of just replacing the value in the yaml with "***pasword***" or some such placeholder text, on the way out
[12:28] <ogra_> yeah
[12:28] <Chipaca> ogra_: which is something you could do with bip too :)
[12:28] <ogra_> just to indicate there is one set
[12:28] <Chipaca> (was it bip?)
[12:29] <ogra_> yeah
[12:29] <ogra_> the package is called ircproxy :)
[12:29] <ogra_> but it uses bip
[12:30] <Chipaca> ogra_: another way would be to use a special yaml thing for passwords
[12:30] <Chipaca> i could dig into that if it'd be useful
[12:31] <ogra_> we should ask jdstrand for input here
[12:31] <ogra_> after all thats a security thing :)
[13:28] <Chipaca> ogra_: echo "config: {ubuntu-core: {password: password}}" | snappy config ubuntu-core -- -
[13:28] <Chipaca> \o/
[13:29] <ogra_> :)
[13:30] <clobrano> Hi Chipaca, any news from security guys for Bug #1496319? :)
[13:30] <Chipaca> clobrano: no
[13:30] <Chipaca> clobrano: but i hear they're backlogged atm
[13:31] <ogra_> and most of them are in the US....
[13:31] <ogra_> where nobody works today... celebrating that guy who got lost
[13:33] <clobrano> :D
[14:03] <jdstrand> Chipaca: we are we needed for 1496319?
[14:11] <tbr> did anyone look into snappy images for scaleway yet?
[14:17] <jdstrand> beuno: fyi, I tried to accept docker in the review: OOPS ID: OOPS-3587e98ff8044c0db2885414f81ffd46
[14:17] <jdstrand> kickinz1: ^
[14:18] <jdstrand> beuno: I don't know how to proceed and am afraid to try to approve again
[14:18] <jdstrand> beuno: it is ok to accept (kickinz1 will fix 'architectures' for next time and the security policy changes are ok)
[14:19] <jdstrand> it appears to have been accepted
[14:20] <jdstrand> (based on the website)
[14:31] <beuno> jdstrand, I accepted it as well
[14:31] <beuno> maybe we fought over accepting it
[14:31] <beuno> jdstrand, I'll look into it, thanks
[14:43] <jdstrand> maybe
[14:51] <tedg> ogra_: That's Monday actually, US is in today :-)
[14:51] <tedg> (well I imagine some people took vacation)
[14:57] <ogra_> tedg, oh, not today ?
[14:57] <ogra_> damn, mixed that up
[14:58] <ogra_> tbr, i dont think anyone has started on that
[14:58] <tbr> k
[14:58] <tbr> it's interesting because it's cloud, but it's ARMv7
[14:58] <ogra_> yeah
[15:22] <Chipaca> fgimenez: any idea why umount would pin a cpu at 100% at the start of adt-run?
[15:23] <Chipaca> 32223 root       20   0 25392  1688  1512 R   1 100.  0.0  8:52.81 umount /tmp/diskimage185973715/system
[15:23] <Chipaca> like so ^
[15:24] <fgimenez> Chipaca, nope atm, how do you run it?
[15:24] <Chipaca> fgimenez: GOPATH=~/canonical/snappy ./run-checks
[15:26] <fgimenez> Chipaca, never saw that before, from which branch are you running it?
[15:27] <Chipaca> fgimenez: my auth thing
[15:28] <fgimenez> Chipaca, didn't try run-checks, go run _integration-tests/main.go goes fine here, i'll check run-checks
[15:28] <Chipaca> it's u-d-f hanging somehow
[15:28] <Chipaca> sergiusens: you seen that?
[15:29] <sergiusens> Chipaca, fgimenez if u-d-f was rebuilt, maybe check all the FDs are closed
[15:29] <sergiusens> lsof
[15:29] <sergiusens> it shouldn't cause a spin of the cpu
[15:31] <Chipaca> oh
[15:31] <Chipaca> no space left on device
[15:31] <Chipaca> that might cause it
[15:31] <elopio> fgimenez: could we use a link to the icon, instead of copying it into every snap?
[15:31] <elopio> does that work? I'll give it a try.
[15:33] <fgimenez> elopio, it would be very useful, let me know how it goes
[15:41] <elopio> fgimenez: I did this service test before I realized I wanted to copy your local snaps style.
[15:41] <elopio> I regret that because now every other branch depends on it.
[15:41] <elopio> are you ok if I land it, and then make another branch to move the helloDBus tests to examples, and add a local snap instead?
[15:43] <fgimenez> elopio, sure, np
[15:44] <Chipaca> fgimenez: rebooted because my /tmp got into a mess, and now i get past the unmounting, but am still at the "ssh connection failed" bit
[15:44] <Chipaca> i've never gotten past this stage
[15:44] <Chipaca> how do i get it past this stage?
[15:46] <fgimenez> Chipaca, which version of autopkgtest are you using?
[15:46] <Chipaca> fgimenez: 3.17.3
[15:47] <fgimenez> Chipaca, same here, what if you execute go run _integration-tests/main.go -release 15.04 ?
[15:47] <elopio> Chipaca: did your udf fail? I get this every other time: https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1496484
[15:48] <Chipaca> elopio: when it failed, i aborted, cleared loop0p5, and redid
[15:49] <Chipaca> fgimenez: doing that now
[15:49] <elopio> tedg: how do I make a snappy lxc?
[15:53] <Chipaca> fgimenez: getting the same “adt-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds...”
[15:53] <Chipaca> fgimenez: except more than 3 seconds pass between each one
[15:53] <Chipaca> and the qemu is doing *something*
[15:57] <fgimenez> Chipaca, you should be able to access the image with kvm -m 512 -redir :8022::22 /tmp/snappy-test/image/snappy-rolling-edge-latest.img
[15:57] <fgimenez> Chipaca, does it boot ok?
[15:58] <Chipaca> well, 15.04 not rolling because you just told me to -release 15.04 :)
[15:58]  * Chipaca tries it
[15:58] <fgimenez> Chipaca, yes, sorry :)
[15:59] <Chipaca> it's not booting
[16:00] <fgimenez> Chipaca, maybe udf doesn't create it properly
[16:01] <ogra_> is that 204 ?
[16:01] <ogra_> (that is exactly what i wanted to have tested)
[16:01] <ogra_> could be the grub changes, but these only landed in 204
[16:03] <Chipaca> this is 15.04
[16:03] <Chipaca> not sure the revno
[16:03] <Chipaca> redoing from the start
[16:03] <ogra_> u-d-f should have printed it
[16:04] <fgimenez> ogra_, 15.04 204 is working fine here
[16:04] <ogra_> phew !
[16:04]  * ogra_ hugs fgimenez
[16:04] <ogra_> thanks !
[16:05] <ogra_> that saves my weekend :)
[16:05] <fgimenez> ogra_, yw :)
[16:06]  * Chipaca continues to work to ruin ogra_'s weekend
[16:06] <ogra_> haha
[16:06]  * Chipaca likes the feeling of power
[16:06] <ogra_> my heating breaking down already is ahead of you
[16:06]  * ogra_ hopes it is only the oil filter being dirty and not the pump
[16:07] <Chipaca> oil filter? do you use a diesel engine to power the pump?
[16:07] <ogra_> yeah, but its a clean VW one
[16:07] <ogra_> :P
[16:08] <davmor2> ogra_: damn you beat me to it :)
[16:08] <ogra_> (i think 60-70% of german heatings still burn oil)
[16:08] <Chipaca> fgimenez: retried with rolling, still no luck with the tests, but the image boots
[16:08] <ogra_> its a central heating but a oli furnace
[16:08] <ogra_> ... that powers it
[16:09] <Chipaca> fgimenez: and i can ssh in and all
[16:09] <davmor2> ogra_: yes you and america are the reason the cost of diesel rockets in the winter
[16:09] <ogra_> i dont really need the heating, it is warm enough still, but it also does warm water
[16:09] <Chipaca> ogra_: leaves more russian gas for the uk \o/
[16:09] <ogra_> lol
[16:09] <ogra_> i wish we had gas in my street ...
[16:10] <ogra_> but like cable the neighborhood wasnt willing to pay for it
[16:11] <ogra_> (tow streets down they have gas and 200MBit cable)
[16:11] <fgimenez> Chipaca, what if, with the image booted with kvm, you run go run _integration-tests/main.go -ip <IP_ADDRESS> -port 8022 ?
[16:12] <Chipaca> STUFF IS HAPPENING!!!!1!!!one!
[16:12] <ogra_> yay
[16:12] <fgimenez> Chipaca, \o/
[16:14] <fgimenez> this bypass the image creation and booting part, anyway something is wrong, that should be done by the runner
[16:22] <tedg> stgraber: I thought there was a snappy image for LXD, but I can't seem to find it. Am I remembering wrong or just suck at Google? :-)
[16:23] <ogra_> tedg, there is an lxd snap in the store
[16:24] <tedg> ogra_: Yeah, looking the other way around
[16:26] <Chipaca> fgimenez: ohhh...
[16:26] <Chipaca> fgimenez: after a number of reboots and stuff, this:
[16:26] <Chipaca> Rebooting...
[16:26] <Chipaca> bash: line 1:  1087 Killed                  bash -ec './_integration-tests/reboot-wrapper integration.test' 2> >(tee -a /tmp/adt-run.rEvouJ/command1-stderr >&2) > >(tee -a /tmp/adt-run.rEvouJ/command1-stdout)
[16:26] <Chipaca> fgimenez: and now it's stuck waiting for ssh again
[16:26] <Chipaca> (i can log into the system just fine)
[16:26] <Chipaca> ah! but no ipv4 address!
[16:28]  * Chipaca runs dhclient by hand
[16:28] <fgimenez> Chipaca, you found it after all! i thought i was mistaken :) it must be the same think that elopio reported for bbb
[16:35] <fgimenez> leaving, nice weekend everyone o/
[16:54] <Chipaca> ogra_: elopio: have either of you ever seen a package decide it's sideloaded on update?
[17:19] <elopio> Chipaca: nop.
[17:20] <elopio> Chipaca: oh, I forgot. I did this because it was hard to find the test that was failing for you a couple of weeks ago
[17:20] <elopio> https://code.launchpad.net/~elopio/snappy/results_on_error/+merge/273013
[17:21] <longsleep> What is the best approach to add snapcraft plugins, adding an example how to use it?
[17:21] <elopio> not sure if there's a better way to do it. Can you review please?
[17:21] <sergiusens> tedg, until recently there was no snappy image for lxd due to all the security architecture around it
[17:22] <sergiusens> recently though, apparamor gained the possibility of profiles within profiles which was one of the blockers
[17:22]  * sergiusens knows he is using the terminology all wrong
[17:26] <jdstrand> wait, what?
[17:26] <jdstrand> I'm confused by the 'all wrong terminology'
[17:27] <jdstrand> oh, snappy in lxd?
[17:27] <jdstrand> right, so, apparmor doesn't yet have namespace stacking support
[17:28] <jdstrand> which means that the host and the guest can't have unmodified profiles
[17:29] <jdstrand> so it makes running snappy in a container harder than you'd want (should be able to if you disable apparmor for lxd on the host)
[17:29] <jdstrand> the namespace stacking work has not landed yet, but it is coming. we are targeting 16.04
[17:37] <tedg> Ah, okay, so elopio I was wrong about that ^
[17:38] <tedg> Apparently we can't do the tests in LXD yet.
[18:17] <ogra_> Chipaca, never
[18:31] <sergiusens> longsleep, I don't follow, or if I do, just add a small project in the examples directory; to make sure it doesn't break even add a smaller project in integration_tests
[18:55] <ogra_> beuno, you are being missed in a certain "-external" channel
[19:45] <jdstrand> ogra_: fyi, I filed those three snappy bugs we talked about (nameservers, ntp and rsyslog)
[21:25] <sergiusens> jdstrand, I think a little bird told me you were going to get the reviewer tools updated in ppa:snappy-dev/tools for vivid and trusty, is that correct?
[21:25] <jdstrand> yes
[21:26] <jdstrand> but I need to first update them for the things we agreed to :)
[21:26] <jdstrand> I've started that
[22:16] <jdstrand> sergiusens: ok, fix committed to trunk. the store will pick it up next week
[22:16] <jdstrand> sergiusens: I have one other thing to add then I'll push to the ppa
[22:16] <jdstrand> that will happen next week
[22:17] <jdstrand> sergiusens: unless it is critical that you have it in the ppa sooner. let me know and I'll push what I have
[22:20] <sergiusens> jdstrand, it's fine; just noticed an MP where snappy build re enabled the review tools so didn't want have havoc when the tools ppa got updated
[22:24] <jdstrand> sergiusens: right, don't push that yet. feel free to add me as a reviewer
[22:25] <jdstrand> sergiusens: the one thing that is left is actually so that can be turned on
[22:28] <sergiusens> jdstrand, I noticed it landed while I was out; but it hasn't made it to the general population yet ;)
[23:08] <jdstrand> sergiusens: ok, I uploaded review tools 0.34 to the tools-proposed ppa
[23:09]  * jdstrand -> weekend