[18:14] <teward> call out to QAs for other flavors rolling alternate installers: can you replicate https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1559507 ?
[18:14] <teward> confirmed this happens on Lubuntu alt and Serve
[18:14] <teward> Server*
[18:14] <teward> via the dailies
[18:15] <teward> any chance Beta can be delayed?
[18:15] <teward> slightly?  at least until we peek at this (not having keyboard select sounds like a big missing thing)
[18:16] <flocculant> why delay?
[18:17] <teward> flocculant: that was wrong channel
[18:17] <flocculant> if there's an issue should get fixed for those affected - or they have the option to not release
[18:17] <teward> sorry
[18:17]  * teward yawns
[18:17] <teward> flocculant: the issue prevents many of our test cases from completing
[18:17] <flocculant> not ours :)
[18:18] <teward> server normal is step 8,9 to select keyboard layout
[18:18] <teward> lubuntu-alt step 4 is the same
[18:19] <flocculant> read about that bug somewhere
[18:21] <teward> I know phillw found it on the 19th's dailies
[18:22] <flocculant> doubt if it was there - don't look at other flavours dailies
[18:22] <flocculant> not seeing it in my bug mail either
[18:22] <flocculant> *shrug*
[18:49] <j^2> hi!
[18:50] <j^2> I have a question, I work for Chef software (which used to be Opscode), and I’ve been tasked with getting ‘apt-get install chef’ to work with our most up-to-date releases. Is there someone I can talk to about this?
[18:53] <gQuigs> j^2: in 16.04 or just generally?
[18:53] <j^2> i think our main goal when we started this conversation a few months ago was 16.04, but generally would be good too. We had some conversations but it seems it fell through the cracks
[18:55] <j^2> i think both companies would love the idea of apt-get install chef giving the correct thing would make everyone happy
[18:56] <j^2> if i understand the process correctly, we should aim for the “partner” repository?
[18:56] <j^2> that or the universe?
[18:59] <dobey> partner
[19:00] <j^2> yeah
[19:00] <j^2> that seems reasonable for the time being
[19:00] <dobey> i'm not 100% sure on who you need to talk to for that though
[19:00] <j^2> yeah apt-get install -y chef installs 11.8
[19:00] <j^2> that’s really really out of date :(
[19:00] <j^2> and we also have the chefdk we should seriously consider another package
[19:01] <j^2> dobey: yeah, i figured i’d come here to start, then ideally find the next person ;)
[19:01] <dobey> anything in the main ubuntu archive will have to follow much stricter requirements for being released as updates; partner is a little more relaxed though
[19:01] <j^2> and i guess we are “partners” and by default the sources.list has partner in it right?
[19:02] <dobey> i think partner has to be explicitly enabled by the user
[19:02] <j^2> not from the 14.04 box i just spun up :-/
[19:02] <j^2> https://www.irccloud.com/pastebin/zNaD9suT/
[19:03] <j^2> wait
[19:03] <j^2> did i read that wrong?
[19:03] <j^2> crap
[19:03] <dobey> i don't see partner in there
[19:03] <j^2> ah yeah it’s commented out
[19:03] <j^2> https://www.irccloud.com/pastebin/z1eh3JFl/
[19:03] <j^2> crap
[19:03] <j^2> ok, so that’s problematic
[19:03] <dobey> yeah it has to be enabled by the user
[19:03] <j^2> hmmm
[19:04] <j^2> so who/how did chef get in the universe in the first place?
[19:04] <j^2> because it is there ;)
[19:04] <dobey> someone packaged it
[19:04] <dobey> probably in debian
[19:04] <j^2> hmmm
[19:04] <dobey> 16.04 has 12.3.0
[19:04] <j^2> track it back?
[19:05] <dobey> anyway, i think you probably want to talk to people in #ubuntu-server rather than in here
[19:05] <j^2> oh nice
[19:05] <j^2> ok, so 12.3, that’s a great step forward
[19:05] <j^2> thanks, i’ll talk to #ubuntu-server
[19:08] <dobey> so when an ubuntu release happens, the archive is frozen, and updates generally are minor bug fixes or security fixes, and not major release upgrades. there are a few excpetions to that rule though, such as firefox; it might be possible to get a similar exception for chef, such that major releases could be shipped as updates, but the general stable release update process still has to be followed there