[05:13] <drizzt_> why package maintainers never update translations? even there was no release in last years, somebody could contribute new or updated translations, but they are never checked for nor updated in package
[05:16] <micahg> drizzt_: probably depends how the translations are packaged
[05:16] <micahg> drizzt_: what package?
[05:16] <drizzt_> *most* universe packages have missing or outdated translations comparing to project's trunk or whichever upstream it use
[05:18] <micahg> drizzt_: are upstream packaging the translations in the tarballs?
[05:22] <drizzt_> usually they do not backport translations to the release version packaged in Ubuntu, but they usually include it in trunk or recent development version
[05:23] <micahg> drizzt_: well, we take the versions in the release we package generally
[05:24] <micahg> drizzt_: and universe is community maintained, so if there's a package that you'd like to have a new version, you can work on it
[06:43] <anoteng> I've got two packages I'd like to have reviewed by a motu. http://revu.ubuntuwire.com/p/python-easygui bug #596406, and http://revu.ubuntuwire.com/p/transgui bug #332067
[07:33] <ScottK> anoteng: For python-easygui, you might consider packaging it for Debian and having it sync'ed into Ubuntu.  The Debian Python Modules Team is very open to Ubuntu people and sponsoring new Python packages.  See #debian-python on OFTC network.
[07:33] <ScottK> Honestly your odds are better there.
[07:35] <anoteng> ScottK, I'm already looking into it, thanks. I'd still like a review though, as I'm kind of new to this, and probably did something wrong...
[07:36] <ScottK> They don't expect you to be an expert when you show up there, so no need to wait.
[07:36] <ScottK> You'll get more and better reviews there.
[07:36] <ScottK> We get hugely more package requests than we can review each cycle.
[07:40] <anoteng> ok, thanks.
[09:20] <dupondje> How can I upgrade a package to the newest upstream version? The package is not in debian (so no merge/sync)
[09:34] <micahg> dupondje: is there a watch file?
[09:36] <jmarsden> dupondje: See https://wiki.ubuntu.com/PackagingGuide/Complete#Updating%20an%20Ubuntu%20Package for the basic idea.
[09:37] <dupondje> http://ubuntu.dupondje.be/pybootchartgui.debdiff
[09:37] <dupondje> it looks ok ?
[09:40] <micahg> dupondje: you might want to ask the maintainer
[09:46] <BlackZ> zul: could you please take a look at bug #595520 ?
[09:46] <dupondje> micahg: https://bugs.launchpad.net/ubuntu/+source/pybootchartgui/+bug/596475
[09:46] <dupondje> and subscribed the maintainer :)
[09:47] <micahg> dupondje: k
[09:47] <dupondje> can you set it to Wishlist btw ?
[09:47] <micahg> dupondje: sure
[09:48] <BlackZ> dupondje: why is it '0+r141' rather than '0+r141ubuntu1' ?
[09:48] <micahg> BlackZ: native Ubuntu package
[09:49] <BlackZ> ah, true
[09:49] <BlackZ> micahg: good luck for the DMB :P
[09:49] <micahg> BlackZ: thanks :)
[09:52] <micahg> BlackZ: you too
[09:53] <BlackZ> micahg: heh, thanks!
[10:22] <riccetn> Is there any MOTU that can review my package of clementine (Music player): http://revu.ubuntuwire.com/p/clementine
[10:57]  * drizzt_ thinks that we have enough gstreamer-based music players already
[13:37] <ari-tczew> please unsubscribe ubuntu-sponsors from bug 582576
[13:40] <ari-tczew> can someone tell me whether it's necessary change: Update Maintainer field as per spec  ? bug 230350 for example
[13:47] <sebner> ari-tczew: unsubscribed
[13:50] <sebner> ari-tczew: https://wiki.ubuntu.com/DebianMaintainerField
[14:27] <ari-tczew> sebner: thanks for unsubscribe. and what about this maintainer field?
[14:28] <sebner> ari-tczew: I thought that would answer your question if it's necessary to change the maintainer field
[14:28] <ari-tczew> sebner: I asked whether it's necessary
[14:29] <sebner> ari-tczew: well, as the wiki page suggests, every time you modify a debian package that was unchanged before, you have to update the maintainer field
[14:29] <ari-tczew> if there is no delta, package is synced from Debian, so don't change maintainer field
[14:29] <ari-tczew> sebner: still don't understand.
[14:30] <sebner> ari-tczew: right, I don't understand what you don't understand ^^
[14:32] <tumbleweed> ari-tczew: if you modify the package, you update-maintainer. If you sync, the maintainer update is done automatically, on build.
[14:32] <tumbleweed> (and I can't see https://launchpad.net/bugs/230350 due to lp timeouts)
[14:32] <ari-tczew> sebner, tumbleweed: sorry bugs, I have you wrong bug number. let
[14:32] <ari-tczew> let check bug 300858
[14:33] <BlackZ> ari-tczew: what's the problem there?
[14:34] <tumbleweed> BlackZ: no need to mention maintainer update in changelog
[14:34] <ari-tczew> yea
[14:35] <tumbleweed> (also, that bug's description could use an update)
[14:35] <BlackZ> tumbleweed: I think that's not a big deal
[14:35] <tumbleweed> BlackZ: not at all
[14:35] <ari-tczew> BlackZ: and bug number in debian/changelog is wrong
[14:36] <BlackZ> ari-tczew: as you can see, it's a merged change
[14:37] <tumbleweed> BlackZ: however, you didn't close LP: #300858
[14:37] <BlackZ> forgot about that, sorry
[14:38] <ari-tczew> :]
[14:38] <ari-tczew> please check package https://launchpad.net/ubuntu/+source/mtx/1.3.12-3ubuntu1
[14:39] <tumbleweed> yeah, mom should add some boilerplate for closing the merge bug (although I guess people would forget to fill it out)
[14:39] <ari-tczew> Remaining changes: update maintainer according to spec.
[14:39] <BlackZ> ari-tczew: it's not a big deal, as I said
[14:39] <ari-tczew> I think that it's wrong
[14:40] <ari-tczew> BlackZ: what do you mean "not a big deal" ?
[14:40] <BlackZ> ari-tczew: it's not so wrong
[14:40] <ari-tczew> I don't understand a remaining change as update maintainer field
[14:40] <BlackZ> if I found it in the changelog I'd merge it
[14:40] <tumbleweed> ari-tczew: I agree, that could have been a sync.
[14:41] <tumbleweed> there are some other minor changes, though
[14:41] <BlackZ> but as tumbleweed as said, it could be a merge if there aren't other changes
[14:41] <ari-tczew> zul: ping for above case ^^
[14:41] <BlackZ> s/as/has
[14:41] <tumbleweed> ari-tczew: it can't be synced now. ubuntu has never version than debian
[14:42] <ari-tczew> tumbleweed: I know. I want to talk zul for now merging this package due to update maintainer field
[14:42] <ari-tczew> in future
[14:42] <ari-tczew> s/now/not
[14:43] <ari-tczew> BlackZ: "it could be a merge if there aren't other changes" what you mean?
[14:43] <ari-tczew> maybe sync instead merge?
[14:43] <BlackZ> s/merge/sync
[14:43] <ari-tczew> :]
[14:44] <BlackZ> however in my case the sponsor could modify the changelog for remove that if it's considered "wrong" :)
[14:45] <dupondje> tons of merge/sync requests it seems in the MoM :)
[14:46] <ari-tczew> BlackZ: +1. he should upload next XubuntuY with information, that package doesn't need to be merged. no delta
[14:47] <tumbleweed> ari-tczew: the description was changed - there is a delta
[14:48] <ari-tczew> tumbleweed: question of importance of description
[14:48] <ari-tczew> and why he doesn't include information about it in debian/changelog
[14:49] <tumbleweed> :)
[14:55] <ari-tczew> omg, what a mess https://launchpad.net/ubuntu/+source/ilohamail/0.8.14-0rc3ubuntu4
[15:05] <BlackZ> tumbleweed: fixed, thank you
[15:10] <tumbleweed> BlackZ: um, is it just me or has debian fixed your hp-ppd issue? (They run that script with bash)
[15:11] <BlackZ> no tumbleweed, seems it's not fixed at all
[15:11] <tumbleweed> BlackZ: ok how about "it builds fine for me on maverick"
[15:11] <BlackZ> tumbleweed: doesn't it?
[15:11] <tumbleweed> no I'm saying it does
[15:12] <BlackZ> tumbleweed: ah, ok
[15:12] <tumbleweed> ubuntu's solution was to remove bashisms, debian's was to run "bash install.sh"
[15:12] <tumbleweed> looks syncable to me
[15:15] <BlackZ> tumbleweed: in case I will follow up the bug
[15:21] <ari-tczew> NCommander: why did you upload package in version ubuntu4? https://launchpad.net/ubuntu/+source/ilohamail/0.8.14-0rc3ubuntu4
[15:22] <ari-tczew> ah, previous package uploaded in ubuntu3, then you removed old ubuntuX
[15:46] <ari-tczew> sebner: could you take sponsorship for me @ bug 596577 ?
[16:32] <ScottK> statik: You've got a couple of python packages sitting on REVU for almost a year.  Are you still interested in them?
[16:37] <ari-tczew> james_w: why package pyexiv2 doesn't have created branch? https://code.launchpad.net/ubuntu/+source/pyexiv2
[17:21] <slytherin> Now that we support 3.0 formats, we should ideally switch to .orig.tar.bz2 if upstream releases bz2, right? After all every byte of saved storage space counts.
[17:22] <micahg> slytherin: usually, depends if backports lower than lucid are needed
[17:23] <micahg> *archive backports/updates
[17:24] <slytherin> The package in question is gstreamer plugins package. I don't think they are backported frequently.
[17:26] <micahg> slytherin: sounds right
[17:30] <shadeslayer_> any MOTU around to review my REVU upload?
[19:30] <shadeslayer_> hi any MOTU to advocate my package here : http://revu.ubuntuwire.com/details.py?upid=8319
[20:12] <NorthernLights> Hello all
[20:17] <NorthernLights> Hello all
[20:17]  * NorthernLights is poking for a check of REVU packages synergy-plus and killrogues
[20:18] <tumbleweed> NorthernLights: hi. I (stefanor) was just commenting on your synergy-plus package. Looks good to me. But I'd liek to see it in Debian too :)
[20:18]  * tumbleweed uses synergy between debian and Ubuntu
[20:18] <NorthernLights> Hi there
[20:19] <NorthernLights> Sure, as I was answering on launchpad, i want to do this too. I was waiting to get into Ubuntu first, to avoid having to ask twice as much to review my package.
[20:19] <NorthernLights> And I'd like to give the Ubuntu process a chance
[20:35] <shadeslayer_> NorthernLights: could you please check my package too? http://revu.ubuntuwire.com/details.py?upid=8319
[20:35] <NorthernLights> ok
[20:36] <shadeslayer_> thanks :)
[20:44] <shadeslayer_> NorthernLights: ok ill clean that up :)
[20:45] <shadeslayer_> i did put the section as net,then checked p.u.c and saw it was network.. so changed it
[20:47] <shadeslayer_> NorthernLights: also if upstream doesnt ship with a copy right year,do i put in this year?
[20:47] <ScottK> shadeslayer_: Just copy/paste was upstream shipped.
[20:49] <tumbleweed> shadeslayer_: stefanor is me, not NorthernLights :)
[20:49] <shadeslayer_> ohhh
[20:49] <shadeslayer_> tumbleweed: :P
[20:49] <NorthernLights> aaaah ok! Thanks, i was wondering if i pushed the submit button by mistake
[20:50] <shadeslayer_> hehe :)
[20:52] <shadeslayer_> tumbleweed: does : You should have received a copy of the GNU General Public License
[20:52] <shadeslayer_>     along with QIpMsg. If not, see "/usr/share/common-licenses/GPL-3". sound ok?
[20:58] <tumbleweed> fine fine
[20:59] <shadeslayer_> ok fixed most stuff ... will make the rules changes later ....
[21:00] <shadeslayer_> ciao :)
[21:06] <NorthernLights> shadeslayer_, i'm adding a comment too
[21:06] <NorthernLights> (basically, "run lintian :)")
[21:10] <NorthernLights> (i'm building the binary package to make sure it works)
[23:12] <ari-tczew> lool: check your e-mail's inbox. libsmbios's maintainer has Cced message to you about libsmbios package handling
[23:21] <sebner> ari-tczew: well, either you wait until wednesday (quite some stuff to do for university) or you ask someone else aka just wait for someone to sponsor it, and it's a bzw branch too .. brrrr :P
[23:22] <ari-tczew> sebner: sorry, I forgot about your issue
[23:23] <ari-tczew> sebner: I want to see grow of bug numbers sponsored. besides you I'm going block some bugs on 2 other sponsors
[23:23] <ari-tczew> sebner: maybe you should take some lessons about bzr sponsoring?
[23:24] <sebner> ari-tczew: bah let me push that back for maverick +1 :P
[23:24] <ari-tczew> sebner: why +1?
[23:24] <ari-tczew> instead maverick 0 :d
[23:25] <sebner> ari-tczew: well, DIF is around and I think bzr sponsoring will become more stable and more common for maverick+1
[23:25] <micahg> ari-tczew: people have limited time, I had a great idea I ran a session for at UDS that I have to push off till maverick +1
[23:26]  * sebner ^5 micahg 
[23:27] <ari-tczew> micahg: so you won't work anymore in maverick+1? correct translated?
[23:27] <sebner> ari-tczew: deal: I sponsor your non-bzr stuff and I might get into this bzr stuff in my summer holidays
[23:27] <micahg> ari-tczew: no, I just have my own list of things, so this other one has to wait
[23:28] <ari-tczew> sebner: I think that you can download a bzr diff from bug and patch -p1 it on current ubuntu's package
[23:29] <sebner> ari-tczew: I could but that goes against the sense of having a bzr branch and do bzr sponsoring ;)
[23:30] <ari-tczew> sebner: so do you will sponsor it only by debdiff and soon in wednesday?
[23:31] <sebner> ari-tczew: well, keep ubuntu sponsors subscribed and if nobody has sponsored it until then I'll do it
[23:32] <ari-tczew> sebner: ok I'll talk with other sponsors who has not enough sponsored bugs for me
[23:32] <sebner> ari-tczew: so I guess you won't apply tomorrow? (You once told me something about the 22th)
[23:33] <ari-tczew> sebner: no, later
[23:33] <ari-tczew> sebner: not ready now
[23:36] <sebner> kk