[03:34] <darkangel> any 1 here know how to debug? i need help
[21:42] <smaudet> hello, I'm trying to figure out where to put a couple bugs I found with the rpcbind package? They are both in the upstart-job area, so I don't think it is a Debian level bug, but a Ubuntu package maintainer bug, am I correct? Should I just submit a diff of my file to the mailing list? Do I need to use bzr or can I just use dpkg to generate my diff? (I already have downloaded the official source package, I'm on Ubuntu 12.04.3 LTS)
[21:43] <smaudet> I have patches, so I don't just want to submit a bug, although I'm fine with doing that on launchpad as well.
[21:54] <Noskcaj> smaudet, use "ubuntu-bug PACKAGENAME"
[21:58] <smaudet> Noskcaj: thank you, with regards to submitting my patch what is the fastest way to go about this?
[21:59] <Noskcaj> attach the patch to the bug.
[22:00] <smaudet> Noskcaj: ok thank you
[22:00] <Noskcaj> no problem
[22:10] <smaudet> Noskcaj: how long should this process take? It appears the ubuntu-bug program is buggy - there's a window titled "Collecting Problem Information" that appears to have no insides, and its been nearly 10-20 minutes
[22:10] <smaudet> rpcbind is not a large program, as I said I've already download, inspected, and compiled the source, so I should know.
[22:11] <smaudet> I will kill the process and try again in another minute, however if this does not work, what would be the next best avenue to take?
[22:12] <penguin42> no, it should be nearly instant - maybe 30 seconds
[22:12] <Noskcaj> smaudet, if it's not working, try going to https://bugs.launchpad.net/ubuntu/+source/rpcbind/+filebug and attach any logs you think would be used
[22:16] <smaudet> penguin42: just buggy then, worked nearly instantly the second time around
[22:18] <smaudet> Great...ok... so ubuntu-bug worked this time, and then it opened up the wrong browser - I tried copy pasting the url to a different one and it told me invalid oped id transaction - am I going to be able to find the bug I just submitted again?
[22:19] <smaudet> I'm already logged in via my correct browser
[22:20] <Noskcaj> smaudet, Just try to put up with the different browser long enough to report the issue
[22:21] <smaudet> =/ I'm just going to uninstall it and submit again
[22:23] <Noskcaj> smaudet, The issue might have been that you haven't set the browser you use as the default
[22:24] <smaudet> Noskcaj: yes that is probably an issue, my defaults are all a mess - seperate issue for another time
[22:24] <Noskcaj> ok
[22:24] <smaudet> Noskcaj: I have like 5 or 6 different files all saying different things and needing to be updated, so its always russian roulette opening a browser
[22:25] <Noskcaj> lol
[22:25] <smaudet> What happens to defaults when the 'best answer' is to 'right click on it in nautilus' - worst answer there could possibly be actually
[22:29] <smaudet> That worked much better, came up as a notification instead :)
[22:29] <smaudet> Although I still have to figure out how to purge rekonq
[22:32] <Noskcaj> smaudet, "sudo apt-get purge reconq" ?
[22:41] <smaudet> Noskcaj: ran it, I'd have to submit the bug again to see if the conf went away, but its likely a conf issue outside of the package
[22:41] <smaudet> Noskcaj: and thanks for your help, new bug: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1222274
[22:41] <ubot2`> Launchpad bug 1222274 in rpcbind (Ubuntu) "Incorrect upstart-job configuration" [Undecided,New]
[22:42] <smaudet> Noskcaj: I have another bug to submit as well though on a different package so I'll see if rekonq went away yet
[22:42] <Noskcaj> ok
[22:43] <Noskcaj> If you want to try and get them fixed, it helps to see if they still happen on the latest development release. in this case 13.10
[22:43] <smaudet> Nope
[22:43] <smaudet> ?
[22:44] <smaudet> I did check whether the bugs were fixed in the latest branch on launchpad already
[22:44] <smaudet> And it didn't look like it.
[22:44] <Noskcaj> ok
[22:44] <smaudet> Will my patches still be usefull?
[22:44] <Noskcaj> smaudet, definitely. Just wait for someone add the patch
[22:44] <smaudet> :)
[22:45] <penguin42> smaudet: are the bugs ubuntu only bugs or upstream?
[22:45] <smaudet> penguin42: they are in the upstart configuration, so I believe that is Ubuntu only
[22:45] <smaudet> I don't think Debian has upstart-jobs?
[22:46] <smaudet> I did look inside the debian/control if that's what you're asking and it recommended that I mail ubuntu-devel-discuss@lists.ubuntu.com so I think that it is a downstream issue...
[22:46] <smaudet> If you can tell me otherwise I'll push the patch upstream
[22:46] <penguin42> ah, if it's actually upstart then yeh it'll be local
[22:47] <smaudet> There actually is a similar bug in Debian, but they are using init.d scripts, so I didn't think it applied
[22:48] <smaudet> Forgot to put that in the bug report, will edit it.
[22:49] <smaudet> updated