[05:06] <aarcane> I'm trying to do a modified install for an ubuntu based distro that uses ubiquity and doesn't provide an "alternate" disk.
[05:07] <aarcane> I've got a custom, alternate root filesystem not supported by the installer and not backed by a traiditional block device, so I have to set up my / partition and just get ubiquity to install to that.  it should do everything except configure grub and fstab..
[05:07] <aarcane> but I don't know how to tell ubiquity where / is mounted, or where to mount /, and I don't know how to tell it to skip disk management steps.
[10:52] <cjwatson> xnox: You changed usb-creator's binaries back to Architecture: all - are you sure that was the right thing to do?  I deliberately changed them all to "Architecture: amd64 i386" a while back to avoid unsatisfied-dependency noise because they depend on syslinux.
[10:54] <xnox> cjwatson: hmm... pre-mature on having a dd backend & nexus7 backend neither of which will require syslinux.
[10:54] <xnox> cjwatson: where do you see this "unsatisfied-dependency noise" ?
[10:55] <cjwatson> http://people.canonical.com/~ubuntu-archive/testing/raring_probs.html
[10:55] <cjwatson> (All the other problems there are being addressed)
[10:56] <xnox> cjwatson: ack. Ok, I will fix my mess.
[10:56] <cjwatson> Thanks
[10:56] <xnox> thanks for the link.
[10:56] <cjwatson> It'll need manual cleanup after your upload, since the partial-NBS binaries won't go away by themselves
[10:56] <cjwatson> But I'll be able to take care of that
[10:59] <infinity> xnox: It should never be arch:all, if the deps will be different per arch.
[11:00] <infinity> xnox: Since syntax like "Depends: syslinux [amd64], foo-arm-thing [amrhf]" only works on arch:any (or Arch: armhf amd64 etc) binaries.
[11:01] <xnox> infinity: How about Suggests: syslinux ?
[11:01] <infinity> That would be incorrect, if it depends on it. :P
[11:01] <xnox> (assuming it gains a dd backend)
[11:02] <infinity> If the syslinux backend ends up being a less-frequently-used option, it might be alright as a recommends.  But it's always annoying when a menu option just fails to function, too.
[11:06] <xnox> true.
[12:58] <ogra-cb> hmpf
[12:58] <ogra-cb> i'd love to know why orca comes up by default on nexus7 installs
[13:01] <xnox> ogra-cb: ubiquity.
[13:01] <xnox> ?!
[13:01] <ogra-cb> well, i didnt enable anything
[13:02] <ogra-cb> theer is a default enabling of a11y and oboard for the final install though
[13:02] <ogra-cb> so the first one likely makes a11y being on in oem-config, but i dont get why ii get orca instead of onboard
[13:27] <xnox> it appears that we disable background at the accessibility setting v1 (lesser visual impairment support) but not at v2/3 (moderate & blind).
[13:27]  * xnox will fix to disable background at all visual impairment settings, if that is ok.
[13:29] <cjwatson> Yes, I think that's a simple oversight.
[13:30] <xnox> cjwatson: also, compiz has a background picture command line arg, so I'll experiment using compiz for background picture drawing instead of our own "desktop background picture frame" app
[13:32] <ogra-cb> oh, we dont use gnome-settings-daemon for the wallpaper drawing ?
[13:32] <xnox> nope =)
[13:32]  * ogra-cb sees it being started in ubiquity-dm
[13:32] <ogra-cb> we could just use it in cases where g-s-d is running anyway
[13:33] <xnox> ogra-cb: is g-s-d actually drawing the background picture, or does it just store the setting for nautilus/gnome-shell/compiz to draw the background picture?
[13:33] <ogra-cb> hmm, i wonder if its time to finally switch preinstalled images to use the oem user instaed of root
[13:34] <xnox> ogra-cb: well, I am working on supporting compiz, such that we can experiment with unseeding metacity from nexus7 images.
[13:34] <ogra-cb> the install leaves quite some hidden dir cruft in /root
[13:34] <cjwatson> xnox: Sure, as long as it's only when compiz can be used
[13:34] <xnox> cjwatson: ack.
[13:35] <xnox> cjwatson: i'm adding as the last elseif, so existing priorities of WM are not changed.
[13:35] <ogra-cb> xnox, i think its g-s-d itself through one of its plugins, ask seb128 for more details :)
[13:35] <xnox> ogra-cb: interesting.
[14:59] <xnox> compiz support is in - need to fix bugs now =)
[14:59]  * xnox \0/
[15:00]  * ogra-cb hugs xnox 
[15:16] <aarcane> is it possible to bypass the disk configuration step in the ubiquity installer yet ?
[15:17] <xnox> aarcane: sure, just move partman.py plugin out of the way. but then you are expected to get /target setup and ready as the  target install's "root"
[15:18] <xnox> aarcane: or see reuse/replace recepies on reusing pre-partitioned disks.
[15:18] <xnox> aarcane: Can you explain what are you trying to do to skip disk configuration step?
[15:19] <xnox> aarcane: there is oem-config which does user setup only & can be run from pre-partitioned/live-build devices like ac100 & nexus7 for example.
[15:19] <xnox> we call those images "pre-installed" e.g. we ship the tarball + instructions on how to put that on target machine & on first boot oem-config asks to setup the user only.
[15:19] <xnox> (all of this has been available since a long time now)
[15:20] <aarcane> I'm installing on zfs from a ubuntu derivative.
[15:20] <xnox> aarcane: we have zfs support in ubuntu livecd already.
[15:20] <xnox> aarcane: in the installer
[15:21] <xnox> in ubiquity.
[15:21] <aarcane> xnox, this is based on 12.04, I believe.
[15:21] <xnox> aarcane: yes in 12.04.
[15:22] <xnox> aarcane: just preseed default filesystem as zfs instead of ext4
[15:22] <aarcane> the zfsonlinux people don't know this...  they're still relying on the debootstrap method
[15:22] <xnox> aarcane: share the news?!
[15:22] <cjwatson> Uh - partman-zfs is only supported on kFreeBSD
[15:23] <cjwatson> If preseeding the default filesystem to zfs works, it's by accident
[15:23] <aarcane> on a related note, I'm not finding partman.py.  where is it located?
[15:23] <xnox> aarcane: right, so you need to make sure you have working partman-zfs package in the live environment & related zfs tools are available.
[15:24] <xnox> then it should all work, or maybe changes will be required to ubi-partman.py
[15:24] <cjwatson> partman-zfs isn't even in raring any more
[15:24] <xnox> =(
[15:24] <cjwatson> (Because it wasn't built on any Ubuntu architecture)
[15:25] <aarcane> cjwatson, I'm going to say maybe you should build in the zfs support, since the only missing step is running a few commands from the console, namely apt-add-repository ppa:zfs-native/stable and aptitude install ubuntu-zfs, then zfs support is present.
[15:26] <cjwatson> Then somebody needs to fix partman-zfs in Debian to support non-BSD systems
[15:26] <cjwatson> It's not something I'm personally going to do ...
[15:26] <cjwatson> (And really, if those tools are good enough they should be in Debian/Ubuntu directly, not require a PPA)
[15:26] <aarcane> cjwatson, it's a licensing issue.
[15:27] <aarcane> besides, zfs support SHOULD be all based on standardized CLI commands, and should just work regardless of architecture.
[15:27] <aarcane> if the zfs and zpool commands are present, it should work.
[15:27] <cjwatson> Well, even so, we can't build it in unless the underlying partman-zfs package is something other than "Architecture: kfreebsd-any"
[15:27] <aarcane> anyway, I'm going to miss my bus if I don't go get ready now.
[15:28] <xnox> aarcane: sure, make sure you have the partman-zfs, that's the package that verifies that "zfs" is avalable and "gives green" light to the installer to uze zfs.
[20:10] <pmatulis> is kickseed support any more advanced than what i can infer from this: https://help.ubuntu.com/community/KickstartCompatibility
[20:11] <pmatulis> cjwatson? ⤴
[21:01] <cjwatson> pmatulis: There've been a few improvements - the installation guide on help.ubuntu.com is canonical on this.  It's mostly in maintenance mode though.