[01:00] <fully_human> Sorry, I keep forgetting (and keep forgetting to bookmark) the page with the ubuntu dev releases. What is it? Thanks.
[01:04] <Unit193> https://cdimage.ubuntu.com/ ?
[01:05] <fully_human> Unit193, Ah, thanks!
[01:05] <fully_human> Although, https:// seems to be down. :-\
[01:06] <Unit193> Bah. :/  I just typed https out of habit.
[01:07] <fully_human> Unit193, Good habit. :-)
[01:07] <Unit193> Danke.
[15:08] <ESphynx> Hey guys, is anyone maintaining GDB here? I got some non-sense going on
[15:09] <ESphynx> Looks like GDB gets stuck in startup_inferior()->target_wait ()->sigsuspend() ?
[18:26] <jtaylor> meh, tried to finally install trusty on my machine
[18:26] <jtaylor> and guess what, it again deadlocks on detecting partitions :(
[18:26] <teward> jtaylor, and?  (purely curious)
[18:26] <teward> ouch
[18:26] <jtaylor> its getting annoying that this reappears every cycle
[18:28] <jtaylor> its not helping that the detection is so slow, you have to let it sit for 10 minutes to make sure its deadlocked and not just slow :/
[21:09] <fully_human> Hello, trying to submit my first bug patch...So far I'm two days in trying to submit a two-second patch. :-\ I've finally gotten to submittodebian. I had to cancel and fix something, and now submittodebian won't work. It says "dpkg-source: error: cannot read foo/debian/patches/bar: No such file or directory" (where foo is package name and bar is my `bzr branch` name). I didn't get this error before when I was going thro
[21:09] <fully_human> ugh all the steps. Is there any way to "undo" submittodebian steps?  Thanks.
[21:13] <Noskcaj> fully_human, I normally just make the bug in debian via email and attach the patch, fairly simple
[21:13] <teward> same here
[21:14] <fully_human> Make the bug?
[21:14] <fully_human> Oh, reproduce?
[21:15] <teward> i think Noskcaj means file a new bug in Debian via email, if one doesn't already exist
[21:15] <Noskcaj> yeah
[21:16] <teward> or, email bugnumber@bugs.debian.org with a message and attach the patch as an attachment, if the bug DOES exist.
[21:16] <fully_human> No, one exists. I'm just fixing it. I'm following this guide: http://packaging.ubuntu.com/html/fixing-a-bug-example.html
[21:16] <teward> fully_human, do you have the Debian bug number?
[21:16] <fully_human> I have the launchpad bug number. :-\
[21:16] <teward> i'm confused then
[21:16] <teward> you're trying to attach the patch to the LP bug?
[21:17] <fully_human> Yes.
[21:17] <teward> fully_human, do you have the patch on the system you're opening the bug in?
[21:17] <teward> (i.e. the same system you're opening launchpad.net on)
[21:18] <teward> if you do, then you can just open the bug, hit "Add attachment or patch" at the bottom of the bug
[21:18] <teward> put some description in, and a title for it, and attach the file
[21:18] <fully_human> teward, Ah, thanks.
[21:18] <teward> fully_human, you're welcome.
[21:18] <fully_human> What file extension would the patch be? (this is my first bug fix, so sorry for all the newbie questions)
[21:19] <teward> fully_human, i usually use .diff or .patch or .debdiff, depending on the patch.
[21:19] <teward> normally, when I patch things with JUST a patch, I also generate a debdiff, as a power user / SRUer, so mine're usually .debdiff (and the file is created in the debdiff for the patch)
[21:20] <teward> but for JUST a patch or a diff, you can probably use .patch or .diff
[21:20] <teward> Noskcaj might have more guidance than me on that, though.
[21:20] <teward> (I also ahve to fix my debian repo system >.>)
[21:20] <fully_human> I don't see any of those...I must be missing a step...Should I do `debdiff > packagename.patch`?
[21:20] <teward> fully_human, how'd you create the patch?
[21:21] <teward> ... oh THAT'S why my repositories are broke >.>
[21:21]  * teward kicks the system around angrily
[21:22] <fully_human> Actually, I might not have. Sorry for the confusion. I did `bzr branch name-of-bug`, and then `dch -i` Do have to manually create the patch file with bzr diff?
[21:22] <teward> Noskcaj, ^
[21:22]  * teward doesn't use bzr so can't really help there
[21:22]  * fully_human considers teward blessed.
[21:22] <teward> heheheheheh
[21:22] <teward> nah, i just prefer making my life harder xD
[21:25] <fully_human> But do I have to manually do a `bzr diff foo >> foo.patch?`
[21:26] <teward> fully_human, i'll be honest, though, my job's harder, a lot of times I"m doing the opposite of what you're doing, I"m usually taking upstream diffs and applying them to the older versions in ubuntu for SRUs or security updates xD
[21:26] <teward> but i'm sorry i can't give you guidance on this issue :/
[21:26]  * teward disappears to reset his debian repository server
[21:26] <fully_human> teward, No problem. :-)
[21:51] <teward> can someone help me out with getting this bug ready for SRU by approving the nomination for Saucy?  https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1264674
[21:51] <teward> (it's already fixed in Trusty, hence fix released, but it needs fixing in Saucy)
[22:19] <rbasak> teward: done. Thanks!
[23:03] <Noskcaj> fully_human, What was the issue you had? I was afk
[23:05] <ESphynx> hey guys I'm suspecting a kernel bug preventing me to debug my apps at all on latest Saucy kernel... Is there an easy to test installing a newer kernel on Saucy? I tried adding this PPA but now I can't figure out how to install it...
[23:05] <ESphynx> (Said PPA https://launchpad.net/~anton50489/+archive/test2/+build/ )
[23:10] <ESphynx> Or is this http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-saucy/ what I should use