[12:13] <soc> is there a chance that the linux-libertine fonts will be updated before gutsy?
[12:13] <soc> currently they are at 2.5.9
[12:13] <soc> 2.6.9 is already available
[01:23] <StevenK> crimsun: Ping, round 2, re: 118734
[01:26] <crimsun> StevenK: pong, round 2
[01:27] <StevenK> crimsun: I'm just a little confused about your comments as to why atlas-cpp can't be synced.
[01:27] <StevenK> crimsun: The second comment you made looks to be incorrect, since only one .deb contains the .la's.
[01:27] <StevenK> crimsun: And I'm not sure what you meant by the first comment.
[01:29] <crimsun> ignore the first comment
[01:29] <crimsun> (hence the "Sorry")
[01:30] <StevenK> Right, okay.
[01:30] <crimsun> Ubuntu's libatlas-cpp-0.6-0c2a contains usr/lib/libAtlas-0.6.la
[01:30] <StevenK> Oh, now I get it.
[01:30] <StevenK> libatlas-cpp-0.6-1 needs to Conflict/Replace libatlas-cpp-0.6-0c2a
[01:30] <crimsun> yes.
[01:31] <crimsun> (hence no sync)
[01:31] <StevenK> crimsun: Right. Sorry for being thick.
[01:31] <crimsun> np
[01:44] <StevenK> Hrm. Shouldn't Debian have made this change, too.
[01:46] <crimsun> looking at packages.do, it looks so
[01:46] <crimsun> if it's made in 0.6.0-3, *then* we could sync :)
[01:50] <StevenK> Heh
[01:50] <pochu> Good night everyone!
[01:51] <StevenK> man-di: So, why doesn't libatlas-cpp-0.6-1 Conflict and Replace with libatlas-cpp-0.6-0c2a? It ought to.
[02:07] <AndyP> perhaps a motu would like to unsubscribe u-u-s from bug #120869 until the debdiff is revised
[02:07] <ubotu> Launchpad bug 120869 in chromium "Game starts paused if you restart it" [Undecided,Confirmed]  https://launchpad.net/bugs/120869
[02:09] <persia> AndyP: Thanks for checking :)
[02:10] <AndyP> y'welcome
[02:13] <AndyP> btw, what do you do with the debdiffs once they're acceptible? just grab the package and use patch, or is there a more clever way?
[02:14] <persia> AndyP: Ignoring the review steps, I just download the source, `patch -p1 < ../patch` from the source directory, and build.
[02:15] <somerville32> I'm setting up pbuilder on my server so that I can work on packages no matter where I am but I'm running into a weird problem. It is trying to fetch index file that is not in my sources list and hence dies.
[02:18] <AndyP> somerville32: can you pastebin the error messages (if any)?
[02:18] <somerville32> I can just paste it here - one line.
[02:19] <somerville32> Failed to fetch http://wine.budgetdedicated.com/apt/dists/dapper/Release  Unable to find expected entry  main/binary-amd64/Packages in Meta-index file (malformed Release file?)
[02:19] <somerville32> Reading package lists... Done
[02:19] <somerville32> E: Some index files failed to download, they have been ignored, or old ones used instead.
[02:19] <somerville32> Ok.... four lines, lol
[02:19] <somerville32> And as to that url, I don't remember adding that.
[02:19] <somerville32> However, I'm not the only one with root access to the machine
[02:20] <AndyP> have you checked /etc/pbuilderrc?
[02:21] <AndyP> or your ~/.pbuilderrc of course
[05:28] <who_cares> I have a question about the phpbb package
[05:28] <who_cares> why is the version set to 2.0.21-6?
[05:29] <who_cares> the latest version is 2.0.22
[05:29] <who_cares> would that be something to package as an update for feisty? gutsy already has .22
[05:30] <RAOF> You'd need to ask for that to be backported.
[05:30] <RAOF> Since Feisty won't be getting new versions of stuff; it's released :)
[05:30] <RAOF> !backport
[05:30] <ubotu> If new updated Ubuntu packages are built for an application, then they go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging
[05:30] <StevenK> And the phpbb package doesn't exist.
[05:30] <who_cares> http://packages.ubuntu.com/feisty/web/phpbb2
[05:31] <StevenK> Ah. The 2 is important. :-)
[05:31] <who_cares> sorry, I was typing that from memory
[05:31] <who_cares> I wasn't sure if the .22 release should go under https://wiki.ubuntu.com/MOTU/SRU because it has some security patches
[05:32] <StevenK> Security isn't handled by SRU.
[05:32] <who_cares> okay
[05:32] <RAOF> and an SRU generally wouldn't be an upgrade to .22, right?  It'd cherry-pick patches.
[05:33] <StevenK> If you can make/generate a patch for .21 to fix the security holes, someone here can do the update.
[05:33] <StevenK> RAOF: Except if you're firefox, it seems. :-P
[05:33] <RAOF> Ah, of course!
[05:34] <who_cares> no new features are added to the 2.x line except bug fixes and security patches, so it should probably be backported
[05:34] <RAOF> Except backports aren't the way to get bugfixes, IIRC :)
[05:34] <StevenK> What we would usually do is take the security patches, and apply them to .21
[05:35] <who_cares> but it would still keep the .21 version number?
[05:35] <StevenK> Yes.
[05:35] <who_cares> is that what the .21-6 is about?
[05:36] <AndyP> the 6 is the debian package revision
[05:36] <who_cares> that would mess up the phpbb version system though
[05:36] <who_cares> and that leaves an error in the admin area
[05:37] <AndyP> i don't see how it would be a problem, it's just the version number of the package
[05:37] <who_cares> phpbb checks the version number it has on hand and compares it to a text file at phpbb.com and if the numbers don't match it shows a warning that the user needs to update
[05:41] <StevenK> And if they're going to update they are going to ignore the Debian packaging system anyway.
[05:41] <who_cares> yeah
[05:41] <who_cares> they have their own version numbers
[06:09] <TheMuso> Heya Hobbsee 
[06:10] <Hobbsee> hey TheMuso :)
[07:05] <crimsun> LongPointyStick: consider using bzr for ~ .  It has saved my butt thrice.
[07:06] <StevenK> Or, gasp, backups.
[07:06] <LongPointyStick> crimsun: it's only .kde/ that i've lost
[07:06] <LongPointyStick> but that's still...very bad.
[07:06] <RAOF> Hm.  bzr for ~.  Sounds like a good idea :)
[07:07] <superm1> what advantage would it have over rsync though - would versioning be that valuable on ~?
[07:07] <crimsun> superm1: it really depends on your usage
[07:08] <crimsun> I have several files I modify heavily, so it's useful to track their changes
[07:08] <crimsun> (yes, I should probably learn to use a real gui planner or something, but TODO doesn't die easily, durnit)
[07:09] <superm1> i guess i missed what happened to Hobbsee, did she accidentally overwrite something in ~/.kde ?
[07:09] <LongPointyStick> yeah
[07:09] <LongPointyStick> the entire folder.
[07:09] <superm1> LongPointyStick,  :(
[07:09] <LongPointyStick> the stupid thing is - i did consider making a backup...
[07:09] <LongPointyStick> though, oh, i'll be careful, i wont need it
[07:10] <superm1> i made the same mistake with installing pidgin in feisty a few days ago.  it apparantly moves your ~/.gaim/logs to ~/.purple/logs and makes the ~/.gaim/logs a symlink instead.  I decided to stick with gaim for now and rm -rf ~/.purple.  Whoops  -there went all my logs
[07:10] <LongPointyStick> heh
[07:11] <superm1> i've got a weekly incremental sbackup setup now though, so stuff like this won't be of worry in the future
[07:22] <zakame> lpsdoom
[07:22] <StevenK> I should resurrect my backup stuff.
[07:23] <StevenK> And update the two spindles of DVDs I have.
[07:34] <Hobbsee> it's mostly just irc logs that are lost, that are the problem
[07:36] <Hobbsee> most of the configs i have on an old backup
[07:43] <TheMuso> Hobbsee: Sounds like you have had a problem... I hope everything is ok.
[07:43] <TheMuso> Data wise.
[07:43] <Hobbsee> TheMuso: i havent lost that much
[07:43] <TheMuso> Hobbsee: Thats good.
[07:43] <Hobbsee> it's mostly irc logs, which i cant recover
[07:44] <TheMuso> I guess it comes down to just how important those logs are.
[07:46] <crimsun> is aptitude(8) (the man page) a bit wonk for anyone else in gutsy?
[07:46] <crimsun> the COMMAND-LINE ACTIONS section, specifically
[07:47] <jussi01> hello everyone
[07:47] <jussi01> hi crimsun
[07:47] <Hobbsee> TheMuso: uh, reasonably
[07:47] <jussi01> hello Hobbsee, TheMuso
[07:47] <TheMuso> Hey jussi01.
[07:47] <Hobbsee> hiya jussi01 
[07:47] <jussi01> :)
[07:48] <jussi01> does anyone know how to use wireless and wired networks simaltaneously?
[07:48] <StevenK> Set it up that way?
[07:48] <Hobbsee> you cant, with nm
[07:48] <StevenK> And yes, that.
[07:48] <jussi01> heheh... ok...
[07:48] <jussi01> :D
[07:49] <RAOF> crimsun: Yes.  A bunch of \fB's and stuff
[07:49] <coNP> hey everyone
[07:50] <jussi01> hi coNP
[08:12] <porthose> could a MOTU nuke a REVU upload for me, ampache-3.3.3.2, I screwed the upload up (look at the .orig.tar.gz) I have it fixed but when I run dput -f it will not show the changes made 
[08:15] <jussi01> porthose: it seems your new upload is there now
[08:18] <porthose> It's showing june 14 and it should say june18 and ampache-3.3.3.2_0ubuntu1.orig.tar.gz should be ampache-3.3.3.2.orig.tar.gz
[08:20] <jussi01> porthose: http://revu.tauware.de/details.py?upid=5611
[08:21] <porthose> cool woks for me I don't know what was up I reloaded the page several times and it did not show oh well thanks 
[08:21] <StevenK> porthose: The upload id will change with each new upload.
[08:22] <jussi01> porthose: there is also http://revu.tauware.de/details.py?upid=5519
[08:22] <jussi01> diferent upload altogether
[08:23] <porthose> k cool If you have time would you mind looking at it?
[08:24] <jussi01> porthose: Im not a motu, sorry, I can look, however, dholbach might have time :P
[08:24] <jussi01> hello dholbach
[08:24] <dholbach> good morning
[08:25] <porthose> dholback: good morning
[08:25] <dholbach> porthose: I don't know what jussi01 is referring to, but if you don't find anybody else to look at, you can drop me a mail at dholbach at ubuntu.com
[08:25] <StevenK> dholbach: Morning! Do you mind if I borrow/steal your bluez-gnome merge?
[08:25] <dholbach> hi porthose
[08:25] <dholbach> StevenK: not at all
[08:25] <Hobbsee> hiya dholbach 
[08:25] <dholbach> heya Hobbsee
[08:25] <jussi01> porthose: so you heard the man, send him an email with the url from revu
[08:26] <porthose> I sure will thanks 
[08:27] <jussi01> he will get to it in order of his emails... so on a monday morning, thatll be a few hours probably.
[08:36] <RAOF> Yay, a new democracyplayer upstream.
[08:42] <RAOF> Eh, I think some of the patches have made it into the upstream release.
[08:42] <RAOF> So, hopefully, there won't have to be quite so much munging around :)
[08:45] <RainCT> hi
[08:57] <dholbach> porthose: did you send the mail?
[08:57] <dholbach> hey Nightrose
[08:57] <RainCT> AndyP: ping
[08:57] <porthose> sure did
[08:57] <Nightrose> hey dholbach
[08:58] <dholbach> porthose: hum.... I didn't get it yet
[08:59] <porthose> resending
[08:59] <dholbach> thanks porthose
[09:00] <RainCT> AndyP: ah ok, nevermind
[09:00] <porthose> dholback: Here is the link http://revu.tauware.de/details.py?upid=5611
[09:01] <dholbach> porthose: downloading it... will let you know later - still fixing some other bits up elsewhere
[09:01] <porthose> cool works for me have a nice day. I'm going to bed it's 0200am
[09:02] <dholbach> porthose: sleep tight :)
[09:02] <porthose> thanks
[09:04] <crimsun> ** Message: don't know how to handle audio/x-m4a
[09:04] <crimsun> hmm, this is new.
[09:04] <dholbach> porthose: I'm 'dholbacH', not 'dholbacK' - maybe that's why I didn't get the mail?
[09:05] <porthose> could be going to resend
[09:05] <dholbach> porthose: it's fine now, I have the package downloaded
[09:05] <porthose> k going to change my contacts 
[09:06] <crimsun> (hmm, no, gst-typefind-0.10(1) seems more appropriate)
[09:09] <AndyP> RainCT: pong, if it still applies
[09:12] <jussi01> can some one tell me what apt-build does and when id use it?
[09:13] <crimsun> the former should be outlined in its Description (`apt-cache show apt-build`).  The latter may be "if you feel your CPU(s) are much too idle, and you have a severe rash to burn off."
[09:14] <crimsun> e.g., if you are feeling the urge to recompile some subset of source packages for your shining EM64T.
[09:15] <AndyP> sigh, my brain isn't working this morning... can/should i mark bug #92952 fix released?
[09:15] <ubotu> Launchpad bug 92952 in gnu-smalltalk "[can-not-install]  file overwrite error" [Undecided,Unconfirmed]  https://launchpad.net/bugs/92952
[09:15] <crimsun> yes, you may, and yes, you should.
[09:15] <AndyP> thanks
[09:16] <crimsun> np
[09:16] <jussi01> crimsun: ok, thanks :D
[09:18] <dholbach> thanks StevenK
[09:18] <StevenK> dholbach: No problem.
[10:01] <crimsun> argh, I keep typing gst-launchpad[tab] 
[10:01] <crimsun> silly muscle memory
[10:02] <RAOF> :)
[10:03] <RAOF> Anyone else seeing problems with building gtk programs?
[10:08] <RAOF> Specifically: http://paste.ubuntu-nl.org/26084/
[10:09] <RAOF> (There goes the simple democracyplayer merge :()
[10:14] <RAOF> Intriguing.  Anyone know where /usr/include/gtk-2.0/gtk/gtkbuilder.h comes from?  Neither ubotu nor apt-file seem to give me anything!
[10:14] <Burgundavia> RAOF: the brandnew GTK
[10:15] <Burgundavia> http://blogs.gnome.org/johan/2007/06/15/gtkbuilder-has-landed/
[10:15] <RAOF> Ah.  Ok, so it's not going to show up on my feisty apt-file. :(
[10:15] <RAOF> Oh, *awesome*
[10:17] <RAOF> Now, to work out whether democracyplayer FTBFS due to a bug in the new gtk, or due to something stupid in democracyplayer.  I know where *my* money is.
[10:24] <RAOF> Ok, now I'm confused.  I've looked at the two lines from gtkbuilder.h that raise errors in the democracyplayer build, but they look just fine to me.
[10:25] <StevenK> RAOF: dpatch or cdbs patching?
[10:26] <RAOF> StevenK: CDBS
[10:26] <RAOF> Also, I can't see where you're going with this.  Which is perhaps a good thing, since I can't see what's wrong: )
[10:27] <StevenK> Never mind, I was misunderstanding anyway
[10:28] <StevenK> Oh sigh, does the band next door have to practice *now*
[10:28] <RAOF> Yes, yes they do.
[10:28] <RAOF> The twelve moons of a significant planet in Alpha Centauri are perfectly aligned.
[10:30] <StevenK> Keep giggling, I'm reloading. :-P
[10:31] <RAOF> Please unload in the direction of democracyplayer, then.
[01:08] <shawarma> smcgraw: Please disable public away messages.
[01:47] <jellyfish2002> oops
[01:52] <StevenK> dholbach: I've looked at your pyorbit merge too, that was ... entertaining.
[03:42] <pochu> tarzeau: probably #launchpad is a better place to ask, but you should join the Driver team.
[03:43] <tarzeau> pochu: i already am in the driver team?
[03:43] <tarzeau> pochu: but https://launchpad.net/%7Egurkan-linuks/+participation doesn't list it?
[03:45] <pochu> tarzeau: it lists the teams you're in, not the projects.
[03:45] <tarzeau> aha
[03:45] <pochu> e.g. you can be a project driver, without being in a team, since the project driver can be a person too.
[03:47] <tarzeau> can i show project participation?
[03:47] <tarzeau> i mean, to keep track of what i can work on when bored?
[03:59] <pochu> tarzeau: sorry, I can't understand your question. Project participation?
[03:59] <tarzeau> yes
[03:59] <pochu> What do you mean with it?
[03:59] <tarzeau> the main user page has some useful links, but i'm missing the one telling me what projects i work on
[03:59] <tarzeau> when i go to launchpad home i can't see sauerbraten in any list
[04:00] <tarzeau> but i know i'm something of that project
[04:00] <tarzeau> then i go on holidays, forget everything, i need something to remind me on what stuff i work...
[04:00] <pochu> tarzeau: Look at 'Most active in' at https://launchpad.net/~pochu
[04:00] <Hobbsee> tarzeau: use launchpad.net/~<youruserid>
[04:01] <tarzeau> https://launchpad.net/%7Egurkan-linuks/ nothing about most active there?
[04:01] <pochu> tarzeau: it'll show up on your page when you have some karma on any project :)
[04:01] <tarzeau> pochu: how can i get a karma on that project sauerbraten?
[04:01] <tarzeau> i have 0
[04:01] <pochu> Filling a bug, for example
[04:01] <StevenK> LP doesn't show me active in Debian. I uploaded twice last week!
[04:01] <tarzeau> bugs of it are tracked in the debian bts?
[04:01] <pochu> Or doing translations, or...
[04:02] <tarzeau> StevenK: me too!
[04:02] <pochu> StevenK: LP doesn't give karma for uploads yet
[04:02] <StevenK> pochu: I uploaded to *Debian*.
[04:04] <Hobbsee> StevenK: that wouldnt be regarded as the debian ubuntu knows about - with the bugs and such?
[04:04] <StevenK> Hobbsee: But I've done that too.
[04:04] <StevenK> Linking bug reports and such
[04:04] <tarzeau> StevenK: your debian karma is here http://io.debian.net/~tar/bugstats/?steven
[04:04] <nixternal> gooooooooooood morning Ubuntu MOTU!!!!!
[04:05] <Hobbsee> hiya vista-lover
[04:05] <nixternal> boo
[04:05] <nixternal> http://io.debian.net/~tar/bugstats/?nixternal
[04:05] <nixternal> gahaha, my Karma kicks arse!
[04:06] <StevenK> nixternal: Mine is 3.8
[04:06] <tarzeau> 4.3 here
[04:06] <tarzeau> the more variety of stuff you do, the more karma you can get
[04:07] <nixternal> I still have my 2 ITPs to close, and that should bump me up to a solid 1.3 ;p
[04:07] <tarzeau> (((Source + 1) * (Archived Bugs + 1) * (Sponsored Packages + 1) * (NMUs + 1)) / (Active Bugs + 1)) ^ (1 / 3)
[04:07] <tarzeau> that's the formula
[04:07] <StevenK> If I could be bothered fixing some of the more esoteric Linda bugs, my karam would be better.
[04:07] <StevenK> karma, even
[04:07] <tarzeau> StevenK: or you sponsor packages?
[04:08] <tarzeau> increases karma significantly
[04:08] <StevenK> Ha. Ha ha. Hahahahaha
[04:08] <tarzeau> hehe
[04:09] <AndyP> what's the procedure for flagging that i want to package a "[needs-packaging] " package? assign the bug to myself and mark as in progress?
[04:09] <tarzeau> nixternal, StevenK do you have a 128x128 foto of yourselves? i can add it to that bugstats page if you want
[04:09] <StevenK> tarzeau: Yes, and you can't have it.
[04:17] <AndyP> ...i was thinking of packaging something like pycmdr if no one else is interested in it
[04:18] <geser> AndyP: yes, assigning the bug to you and setting it to "In Progress" should work
[04:18] <bmm> Any  MOTU: The ccbuild package is looking for comments or a second advocate. If you have time, see http://revu.tauware.de/details.py?upid=5572
[04:18] <AndyP> geser: thanks
[05:20] <infinito> can any motu give a little review on this? http://revu.tauware.de/details.py?upid=5532... just a little pygtk app...
[05:33] <DarkSun88> Hi all
[05:39] <cbx33> ping imbrandon
[05:40] <AndyP> hehe awesome. seen on a needs-packaging bug: "needs to be packaged so my wife will love me."
[05:41] <cbx33> heheh
[05:41] <shawarma> AndyP: heh. bug no?
[05:41] <shawarma> cbx33: I have a suggestion for vcsfrenzy.
[05:41] <cbx33> ooh
[05:41] <cbx33> shoot
[05:42] <cbx33> I'm all ears
[05:42] <cbx33> and 2 eyes too
[05:42] <shawarma> cbx33: Instead of doing the notifications yourself, you could generate an rss feed which could in turn be read by liferea or whatever rss reader people use.
[05:42] <AndyP> shawarma: Bug #111738 ... pity the link in it is broken
[05:42] <ubotu> Launchpad bug 111738 in Ubuntu "[needs packaging]  Maitreya" [Wishlist,Confirmed]  https://launchpad.net/bugs/111738
[05:43] <cbx33> shawarma possible
[05:44] <cbx33> give me a run down
[05:44] <cbx33> how you would like it to work
[05:45] <shawarma> Well, vcsfrenzy would do it's check-various-repositories magic and write some rss (or Atom or whatever) to some files which will then be served by a webserver to an rss feedreader.
[05:46] <shawarma> It would make it more complex, but I find that a lot (possibly all) of the UI stuff of vcsfrenzy can be done easily by liferea as well.
[05:47] <shawarma> Well, it wouldn't actually be more complex in itself, but the bzr->vcsfrenzy->rss-file->webserver->rss-client chain is obviously more complex.
[05:47] <shawarma> Hmm... liferea could probably read a file:/// url, so you can leave out the webserver bit, if you want.
[05:50] <shawarma> cbx33: Just a thought for the idea pool :)
[05:52] <cbx33> cool
[05:53] <cbx33> coll I'll keep that on my ideas board
[05:58] <Baby> Hobbsee: hi! :)
[05:59] <Hobbsee> heya!
[06:01] <infinito> can any motu give a little review on this? http://revu.tauware.de/details.py?upid=5532...
[06:04] <Riddell> lionel: you confirmed 120190, but you're not in ubuntu-dev so you don't have rights to do so.  it looks fine though from what I see so I'll sync it, but next time you should describe why you agree its a good idea rather than just confirm it
[06:04] <Riddell> bug 120190
[06:04] <ubotu> Launchpad bug 120190 in scim-canna "Please sync scim-canna 1.0.0-2 from debian unstable" [Undecided,Confirmed]  https://launchpad.net/bugs/120190
[06:05] <lionel> Riddell: I'm in ubuntu-dev
[06:05] <Riddell> are you?
[06:05] <lionel> yes, a new one :)
[06:05] <lionel> (new since 15 days or so)
[06:05] <pochu> infinito: I'd change ' More information:' with '  Homepage:' (indented with 2 spaces instead of one)
[06:06] <lionel> Riddell: https://launchpad.net/~lionel.porcheron
[06:06] <Hobbsee> Riddell: he is.  really
[06:06] <Hobbsee> lionel: didnt you just apply for core too, or something?
[06:06] <pochu> That was mrpouit 
[06:06] <lionel> Hobbsee: no, it's not me. It's mr_pouit
[06:06] <pochu> Which is Lionel too ;)
[06:06] <Hobbsee> ohhh
[06:06] <Hobbsee> right
[06:06] <infinito> pochu: sorry, correct link is http://revu.tauware.de/details.py?upid=5542
[06:07] <infinito> that change is already done...
[06:07] <Riddell> lionel: I don't see ubuntu-dev in https://launchpad.net/~lionel.porcheron/+participation
[06:07] <pochu> Riddell: look at the right column
[06:07] <pochu> Indirect participation.
[06:07] <pochu> infinito: hehe, I was thinking I already told you that ;)
[06:08] <Riddell> gosh how confusing
[06:08] <Riddell> what's the difference between MOTU and ubuntu-dev then?
[06:09] <pochu> Appart of the name? ;)
[06:09] <Riddell> yes
[06:09] <lionel> ubuntu-dev is MOTU + core-dev
[06:09] <infinito> pochu: so hard to get reviews that i need to ask again and again ;)
[06:10] <Riddell> lionel: no, I'm sure it's not
[06:10] <Riddell> lionel: anyway, sorry for the mistake, I'll sync it in a few minutes
[06:11] <lionel> Riddell: no problem :)
[06:16] <pochu> infinito: from http://www.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-bpp-pkg-synopsis, I think it'd be better to remove the first line of your long description in debian/control, since it's the same of the short one.
[06:16] <pochu> infinito: Other than that, find a MOTU to review & advocate it :)
[06:17] <infinito> pochu: thats the difficult part, get a MOTU for a review
[06:17] <infinito> packaging is quite easy, get a review is not so easy...
[06:17] <pochu> You can mail ubuntu-motu@ too...
[06:18] <pochu> Or write in capital leters every 10 minutes asking for it until somebody steps up ;)
[06:20] <infinito> that's the worst thing about motu, you have to be here asking every 10 minutes for getting a review
[06:20] <infinito> and there a re chances that you dont get any review
[06:20] <Hobbsee> yes, doesnt help that a lot of the MOTU are taking breaks - or working on other stuff
[06:21] <infinito> i know MOTUs have other things to do, i understand that
[06:22] <infinito> it's just that i sometimes feel that getting reviews is extremly difficult
[06:22] <Hobbsee> it is
[06:23] <Hobbsee> infinito: ack'd
[06:23] <Hobbsee> infinito: i've asked a python person to do the other ack - i dont grok python stuff much
[06:24] <infinito> Hobbsee: thanks!!
[06:24] <Hobbsee> no problem
[06:24] <Hobbsee> geser: how good are you on python?
[06:25] <infinito> i think not getting reviews discourages people to packaga thing for universe
[06:25] <Hobbsee> this is true
[06:25] <Hobbsee> it's a cycle.
[06:25] <infinito> 'cause you try to package, upload, and there waiting for days for a review... and you say "ok, forget about this"
[06:25] <Hobbsee> i know it's screwed.
[06:25] <Hobbsee> lionel: how's your python?
[06:26] <Hobbsee> seems like a lot arent here this week
[06:26] <lionel> not so good :(
[06:26] <Hobbsee> right
[06:26] <pochu> ScottK's is good.
[06:26] <Hobbsee> he said it wasnt, in the revu report
[06:26] <pochu> Ah, did he?
[06:27] <Hobbsee> actually, he said in some areas - but didnt mention which they were
[06:27] <Hobbsee> [02:27]  [Whois]  ScottK has been idle for 1 day, 10 hours, 47 minutes, and 8 seconds.
[06:28] <infinito> yeps, ScottK tried to help me a few days ago, but he said he was not really good at python packaging
[06:28] <Hobbsee> yeah, damn
[06:28] <Hobbsee> the pythoners are all afk
[06:29] <Hobbsee> guess he's busy
[06:38] <pochu> infinito: have you thought in uploading to Debian too?
[06:39] <geser> Hobbsee: I'm still learning but I'm improving :)
[06:39] <Hobbsee> :)
[06:39] <infinito> pochu: yeps, but not really sure how
[06:40] <pochu> infinito: I joint #debian-python on OFTC, and asked there. Was easy to find a sponsor :)
[06:41] <infinito> pochu: OFTC?
[06:41] <tarzeau> StevenK: you've got a karma of 6. i updated the debian bugstats page. the sponsor info was missing
[06:41] <tarzeau> StevenK: because the grep (qa page changed) was not up to date
[06:41] <infinito> pochu: ok, i found it 
[06:41] <geser> infinito: http://www.oftc.net/oftc/ , another IRC network
[06:42] <tarzeau> any idea if i can do stats on ubuntu like at http://io.debian.net/~tar/bugstats/ (the infos on top)?
[09:03] <zul> anyone know what they mean by branch url when registering a new branch for a team in launchpad?
[09:04] <bluekuja> zul: register it manually
[09:04] <bluekuja> dont use lp web interface
[09:04] <zul> so bzr push blah blah?
[09:04] <bluekuja> just bzr push url
[09:04] <bluekuja> yeah ;)
[09:06] <zul> how do I register a product name? ie I want to push to ~/ubuntu-xen/xen-3.1
[09:07] <bluekuja> zul: you need to create a new project
[09:07] <bluekuja> and then push to it
[09:07] <zul> gotcha
[09:07] <bluekuja> ;)
[09:09] <zul> arrgh bzr: ERROR: File exists: u'/~ubuntu-xen/xen-3.1/.bzr': mkdir failed: unable to mkdir
[09:09] <bluekuja> why are you doing it?
[09:09] <bluekuja> just bzr init
[09:09] <bluekuja> (if not already created)
[09:10] <bluekuja> and then when done locally you publish
[09:10] <zul> already done
[09:10] <bluekuja> oh :)
[09:10] <zul> thats the error I get after I push
[09:11] <bluekuja> strange
[09:11] <bluekuja> did you commit and then push?
[09:12] <bluekuja> did you use sftp?
[09:12] <zul> yep
[09:13] <bluekuja> zul: https://launchpad.net/projects/?text=ubuntu-xen
[09:13] <bluekuja> why there are two projects?
[09:13] <bluekuja> e.g xen-3,1
[09:13] <bluekuja> and ubuntu-xen
[09:13] <zul> no idea
[09:14] <bluekuja> try to push into xen-3.1
[09:14] <bluekuja> then
[09:14] <zul> *sigh* nope
[09:14] <bluekuja> :D
[09:16] <zul> ill try again later when im not falling asleep
[09:16] <bluekuja> lol
[09:16] <bluekuja> ok
[09:16] <bluekuja> :)
[09:42] <sistpoty> hi folks
[09:43] <jrib> hi
[09:46] <nixternal> MOTU: http://revu.tauware.de/details.py?upid=5616   <- can I get an AMEN? I mean a revu :)
[09:49] <crimsun> not going to ping frankie on this IRC net first?
[09:50] <nixternal> already did
[09:50] <nixternal> I want to have it ready just in case
[09:50] <sistpoty> hi crimsun and nixternal
[09:50] <nixternal> hiya sistpoty 
[09:50] <crimsun> right, is he going to update "soon"?
[09:50] <crimsun> hi sistpoty 
[09:50] <nixternal> as of right now, probably not
[09:50] <nixternal> but he could change his mind in the email, which I am hoping
[09:51] <nixternal> you know what, he could very well be at debconf as well
[09:51] <crimsun> it looks fine, but I'm not sure what your intent is given your most recent two statements
[09:51] <sistpoty> mr_pouit: regarding your core-dev application: can you ping your sponsors for some cheers? ;)
[09:52] <nixternal> well, if we don't get anything back by the 21st, then we can upload from revu
[09:52] <crimsun> nixternal: well, it's up to you whether you wish to block on his response if you've already contacted him
[09:53] <nixternal> we are still young in Gutsy, so I can wait a few days until DIF
[09:53] <mr_pouit> sistpoty: gpocentek is sleeping now ^^. But he'll do it tomorrow afaik.
[09:53] <sistpoty> mr_pouit: thanks.
[09:53] <infinito> please please please!! http://revu.tauware.de/details.py?upid=5542 :D
[09:54] <sistpoty> infinito: I'll take a look
[09:54] <infinito> sistpoty: thanks!
[09:57] <nixternal> after the 21st, we can't do any more merges or syncs can we?
[09:58] <crimsun> you still can.  That means autosyncer stops.
[09:59] <nixternal> ahh, OK
[10:02] <sistpoty> infinito: so far only minor stuff: python-gtk2-dev and libgconf2-dev are arch:any, so they shouldn't be in build-dep-indep, but in normal build-deps. python (w.o. version) shouldn't be needed at all, since it gets drawn in by python-support
[10:04] <mathiaz> Hi. What's the difference between Outstanding and Updated merges in Ubuntu Merge-o-Matic ?
[10:04] <infinito> sistpoty: so i move python-gtk2-dev and libgconf2-dev to build-deps and remove Build-Depends-Indep?
[10:04] <sistpoty> infinito: yep
[10:05] <infinito> sistpoty: ok, should i reupload with those changes?
[10:05] <sistpoty> infinito: I'm just test-building the package... if you wait a moment, maybe I'll find some more things
[10:05] <infinito> sistpoty: ok
[10:06] <bmm> Hi MOTU people, I'm looking for the second advocate for ccbuild http://revu.tauware.de/details.py?upid=5572
[10:07] <jrib> looking for a reviewer: http://revu.tauware.de/details.py?upid=5444 .  Thanks
[10:09] <sistpoty> infinito: W: pyrenamer: script-not-executable ./usr/share/python-support/pyrenamer/pyrenamer/__init__.py
[10:10] <infinito> sistpoty: should i add a patch using simplesyspatch to fix that?
[10:10] <sistpoty> infinito: no, just chmod in debian/rules (as you can't fix permissions with patches)
[10:12] <sistpoty> infinito: also, it seems a little bit strange to me, that you need arch-dependent build-dependencies at all, as nothing really gets compiled. have you tried with e.g. python-gtk2 instead of python-gtk2-dev?
[10:12] <sistpoty> (also it looks, like the checks during autoconf don't seem to be right, but I guess that upstream should care about that)
[10:13] <pochu> mathiaz: Outstanding means they haven't been merged since Gutsy opened. Updated means they were merged, but there's another debian version, so it can be merged again.
[10:13] <infinito> sistpoty: im upstream too, but not very good at autotools... :(
[10:13] <sistpoty> infinito: ah... :)
[10:14] <pochu> sistpoty: well, he can fix the permission issue removing the hashbang. Then, lintian won't take it as an script.
[10:14] <sistpoty> infinito: have you tried using python-distutils yet? (instead of autotools)?
[10:15] <pochu> And I think that's the correct thing for modules and stuff that isn't intended to be executabled independently.
[10:15] <sistpoty> pochu: ah, right... and that makes even more sense ... I guess I'm out of practice reviewing :)
[10:15] <infinito> sistpoty: yeps, but i dont know how to use it very well....
[10:16] <pochu> sistpoty: well, I had to do that myself for a couple of packages :)
[10:17] <infinito> pochu, sistpoty: in another package i removed the permission warning adding a pathch that removed #!/bin/python from file, is that correct?
[10:17] <sistpoty> infinito: I guess so
[10:17] <pochu> infinito: right, that's the hashbang ;)
[10:17] <infinito> hehehe
[10:18] <crimsun> /bin/python would be wrong regardless
[10:18] <pochu> infinito: it's correct as long as it's not the main program.
[10:18] <sistpoty> infinito: others than that, the package looks clean (even though my piuparts bailed out with it, but thats a piuparts problem *g*)
[10:18] <pochu> Yeah, should be /usr/bin/python, or /usr/bin/env python
[10:18] <infinito> pochu: i know
[10:18] <infinito> just to lazy to write it here...
[10:19] <pochu> Haha, cool then :)
[10:19] <pochu> Irssi autocompletes with the filesystem when I start with / and hit tab :p
[10:28] <infinito> sistpoty: it seems that i need python-gtk2-dev, if i remove it: "checking for PYGTK... configure: error: Package requirements (pygtk-2.0) were not met"
[10:33] <sistpoty> infinito: yep, seems like the autotools tests are wrong in this regard (but I don't mind if you leave it in build-deps)
[10:33] <infinito> sistpoty: http://revu.tauware.de/details.py?upid=5617
[10:34] <infinito> reuploaded
[10:36] <tsmithe> could somebody look at http://revu.tauware.de/details.py?upid=5594 and explain to me which build-depends should be indep and which shouldn't? i still don't quite get it..
[10:37] <sistpoty> tsmithe: indep should be only stuff that's arch:all and not needed during clean rule
[10:37] <sistpoty> tsmithe: if in doubt, just put in in normal build-deps (as afaict launchpad doesn't care for indep anyways)
[10:37] <tsmithe> hmm... since it's a cdbs package, i'm not sure which is and which isn't
[10:37] <tsmithe> ah ok
[10:38] <tsmithe> sistpoty, could you give it a revu, then please? (and upload if you're kind and it doesn't need two sponsors :p)
[10:38] <nixternal> crimsun: you can deny that smb4k request. frankie just updated it :)
[10:39] <sistpoty> tsmithe: sorry, I need to go to bed soon (I'm now a working citizen)...
[10:39] <tsmithe> hehe ok :)
[10:42] <sistpoty> infinito: just for future reference: please list everything you changed diverging from upstream in debian/changelog (e.g. the patch), as the difference between the plain upstream version is especially interesting if anyone else wants to modify your package
[10:42] <infinito> sistpoty: ok
[10:43] <sistpoty> infinito: but the package is fine with me, uploading it ;)
[10:45] <infinito> sistpoty: thats all? i mean, is it uploaded to universe ? or do i need more reviews?
[10:46] <sistpoty> infinito: it's uploaded, but it still needs to go through ubuntu-archive until it hits universe. and then you should of course watch out for bugs etc. ;)
[10:46] <luisbg> zakame, ping
[10:46] <tsmithe> zakame, you around
[10:46] <tsmithe> damn luisbg you beat me to it
[10:47] <luisbg> tsmithe, muahahahaha
[10:47] <infinito> sistpoty: so thank you very much for helping!
[10:47] <sistpoty> infinito: thanks for contributing! :)
[10:48] <infinito> sistpoty: one more question... what should i do when there's a new upstream version?
[10:48] <infinito> upload to revi again?
[10:49] <infinito> s/revi/revu
[10:49] <sistpoty> infinito: yes... if you fix a bug as a *maintainer* w.o. a new upstream version, it's easier to attach a debdiff to a bug and assign it to ubuntu-universe-contributors. For new upstream versions, revu is better suited.
[10:50] <infinito> ok, thanks!
[10:53] <mok0> I am working on a package that wants to compile python extension modules. Configure wants users to define --with-py-site-packages-dir=<installation dir for python packages>. That does not seem to work well with the python packaging guidelines.
[10:53] <mr_pouit> is ubuntu-restricted-extras maintained in bzr (I can't find it on LP), or should I upload directly to add xubuntu-restricted-extras binaries?
[11:02] <xxxxx1> bye all
[11:06] <sistpoty> mok0: did you talk with upstream about that yet?
[11:10] <sistpoty> cya folks
[11:12] <bmm> bye
[11:14] <bmm> I was talking to sistpoty, I'm still here.
[11:14] <bmm> If somebody is thinking about advocating something, take a look at my package http://revu.tauware.de/details.py?upid=5572