[03:00] <xevious> I'm trying to build an Ubuntu 16.04 live ISO with live-build and when I boot it, it says "/casper/vmlinuz: file not found". I checked and that file doesn't exist, but there is vmlinuz-4.4.0-59. Is there something I'm missing to make live-build either copy/link to vmlinuz or write out the bootloader configuration to point to the versioned file name?
[03:01] <xevious> The same thing happened with a completely default build (`lb config && lb build` in an empty directory), which turned out to be 12.04.
[03:02] <xevious> Also, the same error occurred when I changed the PROJECT to ubuntu-base.
[03:02] <xevious> I followed this post: http://swem.logdown.com/posts/763254
[09:16] <davmor2> dmj_s76: No but I'll have a word with cyphermox and the desktopers today about it.
[11:02] <davmor2> cyphermox: ubiquity isn't starting the installer session on the daily image it is starting desktop instead :(
[13:37] <cyphermox> davmor2: ok I'll have a look
[18:14] <xevious> cjwatson: I remember you said this isn't your focus any more, but do you have any tips about the issue I'm having with live-build not correctly naming the kernel and initramfs files compared to the isolinux configuration? (It's last thing I said in the channel about 15 hours ago.) Or, is there someone else with more current experience with all this I should talk to?
[18:27] <cjwatson> afraid I don't.  cyphermox might know
[18:39] <xevious> Thanks.
[18:41] <xevious> cyphermox: If you have a moment, could you read over the problem that I described about 15 hours ago?
[19:00] <cyphermox> I don't know, I suppose it should more or less work, but the process for building CDs isn't just live-build, it also involves debian-cd and other code; maybe there's something missing from there.
[19:17] <xevious> cyphermox: Is the process used to make the official Ubuntu ISOs documented somewhere I can look it over?
[19:30] <dmj_s76> xevious: cyphermox may have better information, but this actually came up in conversation with one of the elementary guys yesterday.  They collected a lot of this info into a document a while back...
[19:30] <dmj_s76> xevious: https://docs.google.com/document/d/1RPPF14h1Sw2gQjGTuZjUIlNHnGrafS8ekhFjJM9MT00/edit
[19:31] <xevious> dmj_s76: That's a great write up. Thanks for the link.
[19:32] <dmj_s76> glad to help :)
[19:32] <cyphermox> we're way past that point though
[19:35] <dmj_s76> well, like I said, might not quite the right thing
[19:36] <dmj_s76> cyphermox: What is actually handling the top panel bar/indicators during install/oem-firstboot?
[19:37] <cyphermox> ubiquity
[19:41] <cyphermox> fixing the top panel on HiDPI is my next task, followed by probably trying to run a live-build to see what's up... it's a little late today to start something very complicated.
[19:41] <dmj_s76> okay, thanks!
[19:42] <dmj_s76> That will be a major improvement for us!
[19:42] <cyphermox> if you have an idea what to do about it, though, feel free to hack at it
[19:42] <cyphermox> I have an idea how to fix it, but no clue if it's doable.
[19:42] <dmj_s76> was just starting to look at it, but don't really have a firm idea yet and need lunch now, so hack away!
[19:44] <cyphermox> ahah, it's going to be easy to fix
[19:44] <cyphermox> let's see
[19:45] <cyphermox> well, it's not going the fix the oversize, but at least it will fix that unsightly doubling easily.
[19:47] <xevious> cyphermox: On an Ubuntu 16.04 system, should running `lb config && lb build` produce a bootable default image of some sort? Or, are more steps needed?
[19:48] <cyphermox> you need to specify what release you want, otherwise it might blow up because it can't find whatever release that defaults to
[19:48] <cyphermox> possibly other things -- I rarely run that at all
[19:48] <xevious> It defaults to precise.
[19:49] <cyphermox> usually I try to wing it, pass the release first, then try to see what's missing from how far I'd get
[19:49] <cyphermox> (because when I run this I usually also need to run something special to hack at it)
[19:49] <cyphermox> so my guess is what you mentioned earlier, the release and flavor, would be sufficient to make it work
[19:50] <cyphermox> flavor = PROJECT
[19:50] <cyphermox> you can also look at lp:ubuntu-cdimage, some of the important variables are set there.
[20:00] <xevious> cyphermox: Here's my current build script, if you're curious: http://sprunge.us/fAUL
[20:01] <xevious> It seems to install a capser-oriented isolinux config even if I choose a non-casper based PROJECT.
[20:02] <xevious> The kernel copying is to account for the paths that the isolinux config expects.
[20:02] <xevious> Forcing gzip is because of this: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1555980
[20:11] <cyphermox> the copying appears to be (at quick glance) to be what you want, since that's done by debian-cd later
[20:12] <xevious> There's an issue in there, since the glob matches both vmlinuz files, cp wants the destination to be a directory.
[20:13] <xevious> dmj_s76: The document referenced as "Community effort to document it" at the end of that write-up doesn't exist any more. Any idea where that went? https://docs.google.com/document/d/1c350g2o7ytnM_sloSprJnkTuUrSocAD4QwUsXYj1GYk/edit
[20:18] <xevious> cyphermox: Does debian-cd copy or move the files?
[20:23] <cyphermox> move, afaict
[20:31] <cyphermox> sorry, I don't know what's wrong
[20:31] <cyphermox> maybe try to set INITRAMFS to "live-boot" instead of "casper" ?
[20:31] <cyphermox> but it seems to me like there's some other setting missing
[20:35] <cyphermox> xevious: try this: lb config noauto --mode ubuntu --distribution zesty --bootstrap-keyring ubuntu-keyring --binary-images none --memtest none --source false --build-with-chroot false --parent-archive-areas main --apt-source-archives false --linux-flavours none --initsystem none --bootloader none --initramfs-compression lzma --linux-packages=none --initramfs=none
[20:35] <cyphermox> then lb build, see how far that gets you
[20:36] <xevious> Kicking it off now.
[20:37] <xevious> Do you mind if I do xenial instead of zesty?
[20:37] <cyphermox> no, should be the same thing
[20:38] <cyphermox> that's just because of where I got the info; basically, from https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/zesty/ubuntu-server/+build/87550; which I got from http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-server/zesty/
[20:44] <xevious> I sure wish I had an all NVMe system to do these builds on.
[20:48] <xevious> cyphermox: I'm still waiting for my last build to finish before I start the one you asked me to try.
[20:49] <xevious> I'm trying to change as few things as possible, so I'm still doing the whole ubuntu project which is, of course, the largest possible one.
[20:50] <xevious> My plan of action is: 1) get it to boot, 2) switch to a project that's got a minimal package set, 3) if casper's still around, figure out how to eliminate it
[20:50] <xevious> Once I've done all that, I can actually start working on what I need to do. :)
[21:16] <cyphermox> well, ubuntu isn't the largest tbh
[21:16] <cyphermox> and I think you should from the start figure out why casper is there, because that changes things completely, the image isn't built the same in that case
[21:22] <xevious> Ok. I'll do that.
[21:22] <xevious> Also, your build completed.
[21:23] <xevious> As per the config options, no binary image was created.
[21:26] <xevious> So, my latest build boots and appears to work fine: Firefox started and can access the Internet.
[21:26] <xevious> That's with this build script: http://sprunge.us/FIaX
[21:27] <xevious> I'll look into eliminating casper now, since obviously my kernel moving script references casper-related paths.
[21:29] <cyphermox> wait, wat?
[21:30] <cyphermox> do you want server or do you want firefox?
[21:30] <xevious> I want a super-minimal environment eventually. That was just how I tested the image that was built with that script.
[21:31] <xevious> I'd like to create as minimal an environment as possible that'll run a single full-screen application.
[21:31] <cyphermox> also, of course a binary was built with the command I gave you, you have exactly what ubuntu-server returns for the official builds, or at least as close as you're likely to get
[21:31] <cyphermox> also, casper is actually useful if what you want is to start graphics, it will get you to the live session correctly.
[21:32] <dmj_s76> cyphermox: Is the a11y icon making it oversized or the other way around?
[21:33] <cyphermox> dmj_s76: I think the accessiblity icon is just bigger in that case because there is more room to use.
[21:33] <cyphermox> dmj_s76: I uploaded a build of ubiquity to my ppa a few mintues ago
[21:34] <xevious> cyphermox: I'm going to address your first point first: I didn't get an ISO from your command. Should I have? The `lb config` included `--binary-images none`. Here's the directory's contents after running `lb build`: http://sprunge.us/VdTR
[21:34] <cyphermox> dmj_s76: https://launchpad.net/%7Ecyphermox/+archive/ubuntu/installer-dev/+sourcepub/7398093/+listing-archive-extra
[21:34] <cyphermox> xevious: you should only have had a boot directory with a filesystem squashfs and kernel/initramfs
[21:35] <cyphermox> xevious: server doesn't do casper, and only uses that and a d-i in the initramfs.
[21:35] <xevious> I see.
[21:35] <xevious> Ah, yes I do have the squashfs there.
[21:37] <xevious> No kernel/initramfs
[21:37] <xevious> Should they be in binary? http://sprunge.us/KCbb
[21:38] <xevious> Or is that due to `--linux-flavours none` being passed to `lb config`?
[21:38] <xevious> Or `--linux-packages=none`?
[21:40] <cyphermox> my mistake, just the squashfs
[21:41] <cyphermox> you know, there are tools in the archive which allow you to remaster an existing image, it would probably be easier to use that than trying to replicate the full processes we use from scratch
[21:46] <xevious> I need something that I can automate, is as minimal as possible, and only runs a single application full-screen. Is there something that can accomplish that that's easier than adding a couple package lists to a live-build configuration?
[21:47] <xevious> Or, rather, a package list referencing several packages.
[21:49] <cyphermox> doesn't seem to me like what you're doing is that much easier. The real question seems to me to be, are you really going to be running it that often than the time spent figuring it out to automate it outweights the effort of tweaking a prebuilt image once in a while?
[21:49] <cyphermox> but ymmv
[21:50] <xevious> Yes. Automated dailies + additional manual runs.
[21:50] <cyphermox> in any case, if you want to rip out casper you'll need new scripts to start up graphics in the livefs, so it might not be a good plan to remove it if you don't absolutely need to
[21:50] <xevious> Yeah it sounds like I should leave casper and just focus on changing what X runs.
[21:51] <cyphermox> doing that is trivial
[21:51] <xevious> I have something that boots to X. Now I just need to minimize it.
[21:51] <cyphermox> start with a minimal image like lubuntu or xubuntu, then you can use a hook (look in the hook directory) to put in the right file to autostart the app you want
[21:52] <cyphermox> (and install the app, of course)
[21:55] <xevious> The goal is to eliminate the existing desktop environment and replace it with X + matchbox-window-manager + my full-screen application.
[22:20] <dmj_s76> cyphermox: Is that ppa package working for you?
[22:20] <dmj_s76> oem-firstboot fails here after installing the ppa, but maybe that's all the netcfg changes?
[22:21] <cyphermox> could be
[22:22] <cyphermox> that package actually needs to be injected in the image in an... unusual way, anway
[22:22] <cyphermox> oh
[22:22] <cyphermox> I see what you did there.
[22:22] <cyphermox> you'd need to look at logs in /var/log/installer to tell.
[22:23] <cyphermox> dmj_s76: it
[22:23] <cyphermox> *it's entirely possible I messed up the change, I was trying to both change the fill method for the panel and fix up its size.
[22:27] <dmj_s76> in /var/log/installer/dm, there's a traceback regarding /usr/bin/ubiquity-dm
[22:29] <dmj_s76> I'm going to see if this regresses compared to zesty.
[22:30] <dmj_s76> Might also try the fix against xenial if zesty is just broken atm
[22:30] <cyphermox> can you share the traceback?
[22:31] <cyphermox> I built this for zesty
[22:38] <cyphermox> looks good here, if you ignore how broken the rest of the installer is
[22:39] <cyphermox> (also, why oh why)
[22:39] <cyphermox> and I
[22:39] <cyphermox> am not on HiDPI, so maybe it's all wrong there.
[22:40] <cyphermox> dmj_s76: given how painful this is to run, I'll remaster the zesty iso now, and I'll make it available here: http://people.canonical.com/~mtrudel/
[22:41] <cyphermox> hum, actually, perhaps I should remaster a yakkety iso instead, to not be caught in the other issues
[22:42] <dmj_s76> http://paste.ubuntu.com/23794768/
[22:42] <dmj_s76> I suspect weird zesty X images
[22:42] <dmj_s76> *issues
[22:43] <cyphermox> ah, that would be startup, yeah
[22:44] <cyphermox> now I know what to exxpect to be up against next week.
[22:48] <dmj_s76> So it fails there in the regular zesty image.
[22:50] <cyphermox> not sure what you mean by that?
[22:50] <cyphermox> I'm rebuilding the squashfs right now for a yakkety image.
[22:50] <cyphermox> it should be all ready in 2 minutes
[22:53] <cyphermox> ... burning to a USB
[22:53] <dmj_s76> I get that same error when running oem-firstboot from a zesty image without installing the package from your ppa
[22:54] <dmj_s76> sweet
[22:58] <cyphermox> well, that's going to take a while to upload.
[23:44] <xevious> cyphermox: "# The scripts require that you work in /build" I've seen this in several places. That doesn't seem like it's true, since I'm building in /mnt/live-build and have created a bootable .iso image. http://swem.logdown.com/posts/763254
[23:44] <xevious> Also, here: https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305/comments/768010