[01:08] <corevette> will UME bill available for the nokia products? (770, n800, etc?
[01:20] <amitk> corevette: https://wiki.ubuntu.com/MobileAndEmbedded/FAQ
[04:19] <corevette> http://en.wikipedia.org/wiki/Ubuntu_Mobile_and_Embedded_Edition ?
[04:23] <mypapit> ?
[06:45] <dholbach> good morning
[13:01] <amitk> lool: Does PPA show a "published" status before it starts building?
[13:02] <amitk> Because I didn't see those log files yesterday
[13:11] <lool> amitk: It should, yes; I think everybody in the team received the failed build logs
[13:12] <lool> amitk: At least StevenK and I did
[13:12] <amitk> lool: I haven't received the logs
[13:13] <lool> amitk: I don't see why I have received them then
[13:13] <Mithrandir> or rather the failed build notification.
[13:14] <Mithrandir> with an URL to the logs
[13:14] <lool> Yes
[13:14] <lool> amitk: I see the linux upload published at https://edge.launchpad.net/~ubuntu-mobile/+archive
[13:14] <lool> It even built for lpia, which is what we're targetting :)
[13:14] <lool> It only failed for amd64 and i386
[13:15] <Mithrandir> you want https://edge.launchpad.net/~ubuntu-mobile/+archive/+builds
[13:15] <Mithrandir> (view build records)
[13:19] <amitk> Mithrandir: So I have to keep polling that page? I don't get email?
[13:20] <amitk> lool: Yes, I noticed the lpia .deb this morning. But last night, the status was "published" and the only files available were orig.tar.gz, diff.gz and the .dsc file.
[13:21] <Mithrandir> amitk: unsure.  I got a "this build failed" email.
[13:21] <Mithrandir> amitk: hm, are you in ubuntu-dev or ubuntu-core-dev?
[13:21] <lool> amitk: Yes, the source was published
[13:22] <amitk> Mithrandir: I am not core dev...... yet :)
[13:22] <lool> Me neither, but I got the mail
[13:22] <Mithrandir> amitk: are you in -dev?
[13:23] <amitk> Mithrandir: nevermind... I am blind. It is sitting in my spam folder.
[13:23] <Mithrandir> heh
[13:40]  * Mithrandir builds the first hardy UME build
[14:02] <lool> Mithrandir: FYI I'm also building against hardy, but I'm running into tons of unrelated issues with MIC
[14:02] <lool> It has a lot of duplication and useless hardcoding of gutsy all around the place
[14:03] <Mithrandir> somehow, I'm not surprised.
[14:03] <lool> I don't even know why they had to override the gutsy debootstrap script
[14:03] <Mithrandir> uh, they don't?  They use it if the distro doesn't provide its own, iirc?
[14:03] <lool> Mithrandir: No, the path is incorrect in MIC
[14:04] <lool> They check for /usr/lib/debootstrap instead of /usr/share, so their script is always used...
[14:04] <lool> It was probably true for an older debootstrap
[14:04] <Mithrandir> at least up and until gutsy, the scripts lived in /usr/lib
[14:05] <lool> Ok, then it's not the case for hardy
[14:05] <lool>   * Change /usr/lib/debootstrap to /usr/share/debootstrap. Closes: #430615.
[14:05] <lool> In the last upload of deboostrap to Debian synced to Ubuntu
[14:06] <Mithrandir> just make sure to fix it in the hardy m-i-c, then
[14:06] <lool> I am; it's part of the unrelated issues I'm mentionning
[14:06] <lool> But if you grep for /usr/lib/debootstrap, you'll see it in no less than 3 places
[14:07] <Mithrandir> somehow, I'm not surprised.
[14:09] <lool> Mithrandir: If you're running tip, there was a known breakage at image creation time which was fixed overnight; make sure to pull if you want to generate actual images
[14:09] <Mithrandir> I refuse to run anything but what's in the archive, except for pure testing purposes.
[14:09] <lool> k, you should be fine then
[14:32] <lool> I'm pretty sure there are some target / buildroot mistakes in MIC grah
[14:49] <lool> Arglg, MIC wasn't calling dh_pysupport with its private module dir, so you could end up with old .pyc files around
[15:02] <lool> Ah Err http://ppa.launchpad.net hardy/main Packages 404 Not Found
[15:02] <StevenK> lool: Probably because nothing has been uploaded to it that targets Hardy
[15:02] <lool> Anybody mind if I upload a dummy hildon-desktop with the same source as in hardy but a lower version number?
[15:03] <lool> StevenK: Yes, quite certainly; and I have nothing to upload in particular!
[15:03] <StevenK> I could upload hildon-input-method-framework, but the package is a pile of crap
[15:03] <StevenK> (but I should probably sleep)
[15:04] <lool> We also have an interesting problem that I started using hardy version + ~um1 for ppa uploads to gutsy, but the sources are shared across all dists in the pool, so I need to distinguish
[15:04] <lool> StevenK: Do sleep, I prefer uploading something which will not actually be used
[15:04] <lool> StevenK: 'night to you
[15:05] <StevenK> Night!
[16:32] <lool> amitk: The Samsung FSET will pull linux-lpiacompat by default; this seems broken; should it pull linux-image or linux-image-lpia?
[16:32] <lool> Or linux-image-lpiacompat?
[16:34] <lool> (I'm using mccaslin BTW)
[17:36] <lool> Does someone know how the hosts file is generated?
[17:36] <lool> With newer MIC, it's copied from the host
[17:37] <lool> Hmm it seems it always was copied over
[19:52] <lool> Mithrandir: I don't have a place to push my MIC yet; I'd like to sort the issue preventing the UI to come up on the device before uploading, but it might not be in MIC itself; if you really need one, let me know and I'll put it as a tar somewhere over the WE
[20:26] <Mithrandir> lool: ok, over the weekend is fine
[20:40] <LuitvD> is Ubuntu Mobile and Embedded just for UMPC-like devices? or also for QVGA smartphones?
[20:41] <smagoun> LuitvD: For now it's just for UMPC-like devices 
[20:41] <smagoun> it requires an x86 CPU
[20:41] <mjg59> Currently we're only targetting x86 compatible devices with a resolution of 800x480 or higher
[20:41] <LuitvD> smartphones (ARM core) are x86 too right?
[20:41] <mjg59> No
[20:41] <mjg59> They're ARM
[20:41] <LuitvD> damn :(
[20:41]  * LuitvD stoopid
[20:42] <smagoun> if you give us money to work on an ARM port, we'll do the work ;)
[20:42] <LuitvD> lol, would it be worth more then OpenMoko? 
[20:42] <LuitvD> (if it would be ARM-compatible?)
[20:42] <mjg59> The current UI is not suited to low-resolution devices
[20:43] <LuitvD> right...
[20:43] <LuitvD> so I should just go with something else?
[20:47] <amitk> lool: You want linux-image-lpiacompat on the samsungs
[20:48] <amitk> and linux-image-lpia on the crownbeach