[04:24] <inkynoo1> In Mobiln Image Creator, what is special about the samsung-q1 (and other) targets? Is it just the kernel which has support for the device? Or are there device specific programs or something? 
[06:23] <dholbach> good morning
[15:26] <ulugeyik> hello
[15:31] <ulugeyik> I am a newbie as far as Ubuntu-Mobile goes and I am confused about how to go about testing it on  Samsung Q1U-SSDXP. 
[15:31] <ulugeyik> As far as I can tell, all pre-built binaries are for installation and not for Live-CD/Live-USB which is what Iam seeking. Should I be building that from scratch?
[15:32] <inkynoo1> ulugeyik, I'm pretty new too, but I think you should be able to use the Moblin Image Creator to build a Live-USB image. I played with it a little bit last night and it was fairly straightforward
[15:33] <inkynoo1> https://wiki.ubuntu.com/MobileAndEmbedded/CreatingAnImageForUMEDevice
[15:34] <ulugeyik> Thanks inkynoo1, that is as much as I got too, thanks for confirming it. I will try it out.
[15:35] <inkynoo1> I tried booting the image on my EeePC, but it hung part way through the boot process. It did create the image though, and let me write it to my SD card
[17:26] <ulugeyik> I am trying to make the image like inkynoo1 suggested. I can not seem to be able to create a working "target". I can only choose "core" (everything else crashes, and it seems like a known bug?0
[17:26] <ulugeyik> then once the target is created, chosing "Live USB" with GUI gives an error about missing kernels.
[17:27] <ulugeyik> any suggestions?
[17:28] <ulugeyik> "no kernels were found" is the error message.
[17:30] <agoliveira> ulugeyik: I've never used the live USB function but first you have to create the image. I suggest you use a very complete one, core only has the minimal.
[17:30] <agoliveira> ulugeyik: Also, check on the console for any errors. If you find anything, open the proper bug report.
[17:30] <ulugeyik> according to https://wiki.ubuntu.com/MobileAndEmbedded/CreatingAnImageForUMEDevice 
[17:31] <ulugeyik> "The image-creator has a nasty bug that makes it crash if any fset different from "core" is selected."
[17:31] <ulugeyik> so does this mean I should do this without GUI?
[17:31] <agoliveira> ulugeyik: This is old and has being fixed.
[17:33] <ulugeyik> hmm. let me try again then. 
[17:38] <ulugeyik> it gets in a cycle of "apt-get update", "apt-get install -f"  due to some missing packages. BTW, I am doing this on Gutsy and not Hardy. 
[17:40] <persia> ulugeyik: You'll get much better results from hardy
[17:40] <agoliveira> ulugeyik: Should not be an issue as it does it in a chroot but I higly recomend using hardy anyway. Gutsy is not supported for UME.
[17:43] <ulugeyik> I assume you mean the host computer that I am using the create the image right? thanks for the advice, I did not realize that, I will upgrade my distro and then try it. 
[17:49] <persia> ulugeyik: You might be able to backport the newer moblin-image-creator to gutsy, but there may be other components that also benefit from the upgrade when creating images.
[17:59] <lool> ToddBrandt: Hey, any reason moblin-applets in ppa builds against moko instead of libmokoui2?
[17:59] <lool> (as in hardy)
[18:31] <ToddBrandt> lool: I was told to build against moko, what's the difference between libmokoui and moko?
[18:33] <lool> ToddBrandt: When were you told this?
[18:33] <ToddBrandt> many months ago
[18:33] <ToddBrandt> moko is our moblinized version of the openmoko stuff
[18:33] <lool> ToddBrandt: Ok; libmokoui2 is "new"
[18:34] <lool> ToddBrandt: moko is a fork of an early libmokoui by Moblin
[18:34] <lool> To add missing API etc.
[18:34] <lool> libmokoui2 is downloaded from openmoko as verbatim as possible
[18:34] <lool> And maintained by the openmoko people
[18:34] <lool> ToddBrandt: Now would be a good time to move to libmokoui2 (before the UME release)
[18:34] <ToddBrandt> If it's straight from the openmoko base then I don't know if it will work, the ubuntu-mobile ppa moko has some changes
[18:35] <lool> ToddBrandt: We do need to port it to the libmokoui2 one
[18:35] <lool> ToddBrandt: I think this is the case in hardy now
[18:35] <lool> ToddBrandt: I would have thought you would have received the corresponding changes
[18:35] <ToddBrandt> ok, Frank Li is our resident moko expert
[18:36] <lool> ToddBrandt: Yes, StevenK and him worked together on this move
[18:36] <lool> and with upstream
[18:36] <ToddBrandt> oh
[18:36] <lool> ToddBrandt: The only change in hardy is:
[18:36] <lool> -PKG_CHECK_MODULES(MOKO, moko)
[18:36] <lool> +PKG_CHECK_MODULES(MOKO, libmokoui2)
[18:36] <ToddBrandt> I see, so basically I need to switch over the applets to use this new guy
[18:36] <ToddBrandt> ok, I'll try it out
[18:36] <lool> in debian/patches/mokoui-changes.diff
[18:37] <lool> ToddBrandt: That'd be nice, thanks
[18:37] <lool> ToddBrandt: Can you ping me when it's the case so that I archive moko from the ppa?
[18:38] <ToddBrandt> yea, I can do it now gimme an hour or so
[18:38] <lool> Cool, thanks
[18:59] <ToddBrandt> lool: I can't get a target to build, is there a problem with libzlui-maemo or 0.8.14-1ubuntu1? The error says that it can't find these packages because of a 404 error
[19:45] <lool> ToddBrandt: You need to apt-get updatez
[19:45] <lool> ToddBrandt: Missing packages 404-ing are usually due to an out of date list of packages on your side
[19:45] <lool> ToddBrandt: Make sure you remove rootstraps etc. as these act as caches
[19:46] <lool> ToddBrandt: I usually wipe everything between MIC builds; however if you have a proxy such as squid it could be the cause as well
[19:46] <ToddBrandt> lool: actually it's a mirror problem, I can build it ok now
[19:46] <lool> Cool
[19:46] <lool> Happens to me too from time to time when the mirror serves an old Packages or Sources.gz and I need a package which has been uploaded in the mean time
[19:47] <ToddBrandt> lool: ok, I swapped moko with libmokoui2-dev in the debian/control file and PKG_CHECK_MODULES(MOKO, moko) with PKG_CHECK_MODULES(MOKO, libmokoui2) in configure.in. I ran it and it seems to work. Did you want me to create a new version and check it in now?
[19:49] <lool> ToddBrandt: Sounds good!
[19:49] <lool> ToddBrandt: Thanks!
[19:51] <lool> ToddBrandt: Why is it that moblin-applets didn't switch to tarballs BTW? :)
[19:51] <ToddBrandt> lool: I overwrote inuka's changes
[19:51] <lool> Ah
[19:51] <lool> ToddBrandt: You mean by mistake?
[19:51] <ToddBrandt> I had to update the debian directory and I thought that was the only way
[19:52] <ToddBrandt> so yea, by mistake
[19:52] <lool> ToddBrandt: You can easily recover his version
[19:52] <ToddBrandt> well, I included all his debian/rules changes for patching
[19:52] <lool> https://launchpad.net/~ubuntu-mobile/+archive?field.name_filter=moblin-applets&field.status_filter=any
[19:52] <lool> ToddBrandt: But we want to keep the packaging separate from moblin.rog
[19:53] <lool> ToddBrandt: The short reason to "why?" is exactly what happened: that you people maintain a debian/ dir which we can't update
[19:53] <ToddBrandt> yea, but for instance, just now I changed the debian/control file
[19:53] <lool> So when you upload yours, changes other people without commit did are lost
[19:53] <ToddBrandt> what's the proper way to update a debian file?
[19:54] <lool> ToddBrandt: You 1) dget -x the .dsc from the ppa
[19:54] <ToddBrandt> I have 0.58 sitting here waiting to be uploaded, I might as well get this one back to the tarball strategy
[19:54] <lool> 2) cd into that tree and do your changes
[19:54] <lool> 3) upload
[19:54] <ToddBrandt> Is this documented in a wiki somewhere that I just haven't seen?
[19:54] <lool> If you have a new upstream release to prepare in 2), you can simply type "uupdate ../moblin-applets-$new_version.tar.gz"
[19:55] <lool> ToddBrandt: Probably not this particularly short version in the w.u.c/MaE wiki, but it's in the main wiki.ubuntu.com wiki for sure
[19:55] <lool> ToddBrandt: If you are physically near inuka_desk, perhaps you could prepare the update together?
[19:56] <lool> ToddBrandt: Be sure to start from inuka_desk's version before following the previous 1/2/3 steps
[19:58] <inuka_desk> ToddBrandt: the info is in our wiki, also sent an e-mail on this last week. Ping me if you have issues
[19:59] <lool> ToddBrandt: https://wiki.ubuntu.com/PackagingGuide/Howtos/DebianWatch
[19:59] <lool> https://wiki.ubuntu.com/PackagingJam
[20:00] <ToddBrandt> inuka_desk: yea I saw that, but I didn't see any info on how to change the debian files
[20:00] <lool> https://wiki.ubuntu.com/PackagingGuide/Recipes/DebianWatch might be the newer one
[20:00] <lool> I have to leave now, see you people
[20:00] <ToddBrandt> lool: so I should delete versions 0.56 and 0.57?
[20:00] <lool> ToddBrandt: No need t
[20:00] <lool> to
[20:01] <lool> ToddBrandt: Start from inuka_desk's latest upload (wget the .dsc, .diff.gz, .tar.gz from the archived versions in the ppa)
[20:01] <ToddBrandt> ahh
[20:01] <lool> ToddBrandt: Then uupdate to the new version (0.58), update control and changelog for your changes
[20:01] <lool> And upload
[20:02] <lool> ToddBrandt: If you have any issue with this, I'm happy to help
[20:02] <ToddBrandt> ok, thanks
[20:02] <lool> But I have to go for tonight, I'm still jetlagged from returning from the US yesterday ;)
[20:02]  * lool &
[20:25] <bspencer_> after I check somthing into the PPA, is there a webpage that will show me the status of things building
[20:25] <bspencer_> or do I just have to wait for the email?
[20:25] <asac> bspencer_: yes, go to the +archive page
[20:26] <asac> bspencer_: then you can go to view build status or something and search for your package
[20:26] <asac> (with "show all states"
[20:26] <asac> )
[20:26] <agoliveira> bspencer_: https://edge.launchpad.net/~ubuntu-mobile/+archive/+builds
[20:29] <bspencer_> asac, agoliveira -- great, thx.
[20:46] <agoliveira> bspencer_: BTW, I tried to create a new image today using image-creator and It's complaining about helix-dbus-server missing
[20:46] <asac> ToddBrandt: could you please be more proactive when choosing versions for ume uploads?
[20:46] <asac> ToddBrandt: just found that you just bumped the ubuntu revision ... which is, erm, not so good :)
[20:47] <asac> ToddBrandt: usually you use the official version and append a ume suffix
[20:47] <ToddBrandt> asac: I'm doing that now, I'm creating a new 0.58 version based on Inuka's original 0.55-1 version
[20:47] <asac> ToddBrandt: ?
[20:47] <asac> network manager has 0.6.6 :)
[20:47] <asac> network-manager - 0.6.6-0ubuntu5 
[20:47] <asac> network-manager-applet - 0.6.6-0ubuntu2 
[20:48] <asac> thats should have been 0.6.6-0ubuntu4+804ume1
[20:48] <asac> or something like that
[20:48] <ToddBrandt> ok, 0.58.1
[20:48] <asac> its ok now. i just have to skip the ubuntu5 version now
[20:49] <asac> ToddBrandt: talking about mobile-applets?
[20:49] <ToddBrandt> asac: yea
[20:49] <asac> for those i don't mind;) ... but i think you should append a ume suffix as well there
[20:49] <ToddBrandt> oh, if you're just talking about network-manager, you can blow those away, I only put those there because the target wasn't being pointed to the latest
[20:50] <asac> ToddBrandt: ah so those are exactly the ahrdy packages?
[20:50] <ToddBrandt> asac: yes, but I think they're a little out of date now
[20:50] <asac> thought it was somethig with mobile patches
[20:50] <ToddBrandt> nope
[20:50] <asac> ToddBrandt: ok ... then it doesn't matter much. we can also keep them there
[20:51] <asac> sorry for the noise ;)