[00:00] rsalveti: what do you need an app core dev for? [00:00] and what is an "app core dev"? [00:00] mhall119: someone that has the permission to approve mrs :-) [00:01] mhall119: fginther approved the mr sergiusens created [00:01] rsalveti: ah, you just needed someone on that app's dev team [00:01] so we're god [00:01] good [00:01] you are? [00:01] nops [00:01] oh, now I'm disappointed [00:01] lol, neither sergiusens, we need to get our hands dirty first [00:01] working on the dark side only [00:03] rsalveti you can't be core in two places [00:03] :-P [00:03] yeah [00:05] jezz, my thinkpad is now just showing 30m of battery the most [00:05] craptop [00:10] Saviq_: rsalveti https://code.launchpad.net/~sergiusens/unity/release_1.69/+merge/157259 [00:13] sergiusens: cool, waiting deb [01:16] OT | Not sure if this is still up to date .. but at least the message is getting out there ... | http://www.knowyourmobile.com/os/ubuntu-android/19842/ubuntu-android-everything-you-need-know === smartboyhw_ is now known as smartboyhw [02:41] hmm redtape, First time i've seen those images, I have a feeling there fake. I try to follow this project as much as possible, 3G isn't enabled, background is wrong plus all those apps are not fucntional. [02:44] daily image out early? [03:19] rsalveti: I'm back fwiw === tux is now known as Guest21807 === jono is now known as Guest52708 === lubuntu is now known as Guest9310 [06:36] good morning === LarrySteeze is now known as LarrySteeze|Away [07:04] hi all, [07:04] 'phablet-flash -l ' failed with Not enough space in /data, found 3.5G [07:06] that's for a nexus7 with 16G, any idea where I can safely 'rm' stuff ? [07:22] where can I find details regarding how phone starts? what address does it go to execute instruction? How memory is mapped ? How to interact with graphic card? etc. [07:23] pvd, that level is pretty much android [07:24] the code for this layer is at phablet.ubuntu.com [07:24] thanks, ogra_; but is there any document where details are listed so that it's easy to understand the code ? [07:26] well, its a minimal android (kernel, HAL and the most minimal system to use them), android documentation applies ... above that there is a container with the ubuntu rootfs ... interaction between container and android is done through the libhybris api [07:27] i dont think there is any specific documentation except the code itself atm [07:28] but as I understood, ubuntu used android core to get into market early, but eventually the plan is to write all the layers in it's code. [07:29] not only to get in the market ... but to have proper driver support ... i dont think that layer is going away soon ... [07:30] there is work going on to flip the container model and to move the android side into a container and keeping the ubuntu rootfs as the "main OS" but to have full HW support the binary drivers from the android side are needed [07:44] ogra: Any details available yet on how the "flipped" containers will look like? Any indication of progress? Thanks! [07:45] https://blueprints.launchpad.net/ubuntu/+spec/client-1303-containers-host-client-ubuntu-android [07:45] Thanks :) === chriadam is now known as chriadam|away === lubuntu is now known as Guest25945 [08:44] seb128, whether the welcome screen is configurable is more a question for rachelliu and chaotic [09:54] mpt, hey, ok, thanks [09:55] seb128, I just asked them about it and they said it should be configurable (including being able to turn it off entirely), but they haven't settled even on default contents yet, so it's a bit early to go into detail. [09:56] mpt, ok [10:01] tsdgeos: ping [10:02] gusch: hi [10:02] tsdgeos: can you review the bugfix of the gallery bug you found yesterday? [10:02] gusch: i guess i can [10:02] if it's not hard :D [10:02] tsdgeos: cool https://code.launchpad.net/~schwann/gallery-app/gallery-cpu-photo-view/+merge/157314 [10:05] gusch: ok, having a look [10:06] tsdgeos: thanks - it's not a long one ;) [10:15] gusch: oh, so it was the ActivityIndicator :D [10:16] tsdgeos: I was pretty surprised, that the visible flag is propagated dorn to the thumbnails [10:16] gusch: do you think it makes sense to create a test for this? or too hard/unuseful? [10:17] tsdgeos: I'm thinking if it is easily possible to test ... [10:21] gusch: what do i delete so that the gallery needs to recreate the thumbnails? [10:22] tsdgeos: ~/Pictures/.thumbnails [10:22] ok [10:23] tsdgeos: testing would be a huge effort - don't think it's worth the effort [10:23] oka [10:23] tsdgeos: unfortunately there where no tests at all when I took over the gallery (one year of work without a single test...) [10:24] tsdgeos: atm I try to increase the number of UI tests - for some basic regression testing [10:25] okidoki === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader [10:41] hello [10:43] i have been searching the project wiki, but was unable to find a page that would list ubuntu-touch features and perhaps future roadmap for the project [10:43] i am tasked with figuring out the easiest way to port apps to ubuntu-touch, so i need to know what the OS supports [10:44] QML/Qt5/C++ and HTML5 for apps [10:44] i saw there was an android layer, is this feature something like the android runtime in BlackBerry 10? [10:45] http://developer.ubuntu.com/get-started/gomobile/ [10:45] ogra_: thank you very much [10:45] there is no java on the images (and isnt planned to) [10:45] the android layer is solely for having support for binary drivers [10:46] ogra_: ok, i get it [10:46] i.e. we use the kernel and HAL .... and the amount of android to make use of them [10:46] ogra_: but the QML/QT code for BlackBerry should be rather easily portable to ubuntu-touch, right? [10:46] the rest is a plain ubuntu which uses libhybris to talk to the HAL layer [10:46] yeah [10:46] ogra_: ok, i will keep that in mind [10:47] there are surely minor differences though [10:47] * ogra_ isnt an app developer :) [10:47] ogra_: sure, but i imagine nothing of that magnitude, that would prevent on from having a common codebase [10:48] i know people have done ports of their projects from and to sawfish without much hassle [10:48] i would imagine BB isnt much different [10:48] the thing is, i got an app, that has separate codebases for android, ios, windows phone and windows desktop and we would also like to support ubuntu touch and blackberry [10:48] cool [10:48] mhall119 can probably say more, he is deep into app dev stuff [10:49] ok, thank you, i'll hang around if he shows u p [10:49] :) === MacSlow is now known as MacSlow|lunch === lbt is now known as lbt_away [11:16] hi all [11:17] is there any architecture schema of Ubuntu Touch somewhere? I don't find any... [11:18] i dont thinnk there is atm [11:18] but feel free to ask questions :) [11:20] so, here are my questions: I know the basis of Ubuntu Touch is the basis of Cyanogen... I also know you can write apps in web technologies, QML, C++ [11:20] what else is used in Ubuntu Touch? [11:23] well as you said, there is a minimal android layer to make use of drivers, then there is a container in which the ubuntu rootfs lives and there is libhybris to allow conversation between these two layers [11:23] on top you have the QML phone shell [11:23] there isnt much more :) the ubuntu rootfs is like any other ubuntu you know [11:23] stuff like GStreamer, Alsa, Telepathy, DBus, SQLite, X11, Mir, Clutter, Wayland, GTK, EFL, Webkit, Gecko, Enyo, PhoneGap/Cordova, [11:24] Can anyone tell me if it is wise to install UT on a Samsung Galaxy S3 (GT-I9300)?? [11:24] there ios no X11 at all [11:24] the current setup uses SurfaceFlinger which is soon to be replaced with Mir [11:24] gstreamer is supported, Gtk isnt [11:25] Norbert, define wise :) [11:26] if you are a developer and want to test your apps on a real device or if you are a designer and want to get an impression it surely is ... [11:26] orga_ Good point. I only wand to have an impression [11:26] if you expect something for day to day use to replace your existing phone it isnt yet [11:27] OK thanks than I will wait. Because the GS3 is not my spare phone [11:27] funny that Ubuntu (Touch) does not use Gtk, but Qt ;-) [11:27] the desktop will soon as well === om26er is now known as om26er] === om26er] is now known as om26er === SkavenXXI-[OFF] is now known as SkavenXXI [11:27] unityNext is QML based [11:28] ah ok [11:28] so, Ubuntu Touch is GPLv3, right? [11:28] yes [11:28] at least, core apps are [11:28] cool [11:28] everything is [11:28] so third party apps are developped in QML, but also web, right? [11:29] ogra_: except anything proprietary driver wise :) [11:29] unless it is based on a foreign project that requires otherwise all code canonical writes and publishes is GPL3 [11:29] Nyconyco, right, you have the choice ... QML or HTML5 [11:30] can you run Android apps on top of Ubuntu Touch? either directly, or through OpenMobile's ACL, like Tizen and Sailfish? [11:30] nope [11:30] there is no java in the image ... and not planned to be added ... [11:30] ok [11:30] but you can surely create an emulator to make it work as a third party app [11:30] I guess... ;-) [11:31] it will get tricky once we switched to Mir though [11:31] so, how is the OS development going? I've updated my Galaxy Nexus, and things are going forward, nice to see ;-) any roadmap? [11:34] we're about to switch to base development to raring (13.04) [11:34] a first image was released a few days ago [11:35] what des it mean? [11:36] https://plus.google.com/100264483712374857174/posts/36eG24ff6LQ [11:37] currently the image is based on an already released ubuntu version [11:37] that makes development not very effective so it is moving into the regular ubuntu archive now [11:40] ok, so should I play with this raring-based version? [11:41] what if I want to demo it? [11:41] stable and fast enough? [11:43] for stability rather use the daily image [11:46] ok, thnaks for your time! ;-) [11:48] <_BAMbanda> wait, so this allows the full terminal to be available to devices? meaning that I can run sudo apt-get while I'm over 3g? and ssh into other machines over a vpn? [11:49] well, there is no gui terminal app yet, but yes it will [11:50] you can ssh to the device today ... apt-get is fully supported (and you can also use adb to get to the ubuntu cmdline) [11:54] <_BAMbanda> hmm no nokia lumia support? how do we add other phones to the list? === dandrader is now known as dandrader|afk [12:05] _BAMbanda, by porting :) [12:05] (see the porting guide) [12:06] ogra_: do you happen to know where the compressed initrd lives? I'd like to muck about with init.rc [12:07] ev, depends on the device, i know the bootimg (which contains kernel, initrd and a config) lives in mmcblk0p2 on the nexus7 [12:08] thanks, that's the badger [12:08] ev, use abootimg to unpack/update/modify [12:08] cheers [12:09] its in the archive ... (even for your PC if you jsut want to dd the img out of the partition and fiddle with it remotely) [12:09] yeah === MacSlow|lunch is now known as MacSlow [12:10] but it also can operate dircetly on the partition in the device if you like [12:10] its very flexible [12:13] <_BAMbanda> ogra_ : is there anyone to jailbreak and do this on the iphone? [12:14] well, the jailbreak wouldnt be the prob but running android on it would i guess [12:14] you need a device that iis supported by cyanogenmod [12:15] if you want to port to one that isnt, you need to add cyanogenmod support first [12:15] <_BAMbanda> i think i've heard of people running android on iphone. I know that iOS is unix based right? [12:15] could be, i never touched an iphone :) === dandrader|afk is now known as dandrader [12:17] <_BAMbanda> according to youtube, people have cyagenmod on iphone [12:17] <_BAMbanda> does that mean everything should work out? [12:17] dunno, try it :) [12:18] <_BAMbanda> ogra_: sorry, I have a problem with getting exciting and asking people stuff without trying! [12:19] :) [12:19] no prob [12:20] <_BAMbanda> this is so genius, imagine the pssoibilities of full linux terminal with netwroking abilities in your palm [12:21] hey ogra_ , you wouldn't happen to know if there's a way to get the on-screen keyboard to show using adb? [12:21] nope, i don't [12:22] I have an Asus Transformer pad and only the keyboard dock works (but mine happens to be broken and only half of the keys work) :( [12:22] probably the maliit documentation knows :) [12:24] didn't know about this, cheers for the heads-up :) === SkavenXXI is now known as SkavenXXI-[OFF] === _salem is now known as salem_ [12:47] so is UnityNext gonna be running on the Ubuntu desktop version AND the Ubuntu Touch version? [12:48] yes, thats the purpose of unitynext [12:51] ogra_: rsalveti so now that I can start building/providing the raring images through jenkins, what should we do cdimage wise? [12:51] since we have a _quantal_ in the name [12:52] move the name :) [12:52] just tell me once you did and i'll update the sync script [12:53] ogra_: well we are still keeping the quantal one [12:53] (on cdimage we usually build them completely generic, only the final publishing tool names them, you should probably consider that too for the jenkins builds) [12:53] UGH! [12:54] you mean you want dailies for quantal still ? [12:54] ogra_: we did build them completely generic [12:54] ogra_: well, it's not my call... it's more of pmcgowan and bfiller ... I wouldn't consider these builds stable yet [12:55] sigh [12:55] ogra_: and yes on quantal, until we get further notice [12:55] you are breaking all cdimage policies [12:55] dailies are ponly for development releases ... i'll see what i can do [12:55] I think its just a transition issue [12:56] why the heck do we duplicate all work [12:56] maybe don't publish raring images yet [12:56] ogra_: huh? [12:56] will we triplicate once S opens ? [12:56] no we will transition again [12:56] pmcgowan: if we don't publish, there's no way people get to start fixing the issues with it though [12:56] pmcgowan, you are doing work on quantal ... while at the same time doing work on raring [12:56] we can get it from jenkins for a week? [12:56] whats your suggestion [12:56] cold turkey? [12:57] i can arrange something, indeed, but the links will change [12:57] pmcgowan: from jenkins, yes, but only people with access to the VPN [12:57] its just short term until we deem it stable [12:57] i suggest doing work on the development release :) [12:57] and leave the done deal behind [12:57] what is the status of the raring image? [12:57] is it solid? [12:58] pmcgowan: not solid, UI works, most apps work, telephony and networking doesn't [12:58] it surely has more issues than quantal [12:58] in a nutshell [12:58] oh, and memory runs out faster [12:58] * ogra_ would replace mwc-demo with the last quantal daily and then move on [12:59] ogra_: replace or add a new one? [12:59] peopple wanting something half way solid can use quantal ... devs can get the daily with breakage and watch it go away over time [12:59] sergiusens, does the mwc one have any value ? [12:59] ogra_: it does to some people [12:59] apart from "hey we were at mwc" [13:00] I think its still used for most demos [13:00] I can check [13:00] but keeping it costs little [13:00] well, if it has, lets put a quantal "final" next to it [13:00] or some other name, as you like [13:01] ogra_: I don't care about the names, but I woud need to update the download tool [13:01] my feeling is raring build needs to be minimally functional for development, and networking and telephony not working doesnt meet that [13:01] pmcgowan: I agree, that's why I say, provide without replace [13:02] sergiusens, rigght, i would liek to avoid changes in multiple places [13:02] lets set some criteria for the switch [13:02] and get people focused on allowing it [13:02] ++ [13:02] having two dailies seems rather bad imho [13:02] sergiusens: lets mark any transitions bugs top priority [13:02] pmcgowan: who should we involve in setting that criteria? [13:03] ogra_: we did the same for migrating from Qt5 beta to proper, took a week and no one noticed (users), which was good [13:03] lets make a proposal and circulate [13:03] pmcgowan: ok, I'll scribble an email [13:03] k [13:04] s/proper/release [13:04] sorry, i'm spolied by distro practices :) [13:04] we make a release and then there is a hard cut [13:04] to not duplicate to much work [13:04] in this case there was no "done" so its a bit different [13:04] we cant regress that far [13:04] yeah, i understand [13:04] k [13:05] ogra_: consider us a rolling release :-P [13:05] haha [13:05] now yu implanted the blues brothers in my ear again [13:05] .... rollin rollin rollin ... === ckpringle_ is now known as ckpringle [13:15] is there an arm equivalent of the lspci command? [13:15] lshw but you need to suppress walking the pci bus [13:15] or lsusb [13:15] and indeed there is sysfs [13:15] ah yeah [13:17] I can't for the life of me figure out how to make this thing dump core. [13:17] might be that the kernel doesnt allow that ... its an android kernel after all [13:18] and we dont change much in the config [13:19] ogra_: yeah, it's starting to seem that way. I did stop debuggerd from spawning, setrlimits to allow unlimited core, and set the core pipe handler appropriately, but no "(core dumped)" portion of the the segfault message [13:20] well, talk to the kernel team ... iirc ppisati just touched the nexus7 kernel, he should roughly know about the config [13:21] i can imagine that android doesnt relly like if your system dumps a core to a limited MMC [13:24] finally, got hci0 on the nexus 4 :D [13:24] yeah [13:24] * ogra_ applauds cyphermox [13:25] ogra_: I haven't taken the time to hack what I wanted in phablet-flash though, but I'll possibly do it this morning === juicyjones|away is now known as juicyjones [13:25] yeah, no hurry [13:26] better later than buggy ;) [13:41] cyphermox: mind checking if today's image has bt support at nexus 7? [13:45] jhodapp: today's image should have chromium_http support as well [13:45] rsalveti, awesome, thanks! === ckpringle_ is now known as ckpringle [13:50] rsalveti: sure [13:51] rsalveti: are those manifested somewhere I can see here? [13:52] pmcgowan: the changelog shows what got updated, but to see in detail you need to check the specific git repository [13:52] http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled.changelog [13:52] http://phablet.ubuntu.com/gitweb?o=age [13:52] Is this pretty stable? I understand it is in development but is it good enough? [13:52] that's just because the output of repo sync is not that useful [13:53] rsalveti: but what can I do with it [13:53] the new stuff [13:53] I assume its more embedded than useable [13:53] pmcgowan: the only thing that might affect you is the bluetooth support at nexus 7 [13:53] pmcgowan: the rest is just infra work [13:53] ack [13:54] I think no way to configure the bt though - no ui yet [13:54] pmcgowan: yup, you have to use cmd line for everything [13:54] k [13:58] Are there any good links for getting started with developing on a device? [13:59] fginther, didrocks: what's the news on daily-build-next? Last I remember, platform-api was about to wend its way through the gauntlet [14:00] mterry: you mean, did platform-api built? [14:01] JamesMR, like developer.ubuntu.com/get-started/gomobile/ ? [14:01] mterry: http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/ didn't start, it seems the head job is not schedule, did you schedule it when deploying? [14:01] didrocks, well, I know it will fail its build. I guess did we get far enough to let it? [14:01] didrocks, I thought so? Maybe not [14:01] mterry: looking at http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head/configure [14:02] didrocks, is there a separate schedule for the whole 'head' suite? (I know each stack has its schedule) [14:02] no, it's schedule: 0 3 * * 1-5 [14:02] on the top of the stack [14:03] (this is what is starting "head", which is piloting everything) [14:03] mterry: you did deploy with -U, right? [14:04] ogra_: Almost, the phone app tutorial seems to be out of date though, and I'm trying to get connected to a nexus10, which doesn't seem to want to happen [14:04] didrocks, nope, forgot the -U [14:04] mterry: blame jibel to force -U! I think we should make it default TBH ;) [14:05] didrocks, OK, just did. So now I'm poking an archive-admin [14:05] hi rox [14:05] what can I help you with [14:05] ? [14:06] ogra_: rsalveti pmcgowan for practical purpose, can I call the raring deploy zip s/raring/latest/ or similar for practical purposes? [14:06] mterry: but who? that's the question :p [14:06] mterry: so, yeah, on Monday, it will try now [14:06] didrocks, I'll start a build [14:06] mterry: sure, please do :) [14:07] sergiusens: not following you [14:07] pmcgowan, same here ... [14:07] ogra_: pmcgowan today the zip is called quantal-preinstalled-phablet-armhf.zip [14:08] the raring one should be called raring-preinstalled-phablet-armhf.zip [14:08] I want latest-preinstalled-phablet-armhf.zip [14:08] didrocks, ah! we do need bootstrap for this step [14:08] only on cdimage [14:08] http://10.97.0.1:8080/job/cu2d-platform-head-1.1prepare-platform-api/1/console [14:08] sergiusens: why does it matter? [14:09] sergiusens, http://paste.ubuntu.com/5679820/ ... thats how our desktop images look like on the builder [14:09] mterry: I'll add a sad face in the future to the message ;) [14:09] pmcgowan: so when we move to S, we don't have to go throug this again [14:09] when throwing this exception [14:09] sergiusens, these are standard names live-build uses [14:09] yeah, maybe we can rename when publishing them as well [14:09] so do something similar witho your builds ... [14:10] I like having the series name at the file itself [14:10] make it a lot easier to find the series used [14:10] rsalveti, right, that will happen anyway once we build everything on cdimage [14:10] right [14:10] sergiusens, i dont need "latest" in the name, i have it in the jenkins path [14:10] yeah [14:10] so just call the "thing" ... whatever you like [14:11] :) [14:11] so just phablet-armhf [14:11] yeah [14:11] just drop the release name [14:11] ogra_: ack... well I just want something that doesn't have the series in it [14:11] sergiusens: I dont think preinstalled has any meaning? [14:11] just dont forget to notify me once the content changes ;) [14:11] since my script adds the release [14:12] pmcgowan, it does in the ubuntu world [14:12] pmcgowan: well with rsalveti we went with a name similar to what was used for the nexus 7 ubuntu image [14:12] what does it mean here? [14:12] presinstalled vs live vs alternate are image/installation types [14:12] it means there is no installer involved [14:12] pre what [14:12] I dont care, just not english to me [14:13] at most you have presonalization (oem-config) [14:13] heh, i seem to have something with my fingers [14:13] pre installed [14:13] and personalization indeed :) [14:14] if it means soemthing to others I am fine with it [14:14] ogra_: do you copy file per file? [14:14] it has a meaning for people searching stuff on cdimage [14:14] ogra_: or the whole subdir? [14:14] i loop [14:14] one sec [14:15] ogra_: because I can add the raring part creation to the same jenkins job, but not sure it will break your topology [14:15] so in the end it will be one more file [14:15] sergiusens, http://paste.ubuntu.com/5679847/ [14:16] line 49 to 60 [14:16] err 66 [14:16] i pull by subarch and suffix [14:17] awe: looking at https://code.launchpad.net/~awe/phablet-extras/ofono-flatten/+merge/156901, don't you think it'd be good to apply the patches from debian/patches before converting it to native? [14:18] they should already be applied, if they're not, then our packaging changed between q & r [14:18] lemme check [14:18] awe: right, might be indeed [14:18] awe: that's why the .pc dir [14:19] sergiusens, if i have some way to distinguish a raring file, just add it ... [14:19] didrocks: you might be able to help us as well, we are currently developing rild support at ofono, and the way we did before was converting the package to native and doing the development at the bzr branch itself [14:19] * awe has too many local ofono branches [14:19] didrocks: to move to the distro, we need to move the development at somewhere else and create a distro patch every time we update our tree [14:19] rsalveti: was it something part of distro before? We are not the only upstream for it? [14:20] rsalveti: is that something under strong development? [14:20] didrocks: yes and yes [14:20] rsalveti: is upstream willing to take our distro patches, do they make sense for them? [14:20] didrocks, not yet [14:20] so we're looking in a way to automate the distro patch generation [14:21] we'll try to get them merged soon, but not yet [14:21] sergiusens, call it phablet-next ;) [14:21] didrocks, almost zero work is being done on ofono in debian or ubuntu [14:21] didrocks, we just package whatever is the latest and that's about it [14:21] for touch, we're actively writing code to glue ofono and RILD together [14:22] ok, and the packages that are imapcted is ofono itself? [14:22] yup [14:22] and the problem is that if we use the std ubuntu packaging format, the MRs look gross due to working with patches [14:22] yeah, not ideal [14:22] that's I'd suggest to push our development in a separated tree [14:22] so the patches are moving a lot I guess [14:23] ogra_: ok, so if I just name it latest-phablet+armhf,zip it will be good [14:23] the problem then is how to generate the distro patch easily [14:23] just our code is moving [14:23] sergiusens, what would latest be now, quantal or raring ? [14:23] rsalveti, as I mentioned yesterday, I'd like to wait to split out my code. [14:23] I'm not sure why it's bad practice for me to continue as is until that happens [14:24] ogra_: raring, but you keep release=quantal and everything will be ok :-) [14:24] awe: so, your patches… are they creating new files/folders or mostly changing existing code? [14:24] we can still work by pushing at the package itself, but once s is open, we'd need a different solution [14:24] which means, at the end of this month [14:24] well, i was thinking we could put raring on cdimage as well, just next to quantal in the daily ;) [14:24] didrocks, creating new files, and modifying existing files [14:24] but mostly in newly developed plugin code [14:24] awe: I think you are ok, this is forward thinking [14:25] awe: ah, and this plugin needs to be in the same source tree, we can put as much as possible in a separate projects that we own? [14:25] I also modify the debian/rules and top-level configure to limit the number of plugins built for a touch deployment [14:25] sergiusens, so you can just drop quantal at some point and i can s/quantal/raring/ in my script [14:25] awe: and only distro-patch the part that we need to "glue" it? [14:25] didrocks, yes... the plan will be to split out all the rild plugin code when we merge back into archive [14:25] awe: that's something we'll need to drop before including at the distro [14:25] ogra_: ok, let's _live_ talk about this just to make sure [14:25] didrocks, however we'll still need to deal with how we deploy to touch vs. desktop [14:26] we can't use your distro patches on desktop? [14:26] sergiusens, i have a call in 5 [14:26]