[00:42] <MacSlow> bbl
[00:52] <haxnok> Hi.
[00:53] <haxnok> I wonder what's the most used linux distribution in japan, for desktop computing, not servers.
[00:55] <haxnok> Macs are so popular nowdays, maybe there are many macs users ofc, and i'm surprise they don't have their own operating system, you know japan OS or whatnot, since they were so active in electronics and IC computer development with all the arcade machines of the 80s 90s the NEC, then all the consoles...
[02:14] <JanC> there are Japanese operating systems, of course, but mostly for embedded & such
[02:23] <JanC> e.g. https://en.wikipedia.org/wiki/ITRON_project
[02:34] <oerheks> https://en.wikipedia.org/wiki/Special:Random
[02:34] <oerheks> i vote against the ney UI
[02:34] <oerheks> c/new
[02:35] <JanC> the new skin is about what the French Wikipedia has used for years really
[02:37] <JanC> you can also change the theme when you login
[02:39] <lotuspsychje> good morning
[02:42] <JanC> oerheks: try https://en.wikipedia.org/?useskin=vector
[02:42] <JanC> hm, seems liek it forgets that as you browse on
[02:43] <sarnold> I was hoping for CRT green
[02:43] <JanC> but ?useskin=vector added to a page shows it using the old skin
[03:05] <oerheks> nice
[07:35] <ducasse> good morning
[15:53] <Eickmeyer> leftyfb: If I see you discriminating based on someone's client of choice (Matrix in this case) I'm going to punt you to the moon.
[15:53] <Eickmeyer> That's 100% against CoC and you know it.
[15:55] <leftyfb> Eickmeyer: it's an IRC channel. I'll read messages posted there and help when I can read the messages. I'm not about to click on a link to finish reading messages that get arbitrarily truncated
[15:56] <Eickmeyer> leftyfb: I. Don't. Care.
[15:57] <Eickmeyer> They don't know it's getting truncated on their end.
[15:57] <Eickmeyer> So how would you feel?
[15:58] <leftyfb> then the matrix bridge needs to be fixed as it's a poor experience for both the user and the people reading their messages
[15:59] <leftyfb> I should not have posted that in the channel
[15:59] <leftyfb> that was a poor gut reaction on my part
[15:59] <leftyfb> but that doesn't take away from the fact that the matrix bridge is a very broken experience for all and should be resolved
[16:00] <Eickmeyer> Regardless, being friendly trumps everything, and doing a poor job of that is bad.
[18:25] <sarnold> Eickmeyer: I think it's very friendly to tell matrix users that irc users aren't going to read their messages
[18:26] <Eickmeyer> sarnold: Maybe, but it was the way it was said.
[18:26] <sarnold> Eickmeyer: ah, okay
[22:42] <charafau[m]> hi! Was told that discussions are happening here, so I joined
[22:42] <Jeremy31> Sometimes that is true


[02:46] <TheMuso> There is no way you can assign a shortcut key to an application in its desktop file correct?
[02:48] <RAOF> I don't believe so, no, although I'm not sure where System→Preferences→Keyboard Shortcuts gets its listings from.
[02:49] <mclasen> keynames come from /usr/share/gnome-control-center/keybindings/*.xml
[02:49] <mclasen> the shortcuts usually get stored in gconf
[02:51] <TheMuso> I know about the gconf shortcuts, but was wondering whether apps could be given a shortcut in their .desktop file, similar to what is possible in Windows.
[02:52] <mclasen> no
[02:52] <TheMuso> Ok, thanks.
[03:37] <bcurtiswx3> kenvandine: if anyone wants to try out the new adium theme in maverick for lucid my PPA has it backported
[03:37] <kenvandine> bcurtiswx3, i saw that, thx!
[03:38] <bcurtiswx3> kenvandine: cool, yw
[04:01] <Sarvatt> I don't suppose anyone would be willing to look at an xterm merge for sponsorship? http://sarvatt.com/downloads/merges/xterm/
[04:04] <TheMuso> Sarvatt: I'll take a look.
[04:05] <desrt> robert_ancell: hey
[04:06] <Sarvatt> TheMuso: thank you a ton for the help
[04:07] <TheMuso> Sarvatt: np
[04:09] <Sarvatt> after that xterm and nvidia-graphics-drivers* rebuilds are all thats left for X stuff
[04:09] <Sarvatt> err xdm
[04:17] <TheMuso> Sarvatt: uploaded.
[04:17] <Sarvatt> thanks!
[04:17] <TheMuso> np
[04:54] <hyperair> anyone here familiar with ureadahead's code?
[04:55] <hyperair> i'd like to implement btrfs support for ureadahead, since i'm sick of waiting and nothing's been done
[06:16] <robert_ancell> desrt, hey
[07:31] <pitti> Good morning
[08:19] <didrocks> good morning
[08:26] <pitti> hey didrocks
[08:27] <didrocks> Guten Morgen pitti
[08:28] <didrocks> hum 712M for the netbook CD :/
[08:28] <didrocks> well maverick desktop amd64 is approximately the same size
[08:28] <didrocks> (not the i386 one, weird)
[08:35] <pitti> ugh, what was added since a1?
[08:38] <didrocks> pitti: don't know for desktop. For netbook it's all the removal of maximus/netbook-launcher in favor of mutter/unity
[08:38] <didrocks> pitti: but I think this huge delta should be due to something else
[08:39] <didrocks> hum, I can remove metacity already
[08:50] <huats> morning
[09:05] <ogra> didrocks, urgh
[09:05] <ogra> didrocks, you  completely broke armel netbook
[09:06] <didrocks> ogra: with yesterday's update unity should build now on armel
[09:06] <didrocks> ogra: I didn't check the status, but I'll refresh the ubuntu-netbook metapackage before the week-end
[09:07] <didrocks> I'll add also the -efl, as I guess it was on the CD as a dep of netbook-launcher
[09:08] <seb128> didrocks, nice work with unity
[09:08] <didrocks> seb128: thanks :)
[09:09] <didrocks> all the transition thing is working well for you?
[09:09] <seb128> yes
[09:09] <didrocks> great!
[09:10] <seb128> didrocks, I get no wm decorations though, wanted or gtk csd bug?
[09:10] <seb128> not sure how to close dialogs out of the using the menus which is suboptimal
[09:11] <didrocks> seb128: it's wanted, I should check again the gconf key (I think it's the same than maximus used)
[09:11] <seb128> weird
[09:11] <didrocks> but yeah, until the titlebar isn't in the panel, not useful, I should change temporary the default
[09:11] <didrocks> thanks for the notice, I changed it a while ago there. Anyway, trying on the stock install for lucid
[09:12] <seb128> np, good work again, it upgraded in a flawless way
[09:20] <pitti> bonojur seb128
[09:20] <seb128> hey pitti
[09:20] <seb128> how are you?
[09:21] <pitti> I'm good, thanks! still catching up with peer reviews
[09:22] <ogra_> didrocks, would you mind if i re-added all the netbook bits for armel you just removed for all arches ?
[09:22] <seb128> pitti, oh, I need to do that as well
[09:22] <pitti> meh, the desktop amd64 CD exploded as well
[09:22] <ogra_> we dont have any desktop anymore with your last change to the seed
[09:23] <pitti> desktops are overrated
[09:23] <ogra_> yeah, arm users should just phone with their HW :)
[09:23] <ogra_> what else is it good for
[09:23] <didrocks> ogra_: regenerating the metapackage should do it (at least, adding unity to armel) with yesterday's evening build. Then, you have to add explicitely as a recommend netbook-launcher-efl, right
[09:24] <didrocks> ogra_: before, it was a dep of netbook-launcher which is removed as just a transitional package now
[09:24] <pitti> will there be an -efl like 2D port of unity?
[09:24] <ogra_> didrocks, i'm currently not caring for unity but for having the old 2D desktop working (maximus, go-home-applet, window-picker etc)
[09:24] <ogra_> pitti, there will be a panel thats a gtk container for indicators
[09:25] <ogra_> but we'll keep the efl launcher in maintenance mode as long as we can for arm
[09:25] <pitti> *nod*
[09:25] <didrocks> ogra_: sure, I can do if it you want, add them for armel
[09:25] <pitti> but we could certainly run n-l-efl with upanel
[09:26] <ogra_> pitti, not sure how well that works, i havent tried upanel yet
[09:26] <ogra_> gnome-panel is definately to heavyweight though which brought up the minimal panel idea at UDS
[09:26] <ogra_> afaik ted is working on it already
[09:27] <pitti> isn't that by and large the panel that we see in unity already?
[09:27] <pitti> i. e. which is just an indicator container?
[09:27] <ogra_> pitti, afaik that still uses a lot of gnome libs
[09:27] <pitti> ah, I see
[09:27] <ogra_> we want to cut down memory footprint and startup speed
[09:28]  * ogra_ has to move rooms at LT now ... see you
[09:28] <pitti> right, just gtk, dbus, and libappindicator would be great
[09:28] <ogra_> yepp
[09:30] <seb128> pitti, ogra_: the issue with unity is not the depends, it's the graphical 3d requirement
[09:31] <pitti> seb128: but that would only go for the launcher, I suppose, not for upanel itself?
[09:31] <seb128> ?
[09:31] <pitti> I mean, upanel certainly doesn't need 3D, does it?
[09:31] <seb128> no, I meant unity does
[09:31] <seb128> both the panel and the launcher
[09:32] <seb128> that's why they need a stock gtk version
[09:32] <didrocks> urgh, seems like I was disconnected…
[09:32] <seb128> didrocks, no you are not
[09:32] <seb128> didrocks, you didn't quit the channel at least
[09:32] <didrocks> did you received? 10:26:40 didrocks | pitti: go-home-applet and window-picker should be ported to it so
[09:32] <didrocks> 10:27:34 didrocks | and upanel is rendered under mutter, not sure how this behave under a 2D driver
[09:33] <seb128> no
[09:33] <didrocks> (and then, I recevied your last sentend "they need a stock gtk version"
[09:33] <didrocks> so, my server was still connected, but not my laptop
[09:33] <didrocks> and as it didn't say "heh, I quit", I don't have the backlog
[09:34] <seb128> didrocks, you didn't miss anything, ogra just said he had to move rooms
[09:34] <didrocks> seb128: oh ok, he didn't answered if I can add them for armel only now?
[09:34] <didrocks> in any case, we have to work on the fallback system again
[09:35] <seb128> didrocks, when did you drop from the channel?
[09:36] <didrocks> seb128: it's ok, I'm reading the log from my bip server now
[09:36] <seb128> ok
[09:36] <seb128> I was going to copy you the log
[09:37] <didrocks> seb128: that's fine, thanks :)
[09:38] <didrocks> yeah, I confirm the upanel can't work without mutter, that's why it can't be used for -efl
[09:39] <didrocks> and window-pickler/go-home-applet are applets, so, don't work (they will need to be rewriten too for the stock gtk bar)
[10:28] <pitti>   * Added unity to netbook [armel]
[10:28] <pitti> didrocks: ^ ??
[10:29] <didrocks> pitti: yeah, some armel card support 3D driver (as we had netbook-launcher working on them)
[10:29] <didrocks> pitti: so, having a fallback plan, as with netbook-launcher is in range, but won't happen before alpha3
[10:30] <didrocks> yesterday, unity wasn't on armel as the version FTBFS
[10:31] <pitti> didrocks: ah, good to know; it just didn't look deliberate after the discussion from above
[10:31]  * pitti hugs didrocks
[10:31] <didrocks> it was deliberate :)
[10:31]  * didrocks hugs pitti
[10:32] <didrocks> but I would prefer a better fallback solution than the one I added to netbook-launcher, we discussed a little about it with asac
[10:32] <didrocks> we'll figure out
[11:08] <mdz> where was the Mozilla maintenance change announced? I'm looking for a URL to link to
[11:09] <mdz> ah, found it: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2010-June/000719.html
[11:09] <mdz> seb128: support != maintenance :-)
[11:10] <seb128> mdz, I copied the blueprint title ;-)
[11:10] <seb128> but right
[12:00] <pitti> seb128: hm, something confuses the hell out of me
[12:00] <pitti> Package: gvfs
[12:00] <pitti> Depends: [...] libgvfscommon0 (>= 1.1.7)
[12:00] <pitti> but libgvfscommon0 is 1.6.1-0ubuntu1build1
[12:00] <pitti> (on lucid, anyway)
[12:00] <pitti> just got a report about a broken upgrade due to that
[12:00] <pitti> but how did that _ever_ work and doesn't cause complete uninstallability?!?
[12:01] <pitti> argh, ignore me
[12:01] <pitti> 1.7.1 != 1.1.7
[12:01] <chrisccoulson> heh ;)
[12:01] <chrisccoulson> i was just thinking that
[12:01] <pitti> so why was it removed for that guy..
[12:01]  * pitti asks
[12:01] <pitti> *brown paperbag*, sorry for the onise
[12:07] <rodrigo_> hi
[12:07] <rodrigo_> is there anything wrong in this uscan line:
[12:07] <rodrigo_> http://download.gnome.org/sources/tomboy/([0-9.]+)/tomboy-([0-9.]+)\.tar\.gz
[12:07] <rodrigo_> bzr bd... doesn't seem to find the 1.2.1 tarball, which is there
[12:10] <rodrigo_> oh, I get another error before that -> dh: unable to load addon quilt: Can't locate Debian/Debhelper/Sequence/quilt.pm
[12:10] <rodrigo_> which package does this file come from?
[12:12] <asac> rodrigo_:
[12:12] <asac> pkg -S /usr/share/perl5/Debian/Debhelper/Sequence/quilt.pm
[12:12] <asac> quilt: /usr/share/perl5/Debian/Debhelper/Sequence/quilt.pm
[12:13] <asac> dpkg -S /usr/share/perl5/Debian/Debhelper/Sequence/quilt.pm
[12:13] <asac> ;)
[12:13] <rodrigo_> hmm, I have it installed, it seems
[12:13] <rodrigo_> ah, no, I don't :)
[12:13] <asac> lol
[12:14] <rodrigo_> but it still can't find the tarball :(
[12:16] <alf__> didrocks: Hi! Did you get a chance to look at my experimental clutter egl packaging?
[12:17] <didrocks> alf__: that's next on my list :)
[12:17] <alf__> didrocks: great, thanks :)
[12:18] <didrocks> you're welcome
[12:18] <asac> am i here?  ... damn connection - this week is clearly bad
[12:18] <alf__> asac: you are
[12:18] <asac> ah ;)
[12:18] <asac> there i am
[12:18] <chrisccoulson> asac - i can't see you ;)
[12:18] <seb128> pitti, sorry I was at lunch, seems you sorted it by now ;-)
[12:18] <asac> chrisccoulson: i think thats a good thing ;)
[12:19] <asac> i try to not look in a mirror right now ;)
[12:19] <chrisccoulson> lol
[12:19] <seb128> rodrigo_, weird
[12:19] <seb128> hey chrisccoulson, asac, glatzor
[12:20] <rodrigo_> seb128, I guess it's getting to an out-of-date mirror?
[12:20] <chrisccoulson> hey seb128 - how are you?
[12:20] <asac> hi seb128
[12:20] <seb128> rodrigo_, you get no clue in the log?
[12:20] <seb128> chrisccoulson, I'm fine thanks, what about you?
[12:21] <chrisccoulson> yeah, good thanks. i'm a bit sleepy today though
[12:21] <asac> alf__: so you said that the es11 and es22 lib is supposed to be binary compatible?
[12:21] <seb128> worked late again?
[12:21] <asac> if igts not we should ship it with different soname
[12:21] <asac> otherwise i dont see why we need to have different test packages for them
[12:21] <chrisccoulson> i worked fairly late last night, fixing the few remaining issues with the hardy updates
[12:21] <rodrigo_> seb128, no, just that it can't get the tarball from that url
[12:22] <seb128> rodrigo_, is your debian dir somewhere online?
[12:22] <seb128> chrisccoulson, oh, ok, did you fix the font rendering one as well?
[12:22] <rodrigo_> seb128, no, it's just lp:ubuntu-desktop/tomboyubuntu branched, and added a patch to debian/patches
[12:22] <chrisccoulson> seb128 - yeah, that's fixed too
[12:23] <rodrigo_> seb128, I can push it if you want
[12:23] <seb128> rodrigo_, would be useful yes
[12:23] <rodrigo_> ok
[12:23] <seb128> chrisccoulson, well done!
[12:23] <chrisccoulson> thanks :)
[12:24] <alf__> asac: Yes they are supposed to be compatible, so yes we could just have one eglx test package
[12:24] <asac> alf__: right. imo we should have that.
[12:24] <alf__> asac: I am 99.9% sure of this, that is why I have two different test packages now
[12:25] <asac> alf__: you can compare symbols files
[12:25] <rodrigo_> seb128, https://code.launchpad.net/~rodrigo-moya/ubuntu/maverick/tomboy/proxy-settings
[12:25] <asac> for the es11 and es22 ... are those identical?
[12:25] <alf__> asac: right, will do
[12:25] <asac> alf__: if we could get rid of it that would be great. also i think the -tests package shouldnt start with lib...
[12:25] <asac> we usually only use lib... prefix for libs
[12:25] <Sarvatt> mutter will be usable with no hardware acceleration in MM at least :)
[12:26] <alf__> asac: ok
[12:26] <asac> alf__: so we could just ship "cutter-eglx-tests"
[12:26] <asac> or i guess
[12:27] <asac> clutter-1.0-eglx-tests
[12:27] <asac> and clutter-1.0-common-tests
[12:27] <asac> and clutter-1.0-glx-tests
[12:27] <alf__> asac: or clutter-glx-1.0-tests, clutter-eglx-1.0-tests?
[12:27] <asac> for me the 1.0 refers to the clutter-1.0 source package
[12:28] <asac> but not sure
[12:28] <asac> get more opinions ;) ... from didrocks and seb128 and others
[12:28] <Sarvatt> asac: mesa is waiting to go through NEW  in debian, I patched it up to work with libdrm 2.4.21 we'll have at the same time so it shouldn't be long. in the process of redoing the mesa packaging so things work when we switch to 7.9 in a few weeks that is very different for the egl/gles stuff
[12:28] <asac> Sarvatt: cool. did you just keep intel1 enabled for Archi: any ?
[12:29] <asac> the package raof upped had a problem there ... imo intel1 should just be any
[12:29] <Sarvatt> yeah until someone fixes plymouth :(
[12:29] <asac> thats fine. i dont see why just intel1 should be disabled on non intel archs ;)
[12:29] <Sarvatt> it makes no sense to be any but it needs to be any because plymouth needs it on all arches..
[12:29] <Sarvatt> because its just wasting space on non intel arches :)
[12:29] <asac> so it makes sense ;)
[12:30] <asac> yeah well. but afaik we also ship X drivers for hardware that will probably never exist for arm or sparc deployments ;) ... so its in line
[12:31] <seb128> rodrigo_, I think it looks for the newest version and find only the 1.3 serie
[12:31] <Sarvatt> they aren't always going to be installed actually wasting space though unlike libdrm-intel1 :)
[12:31] <rodrigo_> seb128, oh, why? it should be looking in the 1.2 directory, right?
[12:31] <seb128> rodrigo_, dunno
[12:31] <seb128> rodrigo_, you don't specify a serie in the watch it uses the newest
[12:32] <seb128> rodrigo_, get the lucid tarball?
[12:32] <Sarvatt> swrast in mesa 7.9 can run compiz and mutter though so that'll all be usable on arm
[12:32] <seb128> rodrigo_, if you have a lucid-update deb-src it will just work
[12:32] <rodrigo_> seb128, well, this is for maverick, does maverick have the 1.3 version already?
[12:32] <rodrigo_> no, 1.2.1
[12:33] <seb128> rodrigo_, no, but it might be a bug in the download code which is fixed in maverick and not lucid
[12:33] <rodrigo_> seb128, I'm on maverick
[12:33] <seb128> oh
[12:34] <seb128> well dunno
[12:34] <rodrigo_> seb128, can I just download the tarball and place it somewhere so that it doesn't try to get it?
[12:34] <seb128> it's a bug
[12:34] <seb128> you can
[12:34] <seb128> if you have a maverick deb-src it will just work
[12:34] <seb128> either make the watch point to the serie you use
[12:35] <seb128> or download the tarball yourself
[12:35] <seb128> or configure an ubuntu deb-src so it uses it
[12:36] <rodrigo_> so, place it in the parent dir?
[12:36] <seb128> yes
[12:37] <seb128> wget http://archive.ubuntu.com/ubuntu/pool/main/t/tomboy/tomboy_1.2.1.orig.tar.gz
[12:39] <rodrigo_> ok, that works, thanks!
[12:39] <didrocks> asac: you already have something to work on with asac's comment, don't you? I would just say in addition to this: don't change the packaging too much before ensuring debian will take it (like dh5 -> dh7, remove of debian/control.in and using debian quilt format 3)
[12:39] <didrocks> upss alf__ ^^
[12:40] <asac> didrocks: well.
[12:40] <asac> didrocks: current package i cdbs
[12:40] <asac> so if it moves somewhere it should move to dh7
[12:40] <asac> directly
[12:40] <didrocks> asac: ok, is there a discussion with the DD responsible for that package? or do we want to diverge forever?
[12:41] <slomo> seb128: who was the guy with the gtk+3.0 package again? did you take a look at his package already?
[12:41] <asac> didrocks: our goal should be to get the same features packaged in debian so we can sync at some point. we should start that discussion. if they want to go for cdbs we can work with them on that still and drop our packaging if it comes to it
[12:42] <rodrigo_> seb128, well, that patch does not apply to 1.2 :(
[12:42] <asac> if they want to adapt our packaging, even better ...
[12:42] <rodrigo_> seb128, can I upgrade to 1.3?
[12:42] <asac> having a patch like this maintained as a downstream diff is painful in anyway; so either they adapt our features or we will be alone imo
[12:42] <slomo> seb128: this here? https://launchpad.net/ubuntu/+source/gtk+3.0
[12:42] <didrocks> asac: agreed, just to ensure that the discussion has already began to have an easier adoption :)
[12:42] <seb128> rodrigo_, no
[12:43] <rodrigo_> seb128, ok
[12:43] <asac> didrocks: hoped you opt in to that  ;)
[12:43] <seb128> slomo, right, the ppa there, ricotz
[12:43] <slomo> seb128: thanks
[12:43] <seb128> slomo, he's on #ubuntu-devel
[12:43] <rodrigo_> seb128, are you waiting for something before updating the 2.31/ tomboy 1.3?
[12:43] <asac> didrocks: by ensuring you are happy with the direction it might be easier to our stuff upstreamed
[12:43] <asac> e.g. we are one time contributors, while you maintain a constant relationship ;)
[12:43] <asac> (hopefully)
[12:44] <seb128> rodrigo_, we don't plan to update to 2.31 this cycle
[12:44] <asac> anyway, if not, we will ensure htis comunication happens
[12:44] <rodrigo_> seb128, ah, why?
[12:44] <didrocks> asac: great :)
[12:44] <seb128> rodrigo_, we don't want gtk3 in the default installation, not reliable schedule, and the transition will take over a cycle
[12:45] <didrocks> alf__: can you do asac's changes and then ping me back? I will do a closer review
[12:45] <asac> cool
[12:45] <rodrigo_> seb128, hmm, ok, we'll have to backport the patch to 1.2 then
[12:45] <seb128> rodrigo_, it conflicts with gtk2 at runtime so we would need to duplicate lot of sources to have gtk2 and gtk3 builds
[12:45] <rodrigo_> right
[12:45] <seb128> rodrigo_, which is an issue for cds and a non trivial transitions
[12:46] <seb128> rodrigo_, we plan it for next cycle, gtk3 will go to universe this cycle
[12:46] <rodrigo_> seb128, ok, good to know, we'll backport the patch then
[12:46] <seb128> rodrigo_, if the new tomboy will not depends on gtk3 we can update though
[12:46] <rodrigo_> seb128, hmm, don't know, I'll check
[12:46] <seb128> rodrigo_, you might want to try to figure what upstream wants to do
[12:46] <rodrigo_> yes
[12:46] <seb128> thanks
[12:47] <seb128> slomo, I didn't check his work no
[12:54] <alf__> asac, didrocks: It seems that clutter es11 an es20 are not compatible after all, at least symbol-wise... unless the differing symbols are internal and exposed by error. I'll check with upstream...
[12:55] <asac> alf__: what are those symbols?
[12:55] <asac> cogl_ stuff?
[12:56] <alf__> asac: yes
[12:56] <alf__> asac: eg cogl_fixed_vertex_shader_*
[12:58] <asac> thats coming from cogl/driver ... with some luck thats just internal and can be hidden
[12:59] <asac> alf__: so check with upstream
[13:01] <asac> alf__: you could try to add #pragma GCC visibility push(hidden)
[13:01] <asac> to the start
[13:01] <asac> and
[13:01] <asac> #pragma GCC visibility pop
[13:01] <asac> at the bottom of all .h files in cogl/cogl/driver/*/*.h
[13:01] <asac> well start == after all other includes
[13:01] <alf__> asac: sure, I am waiting for upstream to confirm
[13:02] <asac> right. but if tests etc. stil build fine with that it should be ok
[13:02] <asac> (and if the symbols are really gone ;))
[13:08] <om26er> didrocks, Hi! the latest upload of ubuntu-netbook-unity-default-settings in UNE ppa removed Unity session from GDM list, is that expected?
[13:08] <didrocks> om26er: hum, no, it's not
[13:09] <didrocks> apt-cache policy ubuntu-netbook-unity-default-settings && dpkg -L ubuntu-netbook-unity-default-settings
[13:09] <didrocks> I've tested the migration on my netbook and it worked
[13:10] <om26er> hmm, I actually downgraded and then it worked
[13:10] <didrocks> om26er: can you try upgrade to latest version and dpkg -L, please?
[13:10] <didrocks> I confirm there that the session is installed
[13:11] <alf__> asac: although the correct way for a library would be to for everything hidden by default and push(default) explicitly for public symbols...
[13:11] <alf__> asac: but such is life :)
[13:11] <om26er> didrocks, sure brb
[13:13] <om26er> didrocks, upgraded and its still there.
[13:14] <om26er> mean, now unity session works
[13:14] <didrocks> om26er: hum, that's weird, unfortunately, doesn't seem it's reproduceable so :)
[13:14] <didrocks> seems we are all good so :)
[13:14] <didrocks> s#:)#:/
[13:15] <om26er> didrocks, great, Thanks :)
[13:15] <didrocks> om26er: you're welcome
[13:16] <didrocks> om26er: and thanks for testing unity and your bug triaging work on UNE btw :)
[13:18] <asac> alf__: true.
[13:25] <asac> didrocks: so how do we do mutter with gles?
[13:25] <asac> e.g. how can i test/try that?
[13:25] <asac> guess i need to spin that aganst the egl clutter ... but what do i do with that then?
[13:25] <didrocks> asac: I would think, take the package in maverick, link against gles in a ppa, and launch it with mutter --replace
[13:26] <asac> didrocks: you mean i could run that in my -efl sessioN?
[13:26] <asac> what would happen :)
[13:26] <didrocks> asac: with a device that doesn't support glx, right?
[13:27] <asac> yes
[13:27] <didrocks> so, yes, you can just run that in you -efl session
[13:27] <didrocks> it will replace metacity by mutter
[13:27] <asac> didrocks: so we need mutter + unity built against gles/egl i guess?
[13:27] <didrocks> you can see it really running as it have some little effects
[13:27] <asac> is there anything else we need to prepare to test the full stack?
[13:28] <didrocks> asac: right, but I think beginning with mutter only is the first step to see how it behaves
[13:28] <didrocks> no, mutter and unity is everything you need
[13:28] <asac> didrocks: sure. however, plan is to get the full stack packaged and then let vendors and upstream developers collaborate on fixing things
[13:28] <didrocks> all the remaining things are just library without any rendering
[13:28] <asac> just want to undersatnd how much work this will be on packaging side
[13:28] <asac> but seems we are quite close with just unity and mutter missing
[13:29] <didrocks> asac: of course, you will need the other librairies, but nothing special for egl
[13:29] <om26er> didrocks, its reproducable on the live cd(lucid) and also on new install( where I first got the problem). installing the previous version of *-default-settings and then upgrading works
[13:29] <didrocks> asac: you can depend on the lucid UNE ppa
[13:29] <asac> sure. but those are hopefully avaiable
[13:29] <asac> didrocks: well. i need to copy this stuff to the native ppa i guess ... or is lucid UNE with arm ?
[13:29] <asac> but i will check ;)
[13:30] <asac> didrocks: do you have url for that lucid UNE ppa at hand?
[13:30] <didrocks> om26er: ubuntu-netbook-unity-default-settings is the package having all the dep, this one have to be installed
[13:30] <didrocks> asac: https://launchpad.net/~canonical-dx-team/+archive/une/
[13:30] <asac> thx
[13:31] <asac> hmm. what is plasma-* stuff doing there ;)
[13:31] <didrocks> om26er: the instruction to install unity is now: 1 - add the UNE ppa, 2- install ubuntu-netbook-unity-default-settings
[13:31] <asac> is that ppa state to be considered stable?
[13:31] <didrocks> asac: yeah, dx team plays with the ppa too
[13:31] <didrocks> asac: right, for unity stuff at least
[13:31] <asac> e.g. could it be that it doesnt work at all?
[13:31] <didrocks> I upgrade it once a week
[13:32] <didrocks> no, it's working, I'm trying it
[13:32] <asac> didrocks: do you know out of your head what stuff i need from there that doesnt do rendering?
[13:32] <didrocks> asac: sure, one sec
[13:32] <asac> coool thats helpful ;)
[13:33] <didrocks> asac: bamf, dee, libunity-misc, ubuntu-netbook-unity-default-settings, unity-asset-pool
[13:33] <didrocks> asac: then, you will need for rendering: clutk, mutter and unity
[13:36] <asac> didrocks: right. let me copy all those for now and then we improve the rendering bits
[13:37] <didrocks> asac: ok, so you will stay on that version for now, right?
[13:37] <didrocks> (it's quite fresh, from yesterday's evening :))
[13:37] <asac> if there are updates coming soon we should wait for i can do that
[13:37] <asac> but in the end i hope it doesnt make much of a difference; we can rebase the packaging changes required
[13:38] <asac> didrocks: so the gtk menuproxy thing isnt needed?
[13:38] <didrocks> asac: no, this new version is only if you want your menu in the panel
[13:39] <didrocks> as indicator-datetime which is installed by default in UNE, I don't think you want to bother with that for now
[13:39] <om26er> didrocks, on today's(20100611) UNE daily build there is only gnome session which might make it the same bug?
[13:40] <asac> ok lots of things spinning now: https://edge.launchpad.net/~asac/+archive/armel1/+packages
[13:40] <asac> stay tuned
[13:41] <didrocks> om26er: I don't understand, did you try what I told you on a fresh install? 1 - add the ppa ; 2 - install ubuntu-netbook-unity-default-settings? that's how unity should be installed
[13:41] <didrocks> asac: and be afraid? ;)
[13:41] <asac> yeah!!!
[13:42] <om26er> didrocks, yes exactly
[13:42] <didrocks> om26er: and then, you don't get the unity session?
[13:42] <om26er> didrocks, no
[13:43] <didrocks> hum, let me try
[13:44] <om26er> oh,, installing unity dont install default-settings?
[13:45] <didrocks> om26er: that's what I'm telling you from 15 minutes
[13:45] <didrocks> :)
[13:45] <didrocks> for*
[13:45] <om26er> oh
[13:46] <didrocks> in maverick, ubuntu-netbook is the metapackage installing unity and the default-settings (as before, it was installing netbook-launcher and the default-settings)
[13:46] <didrocks> of course, we don't have a metapackage in the ppa
[13:46] <didrocks> so, it's the default-settings which contains the session which also have those deps
[13:47]  * didrocks setup a wiki page
[14:02] <pitti> hm, with yesterday's -proposed updates the keyboard indicator now has a different font and looks hideously blurry
[14:02] <didrocks> https://wiki.ubuntu.com/DesktopTeam/Unity
[14:11] <seb128> pitti, right
[14:11] <seb128> pitti, it used to use cairo directy and is now pango rather...
[14:13] <pitti> hm, why was that done in an SRU? appending an "1" for previously identical layouts doesn't seem to need a change in the font rendering, just in the displayed strings?
[14:13] <seb128> no
[14:13] <seb128> but he used cairo directly because he didn't know how to do otherwise before
[14:14] <pitti> ah, so it's an independent change
[14:14] <seb128> but cairo has limitations
[14:14] <seb128> it doesn't respect some of the pango rendering and font settings
[14:14] <seb128> and there was crashers in the code
[14:14] <asac> didrocks: mutter seems to not like us using clutter 1.3.x ;) http://launchpadlibrarian.net/50131541/buildlog_ubuntu-lucid-armel.mutter_2.29.0-1ubuntu1dx3%2Br3435_FAILEDTOBUILD.txt.gz
[14:14] <asac> didrocks: guess i have to hack that out
[14:14] <seb128> upstream argue that the new code is better and has less bugs and that we should take it
[14:15] <didrocks> asac: more than possible, it's the first time having a new clutter is quite painful
[14:15] <didrocks> seb128: the new mutter?
[14:15] <seb128> didrocks, no, libgnomekbd
[14:15] <didrocks> oh sorry seb128, drop into the discussion
[14:15] <seb128> didrocks, I'm talking with pitti there ;-)
[14:15] <didrocks> :)
[14:16] <asac> didrocks: so you think i should get rather new mutter from dev branch packagesd? or try to hack out the configure test?
[14:16] <asac> the abi/api is compatible
[14:16] <seb128> pitti, well I find the rendering a bit less nice on some layouts as well but upstream said we should take the new version since it fixes some crashers and is the right way to do it
[14:17] <didrocks> asac: maybe try with ours for now. We are sure that unity is working with it
[14:17] <pitti> seb128: ack
[14:18] <asac> didrocks: what do you mean with "ours"?
[14:18] <didrocks> asac: the current version in the ppa (with our patch)
[14:18] <asac> we cant use the current clutter version ... that doesnt support egl/gles2 properly
[14:18] <didrocks> asac: you talked about mutter*
[14:19] <didrocks> "get rather new mutter"
[14:19] <asac> yeah. ok
[14:19] <asac> strange that it complains
[14:19] <asac> i see it uses pkg-config --at-least 1.2.0 clutter-1.0
[14:20] <didrocks> so, it should work…
[14:20] <milanbv> git mutter has in configure.in
[14:20] <milanbv> CLUTTER_VERSION=1.2.0
[14:20] <asac> yes, but then tries to use --atleast-version
[14:20] <milanbv> yeah
[14:20] <asac> and we have 1.3.x
[14:23] <asac> hmm. did upstream move to clutter.pc from clutter-1.0.pc? or is that a packaging regression
[14:23] <asac> alf__: ^^
[14:26] <asac> hmm ok thats the upstream buld system renaming
[14:32] <asac> alf__: libclutter-1.0-dev lacks depends on the libjson thing
[14:32] <asac> add that to the list of changes ;)
[14:32] <alf__> asac: ok, will fix
[14:35] <pitti> dobey: maverick u1> it was/is probably stuck in NEW
[14:38] <dobey> pitti: hrmm. don't know, as i haven't gotten any e-mail about it. i just know it's built and lp says 'pending publication' for all archs
[14:39] <dobey> pitti: but if you can kick it into 'published' the world will love you :)
[14:39]  * kenvandine would love you :)
[14:39] <kenvandine> can't get files synced :/
[14:40] <lool> Hmm second time I get http://paste.ubuntu.com/448252/ in a couple of days
[14:41] <pitti> dobey: which source package was that? (sorry, I already deleted the bug mail, and only thought about telling you afterwards)
[14:41] <dobey> pitti: ubuntuone-client
[14:41] <pitti> ah, ubuntuone-client is in NEW
[14:41] <pitti> protobuf, too
[14:41] <pitti> for libsyncdaemon
[14:41] <dobey> ah, because of the new binary package?
[14:42] <pitti> right
[14:42]  * pitti sends it to main and accepts
[14:43] <dobey> pitti: thanks!
[14:43] <kenvandine> awesome
[14:44] <kenvandine> i'll finally be able to see if the music store is fixed :)
[14:44] <pitti> shoulld be published in 75 mins
[14:44] <pitti> protobuf accepted as well, in case that's urgent
[14:44] <kenvandine> does anyone know what is causing this mouse jiter?
[14:45] <kenvandine> in maverick...
[14:45] <kenvandine> started happening to me yesterday, and last night bratsche saw it too
[14:45]  * kenvandine doesn't know what package to look for bugs on :)
[14:46] <seb128> kenvandine, try #ubuntu-x
[14:46] <dobey> my mouse was jittery when i 'came into work' today, and went to unlock the screen
[14:46] <seb128> likely a new xorg issue
[14:46] <dobey> but i'm on lucid
[14:46] <kenvandine> dobey, weird....
[14:46] <dobey> and i think it was due to chrome eating up my RAM
[14:46] <kenvandine> oh... that isn't my problem
[14:46] <dobey> chrome was at 30% usage, and firefox at like 25%
[14:46] <dobey> fun times...
[15:20] <kenvandine> pitti, can you look at https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-ubuntu-one-file-sink-ui-changes
[15:21] <kenvandine> pitti, and see if you can tell why it isn't showing up on the ubuntuone-hackers burndown?
[15:45] <Sarvatt> RAOF: are you around? nvidia-* is still providing abi 6 and leaving people with it installed in a broken state, we really should just do a no change rebuild if you dont have the apport stuff ready
[15:54] <Sarvatt> tseliot: can you upload no change rebuilds of nvidia-graphics-drivers* for maverick to unbreak people's systems? :) it's been 5 days now, they seem to be getting antsy :)
[15:55] <tseliot> Sarvatt: X abi change? sure
[15:56] <Sarvatt> yeah, 173 and under don't work without IgnoreABI still but current is fine, at least if the others were rebuilt the breaks: xserver-xorg-video-6 on xserver-xorg-core wouldn't be totally screwing people over
[15:57] <seb128> kenvandine, didrocks: could one of you do the empathy stable update as a sru?
[15:57] <kenvandine> didrocks, do you have time?  i am feeling very behind today...
[15:57] <Sarvatt> tseliot: thanks a ton!
[15:57] <tseliot> np
[15:57] <didrocks> kenvandine: can do, but it will be in a couple of hour, if not more…
[15:58] <didrocks> kenvandine: I want to release Quickly 0.4.3 today
[15:58] <didrocks> everytime it's postponed…
[15:58] <kenvandine> didrocks, ok... that is probably sooner than i could... i still haven't worked on anything i planned to work on today
[15:58] <seb128> didrocks, kenvandine: next week works as well no hurry
[15:58] <kenvandine> ok
[15:58]  * didrocks tries to do thing he couldn't for a long time
[15:58] <didrocks> so, next week, perfect :)
[15:58] <kenvandine> hehe :)
[15:59] <seb128> thanks
[15:59] <seb128> ccheney, there?
[15:59]  * kenvandine grumbles about tomboy not working...
[15:59] <seb128> ccheney, do you still plan to get the dictionnary and cifs bugs fixed for .1?
[16:04] <rodrigo_> where is there a list of packages in main?
[16:06] <rodrigo_> seb128, ^
[16:06] <seb128> why do you need that?
[16:06] <seb128> there is many way to check where a package is
[16:06] <seb128> or you can look to /var/lib/apt/lists
[16:07] <seb128> the indexes from apt are there
[16:07] <seb128> you can grep in the main one if you want
[16:07] <rodrigo_> ah, ok
[16:07] <rodrigo_> seb128, I'm going to do a MIR for MS office :D
[16:07] <seb128> lol
[16:08] <rodrigo_> seb128, no, seriously, we need python-libproxy for u1-client
[16:08] <rodrigo_> and want to check if libproxy is in main
[16:08] <seb128> it's in universe
[16:08] <seb128> but libproxy is in main
[16:08] <seb128> so you can depends on python-libproxy
[16:08] <seb128> we will promote it once something do
[16:09] <seb128> ie the source is in main, the python binary is not because nothing use it
[16:09] <rodrigo_> seb128, ah, cool, so just need a MIR for python-libproxy
[16:09] <seb128> no
[16:09] <seb128> the source is in main
[16:09] <seb128> you don't need anything
[16:09] <seb128> just ping me when you upload something which use it
[16:10] <rodrigo_> seb128, ah, cool, dobey already uploaded a u1-client package that uses it
[16:10] <rodrigo_> that's how we found out :)
[16:10] <seb128> ok, let me promote it
[16:14] <rodrigo_> seb128, thanks
[16:14] <rodrigo_> dobey, problem solved! :D
[16:15] <dobey> well partially
[16:15] <kenvandine> dobey, yay... syncdaemon is starting :)
[16:15] <dobey> unless it got pulled in by ${python:Depends} anyway
[16:25] <rodrigo_> seb128, so, tomboy will not depend on gtk3, until gtk-sharp does the move, and tomboy would keep working ok with both gtk-sharp bindings
[16:25] <rodrigo_> seb128, sandy from tomboy says that he plans to keep supporting old distros, so can I then upgrade to 1.3?
[16:25] <seb128> yes
[16:26] <rodrigo_> seb128, if for some reason there is a gtk3 dep added, we can backport easily, right?
[16:26] <rodrigo_> seb128, not that it's going to happen, but just inc ase
[16:26] <seb128> backport what?
[16:26] <rodrigo_> backport to 1.2
[16:26] <rodrigo_> the package
[16:26] <seb128> get the code to still work on gtk2?
[16:26] <seb128> or, downgrade
[16:26] <seb128> yes we could
[16:26] <rodrigo_> no, no
[16:26] <rodrigo_> upload the 1.2 version
[16:26] <rodrigo_> ok
[16:27] <seb128> kenvandine, can you do a quick dx, os update in the meeting when it's desktop turn?
[16:28] <kenvandine> release meeting?
[16:28] <kenvandine> ok, dbarth usually does that
[16:28] <kenvandine> did he update the wiki page?
[16:30] <seb128> kenvandine, it's our turn now
[16:30] <kenvandine> ok
[16:31] <seb128> davidbarth, ^
[16:31] <seb128> davidbarth, not joining the release meeting for dx update?
[16:31] <kenvandine> he might be in another meeting... i can try to cover it :)
[16:31] <kenvandine> didn't prepare... but should know
[16:31] <kenvandine> just point to me when it is time
[16:32] <kenvandine> unless davidbarth pipes up :)
[16:34] <seb128> kenvandine, sorry for the short notice but don't worry it's early in the cycle
[16:34] <kenvandine> :)
[16:34] <davidbarth> what's that
[16:34] <seb128> kenvandine, I've to admit I forgot those meetings where starting again today so didn't prepare either
[16:34] <davidbarth> i'm here in the meeting
[16:34] <davidbarth> my turn?
[16:34] <kenvandine> davidbarth, yeah... i covered for now... but you can take over :)
[16:34] <davidbarth> https://wiki.ubuntu.com/DesktopExperienceTeam/MaverickReleaseStatus
[16:35] <seb128> davidbarth, seems kenvandine covered for you, sorry I messed up I checked for "dbarth"
[16:35] <kenvandine> :)
[16:35] <seb128> davidbarth, ok, your turn ;-)
[16:43] <davidbarth> kenvandine, seb128: thanks for covering for me, i was just finishing putting the report with all the links
[16:44] <seb128> davidbarth, np, sorry I checked the wrong nickname there ;-)
[17:05] <rickspencer3> didrocks, congrats on releasing the latest version of your book!
[17:05] <didrocks> rickspencer3: heh, thanks, I was released during UDS, but I just didn't have the time to blog about it :)
[17:06] <didrocks> (and yes, it was finished BEFORE UDS, I didn't write it there :p)
[17:06] <didrocks> just the last "read and fix rounds"
[17:21] <seb128> pitti, still there?
[17:22] <pitti> yes, apt is naughty
[17:22] <seb128> pitti, ok, I've sponsored appmenu-gtk for kenvandine, it's pretty trivial, not sure if you would have a few minutes to NEW review it before eow?
[17:27] <pitti> can do
[17:27] <seb128> pitti, if that's not today that's fine don't feel forced to do it
[17:28] <seb128> pitti, on monday works as well
[17:28] <seb128> I will upload an indicator-appmenu as well in a bit
[17:30] <pitti> seb128: I can't do it on Monday
[17:31] <pitti> because it's not in NEW
[17:31] <seb128> hmu?
[17:31] <seb128> oh
[17:31] <pitti> that's because it's in accepted :-P
[17:31]  * seb128 hugs pitti
[17:31] <seb128> that was quick ;-)
[17:31] <seb128> ^
[17:31] <kenvandine> hehe
[17:31] <kenvandine> :)
[17:32] <pitti> next time, flushing the changelog would be nice
[17:32] <seb128> pitti, do we have a policy about that? I was already wondering for the unity uploads
[17:33] <seb128> pitti, the indicator-appemenu is in NEW as well
[17:33] <seb128> pitti, if you still feel like reviewing one
[17:33] <pitti> policy> not that I know of, it just looks odd for a new pacakge
[17:33] <seb128> I guess that would make jcastro and kenvandine happy to get that in universe today
[17:33] <seb128> I will bin-NEW later
[17:33] <pitti> oh, I sent appmenu-gtk to main
[17:33] <pitti> it's trivial and our own breed
[17:33] <kenvandine> oh... thx... i'll do the MIR today then :)
[17:33] <pitti> we don't need it in main?
[17:33] <kenvandine> we do
[17:34] <jcastro> it would!
[17:34] <kenvandine> pitti, should i still do an mir bug?
[17:34] <pitti> well, if you wish
[17:34] <kenvandine> indicator-appmenu needs to go to main as well
[17:34] <pitti> but the point of MIRs is mainly to review imported and thirrd-party packages; I already reviewed the packaging now, and there's little question about upstream and support
[17:35] <kenvandine> ok
[17:36] <pitti> kenvandine: but for a paper trail, a MIR bug might be good, yes; not sure whether other MIR team members share my opinion about this :)
[17:36] <kenvandine> pitti, already done
[17:37] <pitti> cool, thaks
[17:37] <pitti> kenvandine, seb128: hm, no debian/compat in indicator-appmenu?
[17:37] <kenvandine> pitti, so if you want to resolve bug 592739
[17:37] <ubot2> Launchpad bug 592739 in appmenu-gtk (Ubuntu) "[MIR] appmenu-gtk (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/592739
[17:39] <pitti> ah, cdbs creates it on the fly with "5" if you don't have one, doesn't it?
[17:39] <pitti> kenvandine: done
[17:39] <seb128> pitti, yes, but that's a valid point, we should have one ideally
[17:40] <pitti> i-appmenu NEWed
[17:42] <seb128> pitti, you rock, thanks
[17:42] <seb128> jcastro, ^
[17:42] <jcastro> thanks pitti!
[17:42] <pitti> my pleasure
[17:43] <pitti> seb128: how was the release meeting?
[17:44] <kenvandine> pitti, bug 592743
[17:44] <ubot2> Launchpad bug 592743 in indicator-appmenu (Ubuntu) "[MIR] indicator-appmenu (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/592743
[17:44] <seb128> pitti, it went ok, not as well tidy that the end of cycle ones
[17:44] <seb128> pitti, ie, not so much specific points to track and no current r-m watching things
[17:45] <seb128> pitti, but it went ok otherwise ;-)
[17:45] <pitti> good
[17:45] <pitti> (except that no RM -> bad)
[17:45] <seb128> pitti, thanks for asking btw ;-)
[17:45]  * seb128 hugs pitti
[17:45] <pitti> I just wondered whether you have any troubles right now
[17:45] <pitti> with ReleaseStatus, etc.
[17:46] <pitti> and cracking the whip :)
[17:47] <chrisccoulson> heh, "Dear ubuntu-mozillateam-bugs! 80% Sale continues" from Best ViagraPharmacy Online
[17:47] <chrisccoulson> are these lists not moderated? ;)
[17:49]  * didrocks thinks that seb128 found too easily the whip :)
[17:49] <pitti> didrocks: gosh, all these wounds on your back!
[17:50] <didrocks> seeing that? it's terrible :p
[17:50] <seb128> pitti, no, I'm doing fine so far I think ;-) but good to think you are still around in case I've issues ;-)
[17:51] <seb128> didrocks, speaking of which and since you a still around, how busy are you tonight? ;-)
[17:51]  * didrocks runs away
[17:51]  * didrocks is already not there
[17:52] <didrocks> don't try even :-)
[17:52] <seb128> lol
[17:52]  * seb128 hugs didrocks
[17:52] <didrocks> seb128: more seriously, I will take one hour break, but still can do some stuff
[17:52]  * didrocks hugs seb128
[17:52]  * seb128 hugs pitti
[17:52]  * didrocks hugs pitti too
[17:52] <didrocks> (take care of the wounds)
[17:52] <seb128> didrocks, I was joking, enjoy your weekend, you should call it a week not take a break
[17:52]  * pitti hugs seb128 and didrocks
[17:53] <seb128> didrocks, you had a busy week and did great work
[17:53] <seb128> didrocks, nice to see unity landing so nicely in maverick and upgrade working without out
[17:53] <seb128> out -> issue
[17:53] <seb128> doh, tired ;-)
[17:53] <didrocks> seb128: well, tomorrow I have an uninteresting ubuntu party meeting all the afternoon, I can do some useful stuff meanwhile :)
[17:53] <didrocks> seb128: thanks :-)
[17:53] <seb128> didrocks, also thanks for making our workitems count catch up with the trend line
[17:53] <seb128> didrocks, you closed quite some bugs this week ;-)
[17:53] <didrocks> heh, that was a great target ^^
[17:54] <didrocks> seeing all this TODO -> DONE
[17:54]  * didrocks breathes
[17:54] <jcastro> didrocks: <3
[17:54] <seb128> didrocks, say hello to kinouchou and others from me
[17:54] <didrocks> seb128: sure, I will :)
[18:21] <pitti> hah, I bent apt to my will
[18:21] <pitti> have a nice weekend everyone!
[20:05] <didrocks> jcastro: hey
[20:05] <didrocks> jcastro: does the appmenu in lucid ppa works? On which package should I depend?
[20:06] <jcastro> Yes it does!
[20:06] <jcastro> didrocks: #ayatana please!
[20:14] <ccheney> seb128: i believe so, i'm off until jun 18 though, is there a pending .1 deadline?
[20:14]  * ccheney may have been looking at the wrong page but thought .1 was for late july
[20:20] <seb128> ccheney, hi, no hurry I was just checking they were still on your list
[20:25] <ccheney> seb128: yea, i am planning on doing a full 3.2.1 update on OOo, hopefully soon after i return from paternity leave
[20:25] <ccheney> seb128: i have quite a few SRUs to write up and verify at that time related to the update :)
[20:25] <ccheney> iirc somewhere around 30
[20:26] <seb128> ccheney, ok, as said no hurry, enjoy your time off work for now ;-)
[20:26] <seb128> ccheney, when is the new openoffice going to be there?
[20:27] <seb128> ccheney, I was just checking because those were on the rt list for the meeting today
[20:28] <ccheney> seb128: 3.2.1 is already released, but my MIRs are still waiting on doko to review from june 5
[20:28] <seb128> ok
[20:28] <ccheney> seb128: so the 3.2.1~rc hasn't been built yet for maverick
[20:28] <seb128> let's see that next week
[20:28] <seb128> it's weekend time for now
[20:28] <ccheney> once it has built everywhere and i can see i don't need to fix any other issues on various arch i will do an upload of the final version
[20:29] <ccheney> afaik the 3.2.1 i uploaded is essentially the same as final, just had to be voted on for approval
[20:29] <seb128> ok
[20:29] <ccheney> there are probably additional ooo-build fixes for it, but i pull those in for each new upload
[20:30] <seb128> ok
[20:30] <seb128> let's check when you are back to work
[20:30] <seb128> it's weekend time for me and you are not supposed to be working
[20:31] <ccheney> ok
[20:32] <ccheney> feeding the baby atm but will be around all week but lagged


[17:06] <annerajb> rsalveti, it failed saying something about symlinks failed but the first time it ran fine the second time is when i usually get that message so i think something may not be clearing up correctly
[17:07] <annerajb> rsalveti, got it OOM
[17:10] <annerajb> rsalveti, http://pastebin.com/8cxgJ9Ba this device has a smaller /system partition so it may be running out of memory because i either failed to apply a patch correctly or i have extra stuff that i didnt delete when i made the bootstrap
[17:10] <MIhir> hey..
[17:11] <MIhir> what is other channel for development ?
[17:11] <MIhir> discussion ?
[17:11] <andrea_> ubuntu-app-devel
[17:14] <rsalveti> annerajb: weird, in theory this zip should be smaller than the original one from CM
[17:14] <rsalveti> annerajb: can you try flashing that with another recovery?
[17:14] <annerajb> rsalveti, in that case i may have inputted the wrong numbers on the partition space change i did.
[17:15] <rsalveti> right, could be as well
[17:18] <sil2100> bfiller: hmm, would you mind if I remove phone-app from the daily-release config/
[17:18] <sil2100> bfiller: since I guess it's still valid that this package gets removed and is deprecated, yes?
[17:20] <bfiller> sil2100: well we still need it the build until we have a replacement, fine with it staying in the ppa until we have a replacement as it won't go in the archive
[17:20] <annerajb> rsalveti, i verified and i have the patch applied that was applied to get quantal to build i am going to try another recovery.
[17:21] <sil2100> bfiller: but no new merges will go in related to it, right?
[17:21] <sil2100> bfiller: since it's already in the archive right now, so at least it won't disappear
[17:22] <sil2100> Wait, no
[17:22] <sil2100> I'm wrong
[17:22] <sil2100> Scratch that...
[17:22] <bfiller> sil2100: there might be some merges that still need to happen as bug fixes until we land the newer stuff
[17:23] <sil2100> bfiller: right, ok, so let me leave it for now
[17:24] <sil2100> bfiller: any news related to ubuntu-ui-extras ?
[17:25] <bfiller> sil2100: not yet, been in meetings for last hours, will look as soon as off phone
[17:25] <sil2100> bfiller: ok, if anything, send me an e-mail about it if you can, since I need to EOD pretty soon
[17:29] <annerajb> rsalveti, BTW i have to do a factory stock rom because clock work recovery cannot install because it needs the /system partition also the version i have of clock work recovery is <IP_ADDRESS>
[17:30] <annerajb> rsalveti, if i try to install with that version of CWR it fails because it can´t read the device property from the /system partition
[17:30] <rsalveti> oh, quite old
[17:30] <rsalveti> maybe twrp
[17:30] <annerajb> all right let me update to a later CWR
[17:31] <annerajb> thought this one installed fine the quantal build
[17:32] <sergiusens> cyphermox_: rsalveti happroved
[17:35] <annerajb> rsalveti, i looked at the clock work website and the latest version they have for my device is the one i have <IP_ADDRESS> maybe the latest recovery <IP_ADDRESS> uses too much memory making it go oom while installing?
[17:36] <rsalveti> yeah, not sure, you could also try flashing the original cm image (10.1.2) with the latest cwm you have
[17:36] <rsalveti> and see if the error happens there
[17:36] <rsalveti> otherwise it might be something specific to your port
[17:36] <rsalveti> alright, time for some lunch now
[17:36] <annerajb> rsalveti, original cm image from where?
[17:37] <annerajb> rsalveti, bona petit
[17:37] <rsalveti> annerajb: http://www.get.cm/?device=epicmtd
[17:37] <rsalveti> as your port is probably based on that code anyway
[17:37] <rsalveti> and the image there might be even bigger
[17:38] <rsalveti> thanks :-)
[18:02] <sergiusens> om26er: https://code.launchpad.net/~sergiusens/phablet-tools/test_update/+merge/175355
[18:03] <sergiusens> ogra_: habemus build?
[18:05] <sergiusens> ogra_: also https://code.launchpad.net/~sergiusens/ubuntu-seeds/locationless/+merge/175320
[18:08] <sergiusens> boiko: hey, where are we at?
[18:09] <boiko> sergiusens: telephony-service packaging MR passed and was approved by tiago
[18:10] <boiko> sergiusens: for the other two (dialer-app and messaging-app) CI passed, but tiago needs to fix some things in the MR itself
[18:11] <kenvandine> Saviq, the gsettings-qt api break has landed, the unity8 branch for background settings should be safe to land now
[18:14] <Saviq> kenvandine, cheers
[18:14] <kenvandine> Saviq, the latest CI run failed so i triggered a rebuild
[18:14] <kenvandine> i'll top approve it when that passes
[18:15] <bfiller> sergiusens, ogra_ : can one of you review this to add address-book-app to the seed: https://code.launchpad.net/~bfiller/ubuntu-seeds/ubuntu-touch.saucy-address-book/+merge/175359
[18:15] <Saviq> kenvandine, there's no review from our people yet
[18:15] <Saviq> kenvandine, so please let us do our stuff :)
[18:15] <kenvandine> oh
[18:15] <kenvandine> sorry... i thought it was :)
[18:16] <kenvandine> it's not waiting on anyone else, so likely not in anyone's queue
[18:16] <kenvandine> want me to add a reviewer?
[18:17] <ogra_> bfiller, merged
[18:17] <bfiller> ogra_: thanks
[18:18] <sergiusens> boiko: ack, thanks
[18:18] <boiko> sergiusens: thanks for looking into that
[18:18] <ogra_> i'll wait with the meta upload since i know that there is another seed merge from ricmm waiting
[18:18] <sergiusens> ogra_: yeah, this one: https://code.launchpad.net/~sergiusens/ubuntu-seeds/locationless/+merge/175320
[18:19] <ogra_> sergiusens, merged too
[18:25] <ogra_> sergiusens, why would we have a new build btw ?
[18:25] <pmcgowan> ogra_,  no 17 today?
[18:25] <sergiusens> ogra_: I thought we wanted to try the click packages
[18:25] <ogra_> sergiusens, as i understood asac he wants to see the dashboard green before i can start a new one
[18:26] <doanac> gema, asac: i've got utah tested and working on touch images again. the unity8 fix is in, the dbus session is in, the --pending is in, and now i'm waiting for the PPA to build
[18:26] <doanac> 0.14.2 will be released shortly and I'll be able to kick off smoke testing again
[18:26] <ogra_> (that is, the tests need to work first)
[18:26] <ogra_> pmcgowan, not released, you could install it using --pending
[18:26] <pmcgowan> ogra_, anything wrong with it?
[18:27] <sergiusens> doanac: heads up on the image updates stuff that is comming
[18:27] <ogra_> (17 failed dues to a PPA error, 17.1 is fine)
[18:27] <ogra_> pmcgowan, nothing except the new rule is that we are not allowed to release them if the dashboard isnt gree
[18:27] <ogra_> n
[18:27] <pmcgowan> ogra_, ok ty
[18:27] <ogra_> pmcgowan, http://reports.qa.ubuntu.com/smokeng/saucy/
[18:28] <ogra_> pmcgowan, it works  absolutely fine though
[18:28] <ogra_> (teh test suite is broken)
[18:28] <pmcgowan> gotcha
[18:28] <pmcgowan> yar
[18:29] <ogra_> heh
[18:29] <ogra_> now thats intresting
[18:29] <ogra_> http://reports.qa.ubuntu.com/smokeng/saucy/image/3038/
[18:29] <ogra_> Summary of smoke testing for saucy touch image 20130717 ? on maguro
[18:29] <sergiusens> ogra_: so first step is to get a new build with tests and then add the click hook?
[18:29] <ogra_> i wonder why it adds the question mark
[18:30] <ogra_> sergiusens, dunno, i thought doanac would be able to re-run them once he finished his loacl tests
[18:30] <ogra_> sergiusens, but i can also just roll a new image anyway i guess ... let me do that livecd-rootfs merge :)
[18:31] <ogra_> sergiusens, did cjwatson's fix land already ?
[18:31] <sergiusens> ogra_: let me check, oh, I have a merge conflict I'm just seeing now :-/ ... changelogs have been change! Go figure :-P
[18:31] <sergiusens> change[d]
[18:32] <ogra_> yeah, i would have handled that :)
[18:32]  * ogra_ saw it already
[18:36] <gema> doanac: sounds good
[18:36] <gema> doanac: let me know when it lands in the lab so that we know which images are tested with the --pending change
[18:37] <ogra_> gema, seems the system picks them up anyway and several people want a fresh build
[18:37] <doanac> gema sure
[18:38] <ogra_> gema, so i'll just trigger a build later and utah should just do its job :)
[18:38] <ogra_> (that will then be 20130717.2)
[18:39] <doanac> ogra_: note: the 0.14.2 utah ppa still hasn't finished building. so i still need time before I can deploy to our server
[18:39] <gema> ogra_: awesome
[18:39] <ogra_> doanac, we still need a merge of sergiusens stuff before i can start a build, that will still take a while, no worries
[18:40] <ogra_> i guess you will be done before we are ready
[18:40] <sergiusens> ogra_: https://launchpad.net/ubuntu/saucy/+source/click/0.1.5
[18:41] <ogra_> sergiusens, ah, still in proposed
[18:41] <ogra_> (and waiting for ppc it seems)
[18:41] <sergiusens> Fix infinite recursion in ClickUser.click_pw.
[18:42] <ogra_> yeah :)
[18:42] <ogra_> https://launchpad.net/ubuntu/+source/click/0.1.5/+build/4802230
[18:43] <ogra_> start in 5h
[18:43] <ogra_> that doesnt look good
[18:43] <sergiusens> ogra_: I wonders why powerpc builders build private jobs :-P
[18:43] <sergiusens> ogra_: https://launchpad.net/builders/
[18:44] <ogra_> security stuff
[18:44] <ogra_> i guess
[18:53] <annerajb> rsalveti, i ran df -h on a loop while insatlling the bootstrap i build yesterday and the system partition ran out of disk space. ill have to look into trimming that image.
[18:55] <ogra_> sergiusens, merged, but i'll refrain from releasing livecd-rootfs until click is in
[18:55] <sergiusens> ogra_: that's good enough
[18:56] <ogra_> i dont really want to risk an endless click loop at buildtime :)
[18:58] <jimmy__> Hi there
[18:58] <sforshee> rsalveti, mfisch: another powerd MR: https://code.launchpad.net/~sforshee/powerd/clean-up-cli-output/+merge/175376
[18:58] <mfisch> sforshee: ah, I forgot to to the last one too
[18:59] <mfisch> sforshee: I'll do both now
[19:00] <sforshee> mfisch: thanks
[19:05] <mfisch> sforshee: commented on the upower on
[19:05] <mfisch> sforshee: can we delete asac's reviews?
[19:06] <sforshee> yes
[19:07] <mfisch> sforshee: I'm +1 on removing the "We get signal" call, but when MMS works, we'll need to retest it all, it might be a different signal
[19:09] <mfisch> sforshee: approved the CLI review
[19:18] <mfisch> sergiusens: who is working on/owns the browser app?
[19:19] <sergiusens> mfisch: oSoMon
[19:19] <mfisch> sergiusens: thanks
[19:20] <sforshee> mfisch: we don't need the "we get signal" print. If you enable debug the same information will be printed for any unknown signal.
[19:20] <sforshee> mfisch: responded to your comments on the upower MR
[19:26] <stgraber> sergiusens: here's the bootstrap script for the readonly image based setup: http://paste.ubuntu.com/5885313/
[19:27] <stgraber> sergiusens: we plan on sending a call for early testers (for people who have a spare device and don't mind loosing data) on Friday, so it'd be great if we could have that code as a --bootstrap-image option in phablet-flash by then (otherwise I'll just link to that script directly)
[19:28] <mhall119> stgraber: will we have a way for those folks to install apps?
[19:30] <stgraber> mhall119: not until click packages are fully working (I'll make it very clear in the blog post, that it's read-only with no way of running apt)
[19:30] <mhall119> ok
[19:30] <mhall119> rsalveti: the apps I added to the ubuntu-seeds branch, those are still being installed from .debs not .click packages right?
[19:30] <stgraber> what I really want to get is feedback on all 4 supported models and making sure that basic functions (telephony, network, ...) work as well as they do on flipped
[19:30] <stgraber> then hopefully soon after that, we'll get click working and we can go with a bigger pool of testers
[19:30] <stgraber> and soon after that, just make it the default and be done with it :)
[19:32] <mhall119> stgraber: I'll let you know if camera and audio don't work on the N7 :)
[19:32] <sergiusens> stgraber: ack
[19:32] <sergiusens> stgraber: it's going to happen today :-)
[19:32] <sergiusens> stgraber: I'll be testing on two devices and also check what's needed for testing since it's a hot topic ;-)
[19:34] <stgraber> sergiusens: cool, thanks!
[19:34] <stgraber> sergiusens: I tested on mako and grouper. grouper had a problem (cache partitioning not mounting) which I now fixed, so it'll be good in the next image.
[19:35] <stgraber> sergiusens: if you test with grouper, it'll work, however further updates with system-image-cli won't, so you'll need to re-bootstrap with the next daily to get the fix
[19:35] <sergiusens> ok, no worries, these are not final systems :-)
[19:35] <stgraber> maguro and manta may be affected by the same bug, not sure, in any case, I expect a bootstrap to work and updates to be broken, so as long as you re-bootstrap tomorrow, you'll be fine
[19:37] <stgraber> I've got to run for very late lunch and some errands but should be back in an hour or so
[19:38] <annerajb> sergiusens, where can i find direct_sf_test in the raring-preinstalled-phablet-armfh*.zip  ??
[19:39] <mfisch> sforshee: approved the upower mp
[19:39] <sforshee> mfisch: thanks
[19:41] <oSoMoN> mzanetti: hey, are you around?
[19:41] <annerajb> ogra_, now when i boot it seems to be on android since it shows root@android:~#
[19:42] <annerajb> ogra_, and it has the ubuntu partitions loaded
[19:42] <ogra_> great
[19:43] <annerajb> ogra_, thought i get a black screen where is /var/log/messages??
[19:43] <ogra_> black screen is good that means surfaceflinger works :)
[19:43] <ogra_> (something else doesnt though)
[19:43] <ogra_> use logcat
[19:44] <annerajb> i am watching the logcat output dont see anything meaningful let me figure out how to get this into a file
[19:47] <annerajb> ogra_, http://pastebin.com/Zb8Yy04x i dont see anything apart fromt he time stuff that's error level messages
[19:48] <ogra_> annerajb, hmm, i dont see it starting any of the ubuntu-android bits ... like uchroot or ubuntuappmanager
[19:48] <ogra_> rsalveti, ^^^
[19:49] <annerajb> ogra_, where should those binarys be let me take a look if they are there
[19:49] <annerajb> ogra_, i found uchroot in /system/bin
[19:50] <ogra_> yeah, android in the unflipped images should execute it
[19:51] <annerajb> i tried running ubuntu_chroot shell and it said cannot determine your username.
[19:51] <rsalveti> mhall119: yes, sergiusens is working on converting them to click packages
[19:51] <annerajb> and if i run uchroot it hangs and dosnt appear to do anything ogra_
[19:52] <rsalveti> uchroot will only work if you also installed the ubuntu zip
[19:52] <rsalveti> but first let's make sure the android one is working as expected
[19:52] <rsalveti> so it seems the device is now up and running correctly
[19:52] <ogra_> SF runs
[19:52] <rsalveti> annerajb: can you run ps to see if you have ubuntuappmanager running?
[19:53] <annerajb> rsalveti, it's running
[19:53] <rsalveti> cool
[19:53] <rsalveti> then just flash the ubuntu zip now
[19:53] <annerajb> hmm i did lol rsalveti this is running the ubuntu zip
[19:54] <annerajb> rsalveti, a whole ps  http://pastebin.com/ZsWanKkF
[19:54] <ogra_> which zip did you download ?
[19:56] <rsalveti> annerajb: I mean, did you also flashed the raring zip I pasted you yesterday?
[19:56] <annerajb> raring-preinstalled-phablet-armhf.zip
[19:56] <annerajb> rsalveti, yes i did
[19:56] <rsalveti> yeah, that's the one
[19:56] <rsalveti> then check if you have the ubuntu rootfs under /data/ubuntu/
[19:57] <annerajb> i do rsalveti
[19:58] <rsalveti> annerajb: then just need to check why 'ubuntu_chroot shell' might not be working for you
[19:58] <rsalveti> annerajb: did you enable all the required kernel configs?
[19:58] <rsalveti> otherwise it'll fail when enabling the container
[20:01] <annerajb> rsalveti, i applied some kernel changes but werent from the wiki page was from the last guy that got the image working for quantal i am missing some namespace kconfig variables that have to be enabled
[20:02] <annerajb> so ill do all the kernel changes and recompile and see if i can get another build tonight
[20:05] <rsalveti> annerajb: cool
[20:06] <annerajb> thanks for the help rsalveti and others
[20:06] <rsalveti> getting close :-)
[20:08] <annerajb> rsalveti, how should i build now make clean; make? or make clean; brunch epicmtd?
[20:08] <sergiusens> rsalveti: by using the raring image, won't platform-api break since the refactor was after?
[20:08] <rsalveti> sergiusens: don't think we had any api/abi changes in there
[20:09] <rsalveti> the refactoring happened mostly in the ubuntu side
[20:17] <annerajb> rsalveti, if i would like to have this stuff on git. i assume i shoudnt merge request that into cyanogen mod since it will break the android version so where should i store the android changes make a fork on github and commit the changes there?
[20:18] <rsalveti> annerajb: pushing stuff in your personal github account would be a good start, we can then merge it in phablet.u.c later
[20:18] <cjwatson> sergiusens: Yeah, sorry, we're temporarily one builder short on powerpc - that'll be sorted out later this week
[20:19] <annerajb> all right. rsalveti also didnt tell you how i fixed the running out of disk issue..
[20:19] <rsalveti> we hope to have gerrit in place soon, then once merged you'll be able to propose merge requests there
[20:19] <rsalveti> annerajb: what was the problem?
[20:19] <cjwatson> sergiusens: I've scored click/0.1.5/powerpc up insofar as it'll make much difference
[20:19] <annerajb> rsalveti, had to delete all the apks in /app and /media/audio /media/bootanimations.zip after that when installing the bootstrap i build yesterday it was left with 300k of disk.
[20:20] <rsalveti> annerajb: right, cool
[20:20] <sergiusens> cjwatson: thanks for the update
[20:21] <annerajb> rsalveti, are those apks really necesary when installing the bootstrap? i assume there are other phones where there may not be a lot of space ont he system partition.
[20:21] <rsalveti> annerajb: probably not
[20:24] <pmcgowan> rsalveti, is the network indicator broken today?
[20:24] <rsalveti> pmcgowan: it shouldn't, using which image?
[20:24] <pmcgowan> 17.1
[20:24] <rsalveti> I think we didn't yet publish today's build
[20:24] <pmcgowan> I am connected but it says not
[20:24] <rsalveti> hm, let me flash that
[20:25] <rsalveti> but I know ogra_ tested it already
[20:25] <pmcgowan> bfiller, I dont see thumbnails in history yet
[20:27] <bfiller> pmcgowan: checking
[20:28] <ogra_> rsalveti, i didnt test todays build since it was clear that asac didnt want it released, popey tested though
[20:28] <rsalveti> right, flashing it now to see
[20:28] <rsalveti> ogra_: next one should be all good right?
[20:28] <rsalveti> seems doanac fixed all the issues already
[20:28] <ogra_> rsalveti, hopefully
[20:29] <rsalveti> :-)
[20:29] <ogra_> rsalveti, i would trigger a build but then we cant have sergiusens click work in
[20:29] <ogra_> needs this fix https://launchpad.net/ubuntu/saucy/+source/click/0.1.5.... which is stuck waiting for a free powerpc builder
[20:30] <rsalveti> oh, wget will now be installed by default
[20:30] <rsalveti> awesome
[20:30] <rsalveti> hahaha
[20:30] <rsalveti> that was so annoying
[20:31] <pmcgowan> ogra_, cant we disable powerpc builds for things
[20:31] <ogra_> :)
[20:31] <rsalveti> how long will that take?
[20:31] <ogra_> pmcgowan, thats the archive, no we cant
[20:31] <ogra_> click n the ppc link ... it should tell you the ETA
[20:31] <rsalveti> yeah, don't trust that
[20:31] <ogra_> last time i checked it was 5h
[20:31] <rsalveti> 2h now
[20:31] <rsalveti> 18 jobs (2 hours 40 minutes)
[20:32] <ogra_> ah, so it moved forwatd 3h within 1h
[20:32] <rsalveti> queue, so should be done soon indeed
[20:32] <cjwatson> I scored it up
[20:32] <cjwatson> But I'll just force it into the release pocket
[20:32] <ogra_> cjwatson, thanks
[20:32] <rsalveti> great
[20:32] <ogra_> so i can upload livecd-rootf then
[20:32] <ogra_> +s
[20:32] <ogra_> i held that back to not hit an endless loop :)
[20:33] <bfiller> pmcgowan: working for me, check your versions of these: http://pastebin.ubuntu.com/5885486/
[20:34] <pmcgowan> bfiller, let me make sure it flashed, probably no space
[20:34] <pmcgowan> bfiller, bah nm
[20:34] <annerajb> rsalveti, how can i setup a proxy for downloading the ubuntu-ramdisk.img??? i am behind a proxy and it's not downloading it
[20:34] <pmcgowan> gets me every time
[20:35] <bfiller> pmcgowan: although I am seeing some issues I wasn't seeing during testing, some thumbnails are empty
[20:35] <ogra_> livecd-rootfs uploaded
[20:35] <rsalveti> annerajb: hm, need to check that
[20:36]  * ogra_ sets an alarm to be notified once it hits the achive and goes afk
[20:36] <rsalveti> it downloads the debs with urllib2
[20:40] <annerajb> rsalveti, i setup the http and apt proxys let's see if that fixes it
[20:41] <sergiusens> rsalveti: should I also move the upstart job to maliit-framework or should that be a new upload?
[20:41] <sergiusens> so we can sync it better
[20:41] <rsalveti> sergiusens: let's take that as another upload
[20:42] <rsalveti> annerajb: in theory urllib2 will use the http_proxy env variable
[20:44] <rsalveti> just need to check if it's indeed using http there, instead of https
[20:44] <cjwatson> There, you'll have click 0.1.5 in saucy after the next publisher run
[20:45] <sergiusens> \o/
[20:45] <cjwatson> Which will start in ~3mins
[20:46] <rsalveti> annerajb: yeah, using https
[20:48] <annerajb> rsalveti, all right just setup all the proxys in upper case and lower case and it's been building for a while in retrospective i shold have run make bacon
[20:53] <rsalveti> xnox: you said you'd be replacing the pull-lp-bin tool as well, any progress on that?
[20:54] <rsalveti> that might handle proxy better as well
[20:54] <sergiusens> rsalveti: he's EOD iirc
[20:54] <rsalveti> hahha, he's always on-line
[21:14] <oSoMoN> WebbyIT: thanks for the review
[21:15] <oSoMoN> I’ll take the liberty of top-approving myself, seeing that it’s trivial enough and has been approved by one person + jenkins already
[21:18] <WebbyIT> oSoMoN: yeah, I think that you can do it, certainly does not break anything
[21:34] <DJJeff> is ummmmm usb tethering possible? http://i.imgur.com/FszXfdO.png
[22:25] <asac> ho
[22:25] <asac> ttyt
[22:27] <ogra_> rsalveti, sergiusens, build running
[22:34] <popey> ogra_: to finish tonight?
[22:34] <ogra_> 50min
[22:34] <ogra_> popey, dont worry about testing
[22:34] <popey> no?
[22:34] <ogra_> we need to wait for the dashboard anyway
[22:35] <ogra_> well, you can if you feel like
[22:35] <vthompson> balloons_, do you have a second for some hand holding with autopilot (trying to get playing a song in music-app to work)?
[22:37] <stgraber> sergiusens: so does that look easy to integrate?
[22:37] <sergiusens> stgraber: I'm on it, I was just using python2 though, never migrated since I need to work on precise and never check
[22:38] <stgraber> sergiusens: should be easy enough, just import urlretriever from urllib instead of urllib2.request
[22:38] <stgraber> I believe that's the only py3 specific bit in that code
[22:39] <balloons_> vthompson, shoot
[22:41] <vthompson> balloons_, excellent. So I have an UbuntuShape that I want to test that the image.source changes to a different icon when clicked. However, I can't seem to get access t the UbuntuShape's image attribute.
[22:42] <Azelphur> Is there any docs for dual booting Ubuntu touch?
[22:42] <vthompson> balloons_, I get the following: AttributeError: Class 'UbuntuShape' has no attribute 'image'.
[22:42] <balloons_> what's the qml file show?
[22:43] <popey> Azelphur: i have seen someone dual boot on nexus 7
[22:43] <Azelphur> popey: nice
[22:43] <popey> http://barrenfrozenwasteland.com/2013/03/dual-booting-android-and-ubuntu-touch-on-the-nexus-7/
[22:44] <vthompson> balloons_, http://paste.ubuntu.com/5885798/
[22:46] <balloons_> vthompson, ahh.. add an objectName for the image
[22:46] <vthompson> balloons_, do I have to then reference this by the objectName?
[22:46] <balloons_> vthompson, then do the select_single type Image and objectName=yourname
[22:47] <annerajb> Is Ubuntu touch gonna have a menu option for rotate lock?
[22:47] <vthompson> balloons_, select_single is one of the functions in your emulator?
[22:47] <balloons_> vthompson, http://unity.ubuntu.com/autopilot/api/introspection.html
[22:48] <balloons_> vthompson, it's the normal introspection routine
[22:52] <balloons_> vthompson, so self.app.select_single('Image', objectName='shapeImage')
[22:53] <vthompson> balloons_, Ok does the UbuntuShape still need an objectName? I get the following error: AttributeError: 'NoneType' object has no attribute 'source'
[22:55] <annerajb> rsalveti: what's the best way to know if somebody is working on a port so I don't waste effort on a port
[22:55] <annerajb> Is there a wiki page?
[23:11] <popey> annerajb: yes https://wiki.ubuntu.com/Touch/Ports
[23:11] <popey> annerajb: sorry, https://wiki.ubuntu.com/Touch/Devices
[23:13] <annerajb> popey: thx
[23:16] <Chocanto> popey: Hey ! How are you ? :) Do you know if the sdk team is working on file I/O ?
[23:21] <popey> Chocanto: hi, how do you mean?
[23:29] <Chocanto> popey: I mean if the file I/O api is planned, or if they are working on :)
[23:31] <popey> The SDK team have lots to do ☻
[23:31] <popey> I don't believe direct file io is something we are doing
[23:35] <stgraber> ogra_: ah cool, you're already doing a touch build, I was just about to kick one
[23:35] <Chocanto> popey: Ok :) It was just to know, because I need it for docviewer ^^
[23:36] <popey> Chocanto: https://wiki.ubuntu.com/Touch/SdkFeatureStatus see "Content management"
[23:36] <Chocanto> popey: to avoid having to use the temporary launcher, and use Arguments and I/O api of sdk team
[23:37] <Chocanto> Ah thanks, I didn't know the existence of this page ^^
[23:42] <popey> sorry about that Chocanto
[23:43] <Chocanto> nono, that's good :) It was just because mhall asked me to test Arguments in docviewer, but I can't without file I/O. But I'll wait ;)
[23:48] <mhall119> Chocanto: I didn't think the docviewer had to do any IO in QML
[23:48] <mhall119> or your wrapper
[23:48] <mhall119> I thought it just passed file paths to other plugins
[23:50] <Chocanto> mhall119: That's juste because I need to know the mimetype of the file, and other usefull informations about it.
[23:50] <Chocanto> mhall119: I can do it with a plugin
[23:50] <mhall119> ah, I see
[23:51] <Chocanto> mhall119: Because arguments work nice and exactly fit with what we need, so I can get the filepath
[23:52] <mhall119> so then are you just going to make a plugin to give file meta-data like mimetype?
[23:52] <mhall119> there might already be something like that somewhere
[23:53] <Chocanto> mhall119: I hope, but if not yes I will do.
[23:53] <mhall119> ok
[23:54] <Chocanto> mhall119: Did you asked tsdgeos about the poppler package ?


[08:56] <Laney> slangasek: Do you plan on uploading an upstart with user sessions to unstable (soon)? I'm wondering whether to forward stuff and/or trying to have some kind of discussion about adding support to pkg-gnome packages.
[09:25] <vanguarde9> Hello guys , i have a question
[09:25] <vanguarde9> http://pastebin.com/XrXXv3Ue
[09:25] <vanguarde9> I have this upstart scripts
[09:26] <vanguarde9> In pre-start stanza Im reading simple config file
[09:26] <vanguarde9> to get content of one shell variable
[09:26] <vanguarde9> but when i try to echo this variable in script stanza
[09:27] <vanguarde9> its empty
[09:27] <vanguarde9> can somebody tell me what im doing wrong ?
[09:27] <vanguarde9> why this variable is not propagated later ?
[09:27] <jodh> vanguarde9: http://upstart.ubuntu.com/cookbook/#pass-state-between-job-processes
[09:30] <vanguarde9> thanks for hint
[09:31] <xnox> jodh: note debian-devel & debian-bsd w.r.t. kfreebsd upstart porting =)))))
[09:35] <jodh> xnox: interesting :)
[12:47] <joaojeronimo> so, I have a process that forks 4 times, and upstart is only changing the uid for the father. The children end up not having enough permissions to do stuff on the file system
[12:47] <joaojeronimo> how do I correctly setuid for all the children ?
[12:51] <jodh> joaojeronimo: upstart requires that processes only fork up to 2 times (since that is the maximum number of forks required to fully daemonize). I'd suggest either running your app in the foreground if it provides an option to do. Alternatively, 'expect stop' might be an option for you? (http://upstart.ubuntu.com/cookbook/#expect-stop)
[12:53] <joaojeronimo> jodh: 'expect stop' doesn't seem to fix this problem about the file permissions of the children
[12:54] <joaojeronimo> jodh, the problem is I'm running an app that uses leveldb, and leveldb is making 4 forks that need to read and write to the OS. Even using setuid on upstart, apparently the children end up not having correct permissions
[12:55] <jodh> joaojeronimo: upstart only sets the initial processes uid - sounds like your app is changing it again somehow.
[12:56] <joaojeronimo> jodh: I don't know how this works exactly but it sounds like it starts the process, the process forks, and then upstart changes the uid for the initial process ?
[12:56] <jodh> joaojeronimo: correct.
[12:57] <jodh> joaojeronimo: well, upstart forks, changes to the user you specify, then runs your app. whatever happens next wrt uids is the apps responsibility.
[12:57] <joaojeronimo> interesting... ok got it..
[12:58] <joaojeronimo> well it's a node.js app, I even tried process.setuid('correctusername') but apparently the children still don't get the correct uid
[12:58] <jodh> joaojeronimo: try running your job replacing the node.js bit with procenv to show what environment upstart gives it (see http://upstart.ubuntu.com/cookbook/#see-the-environment-a-job-runs-in)
[13:00] <dottedmag> I am trying to run a daemon (which does not have an option to stay in foreground). I use 'expect daemon' and everything works fine, except
[13:00] <dottedmag> if this daemon detects configuration problem up launch and exits, and then upstart fails to detect that daemon exited before fork.
[13:01] <dottedmag> So upstart continues to report status as start/running (no pid) until I explicitly 'stop' it.
[13:01] <dottedmag> Is that expected?
[13:02] <dottedmag> It's pretty simple to reproduce. The following job description will stay in 'start/running' state after start: http://pastebin.com/ypdmTPAS
[13:06] <jodh> dottedmag: Please read the cookbook. This is correct behaviour because upstart is attempting to run your failing job repeatedly as you have specified 'respawn'.
[13:06] <jodh> dottedmag: see: http://upstart.ubuntu.com/cookbook/#expect, http://upstart.ubuntu.com/cookbook/#respawn, http://upstart.ubuntu.com/cookbook/#implications-of-misspecifying-expect.
[13:06] <jodh> dottedmag: note the big warning which covers your scenario at the start of the respawn section.
[13:08] <dottedmag> I see, thanks.
[13:26] <dottedmag> Hmm. But the job does not get respawned. Log file only shows single attempt to run it.
[14:06] <SpamapS> jodh: why doesn't init-checkconf ever work?
[14:06] <SpamapS> jodh: I say that as it now works for me. But the other day, it didn't.
[14:07] <SpamapS> jodh: n/m ;)
[14:13] <jodh> SpamapS: sorry, without more details I don't know. Can you raise a bug if you can recreate?
[15:00] <dottedmag> Where do the upstart log messages go? I have started it with --verbose, but the only place I see those messages is /var/log/dmesg and only up to DM start moment.
[15:00]  * dottedmag slaps his forehead
[15:00] <dottedmag> dmesg :)
[15:00] <slangasek> Laney: updating upstart in unstable is on my List, but not a top priority currently
[15:00] <Laney> k
[15:16] <dottedmag> I've got a situation when daemon fails on startup and upstart does not cause it to be restarted: http://pastebin.com/ePciMNWw
[15:16] <dottedmag> zabbix_agent fails and (trivial fork/fork/exit) daemon-exit does not.
[15:18] <dottedmag> zabbix_agent does not do anything weird on startup: http://pastebin.com/0mkKvg1d
[15:18]  * xnox thought it needs to start to be respawned....
[15:19] <xnox> e.g. respawned if it segfaults / killed / etc. not when it gracefully exits.
[15:19] <dottedmag> It exits with exit code 255
[15:19] <dottedmag> Also, if I just run /bin/false, it gets respawned to matter what.
[15:19] <dottedmag> And zabbix_agent gets stuck in start/running state.
[15:24] <jodh> dottedmag: are you aware that zabbix-agent has already been packaged for Upstart in Ubuntu? http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/zabbix/saucy/view/head:/debian/zabbix-agent.upstart
[15:26] <dottedmag> jodh: I am aware of it, but have a look at bugtracker.
[15:26] <dottedmag> Also, I need 2.2 (not yet released one).
[15:27] <dottedmag> Anyway, now I can reproduce the error without zabbix_agent.
[15:35] <dottedmag> Please have a look: https://bugs.launchpad.net/upstart/+bug/1182943 -- this one is distilled to bare minimum.
[15:37] <jodh> dottedmag: this is not a bug in upstart so much as an incorrect .conf file - /bin/false does *not* fork twice, but you've told upstart it does...
[15:38] <dottedmag> jodh: Yes. But it's upstart's job to handle failing daemons properly.
[15:38] <jodh> ...which it does perfectly well when provided with a valid .conf file.
[15:38] <dottedmag> Uhm.
[15:38] <jodh> dottedmag: upstart cannot "guess" how your app works I'm afraid, hence "expect".
[15:39] <dottedmag> zabbix_agent checks the configuration and exits if it is incorrect. Otherwise it forks twice and runs.
[15:39] <dottedmag> How should I write a .conf in this case?
[15:40] <jodh> dottedmag: does zabbix have an option to "just check its config file and exit"? If so, put that call in a pre-start section which will stop the main job process starting in case of an invalid config file.
[15:40] <dottedmag> jodh: just had a look. Nope, it does not.
[15:41] <dottedmag> Hum-hum. I think I can abuse one of the options for this check.
[15:41] <dottedmag> Still.
[15:43] <dottedmag> If you look at log file, upstart correctly saw abrupt termination of daemon (and proper PID), so it seems to be just a matter of event ordering.
[15:45] <dottedmag> jodh: thanks for suggestion.
[15:45] <jodh> dottedmag: yes, "-t" is ripe for abuse fwics.
[15:46] <dottedmag> I still feel it's kind of shaky to rely on daemons always reaching their intended number of forks and not failing before.
[15:46] <dottedmag> I'll have a look, might be it is not hard to fix
[15:51] <jodh> dottedmag: the problem is the "respawn" - upstart  cannot restart an app until that app has fully started (and then exited).
[15:52] <jodh> dottedmag: in your case, another consideration is how the config file became invalid in the first place.
[15:52] <jodh> dottedmag: the zabbix one that is.
[15:53] <dottedmag> jodh: that's just a syntax error, and I am not really worried about it.
[15:53] <dottedmag> jodh: I am worried about job being in start/running state, while no service is actually running.
[16:12] <dottedmag> Uhm, -t does not check config. Wonderful.
[16:27] <jodh> dottedmag: you might be able to use a "post-start" stanza to sniff around and determine if the agent started or not and just call "stop" if it isn't to tell upstart that it has died.
[16:28] <dottedmag> jodh: I will probably just add no-fork option to agent, seems much simpler.
[16:28] <jodh> dottedmag: frankly, most daemons provide such an option. And one to check any config file they use.
[16:28] <dottedmag> Yes, zabbix seems to be a bit... antique.
[16:28] <jodh> dottedmag: I was going to say "unique", but yeah ;)


[12:12] <smithj> thanks
[12:15] <cjwatson> in the case of a new upstream, it contains our diff against the corresponding base version in Debian rather than against the previous version in Ubuntu
[12:16] <cjwatson> this tends to be more useful if you're just trying to monitor what Ubuntu developers are doing; if you actually want the true diff in Ubuntu every time, contact Scott James Remnant and see if you can work something out
[12:18] <smithj> cjwatson: i'm mainly just monitoring
[12:18] <smithj> trying to keep abreast of what the major distros are doing, etc
[12:20] <cjwatson> good luck keeping up, then :)
[12:22] <cjwatson> hmm, interesting, it doesn't pick up on Ubuntu-native packages without *ubuntu* version numbers
[12:23] <Fujitsu> I also note that MoM does funny stuff, like mailing the PTS with `New upstream version' even if it isn't one.
[12:26] <cjwatson> Fujitsu: it means upstream relative to Ubuntu, i.e. a new base version from Debian
[12:26] <cjwatson> there are multiple levels of upstreamishness in the modern distro world ...
[12:26] <Fujitsu> Ah.
[12:26] <Fujitsu> OK.
[12:27] <cjwatson> I agree the terminology is a bit confusing when mailing Debian lists, though. Do you want to mail Scott and suggest that it should be "New base version" or something?
[12:31] <Fujitsu> That sounds better, as it is mailing Debian, and it's not upstream to them.
[12:50] <Seveas> keescook, ping
[01:21] <sladen> mdke: pong?
[01:22] <sladen> mdke: could you ask the question you and T` were after, I didn't get the full highlight.
[01:27] <mdke> sladen: I believe mjg59 handled it, it was something about Gnome volume control hotkeys
[01:27] <mdke> sladen: sounded like he wanted to implement something similar for xfce
[01:34] <sladen> mdke: gotcha, thanks
[02:17] <keescook> Seveas: distant pong.  what's up?
[02:18] <Seveas> keescook, about the USN RSS feed
[02:18] <Seveas> it moved to http://media.ubuntu-nl.org/rss/usn.xml
[02:19] <keescook> ah, very cool.  People keep asking about one, so I'm gonna send them that way until there is an "official" one.  :)  thanks!
[02:21] <Seveas> keescook, might as well make that one official if you mirror is on *.ubuntu.com or let me upload there ;)
[02:21] <Seveas> s/is/it/
[02:21] <keescook> Seveas: yeah, it's a bit out of my hands, though.  :)
[02:22] <Burgundavia> given the website is currently up for discussion right now, we should be able to do something liek that on the new one
[02:25] <bhale> hi all
[02:27] <keescook> Burgundavia: yawp
[02:27] <keescook> hiya bhale
[02:28] <grimeboy> Since icecast1 is deprecated to the extent that it doesn't receive bugfixes and is a bloated [self censorship]  should it not be removed from the repos?
[02:28] <grimeboy> WOr should this go in #ubuntu-motu
[02:28] <grimeboy> -W
[02:28] <grimeboy> +?
[02:29] <grimeboy> Assuming yes since it's in universe. Sorry.
[03:06] <avis> merry christmas to all ubuntu developers :)
[03:20] <Burgundavia> lamont: in edgy or feisty?
[03:20] <lamont> edgy.
[03:21] <lamont> more to the point, how do I trigger /etc/event.d/ttyS1 :)
[07:09] <pluto> Anyone around?
[07:10] <Burgundavia> yep
[07:10] <pluto> I got told to come here to see if anyone knew about how to fix a make clean error I'm getting
[07:11] <pluto> I've removed and reinstalled the headers, but when I go to make clean, I get scripts/Makefile.clean:17: /usr/src/linux-headers-2.6.17-10-generic/drivers/infiniband/ulp/srp/Makefile: No such file or directory
[07:13] <pluto> Any ideas?
[07:13] <Burgundavia> nope
[01:27] <tiglionabbit2> hello.  I would like to know what the process is to get a package added to the repositories?
[01:29] <tsmithe> tiglionabbit2, look on the wiki
[01:29] <tiglionabbit2> um, what part?
[01:29] <tsmithe> hang on
[01:29] <tsmithe> https://wiki.ubuntu.com/MOTU/Packages/New
[01:32] <tiglionabbit2> what if our request is to update a very old packageL
[01:32] <tiglionabbit2> the ruby interpreter, specifically
[01:35] <Chipzz> tiglionabbit2: you file a sync request
[01:35] <tiglionabbit2> and how do I do that?
[01:35] <Chipzz> it's somewhere on the wiki
[01:36] <Chipzz> but frankly, I can't believe ruby would be *that* much out-of-date? :)
[01:36] <tiglionabbit2> it's two years old
[01:36] <tiglionabbit2> well, 3 now
[01:36] <_ion> It's the same version as in Debian.
[01:37] <_ion>    ruby1.8 | 1.8.5-4ubuntu1 | http://fi.archive.ubuntu.com feisty/main Sources
[01:37] <_ion>    ruby1.8 |    1.8.5-4 | http://ftp.fi.debian.org sid/main Sources
[01:38] <_ion> In edgy, it's 1.8.4, which isn't very old either.
[01:38] <tiglionabbit2> oh whoops, it's called ruby1.8
[01:38] <tiglionabbit2> my bad
[01:40] <Chipzz> tiglionabbit2: there's even ruby1.9
[01:40] <Chipzz> but then, I'm running feisty; maybe bot on edgy
[01:42] <_ion> 1.9 is the ever-changing development version towards 2.0, it's not intended to be used in production.
[01:43] <tiglionabbit2> why does "ruby" point at the 1.8.2 version?
[01:43] <Chipzz> I didn't say he had to; I was just pointing it out to prove that ruby is not out-of-date ;)
[01:43] <_ion> It's just a metapackage. dpkg -L ruby, apt-cache depends ruby
[01:44] <tiglionabbit2> oh, you're correct
[01:44] <_ion> ...or just apt-cache show ruby :-)
[01:44] <Chipzz> tiglionabbit2: for the record, "ruby" points at the "ruby1.8" package , not the 1.8.2 version ;)
[01:44] <tiglionabbit2> weird that it would have the old version number then
[01:44] <Chipzz> subtle difference
[01:45] <_ion> Its version number doesn't really matter at all. It just happened to be created when the version of Ruby was 1.8.2
[01:46] <tiglionabbit2> =]  thanks
[07:35] <surfbuddy> is it cumpulsory to go through the gparted thing while installing ubuntu ???
[07:36] <surfbuddy> looks like  a bug while trying to install ubuntu - ( installer hangs when i use the set time button )
[07:38] <cjwatson> known
[07:38] <cjwatson> gparted> that or autopartitioning, or the alternate install CD
[07:38] <cjwatson> hope to get rid of gparted for advanced partitioning once I've finished writing the replacement
[07:41] <surfbuddy> whner i press the set time button the installer hangs and i have to reboot or relog to continue
[07:41] <cjwatson> yes, that's known I'm afraid
[07:41] <cjwatson> don't do that :-)
[07:42] <cjwatson> "Set time..." is just a nicety and it's been too much trouble so I'll probably just remove that button at some point
[07:42] <cjwatson> you can always set the time using the usual desktop facilities after installation if necessary
[07:42] <surfbuddy> cjwatson, yes .. no problem
[07:42] <surfbuddy> cjwatson, another thing.... ( writing )
[07:44] <surfbuddy> cjwatson, i already have an ext3 formatted parititon on /dev/sda1
[07:44] <surfbuddy> while going through the installer, ( which i forcibly have to ) , i create a ext3 on sda1 and swap on sda6
[07:45] <surfbuddy> but it always throws an error that ext3 format failed !
[07:45] <surfbuddy> can it be something related to the clock speed ( usb 1.1 or usb 2.0 )
[07:45] <cjwatson> no
[07:46] <cjwatson> file a bug at https://launchpad.net/distros/ubuntu/+source/ubiquity/+filebug and attach /var/log/syslog and /var/log/partman
[07:46] <cjwatson> this channel is for developer coordination rather than support
[07:46] <surfbuddy> would do it.