[10:51] <caribou> Hi, I'm working on the following bug : https://bugs.launchpad.net/ubuntu/+source/dante/+bug/857598
[10:51] <ubot2`> Ubuntu bug 857598 in dante (Ubuntu) "socksify fails to run" [Undecided,In progress]
[10:52] <caribou> I would need a task for precise as I will also propose a fix for precise as part of another bug I'm working on
[10:54] <caribou> I have also taken the liberty to switch it to In Progress as I've assigned myself to it
[10:54] <caribou> not sure if it  was to proper thing to do
[10:55] <jibel> caribou, done and assigned to you
[10:55] <caribou> jibel: merci
[10:55] <jibel> caribou, if you're working on it in progress is the right status
[10:56] <caribou> jibel: that's what I thought
[10:56] <jibel> for reference https://wiki.ubuntu.com/Bugs/Status
[14:18] <caribou> What should I do if I have a debdiff that fixes two separate bugs ?
[14:18] <caribou> attach it to both bugs ?
[20:00] <phillw> Hi good people, can someone check out bug 1200304 and get any private data removed so that it can be made public.
[20:00] <phillw> The request comes from the OP
[20:14] <jtaylor> op can make it public himself
[20:15] <jtaylor> and I think he can also read and remove his own data
[20:15] <TheLordOfTime> ^ that
[20:16] <TheLordOfTime> phillw:  ^
[20:16] <phillw> jtaylor: I'll ask that he does.
[20:16] <jtaylor> strangely I can't even see the bug
[20:17] <TheLordOfTime> jtaylor:  nor I which is suspicious
[20:17] <TheLordOfTime> or suggests something broke
[20:17] <TheLordOfTime> or maybe its one of the packages or projects bugcontrol doesn't have access to
[20:17] <hggdh> not really. It all depends on how the bug was opened, and against what
[20:17] <hggdh> ^
[20:17]  * TheLordOfTime shrugs
[20:18] <hggdh> anyway, phillw ^ we cannot see it
[20:18] <TheLordOfTime> so the OP will have to remove the data, or wait until someone who can see it can get to it
[20:18] <hggdh> yep
[20:18] <TheLordOfTime> hmmmmmmmmmmm
[20:18]  * TheLordOfTime checks something
[20:19] <phillw> I've asked the OP to mark it as public, but I'm a little concerned that in doing so, it could reveal private information that should not be made public before having such data removed....
[20:19] <TheLordOfTime> phillw:  he should go through the data and remove it himself
[20:19] <phillw> He is a tester, not a programmer!
[20:19] <TheLordOfTime> hehe
[20:20] <hggdh> phillw: it might, indeed. But since we cannot see it -- not even to know what is in there --, there is not much we can do. If you could find from the OP what he opened the bug against, we then could find who would have access
[20:20] <TheLordOfTime> mhm
[20:21] <hggdh> like, opened against upstream as opposed to an Ubuntu package, marked the bug as a security issue (which means only the security team can see it), etc
[20:22] <TheLordOfTime> yep
[20:23] <phillw> I've copied this chat to the OP, not too sure which time zone he is on, so I will await a reply. Thanks for your help.
[20:25] <hggdh> phillw: glad to help, even if we did not actually helped...
[20:25] <hggdh> oh, bad tense. Ah well. It is Friday.
[20:27] <TheLordOfTime> hggdh:  you're excused :)
[20:28] <phillw> hopefully the grammer nazis are jumping off cliffs :P
[20:28] <TheLordOfTime> phillw:  i'm a grammar nazi usually
[20:28] <TheLordOfTime> but i'm just as bad typing from a phone
[20:28] <TheLordOfTime> :/
[20:35] <hggdh> TheLordOfTime: since it is Friday, you should have said "... excuset", or something like it. So that I would not feel alone, and all that :-)
[20:35] <TheLordOfTime> :P
[20:36] <TheLordOfTime> hggdh:  autocorrect on the iOS is decent at doing its actual jonbn
[20:36] <TheLordOfTime> job*
[20:36] <hggdh> TheLordOfTime: THANK YOU!
[20:36]  * hggdh now has company
[20:36] <TheLordOfTime> :P
[20:37]  * TheLordOfTime goes back to figuring out an FTBFS problem in non-Ubuntu software.
[20:49] <phillw> the bug is against lightdm
[21:03] <hggdh> phillw: not lightdm(Ubuntu), but just lightdm, right?
[21:03] <TheLordOfTime> hggdh:  is it against "lightdm (Ubuntu)"  or just the lightdm project
[21:03] <TheLordOfTime> because if it's the second of those i don't think bugcontrol has access
[21:03] <phillw> hggdh: lightdm(Ubuntu)
[21:04] <hggdh> then it was probably masked as a security bug
[21:04] <TheLordOfTime> ehh whatever i was going to say is bleh
[21:04] <TheLordOfTime> that's probably it then
[21:04] <hggdh> cuz otherwise we would have access to it
[21:04] <TheLordOfTime> private security i think needs sec team
[21:04] <TheLordOfTime> security*
[21:04] <hggdh> yes. They are the only ones that can see them
[21:05] <phillw> the screen shot is at http://imagebin.org/264322
[21:06] <hggdh> phillw: oh, OK, it is a crash. Only apport retracing has access to it right now
[21:06] <phillw> who are they? :)
[21:06] <hggdh> phillw: others will only have access *after* initial apport processing
[21:07] <hggdh> phillw: they who?
[21:07] <phillw> apport retracing
[21:07] <hggdh> phillw: when a crash bug is opened, the bug is restricted -- the presence of a coredump is more than enough to make it restricted
[21:08] <phillw> So, what advice should I give to the OP?
[21:08] <hggdh> so only an internal back-office process -- the apport retracing utility -- has access to the bug. When the retracing is done, the coredump is deleted, and the bug is accessible for some
[21:09] <hggdh> phillw: tell him/her to please wait. The bug should NOT be made public right now
[21:09] <phillw> okies, again - thanks
[21:09] <hggdh> phillw: after we have the retracing done, we can look at it, and see if it is good to be public
[23:08] <phillw> TheLordOfTime: could you have a read of a new section https://wiki.ubuntu.com/QATeam/Overview#My_bug_is_marked_private to see if it is factually correct, thanks.
[23:09] <TheLordOfTime> phillw:  someone else can, I'm busy atm yelling at PayPal
[23:09] <phillw> okies!
[23:10] <pleia2> phillw: have a moment for a quick PM?
[23:10] <phillw> Hi, can someone from bug-squad check on if https://wiki.ubuntu.com/QATeam/Overview#My_bug_is_marked_private is factually correct, i
[23:10] <phillw> pleia2: always :)