[07:06] <dholbach> good morning
[07:12] <philipballew> Good morning dholbach
[07:13] <dholbach> hi philipballew
[07:13] <philipballew> good day in your neck of the woods I hope
[07:17] <dholbach> I'm sure it will be :)
[07:21] <philipballew> Most excellent!
[07:32] <pibara> I'm not quite sure what to do with respect to getting a library I wrote into universe. I've added a script for generating a proper deb package (for amd64) from the source tree, and probably could do the same for other architectures (to what I don't have access). Should I look for an existing universe maintainer willing to add my package to universe, or go trough the mentor thingy to become one myself? I would prefer the first, but not sure if this is possible,
[07:37] <pibara> Anyone who could advice me on that? Do I look for a universe maintainer (if so where do I find one), or do I need to go trough the mentor mill to become one myself?
[07:42] <pibara> For some more context, its a C++ JSON parsing library build on top of the GLIB JSON C library.
[07:56] <micahg> pibara: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[08:17] <pibara> micahg: tnx
[09:38] <hakermania> tumbleweed: some time you suggested me to work on other projects too, while you'll be looking on mine, or something like that. Were you reffering to bug fixes?
[09:39] <tumbleweed> hakermania: I mean if you are hanging around in #ubuntu-motu, you could help out with Ubuntu :) see the links in the topic
[09:42] <hakermania> tumbleweed, would love to
[10:49] <jtaylor> is this supposed to throw an exception in python2.7? import locale; locale.normalize(u"en_US")
[10:49] <jtaylor> it works without unicode
[11:45] <tumbleweed> jtaylor: works on debian
[11:47] <Pici> jtaylor: works on Ubuntu (Natty) as well.
[11:47] <jtaylor> o_O
[11:48] <jtaylor> does not work in my unstable chroot
[11:50] <tumbleweed> ah, this was on testing, you're right re unstable
[11:50] <jtaylor> its a python 2.7.2 regression then
[11:51] <jtaylor> introduced by this patch: http://bugs.python.org/issue1813
[11:53] <tumbleweed> that looks about right
[11:54] <tumbleweed> so, what does it break?
[11:54] <jtaylor> playonlinux and aptdaemon
[11:54] <jtaylor> the latter was fixed
[11:54] <jtaylor> or worked around
[11:54] <jtaylor> former patch submitted to debian
[11:55] <jtaylor> but it will break a lot of wx code
[11:55] <jtaylor> wx.Locale.GetCanonicalName returns unicode
[11:56] <tumbleweed> :/
[11:59] <jtaylor> reported upstream http://bugs.python.org/issue12752
[12:08] <jtaylor> Should I report it against python package too?
[12:08] <jtaylor> and put all bugs duplicate against it
[12:08] <jtaylor> found 3 already
[12:09] <systemclient> given that my package was accepted into debian unstable, what do I have to do to get it into ubuntu?
[12:10] <tumbleweed> jtaylor: yes (against python2.7),  it sounds like we should do something in Debian/Ubuntu about it.
[12:10] <tumbleweed> systemclient: we're in feature freeze, so file a sync request witha feature freeze exception
[12:10] <systemclient> tumbleweed: or wait till 12.04?
[12:11] <tumbleweed> systemclient: you can do that too. But, we are only a few days into feature freeze. if it's a leaf package you'd like to see in oneiric, you can file a request
[12:12] <systemclient> tumbleweed: what is a leaf package? Nothing depends on it?
[12:12] <tumbleweed> yes
[12:13] <systemclient> that is the case … I'll look into sync requests tonight then
[12:13] <systemclient> thank you!
[12:20] <jtaylor> can someone set it to triaged? maybe also set importance: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/824734
[12:21] <Laney> jtaylor: please get bug control ;-)
[12:21] <Laney> what importance would you set?
[12:22] <jtaylor> as it affects some core components (update-manage) I#d say high
[12:22] <paultag> Yeah, I agree
[12:22] <paultag> it breaks unrelated software. Setting now
[12:23] <Laney> just testing
[12:23] <paultag> jtaylor: all set. Thanks for picking that one out :)
[12:23] <nigelb> jtaylor: I'd +1 Laney's suggestion. Please get bug control or alternatively MOTU :)
[12:24] <Laney> bug control should be much quicker
[12:24] <Laney> no reason to not get it based on some other pending application
[12:24] <paultag> yar, -bugs is fairly active
[12:24] <paultag> honestly I thought this was bugs until I checked
[12:24] <nigelb> heh
[13:43] <jtaylor> sent an application for bug control
[13:46] <nigelb> stuck in moderation, should come in, in a few
[14:26] <jtaylor> someone here a member of debian-gnome and can sponsor meld(exp)?
[14:26] <jtaylor> it ould allow fixing a bunch of ugly meld bugs in natty
[14:27] <Laney> have you pinged in there?
[14:27] <jtaylor> the debian maintainer did a couple fo times already
[14:29] <Laney> ok
[14:29] <Laney> i'll do it later
[14:29] <jtaylor> great thanks
[15:58] <hggdh> jtaylor: OK. You got the first +1 on -control ;-)
[16:36] <micahg> jtaylor: BTW, dev membership includes bug control :)
[17:07] <tumbleweed> so apply already
[17:10] <Laney> how can I tell svn-bp that I have an orig.tar.xz?
[17:10] <jtaylor> by patching it
[17:10] <jtaylor> meld was uploaded already
[17:10] <jtaylor> it wasn't you?
[17:11] <Laney> no
[17:11] <Laney> someone did it?
[17:11] <jtaylor> yes short while ago
[17:12] <Laney> fair
[17:12] <Laney> still, it needs patching to do that?
[17:12] <Laney> what a hunk
[17:12] <jtaylor> its easier to fix than pristine-tar needed for git-bp :/
[17:14] <Laney> pristine-tar: committed meld_1.5.2.orig.tar.xz.delta to branch pristine-tar
[17:14] <Laney> seems like the delta is the entire file
[17:15] <Laney> works though
[18:27] <tumbleweed> hrm, I notice ubuntu-sponsoring no longer things MOTUs can upload to universe
[18:27] <tumbleweed> thinks
[18:27] <tumbleweed> Laney: I wonder if that was due to going anonymous
[18:33] <micahg> tumbleweed: what do you mean?
[18:33] <tumbleweed> micahg: bold vs italic on the sponsorship overview
[18:34] <micahg> ah, yes, I noticed that
[18:42] <Laney> tumbleweed: why would it?
[18:42] <Laney> sounds like an api bug if so
[18:42] <Laney> can you run the method manually
[18:42] <Laney> ?
[18:42]  * Laney is cooking ATM, then DMB — sorry
[18:43] <Laney> it was a fairly uninvolved change from my side :P
[18:43] <geser> Laney: thanks for the reminder
[18:47] <Laney> heh heh
[18:47]  * Laney hopes maco and persia can make it too
[18:47] <paultag> I thought maco steped down from the DMB
[18:47] <paultag> thought I got an email about that
[18:48] <geser> paultag: she is
[18:48] <tumbleweed> Laney: yeah I should look at it properly too. I remember the api call being horrible (you determine True or false by whether you get an exception or not): P
[18:49] <geser> paultag: we hope she will be available till the vote for her replacement
[18:49] <paultag> geser: ah, right. CoC and all that
[18:51] <Laney> tumbleweed: actually I remember somethign weird about that call
[18:52] <Laney> perhaps it wasn't a function of the launchpad object?
[18:52] <tumbleweed> actually maybe that was the call as me. after supper...
[18:58] <geser> tumbleweed: it might be really that anon is not enough. If I did my quick api test correctly then distribution.main_archive.getPermissionsForPerson(person=person) returns an empty list which results in False for person_can_upload (assuming that the first part of function doesn't return anything)
[18:59] <Laney> why would that be?
[19:05] <geser> I didn't check each call of the function but IIRC the second part was needed too (I asked about it in the past when writing a similar function for requestsync)
[19:06] <tumbleweed> geser: this sounds like a bug in launchpad
[19:06] <tumbleweed> yeah I see the empty list vs populated list when logged in
[19:39] <paultag> Hey MOTU
[19:39] <paultag> does anyone remember what we did after warty warthog when the release name+1 was < then the stable release?
[19:40] <paultag> was there a massive debian-local version bump and rebuild or what?
[19:41] <paultag> e.g. package-1.0~warty1 > package-1.0~dapper1
[19:41]  * tumbleweed wasn't an ubuntu-user in those days, but was it such a big issue? Was the release name in many package versions?
[19:42] <Laney> I can only think of backports, and I'm not sure if that existed then
[19:42] <tumbleweed> well, people could use a release name in SRU versions too
[19:42] <ScottK> It was not part of the archive.  It was on sourceforge.
[19:42] <paultag> right
[19:42] <ScottK> (project is still there if you're interested in historical artifacts)
[19:43] <paultag> ScottK: do you seem to remember what was done for when this happend, or what the plan is post Zadjective Zanimal ?
[19:43] <ScottK> paultag: It was before my time (I started with Dapper).
[19:44] <paultag> Ah, I need someone from badger-era :)
[19:44] <paultag> humm. I'm betting good money Debian has to deal with this after wheezy
[19:44] <paultag> they append the version ID to migrations, I think
[19:45] <paultag> Oh wait, SRUs, right
[19:45] <micahg> well, they use versions in backports usually, not codenames
[19:45] <tumbleweed> paultag: even then it won't affect that many packages
[19:45] <tumbleweed> micahg: +squeeze1 is common for SPU (SRU in debian)
[19:45] <paultag> tumbleweed: well the changes would be pushed to unstable as well with a bump
[19:45] <paultag> even if it's a NMU it should work OK
[19:46] <micahg> tumbleweed: yes, but that packages is usually superceded in testing
[19:46] <tumbleweed> micahg: yes, and it'll only be an issue if it isn't
[19:47] <micahg> I would expect the stable release team in Debian to prevent such things from occuring :)
[19:53] <tumbleweed> you'll never have copy-up from spu to testing or tpu to unstable. The only way it could happen is if something was tpu-ed and never migrated from unstable again until the next release. not going to happen :)
[22:03]  * tumbleweed can't remember why I've got a netatalk beta in my ppa, but it seems to generate lots of e-mail from people to me, wanting new releases
[22:03] <tumbleweed> clearly they can't read the "This PPA is my personal play-ground, and full of weeds. Don't expect anything to not break your system or to still be here tomorrow."
[22:03] <ajmitch> it's not one of those things that you expect people to still be using these days
[22:04] <Laney> google for "$software ppa", add first result, ???, profit
[22:04] <Laney> second result in this instance (after the ubuntu +source page)
[22:05] <tumbleweed> Laney: hrm, that's probably it
[22:05] <tumbleweed> oh well I'll do a new upload then. /me pleases the anonymous masses
[22:05] <Laney> yeah, having (some) PPAs not be indexed by search engines would be good
[22:06] <ajmitch> I see that oneiric at least has a recent release of it
[22:06] <tumbleweed> apparently there's a 2.2 final release out
[22:07] <ajmitch> released only ~3 weeks ago, too
[22:07] <ajmitch> I didn't know anyone still cared about AFP
[23:19] <Laney> tumbleweed: there's a backport request for 2.2 final too
[23:19] <Laney> fancy it? :-)
[23:20] <broder> haha, i was just looking at that bug
[23:20] <tumbleweed> Laney: we'd have to get it into oneiric first
[23:20] <tumbleweed> broder: I was just about to ask you to review it :)
[23:20] <tumbleweed> broder: (err ubuntu-be--tools if that's what you were asking about)
[23:20] <Laney> yep
[23:21] <Laney> and before that, sid — right? :P
[23:21] <broder> tumbleweed: wait, huh? i was referring to the backport request
[23:21] <tumbleweed> Laney: ok, I got it to build with the addition of a patch called "compile-dammit"
[23:21] <tumbleweed> broder: I just fixed the backportpackage local dsc bug
[23:21] <tumbleweed> well, discovered I'd fixed it during debconf
[23:21] <broder> tumbleweed: +1
[23:22] <broder> i'll take a look
[23:22] <tumbleweed> Laney: so, sure, I'll give jonas my patches (which are all upstream bugs), and remind him that he has desparate users
[23:23] <Laney> excellent
[23:26] <broder> tumbleweed: where's the patch?
[23:28] <broder> tumbleweed: nvm, found it
[23:35] <tumbleweed> broder: ok, I'll merge it and upload to Debian
[23:46] <tumbleweed> Laney: aha "I found a link to your ubuntu repository on the ubuntu forum about Time Machine Backup with lion." That kind of thing gives google hints :)