[19:33]  * Unit193 points at wrst.
[19:33] <Unit193> He did it.
[19:34] <Unit193> Howdy, netritious.
[21:18] <wrst> Unit193: I did nothing!
[21:18] <wrst> and hello netritious
[21:19] <cyberanger> hey netritious
[21:19] <cyberanger> hey wrst
[21:19] <wrst> howdy howdy !
[21:19] <cyberanger> netritious: do you still use gpg?


[00:03] <jmarsden> Lintian warning of debian-changelog-file-is-a-symlink (using CDBS on Intrepid) is a Debian/Ubuntu philosophy difference I can ignore, right?
[00:06] <mok0> right
[00:06] <mok0> The symlinks are a Ubuntu specialty
[00:06] <mok0> To save space on the CD
[00:14] <Laney> Anyone got a pending sync? I want to test a fix to requestsync
[00:15] <mok0> Laney: can't you use staging?
[00:15] <Laney> If I knew how to tell requestsync to
[00:17] <mok0> Laney: I'm sure it can be done but I can't tell you how
[00:17] <Laney> right
[00:18]  * Laney trolls the rcbugs page
[00:20] <mok0> Laney: are you hacking the requestsync code?
[00:20] <Laney> mok0: Just a small fix
[00:20] <Laney> for bug #320984
[00:20] <Laney> I filed it and then felt guilty about being too lazy to fix it
[00:20] <Laney> so decided to do so
[00:21] <mok0> Laney: good for you!
[00:21] <mok0> Laney: the file common.py has a lot of refs to launchpad
[00:23] <Laney> I think it's get_launchpad
[00:25] <mok0> get_launchpad? I don't see that anywhere
[00:26] <Laney> ubuntutools/lp/libsupport.py
[00:27] <mok0> Hm, my copy must be out-of-date
[00:27] <Laney> this is latest bzr
[00:27] <mok0> I have revision 99
[00:27] <Laney> oh, interesting. requestsync seems separately broken
[00:30] <Guest56275> Hi, I packaged the new version of zekr (0.7.2), the old version in ubuntu is 0.5.1. Can anyone take a look please? http://revu.ubuntuwire.com/details.py?package=zekr
[00:31] <Laney> jpds: functions.py misses copyright info
[00:31] <Laney> (it was you, right?)
[00:31] <Laney> yes, it was
[00:35] <Laney> bah, staging seems interminably slow
[01:10] <Laney> mok0: If you have time, I proposed my branch for merging
[01:12] <mok0> Laney: ok... what do you want me to do
[01:13] <mok0> where's your branch
[01:14] <Laney> mok0: bzr merge lp:~laney/ubuntu-dev-tools/dev in your copy
[01:14] <Laney> review my changes then push it up if you'd be so kind
[01:15] <mok0> Laney: actually, my copy is my own experimental branch
[01:15] <mok0> I don't think I can push that elsewhere?
[01:15] <Laney> you can bzr get a fresh copy of trunk
[01:15] <Laney> I don't know if there's a better bzr workflow, probably is
[01:16] <mok0> Laney: yeah... I only have a very rudimentary understanding of bzr... I use git mostly
[01:17] <mok0> Laney: I'm getting a whole bunch of error message
[01:18] <Laney> mok0: when doing what?
[01:18] <mok0> bzr branch on your branch
[01:18] <mok0> but the source is here now
[01:19] <Laney> you should branch from trunk and then merge my branch
[01:19] <Laney> I think that's the proper way
[01:19] <mok0> Ah, ok, I'll try that
[01:19] <Laney> hope I didn't break bzr...
[01:20] <mok0> Well, it did something... let me pastebin the error message for your reference
[01:23] <mok0> http://paste.ubuntu.com/109200/
[01:24] <Laney> Oh yeah, I think that's just LP not supporting the newest bzr repo format yet
[01:24] <mok0> Laney: I dunno... is it your branch that needs bzr upgrade??
[01:24] <mok0> Ah
[01:24] <Laney> maybe, it's harmless anyway
[01:24] <Laney> laney@chicken:~/bin/ubuntu-dev-tools$ bzr upgrade
[01:24] <Laney> bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format.
[01:25] <mok0> Anyway, what should I look at?
[01:25] <Laney> you can "bzr diff" to see my changes
[01:25] <mok0> bzr diff?
[01:26] <Laney> then test a sync if you'd like, to see if it sets the bug as wishlist
[01:26] <Laney> obviously I couldn't test that as I'm not in the team
[01:27] <mok0> The change in functions.py, is... ?
[01:27] <mok0> ah
[01:27] <Laney> using the same name caused an error
[01:28] <mok0> urlopener?
[01:28] <Laney> yep
[01:28] <Laney> urlopener = urlopener...
[01:28] <mok0> oh yes of course
[01:28] <mok0> was that never tested?
[01:29] <mok0> Hm, so now I need to find a sync
[01:29] <Laney> check multidistrotools
[01:29] <Laney> pretty easy to find something worth syncing on there
[01:32] <mok0> multidistrotools?
[01:32] <Laney> quadrispro: syncs should be new until acked
[01:32] <Laney> mok0: http://qa.ubuntuwire.com/multidistrotools/
[01:32] <Laney> Sid version > Jaunty version is a good place to look
[01:33] <mok0> Oh that
[01:34] <quadrispro> oh Laney, I'm very sorry (and very tired) :) good bye
[01:34] <Laney> heh
[01:34] <Laney> night
[01:34] <quadrispro> bye guys!
[01:34] <mok0> Laney, hang on looking for a good one
[01:35] <Laney> mok0: I'm not off yet
[01:35] <maxb> Can syncs ever happen from places other than Debian?
[01:36] <Laney> yep
[01:38] <mok0> Laney: ./requestsync --help gives traceback
[01:38] <Laney> not here
[01:39] <mok0> NameError: name 'EDGE_SERVICE_ROOT' is not defined
[01:39] <mok0> I'm an edge user
[01:40] <Laney> I am too, but I don't see that. Where does the traceback come from?
[01:40] <mok0> libsupport.py
[01:40] <Laney> maybe it's your version of python-launchpadlib
[01:41] <Laney> python-launchpadlib: Installed: 0.2~bzr25-0ubuntu1
[01:41] <mok0> I don't have it
[01:41] <Laney> that'll do it
[01:42] <mok0> yep
[01:42] <mok0> Is it using staging?
[01:43] <Laney> if you add from launchpadlib.launchpad import STAGING_SERVICE_ROOT and then pass STAGING_SERVICE_ROOT as the second parameter to get_launchpad
[01:43] <Laney> but I don't think staging is working atm
[01:43] <mok0> I tried, and got a stacktrace
[01:44] <Laney> try and visit http://staging.launchpad.net - it's dead
[01:45] <mok0> http://pastebin.com/f35d63435
[01:46] <mok0> He, yes, it's off on weekend
[01:46] <Laney> you need the --lp param to use the new code
[01:47] <mok0> oh yes
[01:47] <mok0> That gave another problem but no exception
[01:47] <Laney> (and to ./manage-credentials -c ubuntu-dev-tools)
[01:48] <mok0> http://pastebin.com/f29502c64
[01:49] <Laney> yep, you need credentials to use lplib
[01:50] <mok0> That's new
[01:50] <mok0> I need to give my lp password?
[01:51] <Laney> no, you just need to authorise the application in launchpad
[01:51] <Laney> manage-credentials will open a browser window to do this
[01:51] <mok0> Oh, I'm remotely connected to my box via ssh
[01:52] <Laney> heh
[01:52] <mok0> I'm on my mac right now
[01:52] <Laney> I don't know what it'll do then
[01:52] <Laney> jpds wrote the tool
[01:53] <mok0> I'm more trouble for you than it's worth
[01:53] <mok0> Ah, it open elinks
[01:53] <mok0> cool
[01:56] <mok0> Laney: so now I'm on a screen where I need to authorize application
[01:56] <Laney> yeah, that's right
[01:57] <mok0> What privs does it need?
[01:57] <mok0> "Read non private data"?
[01:57] <Laney> and write, I think
[01:57] <mok0> "Change non-private data"?
[01:58] <Laney> sounds about right
[01:58] <mok0> That can't hurt
[01:59] <mok0> Ah credentials succeeded
[01:59] <mok0> So now I will try requestsync again
[02:00] <mok0> OK, it printed the changelog, and asks me if I want to edit the report
[02:00] <Laney> good, that's what it should do
[02:01] <mok0> (I wander wtf this rcconf is for )
[02:02] <mok0> done. Bug 321004
[02:02] <Laney> wishlist \o/
[02:03] <mok0> Laney: well thanks for the intro to launchpadlib
[02:04] <Laney> you're welcome. It's going to be the way for apps to interact with lp
[02:05] <skorasaurus> hi, how do i figure out what packages are required for a package ?
[02:05] <mok0> Laney: so apps need to be authenticated, but can then manipulate the LP database?
[02:05] <mok0> skorasaurus: for what purpose?
[02:06] <mok0> dpkg-checkbuilddeps may be what you are looking for
[02:06] <skorasaurus> mok0, the package (jabref) is updated upstream (by the dev), but debian hasn't updated their package to the newest stable upstream
[02:07] <skorasaurus> if it's not too big of a task for me, I'd like to update for ubuntu.
[02:07] <Laney> That's how I understand it, yes. You authenticate applications to manipulate LP on your behalf
[02:08] <skorasaurus> http://packages.qa.debian.org/j/jabref.html
[02:08] <mok0> skorasaurus: hm, normally you download the existing source package, and use uscan
[02:09] <mok0> skorasaurus: but the watch file for jabref is broken
[02:09] <skorasaurus> mok0, which src package ? the debian one ?
[02:09] <mok0> skorasaurus: no, the ubuntu one
[02:09] <mok0> skorasaurus: because jabref is a merged package
[02:10] <ryakubo> hello
[02:14] <mok0> goodnight!
[02:14] <skorasaurus> g'nite.
[02:25] <ryakubo> http://www.debian.org/doc/maint-guide/ch-start.en.html <-- this mentions being updated for potato and woody. is there anything newer I should be reading?
[02:32] <DGMurdockIII> if you go there http://www.nvidia.com/object/product_geforce_9400m_g_us.html click buy now you will see who is using them
[02:36] <ScottK> ryakubo: https://wiki.ubuntu.com/UbuntuDevelopment/FAQ has link to a number of good docs.
[02:41] <ryakubo> ScottK: yeah, I'm checking everything out. This was linked from the wiki, I just wasn't sure if it was the most recent copy... looks like it is.
[02:44] <ryakubo> mm, videos
[02:44] <ryakubo> i'm a sucker for convenience :)
[02:45] <DGMurdockIII> if you go there http://www.nvidia.com/object/product_geforce_9400m_g_us.html click buy now you will see who is using them
[02:45] <DGMurdockIII> http://developer.nvidia.com/object/nvapi.html
[02:45] <ScottK> DGMurdockIII: Spamming every Ubuntu IRC channel isn't going to win you any friends.
[02:46] <DGMurdockIII> http://developer.nvidia.com/page/home.html
[02:47] <ryakubo> i don't think nvidia even needs to spam. definitely not in a linux channel... :P
[03:12] <sooth> Is there an easy way to add keys from the keyserver?
[03:12] <sooth> (to apt)
[03:23] <ScottK> Look at the instructions on backports.org.  It tells you how.
[03:33] <sooth> Thanks
[03:36] <ScottK> YW
[03:57] <dooooomi> ScottK: weird, the pyliblo package built fine for me. i take it instead of adding debian/tmp to the paths i could also just take the manpages directly from the scripts directory?
[04:10] <ScottK> dooooomi: Are you building in a pbuilder or similar chroot?
[04:13] <dooooomi> ScottK: no, i'm afraid not
[04:13] <ScottK> You have the package installed on your system, right?
[04:14] <ScottK> dooooomi: ^^
[04:14] <dooooomi> ScottK: pbuilder?
[04:14] <ScottK> dooooomi: No. pyliblo
[04:16] <dooooomi> ScottK: yes, but after your comment i tried uninstalling it and then rebuilding the package, still worked fine
[04:16] <ScottK> OK.  You're .manpages file had /usr/share/man/man1/send_osc.1 in it.
[04:16] <ScottK> Note the leading /
[04:17] <ScottK> So that absolute path is where it was looking.
[04:17] <ScottK> I'm guessing it worked for you because it was picking up the installed man pages.
[04:20] <dooooomi> ScottK: oops, you're right. for some reason there were uncompressed manpages in /usr/share/man/man1 which didn't get deleted when i uninstalled the package
[04:21] <ScottK> So that explains it.
[04:21] <dooooomi> ScottK: ok, but scripts/send_osc.1 instead of debian/tmp/usr/share/man/man1/send_osc.1 would work?
[04:22]  * ScottK looks
[04:22] <ScottK> dooooomi: Yes.  Use that instead and delete the copies from your debian dir.
[04:23] <ScottK> I didn't realize upstream shipped man pages.
[04:24] <dooooomi> ScottK: there are no manpages in the debian dir, except for the "installed" ones in debian/tmp
[04:24] <ScottK> Oh.
[04:25] <ScottK> Ah.  Youre setup.py installs them.
[04:25] <ScottK> Sorry.  It's late and I'm doing too many things at once.
[04:27] <ScottK> dooooomi: In that case debian/tmp/usr/share/man/man1/send_osc.1 is the way to go.
[04:28] <ScottK> dooooomi: This is also a good lesson on why building in a clean chroot is important.  The fact that you weren't masked a bug in your package.
[04:34] <dooooomi> ScottK: ok, i've changed the paths and uploaded a new package
[04:35] <dooooomi> ScottK: and setting up pbuilder is very high up on my todo list :)
[04:35] <ScottK> dooooomi: If you install ubuntu-dev-tools it's as simple as pbuilder-dist jaunty create
[04:44] <AnAnt> ScottK: Hello
[04:45] <ScottK> AnAnt: Hello.
[04:45] <AnAnt> ScottK: I have a question regarding zekr package
[04:45] <AnAnt> ScottK: the one in REVU
[04:45] <ScottK> Right.
[04:46] <ScottK> It's 0.7.2.  All I found at zekr.org was 0.7.1.
[04:46] <AnAnt> ScottK: if I attach a diff.gz file to a bug report, how will you get the orig tarball ?
[04:46] <ScottK> From upstream.
[04:46] <AnAnt> ScottK: oh, I will see with upstream about that
[04:47] <AnAnt> ScottK: 0.7.2 was in SVN, and not tarball'ed it seems !
[04:47] <AnAnt> ScottK: I
[04:47] <ScottK> If you want to adjust your package for 0.7.1 we could go ahead.
[04:47] <ScottK> Then you could update it once 0.7.2 is released.
[04:48] <AnAnt> ScottK: I think they just forgot to release 0.7.2
[04:49] <ScottK> OK, well I can't upload something called 0.7.2 until they do.
[04:49] <ScottK> Anything particularly wrong with 0.7.1?
[04:49] <AnAnt> ScottK: yes, of course, I'll contact upstream about that
[04:49] <ScottK> OK
[04:50] <AnAnt> ScottK: I dunno what's new in 0.7.2 actually, I am just co-maintaining the package with Derakhshani
[04:54] <AnAnt> ScottK: so, will it be reviewed when attached to bug report ?
[04:56] <AnAnt> ScottK: 0.7.2 is released it seems
[04:56] <AnAnt> ScottK: http://zekr.org/quran/quran-for-linux
[04:56] <AnAnt> ScottK: last link
[04:59] <ScottK> Looking
[05:01] <ScottK> AnAnt: Got it.
[05:01]  * ScottK will look at it.
[05:02] <AnAnt> thanks
[05:03] <ScottK> dooooomi: Looks good.
[05:23] <ScottK> AnAnt: You need to consolidate all the ppa debian/changelog entries.  Those packages weren't in Ubuntu so they aren't relevant.
[05:23] <ScottK> Just add the useful bits into the current entry.
[05:24] <ScottK> AnAnt: You also need to set the Maintainer to MOTU again.
[05:26] <AnAnt> ok
[05:26] <AnAnt> thanks
[05:27] <AnAnt> can it be set to a team mailing list ? Ubuntu Muslim Edition Team<EMAIL_ADDRESS>[05:27] <AnAnt> ah, nevermind, the team name must change anyways
[05:29] <thepxc> hi! I have a quick question about my freshly created PPA. I've uploaded a package using dput, which does not let me upload again (since I already did). However, the package hasn't yet shown up in my PPA. When should I expect it/what can I do?
[05:30] <ScottK> thepxc: PPA's have nothing to do with Ubuntu.  Ask in #launchpad.
[05:30] <EagleScreen> it takes some hours
[05:31] <thepxc> thanks and sorry for asking in the wrong place
[05:31] <thepxc> I didn't mean to interrupt :-P
[05:36] <ScottK> No problem.
[06:24] <binarymutant> Am I allowed to change setup.py like a Makefile so that everything installs under /usr/bin instead of /usr/local/bin?
[09:56] <jpds> Laney: manage-credentials opens up w3m if it can't open Firefox.
[09:56] <jpds> And I'll add the copyright to functions.py.
[11:12] <Webspot> If there are any MOTUs available, would they be able to review my packages on REVU: http://revu.ubuntuwire.com/details.py?package=osm-gps-map http://revu.ubuntuwire.com/details.py?package=pyofa - Thanks :)
[11:16] <fabrice_sp_> Webspot, I'm not a MOTU, but I saw in your diff that you change a file outside the debian directory (build.cfg). Either patch it or if it's a temporary file. delete it in clean target
[11:17] <Webspot> fabrice_sp_: Thanks. I'll take a look at that.
[11:17] <fabrice_sp_> by the way, it's a huge version: 1.0.3+hg20090101+a08112357b80
[11:18] <Webspot> fabrice_sp_: Is that bad? I included the date of the code checkout and the revision ID.
[11:26] <fabrice_sp_> Webspot, I thnik the date is not usefull if you have the revision id
[11:28] <Webspot> fabrice_sp_: The revision ids aren't ordered though, so a new revision could have an ID that is less, when ordered, compared to the last one, meaning it's not a newer version.
[11:28] <fabrice_sp_> arghhh
[11:29] <fabrice_sp_> Webspot, then only put the date
[11:30] <Webspot> fabrice_sp_: Okay. Will do. Thanks for your help :)
[11:31] <fabrice_sp_> Webspot, you're welcome :-) I'll continue to check you're packe, to see if I see errors
[11:45] <ia> hello. i have a question about reprepro (it's a tool for creating deb repo) - does exist some way to turn off asking passphrase(but not signing packages for repo) each time, when package are putting in repo?
[11:59] <binarymutant> is it allowed in the packaging policy to change a setup.py like a makefile so that everything is installed in /usr/ instead of /usr/local/?
[12:00] <directhex> no package can install to usr/local
[12:02] <binarymutant> I know, but am I allowed to change an upstream's setup.py like a makefile so that the source builds in /usr ? setup.py defaults to /usr/local
[12:04] <binarymutant> if that makes sense...
[12:11] <Laney> binarymutant: Is it normal for setup.py to install in /usr/local or is this a particular upstream curiosity?
[12:11] <fabrice_sp_> binarymutant, by patch, yes
[12:11] <Laney> you can either patch it, or use dh_install to put the files in the right location, or maybe cdbs/dh7 will take care of it automatically if this is a common case
[12:12] <binarymutant> I'll patch it, thanks for the help
[12:12] <binarymutant> what if my package made it to the new queue but I know there's something wrong with it? Should I reupload to revu?
[12:13] <fabrice_sp_> binarymutant, yes. It's quite common to upload several times, without review
[12:13] <binarymutant> thanks for the info :)
[12:25] <fabrice_sp> Webspot, your package FTBFS
[12:25] <fabrice_sp> I think you miss some build dependencies
[12:25] <Webspot> fabrice_sp: Sorry? FTBFS?
[12:25] <Webspot> Oh
[12:25] <Webspot> Right
[12:25] <fabrice_sp> Fail To Build From Source
[12:26] <fabrice_sp> :-)
[12:26] <Webspot> I'll have a look at that. Thanks again for looking at it.
[12:26] <fabrice_sp> do you want the log?
[12:26] <fabrice_sp> I can pastbin it
[12:26] <Webspot> Yes please.
[12:27] <fabrice_sp> http://pastebin.ubuntu.com/109335/
[12:27] <fabrice_sp> good luck ;-)
[12:27] <Webspot> Thanks
[12:37] <DktrKranz> Laney, hi! Do you plan to manage haskell transition? I was looking at it, so we can share efforts
[12:40] <Laney> DktrKranz: I was going to look at it today, shouldn't be too bad
[12:41] <DktrKranz> Laney, good! quadrispro is after it too, so we can have this done very soon.
[12:41] <Laney> btw we needn't have had it at all
[12:41] <Laney> the merge wasn't necessary for us :(
[12:43] <DktrKranz> yup, but now it's in, so we have to do it anyway
[12:44] <Laney> correct
[12:56] <fabrice_sp> Hi mok0: do you have time to re-review dvdstyler? ScottK find some things that I fixed in the last upload (like splitting the package in 2). You can find it at http://revu.ubuntuwire.com/details.py?package=dvdstyler. Thanks.
[12:56] <DktrKranz> Laney, I'll add some more tasks on bug #320946, just to make sure we won't miss anything
[12:57] <DktrKranz> (unless you already filed similar bugs)
[12:57] <Laney> DktrKranz: No, I just had to do that one for darcs. Please add all that are affected and I'll pitch in in a bit
[12:58] <Laney> some will be syncs fro sid
[12:58] <DktrKranz> good. please ping me for sponsorship once ready :)
[12:58] <Laney> just playing l4d \o\
[13:00]  * directhex startles the witch
[13:02] <Laney> expert is pretty imposible
[13:03] <Laney> +s
[13:06] <mok0> fabrice_sp: yeah, sure
[13:06] <mok0> fabrice_sp: I'll look at it later today
[13:17] <bmm> If I run "sudo mount --bind -o ro /bin bin" from my home directory, then the files in bin are not read only and sudo vim bin/zless can still change the files. Mount says (ro,bind), but still ro is not applied.  I found it, I need to issue a remount after the mount :D
[13:22] <Laney> bmm: Try #ubuntu for support
[13:23] <quadrispro> hi Laney!
[13:23] <Laney> howdy
[13:23] <bmm> Laney: just found it and already tried that. But found the solution online already :D
[13:29] <bmm> Laney: seemed you need to remount ro after the bind to get it to work.
[13:48] <loic-m> james_w: ping
[14:51] <Laney> DktrKranz: Just building everything
[14:51] <Laney> debdiff flood imminent
[14:51] <DktrKranz> Laney, cool!
[14:51] <Laney> there's a couple that have to be done before some others
[14:51] <DktrKranz> I'm testbuilding packages to be synced and file them once ready
[14:52] <Laney> oh, I Was doing that too
[14:53] <Laney> be aware that hdbc needs to be done before any of the hdbc-* ones
[14:54] <directhex> sigh, i dislike the debian bts
[14:54] <Laney> more than LP?
[14:57] <DktrKranz> Laney, no problem then, I'll ACK syncs once they catch up
[14:58] <Laney> nhandler: Haha, I just found an amusing bug in pull-debian-source
[14:58] <Laney> laney@chicken:~/dev/ubuntu/packaging/haskelltransition/sync$ pull-debian-source omg-h unstable
[14:58] <Laney> USAGE: pull-debian-source [-h] <source package> [target release]
[14:58] <Laney> it parses the -h in the package name as asking for help
[15:00] <Laney> easy fix, add a ^ anchor to the regex
[15:07] <directhex> Laney, more than LP. debian has no "invalid" or "notabug" for one thing
[15:25] <didrocks> I have my package waiting in REVU and have some typos issues and some sentences to rephrase. Can somebody just correct typos as I am not en English native speaker? Thanks: http://paste.ubuntu.com/109419/
[15:28] <Laney> DktrKranz: debdiffs are up
[15:28] <Laney> bug #320946
[15:29] <DktrKranz> Laney, I'll have a look right now (and I commit pull-debian-source fix to bzr branch)
[15:29] <Laney> DktrKranz: I'm off out but I will file any remaining syncs when I get back. They all seemed to build except for hdbc which I expected to fail
[15:30] <DktrKranz> Laney, sure. Once filed, please ping/mail/subscribe me and I'll ACK them
[15:45] <anakron> hi all
[15:45] <Webspot> Hi. I'm having problems with pkg-config, while trying to package something for jaunty. On my intrepid system, "pkg-config --cflags libavcodec" gives me the cflags back, whereas jaunty just sends back a blank line. Can someone help me please?
[15:48] <anakron> Hi all
[15:48] <anakron> what do you think about it
[15:48] <anakron> https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/312123
[15:49] <anakron> it must be changed or not? im asking because i wanna know if it's right to do changes to this desktop file
[15:49] <mok0> anakron: yes
[15:49] <loic-m> didrocks: there's at least a spellchecker in gedit and kate. Running your text through it is a good habit if you want to contribute any text/doc in English
[15:49] <anakron> ok ill do some changes in the desktop file
[15:49] <anakron> but
[15:49] <anakron> mok0
[15:49] <mok0> anakron: it's a merge anyway
[15:50] <loic-m> didrocks: f.e., "essentiel" would never pass any spellcheck afaik
[15:50] <anakron> do you think that english comment and french must be changed
[15:50] <anakron> or only french
[15:50] <anakron> because french is too large
[15:50] <anakron> its obvious that is a program
[15:51] <mok0> anakron: what the bug suggests sounds perfectly reasonable
[15:51] <didrocks> loic-m: hum, I will see how to have a English spellchecker in gedit in addition to my French one :)
[15:51] <anakron> ok thanks :) ill watch it in debian too
[15:51] <mok0> anakron: great
[15:52] <pochu> Webspot: do you have the appropriate -dev package installed in jaunty?
[15:52] <didrocks> loic-m: I think this is you who reviewed my work. Was my English so awful? :)
[15:53] <loic-m> loic-m: tools>choose language... the English one is there by default
[15:53] <Webspot> pochu: Yeah. I've also looked in the libavcodec.pc file in /usr/lib/pkgconfig. The Cflags line seems to be missing "/libavcodec" on the end. Is this right, or am I totally wrong?
[15:53] <loic-m> didrocks: tools>choose language... the English one is there by default (sorry for the bad copy/paste)
[15:54] <didrocks> loic-m: thanks. I am on it (I am more worried about rephrasing some complicated sentences)
[15:54] <loic-m>  didrocks: tools>Set language actually ;)
[15:54] <didrocks> loic-m: yes, I corrected myself :)
[15:55] <anakron> mok0
[15:55] <anakron> but is this issue is real
[15:55] <loic-m> didrocks: split them so it's simpler, the rest a native English speaker might improve, but at least you get a good habit for other uploads
[15:55] <anakron> i must take out all the "program" added
[15:55] <anakron> or i must adjust to the bug
[15:55] <didrocks> loic-m: ok. I will try. I have fixed other changes. Just this one is remaining
[15:55] <anakron> in russian in can't do something
[15:55] <anakron> XD
[15:56] <loic-m> didrocks: pastebin it when you're done
[15:56] <didrocks> loic-m: ok, thanks :)
[15:56] <anakron> ping mok0
[16:00] <pochu> Webspot: it can be ok as is, look at the changelog for what the reason was
[16:00] <Webspot> pochu: Ok. I'll have a look. Thanks.
[16:02] <mok0> anakron: ah you did ping me :-)
[16:03] <Turl> surely a n00b question, but is there any way I can set up dch to use my correct mail and address?
[16:03] <Turl> I hate to edit them by hand every time
[16:07] <Webspot> pochu: Sorry. I'm quite new to all of this, shouldn't pkg-config --cflags libavcodec show "-I/usr/include/libavcodec/"?
[16:07] <jcfp> Turl: set DEBEMAIL and DEBFULLNAME
[16:08] <Turl> thanks jcfp :)
[16:09] <didrocks> loic-m: is it better http://paste.ubuntu.com/109443/ ?
[16:11] <loic-m> didrocks: I'm having a look
[16:11] <didrocks> thanks a lot :)
[16:32] <mib_pt8tdy91> hi
[16:32] <fabrice_sp> mok0, did you had time to have a look at dvdstyler?
[16:33] <fabrice_sp> hi mib_pt8tdy91
[16:35] <mok0> fabrice_sp: not yet
[16:35] <fabrice_sp> ok. Thanks anyway! :-)
[16:36] <mib_pt8tdy91> fabrice_sp: hi
[16:36] <mib_pt8tdy91> fabrice_sp: whats dvdstyler?
[16:37] <fabrice_sp> a DVD Authoring tool that I packaged, and uploaded to REVU
[16:40] <mib_pt8tdy91> fabrice_sp: is it like anyother DVD authoring tool or its special? :)
[16:41] <fabrice_sp> well, it's the only one that really worked for me in Ubuntu
[16:41] <fabrice_sp> (and I was using it in Windows before switching)
[16:42] <Turl> fabrice_sp: is it like devede?
[16:42] <mib_pt8tdy91> fabrice_sp: give a link to your app
[16:43] <fabrice_sp> you can find it in my ppa
[16:43] <fabrice_sp> (https://launchpad.net/~fabricesp/+archive)
[16:44] <fabrice_sp> Turl, yes, it seems so
[16:45] <Turl> fabrice_sp: does it allow you to set several soundtracks and subtitles for 1 movie? I need that functionality, and devede doesn't provide it
[16:47] <fabrice_sp> Turl, I have to check, but I remember making DVD with 2 audio tracks
[16:47] <loic-m> Turl: Avidemux doesn't either, I had to use mencoder :(
[16:49] <Turl> devede uses mencoder iirc, it won't be difficult to add that functionality then
[16:50] <fabrice_sp_> Turl, it can: http://dvdstyler.wiki.sourceforge.net/FAQMultipleAudio
[16:59] <mib_pt8tdy91> QUESTION: How are versions made?If I start a new project is there any standards that I should follow?( for learning purposes)
[17:00] <slytherin> Does anyone have any idea why would /dev/null have permissions 600?
[17:01] <Turl> slytherin: no idea :/ mine is crw-rw-rw- (read-writeable by all)
[17:02] <slytherin> Turl: yes, that is correct.
[17:03] <fabrice_sp_> mib_pt8tdy91, what do you mean by version? Packaging an existing program, you mean?
[17:06] <mib_pt8tdy91> fabrice_sp_: no I want to start a new project I have just packaged it and I want to give it some meaningful name that corresponds to [project name]+[stable release no]+[beta release no]+etc
[17:07] <mib_pt8tdy91> fabrice_sp_: I think thats when version comes into the scene..Am I right?
[17:18] <fabrice_sp_> mib_pt8tdy91, sorry, I don't understand what you mean. Are you asking for the package name of the app name?
[17:18] <Guest92828> Hi ScottK, ScottK-desktop, thank you for reviewing zekr. Will you be kind enough to look over my new upload again.
[17:18] <mib_pt8tdy91> fabrice_sp_: yes exactly
[17:20] <Guest92828> ScottK: Sorry I forgot to give the link: http://revu.ubuntuwire.com/details.py?package=zekr
[17:21] <Turl> mib_pt8tdy91: iirc, it's packagename_upstreamversion-debianrevision
[17:21] <Turl> so for example, if my app is called hello and version is 3.9, bash_3.9-1 for a first revision of that version
[17:22] <slytherin> Turl: he is not talking about versions in debia/ubuntu
[17:22] <Turl> slytherin: then I don't get what he means :p
[17:22] <slytherin> mib_pt8tdy91: I don't understand how can we advice you on the version number for your project.
[17:25] <mib_pt8tdy91> slytherin: I am asking what is the importance of version number and why its so complex like bash_3.9_1 instead of hello1, hello2 and so on...
[17:25] <Turl> what does this mean? W: aircrack-ng source: patch-system-but-direct-changes-in-diff patches/000-Airmon_needs_bash.diff and 1 more
[17:26] <mib_pt8tdy91> Turl: I didn't get u!!!
[17:26] <slytherin> mib_pt8tdy91: probably to separate name from version
[17:26] <slytherin> Turl: you are using some patch system in the package. but some source is directly patched.
[17:27] <Turl> yeah, I'm using quilt
[17:27] <Turl> but quilt pop -a reports no source is patched
[17:28] <mib_pt8tdy91> slytherin: There are many releases and patches and to separately identify the order they were released we use version numbers...right?Are there any standards?or simply we keep it as we like?
[17:28] <rugby471> quick question, if you were replacing an image in a deb, how do you create a debdiff?
[17:29] <Turl> mib_pt8tdy91: the version number should be the same as upstream, if that is what you want to know
[17:29] <bholtsclaw> rugby471: uuencod'ed patch ?
[17:29] <slytherin> Turl: can't help much without looking at package.
[17:29] <rugby471> bholtsclaw:what's that?
[17:29] <Turl> for example, application "myapp 5.9.8 was released". package would be myapp_5.9.8-1 for a first debian revision
[17:29] <fabrice_sp_> Turl, did you export QUILT_PATCHES ?
[17:30] <bholtsclaw> rugby471: a way to patch images in deb's
[17:30] <mib_pt8tdy91> Turl: I am kinda new to ubuntu devs can you explain whats upstream?
[17:30] <Turl> fabrice_sp_: nope
[17:30] <fabrice_sp_> Turl, should point to debian/patches
[17:30] <mib_pt8tdy91> Turl: I got it
[17:30] <mib_pt8tdy91> Turl: but whats upstream?
[17:30] <Turl> mib_pt8tdy91: upstream is the (group of) people who code the app
[17:30] <rugby471> bholtsclaw:how does it work? is documentation of it on the wiki?
[17:31] <mib_pt8tdy91> Thanx Turl slytherin fabrice_sp_
[17:31] <Turl> for example, the "dd" upstream is GNU, ubuntu's upstream is debian, ...
[17:31] <imbrandon> rugby471: i'm sure, lemme look
[17:31] <rugby471> thx
[17:31] <mib_pt8tdy91> Turl: The debian people develop and you distribute?
[17:31] <mib_pt8tdy91> Turl: *you means Ubuntu
[17:32] <Turl> mib_pt8tdy91: not really, but debian is the "source" of ubuntu
[17:32] <Turl> ubuntu is based on debian
[17:33] <mib_pt8tdy91> Turl: so Ubuntu takes some of the apps from debian edit its source code and then release it.
[17:33] <mib_pt8tdy91> great
[17:33] <Turl> sometimes, sometimes not
[17:34] <mib_pt8tdy91> ya thats why I wrote "some" of the apps
[17:34] <Turl> sorry, that one is a bad example
[17:34] <mib_pt8tdy91> which one?
[17:34] <Turl> the debian-ubuntu one
[17:34] <mib_pt8tdy91> anyways I got the essence
[17:34] <Turl> you know gcc, the C compiler? upstream is GNU
[17:34] <mib_pt8tdy91> ya
[17:35] <Turl> or brasero, the upstream is the GNOME guys
[17:35] <mib_pt8tdy91> Turl: OK
[17:40] <Turl> well, the W: aircrack-ng source: patch-system-but-direct-changes-in-diff patches/000-Airmon_needs_bash.diff and 1 more still is there, even after reextracting the original source and copying the debian dir, reimporting the patches and debuilding
[17:42] <fabrice_sp> Turl, do you have a patches directory in the root directory?
[17:43] <fabrice_sp> it seems that upstream is shipping this file
[17:45] <Turl> fabrice_sp: i have debian/patches
[17:47] <fabrice_sp> Turl, and not patches/000-Airmon... ?
[17:47] <Turl> the patches in /patches are a totally different thing, except for the one "000-Airmon_needs_bash.diff" one
[17:47] <fabrice_sp> so it seems you modified this one
[17:48] <fabrice_sp> do you have patch to modify this patch?
[17:48] <Turl> nope
[17:48] <fabrice_sp> have a look at you diff file to see what has been changed
[17:49] <Turl> it's the same patch I have in debian/patches
[17:49] <Turl> ok fabrice_sp
[17:49] <rugby471> don't owrry I found it https://wiki.ubuntu.com/PackagingGuide/Howtos/BinaryFilesInDiff
[17:51] <Turl> fabrice_sp: it seems quint modifies both series files
[17:51] <fabrice_sp> Turl, if you set QUILT_PATCHES to debian/patches, it shouldn't
[17:54] <Turl> fabrice_sp: working fine now, thanks :)
[17:55] <fabrice_sp> Turl, you're welcome ;-=
[17:59] <Turl> how much time can it take for a sponsor to look at a bug?
[18:04] <fabrice_sp> Turl, it depends. Did you subscribed u-u-s?
[18:06] <Turl> fabrice_sp: yep
[18:07] <fabrice_sp> Turl, if you put the status to Confirmed, it should be a couple of days
[18:08] <Turl> it's already confirmed
[18:09] <fabrice_sp> ok
[18:11] <quadrispro> hi guys
[18:11] <quadrispro> w-scan needs some love :) -> http://revu.ubuntuwire.com/details.py?package=w-scan
[18:13]  * Turl hugs w-scan
[18:16] <Piratenaapje> Is anyone welcome to fix the [needs-packaging]-bugs in the ubuntu launchpad buglist?
[18:17] <fabrice_sp> Piratenaapje, I think that you will be more welcome if you fix others bugs report
[18:17] <fabrice_sp> :-)
[18:17] <quadrispro> bye
[18:18] <Webspot> Hey. If there are any MOTUs around and available, could they review my packages at REVU? One is osm-gps-map, which is a GTK widget for embedding openstreetmap. And the other is pyofa, which creates audio fingerprints for files. http://revu.ubuntuwire.com/details.py?package=osm-gps-map http://revu.ubuntuwire.com/details.py?package=pyofa - Thanks :-)
[18:19] <Piratenaapje> I should just reply to the bug and say that I'm trying to package it?
[18:19] <Piratenaapje> Or do I need to offer mentorship?
[18:20] <Webspot> Piratenaapje: I understand you assign the bug to yourself, and set it to in progress.
[18:20] <slytherin> Piratenaapje: if you are going to package it, assign the bug to yourself
[18:21] <Piratenaapje> Ah alright, thanks
[18:49] <Piratenaapje> I have a question again: I want to package a program of which upstream development has stopped, but I've made some changes to it myself, to make it work a bit better.
[18:49] <Piratenaapje> It isn't ok to package it with a higher version number I guess, so what should I do with it?
[18:58] <pochu> Piratenaapje: put your changes in a patch, and patch the upstream version when building using a patch system
[18:59] <Piratenaapje> pochu: Is it ok to release under a new version number then?
[18:59] <pochu> Piratenaapje: no
[18:59] <pochu> use what upstream has
[18:59] <pochu> but patch it before building
[18:59] <pochu> e.g. if upstream is 1.0
[19:00] <pochu> you package it as 1.0-1, put a patch in debian/patches, and when building the patch is applied with your modifications
[19:00] <pochu> the version is 1.0-1, that's not a problem
[19:00] <Piratenaapje> pochu: But what if I want to actively develop it further?
[19:00] <pochu> (if it's free software)
[19:00] <pochu> Piratenaapje: then take over upstream
[19:00] <Piratenaapje> Release it under a different name?
[19:01] <Piratenaapje> Hmm ok, guess I'll try to contact the old developers
[19:01] <pochu> Piratenaapje: you can do either that, or contact upstream telling you want to continue the project
[19:09] <mabafu> hi there
[19:10] <pochu> hi mabafu
[19:10] <mabafu> hi pochu
[19:10] <mabafu> I don't know if this is the propper... channel...
[19:11] <mabafu> would like some hints on ubuntu development
[19:11] <pochu> yeah, this is a good place
[19:11] <pochu> mabafu: https://wiki.ubuntu.com/MOTU/Contributing is a good place to start
[19:13] <mabafu> tks pochu
[19:14] <fabrice_sp> One hour to start building a package in my ppa! Is there something heavy building?
[19:17] <hyperair> pochu: you're a motu right? could you revu some packages for me? =p i'm missing a final advocate for two of them
[19:22] <pochu> hyperair: which ones?
[19:22] <hyperair> sigx and bansheelyricsplugin
[19:23] <hyperair> pochu: ^
[19:26] <pochu> hyperair: for bansheelyricsplugin, you want a review from directhex, but he's not a MOTU yet
[19:27] <hyperair> pochu: hmm?
[19:27] <hyperair> pochu: actually regarding bansheelyricsplugin i've uploaded it to mentors.debian.net
[19:28] <pochu> ah, cool
[19:28] <hyperair> pochu: so perhaps i should archive it or something
[19:28] <pochu> I'm gonna review sigx
[19:28] <hyperair> pochu: thanks
[19:28] <pochu> hyperair: you can get it uploaded... jpds reviewed it and said he was happy, perhaps he would advocate it now
[19:29] <pochu> hyperair: if you want it in jaunty, I suggest you get it uploaded to Ubuntu directly too
[19:29] <directhex> with the same orig!
[19:29] <directhex> fakesync sucks
[19:29] <pochu> heh
[19:30]  * directhex is still waiting for moon to pass NEW
[19:30] <directhex> and i suspect mono 2.2 will need to be 0ubuntu1's due to NEWness
[19:32] <fabrice_sp> ScottK, I've split dvdstyler in 2 packages, but doing so, I lost your advocate. Can you please check it? (or any other motu ;-) ). It's at http://revu.ubuntuwire.com/details.py?package=dvdstyler
[19:33] <hyperair> jpds: could you advocate sigx please? you've reviewed it before
[19:34] <hyperair> pochu: get it uploaded directly meaning?
[19:36] <pochu> hyperair: weird that Debian #470532 isn't fixed
[19:37] <pochu> hyperair: yeah, I mean don't wait for the package to get into Debian and pass NEW, because then it may be too late for Jaunty
[19:37] <hyperair> pochu: in that case i should attempt to get one more advocate for bansheelyricsplugin on revu?
[19:37] <pochu> hyperair: yes
[19:38] <pochu> (not me)
[19:38] <hyperair> pochu: heheh why not?
[19:38] <pochu> if there were no advocates, maybe, but I'm not used to C# packages, so... :)
[19:40] <pochu> hyperair: have you already asked sigx upstream to release a .tar.gz tarball for you? :)
[19:40] <hyperair> pochu: eh no?
[19:41] <pochu> hyperair: then do it so that you don't need to repakcage their tarballs ;)
[19:41] <hyperair> sigh
[19:41] <hyperair> but i've already repackaged it
[19:42] <pochu> hyperair: yeah, I mean for the future
[19:42] <pochu> scons -c distclean || return 0
[19:42] <pochu> I think you want || true
[19:42] <hyperair> oh
[19:42] <hyperair> right
[19:43] <hyperair> pochu: i'll upload another with the change
[19:44] <pochu> hyperair: wait, I may find something else :)
[19:44] <hyperair> pochu: alright
[19:44] <pochu> I would use the changelog version for $UPSTREAM_VERSION, but that's just my opinion, it's fine as is
[19:45] <pochu> hyperair: and $(DEBIAN_DIR) is just ./debian, no need for so many hacks ;)
[19:46] <hyperair> pochu: according to the get-orig-source spec, it's supposed to be callable from any directory
[19:46] <hyperair> pochu: ./debian only works if you're calling from the source directory
[19:47] <pochu> hyperair: ah, ok
[19:47] <pochu> hyperair: are you using debhelper compat 7 for any reason? if it works with 5, use 5
[19:47] <pochu> (doesn't look like you use anything from 7)
[19:48] <hyperair> pochu: i think dh_make made it like that =\
[19:49] <pochu> hyperair: so change it :)
[19:49] <hyperair> alright
[19:49] <pochu> hyperair: and remove libsigx-2.0-dev.lintian-overrides, that's just a warning, it's Ubuntu specific and you can ignore it
[19:50] <hyperair> pochu: i thought lintian had to be clean
[19:51] <pochu> hyperair: mostly, but that's from an Ubuntu hack
[19:51] <pochu> hyperair: and hiding a warning isn't exactly cleaning it :)
[19:52] <pochu> i.e., if there's a reason to ignore it, just say so and we will ignore it when reviewing ;)
[19:52] <hyperair> pochu: oh. okay then
[19:52] <hyperair> heh. i had a whole bunch of lintian overrides for this issue in codelite
[19:52] <hyperair> =\
[19:52] <hyperair> and that's already accepted
[19:52] <hyperair> no wait, uploaded, but not accepted
[19:56] <pochu> hyperair: and remove the other override too, that's not even a warning! :)
[19:57] <hyperair> pochu: eh okay
[19:58] <hyperair> should i document all of this in README.source or something?
[19:59] <pochu> what? the lintian warnings? nope
[19:59] <pochu> ./usr/lib/sigx-2.0/sigxconfig.h
[19:59] <pochu> ^ that looks not very FHS compliant...
[19:59] <pochu> s/looks not/doesn't look/
[20:00] <pochu> hyperair: libsigx-2.0-doc.docs shouldn't have docs/html, that should be in libsigx-2.0-doc.install
[20:01] <hyperair> pochu: some other MOTU told me to shift it from .install into .docs
[20:01] <hyperair> pochu: i think it's in the comments somewhere
[20:01] <hyperair> pochu: also, why not?
[20:01] <pochu> that's not a doc, they are a bunch of files :)
[20:01] <hyperair> pochu: those are docs
[20:01] <hyperair> pochu: once you run scons doc
[20:02] <hyperair> pochu: also, in my defence about /usr/lib/sigx-2.0/sigxconfig.h.. there's a similar file in sigc++
[20:04] <pochu> hyperair: README looks more something to be read by the person building it than the one using it... I'd remove it from docs
[20:04] <hyperair> pochu: alright.
[20:04] <bmhm> hi all
[20:04] <pochu> same for TODO (looks for people developing sigx)
[20:04] <pochu> hi bmhm
[20:04] <bmhm> can someone help me with pbuilder pls?
[20:04] <bmhm> just a small issui (i guess)
[20:04] <hyperair> bmhm: ask and ye shall receive
[20:05] <bmhm> http://paste.ubuntuusers.de/393885/
[20:05] <bmhm> where does the+ trap - exit sighup come from?
[20:05] <hyperair> pochu: i think the TODO might be good for telling the developers who use sigx what hasn't been implemented and so on
[20:06] <pochu> hyperair: ok
[20:06] <pochu> hyperair: the -dev package should be arch: all
[20:06] <hyperair> ah
[20:07] <pochu> hyperair: I think other than that, it's good
[20:07] <pochu> well, I haven't looked into copyright
[20:07] <hyperair> pochu: okay i'll make another upload
[20:07] <pochu> hope you got that fine :)
[20:08] <hyperair> pochu: well i followed licensecheck's output and made sure i covered everything =\
[20:08] <bmhm> anyone got an idea?
[20:09] <pochu> hyperair: looks fine, yes
[20:09] <hyperair> pochu: are you sure the -dev should be arch: all? i get some non-binmuable lintian error
[20:10] <pochu> hyperair: I also do `grep -Ri copyright *`
[20:10] <pochu> hmm
[20:10] <hyperair> pochu: and it seems i need to work around it by using Depends: libsigx-2.0-2 (>= ${source:Version}) and (<< ${source:Version}.1~) or something
[20:11] <bmhm> :-/
[20:11] <hyperair> bmhm: dyou have any strange pbuilder hooks?
[20:11] <bmhm> well I'll post my pbuildrc, second
[20:12] <bmhm> MIRRORSITE=http://archive.ubuntu.com/ubuntu
[20:12] <bmhm> DISTRIBUTION=intrepid
[20:12] <bmhm> OTHERMIRROR="deb http://archive.ubuntu.com/ubuntu intrepid universe multiverse"
[20:12] <pochu> hyperair: ok, leave it as arch:any, its size is small so it's fine
[20:13] <pochu> hyperair: ok, I think that's all from me :)
[20:13] <hyperair> pochu: okay
[20:13] <bmhm> oh and I just found a hook
[20:14] <bmhm> http://paste.ubuntuusers.de/393886/
[20:15] <hyperair> pochu: okay, i've made a new upload. could you look through it, and if nothing's wrong, advocate it please? =p
[20:17] <jmehdi> Could someone review my package: http://revu.ubuntuwire.com/details.py?package=webstrict, I've fixed the latest problems (I hope)
[20:18] <bmhm> well... any ideas now?
[20:19] <pochu> Logged in as pochu (Contributor).
[20:19] <pochu> WTF
[20:19] <pochu> RainCT: ^ I want my Advocate checkbox back pliz :)
[20:20] <RainCT> pochu: uhm?
[20:20] <pochu> RainCT: REVU thinks I'm not a MOTU :/
[20:20] <RainCT> REVU doesn't like you :P
[20:20] <RainCT> did you do something bad to it?
[20:21] <pochu> not really... I almost never visit it :)
[20:21] <RainCT> pochu: so, you did something bad *G*
[20:22] <RainCT> ok, you're reviewer
[20:22] <pochu> doesn't REVU know that from LP anymore?
[20:23] <pochu> hyperair: advocated
[20:23] <hyperair> pochu: thanks
[20:23] <RainCT> pochu: nope, that's on some long TODO list :P
[20:24] <pochu> RainCT: ah, ok
[20:24] <hyperair> mok0: sorry to ask this of you again, but could you look at sigx again? i've made a new upload.
[20:24] <nellery> if a new copyright year is added to a new upstream release, should that be added to debian/copyright?
[20:24] <dtchen> yes
[20:25] <pochu> RainCT: ~motu is a member of ~revu-contributors so that MOTUs can upload to REVU, right?
[20:25] <RainCT> pochu: revu-contributors is deprecated, obsoleted and whatever you want :P
[20:25] <pochu> err, ~revu-uploaders
[20:25] <RainCT> err, revu-uploaders ;P
[20:25] <pochu> ah, good
[20:25] <jpds> Que raro.
[20:25] <pochu> so I want ~motu not be a ~revu-uploaders member anymore please :-)
[20:25] <RainCT> pochu: logging in once is enough to be able to upload
[20:25] <nhandler> pochu: We stopped using that team when we switched to openID for the logins
[20:26] <jpds> hyperair: sigx looks good to me. Better without the *.symbols file.
[20:26] <pochu> RainCT: so, can you remove MOTU from https://edge.launchpad.net/~revu-uploaders/+members? thanks :)
[20:27] <hyperair> jpds: thenn could you advocate it? =p
[20:27] <RainCT> pochu: won't that send a mail to everyone?
[20:28] <pochu> RainCT: don't think so, there's a ML for the motu team
[20:28] <pochu> and it will get moderated I guess
[20:28] <RainCT> pochu: ML is only for bugmail
[20:28]  * RainCT learned that the hard way :P
[20:29] <jpds> RainCT: Well this time if something bad happens, you can blame pochu.
[20:29] <pochu> ah, right
[20:29] <pochu> hehe, yeah
[20:29] <pochu> and I will blame Launchpad :P
[20:30] <Piratenaapje> Hmm I've run into a problem: the program I'm currently packaging installs ode by downloading it, this is not the same version as is included in Ubuntu, which it won't compile with. Is it a problem if the configure downloads and installs a package?
[20:30] <jpds> Piratenaapje: Yes, there is no networking on the build daemons.
[20:30] <Piratenaapje> Ah crap
[20:32] <Piratenaapje> jpds: would it be ok to have configure just build it, without downloading it?
[20:32] <jpds> Piratenaapje: Could you upgrade the other package needed in Ubuntu first?
[20:34] <jpds> Piratenaapje: Or you could patch the one you're working on right now so that it didn't download the other.
[20:34] <bmhm> well
[20:34] <bmhm> where can I ask about my problem then?
[20:34] <Piratenaapje> jdps: It's a custom version of the library, so that's not a possibility
[20:35] <jpds> Piratenaapje: Hmm, tricky.
[20:37] <Piratenaapje> jpds: Patching the configure, and including the ode.tar.gz is allowed?
[20:39] <Laney> convincing upstream to not need it is the best way
[20:39] <Piratenaapje> "ODE is released     by distros in a lot of various versions (0.3x, 0.5, 0.6, CVS), wich makes     things very complex for us" is the reason they give for using their own version
[20:40] <Piratenaapje> so not going to happen I'm afraid
[20:40] <Laney> ?
[20:41] <Laney> They can require a particular version (say 0.5), and then for a distro to use their software they must update the lib to 0.5
[20:41] <jpds> Laney: They use a custom version appartently.
[20:41] <Laney> broken distros aren't really their problem
[20:41] <Laney> Then they should try to upstream their patches
[20:42] <Piratenaapje> Well anyway, there hasn't been a new version released in 2.5 years, so I doubt anything is going to change :p.
[20:42] <Laney> then you should consider whether we want to maintain unsupported software
[20:43] <Piratenaapje> I was trying to package it because a [needs-packaging] bug was filed in launchpad
[20:43] <Piratenaapje> Not by the actual developers I suppose
[20:43] <Laney> we don't have to fulfill every needs-packaging bug
[20:44] <bmhm> well can someone tell me why pbuilder gets an sigHUP?
[20:44] <bmhm> http://paste.ubuntuusers.de/393885/
[20:45] <Piratenaapje> Laney: so I suggest I stop trying to package it?
[20:45] <Piratenaapje> *you
[20:45] <Laney> Piratenaapje: It certainly sounds like something we don't want to maintain
[20:46] <Laney> but if you want to fork it and become upstream...
[20:46] <Piratenaapje> Guess it won't be packaged then :p
[20:48] <ScottK> fabrice_sp: Why put all the usr/share/ stuff in the main package and not in the -data package?
[20:48] <hyperair> jpds: thanks for the advocate
[20:48] <Piratenaapje> Laney: thanks for saving me work :)
[20:49] <jcfp> Laney: could you take a look at sabnzbdplus? You reviewed it recently, all issues you raised have been fixed (including upgrading the mochikit package)
[20:50] <Laney> jcfp: I'm not a MOTU sadly
[20:50] <bmhm> oh wait... http://paste.ubuntuusers.de/393888/ line 1063++
[20:50] <bmhm> can you just take a look at it please?
[20:50] <jcfp> Laney: bummer, you should be ;)
[20:50] <Laney> soon
[20:52] <Laney> jcfp: I never looked into it before, but the /etc/default behaviour seems odd. Did you get that from somewhere?
[20:53] <Piratenaapje> What would be the best way to take over a old package? Take over upstream, or just fork it?
[20:53] <jcfp> Laney: no created that myself, what's odd in it?
[20:53] <Laney> jcfp: I'd expect it to just work I guess
[20:54] <Laney> is there any reason why you can't create a sabnzbd user?
[20:54] <pochu> RainCT: so, are you gonna remove it? :)
[20:55] <jcfp> Laney: that creates other problems, such as permissions on download (they'd be owned by that user, etc)
[20:55] <Laney> jcfp: The most similar package I can think of is torrenflux. Maybe you could look into how that package does it?
[20:55] <jcfp> and also not everybody will want to run it at boot
[20:55] <jcfp> i'll check
[20:55] <Laney> jcfp: Right, then /etc/defaults/sabnzbd becomes a boolean flag
[20:55] <Laney> startonboot = true
[20:56] <jcfp> it already is, just that in this case the user being filled in or not functions as the kill switch
[20:58] <jcfp> Laney: is there any "best practice" when it comes to creating users accounts like this?
[20:58] <Laney> I really don't know - that's why I referred you to torrentflux :(
[20:59] <jcfp> k, np
[20:59] <Laney> actually, maybe that wasn't a good example
[20:59] <Laney> I think torrentflux might be a PHP script
[20:59] <Laney> think of your favourite daemon and see how it does this
[21:10] <Laney> how strange, I don't get bugmail for new syncs any more
[21:28] <oojah> Piratenaapje: If you can contact upstream and they're happy to hand on development, then I'd say doing that would be better than forking. Just my opinion.
[21:29] <Piratenaapje> oojah: I've sent them a mail, but I'm not really expecting a response, their sourceforge page has been dead for over 2 years, and all I had was their sourceforge addresses :S
[21:30] <Piratenaapje> I'll wait a week or 2 to give them a chance to respond though
[21:34] <oojah> Piratenaapje: Sounds reasonable.
[22:31] <dtchen> woops
[22:31] <dtchen> forgot to sub u-u-s, done now if someone wants to sponsor the fix for bug 313820
[22:32] <dtchen> (see the #ubuntu-devel irclogs from 2009-01-04 for verification from the reporter)
[22:46] <Webspot> Hey. If there are any MOTUs around and available, could they review my packages at REVU? One is osm-gps-map, which is a GTK widget for embedding openstreetmap. And the other is pyofa, which creates audio fingerprints for files. http://revu.ubuntuwire.com/details.py?package=osm-gps-map http://revu.ubuntuwire.com/details.py?package=pyofa - Thanks :-)


[12:11] <dilys> Merge to devel/launchpad/: improve logging update-branches.py [r=BjornT]  (r3161: David Allouche)
[12:36] <jordi> hello
[12:36] <jordi> SteveA: ping?
[12:37] <jordi> mpt: you don't have lp superpowers, do you?
[12:37] <jordi> ie, adding people to translation groups, or editing a team's name
[12:37] <jordi> https://launchpad.net/people/ubuntu-l10n-ak
[12:38] <jordi> this should be Ubuntu Akan translators
[12:38] <mpt> jordi, not any more
[12:38] <jordi> hrm
[12:38] <jordi> and SteveA should be away.
[12:38] <mpt> I've been deadminified
[12:40] <LarstiQ> heh
[12:41] <mpt> lifeless and stub should be awake, but not necessarily available since it's Saturday
[12:41] <mpt> https://launchpad.net/people/admins
[12:41] <lifeless> what needs done ?
[12:43] <mpt> lifeless, jordi's request above
[12:44] <lifeless> jordi: I'm happy to edit the name for you
[12:46] <lifeless> jordi: what is i you want changed? the description ?
[12:49] <jordi> lifeless: oh, hello
[12:49] <jordi> I actually have several requests, as usual
[12:49] <lifeless> it seems to have a valid description already ?
[12:49] <jordi> lifeless: team name should be "Ubuntu Akan Translators"
[12:49] <lifeless> jordi: the display name I presume ?
[12:49] <jordi> er, yes.
[12:50] <lifeless> why is it set to this kasharow stuff ?
[12:50] <jordi> I.. have no idea
[12:50] <jordi> they created it like this
[12:51] <jordi> after this, I'll need you add that team to https://launchpad.net/rosetta/groups/ubuntu-translators/+appoint
[12:51] <lifeless> will you contact them to tell them its been changed ?
[12:51] <lifeless> so they don't get all confused ?
[12:51] <lifeless> what about the description ?
[12:52] <jordi> it has no description, does it?
[12:52] <jordi> it's not err
[12:52] <jordi> yeah, I really don't care much about the desc, as it's going to change again I'm afraid
[12:53] <jordi> I'll mail them about their name, that we want it to be as the other teams
[12:53] <lifeless> should I leave it, or change it or delete it ?
[12:53] <jordi> the display name gets displayed in the groups list, so it was more worrysome
[12:53] <jordi> lifeless: change what?
[12:53] <jordi> I see no description here.
[12:53] <lifeless> the description
[12:54] <lifeless> team description:
[12:54] <lifeless> 'The kasahorow Localization Project (www.kasahorow.org).'
[12:54] <jordi> I wonder where that gets displayed because I don't see it
[12:55] <lifeless> dunno
[12:55] <lifeless> but its there
[12:55] <jordi> lifeless: I say leave it
[12:55] <lifeless> ok
[12:55] <lifeless> done
[12:55] <jordi> great
[12:56] <jordi> now, the groups thing
[12:56] <lifeless> ooooh
[12:56] <lifeless> ak is not akan
[12:56] <lifeless> aka is akan
[12:56] <lifeless> ak is akkadian
[12:56] <jordi> wrong
[12:56] <jordi> both ara Akan
[12:56] <lifeless> meep
[12:57] <jordi> hmm
[12:57] <lifeless> which one should I set in the https://launchpad.net/rosetta/groups/ubuntu-translators/+appoint page then ?
[12:57] <jordi> This would be a major pain
[12:57] <jordi> doh
[12:57] <jordi> let me see
[12:57] <jordi> akkadian, wow
[12:57] <lifeless> meheheheheh
[12:57] <LarstiQ> isn't that used in israel?
[12:57] <jordi> I see nothing like that in thel ist
[12:57] <jordi> hey LarstiQ
[12:58] <lifeless> is akan related to ghana ?
[12:58] <lifeless> I can change the team to be ubuntu-l10n-aka
[12:58] <LarstiQ> ah no, that was Aramaic
[12:59] <jordi> lifeless: Akan is related to Ghana, yes.
[12:59] <jordi> http://www.loc.gov/standards/iso639-2/englangn.html
[12:59] <lifeless> ok
[12:59] <jordi> lifeless: ^^ that is like *the* list.
[01:00] <jordi> what lp id is assigned to "ak"?
[01:00] <jordi> this is bizarre
[01:00] <lifeless> so the kasahorow folk are correct for akan. the question is the -ak or -aka
[01:00] <lifeless> lp has -aka for akan
[01:00] <jordi> akkadian is "akk
[01:00] <jordi> Akan is "ak" and "aka". So we use "ak".
[01:00] <lifeless> ok
[01:00] <jordi> Akkadian should be "akk" instead.
[01:00] <lifeless> can you file a bug on the akkadian one ?
[01:01] <jordi> can't you change it from there?
[01:01] <jordi> I can, in any case :)
[01:01] <lifeless> no
[01:01] <jordi> oh damn
[01:01] <jordi> against rosetta?
[01:01] <lifeless> I'm pretty sure some of this language stuff is hard coded down in reference tables
[01:01] <jordi> doh
[01:01] <lifeless> and even if it wasn't, I'd want carlos or daf to weigh in first
[01:01] <jordi> what should I say?
[01:02] <jordi> daf: dude :)
[01:02] <lifeless> 'language code ak is incorrectly listed as akkadian rather than akan, and akkadian should be listed with language code akk'
[01:04] <jordi> Ubugtu: 31835
[01:04] <jordi> bleh
[01:04] <lifeless> bug 31825
[01:04] <Ubugtu> malone bug 31825 in evince "No anti-aliasing with partly embedded fonts" [Normal,Unconfirmed]  http://launchpad.net/bugs/31825
[01:04] <lifeless> bug 31835
[01:04] <Ubugtu> malone bug 31835 in rosetta "Akkadian assigned to "ak" code in ubuntu-translators group" [Normal,Unconfirmed]  http://launchpad.net/bugs/31835
[01:05] <jordi> can't type at this time in the night
[01:05] <lifeless> anything else I can do for you ?
[01:07] <jordi> lifeless: I think that's it.
[01:07] <lifeless> k.
[01:07] <lifeless> I'll be around for another hour or so if you think of anything else
[01:08] <CarlFK> what is a good email filter rule for launchpad messages?
[01:08] <CarlFK> sender=bounces@canonical seems dumb
[01:10] <jordi> lifeless: thanks
[01:11] <jordi> lifeless: so akadian is currently assigned to "aka", right?
[01:11] <lifeless> no
[01:11] <jordi> oh, "ak"?
[01:11] <lifeless> aka is akan
[01:11] <jordi> err
[01:11] <jordi> sorry, that's what I meant
[01:11] <jordi> akan -> "aka", akkadian -> "ak", for now?
[01:11] <jordi> ok, so the Akan guys can't start translating still.
[01:12] <lifeless> right
[01:12] <jordi> or when they get their real code, it's going to be a mess.
[01:12] <jordi> I'll  try to get carlos confirm this to you asap, because this is a blocker for a team
[01:17] <lifeless> carlos will know how to fix it too
[01:18] <jordi> nod
[01:18] <jordi> I mailed him
[04:57] <omega21> hi, is there something wrong with shipit?
[04:57] <omega21> I cant make a new account
[04:58] <omega21> anyone?
[05:23] <omega21> hi there
[05:23] <omega21> im having trouble registering on launchpad... can anyone help?
[06:49] <stub> omega21: Whats up?
[11:11] <jblack> stevea: ping
[11:24] <SteveA> hello jblack
[12:00] <cprov> morning
[12:27] <matsubara> good morning!
[01:09] <acathla> hi
[01:12] <acathla> i would like to report an ubuntu bug on launchpad but the bug reporter has a bug, i obtained a: " Please report this as a bug"
[01:17] <acathla> this is recursiveness...
[01:21] <matsubara> acathla: did you get a oops number?
[01:24] <acathla> ha, yes
[01:27] <matsubara> do you have it there? I could check if you're running into a known bug.
[01:27] <acathla> OOPS-49D293
[01:27] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/49D293
[01:29] <matsubara> acathla: the oops log isn't available yet. give me 10 min and will re-check for you.
[01:29] <acathla> i had to re-submit, i forgot to save the number
[01:29] <matsubara> no problem
[01:29] <acathla> ok, thanks
[01:33] <matsubara> acathla: you're running into bug 31367.
[01:33] <Ubugtu> malone bug 31367 in malone "Specifying a non-published binary package when filing a bug causes an oops" [Normal,Confirmed]  http://launchpad.net/bugs/31367
[01:34] <matsubara> acathla: I'll work on it as soon as possible. I'm sorry for the inconvenience.
[01:37] <matsubara> acathla: as an workaround to it, you could report your bug without specifying the package.
[01:38] <matsubara> acathla: just leave a note on the bug description to which package you were trying to assign it to. will help the bug triager later.
[01:40] <acathla> ok
[01:41] <acathla> it works, thanks :)
[01:41] <acathla> Bug #31873
[01:41] <Ubugtu> malone bug 31873 in Ubuntu "network "Device not found" with any NIC tested and any Dapper kernel." [Normal,Unconfirmed]  http://launchpad.net/bugs/31873
[01:43] <matsubara> cool
[02:26] <mdke> has any progress been made on people searches? It's unusual that I don't get an oops when searching
[02:26] <daf> work has been done on it
[02:26] <mdke> cool
[02:26] <daf> expect improvements in the Tuesday Launchpad update
[02:27] <mdke> daf, thanks, I will :)
[03:25] <kiko-zzz> was anyone looking for me?
[03:48] <matsubara> kiko-zzz: did you start the fix for bug 31367?
[03:48] <Ubugtu> malone bug 31367 in malone "Specifying a non-published binary package when filing a bug causes an oops" [Normal,Confirmed]  http://launchpad.net/bugs/31367
[03:48] <kiko-zzz> nope
[03:48] <kiko-zzz> I got stuck trying to remove IBugTarget.bugtasks