[01:48] <ledah_> hi anyone know about makefile programming? i'm trying to install a webcamstudio on natty since debs doesn't work i'm tangled with the source code @_@
[04:23] <hiexpo> hello all
[04:24] <hiexpo> I have a ?  I got banned from the ubuntu forums over a year ago can i please get the ban lifted thank you
[04:26] <hiexpo> I am unable to login and read any support on ubuntu problems
[04:29] <hiexpo> I currently install ubuntu on all the laptops i sell and do need support sometimes so this makes it rather difficult at times and if we are unable to resolve this than unfortunately I am going to have to switch to another distro to put on my laptops and sell   thanks again   Dion  i
[09:52] <s-fox> Hello.
[22:40] <hiexpo> no ops today ?


[06:46] <zyga> mwhudson, ?
[06:46] <zyga> mwhudson, some paste
[07:00] <gour> morning
[07:03] <gour> co-located branches doc (http://doc.bazaar.canonical.com/developers/colocated-branches.html) lists few 'use cases' (http://doc.bazaar.canonical.com/developers/colocated-branches.html#use-cases) and i'm not sure whether co-located branches are real need in bzr (yesterday i played with --lightweight checkouts used for feature branches based on shared repo) or is it more of filling the gap to hg/git's features?
[07:14] <spiv> gour: they are more convenient than lightweight checkouts + branchless repo, and just as good for many cases, so that's a pretty valuable improvement
[07:15] <gour> spiv: i see...thanks...are they going to be ready for 2.6?
[07:17] <spiv> They're already ready in 2.5: http://doc.bazaar.canonical.com/bzr.2.5/en/whats-new/whats-new-in-2.5.html#basic-colocated-branch-support
[07:17] <spiv> No doubt they'll be even better in 2.6 :)
[07:19] <gour> iirc, jelmer or someone else was speaking something about UI not polished (yet)...otoh, i was not aware they're already in...does it mean we should (try) to adopt 'em instead of lightweight co-s & branchless repos?
[07:19] <spiv> I'd give it go, yes.
[07:19] <gour> ok
[07:20] <spiv> If you don't like them for some reason you can always change your mind later and use lightweight checkouts and boring old branches in treeless repo, etc :)
[07:21] <gour> :-)
[07:23] <gour> in some use cases, i like treeless repo and lw co-s...eg. i'm using weechat irc client and my ~/.weechat is lightweight co keeping track of weechat's config files, while the treeless repo is in ~/repos
[07:27] <gour> hmm, colocated branches need new format...we just talked about bzr's formats yesterday :-)
[07:29] <gour> 2.6 docs when speaking about colocated branches uses future tense, so wondering what's avaialable today...
[07:39] <bob2> suspect once you get used to them you'll want to use colocated all the time
[07:42] <spiv> bob2: well, it's not especially well-suited for the .dotfiles use case mentioned above.
[07:43] <spiv> But for general code hacking, yeha.
[07:44] <jelmer> gour: huh?
[07:44] <jelmer> gour: colocated branches need a new format?
[07:47] <gour> jelmer: bzr init -h ==> --development-colo  The 2a format with experimental support for colocated
[07:48] <gour> branches.
[07:49] <gour> or it means something else i'm not aware of?
[07:50] <jelmer> gour: the development-colo format isn't  necessary for colocated branches anymore
[07:50] <jelmer> gour: you can just use them with 2a these days
[07:51] <gour> jelmer: hmm, it seems that docs needs some love then ;)
[07:51] <jelmer> gour: which docs?
[07:53] <gour> jelmer: bzr-2.5.1 help text for 'init' command
[08:00] <mgz> morning!
[08:03] <jelmer> hey mgz
[08:03] <jelmer> gour: ah, but I guess it's listed under the development formats still?
[08:07] <gour> jelmer: well, it's listed under branch format section along with --2a etc., iow. valid option for 'init' in 2.5.1
[08:09] <jelmer> gour: sure, but there's lots of other uninteresting formats there too
[08:09] <jelmer> *development
[08:09] <jelmer> though we should probably hide development-colo
[08:14]  * gour nods
[12:44] <anddam> do I need to register a launchpad account in order to just clone (branch?) a repository?
[12:44] <jelmer> anddam: no, you can clone a branch (as long as it's not private) without an account
[12:45] <anddam> jelmer: do I need to init a repo before running bzr branch?
[12:46] <jelmer> anddam: no, see the mini tutorial
[12:46] <jelmer> http://doc.bazaar.canonical.com/latest/en/mini-tutorial/
[12:46] <anddam> I tried both, "bzr branch lp:foo" and "mkdir foo; cd foo; bzr init; bzr branch lp:foo"
[12:46] <anddam> k
[12:46] <anddam> I just read that
[12:46] <anddam> it shows how to init-repo and init but it doesn't says it that's *mandatory* or not
[12:47] <anddam> with git a "git clone" would create the local repository as well
[12:48] <jelmer> anddam: in bzr the repository is created if a shared one doesn't exist too
[12:48] <anddam> I'm trying cloning lp:groundhog
[12:48] <anddam> I get    bzr: ERROR: Not a branch: "http://bazaar.launchpad.net/~juanjux/groundhog/groundhog-juanjo/"
[12:49] <anddam> when running "bzr branch lp:groundhog", is that an issue on my side or not?
[12:49] <jelmer> anddam: that branch doesn't really exist - it's never been pushed to according to the web page
[12:49] <anddam> sounds like it isn't
[12:49] <anddam> I see
[12:50] <anddam> Recent revisions
[12:50] <anddam> This branch has not been pushed to yet.
[12:50] <anddam> so the launchpad repository for the project is empty, isn't it?
[12:50] <jelmer> it doesn't actually have a control directory I think
[12:51] <jelmer> so it's not even empty
[12:51] <anddam> I apologize but I'm really new to bzr
[12:51] <anddam> idk what a control directory is
[12:51] <anddam> the point is that lp:groundhog has no code, is this correct?
[12:51] <jelmer> it's the same thing as ".git" in git
[12:52] <jelmer> I mean, in git the control directory is named ".git"
[12:52] <jelmer> anddam: yes, lp:groundhog doesn't have any code
[12:52] <anddam> I see lp:~juanjux/groundhog/trunk is listed as branch and that has code
[12:52] <anddam> is there any difference between a subdir in user space or a root level project?
[12:53] <anddam> I mean is that just a convention, a matter of taste or so?
[12:53] <anddam> (fetching)
[13:00] <jelmer> anddam: I'm not sure I follow
[13:00] <jelmer> anddam: subdir in user space?
[13:04] <anddam> jelmer: yes, ~juanjux/groundhog rather than groundhog
[13:05] <jelmer> anddam: ah, that's just convention
[13:11] <anddam> thx
[13:11] <anddam> bye
[13:38] <abentley> vila: Could you please review https://code.launchpad.net/~abentley/bzr/config-branchname/+merge/110825 ?
[14:51] <abentley> jam: Changing branchname to fall back to basename is a 1-line change, and I'm happy to do that.  Maybe rename to "shortname".  But you're not proposing we remove "basename", right?  So we'd still be introducing a new variable.
[14:51] <jam> abentley: I'm fine with a new var, what I want is to have 1 var that can just be used, without needing to think "do I need X or Y in this case"
[14:52] <abentley> jam: Okay.  Does "shortname" work?  ("branchshortname" seems...long)
[14:53] <jam> branchname is fine for me
[14:53] <jam> I think I prefer that
[14:55] <abentley> jam: "branchname" was meant to refer to the colocated branch terminology.  jelmer, is it cool if I introduce a config var called "branchname" that is ",branch=$NAME" but falls back to "parent/$NAME"?
[17:55] <mgz> Have we got a bug for `bzr config --remove launchpad_username` not working on 2.5.1?
[17:56] <mgz> needs --scope=bazaar
[20:33] <gour>     /q


  You must supply either a Commit Message on your MP, or a custom debian/changelog entry
[01:06] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2924 Preparing packages
[01:25] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2924 Failed to build (xenial/autopkgtest, zesty/autopkgtest). Ready to build (yakkety/autopkgtest)
[03:09] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2924 Preparing packages
[03:25] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2924 Failed to build (xenial/autopkgtest, zesty/autopkgtest). Ready to build (yakkety/autopkgtest)
[03:38] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2924 Preparing packages
[04:05] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2924 Pending binary packages (xenial/autopkgtest, zesty/autopkgtest). Ready to build (yakkety/autopkgtest)
[04:25] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2924 Successfully built
[07:32] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2925 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[07:45] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2925 Pending binary packages
[08:05] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2925 Diff missing
[08:32] -queuebot:#ubuntu-ci-eng- jamespage, https://bileto.ubuntu.com/#/ticket/2803 Abandoning ticket
[08:33] -queuebot:#ubuntu-ci-eng- jamespage, https://bileto.ubuntu.com/#/ticket/2883 Abandoning ticket
[08:34] -queuebot:#ubuntu-ci-eng- jamespage, https://bileto.ubuntu.com/#/ticket/2926 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[08:42] -queuebot:#ubuntu-ci-eng- seb128, https://bileto.ubuntu.com/#/ticket/2927 Preparing packages
[08:43] -queuebot:#ubuntu-ci-eng- seb128, https://bileto.ubuntu.com/#/ticket/2927 artful/indicator-session: Failed to commit https://code.launchpad.net/~jbicha/indicator-session/lp1600502-fix-icon-install. You must supply either a Commit Message on your MP, or a custom debian/changelog entry
[08:45] -queuebot:#ubuntu-ci-eng- seb128, https://bileto.ubuntu.com/#/ticket/2927 Preparing packages
[08:46] -queuebot:#ubuntu-ci-eng- jamespage, https://bileto.ubuntu.com/#/ticket/2926 Ready to build
[09:07] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2928 Preparing packages
[09:09] -queuebot:#ubuntu-ci-eng- seb128, https://bileto.ubuntu.com/#/ticket/2927 Destination version missing from changelog
[09:16] -queuebot:#ubuntu-ci-eng- seb128, https://bileto.ubuntu.com/#/ticket/2927 Publishing packages
[09:17] -queuebot:#ubuntu-ci-eng- seb128, https://bileto.ubuntu.com/#/ticket/2927 Publish failed: Destination version missing from changelog
[09:28] -queuebot:#ubuntu-ci-eng- seb128, https://bileto.ubuntu.com/#/ticket/2927 Destination version missing from changelog
[09:30] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2928 Failed to build (artful/indicator-datetime). Pending binary packages (artful/indicator-power, artful/indicator-sound)
[09:36] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2892 Currently building (artful/compiz). Failed to build (artful/nux, artful/unity)
[09:50] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2928 Failed to build (artful/indicator-datetime). Successfully built (artful/indicator-power, artful/indicator-sound)
[09:54] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2892 Failed to build (artful/nux, artful/unity). Pending binary packages (artful/compiz)
[10:14] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2892 Failed to build (artful/nux, artful/unity). Successfully built (artful/compiz)
[10:32] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2848 Preparing packages
[10:53] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2848 Preparing packages
[11:52] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2848 Pending binary packages
[12:11] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2848 Successfully built
[12:24] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2929 Preparing packages
[12:25] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2929 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[12:50] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2929 Diff missing
[13:30] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2848 Publishing packages
[13:30] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2848 Publish failed: Bad merges
[13:32] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2928 Preparing packages
[13:50] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2928 Failed to build (artful/indicator-datetime). Successfully built (artful/indicator-power, artful/indicator-sound)
[13:52] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2848 Successfully built
[14:50] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2929 Pending binary packages
[14:59] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2918 Diff missing (artful/qemu). Pending binary packages (artful/ipxe)
[15:19] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2918 Diff missing
[15:36] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2928 Preparing packages
[16:11] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2928 Successfully built
[16:56] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2916 Failed to build (artful/gnome-shell). Needs rebuild due to burned version number (artful/budgie-desktop). Needs rebuild due to higher version at destination (artful/mutter). Successfully built (artful/gnome-shell-extensions)
[21:16] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2916 Failed to build (artful/gnome-shell). Needs rebuild due to higher version at destination (artful/budgie-desktop, artful/mutter). Successfully built (artful/gnome-shell-extensions)
[21:45] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2924 /: Failed to update local lp:~tdaitx-bileto/autopkgtest/+git/autopkgtest cache
[21:47] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2924 Preparing packages
[21:51] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2930 Preparing packages
[22:05] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2924 Successfully built
[22:11] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/2930 Successfully built


[14:54] <alkisg> Eickmeyer: I went to #edubuntu to say good luck but it was empty! So I'll do it here instead, good luck! :)
[14:55] <Eickmeyer> alkisg: We're there! Wanted to discuss some LTSP stuff with you for future releases, actually.
[14:55]  * arraybolt3[m] pokes head in to say hi
[14:56] <alkisg> Stupid matrix said "1 user in edubuntu" :/
[14:56] <arraybolt3> Way more than 1 user in there.
[14:57] <arraybolt3> And there's another channel I accidentally fell out of last IRC client switch. *sigh*
[15:34] <leftyfb> did we give up on #ubuntu-release-party? No bot there and only 22 people
[15:36] <lotuspsychje> the partys on freenode were bigger
[15:37] <leftyfb> the chat was constantly scrolling
[15:37] <lotuspsychje> yeah
[15:37] <ravage> the messages are just held back until you attach your pro key to the channel
[15:38] <lotuspsychje> lol
[17:27] <aaronprisk[m]> Happy Release Day IRC folks!
[17:29] <oerheks> !party
[17:35] <gjolly> Hello, I would like to update my post here: https://discourse.ubuntu.com/t/find-ubuntu-images-on-azure/34259 to be able to add the new Lunar offer on Azure. But it's been more that 30days since I wrote it and I lost the ability to edit it. Can someone with enough permissions help me there?
[17:50] <aaronprisk[m]> Hey gjolly can you try to edit that topic now and let me know if it works?
[18:01] <gjolly> aaronprisk[m]: it works thanks!


[16:59] <astraljava> Is there anyone here for the Ubuntu Studio contributors meeting?
[16:59] <knome> o/
[16:59] <astraljava> Whee! :)
[16:59] <knome> +l?
[16:59] <knome> :P
[17:10] <astraljava> Ok, maybe next time, then.


[09:35] <apw> chiluk, they should be hanging out here really, too.
[09:38] <apw> chiluk, passed that bug over to someone in the team ...
[12:10] <chiluk> Apw rtg built a few kernels I need to finish testing.


[06:18] <kvalo> morning
[06:19] <spikeb> good morning
[06:19] <kvalo> good morning spikeb
[07:46] <kamstrup> morning everyone
[07:48] <smspillaz> DBO: the paint attributes ?
[07:48] <smspillaz> DBO: gWindow->paintAttrib ()
[07:48] <DBO> smspillaz, yes
[07:48] <smspillaz> (sorry about the delay(
[07:49] <DBO> oh I can just set that anytime?
[07:49] <smspillaz> no you can't just set it any time
[07:49] <smspillaz> that's the *last
[07:49] <smspillaz> *last
[07:49] <smspillaz> arhg
[07:49] <smspillaz> *last* paint attribu
[07:49] <smspillaz> to set it you have to wrap either glPaint or glDraw and do it there
[07:50] <smspillaz> if it's in the unity plugin I suggest wrapping glDraw, and then doiing GLFragment::Attrib fA (fragment);
[07:50] <smspillaz> and then modifying it, eg fA.setSaturation (foo);
[07:50] <DBO> its a const in glPaint
[07:50] <smspillaz> and then passing the chain
[07:50] <smspillaz> DBO: that's the point
[07:50] <DBO> OH!
[07:50] <smspillaz> DBO: you copy it, modify it and then call the gWindow->glPaint (myAttribute, foo);
[07:50] <smspillaz> DBO: wrap chains
[07:51] <smspillaz> DBO: I would wrap glDraw though
[07:51] <smspillaz> since wrapping two functions is more expensive than one
[07:51] <DBO> yes but onestone made it very clear to me that doing any modifications like that in gldraw is evil
[07:51] <smspillaz> because other plugins don't catch it
[07:51] <smspillaz> this is correct
[07:52] <smspillaz> however, since we are loaded last, that doesn't really matter
[07:52] <smspillaz> DBO: do it in glDraw unless you want the fade plugin to automatically fade your modifications
[07:53] <smspillaz> DBO: I think "dock" and "sticky" conflict and make core stack it like a normal window
[07:53] <DBO> nope
[07:53] <DBO> checked that
[07:53] <smspillaz> at least it was something and dock that conflicted
[07:53] <DBO> its acting right now that I made the windows input/output
[07:53] <smspillaz> weird
[07:54] <smspillaz> DBO: might be doing weird things because it's not attrib.is_viewable
[07:54] <smspillaz> DBO: be warned though, I hate touching the stacking code
[07:55] <smspillaz> it's such a bloody mess
[07:55] <smspillaz> so in reality I am doing a very big favor for you :)
[07:55] <didrocks> good morning
[07:56] <smspillaz> DBO: window.cpp:2051
[07:56] <RAOF> smspillaz: Do you want to debug your intel problem sometime?
[07:57] <smspillaz> RAOF: yeah, but not right now
[07:57] <smspillaz> RAOF: I can boot in safe mode and work from there
[07:57] <smspillaz> DBO: err priv->attrib.map_state
[07:57] <RAOF> Ok.  In your own time :)
[07:57] <smspillaz> RAOF: thx
[07:57] <kvalo> kamstrup: good morning. feeling better now?
[07:58] <smspillaz> didrocks: I got the GFile stuff done btw
[07:58] <DBO> smspillaz, Im working on this shiz I almost got it working right
[07:58] <kamstrup> kvalo: yeah, a bit. Will start your review now
[07:58] <smspillaz> DBO: I hate the stacking code with a passion
[07:58] <didrocks> smspillaz: oh nice! for both backend I guess? Did you get some testing?
[07:58] <smspillaz> didrocks: yes it works fine
[07:58] <smspillaz> didrocks: patches are in your inbox
[07:59] <didrocks> smspillaz: nice!
[07:59] <didrocks> smspillaz: btw, I finally understand the "profile" system
[07:59] <smspillaz> cool :)
[07:59] <didrocks> smspillaz: and why we get this "bug" yesterday
[07:59] <didrocks> in fact, it's a bug, and we don't need my patch :)
[08:00] <smspillaz> cool
[08:00] <smspillaz> what was the bug?
[08:00] <didrocks> looking at the code, the "profile" as the environment variable set (the "general_<profile>") is adding a new "session tpe"
[08:00] <didrocks> so, general_unity is a session type
[08:00] <smspillaz> yeah, that's the point
[08:00] <didrocks> if you change the profile there, it will affect the profile= in general_unity
[08:01] <didrocks> so, you're safe for other session
[08:01] <DBO> smspillaz, how do I just make a window not draw then?
[08:01] <didrocks> it's just a shame that both notions are called "profile", so confusing :)
[08:02] <smspillaz> DBO: this is a massive hack and half, but wrap glPaint and do mask |= PAINT_WINDOW_NO_CORE_INSTANCE_MASK
[08:02] <DBO> what?
[08:02] <DBO> there is no way to make a window just not paint?
[08:02] <smspillaz> DBO: there's a variable called "mask" in glPaint, if you do that then it won't be painted period
[08:02] <smspillaz> DBO: err you could be a little smarter actually
[08:03] <smspillaz> DBO: do you mind if I can see your code and write something to do that?
[08:03] <MacSlow> greetings erverybody
[08:03] <smspillaz> DBO: basically we'll just pop your nux windows from the paint list
[08:03] <MacSlow> hey smspillaz
[08:03] <smspillaz> MacSlow: hi
[08:03] <DBO> smspillaz, painting with 0 opacity works too
[08:03] <DBO> but it seems to paint regardless
[08:03] <smspillaz> DBO: yeah, I'll do my solution
[08:04] <smspillaz> DBO: push your code to some branch and I'll do the bits to pop it from the paint stack
[08:04] <DBO> smspillaz, https://pastebin.canonical.com/40163/
[08:04] <smspillaz> DBO: push your code to some branch and I'll do the bits to pop it from the paint stack
[08:04] <smspillaz> ;-)
[08:04] <DBO> ah fuck I just want to know how to make its opacity 0
[08:04] <DBO> why does that not work?
[08:04] <DBO> you can do your thing after I learn
[08:04] <smspillaz> DBO: making the opacity zero is one way to do it but you are still darwing the window with opengl = stupid
[08:05] <DBO> no no
[08:05] <DBO> it does not work
[08:05] <DBO> the window is still drawn
[08:05] <DBO> thats what I am saying
[08:05] <MacSlow> hey DBO
[08:05] <DBO> hey MacSlow
[08:06] <smspillaz> DBO: try copying attrib
[08:06] <didrocks> smspillaz: looking at your patch
[08:06] <DBO> why?
[08:06] <MacSlow> salut didrocks
[08:06] <smspillaz> DBO: eg GLWindowPaintAttrib fA (attrib);
[08:06] <didrocks> smspillaz: you don't remove .config/compiz-1/compizconfig for existing users?
[08:06] <smspillaz> DBO: this is how the other plugins do it, just try it
[08:06] <smspillaz> didrocks: no, we just merge the old config
[08:06] <didrocks> smspillaz: so it will end as .config/compiz-1/compizconfig/compizconfig, isn't it?
[08:06] <didrocks> smspillaz: oh ok :)
[08:06] <didrocks> nice, (just had a quick lookà
[08:07] <didrocks> Guten Morgen MacSlow
[08:07]  * didrocks enjoys tooltips :)
[08:07] <DBO> still paints it
[08:07] <kamstrup> kvalo: it's this one right? https://code.launchpad.net/~kvalo/indicator-network/libconnman-backend/+merge/41734
[08:08] <didrocks> smspillaz: waow, it's a very C++ way of using glib :) but looks good!
[08:08] <smspillaz> DBO: weird. maybe it hates you
[08:08] <smspillaz> didrocks: hehe
[08:08] <smspillaz> DBO: did you pass fA to glDraw instead of attrib ?
[08:08] <DBO> yes
[08:08] <smspillaz> hmm wtf
[08:08] <didrocks> kamstrup: hey dude! feeling better?
[08:08] <kvalo> kamstrup: yes, that's it
[08:09] <smspillaz> DBO: stick an fprintf on line 11 and make sure it is actually changing the opacity
[08:09] <smspillaz> DBO: also make sure the screen is damaged
[08:09] <DBO> i did
[08:09] <smspillaz> or window rather
[08:09] <DBO> its hitting
[08:09] <kamstrup> didrocks: yeah, I manage, not fully back to normal, but I think I can code :-)
[08:09] <smspillaz> argh wtf
[08:09] <didrocks> kamstrup: unstoppable!
[08:09] <smspillaz> DBO: use fire to trigger full screen repaints and see if it is actually damaging
[08:09] <DBO> doing it glPaint worked
[08:10] <smspillaz> DBO: yeah, weird
[08:10] <DBO> whatev
[08:10] <DBO> it works now
[08:10] <smspillaz> DBO: oh right, I think you need to set PAINT_WINDOW_BLEND_MASK or something for it to work
[08:10] <smspillaz> and glPaint will do that
[08:10]  * smspillaz has a look at the code
[08:11] <DBO> okay whatever
[08:11] <DBO> the point is it works
[08:11] <DBO> and much nicer
[08:11] <smspillaz> DBO: cool
[08:11] <smspillaz> DBO: however, I know of a better way to do this
[08:11] <DBO> you can fix it after I push
[08:11] <smspillaz> DBO: push your code somewhere
[08:11] <MacSlow> hey kvalo, kamstrup
[08:11] <MacSlow> kamstrup, so feeling a bit better now?
[08:12] <MacSlow> didrocks, everything should even look nicer by monday
[08:12] <kvalo> MacSlow: hi
[08:12] <smspillaz> DBO: actually, I think the way core was stacking the windows the way it was is because there is no usecase for invisible dock windows
[08:12] <smspillaz> well inputonly ones
[08:12] <DBO> smspillaz, I dont want to mess with core stacking
[08:12] <DBO> we can use inputoutput windows
[08:12] <DBO> its safer
[08:12] <smspillaz> yeah fair enough
[08:13] <smspillaz> still seems like  hack to me though
[08:13] <DBO> it is
[08:13]  * smspillaz hears kittens dying
[08:13] <DBO> but there are two options here
[08:13] <smspillaz> DBO: hey are you using the glibmm branch?
[08:13] <didrocks> MacSlow: you mean, working QL with pin/unpin? :)
[08:13] <DBO> A) Fix compiz handling of invisible dock windows
[08:13] <DBO> B) Use visible dock windows and get sane stacking
[08:14] <DBO> A) is correct but wont be ready for Natty
[08:14] <DBO> B) is a hack but works right now
[08:14] <smspillaz> DBO: actually, inputOutput sort of makes sense in terms of a broader future
[08:14] <DBO> I choose b
[08:14] <MacSlow> didrocks, not working on the logic right now... but this will come too of course
[08:14] <DBO> smspillaz, the changes are in trunk
[08:14] <DBO> you must update nux and compiz
[08:15] <DBO> nux and unity rather
[08:15] <DBO> smspillaz, I am not using glibmm
[08:15] <DBO> did you merge that into the master DBO branch?
[08:16] <smspillaz> DBO: no I have not yet
[08:16] <smspillaz> DBO: there is some stupid bug
[08:16] <DBO> fix that, then do so :)
[08:16] <smspillaz> calls to null timers
[08:16] <smspillaz> yeah
[08:16] <smspillaz> the problem is
[08:16] <smspillaz> I can't figure out how to reproduce it reliably
[08:17] <smspillaz> i was wondering if you had
[08:21] <DBO> no
[08:21] <DBO> I have sent an email to the dx-team list explaining the change to InputOutput windows
[08:22] <smspillaz> cool
[08:22] <DBO> can we enforce window resizing on map?
[08:22] <DBO> so that if a window is too big for the screen, it resizes down
[08:23] <smspillaz> DBO: in core?
[08:23] <DBO> in place I would assume
[08:23] <smspillaz> DBO: I think place does it already
[08:23] <DBO> it fails
[08:23] <DBO> or more accurately, it doesn't take panels into account
[08:23] <smspillaz> only for certain window types though
[08:23] <smspillaz> yeah well resizing panels makes no sense
[08:23] <DBO> actually
[08:23] <smspillaz> panels should be smarter than that ;-)
[08:24] <DBO> do we sitll have the panel shadow hack?
[08:24] <smspillaz> no
[08:24] <smspillaz> you can task me to port that patch though
[08:25] <smspillaz> DBO: still no mail re the inputoutput windows
[08:26] <DBO> I just got it
[08:26] <DBO> so it worked
[08:31] <DBO> alright I think thats it for me
[08:35] <didrocks> reboot, brb
[08:43] <smspillaz> DBO: night
[08:44] <smspillaz> DBO: BTW one thing you'll come to love about compiz is that you can change the paint list to anything you like
[08:44] <smspillaz> like, anything
[08:44] <smspillaz> the order in which windows are painted is completely pluggable
[08:44] <smspillaz> also you can change the stacking order
[08:48] <didrocks> smspillaz: I hate this profile thing! With the latest backend, I couldn't get the gconf key picked up (and yes, I have /options at the end this time :p)
[08:48] <didrocks> (under compizconfig-1 of course)
[08:49] <didrocks> and it says it starts the "unity" profile
[08:55] <didrocks> smspillaz: if I try to add it to ccsm, it added it to the "Default" profile, even if I have the unity profile selelcted in ccsm…
[08:55] <spikeb> does anyone actually like any aspect of this? ;)
[08:56] <didrocks> smspillaz: also, it's dumping the it under compiz-1/general*/options/active_plugins … sounds like a mess :)
[09:02] <smspillaz> didrocks: with the transition thing?
[09:02] <smspillaz> didrocks: soudns like a bug
[09:02] <didrocks> smspillaz: I think it's not impacted by the transition thing
[09:02] <didrocks> yeah, sounds like a bug :)
[09:02] <didrocks> one sec, run after some plug
[09:02] <smspillaz> didrocks: sure
[09:04] <didrocks> ok so
[09:04] <didrocks> I've resetted all my gconf tree for /apps/compiz*
[09:04] <didrocks> first, I have a leftover to /apps/compiz, even after the reset
[09:04] <didrocks> sounds like there is a schema installing something there
[09:05]  * didrocks greps
[09:06] <didrocks> ok, they come from compiz-gnome
[09:06] <didrocks> which is part of compiz-core
[09:06] <didrocks> and they all install in /apps/compiz
[09:07] <didrocks> ok, ./xslt/compiz_gconf_schemas.xslt needs to be updated
[09:07] <didrocks> smspillaz: fixing and pushing
[09:08] <smspillaz> didrocks: ahhhh right
[09:08] <smspillaz> yes good find
[09:10] <didrocks> well, not the source of the issue but at least, will help to get a cleaner gconf view of it :)
[09:12] <kamstrup> kvalo: !
[09:12] <kamstrup> kvalo: phew, I'm done :-)
[09:12] <kamstrup> kvalo: very nice, although there where a few leaks so I marked it needsfixing
[09:14] <kvalo> kamstrup: yeah, it was a long one :(
[09:14] <kamstrup> kvalo: it's ok. The code is quite nicely structured that helps a lot
[09:14] <kvalo> kamstrup: cool
[09:15] <njpatel> kamstrup, feeling better?
[09:15] <didrocks> smspillaz: I think that's why as well compizconfig-plugin-main and unity didn't install their gconf schemas recently
[09:15] <njpatel> didrocks, morning dude
[09:15] <didrocks> hey njpatel!
[09:15] <kamstrup> njpatel: it's ok, not fully steaming yet, but good enough to hack :-)
[09:16] <kvalo> kamstrup: I need help with gvariant and "a(oa{sv})". do you know any examples how to properly parse that beast?
[09:17] <didrocks> smspillaz: really, the first day I have some time for hacking, I'll split the 2 "profiles" notion to get "session_type" and "profile"… the code will look so much cleaner
[09:17] <didrocks> having one word for two things makes the debugging sooooo confusing
[09:18] <kamstrup> didrocks: you could also try to profile the profile code ;-)
[09:18] <didrocks> kamstrup: sure, but which part of the "profile code", the profile one or the other profile one? :)
[09:18]  * kamstrup blows up
[09:19] <njpatel> didrocks, NNNOOO you killed kamstrup !
[09:19] <didrocks> :)
[09:19] <njpatel> He still has places work to do!
[09:19] <njpatel> As I told jason yesterday, "you can't be unwell, it's not convenient for me"
[09:19] <spikeb> haha
[09:20] <didrocks> excellent! that's team work :)
[09:21] <kvalo> kamstrup: and actually I don't know how to even create such a variant. I'm trying to implement a simple test case for this.
[09:21] <didrocks> hum? why sladen uploaded unity?
[09:21] <didrocks> it was not the problem…
[09:22] <didrocks> and of course, it blows a non working unity because of it
[09:23] <didrocks> sladen: please, I discussed that publicly in #ubuntu-desktop yesterday to tell to anyone to fix the FTBFS, it was intentional…
[09:24] <kamstrup> kvalo:  sure. that's easy
[09:24] <smspillaz> someone review and merge this https://code.launchpad.net/~canonical-dx-team/unity/unity.remove-io-from-pl/+merge/41936
[09:25] <smspillaz> didrocks: I'll update the glibmm branch to account for your changes
[09:25] <didrocks> smspillaz: ok, but I take that as a distro-patch for now, just rebuilding everything there first
[09:26] <smspillaz> didrocks: did you commit the gconf xml builder upstream ?
[09:26] <smspillaz> err xslt
[09:26] <smspillaz> njpatel: can you review ^^^
[09:26] <didrocks> smspillaz: not yet, I'm finishing to rebuild every schema to ensure it's building right things
[09:26] <smspillaz> didrocks: sure
[09:26] <didrocks> so unity is broken in natty now… thanks sladen
[09:27] <njpatel> smspillaz, taking a look now
[09:28] <MacSlow> didrocks, what's wrong?
[09:28] <didrocks> MacSlow: sladen fixed a ftbfs due to a wrong compiz gconf schema compiler
[09:29] <didrocks> MacSlow: I let it FTBFS yesterday when leaving and told on public chan to not fix it and wait for the new compiz
[09:29] <didrocks> but well… apparently some people just thought "let's remove the gconf schema"…
[09:29] <MacSlow> didrocks, *sigh*
[09:29] <didrocks> of course, there is no update in the bzr vcs packaging, let's discare people working on it
[09:33] <didrocks> I won't add that renaming closed bug is worthless… but well
[09:44] <kvalo> kamstrup: sorry, but it's not easy for me :)
[09:46] <kvalo> kamstrup: I would imagine creating a variant is like this, but no luck: http://paste.ubuntu.com/536612/
[09:46] <kamstrup> kvalo: ok, so it's about parsing it right?
[09:46] <kvalo> kamstrup: parsing is what I need, but I got also interested about creating
[09:55] <kamstrup> kvalo: just cooking up an example
[09:56] <kvalo> kamstrup: thank you very much
[09:58] <njpatel> smspillaz, approved
[10:00] <smspillaz> njpatel: thanks
[10:00] <smspillaz> njpatel: also I know what is causing that timers bug in glibmm
[10:00] <smspillaz> njpatel: timer gets destroyed and glib tries to call the timeout callback func
[10:01] <smspillaz> at which point it fails miserably when we start reading free'd memory
[10:01] <smspillaz> this is not good
[10:01] <njpatel> no
[10:01] <njpatel> it's no good :)
[10:01] <smspillaz> the thing is, I have no idea really how to fix it other than change the timer model
[10:02] <smspillaz> since it doesn't look like there's a way to force remove a timer from a source
[10:02] <njpatel> remove a timeout from glib?
[10:02] <smspillaz> in glibmm
[10:02] <njpatel> g_source_remove
[10:03] <njpatel> GLib::Source::Remove ;)
[10:03] <smspillaz> and that will work 100% ?
[10:03] <njpatel> g_timeout_add returns a guint
[10:03] <njpatel> g_source_remove (uint) will remove it
[10:03] <smspillaz> I'm talkking about glibmm though
[10:04] <smspillaz> all I can find is destroy ()
[10:04] <smspillaz> which could very well work
[10:07] <kamstrup> kvalo: something ala http://paste.ubuntu.com/536622/ it's probably not the most optmized way of doing this, but it should work (although it's completely untested)
[10:07] <kamstrup> kvalo: I use that technique in libzeitgeist at least
[10:08] <kamstrup> kvalo: There are some fairly complex marshalling in libzeitgeist you can look at
[10:08] <kvalo> kamstrup: thanks a lot! don't worry about testing, I can do that
[10:08] <kamstrup> kvalo: especially in zeitgeist-event.c
[10:08] <kvalo> kamstrup: thanks, I'll write that down :)
[10:09] <njpatel> smspillaz, sorry, network issues
[10:09] <njpatel> smspillaz, I'm not sure about glibmm sorry
[10:09] <njpatel> quick look at the source cpp would figure that out
[10:10] <smspillaz> yeah
[10:11] <kamstrup> smspillaz, njpatel: We need g_source_remove() because we don't have pointers to the GSource which are required by g_source_destroy() I take it?
[10:17] <kamstrup> smspillaz: wow, gsource handling in glibmm does not look very nice...
[10:18] <murrayc_> This is why I mentioned this bug yesterday:
[10:18] <murrayc_> https://bugzilla.gnome.org/show_bug.cgi?id=561885
[10:18] <kamstrup> but I guess you must consult the documentation of sigc::connection on how to disconnect a handler. Given that you connect the timeout with Glib::signal_timeout().connect(sigc::ptr_fun(&timeout_handler), 1000);?
[10:18] <murrayc_> Timeout handlers can be disconnected just by returning the right true/false, surely?
[10:19] <murrayc_> gobj() can get your the GSource*, if that helps.
[10:20] <smspillaz> murrayc_: yeah that might work
[10:20] <smspillaz> as a last minute hack
[10:20] <smspillaz> I was thinking of changing CompTimer to PIMPL though and removing the priv bits when needed
[10:20] <murrayc_> (I have not looked at that bug in detail. I have not particular thoughts about it because I don't use that API myself and I don't have much time.)
[10:20] <smspillaz> I'll do that when I get back
[10:22] <smspillaz> murrayc_: BTW that's not the bug
[10:22] <smspillaz> thje bug is my fault
[10:24] <murrayc_> smspillaz: Well, I'd generally like it to be much clearer what all this remove/destroy stuff is about. It's not clear to me in the C docs either.
[10:26] <murrayc_> And I really have no idea what it's even used for.
[10:29] <murrayc_> I guess GSource is just a way to use a timeout or idle callback with a non-default GMainLoop?
[10:46] <kvalo> kamstrup: thanks, I have the beast in control now :)
[10:49] <dbarth> didrocks: hey Didier; i've just had a compiz crash, but it was not automatically restarted by the session
[10:49] <dbarth> didrocks: is that in the new packages?
[10:49] <kvalo> kamstrup: do you prefer I describe the class structure in a separate doc (eg readme) or in each source file?
[10:49] <didrocks> dbarth: hum, it should, not sure, I've on other fish right now but will check later…
[10:50] <didrocks> dbarth: what do you have as required_components on gconf?
[10:50] <dbarth> checking
[10:51] <dbarth> window_manager is there, and is set to compiz elsewhere
[10:52] <dbarth> so maybe a but in gnoime-session then
[10:52] <dbarth> ahj sorry, metacity was first in the list
[10:52] <didrocks> dbarth: well, the respawn should work, if you want, let's discuss that later, the gconf backend of compiz is totally broken and I have to fix it today…
[10:52] <dbarth> sure
[10:52] <mhr3> Cimi, hey, i got a question - do you have docky installed?
[10:53] <Cimi> no
[10:53] <Cimi> oh no, I have
[10:53] <Cimi> not running though
[10:53] <mhr3> cool, could you run it and open the settings window
[10:54] <didrocks> hum, it seems libcompizconfig is asking for the profile before setting the new default… nice
[10:54] <Cimi> mhr3: what's the problem?
[10:54] <mhr3> Cimi, there when you do to docklets, i see that the component that is being used has very bad contrast in maverick with the default theme
[10:54] <Cimi> yeah known bug
[10:54] <Cimi> I guess it's a bug in dicky
[10:54] <Cimi> *docky
[10:55] <mhr3> Cimi, yea, we use the same component elsewhere, could you give me a few hints how to fix it?
[10:55] <Cimi> sure
[10:55] <mhr3> Cimi, basically it's painting the bg using paint_flat_box() with detail cell_odd
[10:55] <mhr3> and the labels have StateType.SELECTED
[10:56] <Cimi> I fixed that in software center
[10:57] <mhr3> got a link to revision with the diff that fixes it? :)
[11:01] <Cimi> here we go mhr3 : http://bazaar.launchpad.net/~cimi/software-center/fix-lp-bug-635208/revision/1243
[11:05] <mhr3> Cimi, thanks
[11:13] <didrocks>  current_profile = Schema (type: `string' list_type: '*invalid*' car_type: '*invalid*' cdr_type: '*invalid*' locale: `C')
[11:13] <didrocks> hum, I think I found something :)
[11:14]  * didrocks likes monolog in detective mode :)
[11:16] <kamstrup> w00t!
[11:16] <kamstrup> I have a compiz that no longer segfaults!
[11:16] <kamstrup> adding tooltips to the launcher even :-)
[11:17] <njpatel> kamstrup, you know what the issue with the tooltips was?
[11:17] <kamstrup> njpatel: nope?
[11:17] <njpatel> kamstrup, "%s %.2f" is "Ubuntu 12,00" on some locales
[11:17] <njpatel> (comma)
[11:17] <njpatel> which breaks pango
[11:17] <kamstrup> lol!
[11:18] <kamstrup> njpatel: let me politely ask how on earth that could break Pango?
[11:18] <kamstrup> njpatel: oh, it's for configuring the font
[11:18] <njpatel> yep
[11:18] <didrocks> kamstrup: I was the guinee pig for that, they have made me compile horrible stuff, if you knew!
[11:18] <njpatel> so pango doesn't get the font string proper so it decides to ignore it completely
[11:19] <didrocks> and will still see that njpatel hates French :) (and so, not only French it seems :))
[11:19] <njpatel> it's not really pangos fault, but something I've never come across
[11:19] <njpatel> didrocks, MacSlow coded that :)
[11:19] <njpatel> He hates the french too
[11:19] <njpatel> ;)
[11:19] <didrocks> njpatel: well, I don't doubt it as well :)
[11:19] <kamstrup> really - Unity should not support i18n or l10n. No a11y or Unicode. Strict ASCII and monospace fonts everywhere
[11:20] <kamstrup> And only one resolution as well of course
[11:20] <nigelb> 800 x 600 one
[11:20] <njpatel> yep, whatever is perfect for my screen
[11:20] <kamstrup> indeed
[11:21]  * njpatel will change it before release weekly
[11:21] <njpatel> 1440x900
[11:21] <kamstrup> njpatel: yeah, you should be tech lead on Unity
[11:21] <kamstrup> njpatel: oh, wait... you are ;-)
[11:21] <njpatel> heh, coding style and screen resolution: the two perks of tech lead
[11:21]  * didrocks will distro-patch njpatel's change :)
[11:22] <didrocks> \o/
[11:22] <kamstrup> njpatel, didrocks: So Unity is basically a Hello World in Gtk+. The rest is just a huge distropatch
[11:22] <didrocks> kamstrup: what else it can be? :-)
[11:22] <njpatel> didrocks, that's fine, I'll just use the "pure" packaging from debian :p
[11:22] <njpatel> kamstrup, lol
[11:23] <didrocks> njpatel: ahah, raphael proposed me to maintain unity in debian! :-)
[11:23] <didrocks> you're stuck, dude!
[11:24] <didrocks> you won't espace from Monkey Isl… oh wait!
[11:26] <njpatel> nooooooo
[11:30] <kamstrup> lol, I love the attention call from the launcher :-D
[11:30] <kamstrup> the icon just peeks in from the left, only half way in... Looks like "Uh, I'm most sorry to bother you, but there's thing... I think you need to check it out"
[11:31] <MacSlow> kamstrup, didrocks, njpatel: it's an issue with proper locale-aware parsing of float-values
[11:31] <kamstrup> MacSlow: oh I thought it was intentional that it only came halfway in
[11:32] <MacSlow> kamstrup, didrocks, njpatel: this nasty-ness chooses to show up at the oddes of moments
[11:37] <njpatel> kamstrup, it's really cute right?
[11:37] <njpatel> kamstrup, have you seen when you minimise? it comes out to collect the window if you have zoom animation on
[11:37] <kamstrup> njpatel: uh... i can haz blong!?
[11:37] <kamstrup> (blong is the new bling)
[11:37] <njpatel> heh
[11:38] <njpatel> kamstrup, ccsm ->animations (enable if needed)-> minimise (make sure it's "zoom")->Effect Settings tab-> Zoom -> Spinginess = 0.8
[11:40] <kamstrup> njpatel: stop tricking my into crashing compiz!
[11:40] <njpatel> woops! sorry :/
[11:43] <kamstrup> njpatel: wow, that's crazy bling!
[11:44] <kamstrup> it works now, although it seems that the new compiz is not so fond of the Magic Lamp animation
[11:44] <njpatel> heh :D
[11:44] <njpatel> kamstrup, what happens?
[11:44] <kamstrup> njpatel: crash
[11:44] <kamstrup> njpatel: but kudos to whoever did the zoom thingi
[11:44] <kamstrup> njpatel: I was just trying if Magic Lamp would swirl into the launcher as well
[11:45] <njpatel> yeah, it should do
[11:46] <didrocks> njpatel: 0.8, not 0.08?
[11:47] <njpatel> i thought 0.8
[11:47] <njpatel> might be wrong
[11:49] <didrocks> njpatel: it was 0.08, but it's as you wish :)
[11:52] <MacSlow> hey seiflotfy, hyperair
[11:52] <hyperair> hey MacSlow
[12:18] <kvalo> kamstrup: pushed fixes: https://code.launchpad.net/~kvalo/indicator-network/libconnman-backend/+merge/41734
[12:30] <sladen> didrocks: my apologies if your FTBFS upload was intentional
[12:31] <didrocks> sladen: the FTBFS wasn't, but then, I realized that my local compiz version which was more up-to-date than the one on natty infered on that
[12:31] <didrocks> sladen: so, I went to #ubuntu-desktop, as people concerns by those components are there and warned about it
[12:31] <didrocks> telling that I have some fixes to do on compiz first
[12:32] <sladen> didrocks: yup, compiz is broken (the one in the PPA sort of works).  what do you want to do about libnux which has a cast alignment warning for ARM (it's not actually an error per se)
[12:32] <didrocks> so currently, all people upgrading won't have unity by default in my next upload
[12:33] <didrocks> sladen: no compiz isn't broken in natty, the migration is
[12:33] <didrocks> sladen: because upstream didn't migrate
[12:33] <didrocks> sladen: for nux, the ARM issue is already signaled upstream
[12:37] <didrocks> I think asking to people responsible on components first is what should be done… especially when others as little knowledge in it.
[12:37] <didrocks> for instance, I won't upload gtk or glib without asking seb128
[12:40] <sladen> didrocks: I wouldn't do an upload of a package, but I'd generally be quite happy to do a trival FTBFS fix.   Again my apologies if the upload was intentionall broken
[12:40] <didrocks> sladen: yeah, but your "trivial fix" is breaking people
[12:40] <sladen> didrocks: and had the trival fix been there anyway, it would have broken anyway
[12:41] <didrocks> sladen: well, it wasn't published
[12:41] <didrocks> sladen: so people won't get it
[12:41] <sladen> didrocks: that it happened not to build seemed to have been a retrospective stroke of luck
[12:41] <didrocks> sladen: no, because I tested on the new compiz there
[12:41] <didrocks> with fixed one
[12:41] <didrocks> which doesn't break the gconf schema generation
[12:42] <sladen> excellent
[12:42] <didrocks> …
[12:42] <didrocks> I won't comment…
[12:43] <sladen> didrocks: if you want another answer, tell me, and I'll give it
[12:44] <didrocks> sladen: I hope that the answer is just "stop uploading things when you aren't on the channel of people there"
[12:44] <didrocks> especially when there is no gate
[12:44] <didrocks> and you knew I would wake up the day after
[12:44] <sladen> didrocks: I _didn't_ do the initial broken upload
[12:45] <didrocks> sladen: the "broken upload" as you told, was because I had a newer compiz, and so, the fact that the old one is still on natty made it FTBFS
[12:45] <didrocks> but a FTBFS == don't reach the user
[12:45] <didrocks> so, it can wait for 10 hours
[12:45] <didrocks> making a broken package == reach the users
[12:45] <didrocks> and there, you are breaking them
[12:46] <sladen> didrocks: excellent, I've reprogrammed my internal state machine that trivally broken package uploads by didrocks are intentional.  Done.  I'll file a bug and patch next time if you were the uploader
[12:47] <sladen> didrocks: remember that we operate on a source code level in Debian/Ubuntu.  What's published is the source code and used for version differiation is the source code
[12:47] <didrocks> sladen: stop with that tone… of course the upload wasn't intentional, but it seems you know CMake internals and to check that includes files are still compiling gconf schema
[12:48] <didrocks> sladen: remember that we work as a team
[12:48] <didrocks> sladen: seems you are not…
[12:48] <sladen> didrocks: and not the binaries, which are merely an installation optimisation... apt-get source  returns the broken version
[12:48] <didrocks> sladen: sure, but did you needed to apt-get source that one?
[12:49] <didrocks> why rushing fixing a broken thing in a buildd when the user isn't impacted?
[12:49] <didrocks> and we are not close to any gate, this could have wait 10 hours
[12:49] <sladen> didrocks: yes, because yesterday you told me that I should be testing unity-compiz rather than unity-mutter
[12:49] <sladen> didrocks: so I went off to ensure I had a (semi-working) environment.
[12:49] <didrocks> sladen: and? is the current situation any better?
[12:50] <sladen> didrocks: I have a semi-working environment, and the archive binaries are aligned to the source code revision
[12:50] <didrocks> if it please you fine, it won't enjoy people not having automatically unity by default then…
[12:52] <didrocks> http://irclogs.ubuntu.com/2010/11/25/%23ubuntu-desktop.html
[12:52] <didrocks> look at [20:15]
[12:52] <didrocks> I reconnected on purpose to warn people…
[13:17] <boulabiar> fagan, hi !
[13:17] <fagan> boulabiar: hi
[13:17] <boulabiar> I need to root android before installing ubuntu there ?
[13:17] <fagan> yep
[13:17] <fagan> thats what I saw when I did a 5 minute google search for it
[13:18] <boulabiar> if you have any links that would be great !
[13:18] <boulabiar> the device support 4 fingers mt, but I need to put ubuntu to deeply test the hw
[13:18] <fagan> give me a sec and ill find a good one
[13:20] <fagan> boulabiar: I have a step by step how to do it on an ac100 and thats the same hardware except the screen so I presume it works
[13:21] <boulabiar> ok, maybe I need to test that first
[13:21] <fagan> well you run it from the sd card or usb first to test it
[13:24] <fagan> boulabiar: http://www.youtube.com/watch?v=5GJsy7FEPak this should work the same on the touchbook thingy
[13:24] <fagan> its the one for the ac100 but they are the same device other than the screen
[13:24] <didrocks> ok, default profiles fixed \o/
[13:25] <fagan> so it should work but I dont know about the touch functionality
[13:25] <didrocks> now, let's see what's changed in the cmake for not building gconf schemas…
[13:25] <boulabiar> fagan, thanks !
[13:27] <fagan> boulabiar: I was playing about with that device for a few minutes a while back and android is just bad on it
[13:27] <fagan> and toshiba have a bit of bloatware on it too
[13:27] <boulabiar> yep
[13:35] <lamalex> morning
[13:37] <fagan> I really hate the way the launcher slides up and down whats that actually meant to do?
[13:40] <kamstrup> kvalo: approved!
[13:40] <didrocks> sladen: the bug on gconf backend migration you mentionned on bug #675307 (some plugins got renamed and upstream hasn't done a migration tool) should be fixed once I upload <IP_ADDRESS>git101125-0ubuntu1.
[13:41] <didrocks> sladen: I don't close the bug as virtualbox issue is different
[13:41] <didrocks> sladen: smspillaz made the patch and test on some hw, I've done the same, but as it's a complex operation, to not hesitate to give any feedback
[13:56] <kamstrup> someone have an i7 with some spare cycles?
[14:05] <sladen> didrocks: renaming closed bugs is not worthlesss... I yesterday filed a dup (after searching for dups) and was told it was a dup... by increasing the search domain on the bug title it increases the chance that it's easier for the next person to find
[14:05]  * lamalex will go out and buy one if he can expense it
[14:06] <sladen> didrocks: and I'd spent 30 minutes specifcally looking for that one bug, so I was /going/ to do something about it :)
[14:07] <didrocks> sladen: I don't think a lot of people is looking in advanced mode the "fix released" bugs (which are ignored by default). But if you do and other do, that's fine :)
[14:07] <didrocks> sladen: hehe, yeah, agree that some bugs title aren't the best they can
[14:07] <didrocks> sladen: sometimes, I only know it's a dup because I'm subscribe to all unity bugs… I try to rename them little by little but getting all mental pattern is hard ;)
[14:08] <sladen> didrocks: yup, I've subbed now... if I see the flow going past I'll have a better idea of what has already gone
[14:08] <seb128> sladen, hi
[14:09] <sladen> didrocks: sorry, I'm only just getting up to speed on Unity---I had ignored it during the previous cycles because it wasn't battery efficient
[14:09] <didrocks> sladen: you should subbed to bamf and nux as well I think (package and upstream task) as most of the bugs will flow on the three
[14:09] <seb128> sladen, btw what didrocks was saying early was "don't upload packages actively maintained without pinging the maintainer before"
[14:09] <didrocks> sladen: no worry about the bug, it's just that it was frustrating from my point of view but now it will be good :)
[14:11] <lamalex> ah man ted has off today..
[14:11] <lamalex> hm
[14:12] <kamstrup> kvalo: if you still have time, bzr branch lp:unity-jhbuild and follow the instructions in the README
[14:12] <kamstrup> kvalo: wait
[14:12] <lamalex> does anyone know how the sound/session indicators set their color? Is it just swapping a different colored icon, or is it actually setting a color and painting it
[14:12] <kamstrup> kvalo: bzr branch lp:unity-jhbuild ~/unity
[14:13] <kamstrup> kvalo: and then follow ~/unity/README
[14:13] <kvalo> kamstrup: on it
[14:13] <kamstrup> kvalo: you can edit ~/unity/unity.hjbuildrc to set the -jN paramter for make if you want
[14:13] <sladen> seb128: right, and I have never generally regardless trival FTBFS to be in that category---the upload was the source code, and for a trival FTBFS has already been done.  The trival patch would not pushed back to the VCS because none was/is listed in the package (implying that it is maintained in the tarball, not a VCS)
[14:13] <sladen> s/regardless/regarded/
[14:13] <sladen> s/would/was/
[14:14] <kamstrup> kvalo: so find makeargs=... and set it to -j4 or what you want
[14:14] <kvalo> kamstrup: ah, but i7 is still on lucid. is that a problem?
[14:14] <kamstrup> kvalo: that should be ok. But it's quite heavy since it builds some big projects like glib, vala, and Nux
[14:14] <kvalo> kamstrup: and will it break something? :)
[14:14] <kamstrup> kvalo: no
[14:14] <kvalo> cool
[14:14] <kamstrup> kvalo: everything goes under ~/unity
[14:14]  * kvalo continues
[14:15] <dbarth> lamalex: hmm, it's in the code i think
[14:15] <kamstrup> kvalo: no matter how awesome your i7 is I think you can safely grab a cup of tea while it builds :-)
[14:16] <dbarth> lamalex: i mean, the color is meant to be symbolic, ie the indicator should infer whether it's red or green depending on the meaning
[14:16] <seb128> sladen, ok, I was just pointing it, seems in the case the trivial ftbfs was rather due compiz but I can see how you though it was easier than that
[14:16] <jcastro> njpatel: ok cool, you appear to have imported all my panel icons into the launcher with this update. That is quite neat.
[14:16] <kvalo> omg, jhbuild suggests tla :)
[14:17] <kvalo> I'm sure I will see nightmares next night...
[14:17] <dbarth> lamalex: where exactly do you need to read/change that color?
[14:17] <lamalex> dbarth, not for that- for something else completely unrelated to unity
[14:18] <kvalo> kamstrup: run 'jhbuild -f ~/unity/unity.jhbuildrc' now
[14:18] <kamstrup> kvalo: right
[14:18] <kamstrup> kvalo: you may need to sudo apt-get install jhbuild
[14:19] <kvalo> did that already
[14:19] <kvalo> building glibc now, I think
[14:20] <lamalex> dbarth, I want to use symbolic icons in banshee but google won't tell me if there's a programatic way to set the color, or if you just use different colored icons
[14:20] <kamstrup> kvalo: hopefully not glibc :-) glib rather...
[14:20] <kvalo> kamstrup: haha. let's hope so :)
[14:21] <kvalo> damn, my cairo is too old
[14:21] <kvalo> and libpng
[14:21] <kvalo> Requested 'cairo >= 1.9.14' but version of cairo is 1.8.10
[14:21] <kvalo> Requested 'libpng >= 1.2.44' but version of libpng is 1.2.42
[14:23] <kamstrup> kvalo: bugger... I don't think it's a good idea to add cairo and libpng. We'd probably end up building the entire Natty stack
[14:23] <kamstrup> kvalo: so one probably needs at least Maverick to build
[14:23] <kvalo> kamstrup: I'll try to compile it inside maverick kvm
[14:23] <kamstrup> kvalo: oh cool
[14:33] <kvalo> kamstrup: jhbuild should "just quit, damnit" option
[14:33] <kvalo> *should have
[14:33] <kamstrup> kvalo: Ctrl-C? :-)
[14:34] <kvalo> yeah, that's what I alwayd do. but I have this fear that it breaks something
[14:36] <dbarth> lamalex: so you want to set the color for the banshee icon inside the sound menu? or to set the icon color on the panel directly?
[14:38] <kvalo> kamstrup: I have to admit that i7 is handy for this type of testing :p
[14:38] <kamstrup> kvalo: indeed!
[14:38] <kamstrup> kvalo: still compiling cleanly?
[14:38] <kvalo> kamstrup: I had to install gnome-core-devel first
[14:39] <kvalo> ah, now nux complains about glew
[14:39] <kvalo> I don't usually compile with this vm
[14:40] <kvalo> kamstrup: apt-get build-depends or similar command would be really nice for newbies like me
[14:41] <kvalo> sigc++
[14:41] <kvalo> finally nux started compiling
[14:47] <kamstrup> kvalo: ah, right
[14:47] <kvalo> now cmake is missing
[14:49] <jcastro> dbarth: http://reports.qa.ubuntu.com/reports/unity-stats/
[14:49] <kvalo> kamstrup: let's take this offline, no need to spam everyone
[14:49] <kamstrup> kvalo: sure
[14:49] <didrocks> grrr, it's been years I didn't play with xslt and dtd… not fun for a Friday :)
[15:00] <dbarth> jcastro: uh, flat?!
[15:00] <dbarth> jcastro: thanks for the pointer
[15:00] <dbarth> jcastro: and hi, btw ;)
[15:00] <jcastro> dbarth: it started like, just now. :)
[15:00] <dbarth> ah, ok, it's just because they've been started
[15:00] <jcastro> dbarth: that brings me to my actual question, as you see them if you could tag a few unity bugs "bitesize" I can start working on the workflow
[15:01] <dbarth> right, i see
[15:01] <jcastro> I only need like 1 or 2 to start off with
[15:01] <dbarth> yeah
[15:02] <dbarth> well, i've just triaged one i think
[15:05] <dbarth> jcastro: https://bugs.launchpad.net/unity/+bug/680397
[15:06] <dbarth> jcastro: do you have a page on the process; or we should do one real quick
[15:06] <jcastro> yes
[15:06] <jcastro> today is my "we should do one really quick"
[15:06] <dbarth> so you mean, let's do one?
[15:06] <jcastro> yeah
[15:06] <jcastro> http://unity.ubuntu.com/getinvolved/
[15:06] <jcastro> check this out
[15:06] <jcastro> it's 90% there
[15:06] <jcastro> we just need Unity/Bitesize
[15:07] <jcastro> and then link to the tag in lp, this page
[15:07] <jcastro> and then we can add stuff to it
[15:08] <dbarth> we should reuse the papercuts way
[15:08] <dbarth> jcastro: also i've emailed jono for getting access to the server, and fix some paragraphs
[15:08] <jcastro> I filed a ticket with IS
[15:08] <jcastro> openid is broken on it
[15:08] <dbarth> typically, once people have uploaded a branch with a fix
[15:08] <dbarth> ah ok, thanks
[15:09] <dbarth> they should do a merge proposal
[15:09] <jcastro> as soon as they fix it I can resolve the ~3 bugs people have filed on the web page
[15:09] <dbarth> and sign the contributor agreement
[15:09] <dbarth> yeah, i know
[15:10] <dbarth> jcastro: https://wiki.ubuntu.com/PaperCut
[15:10] <jcastro> ok I will start a page
[15:10] <jcastro> and get back to you
[15:11] <jcastro> :)
[15:12] <dbarth> super, thanks jcastro
[15:13] <didrocks> ok, so unity by default upload on natty in few minutes :)
[15:13] <jcastro> oh?
[15:13] <didrocks> jcastro: still gnnome-panel for now as the question is tricky, and we need the nm-applet indicator
[15:13] <jcastro> nice!
[15:13] <jcastro> didrocks: I just tested nm-indicator this morning
[15:13] <didrocks> (so unity + gnome-panel in the default session)
[15:13] <didrocks> and gnome-panel in the second session
[15:13] <jcastro> didrocks: it's looking quite good, however I haven't ventured out to roam with it yet, etc.
[15:14] <jcastro> \m/
[15:14] <didrocks> jcastro: nice! that doesn't solve the tricky issue with gnome-panel and fallback and such, but it's a nice step forward :)
[15:14] <jcastro> didrocks: probably fire off a mail to -desktop when you upload to explain that? People might be confused that they have a mixed session
[15:15] <didrocks> jcastro: well, i've already fired a mail about the gnome-panel issue later this week :)
[15:15] <jcastro> eralier you mean?
[15:15] <didrocks> oupss, earlier, yeah
[15:16] <didrocks> but I'll fix it for A1 in any case, even if it's a temporary bad workaround
[15:17] <jcastro> dbarth: ok, so this page will be temporary, I think it will be better to just add the bitesize and the merge proposal/CA thing to the existing page.
[15:20] <jcastro> https://wiki.ubuntu.com/Unity/Bitesize
[15:20] <dbarth> the one on u.u.c you mean, yeah makes sense
[15:28] <lamalex> WOW
[15:28] <lamalex> last update..
[15:28] <lamalex> f'd my computer up real bad
[15:33] <dbarth> lamalex: what in particular? x? network?
[15:34] <lamalex> dbarth, unity (mutter) causes my screen to just flash
[15:34] <dbarth> lamalex: ah on maverick?
[15:34] <lamalex> dbarth, yeah
[15:34] <lamalex> like, system update
[15:34] <dbarth> weird
[15:35] <dbarth> i've switched to natty and that reminds me that i need to warn people about starting to switch as well
[15:36] <lamalex> well, I might switch pretty soon since my maverick is horribly broken
[15:52] <dbarth> restarting my unity session
[16:01] <jcastro> agateau: hey what's the 10 second summary of appmenu support in upstream Qt?
[16:32] <didrocks> njpatel: the value you wanted to change is the zoom_springiness, right?
[16:33] <didrocks> (the animation plugin wasn't activated, adding it)
[16:34] <didrocks> hum, the sidekick_springiness I guess, rather
[16:47] <didrocks> DBO: ^^
[16:48] <DBO> didrocks, zoom springiness
[16:49] <didrocks> DBO: the zoomspringiness is off by default
[16:49] <didrocks> (on ubuntu)
[16:49] <DBO> yes I know
[16:49] <didrocks> DBO: what should it be?
[16:49] <DBO> I want animation enabled
[16:49] <DBO> zoom as the minimize animation
[16:49] <didrocks> that can be done :)
[16:49] <DBO> and the zoom springiness to be 0.08
[16:50] <didrocks> DBO: oh, so animation showing the window reducing to the panel?
[16:50] <DBO> yes
[16:50] <didrocks> I found it cool it knew about the panel, but oh well :)
[16:52] <didrocks> DBO: changed, just for you dude :)
[16:52] <didrocks> (even if I don't like it :))
[16:53] <DBO> there are design videos that show a springiness to their minimize
[16:53] <DBO> 0.08 is about as close as I could get it visually
[16:53] <didrocks> DBO: but not to the launcher? we got some bug report about people thinking it should minimize to the launcher
[16:53] <DBO> it does minimize to the launcher
[16:54] <DBO> if you enable the zoom animation as your minimize animation in the animation plugin
[16:54] <DBO> it goes right to the launcher
[16:54] <DBO> if the launcher is hidden the icon jumps out to catch the minimized window
[16:54] <didrocks> DBO: hum, something shouldn't be right with our default settings then
[16:54] <didrocks> DBO: let me make a video, ok?
[16:55] <DBO> are you running gnome panel?
[16:55] <didrocks> DBO: yes
[16:55] <didrocks> DBO: but it doesn't go from gnome panel as well
[16:55] <DBO> didrocks, if you have another pager
[16:55] <DBO> it may be conflicting
[16:55] <agateau> jcastro: 10 second summary about Qt appmenu support: merge request is in progress, I need to rework it a bit
[16:55] <didrocks> it's working without the zoom effect
[16:55] <didrocks> DBO: let me show you that, one sec :)
[16:56] <didrocks> launching ccsm in LANG=C as well
[16:56] <jcastro> agateau: excellent, thanks.
[16:56] <DBO> didrocks, also can you make sure everyone knows that they need to update both nux and unity for best window stackign results
[16:56] <DBO> since I am not technically working today
[16:57] <jcastro> agateau: they've been working in our KDE/Qt since 10.10 though right?
[16:57] <didrocks> DBO: yeah, the packaging has done that
[16:57] <didrocks> DBO: sorry dude :)
[16:57] <DBO> didrocks, wait you mean minimize goes to the launcher but unminimize kinda doesn't?
[16:58] <didrocks> DBO: not really, showing you that in a minute
[16:59] <agateau> jcastro: yes
[17:03] <smspillaz> DBO: I love it how we say "technically not working today, but eh, I hang out on IRC"
[17:03] <DBO> its sad really
[17:04] <DBO> didrocks, i really need that preview soon
[17:05] <didrocks> DBO: http://people.canonical.com/~didrocks/zoom-spriginess.ogv
[17:05] <didrocks> come one, DBO likes that :)
[17:06] <didrocks> hum, I should try a compiz --replace, maybe it can help
[17:07] <DBO> didrocks, you dont want minimize from center
[17:07] <DBO> you want that option as off
[17:07] <DBO> as to why its missing
[17:07] <DBO> it looks like something else set its icon geometry
[17:08] <DBO> you could inspect xprop to see where it minimizes to
[17:09] <DBO> _NET_WM_ICON_GEOMETRY(CARDINAL) <--- that tells you where the window is slated to go to didrocks
[17:09] <didrocks> DBO: ok, let me see
[17:09] <didrocks> so, theorically, I just let the option "off"
[17:09] <didrocks> and change the slider value, right?
[17:09] <DBO> didrocks, correct
[17:10] <DBO> didrocks, the off is for minimizing to the center, which you want off
[17:10] <DBO> the two options are not related
[17:10] <didrocks> ok :)
[17:11] <didrocks> grrr, compiz segfault at start
[17:11] <didrocks> ok, unsetting everything and trying again
[17:11] <DBO> you know about the crashhandler plugin right?
[17:12] <didrocks> it's not activated
[17:12] <didrocks> we will get apport
[17:12] <DBO> yes but for you
[17:12] <DBO> since you *are* a member of the devteam
[17:12] <DBO> I want you to get backtraces
[17:12] <didrocks> it's even before the plugin activate there :)
[17:13] <DBO> ah
[17:13] <didrocks> ok, let me restart X
[17:17] <dbarth> DBO: what's the proper way to enable it? the crashandler plugin?
[17:17] <didrocks> DBO: a compiz restart away and all looks good!
[17:18] <didrocks> DBO: enabling the animation plugin by default then + 0.08 for zoom springiness
[17:18] <didrocks> thanks :)
[17:20] <DBO> dbarth, enable it in CCSM
[17:20] <DBO> didrocks, super
[17:20] <didrocks> DBO: I just thought that the options were linked in ccsm…
[17:21] <DBO> its okay
[17:21] <DBO> okay gentlemen, I worked yesterday so I could have today off
[17:21] <didrocks> DBO: enjoy!
[17:22] <DBO> yes.... enjoy time with the in-laws to be...
[17:23] <dbarth> it's not in the packages i have installed anymore; i've switched to natty .debs
[17:24] <dbarth> plugins-extra i assume
[17:32] <dbarth> didrocks: hey, i'm missing compiz-fusion-plugins-extra
[17:33] <didrocks> dbarth: didn't you tell that you didn't like the bling bling? :)
[17:33] <dbarth> apparently only the 0.8 version is available
[17:33] <dbarth> ah
[17:33] <dbarth> sure
[17:33] <didrocks> dbarth: yeah, it's not package with 0.9, I didn't have the time :)
[17:33] <dbarth> except the crashhandler is there
[17:33] <dbarth> okay
[17:33] <didrocks> argh :)
[17:33] <dbarth> the thing is that i was using the compiz built from source and it was there
[17:33] <didrocks> well, after alpha1 or if a motu wants to help there
[17:33] <dbarth> so i didn't understand why it was missing
[17:33] <dbarth> now i see
[17:34] <didrocks> dbarth: other solution, no crash on unity :p
[17:34] <dbarth> right, after alpha-1 it'd be nice to get this one and a couple other to be built
[17:34] <dbarth> so that we can document the procedure for reporting bugs or perf. issues
[17:34] <dbarth> didrocks: uh, that's a solution
[17:34] <dbarth> ;)
[17:34] <didrocks> \o/
[17:35] <didrocks> dbarth: well, more seriously, with sam compiz repo reorganization and a big source tarball, it will be easier
[17:35] <dbarth> ah, right
[17:35] <didrocks> so, after A1 for that and you will have all the desired plugins :)
[17:36] <seb128> ideally we should need nothing from extra in unity
[17:36] <seb128> dbarth, we have a performant crash handling system in Ubuntu ;-)
[17:37] <didrocks> seb128: maybe the two can communicates? I don't know what the plugin does TBH
[17:37] <seb128> it gives you a stacktrace
[17:37] <kvalo> didrocks: hey, how does autotools and a medium size pygtk app (multiple classes in different files etc) fit together?
[17:37] <seb128> I don't see how it will be better than having a crash sent to retracers
[17:38] <dbarth> seb128: yeah, but the issue is that during development it's quite easy to be one version behind and in which case apport will not let you file a bug
[17:38] <dbarth> yet, the crasher info should be preserved
[17:38] <seb128> dbarth, well you still get the .crash locally with the stracktrace
[17:38] <didrocks> ok, if there is no additional info like plugins settings and such that we can't have in a apport hook, there is no need
[17:38] <seb128> dbarth, it's just the submitting part failing
[17:38] <dbarth> right
[17:38] <dbarth> yeah
[17:38] <seb128> dbarth, the .crash also has the dump, you can use gdb on it
[17:38] <dbarth> true
[17:38] <didrocks> kvalo: I would say, prefer python-distutils-extra and a setup.py if possible
[17:39] <dbarth> well, so you're right maybe there's no need to make that more complex than it should
[17:39] <dbarth> i'd just like to make sure that the plugin doesn't provide something better for compiz itself
[17:40] <kvalo> didrocks: my problem is that indicator-network already uses autotools. is there any way to combine python-distutils and autotools, or am I forced to create a new (debian) source package?
[17:40] <didrocks> kvalo: no, in that case, use autotools for packaging python
[17:40] <didrocks> kvalo: but it's not a nice game from my experience :)
[17:41] <didrocks> kvalo: I can give you some examples on monday (like the first Quickly revisions)
[17:41] <kvalo> didrocks: I was just worried it's something like that. thanks for the help, let's talk more next week
[17:42] <kvalo> kenvandine: ping?
[17:49] <mhr3> Cimi, can i ask for extra detail for gtk3 murrine's draw_flat_box? :)
[17:49] <dbarth> kvalo: he's probably out for thanksgiving (kenvandine)
[17:49] <Cimi> mhr3: quickly cause I'm going out
[17:49] <kvalo> dbarth: ok, thanks. I'll ping him on monday
[17:50] <mhr3> Cimi, i want it to paint the same thing as cell_even/cell_odd but without the need for the widget to have focus
[17:50] <Cimi> mhr3: talk to you in 3 hours
[17:50] <mhr3> Cimi, very well, cu
[18:51] <c10ud> cando_, :o
[18:56] <cando_> c10ud!!!
[20:09] <lamalex> smspillaz, ping
[22:05] <Cimi> mhr3: pong