[03:14] <RAOF> pochu: What, if anything, are you doing about bug #274485?  Do we know whether a simple rebuild of anjunta and python-gnome2-extras will strip the libgdl-gnome dependency, or whether we need to reinstate the libgdl-gnome package?
[03:17]  * RAOF gardens that bug.
[05:46] <dholbach> good morning
[06:20] <didrocks> good morning o/
[06:22] <dholbach> didrocks: I uploaded g-s-t - it's in the queue right now
[06:25] <didrocks> dholbach: thanks a lot! Was your bug jam interesting? :)
[06:25] <didrocks> (I reckon, yes, as usual ;))
[06:26] <dholbach> it was great, we had around 15 people there, almost all pretty new to bug triage, so we didn't get a lot of bugs done, but everybody left very excited for the next jam :)
[06:26] <dholbach> so I'd say "a success"
[06:26] <dholbach> I'll blog about it in a bit
[06:26] <iulian> G'morning.
[06:28] <didrocks> dholbach: that's good news! I'll experienced an internal bug jam party in the « Ubuntu Party » for the next release (2 days event)
[06:28] <dholbach> 2 days of bug jam?
[06:31] <didrocks> dholbach: no, the party (conferences, install party, open talks, demos, beginner courses) will length 2 days. We have planned to make two bug jams (one each day), for a limited time, more to find/teach new bug triagers
[06:31] <dholbach> nice
[06:32] <dholbach> that sounds great
[06:32] <didrocks> hope it will ^^
[06:36] <geser> good morning
[06:38] <dholbach> hi geser!
[06:38] <geser> hi dholbach
[07:02] <LucidFox> doko, are you here?
[08:19] <iulian> I'm looking for someone to ack bug 274276.
[08:19] <iulian> I'd be more than happy to see this uploaded as the current version is pretty useless.
[09:25] <huats> morning everyone
[09:31] <dholbach> hi huats
[09:32] <huats> hey dholbach
[09:32] <huats> :)
[09:32] <huats> how are you ?
[09:32] <dholbach> good good - how 'bout you?
[09:32] <huats> great too
[09:32] <huats> I am just returning from an Open Source event in paris
[09:32] <huats> it was nice to see all that known faces :)
[09:33] <directhex> yeah, but french people? :o
[09:33] <huats> (vuntz, nijaba, didrocks and more :)
[09:33] <huats> sure....
[09:33] <dholbach> cool
[09:33] <huats> directhex: sure french people, but since I am also french :)
[09:33] <directhex> tsk!
[09:33] <didrocks> yep ^^
[09:34] <directhex> they let anyone work on software these days...
[09:34] <didrocks> directhex: :p
[09:36] <directhex> coo, new stable rockbox release. i'll update from my svn build
[09:43] <dholbach> \sh: are you going to take care of bug 239734?
[09:48] <POX> a propos sync requests: is anyone using SQLAlchemy here? If yes, you probably want to sync 0.4.7p1-2 from Debian (Ubuntu has 0.4.6-1), I don't have time right now to check if it works on Ubuntu (it should, I didn't change that much in the package)
[09:50] <directhex> feature freeze is in effect. is it a bugfix-only release?
[10:17] <POX> directhex: well, it's new upstream but it's mostly bugfix release (+few minor features backported from 0.5 which is currently in experimental)
[10:20] <POX> here's (very detailed) upstream changelog: http://www.sqlalchemy.org/trac/browser/sqlalchemy/tags/rel_0_4_7p1/CHANGES, my changes are
[10:20] <POX> in debian/changelog
[10:21] <POX> http://packages.debian.org/changelogs/pool/main/s/sqlalchemy/sqlalchemy_0.4.7p1-2/changelog.html
[10:47] <rulus> If someone has time for a small upload, I just filed bug #274722. It's a bugfix only release, so I don't think this needs a FFe?
[10:48] <Laney> rulus: It might be nice to say that it is bugfix only (and paste the upstream changelog) in the bug to help the sponsors
[10:49] <rulus> ah, sure, I'll change it :)
[10:56] <zorglu_> q. what is the status of vlc 0.9 on hardy ?
[10:56] <zorglu_> any motumedia around ?
[11:02] <persia> zorglu_: There was an FFe for 0.9.2, which I think I heard was approved.  I've seen traffic implying the bugfixes from 0.9.3 are expected to be included, but I'm not sure what the version string will show.
[11:24] <zorglu_> persia: what FFe mean ?
[11:25] <persia> zorglu_: Feature Freeze Exception
[11:25] <zorglu_> persia: ?? for hardy ?
[11:25] <persia> For intrepid.
[11:25] <persia> FOr hardy, I thought the plan was to stick with 0.8.x.x
[11:25] <persia> For hardy-backports, I've heard nothing.
[11:25] <zorglu_> persia: ok :) and for hardy ?
[11:25] <zorglu_> persia: hmmm ok
[11:25] <Laney> zorglu_: There's a bug on hardy-backports but I think it was rejected as the dependencies can't be satisfied
[11:26] <zorglu_> so i will have to run vlc in a VM in my servers :)
[11:26] <persia> zorglu_: There's no point looking for hardy-backports until it's in intrepid anyway.
[11:26] <zorglu_> persia: ok thanks
[11:26] <persia> Laney: Oh, did that already happen?  Thanks.
[11:26] <Laney> persia: The Intrepid upload did, yes
[11:26] <zorglu_> Laney: ok
[11:27] <persia> Laney: I meant the -backports discussion, but that too :)
[11:27] <Laney> Well, yes, both did ;)
[11:28] <Laney> bug #274399
[11:40] <pochu> RAOF: huats is working on it. I think we need to disable gdl support somewhere
[11:41] <huats> I am working on something :)
[11:41] <huats> pochu: I'll have a look after...
[11:41] <huats> I am finishing anjuta first
[11:42] <pochu> huats: sure
[11:43] <pochu> huats: RAOF: I think eliminating libgdl-1-dev from gnome-python-extras' build-depends will solve it
[11:54] <directhex> O_o @ user on launchpad answers correcting me
[11:54] <directhex> i'm pretty sure a package I got into intrepid is X version, not the Y version you claim, y'know!
[13:28] <directhex> someone's been smoking too much crack: https://answers.launchpad.net/ubuntu/+source/mono/+question/44628
[13:29] <bobbo> Adri2000: ping
[13:30] <laga> directhex: rotfl
[13:30] <directhex> this is what i get for getting involved in Answers
[13:31] <Adri2000> bobbo: pong
[13:32] <bobbo> Adri2000: what were your concerns about the mpd merge?
[13:36] <Adri2000> bobbo: just that you mention it fixes a segfault bug, whereas your merge only changes the init script
[13:36] <bobbo> Adri2000: ah, sorry, i meant to get rid of that one, thanks for reminding me :)
[13:38] <directhex> laga, hit f5 ¬_¬
[13:54] <laga> directhex: hahaha
[13:54] <laga> that's priceless
[14:46] <bddebian> Heya gang
[14:56] <kirkland> procedural question on a package that just got it's second +1 in REVU this morning....
[14:56] <kirkland> am i correct in assuming it's too late to add it to the universe archive for intrepid?
[14:56] <kirkland> since we're in beta freeze?
[14:56] <geser> Hi bddebian
[14:57] <dholbach> kirkland: https://wiki.ubuntu.com/FeatureFreezeException
[14:57] <geser> kirkland: yes, unless you have an exception
[14:57] <geser> kirkland: that's already since FF not just since beta freeze
[14:57] <dholbach> excusez-moi... https://wiki.ubuntu.com/FeatureFreeze
[14:57] <dholbach> arg
[14:57] <dholbach> https://wiki.ubuntu.com/FreezeExceptionProcess
[14:58] <kirkland> geser: dholbach: okay, i don't think this will get a FFe, so is it just a matter of waiting until the archive reopens?
[14:58] <dholbach> kirkland: yeah and chaging "intrepid" to "jaunty"
[14:58] <kirkland> dholbach: ah, good call ;-)
[15:12] <bddebian> Heya geser
[15:23] <superm1> persia, have you been experimenting much with that bluez-gnome 0.28 package off of that ppa?
[15:24] <persia> superm1: I have been.  It works for comms, but I've not been able to get it to work with a keyboard (but I can't get my keyboard to work with 0.25 either).
[15:25] <persia> I've also been working with crevette to look at the fedora patches, etc. and try to get all the fixes together in one upload.  I'm just *very* fearful of regresion for people with bluetooth keyboards and mice.
[15:25] <superm1> persia, have you tried a mouse?
[15:25] <persia> I don't have a bluetooth mouse.
[15:25] <superm1> persia, i've gotten it to work with a mouse at least
[15:25] <superm1> persia, i'll have to get some more batteries to experiment with a keyboard
[15:25] <persia> You have!  That's excellent news.
[15:26] <persia> Could you report that it works with a mouse in the bug?  That ought be enough we can ask for an upload.
[15:26] <superm1> what's the bug number again, do you know off hand?
[15:26] <persia> I'd really like to see 0.28 in beta if we're going to ship it in intrepid.
[15:26] <persia> I think it's the right thing to do anyway, because we'll surely be looking at BlueZ 4 for jaunty.
[15:26] <superm1> most definitely.
[15:26] <directhex> i'd like to see monodoc 1.9, but sometimes life just doesn't go the right way
[15:27] <superm1> i wanted to get mterry's patch for the nice pairing wizard too, but it didn't work properly when i rebased it to 0.28
[15:27] <persia> But it works for 0.25?
[15:27] <superm1> it works for what was in hardy. lets see what that was
[15:28] <superm1> 0.25 it looks like i suppose yeah
[15:28] <superm1> we're past UI freeze though
[15:28] <persia> superm1: Well, which do you think is the better route?
[15:29] <superm1> persia, that's a tough question, but i suppose since things appear broke right now, either are feasible solutions
[15:30] <superm1> mterry, would you be able to look at the rebase on 0.28 i did (attached to your bug) and see if anything stands out about it?
[15:30] <persia> superm1: Right.  I know 0.28 contains lots of bugfixes, but the UI leaves something to be desired.
[15:30] <superm1> ideally doing 0.28 + that patch would be the best solution
[15:31] <persia> Indeed.  Maybe 0.28 RSN, and the patch in a couple days?
[15:31] <mterry> superm1: Yeah, OK.
[15:34] <mterry> superm1: In what way doesn't it work on 0.28?
[15:34] <superm1> mterry, the UI froze up when i tried to pair
[15:35] <mterry> superm1: Guh, OK
[15:38] <salutis> hello all, I have big problem - recently I moved my packages from my own server to ubuntu's PPA at launchpad. and now I can't build my packages anymore. I placed my log at 'http://www.salutis.sk/ppa-log.txt'. can anyone please help me? thanks!
[15:38] <persia> Oh, and it's bug #256994
[15:38] <superm1> persia, yeah i just found it and responded :)
[15:43] <geser> salutis: the build target is always run as non-root on the buildds, just remove the dh_testroot from the build target and it should get farther
[15:43] <rizobs> join irc.esylum.net #bishes-chat type !rizobs for access to our pre-channel & fast bots
[15:43] <rizobs> join irc.esylum.net #bishes-chat type !rizobs for access to our pre-channel & fast bots
[15:43] <rizobs> join irc.esylum.net #bishes-chat type !rizobs for access to our pre-channel & fast bots
[15:43] <directhex> fascinating ¬_¬
[15:44] <salutis> ﻿geser: aha!
[15:44] <StevenK> Heh, I was about to call the ops
[15:44] <StevenK> And then they left
[15:44] <salutis> geser: I will try
[15:44] <directhex> i'm asking a freenode staffer to intervene
[15:48] <directhex> laga, f5!
[15:49] <sistpoty|work> hi folks
[15:50] <Hobbsee> sigh
[15:50] <directhex> something amiss?
[15:50] <Hobbsee> rozobs
[15:50] <Hobbsee> er, rizobs
[15:51] <directhex> it appears my pet freenode staffer is MIA. so anyone wants to get the ip something-lined needs to follow conventional channels
[15:54] <Hobbsee> directhex: not much point - nothing on that ip's on freenode now anwyay
[15:54] <directhex> bleh
[15:54] <Hobbsee> sending 240v down there might be more effective, though.
[15:54] <directhex> 415 do you?
[15:55] <Hobbsee> sounds good.
[15:55] <directhex> did you get a chance to read my wonderful and life-changing blog entry then? \o/
[16:53] <superm1> persia, i just verified with hardy and intrepid on live usb keys that keyboard pairing is not sticking with intrepid - either 0.25 or 0.28
[16:53] <superm1> persia, but it works with hardy
[16:54] <superm1> so i'd be inclined to believe it's caused by something different
[16:54] <persia> superm1: That was my experience.  So, 0.28 isn't a regression, but it's broken for some other reason?
[16:54] <superm1> persia, it "pairs" in the UI, and shows that it connects/disconnects, but doesnt work
[16:54] <superm1> right
[16:54] <persia> Right.  I think it's something with Xinput2 hotplug, but haven't figured out what.
[16:55] <persia> I can force the pairing in intrepid with bluez-utils (no need for bluez-gnome), but I can't make it work in X.
[16:55] <iulian> Hi
[16:55] <superm1> have you looked if hal starts to see the devices in either case?
[16:55] <superm1> hardy or intrepid
[16:55] <persia> No :)
[16:55]  * persia adds that to the list of things to do soonish like.
[16:55] <superm1> okay well i'm booted into hardy right now, and it does show up in lshal
[16:56] <superm1> so there's a first data point
[17:00] <mterry> superm1: I tried 0.28 with your bluetooth patch (on a hardy machine, so perhaps invalid test), and I successfully connected/used a mouse and headphone with the wizard
[17:00] <persia> mterry: That's excellent news.  I think you've demonstrated that bluez-gnome 0.28 isn't the source of the issue.
[17:02] <superm1> mterry, interesting.  i'm wondering what the UI timeouts could have been on this end.  persia and i will get back to that patch after we get keyboards working in intrepid
[17:19] <persia> superm1: It's showing in gnome-device-manager for me, but oddly my keyboard is considered a "pointing device".  It also automatically disconnects without having done anything.  This is 0.25 in intrepid.
[17:30] <pochu> why is ~motu a subteam of ~universe-contributors?
[17:39] <pochu> re
[17:39] <pochu> my question still stands :-)
[17:39]  * sistpoty|work heads home... cya
[17:41] <persia> pochu: because all MOTU are also universe contributors.
[17:42] <persia> OK.  A little history:
[17:42] <persia> First, MOTU granted membership.  Then MC asked CC for the right to separate MOTUship and Membership, and CC asked for the creation of UC.  MOTU is now part of UC to gain membership.
[17:43] <persia> (and maybe I forgot to press some buttons in LP, but that's the idea)
[17:49] <pochu> persia: so ~motu is no longer a subteam of ~ubuntumembers, so ~motu has to be a subteam of ~u-c to be a subteam of ~ubuntumembers?
[17:49] <persia> pochu: At least that's the idea.  I don't remember if I pressed all the right buttons.
[17:50] <pochu> ok
[17:50] <persia> (and if I haven't, I'm a little fearful of accidentally breaking some developers @ubuntu.com)
[17:50] <pochu> I just wondered because I started to see MOTUs with the u-c icon
[18:00] <superm1> persia, well it's not generating an input device in dmesg or /sys like it should
[18:00] <superm1> at least for me
[18:00] <superm1> an important data point is that in intrepid we are using the new "btusb" driver
[18:00] <persia> superm1: How about a new entry in /dev/input/ or something with lsinput?
[18:00] <persia> That is an important data point.
[18:00] <superm1> persia, not for me at least
[18:00] <superm1> the older driver is available in the kernel still, but you cant have them both compiled side by side
[18:01] <persia> using bluez-gnome. or bluez-utils?
[18:01] <superm1> i've been using the gnome applet
[18:01] <superm1> hidd isn't supported upstream so i dont use it ever
[18:01] <persia> I can't get bluez-gnome to connect at all, but have limited success with bluez-utils.
[18:01] <persia> Ah.  hidd is kinda working for me.  I get the input device, I just can't use it.
[18:02] <superm1> persia, from some searches i'm finding that people are running into troubles with suspend/resume on btusb too
[18:02] <superm1> there is a patchset sitting on bluez.org at least for suspend/resume, but it's not in linus' tree yet
[18:02] <superm1> so i'm thinking at this point, we need to compile the hci_usb driver again, and test with it
[18:02] <superm1> if things are sane with it, we should just not go out the door with btusb
[18:02] <superm1> wait for it to stabilize before making the switch
[18:03] <persia> That sounds like a good plan.  I'm not so good with drivers, but I'm happy to be a tester.
[18:04] <superm1> persia, lets pop in #ubuntu-kernel and see if we can just get one of them to put out a kernel on a ppa w/ hci-usb instead
[18:08] <superm1> mterry, regarding your patch not working on intrepid, i suspect it's due to newer bluez-utils.  the patch times out regarding services (which i'd imagine was meaning dbus services).
[18:09] <persia> And the newer bluez-utils fixes a *large* number of connectivity bugs with symbian devices, so we don't want to revert that.
[18:12] <superm1> well is there a way to look at the registered dbus services?
[18:12] <superm1> an equivalent to lshal in dbus form
[18:13] <persia> dbus-monitor may help.
[18:14] <mterry> superm1: OK, I'll update my bluez-utils
[18:16]  * persia wonders what the GNOME equivalent to kdbus might be
[18:20] <sebner> huhu persia :)
[18:35] <superm1> persia, http://people.atrpms.net/~mlimonciello/hci_usb.tar.gz
[18:35] <superm1> grab that, install kernel headers and type make
[18:36] <superm1> you should get an hci_usb.ko  that you can experiment with
[18:36] <superm1> i pulled it out of the 2.6.27 tree and adjusted header inclusions to let it compile
[18:38] <persia> superm1: OK.  Then I just modprobe -r btusb, and mobprobe hci-usb?
[18:38] <superm1> theoretically
[18:39] <superm1> i couldnt rmmod btusb
[18:39] <superm1> and it makes it difficult to blacklist it when i'm operating off a usb key
[18:39] <superm1> and it wont modprobe unless you drop it somewhere in /lib/modules/`uname -r` and depmod -a
[18:39] <superm1> you'll have to insmod ./hci_usb.ko instead
[18:40] <sebner> persia: I think I already asked you but is bug #261986 valid to pass it to the archive admins?
[18:41] <persia> OK.  insmod isn't an issue, and I've a proper install.
[18:43] <persia> sebner: It was when it was acked.  I'm not sure about it now: it would need a review to see if it requires an FFe.
[18:43] <sebner> persia: I'll subscribe u-u-s then?
[18:44] <persia> sebner: No.  It has all the uus stuff done.  It just might need an FFe.  If it doesn't, you can subscribe the archive-admins.  If it does, you need to fill in the details, and subscribe motu-release.
[18:45] <sebner> persia: well, you said it needs a review. by me or do you refer to a MOTU?
[18:45] <persia> sebner: By someone.  You'd probably be a good person.
[18:46] <sebner> persia: ^^, what points do I have to mind?
[18:47] <persia> sebner: That we're in FeatureFreeze, UI Freeze, and Beta Freeze.  It needs to fix bugs, and not break anything.
[18:48] <sebner> persia: well, we have no open bugs in ubuntu but I'll take a deeper look at it
[18:50] <persia> sebner: Right.  It ought to have been subscribed to the archive admins a month ago.  This is probably my fault.
[18:50] <sebner> persia: of course it's yours :P but nvm. ;)
[18:57] <sebner> persia: bah ... UI changes. Seems not that worth it at this time of release cycle
[18:57] <persia> sebner: Sorry :(
[18:58] <pochu> who moderates ubuntu-motu-mentors@ ?
[18:58] <sebner> persia: I don't use it and so far no one complained that we have this old version so please don't worry. I also could have asked you earlier :)
[18:58] <pochu> norsetto: ping, do you moderate ubuntu-motu-mentors@ ?
[19:15] <persia> superm1: As I'm testing this, I'm reminded of the massive package split.  Do we want to do some recommending whilst we're looking around at this?
[19:16] <superm1> recommending of which?
[19:16] <persia> bluez-input, bluez-network, etc.
[19:17] <superm1> persia, latest bluez-utils should have recommends fixed
[19:17] <superm1> persia, 3.36-1ubuntu2
[19:17]  * persia upgrades *everything*
[19:23] <superm1> persia, considering the quite broken state of things, i'm not sure it should be entirely out of the question to switch to the 4.x series if these problems are solved
[19:24] <persia> Last I heard 4.x wasn't in great shape either, but having buggy beta software that might get fixed might be better than having buggy stable software that won't get fixed.
[19:25] <superm1> yeah that's exactly what my thought process was
[19:25] <persia> That said, I was getting useful stuff out of hci_usb.  I'm just waiting for update-manager to catch up (this was a fresh install of an image from the 23rd), and will fiddle.
[19:26] <persia> If we can fix this with a kernel driver selection change, that seems the better choice to me.
[19:26] <superm1> right
[19:26] <persia> (and I'm very happy, as I've spent the last week kicking myself trying to figure out how to connect to the keyboard: at least now I know it's broken)
[19:27] <superm1> persia, well i'm glad this is getting caught now, 8.04 went out with keyboard support that timed out after 30 minutes
[19:27] <superm1> we tracked down a patch that made it into 8.04.1 luckily
[19:28] <persia> Actually, credit belongs to slytherin and crevette who have been chasing this for the past month.  That's why we have such a good candidate available for 0.28
[19:28] <persia> My initial impulse to upgrade was just for version tweaking, which is why I gave up so easily when we hit FF.
[19:30] <superm1> interesting thing i'm reading in the changelog is that authentication and encryption for HID devices doesn't show up until bluez 4.6.  i wonder what the 3.x series was even doing then
[19:35] <persia> broadcasting
[19:37] <superm1> ah that's quite reassuring...
[19:37] <superm1> but you're probably right
[19:41] <persia> OK.  All upgraded.  All the services present.  No passkey input,  Authentication fails.
[19:42] <persia> So, hci_usb gives me the same results as btusb
[19:42] <superm1> it comes up behind the window sometimes
[19:42] <superm1> and you also sometimes need to enter your passkey on the keyboard first (even though it doesnt tell you)
[19:43] <persia> Tried both of those options.  No luck
[19:44] <persia> So, what's next?  Package and patch 4.x in a PPA?
[19:44] <superm1> ugh it's gonna be a big effort to do this package
[19:44]  * persia expects it needs a *lot* of testing to be included.
[19:44] <superm1> bluez-utils + bluez-libs == bluez now
[19:44] <superm1> so NEW source package
[19:44] <superm1> w/ a proper libbluetooth and bluez binary package
[19:44] <persia> Yeah, it's very much not to be taken lightly.
[19:45] <superm1> for now, i say lets put 0.28 in the archive
[19:45] <superm1> to make beta
[19:45] <superm1> and have broken keyboard
[19:45] <persia> As much as anything the interesting question is: can this be fixed.
[19:45] <superm1> its an improvement over the current situation
[19:45] <persia> Under the assumption that a keyboard is broken anyway?
[19:45] <superm1> well under the assumption that 0.28 didn't make it worse
[19:45] <persia> OK.  I'm good for that.
[19:46] <superm1> which it didn't since mterry tested 0.28 on hardy and was able to use it fine
[19:46] <persia> Right, and 0.28 + the new fedora patches do fix a number of outstanding issues.
[19:46] <superm1> i wonder if the debian bluetooth team started doing 4.x already
[19:46] <superm1> if so that, might help out a little here
[19:46] <superm1> at least on alioth
[19:48] <persia> Maybe.  Last I chatted with them (August) they were sitting on 0.27 for lenny, working on other stuff, and planning to look at 4.x for squeeze.
[19:48] <norsetto> pochu: no
[19:49] <superm1> looking at their svn on alioth i dont see any indications that they've started 4.x packaging
[19:49] <pochu> norsetto: ok. do you know who moderates it?
[19:49] <persia> Nope.  Looks like work in experimental on bluez-utils 3.36
[19:50] <norsetto> pochu: no idea, perhaps dholbach
[19:50] <superm1> well i was hoping they did the packaging and didnt upload it to anything yet
[19:50] <superm1> i know teams in debian that like to do that
[19:50] <superm1> during freezes
[19:50] <pochu> norsetto: ok, thanks
[19:51] <persia> No.  filippo specifically wanted to do something else.  Too bad he got stuck cherrypicking stuff.
[19:51] <norsetto> pochu: here: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu-mentors (dholbach, soren, nixternal)
[19:56] <pochu> norsetto: thanks!
[19:56] <norsetto> pochu: de nada
[19:57] <pochu> soren, nixternal: "supravat paul" in ubuntu-motu-mentors@ is asking for a moderation...
[20:02] <persia> superm1: Did you havea  version of mterry's patch that applied against crevette's 0.28 snapshot?  Do you want to add an updated debdiff to bug #256994 including that, and we can get someone to upload?
[20:03] <superm1> persia, mterry's patch doesn't work against the current dbus services i think.  go without it for now
[20:03] <superm1> persia, it'd need some more testing anyhow
[20:04] <persia> OK.  I'll poke crevette to get a final debdiff up, and try to get a sponsor then.  Do you know if we need ubuntu-release approval before or after sponsoring?
[20:04] <superm1> persia, so the existing diffs that were ready for 0.28 should be sufficient
[20:04] <superm1> persia, should need it before sponsoring
[20:05] <soren> pochu: Nothing in the moderation queue.. Maybe someone beat me to it.
[20:05] <persia> Right.  I'm to bed, but I'll add the diffs, etc. tomorrow if someone doesn't get to it whilst I sleep, and push to the release team.
[20:07] <superm1> persia, okay sounds good.  i'll take a look at how bad doing 4.x will be packaging wise, but no guarantees
[20:08] <persia> superm1: Understood.  Given the number of screaming intrepid testers complaining that bluetooth is terribly broken, I'm not sure it's worth going for the upgrade unless you run into a bunch of time.
[20:08] <persia> I'd rather explain it's not working because it's not 4.x than that it's not working because we don't want to cherrypick anymore.
[20:09] <persia> Mind you, if there were lots of people making noise, I'd probably not have that opinion.
[20:09] <superm1> persia, well unfortunately i have 2x BT keyboards at home, and i was planning upgrading to intrepid soon :)
[20:09] <persia> superm1: Oh.  Well.  Now you have an incentive to upgrade earlier in the cycle :)
[20:10] <superm1> persia, both have fglrx, so aint gonna happen yet :)
[20:10] <persia> Ooooh.  Those might just be good candidates to help troubleshoot the 8.04 -> 10.04 upgrade with 8.04 -> 9.04.
[20:11] <persia> Anyway, in the interests of completing freeze exception documentation sooner, I depart.
[20:11] <superm1> okay g'night
[20:13] <pochu> soren: I mean, he's sent 7 messages with "Help" as subject asking for help on installing things, and someone already asked him to use ubuntu-users@
[20:14] <pochu> soren: so it's rather the opposite, stop him from being able to post to the list (without reviewing by an admin, not neccessarily a ban)
[20:37] <directhex> it might be soon to guess, but roughly when is jaunty feature freeze gonna be?
[20:38] <pochu> directhex: likely in February
[20:41] <directhex> pochu, i'm smiling sweetly at upstream & asking them to port some code to use a lib in main instead of one in universe
[20:44] <pochu> directhex: to which upstream?
[20:46] <directhex> pochu, mono. the final relevant ubuntu patch, post-intrepid, is some mangling of dependencies to not depends: on gda2, and suggests: on it instead
[21:29] <directhex> laga, still got that window open? f5 power!
[21:33] <laga> directhex: great :)
[21:45] <directhex> laga, after all that, surprise surprise, i knew what the caress i'm talking about
[22:44] <superm1> persia, well i've got 4.x packaged.. the UI is a significant improvement at least
[23:39] <directhex> laga, that guy gets more & more epic :|
[23:41] <wgrant> Which guy?
[23:43] <directhex> wgrant, someone on answers is arguing with me that intrepid has mono 2.0
[23:44] <stgraber>       mono | 1.2.6+dfsg-6ubuntu3 |         hardy | source
[23:44] <stgraber>       mono | 1.9.1+dfsg-3ubuntu2 |      intrepid | source
[23:44] <directhex> stgraber, it's wrong. intrepid has 2.0. apparently.
[23:44] <stgraber> that's what is currently in the archive
[23:45] <stgraber> rmadison never lies
[23:45] <directhex> stgraber, it's wrong. intrepid has 2.0. apparently.
[23:45] <stgraber> well, I'm on intrepid right now
[23:45] <stgraber> stgraber@castiana:~$ mono -V
[23:45] <stgraber> Mono JIT compiler version 1.9.1 (tarball)
[23:45] <stgraber> Copyright (C) 2002-2007 Novell, Inc and Contributors. www.mono-project.com
[23:45] <directhex> if someone was ignoring pkg-mono@alioth and packaging mono independently, i'd have heard the screams of anguish, tbh
[23:46] <directhex> i'd also be administering slaps for ignoring a cross-distro active co-maintainer team
[23:46] <slangasek> see, it says right here in the copyright line - intrepid has all the 2.0 versions of mono between 2.0.02 and 2.0.07

[23:46] <directhex> slangasek, i think it's because some packages have 2.0 in the name
[23:46] <directhex> slangasek, you know, the way they have since mono 1.1.8.1 back in 2005
[23:47] <stgraber> yeah, we have packages for mono with .net 2.0
[23:47] <stgraber> it's not mono 2.0 :)
[23:48] <stgraber> so from my point of view, it's fine to have packages like mono-2.0-devel as their descriptions are correct "Mono development tools for CLI 2.0"
[23:50] <directhex> mono 2.0 packages will appear when the package transition work is done
[23:50] <directhex> which is pretty much waiting on lenny
[23:51] <directhex> so fingers crossed for swift release from debian, since the 2.0 transition will shrink the ubuntu livecd by tens of megs