[00:29] <TheMuso> robert_ancell: oh whoops, thanks. :)
[01:57] <gunnarhj> help
[04:50] <chiz> Is here somebody alive?
[04:52] <nisshh> chiz, whats up?
[04:53] <chiz> nisshh, how to install lxde?
[04:53] <chiz> I want to type smth in terminal to download and install lxde
[04:53] <nisshh> chiz, hmmm, do you want the full lubuntu? or just lxde?
[04:53] <chiz> But I don't know what command
[04:54] <chiz> I have now normal Ubuntu
[04:54] <chiz> I want lxde instead of ...
[04:54] <nisshh> yeah
[04:54] <chiz> I don't know what :-)
[04:54] <nisshh> ah, instead of GNOME
[04:54] <chiz> Smth preinstalled
[04:54] <chiz> Maybe :-)
[04:54] <nisshh> chiz, try this in the terminal: sudo apt-get install lxde
[04:55] <nisshh> then logout and when you log back in change the session from Ubuntu Desktop Edition to LXDE
[04:55] <chiz> Couldn't find package lxde
[04:55] <nisshh> chiz, which version of Ubuntu are you using?
[04:55] <chiz> :-)
[04:55] <chiz> 8
[04:56] <nisshh> 8.04?
[04:56] <chiz> oh
[04:56] <chiz> no
[04:56] <chiz> 6.10
[04:56] <chiz> :-)
[04:56] <chiz> My PC is to slow for 10
[04:56] <nisshh> your running 6.10!?
[04:56] <nisshh> wow
[04:56] <nisshh> chiz, lxde is only available in 10.04 and later
[04:57] <chiz> There is no lxde for 6 version? :-(
[04:57] <nisshh> no
[04:57] <chiz> What a pitty :-(
[04:57] <chiz> ok
[04:57] <nisshh> lxde hasnt been around for ages
[04:57] <chiz> Maybe smth else?
[04:57] <nisshh> chiz, try xfce
[04:57] <chiz> Some lightweight GUI
[04:57] <chiz> instead of lxde?
[04:57] <nisshh> chiz, what hardware are you on?
[04:57] <chiz> In command, I mean
[04:57] <chiz> :-)
[04:58] <chiz> Celeron 1,7
[04:58] <chiz> 512 RAM
[04:58] <nisshh> i see
[04:58] <nisshh> then xfce should work fine
[04:58] <nisshh> try: sudo apt-get install xubuntu-desktop
[04:58] <nisshh> then logout and select it as your session
[04:59] <chiz> Couldn't find package xfce
[04:59] <chiz> oh
[04:59] <chiz> just a sec
[04:59] <nisshh> chiz, you really should upgrade the the newest version of Ubuntu
[04:59] <chiz> Couldn't find package xubuntu-desktop
[04:59] <nisshh> chiz, 6.10 isnt supported anymore
[05:00] <chiz> Bad...
[05:00] <nisshh> chiz, yeah, im not completely sure but i dont think xubuntu was around then either
[05:00] <nisshh> that was 2006
[05:00] <chiz> I understand :-)
[05:00] <nisshh> chiz, 6.10 no longer gets security updates or anything
[05:00] <chiz> What about 8th version?
[05:00] <chiz> Is there some lightweight GUI?
[05:00] <nisshh> 8.04 does, but not for too much longer
[05:01] <nisshh> chiz, if you install Xubuntu 10.10 you will have a lightweight GUI
[05:01] <chiz> I don't worry about security
[05:01] <nisshh> chiz, i see, you should
[05:01] <chiz> This machin is just for reading books and programming j2me apps
[05:01] <chiz> It didn't help
[05:02] <chiz> I tried
[05:03] <chiz> I installed 10 version and lxde on it. It wasn't comfortable.
[05:03] <nisshh> chiz, not lxde, xfce
[05:03] <nisshh> xfce is completely different
[05:03] <chiz> xfce better then lxde?
[05:03] <chiz> oh
[05:03] <chiz> ok
[05:04] <nisshh> chiz, im not at liberty to say which is better, its your choice, but LXDE is newer than XFCE and its also lighter
[05:05] <chiz> lxde lighter?
[05:06] <chiz> nisshh, thanks!
[05:06] <nisshh> chiz, in my experience it is slightly
[05:06] <chiz> I have to go to work :-)
[05:06] <nisshh> but they are both very lightweight
[05:07] <nisshh> ok
[08:31] <rodrigo_> morning
[08:31] <didrocks> hey rodrigo_, how was your week-end?
[08:31] <rodrigo_> hi didrocks
[08:31] <rodrigo_> didrocks, very short :)
[08:31] <didrocks> rodrigo_: oh why?
[08:32] <nisshh> because its only 2 days?
[08:32] <didrocks> :)
[08:32] <rodrigo_> didrocks, yes, only 2 days :)
[08:32] <nisshh> hehe
[08:32] <didrocks> it was enough for me to finish metal gear solid 4!
[08:32] <nisshh> didrocks, oh, didnt know you were a gamer?
[08:33] <rodrigo_> didrocks, oh, on the ps3?
[08:33] <didrocks> nisshh: not as I've been, I restrict myself now to final fantasy/zela/metal gear/mario
[08:33] <didrocks> which are games that take time :)
[08:33] <nisshh> oh, bit of old school :)
[08:33] <didrocks> rodrigo_: yeah, on ps3 :)
[08:34] <didrocks> nisshh: well, I'm not that "old", but yeah, traditional games :)
[08:34] <nisshh> didrocks, i myself play lots of FPS games on PC :)
[08:34] <rodrigo_> I don't like FPS, I get stressed with them :)
[08:34] <nisshh> didrocks, lol, i know that :)
[08:34] <didrocks> nisshh: at least, on GNU/Linux, you have the choice
[08:34] <didrocks> as rodrigo_, I don't really like FPS, I prefer games with a story
[08:34] <nisshh> didrocks, thats exactly right, i dont play any through wine either, i play all native games
[08:35] <rodrigo_> yeah, with some action, but a more relaxed :)
[08:35] <nisshh> i like RPG's as well
[08:35] <didrocks> for instance, I can't imagine anyone playing mgs4 without having played to 1, 2 and 3… should be soooo confusing!
[08:35] <nisshh> hehe
[08:36] <rodrigo_> metal gear solid isn't a shooter?
[08:36] <didrocks> rodrigo_: no really, it's a tactical infiltration game
[08:36] <rodrigo_> ah
[08:36] <didrocks> rodrigo_: the main goal is to be not detected
[08:36] <rodrigo_> I might try it then
[08:36] <didrocks> make people sleep, and such :)
[08:36] <didrocks> sneak inside the building
[08:36] <rodrigo_> I didn't even try it because I thought it was a shooter
[08:36] <didrocks> well, I really like that :)
[08:37] <didrocks> even if mgs4 is the most violent of the serie
[08:37] <didrocks> so, you still have some part where you have to shoot a lot, but it's not like a FPS
[08:37] <nisshh> didrocks, i have gone off stealth shooters, too boring
[08:37] <rodrigo_> ok, I'll get the demo from PSN to try it
[08:38] <didrocks> rodrigo_: the thing is that can either play it as a shooter if you don't sneak well enough :)
[08:38] <nisshh> didrocks, FPS games do have stories, what about halo?
[08:38] <didrocks> rodrigo_: but most of the time, you'll loose then :)
[08:38] <didrocks> nisshh: yeah, I've played a little bit of halo some years ago, but too stressful for me :)
[08:39] <rodrigo_> nisshh, the story being 'kill everyone'? :D
[08:39] <nisshh> didrocks, also, MGS on the PSP punishes you if you dont use stealth
[08:39] <nisshh> rodrigo_, have you even played halo?
[08:39] <didrocks> nisshh: yeah, that's the point of the game :)
[08:39] <rodrigo_> nisshh, no, not really
[08:39] <nisshh> rodrigo_, it has a large story behind it
[08:40] <rodrigo_> as I said, if it looks like a shooter when reading the reviews, I don't even try them
[08:40] <nisshh> didrocks, yeah, the PSP versions suck
[08:40] <nisshh> rodrigo_, oh, it is a shooter, but didrocks was saying shooters dont have stories, when they do
[08:40] <rodrigo_> ah
[08:41] <didrocks> well, not enough story for me, let's say :)
[08:41] <rodrigo_> hehe
[08:41] <nisshh> didrocks, ah, ok :)
[08:41] <didrocks> even when a lot of people hates final fantasy because you can have some part with the story during 30 minutes, I really like that :)
[08:42] <nisshh> didrocks, well, i dont mind FF, but after 14 releases, the story is so screwed
[08:42] <nisshh> i dont even understand it anymore
[08:42] <rodrigo_> :)
[08:42] <nisshh> and thats if i ever did :)
[08:42] <didrocks> nisshh: the story is so screwed? It's another story every time!
[08:43] <didrocks> new people, new world, new epoch…
[08:43] <nisshh> thats exactly my point....
[08:43] <nisshh> it isnt FF if it doesnt carry on from the next one
[08:43] <didrocks> no, but an episod for a story is enough
[08:44] <nisshh> hehe
[08:44] <didrocks> I played FF7 for instance 11 times :)
[08:44] <nisshh> yeah
[08:44] <nisshh> ive played FF7 on the PSP 3-4 times
[08:44] <nisshh> its addictive
[08:44] <rodrigo_> didrocks, you should try uncharted and uncharted2, I think you'll like them
[08:44] <didrocks> more than 100 hours to finish everything in a time :)
[08:45] <didrocks> rodrigo_: yeah, I was powndering buying it. It was too late to try the demo
[08:45] <nisshh> rodrigo_, oh man, i have, they are good games :)
[08:45] <rodrigo_> you can buy them quite cheap 2nd hand now, in GAME shops (I guess there are some in France?)
[08:46] <rodrigo_> nisshh, yeah, the best ones I've tried recently
[08:46] <rodrigo_> apart from assasin's creed
[08:46] <nisshh> hehe
[08:46] <didrocks> rodrigo_: yeah, it was another named before, but it has been renamed GAME as well :)
[08:46] <didrocks> rodrigo_: I'll probably have a try! :)
[08:49] <nisshh> geez
[08:49] <nisshh> i always do that
[09:24]  * pitti waves hello for a quick drive-by (swap day today)
[09:25] <didrocks> hey pitti! did you have a nice travel!
[09:25] <didrocks> ?
[09:25] <pitti> well, travelling eastwards during the night is never "nice" :)
[09:26] <pitti> I slept for about an hour, but I had a nap at home
[09:26] <pitti> so I felt quite well after that
[09:26] <pitti> the concert yesterday evening was awesome
[09:26] <pitti> didrocks: how about you?
[09:27] <didrocks> pitti: I'm fine thanks, nice week-end and knowing that at the end of this week, Julie will be back here (she was on her parents for almost 2 monthes to not be too many to my parents waiting for our flat :))
[09:28] <pitti> oh, nice
[09:28] <seb128> hey didrocks pitti
[09:28] <didrocks> salut seb128, ça va ?
[09:28] <seb128> ouais, et toi ?
[09:28] <seb128> pitti, back in europe? did you have a nice trip back?
[09:28] <seb128> how is your jetlag?
[09:28] <pitti> bonjour seb128
[09:29] <pitti> seb128: see above, flights were on time and uneventful
[09:29] <rodrigo_> hi pitti, seb128
[09:29] <pitti> seb128: Had trouble getting to sleep last night, but I fell reasonably well now -- I'm on swap day today, so I could sleep in until 9 am :)
[09:30] <didrocks> seb128: ça va bien, détente et jeux vidéo :)
[09:30] <seb128> pitti, above was just before I joined I gues
[09:30] <seb128> s
[09:30] <seb128> pitti, ok, great
[09:30] <pitti> ah, ok; I filter out join/part messages
[09:30] <seb128> pitti, enjoy your swap day
[09:31] <pitti> just wanted to do some quick spec review, then some laundry and supermarket
[09:43] <pitti> RAOF: I set https://blueprints.launchpad.net/ubuntu/+spec/hardware-desktop-n-xorg-configuration-the-final-ten-percent back to drafting; this just needs some clarification (see my questions in the whiteboard)
[09:45] <pitti> seb128: just to confirm, you are still working on https://blueprints.launchpad.net/ubuntu/+spec/packageselection-desktop-n-application-selection drafting?
[09:45] <seb128> pitti, hum, no
[09:46] <pitti> seb128: i. e. ready for review?
[09:46] <seb128> pitti, dunno, somebody else wrote the summary and workitems, I didn't realise I was drafting it ;-)
[09:46] <seb128> I think jcastro did
[09:47] <seb128> pitti, let me review it and send it your way if it's ok
[09:47] <pitti> seb128, didrocks: FYI, you have some specs in your review queue
[09:47] <pitti> seb128: merci
[09:48] <seb128> pitti, the appselection seems fine
[09:48] <pitti> seb128: good, will review
[09:48] <seb128> pitti, you can review it
[09:48] <seb128> thanks
[09:48] <seb128> how do I see what is in my review queue?
[09:49] <pitti> https://blueprints.launchpad.net/people/+me/+specs?role=approver
[09:49] <didrocks> pitti: yeah, I'll review them today. Thanks :)
[09:49] <pitti> didrocks: ^
[09:49] <seb128> pitti, will review those today
[09:49] <hyperair> nautilus-share needs someone to upload into -proposed, by the way. =p
[09:49] <hyperair> it's the crasher bug when adding shares.
[09:50] <pitti> bryceh: can you please review/approve https://blueprints.launchpad.net/ubuntu/+spec/multimedia-desktop-n-xorg-general-planning ?
[09:51] <pitti> seb128: https://blueprints.launchpad.net/ubuntu/natty/+specs?searchtext=desktop already looks quite nice; should be possible to get most to approved by meeting tomorrow \o/
[09:51] <pitti> didrocks: "change the seed to have it default in alpha1: TODO" on https://blueprints.launchpad.net/ubuntu/+spec/packageselection-desktop-n-application-selection
[09:52] <pitti> didrocks: is "it" == "Banshee"?
[09:52] <pitti> ah, guess so
[09:52] <didrocks> pitti: I think as jcastro wrote that WI. I don't see on what else he could have commented :)
[09:52] <seb128> pitti, you rock, great work!
[09:53] <seb128> didrocks, ^ can you sponsor the nautilus-share bugfix?
[09:53] <pitti> s/you/desktop team/!
[09:53] <didrocks> seb128: can do today, not now
[09:53] <seb128> didrocks, no hurry I think sru are still frozen so...
[09:54] <didrocks> seb128: still frozen? ok, good to know. Thanks :)
[09:55] <pitti> seb128: the WIs don't cover a tsclient/vinagre decision and dropping gnome-dictionary (was that reconsidered?)
[09:56] <seb128> pitti, right, I just noticed, I'm updating those, 2 minutes
[10:00] <seb128> pitti, done
[10:00] <seb128> didrocks, I've assigned you the "drop gnome-dictionnary" if you are doing the banshee dropping as well I figured you could do both at the same time ;-)
[10:01] <seb128> ups banshee change, not dropping
[10:01] <didrocks> seb128: sure :)
[10:02] <pitti> seb128: cheers, approved
[10:03] <seb128> pitti, thanks
[10:03] <pitti> ok, /me &
[10:03] <seb128> pitti, when you have comments on a spec, do you change the status back to something?
[10:03] <seb128> or do you just let it in the current state?
[10:03] <pitti> seb128: yes, usually "drafting"
[10:03] <seb128> like https://blueprints.launchpad.net/ubuntu/+spec/packagesselection-desktop-n-telepathy-indicator
[10:03] <pitti> if it's something that needs to be changed
[10:03] <seb128> I want a work item about "uploading"
[10:03] <seb128> like a target for when that will land
[10:03] <pitti> so that it falls out of my queue and back into the drafter's
[10:04] <seb128> ok
[10:04] <seb128> thank
[10:04] <seb128> thanks
[10:43] <didrocks> hyperair: do you have a bug report # handy?
[10:43] <didrocks> (for nautilus-share)
[10:43] <hyperair> didrocks: right give me a moment.
[10:43] <hyperair> 655721
[10:44] <hyperair> bug #655721
[10:44] <ubot2> Launchpad bug 655721 in nautilus-share (Ubuntu) "Nautilus crashes when adding a share (affects: 8) (dups: 2) (heat: 56)" [High,Fix released] https://launchpad.net/bugs/655721
[10:44] <hyperair> there we go.
[10:45] <didrocks> hyperair: can you please edit the bug report with a testcase and the changelog entry, please?
[10:45] <didrocks> hyperair: I'll sponsor meanwhile
[10:47] <didrocks> hyperair: so 0.7.2-14 contains the fix, right?
[10:47] <hyperair> didrocks: yes.
[10:47] <hyperair> didrocks: but -14 is in natty, so you'll have to add a ~something
[10:47] <seb128> use 13.1 rather for the sru
[10:47] <didrocks> ok, will upload with -v then :)
[10:47] <didrocks> yeah
[10:47] <didrocks> 0.7.2-13.1 sounds better for maverick
[10:47] <hyperair> =\
[10:47] <seb128> yes
[10:48] <hyperair> okay then
[10:48] <seb128> we will need a new upload to natty with mterry's libgnome cleaning
[10:48] <hyperair> i usually like the version numbers to reflect where they came from though
[10:48] <hyperair> seb128: it's already on mentors.debian.net, i'm waiting for mbiebl
[10:48] <seb128> since apparently that didn't got included in the debian upload for some reason
[10:48] <seb128> ok
[10:48] <hyperair> seb128: because debian is frozen and this was a high-prio bugfix meant for going into squeeze.
[10:49] <seb128> ok
[10:52] <didrocks> hyperair: sponsored to -proposed. I've edited to add the changelog as well. Please, subscribe the SRU team once added the test case
[10:52] <hyperair> didrocks: do they need to be subscribed these days? i thought they just follow the bug number in the .changes
[10:53] <didrocks> hyperair: always better to subscribe them, they tend to not touch those where they aren't subscribe from what I understood as it can means "not ready finally, will do another upload"
[10:53] <hyperair> didrocks: oh, okay.
[10:56] <hyperair> didrocks: alright, done =)
[10:57] <didrocks> hyperair: great, looks good. thanks! :)
[11:02] <hyperair> =)
[11:22] <seb128> Nafallo, hey
[11:22] <seb128> Nafallo, was https://bugs.launchpad.net/ubuntu/+source/gajim/+bug/349661 ever sent to debian or upstream or not?
[11:22] <ubot2> Launchpad bug 349661 in gajim (Ubuntu Jaunty) (and 1 other project) "config rewrites not posix safe (affects: 1) (heat: 5)" [Medium,Fix released]
[11:25] <Nafallo> seb128: can't remember, sorry.
[11:26] <seb128> Nafallo, ok
[11:26] <seb128> seems the ubuntu diffs are small we could perhaps get back in sync in debian
[11:27] <Nafallo> that sounds lovely. I haven't looked at the package myself since I started using empathy either :-/
[11:30] <rodrigo_> seb128, pitti: hmm, in https://blueprints.launchpad.net/ubuntu/+spec/packageselection-desktop-n-gnome3 , what about porting stuff to gdbus so that we can also get rid of dbus-glib?
[11:30] <rodrigo_> most upstream apps are migrating afaics though
[11:31] <rodrigo_> which raises the question, of what does python-dbus use?
[11:33] <rodrigo_> python-dbus uses dbus-glib
[11:53] <seb128> rodrigo_, hello
[11:53] <rodrigo_> hi seb128
[11:53] <seb128> rodrigo_, well, I think the cost is non trivial and the win very small
[11:53] <rodrigo_> yeah
[11:53] <seb128> it's not like dbus-glib was hard to keep or maintain
[11:53] <seb128> I would prefer get ride of a gtk stack of from gconf and bonobo
[11:54] <rodrigo_> yeah
[11:55] <rodrigo_> specially if python-.dbus depends on it, so yeah, not trivial
[11:57] <seb128> would be interesting to know the telepathy plans for it
[11:57] <seb128> it's one of the main users
[11:58] <cassidy> we have to port tp-glib first, which is not a trivial task as you can imagine
[11:58] <seb128> right
[11:58] <cassidy> it *may* happen during this cycle but that's not sure
[11:58] <seb128> that's why I was wondering if that would happen in one cycle
[11:58] <seb128> in any case dbus-glib is not on my deprecation list for this cycle
[11:58] <cassidy> bug is https://bugs.freedesktop.org/show_bug.cgi?id=28782
[11:59] <ubot2> Freedesktop bug 28782 in tp-glib "Migrate from dbus-glib to glib's GDBus" [Enhancement,New]
[13:10] <mdeslaur> seb128: would you have any objection to me uploading the fix for bug 611983 to -proposed?
[13:10] <ubot2> Launchpad bug 611983 in evolution (Ubuntu Natty) (and 4 other projects) "Evolution [Open Link In Browser] not working for new eBay email hyperlinks (affects: 8) (dups: 2) (heat: 58)" [Low,Triaged] https://launchpad.net/bugs/611983
[13:12] <didrocks> mdeslaur: there is already an evolution pending for approval in -proposed, maybe wait for this one to get through?
[13:12] <mdeslaur> didrocks: yes, I intended to
[13:15] <seb128> mdeslaur, no objection
[13:16] <seb128> thank you for working on that and the gnome-keyring issue
[13:16] <mdeslaur> seb128: cool, thanks
[13:16] <mdeslaur> seb128: no problem!
[13:16] <mdeslaur> my mom has been complaining about her ebay links :P
[13:16] <mdeslaur> so you can thank her :)
[13:18] <seb128> it's an issue that we let such bugs go through still
[13:36] <boulabiar> what are the projects where libbamf is used ?
[13:38] <hyperair> does anyone know what version of ubuntu linux mint 9 is based on?
[13:38] <hyperair> https://bugs.launchpad.net/bugs/571707 <-- people using linux mint 9 are claiming that this bug isn't fixed.
[13:38] <ubot2> Launchpad bug 571707 in plymouth (Ubuntu Lucid) (and 4 other projects) "fsck progress stalls at boot, plymouthd/mountall eats CPU (affects: 143) (dups: 16) (heat: 688)" [Undecided,Triaged]
[13:39] <hyperair> hmm it's based on lucid.
[13:39] <hyperair> so why would that bug rear its head on mint and not lucid.
[13:44] <bilalakhtar> seb128: Have you begun accepting Gnome 2.91 package upgrades?
[13:45] <seb128> bilalakhtar, no, not before some weeks
[13:45] <seb128> we just had gtk3 accepted
[13:45] <seb128> we still need to build other libraries with it
[13:45] <seb128> then get gtk3 on the CD
[13:45] <bilalakhtar> seb128: hmm, okay, I just saw gtk+3.0 in the repos so was curious
[13:45] <seb128> well you need libraries your software use to be ported as well
[13:46] <rodrigo_> seb128, gtk3 is in natty now then?
[13:46] <seb128> the launchpad integration one for example
[13:46] <seb128> rodrigo_, yes
[13:46] <bilalakhtar> hmm
[13:46] <rodrigo_> cool, what about the other libs?
[13:46] <bilalakhtar> Any way I am not doing anything until November 20
[13:47] <bilalakhtar> rodrigo_: as seb said, they are being built
[13:47] <rodrigo_> ok
[13:47] <rodrigo_> lunch then, bbl :)
[13:48] <seb128> rodrigo_, they will come over time
[13:48] <seb128> we are not in an hurry anyway since we have the ppa and we don't want to play catching up on abi breakages in natty yet
[13:49] <seb128> we said we would wait to have the gtk abi to stabilize a bit to get gtk3 on the CD
[14:02] <jcastro> didrocks: I didn't write the work items, I just split them off into milestones and organized them
[14:41] <Zdra> seb128, I added gnome3-builds PPA and now clicking any link opens firefox instead of respecting my preference which is epiphany. (just to let you know in case that's a bug in those packages) :)
[14:53] <ricotz> seb128, hi, would you mind using debsrc3 for the gnome-desktop3 package?
[14:57] <seb128> Zdra, weird
[14:57] <seb128> ricotz, hey, it already does in the current commit I did to the debian vcs
[14:57] <seb128> ricotz, why do you need it?
[14:58] <ricotz> seb128, ok, just looked at the ppa, it should be mandatory for new source packages ;)
[14:58] <seb128> well the ppa vcs has it as well
[14:58] <seb128> it's 3.0 quilt
[14:59] <ricotz> ok, i only looked at the uploaded package
[14:59] <seb128> ricotz, hey, it was just not a "new source", we used the gnome-desktop packaging
[14:59] <seb128> but it's already fixed in the vcs
[14:59] <ricotz> alright ;)
[15:03] <nessita> hello people! packaging question: I'm starting a branch from scratch to create a new package. Is there a way of suing bzr merge-upstream to create the needed directory structure?
[15:04] <nessita> using*
[15:08] <rodrigo_> nessita, merge-upstream only merges the source code for the upstream, AFAIK, so you'll have to create debian/ still
[15:08] <nessita> rodrigo_: I used to use it without having the debian dir
[15:08] <nessita> rodrigo_: now I'm getting http://pastebin.ubuntu.com/528196/
[15:08] <rodrigo_> right, it doesn't need a debian dir, it just merges a tarball into a branch
[15:09] <rodrigo_> hmm, I guess he needs a previous version in debian/changelog?
[15:10] <nessita> rodrigo_: right, but there is none :-)
[15:10] <nessita> since this is the first time I'm packaging this project
[15:10] <rodrigo_> nessita, if so, import the tarball into the branch "by hand", and then add the debian/ dir, next time merge-upstream should work
[15:10] <rodrigo_> but there might be a better way
[15:11] <rodrigo_> seb128, pitti, didrocks ^^
[15:11] <nessita> rodrigo_: how can I import it "by hand"?
[15:11] <rodrigo_> nessita, tar xvzf tarball && bzr add $all_files
[15:11] <rodrigo_> but wait for others's answers, there might be a better way
[15:12] <didrocks> hey nessita
[15:12] <didrocks> nessita: I think upstream is you, so in bzr as well?
[15:12] <nessita> didrocks: yes!
[15:12] <didrocks> nessita: bzr branch trunk packaging
[15:12] <didrocks> cd packaging
[15:12] <didrocks> bzr tag upstream-0.0.1
[15:12] <didrocks> (or whatever :))
[15:13] <didrocks> then, add your debian dir and make the first version without merge-upstream
[15:13] <didrocks> bzr add
[15:13] <didrocks> bzr commit -m "initial packaging" && debcommit -r
[15:13] <didrocks> then, you will be able to use merge-upstream
[15:13] <nessita> didrocks: there is no trunk yet
[15:13] <didrocks> nessita: you are packaging something without any code ? :)
[15:14] <rodrigo_> nessita, he means trunk from your project
[15:14] <nessita> didrocks: there is no trunk for the package, yet.
[15:14] <nessita> ah!
[15:16] <rodrigo_> hmm, can't build any introspection stuff on natty :(
[15:17] <rodrigo_> nessita, didrocks: although bzr branch trunk... will have the bzr history for the source project
[15:17] <nessita> exactly
[15:17] <rodrigo_> I would copy the tarball's contents and start the branch from that
[15:17] <rodrigo_> but if didrocks says to do that, believe him more than me :)
[15:18] <didrocks> rodrigo_: I never did that for the 20 packages I handle like that, common history means also common files id and less trouble in the future :)
[15:18] <rodrigo_> ah, ok
[15:18] <seb128> rodrigo_, why not?
[15:18] <seb128> rodrigo_, what do you try to build?
[15:19] <rodrigo_> seb128, librest, ubuntuone-client and a couple others I don't remember right now
[15:19] <rodrigo_> looking now what's wrong
[15:20] <rodrigo_> maybe I'm missing some package?
[15:20] <seb128> well without details on your error I can't say
[15:21] <rodrigo_>   GISCAN RestExtras-0.7.gir
[15:21] <rodrigo_> Namespace is empty; likely causes are:
[15:21] <rodrigo_> * Not including .h files to be scanned
[15:21] <rodrigo_> * Broken --identifier-prefix
[15:21] <rodrigo_> the same in all modules I've tried
[15:22] <boulabiar> didrocks: hmm seems best time to ask you about packaging ginn
[15:22] <didrocks> boulabiar: you can just ask on the channel, if someone is around and can answer, she/he will :)
[15:23] <seb128> rodrigo_, do you get the issue if you build libwnck?
[15:23] <rodrigo_> let me try
[15:23] <rodrigo_> from the package?
[15:23] <boulabiar> I want to package it but will be able to push changes anytime
[15:26] <rodrigo_> seb128, hmm, libwnck builds fine
[15:26] <seb128> rodrigo_, ok, so it's a bug in your sources I guess
[15:27] <seb128> rodrigo_, they probably didn't get updated for the abi changes in gir > 0.9.3
[15:27] <rodrigo_> yes, in u1-client, it's missing the _NAMESPACE line, but not librest
[15:27] <seb128> 0.9.5 or higher changed things
[15:27] <seb128> well GNOME sources changes the options called in makefiles as well
[15:27] <seb128> check maybe what they did there
[15:28] <rodrigo_> ah, wait:
[15:28] <rodrigo_> RestExtras-@API_VERSION@.gir: librest-extras-@API_VERSION@.la Makefile
[15:28] <rodrigo_> RestExtras_@API_VERSION_AM@_gir_NAMESPACE = RestExtras
[15:28] <rodrigo_> it's using API_VERSION and APT_VERSION_AM
[15:28] <rodrigo_> right:
[15:28] <rodrigo_> API_VERSION = 0.7
[15:28] <rodrigo_> API_VERSION_AM = 0_7
[15:33] <rodrigo_> right, that, and missing --identifier-prefix
[15:36] <nessita> didrocks: when you have a moment, I'd like to ask your input in something related to setup.py for python projects
[15:36] <didrocks> nessita: sure, not right now, but in 30 minutes should hopefully be good
[15:36] <nessita> didrocks: awesome, would you ping me?
[15:36] <didrocks> nessita: sure
[15:36] <nessita> thanks!
[15:43] <Zdra> seb128, FYI that was strange, just started chrome, it said it is not default, clicked to make it default, and now chrome starts when I click links... but changing in gnome-default-applications-properties didn't work :P
[15:46] <seb128> Zdra, where do you click?
[15:46] <seb128> Zdra, do you use something built with gtk3?
[15:46] <seb128> could be a mismatch gsettings gconf
[15:46] <Zdra> seb128, I don't think I have anything using gtk3
[15:47] <seb128> ok, so I'm not sure why the capplet doesn't work
[15:47] <Zdra> seb128, only did dist-upgrade after adding the ppa
[16:17] <lamalex> How do I go about requesting that libjson-glib be updated in Natty?
[16:20] <jcastro> didrocks: are you going to continue triaging unity bugs this cycle?
[16:20] <jcastro> I need to find a bitesize bug as an example, any ideas?
[16:21] <didrocks> jcastro: that's what I'm doing nobody else doing it right now… but I won't have the time to do it full cycle
[16:21] <jcastro> ok so who is supposed to do it?
[16:21] <lamalex> didrocks, you keep doing them before I wake up
[16:22] <lamalex> I go through all of my bugmail and go "ok didrocks already did this nm"
[16:22] <didrocks> lamalex: there is 20 NEW bugs for a week I didn't touch in purpose
[16:22] <didrocks> are*
[16:22] <didrocks> https://bugs.launchpad.net/unity/+bugs?search=Search&field.status=New
[16:22] <jcastro> lamalex: ok so it's supposed to be you?
[16:22] <didrocks> https://bugs.launchpad.net/ubuntu/+source/unity/+bugs?search=Search&field.status=New
[16:22] <didrocks> 29 in fact :)
[16:23] <lamalex> jcastro, I think so..
[16:23] <jcastro> lamalex: ok, I'm going to be doing a bitesize-bug campaign, basically like papercuts but for unity.
[16:23] <didrocks> lamalex: you should begin with that then ^
[16:23] <lamalex> ok, didrocks I will
[16:23] <jcastro> lamalex: so as you get them if they're "easyish" please tag them bitesize
[16:23] <didrocks> jcastro: we should only starts once compiz plugin is in natty
[16:23] <jcastro> and then I will have a campaign to get new contributors starting on bitesize bugs
[16:24] <lamalex> yah
[16:24] <jcastro> didrocks: right, but I am explaining now before we forget
[16:24] <didrocks> jcastro: I would propose also a hug day on compiz and unity (well, 2 in fact)
[16:24] <jcastro> didrocks: yeah I will work with pedro on those
[16:24] <jcastro> don't worry we'll have plenty of those I am sure!
[16:24] <didrocks> unity in particular as we will have a lot of bug resolved by the compiz transition :)
[16:25] <jcastro> I suspect we'll close 300 bugs when it lands
[16:25] <jcastro> and then open 300 new ones!
[16:26] <lamalex> didrocks, do you know about how to get json-glib updated?
[16:27] <didrocks> lamalex: well, as I don't have time to follow closely the glib update, I'm not sure
[16:27] <didrocks> jcastro: hehe
[16:27] <didrocks> hum, weird
[16:27] <lamalex> didrocks, it's not actually part of glib
[16:27] <jcastro> lamalex: ok so like if you can identify bitesize's as they come in that would be <3
[16:27] <didrocks> E: compiz-core: unstripped-binary-or-object ./usr/bin/compiz
[16:27] <didrocks> (that was on purpose)
[16:28] <didrocks> but:
[16:28] <didrocks> Reading symbols from /usr/bin/compiz...(no debugging symbols found)...done.
[16:28] <didrocks> oh, I think I got it
[16:29] <seb128> lamalex, you should ask rodrigo_
[16:29] <seb128> he's the maintainer
[16:29] <rodrigo_> lamalex, well, I don't maintain json-glib, I just use it in couchdb-glib
[16:30] <didrocks> rodrigo_: seems you maintain it now :)
[16:30] <rodrigo_> upstream or the package? :)
[16:30] <didrocks> (congrats!)
[16:30] <rodrigo_> didrocks, :-D
[16:30] <rodrigo_> lamalex, should be safe to upgrade, and I think nothing else uses it
[16:30] <lamalex> rodrigo_, I'm happy to do the work, I just can't find a document explaining how to do it
[16:31] <rodrigo_> lamalex, hmm, the ubuntu-desktop branch should do all the magic
[16:31] <lamalex> it seems like the lp:ubuntu/json-glib package includes the whole source and just just the debian dir
[16:31] <lamalex> which seems weird to me
[16:31] <rodrigo_> lamalex, just branch lp:~ubuntu-desktop/json-glib/ubuntu, add the new version to debian/changelog
[16:31] <rodrigo_> lamalex, and propose that branch (after making sure it builds)
[16:31] <kklimonda_> hmm, looks like I have a hilight set on json-glib - every time it's mentioned I somehow end up reading the discussion ;)
[16:32] <rodrigo_> kklimonda_, :)
[16:32] <kklimonda_> good evening :)
[16:32] <rodrigo_> hello kklimonda_
[16:33] <seb128> lamalex, don't bother with learning packaging for that
[16:33] <seb128> I can do the update for you
[16:33] <lamalex> seb128, ha ok
[16:33]  * lamalex is kind of interested though
[16:33] <lamalex> also I need the package on maverick
[16:33] <lamalex> (or I'd like it)
[16:34] <rodrigo_> seb128, can we upgrade packages now in natty?
[16:34] <rodrigo_> seb128, json-glib one, that is
[16:34] <seb128> rodrigo_, yes
[16:34] <seb128> rodrigo_, do you want to do the update?
[16:34] <rodrigo_> if lamalex wants to learn doing it, I'm ok, if not, sure, I'll do it
[16:35] <lamalex> rodrigo_, I think it'd be good for me to know
[16:35] <lamalex> but I can't find the json-glib project in ~ubuntu-desktop
[16:35] <rodrigo_> lamalex, oh, maybe it's not there
[16:35] <lamalex> I dont think itis
[16:35] <lamalex> there is lp:ubuntu/json-glib
[16:35] <lamalex> is that the same?
[16:35] <rodrigo_> no
[16:35] <lamalex> is that a source package?
[16:35] <seb128> lamalex, debcheckout json-glib
[16:35] <rodrigo_> in that case, branch lp:ubuntu/json-glib
[16:36] <micahg> would any of the GNOME library updates have caused bug 662387 requiring a rebuild?
[16:36] <ubot2> Launchpad bug 662387 in gnome-shell (Ubuntu) "Gnome-shell aborts, can't find schema 'org.gnome.shell" (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/662387
[16:36] <rodrigo_> lamalex, and then -> bzr merge-upstream new-tarball.tar.gz --version $new_version
[16:36] <lamalex> seb128, No repository found for package libjson-glib-1.0-0.
[16:36] <seb128> micahg, I doubt our g-s version uses gsettings
[16:36] <seb128> lamalex, right, which means it doesn't have a specific vcs
[16:36] <micahg> seb128: so, should I update to 2.91.1?
[16:36] <seb128> lamalex, otherwise it would have done the checkout for you, but what rodrigo says
[16:37] <seb128> micahg, you can try, I'm pretty sure we lack depends for it
[16:37] <seb128> it requires a gtk3 stack, updated gjs, etc
[16:37] <micahg> seb128: ah, ok, so I guess I'll just let it be broke until more gtk3 components are in?
[16:37] <seb128> I guess so
[16:38] <seb128> you can try to update but I think it will lack things
[16:38] <micahg> seb128: ok, thanks, I'll plan on updating, but not before some other components
[16:39] <seb128> well if you try let us know what is missing
[16:39] <seb128> we can try to get those in natty next maybe
[16:40] <lamalex> rodrigo_,  bzr: ERROR: Unknown target distribution: natty
[16:40] <micahg> seb128: ok, I just won't have time until later this month to really start digging
[16:41] <didrocks> nessita: ping, sorry, was quite delayed but it's ok now :)
[16:41] <lamalex> rodrigo_, nm
[16:41] <rodrigo_> lamalex, you are on maverick?
[16:41] <seb128> lamalex, you are on maverick?
[16:42] <lamalex> i am on maverick
[16:42] <rodrigo_> right, it doesn't know about natty
[16:42] <seb128> bug #668764
[16:42] <ubot2> Launchpad bug 668764 in bzr-builddeb (Ubuntu Natty) (and 3 other projects) "Add Natty to the list of known distros (affects: 2) (heat: 12)" [Medium,Fix released] https://launchpad.net/bugs/668764
[16:42] <seb128> lamalex, edit /usr/share/pyshared/bzrlib/plugins/builddeb/util.py
[16:42] <seb128> then add natty to UBUNTU_RELEASES
[16:42] <lamalex> yes, I that's why I said nm :)
[16:46] <lamalex> i think one of you guys should just do this, it's erroring when I build
[16:47] <seb128> rodrigo_, ^
[16:47] <lamalex> ah wait it was because I was just doing dbuild
[16:47] <lamalex> so bzr was f'ing it up
[16:47] <rodrigo_> lamalex, bzr bd is what you need
[16:48] <rodrigo_> bzr bd -- -b
[16:48] <lamalex> yeah, I remembered
[16:48] <nessita> didrocks: argh, can I ping you back in 15 minutes? I'm about to have lunch
[16:48] <nessita> :-)
[16:49] <rodrigo_> lamalex, if you can't build it, let me know and I'll do it
[16:50] <seb128> nessita, enjoy your lunch ;-)
[16:50] <didrocks> nessita: sure, enjoy :)
[16:50] <didrocks>  /me quit "tooo late :-)"
[16:51] <nessita> thanks!
[16:58] <lamalex> rodrigo_, how do I tell it not to try and sign the deb?
[16:59] <rodrigo_> lamalex, no idea, I always sign it
[16:59] <rodrigo_> but it's done via debuild, so look at its man page
[16:59] <rodrigo_> in fact, what I run is bzr bd -- -b -k'rodrigo.moya@canonical.com'
[17:00] <rodrigo_> whatever you put after the '--' is passed to debuild
[17:01] <and471> mpt, hey, so I have spoken with kvalo and I shall be starting on the UI code for the Networking mockups :)
[17:01] <mpt> and471, cool bananas
[17:01] <and471> mpt, I ahve done some more work on the toggleswitch thing, if you download this script and run it ( python script.py )
[17:01] <and471> hehe
[17:02] <and471> mpt, http://ubuntuone.com/p/NqF/
[17:02] <and471> mpt, so I have clicking, dragging, snapping - a lot working now :)
[17:03]  * mpt runs the program and watches as all his files are deleted and his credit card stops working
[17:04] <lamalex> woo finally building :)
[17:04] <mpt> and471, the last digit of your PI approximation is wrong. It should be 2, not 1
[17:05]  * mpt ducks
[17:06]  * and471 blames nzmm
[17:07] <and471> mpt, I stole that bit of code so you can blame nzmm :)
[17:07] <mpt> oh, yeah, we have a slightly different value for pi in New Zealand
[17:07] <mpt> That's why our pies taste better
[17:07] <and471> hehe, silly kiwis...
[17:07] <and471> mpt, so is the switch behaving as you expected?
[17:08] <mpt> It's splendid
[17:08] <mpt> I'm wondering whether the sliding "ON" and "OFF" is actually better than leaving them static underneath the sliding switch, though
[17:10] <and471> mpt, basically I just copied the iphone in this case, but I can change it if need be
[17:10] <and471> mpt, I personally think it looks better when they do slide, but that is becuase it is more *shiny* :)
[17:10] <and471> *because
[17:11] <mpt> mm
[17:11] <mpt> The lower left corner is just a tiny bit squarer than the other corners
[17:12] <nessita> didrocks: I'm back, are you available?
[17:12] <didrocks> nessita: sure
[17:12] <and471> mpt, I don't actually know how that would be possible
[17:12] <and471> mpt, I can't see it myself
[17:13] <mpt> and471, the lower right corner is #d4d2d0, but the lower left corner is darker, #d4d0cd. The only way I can think that's happening is if the radius is slightly smaller for that corner. Or if the curve is not starting in quite the same place.
[17:13] <nessita> didrocks: so, I was wondering what's the proper way of dealing with paths within a python project. For instance, at installation time we need to have certain files placed in certain folders. I was wondering what's the proper way to deal with this.
[17:13] <nessita> didrocks: example: providing a DBus service that needs a particular file placed somewhere in the filesystem
[17:14] <mpt> and471, other than that, it's excellent work, well done.
[17:14] <didrocks> nessita: what do you use, in setup.py, python-distutils, python-distutils-extra or distribute?
[17:14] <nessita> didrocks: python-distutils-extra, but I can change to whatever you recommned
[17:15] <nessita> recommend*
[17:15] <didrocks> no python-distutils-extra is fine :)
[17:15] <and471> mpt, thankyou, I shall have a look at that later
[17:15] <didrocks> let's see if there is dbus service file support in it
[17:16] <nessita> didrocks: in my current setup.py, the /usr/lib/<project>/<service> path is hardcoded and I can't sleep at night because of it
[17:16] <didrocks> nessita: I'm not the only one the be stressed easily then :)
[17:17] <didrocks> why the service file should be there?
[17:17] <lamalex> rodrigo_, I can't figure out how to propose a merge on this
[17:17] <lamalex> my branch is at https://code.launchpad.net/~alexlauni/+junk/json-glib-0.12
[17:17] <didrocks> nessita: python-distutils-extra should ship it to /usr/share/dbus-1/services/ automatically
[17:17] <didrocks> (it should just be a services file at the root of your project)
[17:17] <nessita> didrocks: yes to the .service file, but
[17:17] <mpt> and471, ah, the lower left corner pixel is only darker after the first click on the switch after focusing the window -- and then, only when I'm not mousing down on the switch. Mouse down, it gets lighter; mouse up, it gets darker again.
[17:17] <nessita> didrocks: the .service file has a path in it
[17:18] <rodrigo_> lamalex, oh, +junk branches cannot be proposed, afaik
[17:18] <nessita> didrocks: and I'd like that path not be hardcoded. Current example of a .service file:
[17:18] <didrocks> nessita: oh, your "service" itself, ok
[17:18] <nessita> yes
[17:18] <lamalex> rodrigo_,  i couldn't figure out what the correct path was to push to
[17:18] <rodrigo_> lamalex, you should have pushed to lp:~alexlauni/ubuntu/json-glib/json-glib-0.12.0
[17:19] <didrocks> nessita: hum, you need to add this automagic in setup.py so, reading from a service.in generating a service file from the values in it
[17:19] <rodrigo_> lamalex, then you'll see a 'propose for merging' link, and then propose it for lp:ubuntu/json-glib
[17:19] <lamalex> rodrigo_, yeah I tried that and got bzr: ERROR: Invalid url supplied to transport: "lp:~alexlauni/ubuntu/json-glib/json-glib-0.12.0": No such distribution series json-glib.
[17:19] <didrocks> nessita: let me find you an example
[17:19] <nessita> didrocks: right. But how can I fing out which path use to replace?
[17:19] <nessita> didrocks: current .service file is http://pastebin.ubuntu.com/528253/
[17:19] <rodrigo_> lamalex, yeah, it's  lp:~alexlauni/ubuntu/natty/json-glib/json-glib-0.12.0
[17:19] <nessita> didrocks: in a aideal world, /usr/lib/ubuntuone-control-panel is not hardcoded
[17:20] <lamalex> rodrigo_, yes I just tried that right now :P
[17:20] <nessita> didrocks: and I replace that path using something given at installation time
[17:20] <lamalex> and it appears to be working
[17:20] <and471> mpt, ah I see what you mean now, I shall note it but I am a bit busy now, it is definitely something to look at
[17:21] <didrocks> nessita: you hardcoded it in setup.py btw? or you just install it using the .install file?
[17:21] <nessita> didrocks: what's a .install file? I'm not using any
[17:22] <lamalex> rodrigo_, thanks for all of your help! https://code.launchpad.net/~alexlauni/ubuntu/natty/json-glib/json-glib-0.12.0/+merge/40353
[17:22] <didrocks> nessita: in other world, how you say "install ubuntuone-control-panel-backend there…"
[17:22] <lamalex> lots was learned
[17:22] <nessita> didrocks: using data_files
[17:22] <nessita> didrocks:
[17:22] <nessita>      91         ('lib/ubuntuone-client', ['bin/ubuntuone-control-panel',
[17:22] <nessita>      92                                   'bin/ubuntuone-control-panel-backend']),
[17:23] <nessita> maybe that's my problem?
[17:23] <didrocks> nessita: ok, then you just need $prefix support, I have that somewhere, one sec
[17:23] <rodrigo_> lamalex, now you need to ping someone to sponsor the package, I can't do it yet
[17:23] <lamalex> ;) ok
[17:24] <lamalex> didrocks, seb128? ^
[17:24] <seb128> lamalex, didrocks, rodrigo_: ok
[17:24] <nessita> didrocks: so I shouldn't be using .install files? (whatever they are :-p)
[17:24] <didrocks> nessita: no, .install is only for packaging :)
[17:24] <didrocks> nessita: one second, building a skeleton in a pastebin
[17:25] <nessita> didrocks: ok, thanks!
[17:28] <didrocks> nessita: is that understandable: http://paste.ubuntu.com/528257/ ?
[17:28]  * nessita looks
[17:29] <nessita> didrocks: nice! is pretty understandable
[17:29] <nessita> didrocks: I'll fix both ussoc and u1cp setup.py
[17:29] <didrocks> nessita: nice :)
[17:30] <nessita> didrocks: another (not related) question: Chipaca mentioned I had a work item assigned to me in https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-desktop-n-oneconf. Can you please clarify what the work item is?
[17:31] <nessita> didrocks: I'm not sure that "provide dbus method for u1 sso so that a popup dialog isn't needed" is what we discussed in the session, that's why I'm asking
[17:33] <lamalex> and471, that toggle is quite nice
[17:34] <didrocks> nessita: isn't that what you told me? something so that I can ask for signing in without having the u1 sso dialog?
[17:35] <nessita> didrocks: mmmm nopes :-) What we agreed on (I think) is the following:
[17:37] <nessita> * the installer will use the current (existent) dbus service to login a user (this dbus service is located at com.ubuntu.sso, object path /com/ubuntu/sso/accounts, interface com.ubuntu.sso.UserManagement). The method name is 'login', and it returns the SSO credentials
[17:37] <nessita> * the installer will store the credentials <somewhere>
[17:38] <nessita> * at first boot, the installer will grab those credentials from <somewhere> and store them using the new (this is new, yes) dbus method
[17:38] <nessita> didrocks: so my work item would be to provide this dbus method to store credentials.
[17:38] <didrocks> nessita: yeah, I mix the "store them using the new dbus method", sorry for the wording, can you update the wi?
[17:39] <didrocks> waow, Shift + w is a shortcut for the expose mode in compiz now
[17:39] <nessita> didrocks: sure! but I wanted to be in synch with you
[17:39] <and471> lamalex, thankyou :)
[17:39] <didrocks> weird when you try to type wi in capital letters :)
[17:39] <nessita> didrocks: FYI, the new dbus method is already in place, but crashes because the keyring can't be accessed within a thread (!)
[17:40] <nessita> but yes, we need to fix that (Still trying to see how we're fixing it, no clear view of that)
[17:40] <didrocks> nessita: nice (or sort of nice :)). Thanks for the info
[17:40]  * rodrigo_ bbl
[17:42] <nessita> didrocks: blueprint updated and branch linked
[17:42] <didrocks> nessita: thanks :)
[17:42] <seb128> lamalex, you need at least to update the gobject-introspection build-depends to match the configure requirement
[17:42] <seb128> in the json-glib update
[17:44] <seb128> lamalex, you need also to update the shlibs or build a .symbol
[17:44] <seb128> kenvandine, ^ do you think you could help lamalex to get the json-glib update done?
[17:46] <lamalex> updated the build-depends
[17:47] <nessita> didrocks: where can I learn what directories/files are automatically handled by distutils-extra?
[17:47] <lamalex> seb128, shouldn't shlibs be handled automagically?
[17:48] <lamalex> isn't that why it depends on $shelibs
[17:48] <didrocks> nessita: /usr/lib/python2.6/dist-packages/DistUtilsExtra/auto.py, at the top, you have a description
[17:48] <nessita> didrocks: thanks!
[17:48] <didrocks> yw :)
[17:49] <seb128> lamalex, no, there is no easy way to know what symbols were in the previous version or added in the source you build
[17:50] <lamalex> Why is that part of the packaging?
[17:52] <seb128> lamalex, because depends are part of the packaging system
[17:52] <seb128> lamalex, http://wiki.debian.org/UsingSymbolsFiles
[17:52] <seb128> lamalex, there is nothing which tell you in a reliable way what symbol has been added when in the upstream world
[17:53] <seb128> debian used to use shlibs
[17:53] <seb128> which is a way to say "this version has the current api, so depends on it if you want to be sure to work"
[17:53] <seb128> the maintainer had to bump that number every time the abi change
[17:53] <seb128> nowadays we have symbols
[17:53] <seb128> basically the dpkg wrapper checks all the symbols shipped
[17:54] <lamalex> ah
[17:55] <lamalex> i dont really get how to make a symbols file, that wiki page isn't very helpful if you're not familiar with the whole thing
[17:56] <lamalex> do I need to manually write a list of the symbols?
[17:57] <seb128> no
[17:57] <seb128> dpkg-gensymbols do that for you
[17:57] <seb128> kenvandine, ^ can you help him?
[17:57] <seb128> I'm to finish some task and run for sport in 15 minutes
[17:57] <kenvandine> seb128, sure can
[17:57] <james_w> https://wiki.ubuntu.com/stefanlsd/dpkg-gensymbols might help
[17:57] <seb128> james_w, hey ;-) thanks
[18:00] <lamalex> this packaging stuff is for the birds man
[18:00] <lamalex> I don't know how you guys do i
[18:00] <kenvandine> hehe
[18:00] <kenvandine> lamalex, is that link more helpful?
[18:01] <lamalex> kenvandine, not sure. reading it now
[18:01] <lamalex> it certainly has more on it
[18:11] <nessita> didrocks: have slot for another distutils extra question?
[18:14] <didrocks> nessita: sure
[18:15] <nessita> didrocks: when the help says "* D-Bus (*.conf and *.service)" or "* GtkBuilder (*.ui) [installed into prefix/share/<projectname>/]", how can I know in which directory should I place the .service and .ui files?
[18:15] <nessita> didrocks: so those are correctly grabbed and used
[18:19] <didrocks> nessita: it's in src
[18:19] <didrocks> for f in src_fileglob(src, '*.service'):
[18:34] <nessita> didrocks: right. Another question (can't promise it will be the last one :-P): what command should I override to customize the cleaning process?
[18:35] <didrocks> nessita: something like "clean"? :)
[18:36] <nessita> didrocks: I don't see the DistUtilsExtra.auto.clean definition in order to override it
[18:37] <didrocks> nessita: it's clean_build_tree you should call at the end
[18:38] <didrocks> nessita: so, override the clean call, and inherite from a clean_build_tree class
[18:39] <nessita> didrocks: when you say clean call you mean the 'clean' key in the cmdclass dict, right?
[18:41] <didrocks> nessita: no, I mean something like that: http://paste.ubuntu.com/528285/
[18:41] <didrocks> (the latest call of run())
[18:43] <nessita> didrocks: that's what I meant! :-P
[18:44] <didrocks> nessita: ok, I was thinking you were speaking about the cmdclass={'clean': BlablaClean}) line where I was speaking about the DistUtilsExtra.auto.clean_build_tree.run(self) call :)
[18:45] <nessita> didrocks: kinda, but I understood correctly, so thanks,
[18:45] <didrocks> nessita: yw :)
[18:48] <nessita> didrocks: why not using super() instead of DistUtilsExtra.auto.clean_build_tree.run(self) ?
[18:48] <nessita> same question for install)auto
[18:48] <nessita> install_auto*
[18:48] <didrocks> nessita: no reason, that's better to use super() indeed
[18:49] <didrocks> well, at least, no reason I can think of :)
[18:49] <nessita> ack :-)
[18:58] <didrocks> dinner and sport, goodnight everybody!
[18:58]  * didrocks quit
[19:33] <bryceh> seb128, can you assign this blueprint over to me?  https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-easy-wayland-testing
[20:51] <rodrigo_> any idea why I get this: http://pastebin.ubuntu.com/528353/
[20:51] <rodrigo_> if I remove the dh --with-autoreconf line, it doesn't fail, but it fails on missing ./configure, although it is in the upstream tarball
[20:52] <chrisccoulson> rodrigo_, the dh --with autoreconf cleanbuilddir line seems wrong, the list should be comman separated
[20:52] <chrisccoulson> *comma
[20:52] <rodrigo_> hmm
[20:53] <chrisccoulson> at least, i think so ;)
[20:53] <rodrigo_> %::
[20:53] <rodrigo_>         dh --with autoreconf $@
[20:53] <chrisccoulson> oh
[20:53] <rodrigo_> the upstream tarball doesn't have an autogen.sh, that's why I added that
[20:54] <rodrigo_> debian/rules -> http://pastebin.ubuntu.com/528357/
[20:55] <chrisccoulson> ah
[20:55] <chrisccoulson> i guess mixing CDBS and dh7 might not help there
[20:56] <chrisccoulson> yeah, some CDBS target has a dependency on cleanbuilddir, which triggers the match-all target in your debian/rules
[20:56] <chrisccoulson> and cleanbuilddir is not a valid debhelper target
[20:56] <chrisccoulson> that's the problem :)
[20:58] <chrisccoulson> rodrigo_, so, you need to decide between dh7 and cdbs. if you use cdbs, then you should drop the match-all target from debian/rules and include /usr/share/cdbs/1/rules/autoreconf.mk
[20:58] <rodrigo_> ah, ok
[20:58] <rodrigo_> what would you suggest? dh or cdbs?
[20:59] <chrisccoulson> or you could use dh7, which would mean you'd drop the CDBS includes, and then use the dh7 way of specifying configure flags
[20:59] <chrisccoulson> most people are moving from cdbs to dh7
[20:59] <rodrigo_> ok
[21:00] <chrisccoulson> if you use dh7, i think you need to provide an override_dh_auto_configure target, which calls dh_auto_configure with your configure arguments
[21:00] <chrisccoulson> the manpage for dh_auto_configure might say how to do that though
[21:01] <chrisccoulson> i don't use dh7 yet
[21:18] <latenite> Hi folk, I use pam_usb and a usbstick to login to my system. All I editet in /etc/pam.d/ is http://pastie.org/1282660 BUT after successfully login in WITH the stick I STILL get asked for the keyring password? I ont want that! How do I unlock the keyring also? Thanks
[21:20] <latenite> anybody up in here?
[21:24] <charlie-tca> latenite: yes, people are here, but support is in #ubuntu
[21:24] <latenite> ohh ok did n know
[21:24] <latenite> what in here?
[21:25] <charlie-tca> home of the Desktop team
[21:25] <charlie-tca> mostly the developers
[21:25] <rodrigo_> ok, now it builds!
[21:25] <rodrigo_> not sure if it's a hack what I came up with, so will push my branch for a review
[21:27] <latenite> charlie-tca, oh ok :) sorry for jumping in so quick...did n know :)
[21:27] <charlie-tca> no problem
[21:35] <seb128> bryceh, done
[21:36] <bryceh> seb128, thanks
[21:36] <seb128> np
[21:36] <seb128> bryceh, you probably want to update the workitems, or at least the distro serie
[21:38] <bryceh> seb128, ok
[22:37] <czajkowski> kenvandine: what does one do when Unity has a hissy fit and freezes doing ctl alt F1 seems less than a great solution