[13:06] <mgariepy> good morning everyone
[15:54] <mhall119> morning
[15:54] <mhall119> highvoltage: I've decided what I'm gonna do about xdg-launcher
[15:55] <mhall119> I'm going to fork it as qimo-launcher, then daker and I can add any extra features that wouldn't necessarily be useful for Qimo to (a renamed) xdg-launcher
[15:58] <highvoltage> ok, cool
[15:59] <highvoltage> and from my side, I build a qimo disc (if you could call it that) with debmower last week
[16:03] <mhall119> yay!
[16:03] <mhall119> highvoltage: when do you need a prototype gnome session from me?
[16:03]  * mhall119 is working on prioritizing
[16:04] <highvoltage> mhall119: whenever you're ready. friday would be good :)
[16:04] <mhall119> :P
[16:04]  * highvoltage is good with applying pressure
[16:04] <mhall119> as long as I get to pick *which* Friday
[16:04] <highvoltage> deal.
[19:14] <highvoltage> Edubuntu meeting time?
[19:14] <highvoltage> (well, was 15 minutes ago but now is just as good :) )
[19:44] <highvoltage> mhall119: I can't remember if I included any documentation with that (probably not)
[19:44] <highvoltage> mhall119: but you basically go to a directory where you want your .iso and run "debmower qimo.debmower" as root
[19:45] <mhall119> okay
[19:45] <mhall119> I'm reading the code now
[19:45] <highvoltage> (if you run debmower without adding anything it will build an ubuntu cd)
[19:45] <mhall119> ok
[19:45] <highvoltage> yep, nothing spectacular right now, this version is just taking some of the stuff from all the old scripts I had and adding it together
[19:46] <mhall119> highvoltage: is there a bzr branch for debm?
[19:46] <mhall119> lp:debmower?
[19:46] <highvoltage> yes
[19:47] <highvoltage> if you want to make changes/improvements I can add you if you want?
[19:47] <mhall119> I'll just propose my changes for merging
[19:47] <highvoltage> ok
[19:47] <mhall119> and file bugs, of course ;)
[19:48] <highvoltage> feel free :)
[19:49] <highvoltage> that builds a qimo cd on my laptop in less than 10 minutes from scratch, it should make it easier for you to move from one ubuntu release to the next
[19:49] <highvoltage> since you don't have to do much more than replace 'maverick' with 'natty' in a definition file
[19:54] <mhall119> yeah, that sure souds nice
[19:54] <mhall119> sounds
[20:08] <dinda> is there a meeting today?
[20:09] <mgariepy> dinda, there was a meeting about an hour ago
[20:09] <dinda> ack, missed it again
[20:10] <mhall119> it's good to see you anyway
[20:10] <mhall119> how are things?
[20:17] <dinda> mhall119: cold - freezing here!
[20:19] <mhall119> what are you doing these days?
[20:19] <dinda> mhall119: working with the platform team on the developer manual
[20:20] <mhall119> still working for canonical?
[20:20] <dinda> mhall119: I sent highvoltage notice that the Edubuntu marketplace was fine with Canonical, even included a disclaimer that it's all community selected
[20:20] <dinda> mhall119: yip
[20:20] <mhall119> ah, good to hear
[20:20] <dinda> mhall119: so was hoping to start getting interested companies listed in the new marketplace
[20:31] <highvoltage> dinda: I'm sure we talked about it before, but stgraber talked to claire at uds and she made other suggestions. for one, canonical will list service companies on the Canonical site and then we'll just link to there (once the pages on the Canonical site is finalised)
[20:31] <highvoltage> the edubuntu one will still be kept for people who sell edubuntu products otherwise
[20:32] <dinda> highvoltage: I'd not heard that
[20:33] <dinda> highvoltage: I wouldn't count on any canonical site getting updated quickly
[20:33] <highvoltage> dinda: and I don't :)
[20:33] <dinda> highvoltage: besides I thought you folks wanted the marketplace to list the Edubuntu only companies and folks interested in offering services
[20:34] <highvoltage> dinda: we wanted to, but we agreed to what claire proposed, so if we're going with something else than that we'd probably have to talk to her again
[20:34] <highvoltage> oops, s/claire/jane/g
[20:36] <dinda> highvoltage: that's s big mixup in peoples :)
[20:36] <stgraber> not the first time he does that :)
[20:36] <highvoltage> heh, stgraber just told me the same thing, there used to be 2 claires and 2 janes, and for some reason I mix all of them up
[20:45] <dinda> highvoltage: good thing there is only one Dinda!  ;)
[20:49] <highvoltage> dinda: heh, yeah. I'm sure I'd have gotten her name right if I was actually at UDS  this time :)
[21:03] <mhall119> highvoltage: debmower only works if all the packages are in the archives, doesn't it
[21:03] <mhall119> or in a PPA
[21:03] <mhall119> some repo
[21:03] <mhall119> where apt can find them
[21:12] <highvoltage> mhall119: indeed. you can specify ppa's or custom archives in the template though
[21:13] <highvoltage> mhall119: so, in /usr/share/doc/debmower/examples/template you'll see an example template for ubuntu and debian
[21:13] <highvoltage> mhall119: for qimo you'd probably want to copy that and make a qimo template
[21:13] <mhall119> tar: ./proc/pts: Cannot mkdir: No such file or directory
[21:13] <mhall119> tar: Exiting with failure status due to previous errors (setting nameservers) (setting /etc/apt/sources.list)
[21:13] <highvoltage> mhall119: inside those example directories you'll see a sources.list file, you could add PPA's and other repositories you'd like to use for qimo in there
[21:14] <mhall119> ok, I'll look into them
[21:14] <highvoltage> mhall119: ah yes, that happens, you can ignore that error for now (or file a bug :) )
[21:15] <mhall119> I'm also going to need to use custon syslinux files
[21:15] <mhall119> I'll add that when I get to that stage though
[21:15] <highvoltage> mhall119: that also goes into the template
[21:15] <highvoltage> I can't remember off-hand where you set the template, but I think that's in the example too :)
[21:16] <mhall119> ah, ok, so there are template and then there are configs
[21:16] <mhall119> I see
[21:16] <highvoltage> yeah, the template is for everything we don't want in debmower itself or in a config file. exactly for the kind of things you mention above
[21:17] <mhall119> ok, makes sense now
[21:17] <highvoltage> I guess the sources.list doesn't strictly have to be a seperate file, but I like it that way and I think it makes it easier for most people
[21:18] <highvoltage> mhall119: when it get's to the grub prompts, just choose nothing, and when it asks you if you're sure you don't want to install grub, then just confirm that
[21:18] <highvoltage> mhall119: that will be fixed when I can preseed that properly
[21:21] <mhall119> ok
[21:28] <mhall119> update-initramfs: Generating /boot/initrd.img-2.6.35-22-generic
[21:28] <mhall119> df: Warning: cannot read table of mounted file systems: No such file or directory
[21:28] <mhall119> cryptsetup: WARNING: could not determine root device from /etc/fstab
[21:28] <mhall119> also normal?
[21:29] <mhall119> hmmm, squashfs errors galore...
[21:29] <highvoltage> mhall119: yep, I'll hide that in the future
[21:29] <highvoltage> mhall119: stuff about xapian file indexes that changed?
[21:29] <mhall119> looks like chroot/proc wasn't unmounted before mksquashfs was called
[21:29] <highvoltage> mhall119: oops, then I need to upload a new version (sorry :p)
[21:32] <highvoltage> mhall119: ah, did you ^C it somewhere during a previous build?
[21:32] <mhall119> yeah
[21:32] <mhall119> I broke something?
[21:33] <highvoltage> mhall119: ah, what happens is that the clean-up part doesn't run, and then the old proc still stays mounted, so when it runs again, it mounts proc again, and when proc is unmounted the 1st proc is still there
[21:33] <mhall119> ok..
[21:33] <highvoltage> mhall119: what I'll do is catch that in the future so when a user presses ^C it will still do the cleanup before aborting
[21:33] <mhall119> let me clean up and run it again
[21:33] <highvoltage> I meant to warn you about that :)
[21:34]  * mhall119 is good at breaking things
[21:35] <highvoltage> I did that a few times too :)
[21:36] <mhall119> also, the qimo config has ISONAME defined before VERSION, but ISONAME contains $VERSION
[21:36]  * highvoltage adds that to the TODO file
[21:37] <mhall119> this is going to make my live at least 10% more awesome
[21:37] <mhall119> life
[21:38] <highvoltage> ok, swapped VERSION and ISONAME in upstream sample :)
[21:40] <highvoltage> I'll be happy if it works for you, I want it to eventually eliminate all its predecessors (some of them are still in use)
[21:40] <mhall119> does bzr builddeb work on lp:debmower
[21:40] <mhall119> ?
[21:41] <highvoltage> I don't know, I haven't used that yet, is there a wiki page or something for builddeb?
[21:41] <mhall119> I think it just looks for a ./debian directory
[21:42]  * highvoltage installs bzr-builddeb and checks
[21:42] <mhall119> nope, doesn't work, needs an upstream tarball
[21:42] <highvoltage> ah, ok. I'll add it to my todo fwiw
[21:42] <mhall119> the way I was told to do things was to put my app's source in one branch, without any deb stuff
[21:43] <mhall119> then make another branch with the debian file and everything
[21:43] <highvoltage> that is indeed the right way to do it
[21:43] <mhall119> then if you have a watch file, you just need to bzr branch lp:debmower-pkgbranch
[21:44] <mhall119> then bzr builddeb will find the orig.tar.gz, download it, and do everything for you
[21:44] <mhall119> so now I upload my source.tar.gz into launchpad, the watch file finds them there
[21:45] <highvoltage> how do you upload your source.tar.gz to launchpad?
[21:46] <mhall119> create a new release
[21:46] <mhall119> you can upload a file to attach to that release
[21:46] <highvoltage> I thought so, I just don't see an option for that in LP
[21:46] <highvoltage> do I need to define milestones first or something?
[21:46] <mhall119> https://launchpad.net/xdg-launcher/+download
[21:47] <mhall119> yeah
[21:47] <mhall119> define a milestone, release the milestone, upload the file for that milestone
[21:47] <highvoltage> ok
[21:48] <mhall119> it's be nice it it where more tightly tied to bzr
[21:49] <highvoltage> yeah, I've never done upstream stuff in LP before, thanks for the tips :)
[21:50] <mhall119> no problem
[21:50] <mhall119> glad I can repay some of the tips you've given me
[21:52] <mhall119> question
[21:52] <mhall119> line 135 of debmower
[21:52] <mhall119>     REMOVE='ubiquity casper user-setup discover1 xresprobe libdebian-installer4 os-prober'
[21:52] <mhall119> any reason that's not $LIVECD?
[21:52] <highvoltage> yes
[21:52] <mhall119> it doesn't seem like it would work for SYSTEM="debian"
[21:52] <highvoltage> I missed that while removing some hardcoded stuff :)
[21:52] <highvoltage> sounds like that should indeed be $LIVECD
[21:53] <mhall119> ok, just making sure I understand what all it's doing
[21:53] <highvoltage> good :)
[21:53] <mhall119> is there a reason for specifying the blocksize on mksquashfs?
[21:54] <mhall119> I've done it in the past to try and get the smallest image possible, but I just guessed
[21:54] <highvoltage> yes, merely to have it tunable, on very slow systems a smaller block size is better performance wise
[21:54] <mhall119> ok
[21:54] <highvoltage> larger blocks = smaller image but slower
[21:55] <highvoltage> smaller blocks = larger image but faster
[21:55] <mhall119> to a degree
[21:55] <mhall119> woot! ISO created, and only 553 MB!
[21:55] <highvoltage> on a geode machine I once had to support it shaved 20 minutes off the installation installing a 2.4GB image
[21:55] <mhall119> wow
[21:56] <mhall119> that's a lot
[21:56] <highvoltage> so setting the blocksize for that client is important
[21:56] <mhall119> okay, this rocks, thanks highvoltage
[21:56]  * mhall119 will be up all night now
[21:56] <highvoltage> cool, now to test if it works :)
[21:57] <highvoltage> you just have to choose qimo from gdm, but as you say, a qimo-desktop package can fix that :)
[21:58] <mhall119> yeah, I just have to make it
[21:58] <mhall119> I'll test the iso once I get home
[21:58] <mhall119> it's 5pm :)
[21:59] <highvoltage> yup
[22:07] <highvoltage> mhall119: making a release tarball also at least encourages me not to make it a native package :)
[23:22] <dgroos> I'm trying to install Smartboard software into the 32 bit chroot and can't start.
[23:23] <dgroos> the software is called: SMART Notebook Software With Drivers 10.package
[23:24] <dgroos> I know how to use apt-get install and dpkg -i commands but neither work with this .package
[23:24] <highvoltage> I'm not familiar with it, but what happens when you log in to the thin client and try to start it?
[23:24] <highvoltage> (as in, in the chroot from a vt on the thin client)
[23:24] <highvoltage> and does it have any logs?
[23:25] <dgroos> I can't even get that far...
[23:25] <dgroos> It just says something like can't find package.
[23:25] <dgroos> let me see...
[23:26] <dgroos> I try this command:
[23:26] <dgroos> sudo chroot /opt/ltsp/i386 dpkg -i  '/home/dgroos/Desktop/SMART Notebook Software With Drivers 10/SMART Notebook Software With Drivers 10.package'
[23:27] <dgroos> and get this: http://pastebin.ubuntu.com/553397/
[23:27] <dgroos> Thanks highvoltage for giving it a look.
[23:27] <dgroos> I think I don't know the command to install .package files.
[23:33] <dgroos> alas...
[23:33] <dgroos> gotta go.
[23:34] <dgroos> maybe tomorrow.