[08:34] <Ciemon> Is anyone creating patches in an amd64 environment?
[08:34] <Ciemon> I seem to be having real problems, and not having any success
[08:34] <ddecator> are you using quilt?
[08:35] <Ciemon> yes... at least, trying to
[08:35] <Ciemon> I'm a n00b, so learning too
[08:37] <nigelb> Ciemon, if you explain what you're trying to do, we could try to help you
[08:37] <ddecator> not sure if this should be done in #ubuntu-packaging or not
[08:37] <nigelb> I'd like to hear first and then decide :)
[08:38] <ddecator> fair enough =)
[08:42] <Ciemon> :) ok, stop me when you like
[08:43] <Ciemon> so, download the branch, move into the source root, and use "quilt push -a"
[08:43] <Ciemon> nothing applied, which could be fine, even though there are a number of diffs within debian/patches
[08:44] <Ciemon> quilt new "diffname.diff" doesn't do anything that I can see
[08:45] <nigelb> Ciemon, aha, you missed something quite important
[08:45] <nigelb> anyway lets head to #ubuntu-packaging
[08:45] <Ciemon> ok
[11:07] <BUGabundo> oias
[13:32] <nailora> could someone un-private this bug (of course only if applicable) https://bugs.launchpad.net/bugs/549655
[13:32] <ubot4> nailora: Error: Bug #549655 is private.
[13:34] <greg-g> nailora: looking at it
[13:35] <nailora> my bug got duplicated to it and my bug contains no private info imho
[13:35] <greg-g> nailora: it is now public
[13:35] <nailora> thx
[13:36] <greg-g> np
[13:36] <nigelb> the original bug contains no private data either
[13:36] <nigelb> oh.. greg-g you beat me to it :)
[13:40] <greg-g> nigelb: this time I tried to tell the channel I was looking at it ;)
[13:41] <nigelb> yeah, I sorta just jumped in :)
[15:52] <matttbe> Hello guys!
[15:52] <matttbe> I'm part of the Cairo-Dock team and I've added 'apport' support in 'cairo-dock' packages but when apport is used, all needed informations are located in a private bug report. So nobody of the 'cairo-dock-team' can't have a look to this private bug : e.g. bug #553265
[15:53] <matttbe> It seems that I've to join the Bug Squad team but is it the best solution?
[15:54] <greg-g> matttbe: well, best solution is subjective.. but, yeah, that is a feature of apport. Just in case there is private information in the bug report (passwords, etc) it is set as private until a trusted member of the QA team reviews it and opens it up. That process usually only takes about 2 minutes
[15:54] <hggdh> matttbe: the basic issue is we do not know, a priori, if there is sensitive data in an apport bug
[15:55] <greg-g> usually, when someone comes in here and asks to have a bug marked public, one of us gets to it pretty quickly
[15:55] <greg-g> *usually*
[15:55] <matttbe> ok
[15:56] <hggdh> one *possible* option is to subscribe the cairo-dock team to the bugs
[15:56] <matttbe> it's done
[15:56] <hggdh> then you should have access to them
[15:57] <hggdh> can you give us a bug # where this does not happen?
[15:57] <matttbe> https://bugs.launchpad.net/bugs/539889
[15:57] <ubot4> Launchpad bug 539889 in cairo-dock (Ubuntu) "cairo-dock crashed with SIGSEGV in cairo_dock_initialize_opengl_backend() (affects: 2) (dups: 1) (heat: 170)" [Medium,New]
[15:57]  * persia recently made that public based on request in -motu
[15:57] <matttbe> I can access to this bug https://bugs.launchpad.net/ubuntu/+source/cairo-dock/+bug/553265
[15:57] <ubot4> Launchpad bug 553265 in cairo-dock (Ubuntu) "cairo-dock crashed with SIGSEGV in cairo_dock_initialize_opengl_backend() (dup-of: 539889)" [Undecided,New]
[15:58] <matttbe> but all needed informations are located in the other bug :)
[15:58] <hggdh> not a very good example, persia had just made it public...
[15:58] <matttbe> ah :)
[15:58] <matttbe> thanks persia ;)
[15:58] <mrand> On this topic, where are the subscribers for an apport report configured?
[15:58] <charlie-tca> Most of the private bugs do not subscribe the team
[15:58] <persia> But it *was* private, and the cairo-dock team *wasn't* subscribed.
[15:58] <charlie-tca> see bug 553238
[15:59] <ubot4> charlie-tca: Bug 553238 on http://launchpad.net/bugs/553238 is private
[15:59] <matttbe> I can't access to charlie-tca's bug
[15:59] <charlie-tca> it's private
[15:59] <matttbe> but it's normal :)
[16:00] <bencrisford> pedro_: i saw the email about the notifications bugday, hopefully we can arrange it so that the edubuntu day doesnt interfere with it
[16:00] <matttbe> *unexceptional
[16:00] <charlie-tca> private bugs now subscribe apport, crash bug triage team, and the reporter only
[16:00] <bencrisford> pedro_: we could maybe host it mainly on #edubuntu
[16:00] <charlie-tca> After they become public, the rest of the teams and subscribers are assigned to it
[16:00] <mrand> charlie-tca: what is supposed to crash bug triage team?
[16:00] <charlie-tca> I have no idea
[16:01] <hggdh> yes, the apport bugs are pre-subscribed to crash-bug-triagers
[16:01] <persia> I have a suspicion that this is hardcoded behaviour
[16:01] <hggdh> after apport ends its magic, all others get it also. But until then, usually only apport and crash-bug-triagers
[16:01] <mrand> ugg, really?
[16:01] <pedro_> bencrisford, Hello! here is fine i think, there's not a lot of bugs on indicator applet anyways
[16:01] <hggdh> persia: AFAICR, yes, it is
[16:02] <hggdh> matttbe: members of bug-control (*not* bugsquad) are also members of crash-bug-triagers
[16:02] <pedro_> bencrisford, also we want to have more folks joining the edubuntu triage day it's better to keep the ball rolling where almost all the bugsquad members are chatting ;-)
[16:02] <bencrisford> pedro_: ok :), it could even benefit our days, we could encourage each others participants to maybe help out with a couple of the other sides bugs
[16:02] <pedro_> bencrisford, yes yes yes ;-)
[16:03] <bencrisford> :)
[16:03] <hggdh> matttbe: are you upstream for cairo?
[16:03] <matttbe> hggdh: yes
[16:03] <matttbe> hggdh: https://code.launchpad.net/~ubuntu-branches/ubuntu/lucid/cairo-dock-plug-ins/lucid
[16:04] <mrand> Ok, it appears that apport retracer, when it comes to visit a bug, subscribes the crash-bug-triagers.   But that is actually bad, because if the person that opened the ticket removes the apport tag, the bug will sit there, private, forever, and even the bug control team can't access it.
[16:05] <matttbe> (but we have to change the maintainer, I will do that for the next release)
[16:08] <hggdh> mrand: there is this risk, yes. But we cannot allow blanket access
[16:09] <mrand> hggdh: I was actually thinking that apport, as it opens the bug, should subscribe the team, not wait until the retracer comes along.
[16:10] <matttbe> mrand: why not adding a line in the apport script in order to subscribe somebody or a team?
[16:11] <hggdh> matttbe: as upstream, you are entitle to a shortcut to the bug-control team (which will give you access to these bugs)
[16:11] <hggdh> matttbe: I have to ask you a few questions, though. Please bear with me
[16:12] <matttbe> mmh ok :)
[16:13] <hggdh> matttbe: (1) have you read https://wiki.ubuntu.com/UbuntuBugControl ?
[16:13] <matttbe> not yet
[16:13] <hggdh> matttbe: please do so ;-)
[16:14] <matttbe> oh yes but a long time ago :), let me read it again
[16:16] <matttbe> ok, done (sorry, there are a lot of links :) )
[16:17] <hggdh> matttbe: do you agree to follow the rules of the game?
[16:18] <matttbe> which game ? :)
[16:18] <matttbe> but yes
[16:19] <matttbe> I've signed the code of conduct and it's not the first time that I use Launchpad for bugs tracking ;)
[16:19] <hggdh> matttbe: thank you. We are adding you as a member to bug-control. If there are other persons (also upstream) to cairo-* that wish to join, please have them ping us here
[16:19] <hggdh> mrand: crash-bug-triagers get subscribed as soon as the bug is opened
[16:20] <matttbe> thank you hggdh !
[16:20] <hggdh> matttbe: you are weolcome, and thank you for helping!
[16:20] <matttbe> I'll send a message to the other member (but the main devs of cairo-dock is on vacation ^^)
[16:21] <hggdh> matttbe: no prob, we are usually here ;-)
[16:21] <matttbe> :)
[16:21] <hggdh> merci beaucoup
[16:22] <matttbe> merci à toi ;)
[16:22] <mrand> hggdh: I would have thought that, but I've seen mythtv package bugs where that didn't seem to be the case :-(
[16:23] <hggdh> mrand: hum. The fine details of apport magic are unknown to me...
[16:23] <Tofe> hi !
[16:25] <Tofe> I'm a developer in the Cairo-dock team, and (as mattbe told you just some seconds ago) I would like to have access to private bug reports... Would it be possible ?
[16:26] <hggdh> Tofe: welcome. Have you read https://wiki.ubuntu.com/UbuntuBugControl ?
[16:26] <hggdh> Tofe: also, have you signed the CoC?
[16:27] <Tofe> not yet: I'll do that right away.
[16:30] <Tofe> for the CoC, yes, I signed it some time ago
[16:40] <Tofe> Ok, done. But, unfortunately, I didn't triage yet any bug; is that a problem, knowing that I'm only really interested in the cairo-dock private bug reports ?
[16:40] <Tofe> (I do some triage for my job, but well, it doesn't have anything to do with ubuntu/launchpad)
[16:43] <hggdh> Tofe: no, it does not apply to you since you are upstream
[16:44] <hggdh> Tofe: what is your LP id?
[16:44] <Tofe> chris-chapuis
[16:50] <hggdh> Tofe: welcome in, then. Thank you for helping!
[16:51] <Tofe> :) my pleasure
[17:38] <nigelb> hggdh, bug 553745 looks okay to be made public?
[17:38] <ubot4> nigelb: Bug 553745 on http://launchpad.net/bugs/553745 is private
[17:45] <mrand> nigelb: have you looked over the attachments for personal info?
[17:46] <hggdh> looking
[17:46] <nigelb> mrand, in one glance I didn't find any
[17:46] <yofel> nigelb: I can't find anything
[17:46] <nigelb> yofel, I didn't either, but I just wanted to be sure :)
[17:47] <mrand> nigelb: I didn't find anything either.  have fun with it!
[17:47] <nigelb> mrand, hehe :)
[17:47] <hggdh> neither did I ;-)
[18:01] <Chris_S> Question: what's the right place to report an apparent problem with security.ubuntu.com itself (as opposed to, say, apt-get)? Is this closest to a support request instead of an Ubuntu bug?
[18:04] <nigelb> Chris_S, easy way would be to tell someone from security team
[18:04] <nigelb> Chris_S, #ubuntu-hardened would be the way to go :)
[18:04] <hggdh> Chris_S: #ubuntu-hardened
[18:05] <hggdh> heh
[18:05] <yofel> hm, does anyone know for who that 'redirect to the bug filing help page from LP' is turned off for? (more like, is it turned off for the bugsquad too or just for bugcontrol?)
[18:05] <nigelb> its turned off for no one right?
[18:06] <yofel> nigelb: If I click on the 'report a bug' link on lp.net/ubuntu I don't get redirected
[18:06] <nigelb> strange
[18:06]  * nigelb checks
[18:07] <Chris_S> Ah, thanks everyone. Let me try that.
[18:09] <nigelb> yofel, ack, I dont get redirected.  so someone from bug squad needs to check
[18:10] <nigelb> yofel, bug control and above doesn't get re-directed
[18:10] <yofel> ah, thanks
[19:19] <bencrisford> !info ubiquity
[19:19] <ubot4> bencrisford: ubiquity (source: ubiquity): Ubuntu live CD installer. In component main, is optional. Version 2.0.10 (karmic), package size 3509 kB, installed size 12428 kB
[19:25] <bencrisford> !info lupin
[19:25] <ubot4> bencrisford: Package lupin does not exist in karmic
[19:26] <bencrisford> !info lupin hardy
[19:26] <ubot4> bencrisford: Package lupin does not exist in hardy
[19:33] <yofel> bencrisford: why don't you just use apt-cache and rmadison ?
[19:35] <bencrisford> yofel: i couldnt remember any cmds for searching packages.  ive been using arch for a few months, in which i could just use pacman -Ss
[19:36] <bencrisford> i havent quite got back into ubuntu mode yet
[19:36] <yofel> heh
[19:36] <bencrisford> but thank you, ill use them instead of spamming the channel next time ;)
[19:36] <mrand> packages.ubuntu.com is what I often use.
[19:36] <yofel> apt-cache is for querying the package database, and rmadison lists the package version in all available releases
[22:08] <danage> JFo: i need a quick clarification on your mail (thank you) re: bug #452519. i've collected and sent the requested information. your mail also asked for feedback on a newer kernel version. i've tested 2.6.33-020633-generic from the mainline ppa which exhibits the same faulty behavior. 2.6.34-rc1 is giving me a kernel panic on boot, the newer rcs seem to be for karmic only (not lucid beta) so i didn't test. would 2.6.33 suffice for our purposes?
[22:08] <ubot4> Launchpad bug 452519 in linux (Ubuntu) "[Karmic] USB Card Reader Malfunction - clutter in DMESG (affects: 9) (heat: 48)" [Undecided,Incomplete] https://launchpad.net/bugs/452519
[22:12] <charlie-tca> yes, it should. also note in the comments that 34-rc1 is giving you a kernel panic
[22:13] <charlie-tca> danage: Thank you for doing that
[22:14] <danage> charlie-tca: ok thank you for the quick reply. i'm thus removing the needs-upstream-testing tag. should i go ahead and remove the one about the kernel logs as well (as apport seems to have provided those)?
[22:14] <charlie-tca> yup
[22:15] <charlie-tca> looks like they are there now
[22:16] <danage> ok done. charlie-tca thanks for helping me, and JFo thanks for the mail.
[22:17] <charlie-tca> Thanks for helping make things better
[22:33] <BUGabundo> boas noites o/
[23:30] <Daniturn> Launchpad bug 555807 in linux "cant use wireless card" [Undecided,New] https://launchpad.net/bugs/555807
[23:30] <ubot4> Daniturn: Bug 555807 on http://launchpad.net/bugs/555807 is private
[23:30] <ubot4> Launchpad bug 555807 in linux (Ubuntu) "cant use wireless card (affects: 1)" [Undecided,New]
[23:34] <gnomefreak> Daniturn: you need to ask a question or make a comment or something dont just post the bug number and hope p[oeple know what you are refering to or what you are thinking. as i said comment on the bug to make us help you more. i left a comment for you please comment on bug about it