[13:38] <beezly|work> Reported a bug some time ago, but not heard anything: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1288644 - I don't mind... it's pretty niche. Just wondered if I'd done it wrong!
[13:43] <rbasak> beezly: the report looks fine to me, though there are >200 untriaged bugs in the eglibc package at the moment.
[13:43] <rbasak> There's also the complication that eglibc is now glibc in Utopic.
[13:44]  * rbasak isn't exactly sure about the status of that move
[13:49] <beezly> rbasak: thanks :) just wanted to make sure I hadn't missed something. Yeah - i realised that it would probably go away when utopic gets released.
[13:50] <beezly> It's definitely specific to eglibc. I took a look at the code and it is a web of #ifdef's and goto's.
[15:22] <neupuceni> hi!
[15:22] <neupuceni> how can i do kernel bisection?
[15:22] <neupuceni> this is my problem
[15:22] <neupuceni> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334230
[20:06]  * RoyK wonders when someone will take care of this https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1171945
[20:09] <rbasak> RoyK: it doesn't sound trivial. Care to volunteer?
[20:13] <RoyK> rbasak: I've tried to dig into this myself, but I don't know upstart well enough
[20:31] <rbasak> RoyK: upstart really isn't that complicated, and it's very well documented too. Do you know about http://upstart.ubuntu.com/cookbook?
[20:31] <rbasak> RoyK: it's just a set of jobs that fire on events. Hardware hotplug (and simulated hotplug on boot) and jobs changing state fire events.
[20:31] <rbasak> That's about it really.
[20:38] <israel> Hi is anyone around that works with SRU?
[20:54] <RoyK> rbasak: just a bit strange that such a bug hasn't been fixed for so long
[20:58] <rbasak> RoyK: I guess it's just the usual - uncommon case with no able developers who are also willing to volunteer the time affected.
[20:58] <rbasak> (or to pay for a fix)
[21:05] <RoyK> rbasak: found the solution
[21:11] <israel> Hi is anyone around that works with SRU?
[21:12] <RoyK> rbasak: the final solution is simple - don't use ubuntu :P
[21:22] <yofel> israel: please just ask your question, someone else might be able to answer your question too
[21:31] <israel> I want to do SRU for a package.  I have a bug report, and a branch setup.  However the wiki page says to upload the package to proposed.... I am not sure how/if I can do this
[21:36] <yofel> israel: you'll need a developer that sponsors your upload, see https://wiki.ubuntu.com/SponsorshipProcess#Requesting_Sponsorship
[21:37] <yofel> israel: also see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure step 5
[21:47] <israel> yofel: thank you!  It is a separate package, rather than a patch, though.   Do I need to do a debdiff?  If so, where is the info on that?
[21:48] <israel> yofel: I found it in the sponsorship page...
[21:48] <yofel> if you're using UDD you can just do a merge request for the branch, debdiff would be the classic way and is generated with "debdiff <old_version>.dsc <new_version>.dsc"
[21:48] <yofel> :)
[21:49] <israel> oh... debdiff is very simple!   What is UDD?  sorry, I am not up on all the lingo :)
[21:49] <israel> Oh... you mean utopic?
[21:49] <israel> Can I merge the version in Utopic back to Trusty?
[21:52] <israel> yofel: this is for a program called lmms... I may have talked to you some time ago about it... your name seems familiar
[21:52] <yofel> no, UDD is the bzr based packaging style
[21:52] <yofel> (ubuntu distributed development)
[21:53] <israel> UDD... ok I have been using bzr and pbuilder, etc.. to do this since 11.10, or maybe 12.04 I can't remember when I started doing this.
[21:54] <yofel> israel: getting the utopic package to trusty is a backport and can be put into trusty-backports, SRU's have to be fixes for specific bugs
[21:56] <israel> yofel: The problem is feature freeze came, and we were frenzied trying to get it in past the freeze... when I accidentally merged the Master in, rather than the Stable.. so there are some unstable components and user data loss issues.  Both my version of 1.0.0 and the utopic 1.0.1 fix the bugs  Which would you recommend?  I really just want to fix my mistake quickly... so whichever one will work to get the users a safer more sta
[21:56] <israel> ble program is what I want to do
[22:02] <yofel> israel: hm, looks like a rather large update, but I would say request sponsorship anyway and then discuss it with the sponsor and ~ubuntu-sru
[22:04] <israel> yofel: There were some features that were not ready to use, so they all needed to be rolled back.  So you are saying I should use my branch, rather than the backport.  Thanks for your help!!
[22:13] <rbasak> RoyK: ah, so you can find some other edge case bug that only affects a small number of people on another distribution instead?
[22:13] <rbasak> :)
[22:17] <israel> rbasak: what is your problem?