[00:00] <sistpoty> (and don't ask about my mail setup, it's just horribly broken atm, and I'm using kmail at work box even from home)
[00:01] <slangasek> sistpoty: done
[00:01] <sistpoty> thanks!
[00:03]  * sistpoty needs some sleep now... gn8 everyone
[00:04] <mdeslaur> pochu: would you object to me backporting the GtkStatusIcon stuff to lucid's liferea so the tray icon looks pretty with the new theme?
[00:05] <Linux000> Is this where anyone wanting to start out fixing bugs/developing for ubuntu should be?
[00:05] <mok0> Yep
[00:05] <persia> Linux000: This is one of many places that it's good to start.
[00:05] <Linux000> thanks
[00:05] <persia> Linux000: What sort of work do you like to do, and how familiar are you with debian-format packaging?
[00:07] <Linux000> persia: I am just starting out with packaging, so not much
[00:07] <persia> Are there any particular areas that interest you?
[00:09] <Linux000> Right now, I don't know much about it, so not really
[00:10] <persia> In that case, I'll recommend you get started with bugsquad.  Reviewing the bugs, and working with packages to test things is a great way to build deeper understanding of how things work.
[00:11] <Linux000> Thanks
[00:11] <persia> Since you have an interest in development, you're sure to encounter some bugs that you have some idea how to fix.  Ask questions here, and we'll help or send you to people who may know better.
[00:11] <persia> The bugsquad tends to hang out in #ubuntu-bugs, and there's lots of good docs in the /topic there.
[01:51] <Linux000> Anyone know how to search for bytesize bugs in launchpad?
[01:54] <Pici> !bitesize
[01:54] <Pici> Linux000: ^^
[01:55] <Linux000> didn't know that(new to irc) thanks
[01:58] <itachi> hello
[02:02] <pochu> mdeslaur: not really, but test it thoroughly :)
[02:02] <pochu> mdeslaur: why does it look bad, the new theme is transparent?
[02:03] <itachi> pochu: what up, d0c?
[02:03] <mdeslaur> pochu: bug #532789
[02:15] <itachi> ejat: wah...
[02:15] <ejat> ?
[02:17] <itachi> ejat: orang indo?
[09:12] <zgreg> I'm still a bit confused about the feature freeze exception process.
[09:12] <zgreg> https://bugs.launchpad.net/ubuntu/+source/libass/+bug/529860
[09:12] <zgreg> "please go ahead", that's not meant for me, is it? since I don't know what I should do :)
[09:18] <dbell> Hi, I'm wondering if anyone can help me here. I've packaged my game and I've got a .desktop file that gets placed in /usr/share/applications and when installing package it says that its rebuild the desktop.cache file (and my game is listed in there, and seems to be complete). I can see my icon in the /usr/share/applications folder - but it's not appearing in the Menu. This is lucid btw (and I've tried installing on karmi
[09:18] <dbell> c and it appears in the menu). Is there anything specific I need to do to get my icon in the menu on lucid?
[09:23] <randomaction> zgreg: if you don't have the upload rights, the sponsors will pick this bug up
[09:25] <randomaction> dbell: try installing the icon in /usr/share/pixmaps
[09:27] <dbell> in addition to having them in /usr/share/icons/hicolor?
[09:27] <zgreg> randomaction: ok
[09:27] <zgreg> that's all I need to know, thanks
[10:26] <randomaction> dbell: I thought you had the icon in /usr/share/applications. Anyway, one instance of icon should be enough. Refer to http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec and http://freedesktop.org/wiki/Specifications/icon-theme-spec
[10:29]  * persia notes that if several versions of an icon are available, hinting the icond cache can provide a better user experience
[10:36] <dbell> randomaction: thanks. I think my .desktop file is fine, desktop-file-validate ran fine, and in karmic, it appears in the menu. Just when installing in lucid it doesn't.
[10:43] <persia> dbell: Could you pastebin the .desktop file (or otherwise point me at it)?
[10:47] <dbell> yea sure, gimme a sec
[10:48] <dbell> persia, http://pastebin.ubuntu.com/389509/
[10:51] <persia> Try "Categories=Game;ActionGame;" or "Categories=Game;ArcadeGame;"  There's some logic in the games menu to group/select games which might cause that.  I can't see anything else that might cause it not to appear.
[10:52] <dbell> ok I'll give it a try
[10:55] <persia> dbell: Hrm.  That doesn't seem to be it.  There's something else wrong, which is masking lots of .desktop files.
[10:55] <dbell> yea, was just about to say... did not work
[10:55] <dbell> is /usr/share/applications the only place I need to install the .desktop file?
[10:55] <persia> Yes.
[10:56] <persia> There appears to be a regression in gnome-menus.
[10:57] <dbell> so the mistake is on lucid and not with my package/.desktop file?
[10:58] <persia> The only issue your .desktop file had was with not specifying the *type* of game.
[10:58] <persia> That's a minor bug, but worth fixing.
[10:58] <persia> There's something else wrong.
[10:58] <dbell> well, I changed that now - added ArcadeGame as suggested.
[11:03] <persia> dbell: I don't understand what happened.  I had your bug replicated, even refreshing the menu cache a few times.  I moved a file, copied it back, and edited it.  Then the menu worked, without a cache refresh.  I moved the original file back overwriting my edits.  I then refreshed the cache a few times, and it's still fixed.
[11:04] <persia> dbell: If you can figure out what changed that made it not work, please report a bug, but I can't figure it out from the state of my local environment :(
[11:22] <dbell> persia: thanks for your help anyway :(. When you say find out what changed to make it not work, do you mean what changed in karmic version to lucid version?
[11:23] <persia> Actually, I suspect it was in the last few days.  Test with Lucid Alpha 3: that likely works.
[11:24] <persia> Wouldn't surprise me if it was a side effect of work on bug #517616 although it might be something else.
[11:24] <dbell> ah good idea. Thanks I will do (and then if It works in alpha 3, and doesn't work with "current" lucid - which it doesn't) I should file a bug, saying that it works in a3 and broken now?
[11:27] <sebner> Please tell me that there is a gconf value for the changing the windows controls back (from the left to the right) or /me waves goodbye
[11:28] <persia> dbell: Looks like it's an artifact of continuous upgrades, and one has to regenerate the cache if one ever had a buggy version.
[11:30] <dbell> Ah, so all the upgrades might have caused this?, How do you regenerate the cache?
[11:31] <persia> See comment #10 in that bug.  If that doesn't work for you, something else is wrong.
[11:32] <persia> I don't know why mine works right now, or how I made it work.
[11:59] <dbell> persia: sorry for delay. comment #10 didn't work. I'm going to try it with alpha-3 soon. Also didn't work with moving and copying the files back that you suggested earlier.
[12:00] <persia> dbell: I wouldn't actually expect what I did to work.  There's no good reason for it.  But the half of my menu items that were missing magically appeared again (and I don't know why)
[12:00] <persia> That *should not* have done anything.
[12:01] <persia> That's why I'm asking you to file a bug, because you still have the symptom.
[12:01] <dbell> yea, I will. Which package? gnome-menus?
[12:07] <persia> dbell: If you're using GNOME: gnome-menus.
[12:07] <persia> If you're using something else, your menu provider.
[12:46] <jetienne_> q. i got a .deb generated by checkinstall. And i would like to upload it in a repository managed by mini-dinstall. but mini-dinstall seems to require a .changes and checkinstall doesnt provide it. Any suggestion on how to fix this ?
[12:46] <persia> don't use checkinstall :)
[12:46] <jetienne_> persia: well this is not me using it :) aka not in my control
[12:46] <persia> more seriously, it's potentially possible to make it work, but the amount of effort required is likely larger than packaging it properly in the first place.
[12:47] <persia> jetienne_: Do you have source?
[12:47] <jetienne_> persia: i was thinking about building my own .changes... is that ferasable
[12:47] <persia> It is, but there are easier ways to work around it.
[12:47] <jetienne_> persia: yep
[12:47] <persia> Excellent.  If you have source, you can package it properly.
[12:47] <jetienne_> persia: ok listening for anything easy :)
[12:47] <jetienne_> you said easy :)
[12:48] <persia> I did.
[12:48] <jetienne_> ok building a pacakge of a full window manager, which i didnt wrote, is not easy for me
[12:48] <persia> Do you need to do anything special to build it, or is it just python-distutils, or simple ant, or make; make install, etc. ?
[12:48] <persia> I will attempt to prove you wrong :)
[12:49] <jetienne_> believe me, you cant :) i wrote like 4 packages this weak, and the 5th is not under my control
[12:50] <jetienne_> persia: all repositories managers requires the .changes ?
[12:50] <persia> All the good ones.
[12:50] <jetienne_> persia: ok what are the bad ones :)
[12:51] <persia> The only one I know is manual management of files and manual editing of the Packages file.
[12:51] <persia> That's completely unautomated, likely to break in unexpected ways, and infinitely flexible.
[12:51] <jetienne_> yep
[12:51] <jetienne_> ok so no good solution for me .... not sure what to do
[12:51] <jetienne_> persia: i understand your point about proper packaging tho. thanks for your h
[12:51] <jetienne_> elp
[12:52] <persia> Shouldn't take more than 30-45 minutes to package it.  Are you sure?
[12:52] <persia> (can take 5 if the licensing is clean)
[12:52] <persia> (can take weeks if the licensing is insane and the buildsystem is dysfunctional)
[12:53] <jetienne_> persia: for you. for me this is like 3h with proper help. and then 1 week to convince external people, then *i* have to maintain his package for life :)
[12:53] <jetienne_> persia: but be sure i do appreciate your help. may be back soon if i can convince the other personn
[12:53] <persia> For me, it usually takes about 20-30 minutes to teach someone to package something properly whilst they do it.  You sure you don't want to try?
[12:53] <jetienne_> :)
[12:54] <jetienne_> persia: im sure i dont now, yes. because my wife is calling for lunch ;)
[12:54] <persia> OK.  I'll likely be in prolonged idle when you get back from lunch, but catch me another time.
[12:59] <persia> Cool!  edit-patch hit lucid.  No more worries about which patch system is in use.
[13:00] <persia> (but no manpage for edit-patch :( )
[13:00] <sebner> persia: hrm hrm hrm?
[13:00] <persia> sebner: Feel like writing a manpage?
[13:00]  * sebner doesn't even know that edit-patch is (besides I should really quit IRC and start learning)
[13:01] <persia> If you're not studying for your exam, you can be learning about edit-patch :)
[13:02] <sebner> persia: that's the problem, If I don't start studying soon I'll not doing it at all which is good for Ubuntu but really bad for me ^^
[13:02] <persia> Then you might want to close/hide your IRC client :p
[13:04] <sebner> persia: If that would be that easy .. :P
[13:04] <persia> You set up your computer to have IRC in a hard-defined region of your root window?
[13:05] <sebner> heh
[13:05] <sebner> persia: citat: The spirit is willing but the flesh is weak.
[13:05] <persia> Anyway.  It's not that hard to stop paying attention.  Watch:
[13:08] <sebner> persia: I'm watching ;)
[13:12] <sebner> persia: Do you intend to write something? ^^
[13:14] <mok0> sebner: I think he's paying attention... to other things :-)
[13:14] <sebner> mok0: I thought he wanted to write something after "Watch:"
[13:15] <mok0> sebner: "watch me paying attention to other things" :-)
[13:15] <mok0> ScottK around  yet?
[13:17] <sebner> mok0: ohohoo, I missunderstood xD
[13:17] <mok0> sebner: IRC will be your doom :-)
[13:18] <sebner> ACK
[13:18] <sebner> christoph_debian: around?
[13:19] <mok0> Hmm, sunny outside today... time for a walk. BBL
[13:19] <sebner> hf mok0
[13:19] <mok0> sebner, thx
[13:22] <christoph_debian> sebner: ja
[13:24] <dbell> persia: I've filled a bug #533264 is there anything that I've missed that should be included?
[13:24] <sebner> christoph_debian: supertux misses a .desktop file. There is supertux2.desktop but it doesn't get installed, I edited *.install to ship it but there is the problem with the icon which is in ./games/supertux2/images/engine/icons/supertux.png
[13:25] <christoph_debian> sebner: oh
[13:26] <christoph_debian> hm probably adding the icon to *.links can have a look later (awesome user so don't necessarily see fdo menus)
[13:26] <sebner> heh
[13:27] <sebner> christoph_debian: anyways, I wait until the sync is processed and then we have to fix it, just wanted to let you know as I'm now really out studying
[15:05] <lfaraone> Can I use CDBS to build a Python C extention which uses a makefile for all supported Python versions?
[15:05] <lfaraone> (preferably with minimal overrides)
[15:05] <lfaraone> I understand how to do so if upstream used setup.py, but alas....
[15:10] <DktrKranz> lfaraone: yes, IIRC
[15:10] <DktrKranz> dh7 (from 7.3.5) for sure, though
[15:11] <lfaraone> DktrKranz: in "zen mode"?
[15:11] <DktrKranz> oh... no. I misread. It works only for distutils-based packages
[15:11] <lfaraone> DktrKranz: so I figured :(
[15:12] <DktrKranz> lfaraone: if you need a working example, I can provide one (it uses dh7, but can be easily adjusted)
[15:12] <lfaraone> DktrKranz: I'm not wedded to cdbs, I'll suse what ever works.
[15:13] <DktrKranz> lfaraone: http://svn.debian.org/viewsvn/python-modules/packages/pyparted/trunk/debian/rules
[15:25] <dupondje> somebody feels working on opensync/synce ?
[15:33] <azeem_> dupondje: in which way?
[15:34] <dupondje> well It needs some adjustmens
[15:34] <dupondje> cause now
[15:34] <dupondje> its just doesn't work ... :(
[15:34] <azeem_> I don't think it will work even with adjustments
[15:35] <dupondje> had it working once
[15:35] <dupondje> but its a mess :( sadly
[15:40] <dupondje> seems like there was put some work in multisync etc, but its useless without good backend imo :(
[15:46] <dupondje> azeem_: you know if there is an alternative ? :(
[15:47] <azeem_> for synce?
[15:47] <azeem_> there's syncevolution for evolution<->syncml syncing
[15:50] <dupondje> azeem_: to sync evolution with windows mobile device
[15:50] <azeem_> I don't think syncevolution does that yet
[15:56] <dupondje> its sad :(
[16:16] <ryanakca> Is it possible to sync package foo from Debian when foo_1.0.1.orig.tar.gz differs in Ubuntu and Debian?
[16:16] <Caesar> crimsun: I've just uploaded a new pacparser to unstable that pretty much addresses all of the changes you made to it in Ubuntu
[16:16] <jpds> ryanakca: No.
[16:16] <ryanakca> jpds: *sigh*, thanks
[16:17] <Caesar> crimsun: how do I get 1.0.9-2 into Lucid?
[17:49] <crimsun> Caesar: simply request a sync of pacparser 1.0.9-2 from Debian unstable main
[18:01] <blueyed> Is it expected behavior that "sudo strace -p $(pgrep X)" freezes the system after some seconds? (from KDE konsole)
[18:05] <hyperair> no, i don't think so
[18:25] <randomaction> Can I assume that clean target is always called before building? This seems to be true for buildds, but Debian policy is a bit unclear about this.
[18:29] <AnAnt> clean target is called before build target, yes
[18:39] <randomaction> So if I unpack the source package and call "fakeroot debian/rules binary", the build is not guaranteed to succeed, right?
[18:58] <paissad_> hi all, do you think possible to get dpkg tools, maintainers tools & so on ... every tool needed to create a .deb package in another system like freebsd for example ?
[19:33] <randomaction> paissad_: Debian has a freebsd port
[19:33] <paissad_> randomaction, i googled some, .... i thought about debootstrap
[19:33] <paissad_> actually, i will use slackware ... not a bsd !
[19:35] <randomaction> so, can you run debootstrap on slackware? I don't know
[19:35] <paissad_> randomaction, what were you thinking ?
[19:36] <randomaction> I think I didn't understand your question
[19:38] <paissad_> randomaction, did you already try debootstrap once ?
[19:38] <randomaction> I only ran it on Ubuntu
[19:38] <paissad_> ok
[22:30] <sistpoty> mr_pouit: would you be willing to act as ubuntu-release delegate for xubuntu packages in universe?
[22:30] <mr_pouit> sistpoty: yeah, sure, no problem
[22:30] <sistpoty> mr_pouit: cool, thanks!
[22:31] <sistpoty> highvoltage: would you be willing to act as ubuntu-release delegate for edubuntu?
[22:54] <arand> How do I change the editor used for dch, and where are the settings trored anyway?
[22:54] <arand> s/trored/stored/
[22:55] <jdong> $EDITOR
[22:55] <jdong> environment :)
[22:56] <hyperair> or $VISUAL
[23:00] <arand> jdong: hyperair: hmm, neither of those seem to have a value set if echoed..
[23:00] <jdong> arand: sensible-editor is the fallback of dch when no value is set.
[23:00] <jdong> but per-user, the recommended way to change the editor preference is EDITOR or VISUAL
[23:01] <jdong> a lot more commands obey the environment variables compared to the sensible-editor fallback.
[23:01] <arand> jdong: So that is what the initial prompt does?
[23:06] <hyperair> sensible-editor seems to use VISUAL and EDITOR as well. so if dch just uses sensible-editor all the way, it'd work too
[23:08] <sistpoty> ScottK: got some insight for FFe bug #527982? would you be willing to do new handling?
[23:20] <arand> hyperair: Ah, got it. ~/.selected_editor *facepalm
[23:48] <duanedesign> what is the LP tag for a bug report that has a patch attached?