[05:41] What is the purpose of the ppa apt sources? [05:41] hi [05:41] eg. deb http://ports.ubuntu.com/ubuntu-ports hardy-updates main restricted universe [05:41] Hi [05:42] er, sorry eg : deb http://ppa.launchpad.net/ubuntu-mobile/ubuntu hardy main [05:44] looking forward to trying ume [05:45] ahh.. v8.04.. I should try it out. [05:45] excellent. [05:46] desktop edition rather. [05:51] and it fits on a cd, cool. [06:41] good morning [07:02] Hoorah! I finallaly got Ubuntu Mobile working on my EeePC. My touchscreen arrived in the mail yesterday, once I get it installed, this is going to be great! [07:36] inkynoob: Cool [07:36] inkynoob: What's your touchscreen? [07:37] A generic 7 inch USB touchscreen from ebay. The manual is in chinese, but I plugged it into my desktop and it worked automatically with Ubuntu Hardy === cprov-afk is now known as cprov === StevenK_ is now known as StevenK [10:10] StevenK: why did you have to upload python-central to the PPA? was the reason something like bug 222829? [10:11] dholbach: For the snapshot, no other reason. [10:12] OK [10:12] it was just weird that there were outdated .pyc files [11:37] Down to 38 source packages! [11:37] in the ppa [11:38] amitk: Could you visit the ppa delete page and see why some linux-* stuff shows up there as superseded? Anything we could drop from there which isn't actually useful anymore? [11:39] asac: Hey, it's unfortunate that we have this xulrunner-1.9 fork in the ppa ATM [11:40] asac: Could you apply the patch on lpia only? Or apply it in all cases, add some ifdefs around its code, and only turn the flag on lpia? [11:40] asac: Otherwise, we will have to update xulrunner-1.9 in the ume stable ppa each time we update xulrunner 1.9 in hardy... [11:42] lool: the patch is too hacky. i hope the gconf component can be properly isolated and shipped as a separate package. [11:42] asac: Even if it's hacky, can't it be surrounded by #ifdef GCONF_HACKY? :) [11:43] lool: if that is done it will stay that way forever ... and lpia users cannot get a clean xulrunner [11:45] asac: Yeah, but it's a better solution for hardy maintenance don't you think? [11:45] asac: Or do you think that gconf bit could be shipped in a separate component in the next month? [11:46] no i don't think so. we should have the proper solution if possible at all [11:46] its not rocket science ... its basically just moving the file somewhere else in the build system [11:46] asac: Ok; will it need to be a separate package? [11:46] lool: done [11:46] amitk: Thanks! did you remove many packages? [11:47] asac: If it does need a separate binary package, I'm a bit worried that it will be acceptable under the SRU policy [11:47] asac: Unless we can build it out of tree [11:47] lool: a separate binary package from same source tree [11:48] asac: Do you think it's acceptable for a SRU? [11:48] lool: i think so [11:48] Cool [11:48] asac: Then that'd be top notch [11:48] lool: yeah. lots of old ones. I thought PPA got rid of superseded ones automatically [11:48] amitk: I thought so too, I wonder whether these were really old and broke some ppa machinery [11:48] amitk: You know we had issues with early kernel builds and all [11:48] lool: perhaps [11:49] amitk: What's the plan for the kernel? Can we drop the ppa version entirely? [11:50] amitk: Basically, what remains to be done WRT to removing packages and uploading to hardy-proposed? (based on the email exchange we had) [11:51] lool: amitk: when you build new binary package names the old ones remain published and hold the source in the archive disk, you have to remove them manually in +delete-packages [11:52] cprov: Thanks for the info. [11:52] lool: a few trivial configs need to be patched into Ubuntu kernel, then we can get rid of all kernel stuff in PPA [11:53] cprov: Interesting, thanks [11:54] you are welcome. [11:54] cprov: Do you beep on ppa? :) [11:54] lool: yes :) [11:54] amitk: Excellent, will that land in the next hardy update? [11:55] lool: yes, but only in July [11:55] Aha [11:55] amitk: And the final intel drivers will be in too at that date? [11:55] I guess so [11:55] lool: lots of beeps and pidging-thinkpad-light-discotech lately :) [11:55] lool: if they provide it by then, yes :) [11:55] It's a plugin to blink the backlight when someone pings you? [11:55] Sounds ultimately cool [11:57] lool: yes, a pigdin plugin to blink the thinkpad-light when some says one of the configurable words ... [11:57] it's cool and sometimes annoying ;) [12:02] * lool is tempted to should p p a p p a p p a [12:02] *shout [13:07] <[NO]> hey all, just had a excellent experience installing 8.04 from XP on a Samsung Q1 ultra :) [14:45] [NO]: How was it? [14:45] [NO]: You installed UME or Windows? [15:01] Good morning [15:01] Hey [15:02] What is the ppa repository for? [15:04] inkynoob: It's a place to put things that aren't necessarily fit for Ubuntu proper. This might mean newer upstreams for basic integration testing. While the archive is frozen, it means just about any updates. The use should decline significantly once intrepid is open. [15:04] inkynoob: You can also use for your own packages. Just put there to be built and made available. [15:04] If I want to be testing things and filing bug reports then, should I be using the ppa repository? [15:06] inkynoob: Yes, you can fill a bug report and add your fixed package there. [15:06] ok [15:07] persia: BTW, not sure you followed this, but I'd like us to push as much as possible out of the ppa in hardy updates when possible [15:07] Especially security sensible stuff [15:07] lool: Based on SRU hijacks? [15:08] Yeah, the mail I sent to ubuntu-mobile@ [15:08] Naturally, we should make sure these have low impact, typically only applied for lpia or similar [15:09] persia: We will have to provide security updates and stable updates for 18 months based on this; it's best if most of it can follow the general hardy procedure than go in the ppa [15:09] Right. I'm presuming that new stuff should hit intrepid mostly directly once it's open, and that it's the current hardy PPA that we're draining in the SRUs. Are we pushing more new stuff into the hardy PPA after intrepid opens? [15:10] persia: The target release date for UME is in about a month; we're pushing updates and bug fixes up to that date [15:10] persia: That's slightly earlier than hardy.1 [15:11] We wont focus on intrepid until the first UME release is out [15:11] lool: OK. Thanks for the clarification. [15:11] I think everything should happen in intrepid next cycle; no ppa-only feature shall be released [15:11] (IMO) [15:15] So last night I got Ubuntu Mobile finally istalled on my EeePC. It's running very nicely, but the volume and brightness controls in the menu bar aren't working. Brightnes and volume are working with the keyboard shortcuts though. Does anyone know where I should be looking to make those work together? [15:17] inkynoob: Looks like issues with hal; you could try the gnome brightness applet to confirm [15:17] Look at the special key assignments in the ume-gui-start script as one place to start. [15:17] I have the same issue on the SR8. [15:18] persia, I'll look at that. lool, it might be that only a subset of Hal got installed. I started from Ubuntu JeOS and installed UME on top of that [15:18] inkynoob: That might do it. Check the fset definitions in the moblin-image-creator package to make sure you have the complete set of packages. MY memory is that the metapackages don't match exactly. [15:19] Are fsets a Debian package thing? I saw them when I played with Image Creator, but I just did a CD install to my computer, didn't use an image [15:20] fsets are a special image-creator thing. [15:21] ok [15:47] I heard that port of Ubuntu Mobile to the ARM arch (to work with ITT of Nokia) is still planed, the FAQ link (in the topic) is apparently outdated about this point, have you got more info ? Thanks ;) [15:48] I know problems for this port about closed software of ITOS developed by Nokia with Maemo, and so, Ubuntu Mobile cannot use the full potential of ITT, if you have more info about "collaboration", I will glad to hear it too :) [16:02] Zic: What happened is that Nokia folks have rebuilt Ubuntu for ARM [16:02] This is not related to Ubuntu Mobile in particular [16:03] We do receive many requests about Ubuntu Mobile on ARM === robr___ is now known as robr [17:21] so you never went bowling with goebbels either? === guerby_ is now known as guerby === asac_ is now known as asac === Zic is now known as Zic[Pipi] === Zic[Pipi] is now known as Zic === robr___ is now known as robr [21:16] @agoliveira : After your session yesterday, I finally manages to set a target , add Fsets (Samsung Full) and even see the UI in Xephyr [21:16] What next ? [21:16] Raseel: Well, you tell me :) What do you want to do? [21:25] Well, frankly I have no idea :-) Are there any bugs I can test to reproduce an' stuff [21:25] Test in Zephyr , of course [21:31] Raseel: well, check launchpad. There's quite. Some of them are easy to fix like problems with dialog boxes sizes and things like that. Any help will be apreciated, of course. [21:32] ok. Lemme see what I can dig up [21:33] One thing, btw, when I tried to install the Fset for the Full Samsung with Propreitary thingy, I get an error "apt-get install" cannot find helix-dbus-server [21:33] Is this a known issue ? [21:46] Raseel: This package needs to be available from the APT repos your configure [21:46] Raseel: We have it in a private repo, but it relies on non-redistributable bits (helix stuff) [21:52] Raseel: You can edit it out from the fset file description. [21:54] I already selected the samsung-full-mobile-stack (no propreitary [21:55] ) and it worked [22:19] asac, lool despite my last email, mobile-basic-flash does not yet work with xulrunner 1.9. Still working out the issues [22:19] hopefully by end of day [22:19] so v0.44 is the last stable release. v0.45 has the patches for xul but doesn't work correctly. [22:19] fyi. [23:15] is there a place that identifies the licenses of all Hardy packages? [23:15] like GPL 2, 3, BSD, etc. [23:17] Looks like each installed package has a copyright file in /usr/share/docs//copyright [23:17] question: I just made a new project/target with MIC and when I run it in Xephyr the icons don't open up the right apps? [23:24] bjwood0, what apps do they open? [23:24] bjwood0, in your drop-down menu (top-left), what categories to you have? [23:25] if you have something about system management, then you are probably reading the /usr/share/applications/*.desktop files from your system, and not your target [23:25] this is a common bug, fixed by running "pkill gconfd" in the target before launching xephyr [23:25] (just guessing) [23:25] shouldn't occur on the target of course. [23:25] s/target/device