[01:20] <kaflowski> hi sebsebseb
[01:29] <kaflowski> can I conplain about the game Nexuiz here?
[01:29] <kaflowski> I believe i was hacked on it
[02:07] <micahg> geser: ping
[02:17] <micahg> cody-somerville: ping
[02:18] <cody-somerville> pong
[02:18] <micahg> cody-somerville: I have a question about adding myself to the DMB agenda, there's no place for Package sets, so I was thinking to add Package Set applications between MOTU and contributing devs
[02:19] <micahg> geser: unping
[02:19] <cody-somerville> micahg, Are you requesting a new package set? Or asking to be granted upload for an existing package set?
[02:19] <micahg> cody-somerville: upload rights
[02:20] <cody-somerville> micahg, Is there a team that grants those rights?
[02:20] <micahg> cody-somerville: DMB
[02:20] <micahg> cody-somerville: Mozilla package set that was approved 3 weeks ago :)
[02:21] <cody-somerville> So we didn't delegate authority for the packageset to another team or something?
[02:21] <micahg> cody-somerville: no, not that I recall
[02:21] <cody-somerville> PerPackageUploader Applications section or a new section is fine
[02:22] <micahg> cody-somerville: are most package set applications authorized by a team other than the DMB?
[02:22] <cody-somerville> some, not all.
[02:22] <micahg> cody-somerville: k, I'll add under per-package uploader then with a note
[02:23] <micahg> cody-somerville: thanks
[02:23] <cody-somerville> np
[02:23] <micahg> cody-somerville: the uploaders team is a smaller subset of the mozilla team w/commit rights to the branches
[02:24] <micahg> s/with/that has/
[02:45] <dobey> hrmm
[02:46] <dobey> anyone know why a package published in the archive already, wouldn't have its data in the bzr tree yet?
[02:47] <dobey> it's interesting, since i uploaded another package today, and it's in the bzr tree already, but the package is in dep-wait for some reason
[02:49] <ajmitch> http://package-import.ubuntu.com/status/ubuntuone-client.html
[02:49] <ajmitch> import failed, file a bug against udd
[02:50] <dobey> huh
[02:52] <ajmitch> I presume that was the package you'd mentioned?
[02:54] <dobey> yeah. it failed in both maverick and lucid
[02:57] <dobey> https://bugs.edge.launchpad.net/udd/+bug/594908
[02:57] <dobey> i guess that's good enough?
[02:59] <ajmitch> hopefully it is
[03:01] <lifeless> have a look at the error log for it
[03:02] <dobey> guess i'll just wait until morning to finish the upload then.
[03:07] <dobey> thanks ajmitch. later :)
[03:07] <ajmitch> np
[06:41] <dholbach> good morning
[06:42] <slytherin> Rhonda: there?
[07:37] <Rhonda> slytherin: Am here now, but you aren't anymore.
[09:51] <EricBa> Hello, is there any motu who has some time to review my package? It's already reviewed by one motu. My programm is a wallpaper changer for gnome. - http://revu.ubuntuwire.com/p/cortina
[09:54] <BlackZ> EricBa: just a question: why are you uploading in on REVU instead of debian? it would have more benefits
[09:54] <BlackZ> and you will get it in ubuntu however
[09:55] <EricBa> BlackZ: I didn't know about any other sites
[09:56] <BlackZ> EricBa: read http://people.debian.org/~mpalmer/debian-mentors_FAQ.html
[09:56] <BlackZ> that could help you
[11:55] <paqman> Hi, looking for somebody to help out with packaging for a quick one line bugfix, check out bug #535193 for iriverter
[11:59] <tumbleweed> paqman: how can I help?
[11:59] <shadeslayer_> tumbleweed: any news on the mesa fix?
[11:59] <tumbleweed> shadeslayer_: you didn't subscribe to the bug? It has been fixed
[12:00] <shadeslayer_> tumbleweed: no i didnt :(
[12:00] <shadeslayer_> tumbleweed: thanks :)
[12:03] <shadeslayer_> whee ... it even built :)
[12:21] <ionte> hi. i have a simple question. am i not supposed to put the "./configure ..." command of the build-process in the configure-section of the rules file?
[12:21] <ionte> the problem is that during debuild it first tries to clean ("make clean"), but it has not generated any Makefile yet
[12:23] <azeem> only make clean if a Makefile is present
[12:24] <azeem> something like
[12:24] <azeem> [ ! -f Makefile ] || $(MAKE) distclean
[12:24] <ionte> ok, thanks. the examples i've seen doesn't do that...
[12:28] <xteejx> QUESTION: If grab-merge shows C* changes between Ubuntu and Debian, but I can see that the files are the same apart from whitespace, can it be synced (the Ubuntu changes were implemented in Debian)
[12:30] <xteejx> Actually, does it even need merged or synced at all if that is the only change?
[12:31] <tumbleweed> xteejx: doesn't C stand for conflict? If ubuntu's changes could be successfully merged, you won't see them in the report
[12:31] <xteejx> tumbleweed: The conflict is only whitespace between Debian and Ubuntu versions
[12:31] <xteejx> 100% sure on that
[12:32] <shadeslayer> ok this is a diff b/w the control file of debian and ubuntu : http://pastebin.com/fBVZHyyw
[12:32] <tumbleweed> xteejx: that doesn't mean debian has merged ubuntu's changes
[12:32] <shadeslayer> do i need to change line 18 and 17 ?
[12:32] <xteejx> tumbleweed: Its in the changelog
[12:32] <shadeslayer> s/and/to
[12:32] <tumbleweed> xteejx: aah, ok
[12:32] <tumbleweed> xteejx: and you've verified that it builds and works
[12:32] <xteejx> It's a safe sync and it builds
[12:32] <shadeslayer> so the ubuntu package reads Depends: ${shlibs:Depends}, ${misc:Depends}
[12:33] <xteejx> yes
[12:33] <tumbleweed> xteejx: sync away
[12:33] <xteejx> tumbleweed: Cool thanks, just was a little unsure about that "conflict" which wasn't really one hehe :)
[12:33] <tumbleweed> shadeslayer_: use everything from the debian version except fro the maintainer change
[12:33] <shadeslayer> tumbleweed: ok...
[12:34] <xteejx> I'm getting good with these merges :D Just keep forgetting to add the LP tag :S
[12:34] <tumbleweed> it looks more likely that debian changed things there than ubuntu did
[12:36] <xteejx> Huh? Why is virtualbox-use-guest-dkms selected for install with an update in Maverick??
[12:36] <shadeslayer_> tumbleweed: seems that debian also released a new upstream version,will mention in changelog
[12:41] <shadeslayer_> tumbleweed: also since debian has a package the version should have 1ubuntu1 right? ( just confirming )
[12:41] <tumbleweed> shadeslayer_: assuming we still need ubuntu changes, yes
[12:42] <tumbleweed> shadeslayer_: are they relevant to debian? Have they been forwarded?
[12:42] <shadeslayer_> tumbleweed: the ubuntu changes?
[12:42] <shadeslayer_> i dont think theres anything different apart from the control file
[12:43] <tumbleweed> shadeslayer_: which package?
[12:43] <shadeslayer_> tumbleweed: kredentials
[12:44] <shadeslayer_> tumbleweed: its on MoM
[12:45] <tumbleweed> shadeslayer_: so, the Ubuntu change was to disable arts support
[12:45] <tumbleweed> (kredentials_0.9.4+nmu1ubuntu1.patch)
[12:45] <shadeslayer_> yes
[12:45] <shadeslayer_>     - debian/rules: Add --without-arts to remove aRts support
[12:47] <shadeslayer_> tumbleweed: also i see dh_clean instances in rules of debian
[12:48] <shadeslayer_> dh_prep as well
[12:48] <shadeslayer_> tumbleweed: http://pastebin.com/89eMAACp
[12:52] <shadeslayer> tumbleweed: we add those as well right?
[12:52] <tumbleweed> shadeslayer: yes the only change you want to keep there is the --without-arts addition
[12:52] <shadeslayer> tumbleweed: ok..
[12:57] <shadeslayer> tumbleweed: debian also added debian/source/format ....
[12:58] <tumbleweed> shadeslayer: the only changes you want to make to the whole package are: maintainer, --without-arts, and changelog merge + new entry
[12:58] <shadeslayer> ok...
[13:06] <shadeslayer_> tumbleweed: wow.. huge debdiff... probably because of new upstream release
[13:07] <tumbleweed> shadeslayer_: yes :)
[13:07] <shadeslayer_> tumbleweed: https://edge.launchpad.net/ubuntu/+archive/primary/+files/kredentials_0.9.4+nmu1ubuntu1.dsc
[13:07] <shadeslayer_> whools
[13:07] <shadeslayer_> tumbleweed: http://pastebin.com/upbzxBG7
[13:08] <tumbleweed> shadeslayer_: aah, so when I said yes to -1ubuntu1 earlier, I didn't realise you were talking about a native package
[13:09] <shadeslayer_> tumbleweed: well yes its a new package :P
[13:10] <tumbleweed> shadeslayer_: new release of a native package
[13:10] <shadeslayer> yep
[13:10] <tumbleweed> native packages don't have -<debian revision number> at the end
[13:10] <tumbleweed> so your version should be 0.9.5ubuntu1
[13:10] <shadeslayer_> ah ok
[13:11] <shadeslayer_> tumbleweed: will post new debdiff :)
[13:16] <shadeslayer_> tumbleweed: will you sponsor the merge?
[13:16] <tumbleweed> shadeslayer_: I have no rights :)
[13:16] <shadeslayer> bhargav: ill be back in a hour then we can talk :D
[13:16] <shadeslayer> or if tumbleweed is kind enough to teach you merging :P
[13:17] <shadeslayer> you can ask him :)
[13:18] <shadeslayer> tumbleweed: aww....
[13:18] <shadeslayer> tumbleweed: thanks anyways :D
[13:18] <tumbleweed> np
[13:20] <EricBa> Hello, is there any motu who has some time to review my package? It's already reviewed by one motu. My programm is a wallpaper changer for gnome. - http://revu.ubuntuwire.com/p/cortina
[14:08] <bilalakhtar> Hey there, can anyone sponsor package python-tweepy??
[14:08] <bilalakhtar> bug #579992
[14:13] <xteejx> Hey guys, bug 391918 ... the mom page shows debian version 2.5.3-2 but the bug has an earlier version. Is this wrong since the debian version is newer than the incorrect? bug report??
[14:22] <geser> xteejx: old comment as the bug is already "Fix released". MoM doesn't clear comments.
[14:23] <xteejx> geser: Ohh right, thought something wasn't right there. So it's workable then I take it?
[14:25] <geser> yes, but ask the last uploader if he's working on it or not
[14:26] <xteejx> Uploader? Daniel Holbach?
[14:27] <geser> sorry, I meant the person who did the last changes
[14:27] <xteejx> geser: no worries :) Ok I'll remove the comment since its out of date and contact the previous guy. Thanks again geser
[14:27] <xteejx> :D
[14:35] <huats> bdrung_, I have seen you were the last uploader of torbutton any reason why there is no binaries in lucid ?
[14:37] <geser> huats: torbutton got removed from lucid: "unsuportable, see https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel/extension-list"
[14:37] <huats> geser, ok thanks ! I have missed that
[15:23] <trombonechamp_> How would one go about getting included in the ubuntu repos?
[15:23] <MTecknology> If I know where a .deb is on http://ftp.us.debian.org/debian/pool/main/... then how can I grab the source and debdiff?
[15:24] <trombonechamp_> Some rather crude .debs (made with python-stdeb)
[15:25] <MTecknology> trombonechamp_: revu.ubuntuwire.com
[15:26] <MTecknology> yay :D - Answered my question
[15:32] <funkyHat> trombonechamp_: the ideal way to go about it would be to get included in Debian's repos, then the package will be automatically synced into Ubuntu in the next (or current) development cycle
[15:32] <geser> MTecknology: dget the .dsc from that directory which matches the version of the deb you want
[15:33] <trombonechamp_> funkyHat: What is the best way to go about that?
[15:35] <dobey> hrmm, wonder what happened to fabrice_sp
[15:56] <anoteng> any motu's willing to take a look at my package? http://revu.ubuntuwire.com/p/transgui bug #332067 I changed the package according to fabricesp's comments.
[16:00] <MTecknology> trombonechamp_: just on what funkyHat said - get something into debian through here - http://mentors.debian.net
[16:19] <rbelem> anyone using cowbuilder?
[16:36] <trombonechamp_> thanks MTecknology, that looks like what I need
[17:00] <bhargav> clear
[17:01] <bhargav> sorry my bad.. was about to type that in the terminal.
[17:50] <MTecknology> what was the command to find what patching system is being used?
[17:51] <MTecknology> found it - I kept thinking which-patch instead of what-patch
[18:27] <evilshadeslayer> bhargav: hey any questions now?
[18:29] <BlackZ> fabrice_sp: unfortunatly I couldn't send the patch for steam to upstream, their bugtracker seems to be down - however I sent them an e-mail
[18:30] <fabrice_sp> Hi BlackZ
[18:30] <fabrice_sp> great: let's see what happens with this patch ;-)
[18:31] <BlackZ> fabrice_sp: check the bug report, I have marked it as "Triaged", for now
[18:31] <fabrice_sp> it's a kind of borderline, as Debian don't have the problem and upstream could answer that it's not 'useful'
[18:31] <fabrice_sp> oh, that's why I received an update of that bug report
[18:32]  * fabrice_sp began to think that he didn't uploaded it
[18:32] <BlackZ> fabrice_sp: you received also why I added the bugwatch to the debian bug tracker :)
[18:33] <fabrice_sp> great :-)
[18:33] <dobey> james_w: still around?
[18:33] <dobey> hi fabrice_sp
[18:34] <james_w> hi dobey
[18:34] <fabrice_sp> Hi dobey
[18:34] <dobey> james_w: hey. the lucid bzr branch for ubuntuone-client seems to still be outdated? there was an SRU released last week. or do those end up in another branch somewhere, that i can't see? :)
[18:35] <james_w> they are in the lucid-proposed or lucid-updates branch
[18:35] <dobey> fabrice_sp: i replied to your comments on the mocker package. i really can't find a longer description anywhere. the description on the launchpad page is even less meaningful to random people :)
[18:36] <dobey> james_w: lp:ubuntu/lucid-updates/ then?
[18:36] <fabrice_sp> dobey, so just create one :-)
[18:36] <dobey> fabrice_sp: i can't think of one either
[18:36] <fabrice_sp> by the way, you know that you can (and probabaly should) submit your package to Debian too?
[18:36] <dobey> find also includes linking in my brain
[18:37] <james_w> dobey: yes, if it's in lucid-update
[18:37] <james_w> s
[18:37] <dobey> yes i know that. but trying to keep its exposure minimal, per upstream request
[18:37] <dobey> james_w: ok, thanks
[18:39] <fabrice_sp> dobey, about watch file: if there is no tarball, you should probably add a get-orig-source target in your rules file
[18:40] <dobey> fabrice_sp: and just have it do bzr branch?
[18:42] <fabrice_sp> create a tarball, as you need a tarball to upload it
[18:42] <fabrice_sp> by the way, the PKG-INFO file contains the following description "Graceful platform for test doubles in Python (mocks, stubs, fakes, and dummies)."
[18:42] <fabrice_sp> and to be honest, I don't even know what it is about :-)
[18:43] <dobey> i made a tarball
[18:44] <dobey> the orig.tar.gz is the tarball
[18:44] <dobey> but i can't upload that as a release
[18:44] <dobey> on the launchpad mocker page
[18:44] <dobey> yes it does, and that is a very non-descript description :)
[18:45] <fabrice_sp> I know, but we need some way to be able to recreate the tarball automatically
[18:46] <dobey> and how exactly does that work for other packages which are just snapshots from git/svn/whatever?
[18:49] <fabrice_sp> you can check aptoncd package
[18:50] <fabrice_sp> this is how upstream works
[18:56] <dobey> fabrice_sp: so aptoncd never actually makes relaeses?
[19:38] <fabrice_sp> dobey, sorry: got distracted
[19:38] <fabrice_sp> dobey, it had one a long time ago, and upstream decided to do next release after rewriting everything, and that never happened
[19:41] <tumbleweed> fabrice_sp: you see atlas built in only 13 hours :)
[19:42] <shadeslayer> hey if compiles http://packages.debian.org/sid/libyahoo2-11 fine on a maverick pbuilder can it be syncd to maverick repos?
[19:42] <fabrice_sp> tumbleweed, the armel one? Great! :-)
[19:42] <tumbleweed> yeah
[19:42] <fabrice_sp> shadeslayer, if changes has been done in Ubuntu, you have to see what the change can be dropped
[19:43] <shadeslayer> fabrice_sp: ah ok :)
[19:43]  * fabrice_sp is glad that no armel buildd admin will wait for him in irc
[19:43] <fabrice_sp> :-)
[19:44] <fabrice_sp> so it's less that ghc6 :-)
[19:45] <fabrice_sp> (34 hours)
[19:46] <tumbleweed> heh
[19:53] <dobey> fabrice_sp: it looks like aptoncd doesn't have a watch file or get-upstream-source rule in debian/rules :)
[19:54] <fabrice_sp> dobey, it's get-orig-source. let me check :-)
[19:54] <shadeslayer> fabrice_sp: ok ive had a look and all ubuntu changes can be dropped.. there was a build dep on dpatch in libyahoo2 which was required for a patch to fix FTBFS
[19:55] <shadeslayer> now that it doesnt FTBFS we can drop it
[19:55] <shadeslayer> also we have new deps from debian....
[19:55] <dobey> fabrice_sp: ok, and it just does bzr --export
[19:55] <shadeslayer> fabrice_sp: https://merges.ubuntu.com/liby/libyahoo2/REPORT
[19:56] <fabrice_sp> dobey, yes: I had hard time to actually find the correct command :-)
[19:56] <dobey> which is weird, because looking at that, it seems broken
[19:56] <dobey> looks like it is using the previous version in the debian/changelog as the version, rather than what might be in the bzr tree
[19:56] <fabrice_sp> shadeslayer, if so, then create the sync bug with requestsync
[19:57] <shadeslayer> fabrice_sp: awesome :)
[19:58] <fabrice_sp> and don't forget to explain why you think that the diff can be dropped
[19:58] <fabrice_sp> dobey, only for the upstream version
[19:59] <fabrice_sp> I may have hardcoded it though
[19:59] <shadeslayer> fabrice_sp: any idea where pbuilder keeps build logs?
[19:59] <dobey> yes, for the upstream version. but it may be incorrect
[20:00] <tumbleweed> shadeslayer: if you use pdebuild it logs to ..
[20:00] <fabrice_sp> shadeslayer, IIRC, you have to specify it at build time
[20:00] <shadeslayer> tumbleweed: doh...
[20:00] <fabrice_sp> dobey, you can submit a fix ;-)
[20:00] <fabrice_sp> (to Debian, as I maintain the package there)
[20:01] <dobey> fabrice_sp: but what about random snapshots that do have regular releases?
[20:01] <fabrice_sp> dobey, in this case, you have to get the lastest release from launchpad
[20:03] <NorthernLights> Hi there
[20:04] <fabrice_sp> Hi NorthernLights
[20:04] <NorthernLights> It's time for my daily poke for a review!
[20:05] <NorthernLights> I saw you, fabrice_sp, had a look at it already, thanks. I uploaded a fix: http://revu.ubuntuwire.com/p/killrogues
[20:05] <dobey> fabrice_sp: how does that solve the problem when i want to ship a snapshot prior to the next release, though? uscan will still complain :)
[20:06] <fabrice_sp> NorthernLights, I won't have time to havve a look at it today. maybe tomorrow
[20:06] <NorthernLights> That's great, thanks.
[20:07] <NorthernLights> I also commented on a few packages but had not so much answer, except for http://revu.ubuntuwire.com/p/gmail-notifier
[20:07] <NorthernLights> Also i was reading docs about MOTU yesterday and was wondering: how much time does it eat you? Being a MOTU and a Debian dev
[20:07] <fabrice_sp> dobey, yes, you're right, but as I saw that the stable version was in 2007, I thought that only bzr would be released :-)
[20:08] <fabrice_sp> NorthernLights, it depends the time you want to spend :-)
[20:08] <NorthernLights> fabrice_sp, for instance, you?
[20:09] <fabrice_sp> NorthernLights, around 3 hours a day during the week, and very variable during the week end
[20:09] <dobey> fabrice_sp: i will be poking upstream to get some new tarballs released in the coming weeks
[20:09] <NorthernLights> 3 hours a day...
[20:09] <fabrice_sp> dobey, cool :-)
[20:09] <NorthernLights> sounds a lot to me
[20:10] <fabrice_sp> NorthernLights, it's the time I want to dedicate to Ubuntu
[20:10] <NorthernLights> right
[20:10] <fabrice_sp> It could be less
[20:10] <NorthernLights> almost a part time job though
[20:10] <fabrice_sp> this is obviously added to my real job :-)
[20:10] <NorthernLights> yes, big days
[20:10] <fabrice_sp> (a 9 to 10 one)
[20:10] <fabrice_sp> yes :-)
[20:10] <fabrice_sp> 9 to 10 hours a day, I meant
[20:11] <NorthernLights> yeah, big days!
[20:11] <NorthernLights> For how long have you been doing it? (Ubuntu + Debian)
[20:11] <fabrice_sp> I mostly spend my time sponsoring
[20:12] <fabrice_sp> let me check my wiki page :-)
[20:12] <dobey> fabrice_sp: so i guess uscan was just failing during the lucid cycle, for gnome-kerying for example, in the same manner, while there were snapshots of it being packaged
[20:12] <NorthernLights> No bug triaging or package maintaining?
[20:12] <NorthernLights> Yes i guess i could check it too
[20:13] <dobey> fabrice_sp: actually, gnome-keyring still fails, because for some reason it is versionsed as "2.92.92.is.2.30.1"
[20:13] <dobey> for the upstream version
[20:13] <dobey> which is weird :)
[20:13] <fabrice_sp> NorthernLights, Motu since 09/09 (and contributing since end of Intrepid cycle)
[20:13] <fabrice_sp> dobey, yes :-)
[20:14] <shadeslayer> fabrice_sp: bug 595224
[20:14] <shadeslayer> fabrice_sp: build log is attached :)
[20:14] <NorthernLights> wow, 9-10 hours a day of job, 3 hours of contributing, a wife and 2 kids. Do you ever sleep?
[20:15] <dobey> fabrice_sp: so i guess the watch file isn't a big issue, unless there are never any more upstream release tarballs, in which case, it can be removed later and replaced with get-orig-source, no?
[20:15] <shadeslayer> NorthernLights: thats the dedication MOTU look for :)
[20:16] <fabrice_sp> NorthernLights, 6 hours of sleep, so I still have some free time ;-)
[20:16] <fabrice_sp> shadeslayer, will have a look later (I broke BlackZ patch right now, so I have to fix it :-) )
[20:17] <NorthernLights> :D
[20:17] <shadeslayer> oh crap... i dropped the laptop :P
[20:17] <NorthernLights> good job though, your wiki page is impressive; nice packages ther
[20:17] <NorthernLights> e
[20:17] <fabrice_sp> NorthernLights, this is what I prepared for applying to u-u-c and Motu
[20:18] <shadeslayer> fabrice_sp: hehe :)
[20:18] <fabrice_sp> it's easier to follow up what kind of stuff I did (and learned)
[20:19] <fabrice_sp> I still discovered some bug I fixed one year ago, and I think "Wouah, I fixed that!" :-)
[20:19] <NorthernLights> :p
[20:21] <NorthernLights> oh, i had another question: how to link a LP bug to a Debian bug? (to link my needs-packaging to the Debian RFP)
[20:21] <arand> NorthernLights: Use the "Also affects distribution" button and paste the BTS link
[20:22] <NorthernLights> tx, gonna try that. i always clicked "also affects project", input "debian", was told "too many results"
[20:22] <fabrice_sp> anybody knows how to put a multiline description in a DEP3 header?
[20:24] <arand> fabrice_sp: Use indentation, or points: Good guidelines here: http://dep.debian.net/deps/dep3/
[20:25] <fabrice_sp> arand, I was looking for that pages. Thanks!
[20:27]  * fabrice_sp should read the error message before asking :-)
[20:27] <shadeslayer> fabrice_sp: how do you assign a bug in MoM ?
[20:27] <shadeslayer> does it get picked up automatically?
[20:27] <fabrice_sp> shadeslayer, there is an hidden field
[20:28] <shadeslayer> fabrice_sp: where? i can only see the comment field
[20:28] <NorthernLights> Also, I was wondering... how can you fix so many bugs in so many packages? Each time I look for a bug to try to fix, and find interesting ones, i feel to fix it would require such a perfect understanding of the packages software that you'd need to be its upstream author
[20:28] <NorthernLights> (s/packages software/packaged software)
[20:28] <shadeslayer> ah ok i needed #
[20:29] <fabrice_sp> shadeslayer, I see you found it :-)
[20:29] <shadeslayer> fabrice_sp: i knew about the comment field... just didnt know i had to put a # in front of bug number :P
[20:30] <fabrice_sp> NorthernLights, most of the time, the patch already exists either upstream o in Debian
[20:31] <NorthernLights> hm, right
[20:31] <NorthernLights> gonna look for bugs:)
[20:32] <shadeslayer> NorthernLights: or there is a patch attached :)
[20:32] <fabrice_sp> good luck :-)
[20:32] <shadeslayer> NorthernLights: also join the bug squad and some bug mailing lists
[20:33] <NorthernLights> i thought i should actually fix something before, to see if i can actually do it
[20:34] <bhargav> Should i keep kdiff3 in Section: devel or kde ?? in debian its in kde
[20:36] <fabrice_sp> shadeslayer, you should have used the requestsync script :-D
[20:36] <shadeslayer> fabrice_sp: 0_o
[20:36] <fabrice_sp> bhargav, is it the only change?
[20:36] <shadeslayer> ahhhh
[20:36] <shadeslayer> fabrice_sp: will use next time... what info does it add?
[20:36] <tumbleweed> shadeslayer: it saves you effort
[20:37] <shadeslayer> tumbleweed: :P
[20:37] <fabrice_sp> the script I uses fail to automatically check it
[20:37] <bhargav> fabrice_sp http://pastebin.com/pdxiwrd5
[20:37] <shadeslayer> fabrice_sp: want me to refile?
[20:38] <fabrice_sp> shadeslayer, I mean there is a helper script for sync request ack that fails in this case
[20:38] <shadeslayer> hmm
[20:38] <fabrice_sp> if you don't mind: just copy/paste the description adn the title from the generated one
[20:38] <shadeslayer> sure
[20:39] <fabrice_sp> bhargav, the less derivation from Debian, the better
[20:40] <fabrice_sp> especially if it's just to keep lintian happy :-)
[20:40] <shadeslayer> fabrice_sp: updated bug 595224
[20:40] <bhargav> fabrice_sp, what about line 82 and 84
[20:40] <shadeslayer> do i copy the changelogs as well? like in the report...
[20:41] <fabrice_sp> shadeslayer, yes, please
[20:42] <shadeslayer> fabrice_sp: fixed :)
[20:43] <fabrice_sp> bhargav, I have no opinion on that. Maybe someone else have an opinion on that kde -> devel change
[20:43] <fabrice_sp> shadeslayer, thanks. I'll check
[20:43] <fabrice_sp> a bit later
[20:44] <shadeslayer> sure
[20:44] <bhargav> fabrice_sp, anyways thanks
[20:58] <ari-tczew> MoM (merges.ubuntu.com) has very ardous bug. new available merge shows deprecated comment from old (previous) merge. this is misleading.
[20:59] <Laney> I believe you can file a bug on lp/merge-o-matic
[21:02] <ari-tczew> is anyone taking care about MoM yet?
[21:02] <micahg> ari-tczew: not all comments will be deprecated by new uploads though
[21:02] <fabrice_sp> shadeslayer, did you actually check the source code, to see if the patch was integrated?
[21:03] <shadeslayer> fabrice_sp: well without the patch it caused FTBFS issues
[21:03] <micahg> ari-tczew: maybe just a warning on top to make sure the bug is still valid before working on or disregarding a merge
[21:03] <tumbleweed> yeah, it'd be sensible to expire comments that just mention a resolved bug
[21:03] <shadeslayer> like the changelog says...
[21:03] <fabrice_sp> Actually, there is an undocumented change. Did you checked it?
[21:03] <micahg> tumbleweed: nope, that won't work either
[21:03] <shadeslayer> fabrice_sp: where?
[21:03] <fabrice_sp> http://patches.ubuntu.com/by-release/ubuntu/liby/libyahoo2/
[21:03] <fabrice_sp> in debian/rules
[21:04] <tumbleweed> micahg: even different bug fixed logo would make an enormous difference
[21:04] <micahg> tumbleweed: for merge in progress that works, but not for blacklist
[21:04] <shadeslayer> fabrice_sp: ill dget  the files.. hold one sec
[21:04] <shadeslayer> fabrice_sp: in the ubuntu package?
[21:05] <fabrice_sp> yep
[21:05] <tumbleweed> micahg: oh yes
[21:05] <fabrice_sp> shadeslayer, it seems the changed line is not there anymore, so it seems safe to sync
[21:05] <ari-tczew> micahg: I don't know whether all comments are deprecated, but I see a lot of examples this issue
[21:06] <shadeslayer> fabrice_sp: :)
[21:06] <micahg> ari-tczew: indeed, if packages are on the blacklist are excluded from MoM and the bugs that are fix released are removed, I think we might be ok
[21:07] <shadeslayer> fabrice_sp: the patch we introduced was to stop the package from failing to build from source
[21:07] <ari-tczew> micahg: blacklist from MoM?
[21:07] <shadeslayer> it was probably forwarded upstream....
[21:08] <micahg> ari-tczew: blacklisted sync packages were excluded from MoM
[21:09] <ari-tczew> micahg: I think you are wrong, because I see also comments like "done", when package is not merged - comment has been excavated from previous merge
[21:09] <fabrice_sp> shadeslayer, or it's not required anymore because the aPI changed back to what is was :-)
[21:10] <shadeslayer> :)
[21:10] <micahg> ari-tczew: well, comments like that probably shouldn't be there in the first place IMHO
[21:10] <fabrice_sp> shadeslayer, by the way, your email adress is not public ;-)
[21:10] <shadeslayer> fabrice_sp: ??
[21:10] <shadeslayer> fabrice_sp: on my LP page?
[21:11] <ari-tczew> micahg: first place?
[21:11] <fabrice_sp> yes, the ack-sync script sign the package with the email address, and in your case, it fails to get it
[21:11] <micahg> ari-tczew: should not have been added at all
[21:11] <shadeslayer> fabrice_sp: theres no option to set it as public :P
[21:11] <shadeslayer> nvm
[21:12] <shadeslayer> fabrice_sp: try now...
[21:12] <fabrice_sp> too late: I manually acked the sync request
[21:12] <fabrice_sp> :-)
[21:12] <ari-tczew> micahg: so are you agree that this is a bug?
[21:13] <micahg> ari-tczew: well, those are IMHO user errors :)
[21:13] <shadeslayer> fabrice_sp: :P
[21:14] <micahg> ari-tczew: maybe it should just be a field for bug #'s and not comments
[21:14] <ari-tczew> micahg: so do you think that someone adds these comments by mistake? I don't think so...
[21:14] <micahg> ari-tczew: no, but perhaps it's a process issue
[21:16] <ari-tczew> micahg: IMO MoM not delete comments cache when package has been uploaded
[21:16] <shadeslayer> fabrice_sp: what does the script you refer to do?
[21:17] <fabrice_sp> shadeslayer, ack-sync
[21:17] <micahg> ari-tczew: yes, but that doesn't always make the comment outdated, you need to address the blacklist issue as well
[21:17] <fabrice_sp> shadeslayer, it makes the sponsoring of sync request easier
[21:17] <shadeslayer> ok
[21:19] <ari-tczew> micahg: we need a modern merges system management :-)
[21:20] <micahg> ari-tczew: ok :), maybe speak with dholbach as I thought the new harvest would incorporate some of this
[21:21] <ari-tczew> what do you think, can we reduce remaining merges to ~50 (50 in main and 50 in universe) before FeatureFreeze?
[21:23]  * micahg will do his merges after getting upload rights (hopefully) at the beginning of the alpha3 cycle
[21:23]  * micahg will do them even if he doesn't get the upload rights though :)
[21:24] <ari-tczew> is micahg going to join MOTU?
[21:24] <micahg> ari-tczew: no, I have my own package set :)
[21:25] <micahg> ari-tczew: I'm working on the xulrunner rdepends and mozilla apps
[21:27] <micahg> ari-tczew: I might go for MOTU next year
[21:30] <ajmitch> morning
[21:30] <dobey> hi ajmitch
[21:30] <NorthernLights> evening
[21:31] <ari-tczew> micahg: how many packages you'll got for upload rights?
[21:31] <micahg> ari-tczew: about 40
[21:31] <ari-tczew> :O
[21:31] <ari-tczew> nice
[21:32] <geser> Hi ajmitch
[21:32]  * ajmitch would upload some packages if his laptop would stop fscking
[21:33] <geser> upgrade to ext4
[21:34] <ajmitch> I probably should, because this gets annoying just often enough to make me want to change it
[21:35] <ari-tczew> ext4 sucks, I can't integrate ext4 in my WinXP
[21:35] <chrisccoulson> micahg - is there anything else that needs to happen to get the packageset implemented btw?
[21:35] <chrisccoulson> that's thefault of WinXP
[21:35] <chrisccoulson> not ext4 ;)
[21:35] <micahg> chrisccoulson: aside from cjwatson having time, not that I know of
[21:35] <ari-tczew> only ext3 I can use by ifs driver
[21:35] <cjwatson> nag me once every couple of days and I swear I'll do it
[21:35] <cjwatson> hopefully tomorrow
[21:36] <chrisccoulson> cjwatson - awesome, thanks :)
[21:36] <chrisccoulson> and thanks micahg for organising this too ;)
[21:37] <geser> cjwatson: you will do it just to stop chrisccoulson nagging you? :)
[21:38] <chrisccoulson> lol, i don't really nag do i?
[21:38] <cjwatson> geser: you'd be amazed at how much of my schedule is the desire for an easy life
[21:47] <shadeslayer> fabrice_sp: does the sync script add stuff like XSBC maintainer by itself?
[21:55] <sebner> shadeslayer: why do you need XSBC for a sync ;)
[21:56] <shadeslayer> sebner: well for the control file.. i thought we need the XSBC field in control.. or do we not?
[21:56] <sebner> shadeslayer: you know what a sync is, do you?
[21:56] <sebner> shadeslayer: sync = packages taken 1:1 from debian
[21:56] <sebner> shadeslayer: what you are talking about is a merge
[21:57] <shadeslayer> sebner: ohhh... so we dont even change the package one bit? awesome ....
[21:57] <sebner> shadeslayer: else we wouldn't be able to do auto-syncs
[21:57] <shadeslayer> sebner: right!
[21:57] <sebner> :)
[21:57]  * shadeslayer sees another sync coming through
[21:57] <shadeslayer> yep
[21:58] <micahg> shadeslayer: only the maintainer filed is mangled in the buildds
[21:58] <micahg> *field
[22:10] <blueyed> Is there no backport of debootstrap yet? (for lucid)
[22:10] <blueyed> This is required by mk-sbuild for example.
[22:10] <EricBa> Hello, is there any motu who has some time to review my package? It's already reviewed by one motu. My programm is a wallpaper changer for gnome. - http://revu.ubuntuwire.com/p/cortina
[22:15] <SpamapS> hmm.. is REVU still the proper way to add packages?
[22:15] <SpamapS> http://revu.ubuntuwire.com/p/pylibmc
[22:15] <SpamapS> "Package is for "maverick" but only packages for "lucid" are currently accepted."
[22:16] <ajmitch> it is, that's a mistake
[22:17] <ajmitch> some issues are because it's hard to upgrade stuff on that server :)
[22:19] <geser> it's better to get new packages into Debian so both Debian and Ubuntu benefit from it (and because we have a lack of reviewers)
[22:19] <lifeless> geser: we can still review here
[22:20] <micahg> geser: can only MOTU and core-dev review packages or any dev?
[22:20] <ajmitch> micahg: anyone can leave comments, not everyone can advocate
[22:20]  * ajmitch wonders if it's safe to change the default distribution in revu.cfg
[22:21] <micahg> ajmitch: what about advocating?
[22:21] <geser> I'm not sure about the current state of REVU: only MOTU and core-dev can advocate, but others can add comments too
[22:21] <ajmitch> micahg: motu can advocate, not sure if it checks that team or ~ubuntu-dev
[22:22] <ajmitch> package sets have made things complicated again :)
[22:22] <ajmitch> or at least PPU
[22:23] <SpamapS> geser: I've filed an ITP too, but I am not a debian developer and I'm not sure I'll be able to get it into debian in time for Alpha2. We're trying to get Maverick's memcache support much better. :)
[22:24] <ajmitch> SpamapS: given that it's a python package, #debian-python on OFTC will probably welcome it as well
[22:25] <ajmitch> whether you get it into debian or ubuntu first, that's still a good place to follow up on getting it sponsored :)
[22:25] <ajmitch> actually...
[22:25] <ajmitch> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556901
[22:26] <SpamapS> wha?
[22:26] <ajmitch>  rmadison -udebian pylibmc pylibmc |      1.0-1 |      unstable | source
[22:26] <ajmitch> looks to be there already
[22:26] <SpamapS> hrm
[22:27] <SpamapS> why didn't it show up in my searches
[22:27] <geser> it "just" need syncing to maverick
[22:27] <ajmitch> and 1.0-1 in maverick
[22:27] <SpamapS> clint@ubuntu:~$ apt-cache search pylibmc
[22:27] <SpamapS> clint@ubuntu:~$
[22:27] <SpamapS> :(
[22:27] <geser> oh, it's already synced
[22:27] <SpamapS> 1.0 is really old
[22:27] <SpamapS> like.. months. ;)
[22:27] <geser> 1.0-1    release (universe)   30 hours ago
[22:28] <ajmitch> yeah, 30 hours isn't long :)
[22:28] <SpamapS> haha doh
[22:28] <SpamapS> ok
[22:28] <geser> and it's in the binary NEW queue
[22:28] <SpamapS> hmm, I only looked in WNPP
[22:28] <SpamapS> because 2 weeks ago I looked in packages and it wasn't there
[22:28] <shadeslayer> geser: whats our policy on packages in debian experimental?:
[22:28] <SpamapS> should have re-checked packages I guess. :-P
[22:28] <shadeslayer> like can we sync/merge those?
[22:29] <ajmitch> SpamapS: it was uploaded in december to debian
[22:29] <SpamapS> ajmitch: I swear I didn't find it on packages.debian.org.. :-P
[22:29] <SpamapS> bleh.. how embarassing
[22:29] <ajmitch> just quietly close the debian ITP... :)
[22:30] <SpamapS> I intend to
[22:30] <geser> shadeslayer: you mean syncing from experimental? if you have a good reason for it, it can be done
[22:30] <SpamapS> so if its been in debian unstable since dec why isn't it synced yet?
[22:30] <ajmitch> SpamapS: it was just synced (30 hours ago)
[22:31] <micahg> SpamapS: Lucid sync'd from testing
[22:31] <shadeslayer> geser: hmm.. im asking because theres a new package called workbench that needs to be added to repos
[22:31] <ajmitch> it wasn't automagically synced to maverick because new get checked over by archive admins at least a little bit
[22:33] <SpamapS> micahg: ah
[22:33] <geser> shadeslayer: if you have tested that the package works, that's a good enough reason to sync from experimental (it should be just something more than "experimental has a newer version")
[22:33] <shadeslayer> geser: of course ;)
[22:35] <shadeslayer> geser: the new mysql workbench replaces mysql query browser and administrator
[22:35] <shadeslayer> and #debian-mentors says since the release is a RC it will go in experimental
[22:41] <SpamapS> hrm.. so the problem with pylibmc 1.0 is that it doesn't work with libmemcached 0.40
[22:46] <wtf1> what is partial upgrade?
[22:52] <arand> wtf1: http://swiss.ubuntuforums.org/showthread.php?t=1286309
[22:54] <ubuntu147> arand:  i upgrade my system with this?
[22:55] <micahg> !support | ubuntu147
[22:55] <ubuntu147> uh, ok
[22:55] <ubuntu147> thnx
[23:08] <shadeslayer> micahg: if suppose packaging copyright is held by a company and we package a new version for ubuntu ( not in the repo aka native package ),do we retain the copyright? and will it get past the upload queue
[23:08] <lifeless> shadeslayer: as long as the *licence* you put on the copyright material is acceptable
[23:09] <lifeless> shadeslayer: nothing (in terms of package uploads/inclusion) Ubuntu is affected by who holds the copyright, its *all* about the licensing
[23:09] <shadeslayer> ah ok...
[23:09] <shadeslayer> the debs released by the company are not in the repos were packaging a new version :)
[23:09] <shadeslayer> for ubuntu + debian :)
[23:10] <lifeless> cool
[23:10] <eagles0513875> ya to replace EOL mysql-query-browser and mysql-admin
[23:13]  * shadeslayer returns to merging ming32
[23:31] <bdrung_> looking at mom, i see: If you are not the previous uploader, ask the previous uploader before doing the merge. This prevents two people from doing the same work.
[23:31] <bdrung_> how far do we need to go? is it enough to check if the person is available on IRC and ask him/her?
[23:34] <ajmitch> email might be nice, especially with some people not being on IRC at the same time as you
[23:36] <bdrung_> ajmitch: and how long should someone wait for a response?
[23:37] <ajmitch> I don't know, it may depend on how much work the merge is and how close to freeze time it is, or how active the previous merger has been lately
[23:38]  * micahg would suggest 72 hrs
[23:41] <shadeslayer> any sponsors around?
[23:41]  * maco hides
[23:41] <shadeslayer> maco: ah there you are :)
[23:41] <shadeslayer> maco: just one sec..
[23:41] <maco> were my ears stickin out? darn it
[23:41] <shadeslayer> maco: :P
[23:42] <bdrung_> maco: to avoid work: just be quiet. :P
[23:43] <maco> bdrung_: yeah im just playing around since i was sponsoring for shadeslayer yesterday and was warned there were more to come
[23:43] <ajmitch> maco: you can still run
[23:43] <maco> heh
[23:43] <maco> im assuming itll be kde extragear stuff
[23:43]  * shadeslayer gets a rope :)
[23:44] <bdrung_> ajmitch: micahg: it's not easy to evaluate how active the previous merger has been lately. it would be nice if there were a recommended way (for example how long you should wait)
[23:44] <shadeslayer> maco: nah.. ming32 compiler this time :)
[23:44] <shadeslayer> im just waiting for a fresh download of the package from debian..
[23:44] <shadeslayer> i might have removed a patch in the debian package by mistake :P
[23:44] <bdrung_> maco: can i ask you to do some sponsoring and warn you that more will come too?
[23:45] <ajmitch> I doubt there's any agreed-upon time that you should wait
[23:45] <ajmitch> though a day or two seems reasonable
[23:45]  * ajmitch would just like to get the merge list cleared up a little
[23:46] <maco> shadeslayer: awww i thought you were just gonna use me to improve the kde : not-kde ratio!
[23:46] <shadeslayer> maco: hehe...
[23:46]  * ajmitch does wish that MoM comments didn't stick around from one release to the next
[23:46] <shadeslayer> maco: well ming32 helps in a way :P
[23:46] <shadeslayer> you can use it to compile kde in windows ><
[23:48] <shadeslayer> maco: can you dget this : http://packages.debian.org/sid/mingw32
[23:48] <shadeslayer> ill post the changes the packaging in a short while
[23:48] <bdrung_> who needs kde and/or windows? *gr&d*
[23:50]  * bdrung_ is in the mood for making jokes.
[23:51] <ajmitch> you'd better be careful
[23:51] <maco> bdrung_: i made a sign that said "Kubuntu > Ubuntu" and put it on the wall above me when i was sitting in rick spencer / jfo / pgraner 's round table at SELF
[23:52] <maco> it was just for rick though... the kernel folks dont care
[23:52] <bdrung_> what's SELF?
[23:53] <bdrung_> ajmitch: that's why i made clear that it was a joke (to avoid misunderstanding)
[23:54] <shadeslayer> maco: apply this : http://pastebin.com/raw.php?i=EkMmtdMt : on top of debian packaging
[23:55] <maco> bdrung_: southeast linuxfest
[23:56] <shadeslayer> maco: all info in changelog :)