[09:25] <stochastic> persia, are you around?
[09:27] <persia> I am
[09:45] <stochastic> sorry I didn't keep my window focused persia, but I was meaning to talk with you about the duties of release management
[09:51] <persia> Oh, sure.
[09:51] <persia> I'm not an expert, but I can certainly give you some pointers.
[09:54] <persia> Sorry.  Hunting URLs.
[09:54] <stochastic> well I'm new to the idea of a release manager's position to be honest, so you're suggestion that we need one is something I'd like to hear more about
[09:54] <persia> So, release management consists of making sure that a given flavour is suited for release.
[09:54] <persia> https://wiki.ubuntu.com/ReleaseProcess talks about the final release process
[09:55] <persia> https://wiki.ubuntu.com/MilestoneProcess talks about steps along the way
[09:55] <persia> (The next milestone is Thursday)
[09:56] <persia> The duties I was thinking about in the meeting are as follows:
[09:57] <persia> 1) Track the status of the image builds (daily and milestone) and make sure that images are a) being built, and b) roughly correct in content
[09:58] <persia> 2) idle in #ubuntu-release and take responsibility for completing or delegating any actions that belong to ubuntustudio
[09:59] <persia> 3) Ensure that there is sufficient testing on the ISO tracker for each milestone release and that any discovered release-critical bugs are escalated appropriately.  This can be done directly, by leading a testing team, or by delegating to a testing team leader.
[09:59] <persia> 4) Attend weekly release meetings, raise any issues of particular importance to ubuntustudio, and mention progress on ubuntustudio goals.
[10:00] <persia> Related to 4) is escalating anything that needs studio developer attention
[10:00] <persia> 5) Making sure the release notes are being generated and will be useful at release time
[10:01] <stochastic> This sounds like more dedication than I'm willing to commit to of my volunteer time to be quite frank.  I can help with some of it, but not all.
[10:01] <persia> Note that all of this is limited in that it's only tracking.
[10:01] <persia> It's the team lead that's supposed to be driving stuff, with the release manager only making sure it's being done and reporting when it's not.
[10:02] <persia> I understand entirely.
[10:02] <persia> I think we'd benefit from having someone who did all of that, but right now I don't think any of it is being done.
[10:02] <persia> Taking over some of the role would likely be of benefit, and I suspect if you took all of it, you could delegate some chunks to others.
[10:03] <persia> For instance, I know ScottL was working on release notes.
[10:03] <stochastic> Isn't #1 being done by the daily health check e-mails?
[10:03] <stochastic> #3 I can likely be on top of
[10:04] <stochastic> #2 I can certainly help with, but I may miss some stuff.
[10:04] <stochastic> #4 is a bit too much dedication.  I likely won't be able to meet every week.
[10:05]  * stochastic checks fridge to see when their meetings are
[10:05] <persia> For #1, someone has to read them and complain when there's an issue.
[10:06] <persia> Even partial coverage of #2 would be a benefit
[10:06] <persia> I can understand #4: perhaps you could delegate to someone?  I can't always stay awake to make those meetings.  I don't know others' schedules.
[10:06] <stochastic> #4 I can only catch the first half hour of the meetings before I need to leave for work every week.
[10:07] <persia> Yeah, and we'd end up at the very end, so that doesn't work.
[10:07] <persia> ScottL: What's your time like on Fridays?
[10:07] <stochastic> he's sleeping right now
[10:11] <persia> Right, but he'll catch it when he wakes.  He's good about reading backscroll.
[10:11] <persia> I think he's the most westerly of us though, which makes him a good candidate for the meeting, since he seems to be able to IRC at work.
[10:13] <stochastic> I am more westerly than he is (Vancouver), but I work at 5pm here and the meeting starts at 4pm.
[10:13] <stochastic> maybe ScottL and I can work together to delegate these duties.
[10:15] <stochastic> persia, were there any other points that needed to be tackled?
[10:18] <persia> There's more to do, but if someone just starts coordinating those 5 points, it's a massive improvement in our chances of having a good release.
[10:18] <persia> And I think a lot of the rest of the stuff really properly belongs to testers and developers.
[10:19] <persia> While there's aspects of release management involved, it mostly comes down to making sure the testers and developers are feeling some pain if the work isn't getting done.
[10:21] <stochastic> a big problem facing Ubuntu Studio is the fact that the testers, developers and release managers are kind of all the same limited group of people
[10:22] <persia> Indeed :)
[10:22] <persia> And by separating the roles we don't all end up duplicating the same work, and hopefully more can get done.
[12:02] <ScottL> persia, stochastic:  i'd have to check the time for the #ubuntu-release meeting (I'll do that at work, I'll be there in thirty minutes)
[12:02] <ScottL> it might be on a knife's edge, if it's 4pm for stochastic it might be right before I leave from work and that might be hard to do
[12:03] <persia> It's something like 3-5 hours from now, except on Fridays.
[12:03] <ScottL> persia, oh, well that puts it more or less right in the middle of my day which should be fine ;)
[12:04] <ScottL> stochastic, and whatever you need me to do (re: delegate duties or whatever really) I will try my best to help
[12:04]  * ScottL off to work
[12:04] <persia> ScottL: It tends to last 60-90 minutes, but check the fridge
[12:04] <persia> (and you'd only be skimming most of it)
[12:05] <ScottL> abogani: Family = my wife and kids (I tend to get up early and they tend not to) - I say this because you asked something about it yesterday morning
[12:09] <abogani> ScottL: How many kids?
[13:18] <ScottL_> the #ubuntu-release meeting is 10am local time, so that shouldn't be a problem me thinks
[13:25] <ScottL_> although I wish the fridge and google calendar had better intergration with UCT/GMT to local time :/
[17:56]  * ckontros is trying out some new Kubuntu
[17:58]  * jussi01 bites ckontros
[18:36]  * ScottL_ laughs
[18:37] <ScottL_> jussi01: any word on a renamed / dedicated Ubuntu Studio forum within Ubuntu Forums?
[18:38] <jussi01> ScottL_: I havent even asked. My apologies, Ill get onto it tonight (been crazy with work and thesis)
[18:39] <ScottL_> jussi01: don't rush, get to it when you can
[18:40] <ScottL_> I'll just keep it in the back of my mind so it doesn't get forgotten
[19:01] <jussi01> ScottL_: I just had a conversation with jdong and sent an email to the FC with you copied in.
[19:01] <jussi01> ScottL_: we should be sorted.
[19:15] <ScottL_> jussi01: super sweet!  thanks
[20:12] <abogani> jussi01: Jussi are you around?
[22:42]  * stochastic bonks his head with the realization that the #ubuntu-release meetings that persia and ScottL were talking about are actually at 4pm GMT not local time, so they're at 8am for myself (a bit before I usually wake up)
[22:44] <persia> UTC actually, so that when BST is in place the time doesn't change everywhere else


[00:03] <jsjgruber> The config file has been moved from Jono's web site to ubuntu-owl.org/lernid/ubuntu.lernid . I think these are the same right now, so there should be nothing to look at right now.
[00:03] <jsjgruber> Does anyone have anything they see that's odd or they want to ask about?
[00:08] <jsjgruber> That's about it. The other thing I'll mention is that after we have Lernid sound and stable I'd like to draw others to the project. There have been a number of people drawn to the project who have asked to join, and some who have proposed merges. A couple of merges did take place, but I'd like to welcome both experienced hands (Lernid is written in Python) and newcomers to help out with advancing Lernid. If you have any ideas, or ca
[00:08] <jsjgruber> n help your self or help draw people please drop me an e-mail. My address is on the Lernid description page at http://launchpad.net/lernid
[00:08] <jsjgruber> Thanks for following along and for helping me test Lernid.
[00:08] <jsjgruber> Anything else Nathan or Jono?
[00:08] <nhandler> Nope, I'm good
[00:09] <nhandler> Thanks a lot for all of your work on lernid jsjgruber
[00:09] <jsjgruber> My pleasure.
[00:15] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2011/06/06/%23ubuntu-classroom.html
[01:13] <crazedpsyc> jsjgruber: Could you (or somebody) set the useragent to 'Lernid/0.8.x' instead of Safari?
[01:15] <jsjgruber> crazedpsyc,  I could look into it if you wouldn't mind filing a bug report so I won't forget
[01:16] <crazedpsyc> jsjgruber: Sure, i'll do that in a minute :)
[01:17] <jsjgruber> crazedpsyc, thank you very much, and thanks for helping us test.
[01:21] <crazedpsyc> glad I could help :)
[03:24] <jsjgruber> http://www.ubuntu.com is a test url


[12:16] <awafaa> rsalveti: ping me know when you're up, please
[12:28] <hrw> awafaa: your appearance at james bond theme evening was awesome
[13:19] <infinity> awafaa: Stop hitting on my coworkers.
[13:21] <awafaa> hrw: thanks, people complained there was too much hair and not enough heels, but it was a good laugh
[13:21] <awafaa> infinity: jealous are we? you didnt seem to mind on wednesday ;)
[13:23] <infinity> awafaa: I knew you'd come back to me, then.    This isn't improving.
[15:56] <awafaa> infinity: it's the natural progression of things ;)
[19:55] <applepi> Hello all...  working on an ubuntu-arm rootfs made with debootstrap and I'm able to boot into it, however everything I try to run inside it, I get 'illegal instruction'
[19:56] <applepi> I'm not sure why, I targeted armel, and when I did this with debootstrap to make a debian rootfs, it seems to work fine...
[20:34] <infinity> applepi: If it's not an armv7 CPU, it won't work.
[20:34] <infinity> applepi: Debian/armel is armv4t, Ubuntu/armel is armv7, which is likely your issue.
[20:34] <infinity> (And Ubuntu/armel is also a dead product now, we stopped shipping it)
[20:35] <applepi> infinity: Really?  Because my kernel is built for armv7..  and oddly it's my Debian build that works.
[20:36] <applepi> infinity: however that's good to know.
[20:40] <infinity> applepi: What CPU/board are you running on?
[20:41] <applepi> imx6sl
[20:41] <applepi> dev board
[22:13] <applepi> infinity: well..  I tried with armhf..  didn't even make it through booting.  :/  the sd card reader for some reason seems to be failing during bootup..
[22:14] <applepi> I'm seeing 'mmc0: no vqmmc regulator found' and then a ton of 'init: Failed to create pty - disabling logging for job', 'mountall: event failed'
[22:14] <applepi> Any suggestions?
[22:16] <infinity> applepi: None off the top of my head, though I have a sabrelite here that I need to find the time to fix up for trusty.
[22:16] <infinity> So, it might magically start working soon. :P
[22:42] <Valduare> wonder if we will ever see small arm computers with mini pcie slots for ssd instead of nand storage
[23:04] <infinity> Valduare: Yup.
[23:05] <Valduare> I have an mk808 right now that i've been playing with
[23:06] <Valduare> dual core, 1.6 gig   8 gigs of nand and 1 gig of ddr3 ram
[23:06] <Valduare> pretty snappy little device


[00:09] <sergiusens> slangasek: seb128 sudo ubuntu-device-flash personal rolling --channel edge --output img.img
[00:35] <slangasek> sergiusens: ok
[00:36] <Odd_Bloke> Is there a specific place that we should look for/put snappy logs?
[07:04] <fgimenez> good morning
[07:08] <dholbach> good morning
[07:25] <seb128> good morning snappy world
[07:31] <ogra_> *snap* *snap*
[07:41] <seb128> slangasek, did you figure out more about that grub issue?
[09:05] <JamesTait> Good morning all; happy Let It Go Day! 😃
[09:05] <ogra_> pfft ... go ...
[09:32] <sergiusens> morning
[09:50] <Chipaca> sergiusens: mo'in
[09:50] <Chipaca> sergiusens: fighting some kind of a bug (in my self, not my code)
[09:50] <ogra_> same here ... and a tooth issue ...
[09:50]  * Chipaca <- blah
[09:50] <Chipaca> blahrgh*
[09:51] <Chipaca> ogra_: ow :(
[09:51]  * ogra_ will take the rest of the day off ...
[09:51] <ogra_> hoping it fixes itself, else i'll have to see a dentist tomorrow
[09:51] <Chipaca> >this< close to doing same, but i'll soldier on for a bit more
[09:51] <Chipaca> ogra_: take care
[09:51] <ogra_> you too
[09:51] <Chipaca> i hate toothaches :(
[09:52] <ogra_> well, the painkillers at least give me a fuzzy warm feeling
[09:52] <ogra_> i just cant concentrate on serious stuff :(
[09:52]  * ogra_ is full of ibuprofen
[09:52] <Chipaca> ogra_: time for tea and netflix \o/
[09:53] <ogra_> heh
[09:53] <sergiusens> ogra_: heh, I went to the dentist last evening
[09:53] <ogra_> no netflix for me ... but perhaps a bit TV ...
[09:53] <sergiusens> Chipaca: did you try bug spray?
[09:53] <ogra_> (netflix on a 2M line isnt really working)
[09:53] <sergiusens> Chipaca: I hear Nopol is quite good :P
[09:53] <Chipaca> sergiusens: :)
[09:54] <sergiusens> ogra_: popcorn time ;-)
[09:54] <Chipaca> sergiusens: testosterone keeps the nits away, for now
[09:54] <ogra_> not with my bad tooth !
[09:54] <ogra_> :P
[09:54] <sergiusens> ogra_: although many things are illegal in germany http://thenextweb.com/media/2015/06/22/spanked-by-old-fashioned-laws/
[09:54]  * sergiusens meant the popcorn time app ;-)
[09:54] <ogra_> lol
[09:55] <ogra_> at least you are allowed to still read them when you like ... though who knows when that changes
[09:57] <sergiusens> ogra_: right, but that means you will need some sort of big brother system to enforce that for the good of knowing you aren't reading anything improper :-P
[09:57] <ogra_> we'll just ask the NSA for that info
[14:05] <elopio> good morning.
[14:06] <fgimenez> hey elopio
[14:08] <elopio> fgimenez: https://plus.google.com/hangouts/_/canonical.com/ubuntu-qa?authuser=0
[14:09] <davmor2> elopio: you need to lose the ubuntu-qa from dude seriously ;)
[14:23] <elopio> davmor2: everybody is invited.
[14:30] <seb128> sergiusens, hey, any idea when you are going to do a goget-ubuntu-touch update in wily? (to include the personal code)
[14:43] <balloons> elopio, did you pin Monday as "the" date for open house?
[14:44] <sergiusens> seb128: let me do that now
[14:44] <seb128> sergiusens, thanks
[14:46] <elopio> balloons: I'm asking about that. Either monday or tuesday.
[14:47] <sergiusens> elopio: we are doing a new release on Monday?
[14:47] <elopio> sergiusens: rsalveti said next week. If we want to release next week, we need an RC early on the week.
[14:47] <sergiusens> elopio: with what fixes? :-P
[14:48] <elopio> sergiusens: we have a small changelog indeed :) That makes it easier. I think what we want is to get a release cadence, even if the version has not changed much.
[14:49] <balloons> elopio, will you know by the end of today which date it is? So we can plan to meet tomorrow
[14:49] <balloons> ?
[14:50] <elopio> balloons: I hope so, but I think rsalveti is busy with sprint meetings. Lets meet tomorrow, and talk about a plan b in case we don't have an answer.
[14:50] <elopio> maybe we can do the first open house from rolling edge.
[14:51] <elopio> then we won't need an RC, and it's still a good experiment.
[14:52] <rsalveti> elopio: I should be able to provide an answer soon
[14:52] <rsalveti> the most tomorrow
[14:52] <sergiusens> rsalveti: does that involve our conversation as well?
[14:52] <rsalveti> sergiusens: yes
[14:53] <slangasek> seb128: no more progress to report yet
[14:53] <sergiusens> rsalveti: great, I will hold off on that until then ;-)
[14:53] <seb128> slangasek, hey, k, let me know if I can help
[14:53] <rsalveti> sergiusens: sure :-)
[14:54] <seb128> slangasek, I copied the grubx64.efi from my laptop and use configfile /efi/ubuntu/grub/grub.cfg on the grub prompt and then I can boot the image, so I'm unblocked for local testing at least
[14:55] <elopio> rsalveti: thanks.
[15:12] <cyphermox> seb128: hey, I want to look at your booting issue... in grub, could you please run 'echo $cmdpath', then 'echo $root' ?
[15:17] <balloons> elopio, ack. I'll get it scheduled
[15:18] <elopio> balloons: if possible, for 14:00 UTC so fgimenez can join us.
[15:21] <balloons> ck
[15:23] <fgimenez> sergiusens, are bugs enabled for goget-ubuntu-touch? https://bugs.launchpad.net/goget-ubuntu-touch
[15:26] <Chipaca> fgimenez: https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch
[15:27] <fgimenez> Chipaca, ok thx :)
[15:28] <seb128> cyphermox, hey, I'm going to need to restore the buggy files and reboot, can that wait a bit? I'm debugging some other issue on the booted stick atm ... but you can build an image yourself for debugging as well if you want ;-)
[15:28] <cyphermox> that's already what I'm doing :)
[15:29] <seb128> k
[15:29] <cyphermox> do I need something special?
[15:30] <cyphermox> a different version of ubuntu-device-flash?
[15:30] <seb128> yes, trunk
[15:30] <seb128> cyphermox, then use the first line from http://irclogs.ubuntu.com/2015/06/23/%23snappy.html
[15:38] <skay> I've followed https://developer.ubuntu.com/en/snappy/start/ for the beagle bone black but after waiting > 2 minutes the ssh step doesn't work
[15:38] <skay> should I be holding down a button when inserting the SD card and powering the device?
[15:40] <seb128> cyphermox, let me know if you manage to get an image with the issue
[15:41] <cyphermox> almost done building the image
[15:42] <cyphermox> I'm building a potential fix too, so I'll be ready to test that as soon as I get an image that reproduces the bug
[15:43] <cyphermox> seb128: have you filed a bug about this? or do you know if someone else has?
[15:45] <seb128> cyphermox, no I didn't, but I'm happy to if you tell me against what
[15:46] <skay> zyga: hey, you successfully got snappy on your bbb, do you have notes on that?
[15:46] <cyphermox> seb128: so, now if I want to run the image I assume I can do so in qemu?
[15:47] <seb128> cyphermox, qemu or a machine with a non uefi boot
[15:47] <seb128> like good legacy bios :p
[15:47] <cyphermox> right
[15:47] <cyphermox> well, this bug is uefi specific
[15:49] <seb128> right
[15:52] <cyphermox> yup, it fails
[15:53] <plars> skay: I have it on my bbb, what's the problem?
[15:53] <plars> skay: oh, just ssh? It's up otherwise? Did you use --enable-ssh?
[15:53] <skay> plars: I have sadly few details for you
[15:54] <skay> plars: I can't tell if it's up, since I can't ssh in to it and didn't have a monitor handy
[15:54] <skay> plars: I did not --enable-ssh
[15:55] <plars> skay: you'll want to do that when you build your image
[15:55] <skay> plars: ah, I used the image listed on the start page, I figured I'd follow that
[15:55] <seb128> cyphermox, let me know if you figure out what the issue is ;-)
[15:55] <plars> skay: also, if you don't have a monitor (or even if you do) I highly recommend using a usb-ttl cable so you can get serial console
[15:55] <plars> skay: ah, yeah... always roll your own image :)
[15:56] <cyphermox> seb128: the issue is some old code in grub to help find the right device for removable install media
[15:56] <skay> plars: oh yeah! I saw someone using a usb-ttl cable when searching around for blog posts about it
[15:56] <cyphermox> ie. when you boot the CD in EFI
[15:56] <skay> plars: I want one
[15:56] <plars> skay: amazon, they are really cheap if you don't have one already
[15:56] <skay> plars: if it's better to roll our own images, then someone should update the start page
[15:58] <skay> plars: I'll try again after building my own image. plus, we have many monitors at the hackerspace and I'll hook one up too
[15:58] <plars> skay: that's my personal opinion if you are going to be doing the kinds of things we want to do, but it's not the quickest/simplest path assuming you have a tv or monitor to hook it up to, and a keyboard to get things going
[15:59] <plars> skay: don't forget you'll need a microhdmi-hdmi cable
[16:00] <plars> skay: something like http://www.amazon.com/Amzer-Micro-HDMI-Speed-Cable/dp/B003OBZSHC
[16:49] <cyphermox>  sergiusens: is there a minimal memory to run a snappy personal image? I can't seem to start it properly in qemu
[16:56] <seb128> cyphermox, what's the issue? you need to pick the "ubuntu" line in the grub menu
[16:56] <seb128> the snappy system-a one just loops reboot
[16:56] <cyphermox> right, that's what I'm seeing, the kernel loads, panics, reboot
[16:57] <seb128> cyphermox, try to pick the ubuntu line
[16:57] <seb128> unsure where the system-a entry is coming from
[16:58] <cyphermox> grub didn't stop to ask me, but I can play with it some more
[16:58] <seb128> help debugging that/cleaning it out would be welcome as well ;-)
[16:58] <cyphermox> I'm still wiating for my grub build to finish
[16:59] <cyphermox> once grub plays nice, we can debug that
[16:59] <cyphermox> at least now I know it's not my stuff that is wrong
[16:59] <cyphermox> (I mean, my qemu settings)
[16:59] <sergiusens> seb128: fwiw, Chipaca and me just revamped most of the grub code to have a very minimal grub.cfg
[17:00] <seb128> sergiusens, I hope personal still boots with it ;-)
[17:00] <cyphermox> sergiusens: is grub.cfg still in /efi/boot/grub.cfg?
[17:01] <sergiusens> seb128: https://code.launchpad.net/~sergiusens/snappy-hub/grubcfg/+merge/262701
[17:01] <sergiusens> cyphermox: yes
[17:01] <cyphermox> alright
[17:01] <sergiusens> default and timeout need fixing there though
[17:01] <sergiusens> but I hope you get the gist of it
[17:02] <seb128> sergiusens, is efi/secure boot going to keep working with that?
[17:02] <cyphermox> sergiusens: does it really have to be at that location? why not /boot/grub? I'm just curious, as in /boot/grub things would mostly work immediately, whereas /efi/boot will need a special case.
[17:03] <sergiusens> cyphermox: I don't know, it's all slangasek's work that led to this
[17:04] <sergiusens> cyphermox: this being grub.cfg in .../efi/...
[17:06] <cyphermox> heh
[17:06] <sergiusens> seb128: I think so, but I have no system to prove it
[17:07] <seb128> sergiusens, I can test those changes if that helps, just not today (in the middle of trying to debug unity8 in a booted session on my key)
[17:08] <sergiusens> seb128: testing this involves building from 7 branches so I wouldn't advise on testing today ;-)
[17:08] <seb128> lol, k
[17:08] <ogra_> sergiusens, do we build the BBB images without --developer-mode ?
[17:08] <seb128> then when those land in trunk
[17:08] <seb128> let me know before doing a release
[17:08] <ogra_> (the conversaition between skay and plars kind of suggest that)
[17:08] <sergiusens> seb128: sure, for now, I'm releasing those snappy personal things
[17:08] <ogra_> *suggests
[17:09] <sergiusens> ogra_: yes, no developer mode by default, why?
[17:09] <ogra_> ah, k
[17:09] <ogra_> sergiusens, the start page doesnt mention that ... or that he should manually build the image to have ssh
[17:10]  * ogra_ makes a note to look over the docs once he is back in business
[17:10] <sergiusens> ogra_: ssh is disabled by default like on all images; it has been subject of controversy
[17:10] <ogra_> not on the rpi :)
[17:10] <plars> I assumed that was by design to keep the getting started page as simple as possible for now, I typically just build my own, but it might not hurt to have a mention that things like ssh will not be enabled if you use the default image
[17:11] <sergiusens> and mentioned in some of the welcome pages, albeit only the cloud ones; whereas it's common to have ssh disabled by default on any ubuntu install
[17:11] <plars> with, perhaps, a link to getting into more detail
[17:11] <ogra_> yeah, probably a sub-page we can link to
[17:11] <plars> it wasn't obvious to her earlier when she was trying to get it working
[17:11] <sergiusens> it is expected for images to not have ssh enabled though
[17:11] <plars> and I suspect a lot of people have this problem of no easy way to attach otherwise
[17:12] <ogra_> plars, yes, thats what got my attention reading the backlog
[17:12] <sergiusens> secure by default mantra and all that
[17:12] <sergiusens> with an 'ubuntu' password ;-)
[17:12] <ogra_> sergiusens, thats fine, but we need to hint people how to get it enabled :)
[17:12] <ogra_> haha, yeah
[17:16] <cyphermox> sergiusens: how can I rebuild the image if I want to use a different gcdx64.efi?
[17:19] <ogra_> cyphermox, you rebuild the oem snap
[17:20] <ogra_> cyphermox, (now dont ask me how you get your hands on the oem snap for amd64 :P )
[17:21] <ogra_> cyphermox, what i do for the RPi: dpkg-deb -x pi2_0.14_all.snap unpack; cd unpack; fiddle ... fiddle ... fiddle; cd ..; snappy build unpack
[17:21] <cyphermox> ugh
[17:22] <ogra_> once you have your new oem snap you can just use it with ubuntu-device-flash to build a new image
[17:22] <sergiusens> cyphermox: isn't that defined by the grub-install from the rootfs?
[17:22] <sergiusens> ogra_: it could be oem snap related, but we don't do the magic I wish we did as for u-boot (copy files and be done with it)
[17:22] <ogra_> oh, ok
[17:23]  * ogra_ didnt know there are still differences
[17:23] <sergiusens> we magically depend on what grub-install decides for us so the outcome can vary from build to build
[17:23] <ogra_> oh man
[17:23] <sergiusens> ogra_: I got rid of most
[17:23] <sergiusens> ogra_: next is to add all these random files to bootassets :-)
[17:23] <sergiusens> and we get a nicely contained system
[17:23] <ogra_> lovely
[17:30] <cyphermox> sergiusens: I can't update files if I can't boot the system to a working shell
[17:30] <cyphermox> sergiusens: so far all I ever get is no grub menu, and booting a kernel that panics
[17:31] <cyphermox> but I do have http://ppa.launchpad.net/mathieu-tl/installer-dev/ubuntu/dists/wily/main/uefi/grub2-amd64/2.02~beta2-25ubuntu2~mtrudel1/ with files that can then be signed :)
[17:38] <seb128> sergiusens, why do we install openssh-server to disable it by a file in /etc?
[17:39] <seb128> btw I didn't look at core, but personal is lacking a /etc/default/locale
[17:39] <seb128> not sure what should create that
[17:43] <seb128> hum
[17:43] <seb128> upstart --session doesn't like snappy much
[17:43] <seb128> if that a known issue?
[17:44] <seb128> the upstart bridge jobs and other things seem to behave weirdly, not start as they should
[18:05] <zyga> skay: yes, I have
[18:05] <zyga> skay: it's rather straightforward, just copy the image, what kind of issues did you see?
[18:05] <zyga> skay: and most important, do you have a serial cable?
[18:45] <skay> zyga: hey, plars suggested building my own image. I was just following the instructions on the site, using hte vanilla image
[18:45] <skay> zyga: I'll update back here if I run in to a problem. I'll prob try it tonight
[19:02] <sergiusens> seb128: for cloud-init
[19:03] <sergiusens> seb128: grep for ssh here https://developer.ubuntu.com/en/snappy/start/#snappy-azure
[19:04] <sergiusens> cyphermox: you can manually put stuff there, just map the image, mount, put, run
[19:05] <sergiusens> chroot or what not
[19:07] <sergiusens> elopio: any luck with adt on trusty btw?
[19:09] <elopio> sergiusens: no sir. I forgot about that, sorry.
[19:09] <elopio> I'm making a note in my todo to do it after lunch/gym.
[19:09] <sergiusens> elopio: thanks!
[19:12] <cyphermox> sergiusens: ok
[19:13] <cyphermox> map the image?
[19:21] <cyphermox> nvm, got it
[19:31] <sergiusens> cyphermox: kpartx
[19:31] <cyphermox> sergiusens: heh, I used losetup, but I got it already, I'm testing my fix
[20:06] <slangasek> cyphermox: "why not /boot/grub" for the record, there is also a grub.cfg in /boot/grub, and if the grubcdx64.efi was capable of finding it on its own it would've done so :)
[20:32] <cyphermox> slangasek: I understand, I'm trying to see if I can't make that work for you
[20:34] <cyphermox> the answer seems likely to be fixing up the patch I sent to grub-devel so they're happy with it
[20:38] <plars> ogra_: https://code.launchpad.net/~zyga/snappy-hub/fix-1464275/+merge/261833 still hasn't been merged?
[20:39] <plars> or did lp just miss it somehow?
[20:43] <sergiusens> plars: there is no automerging for that and it would need to go throught the store as well
[20:43] <sergiusens> -t
[20:43] <plars> sergiusens: so who needs to do that?