[09:14] Hi all! I joined here hoping for some advice. We have a problem with the "picolisp" package in 12.04. It crashes whenever you try to load a dynamic library from it. This is fixed in picolisp upstream. [09:15] How to make picolisp work in 12.04? Bug is here https://bugs.launchpad.net/ubuntu/+source/picolisp/+bug/956731 [09:15] Launchpad bug 956731 in picolisp "PicoLisp upgrade" [Undecided,Confirmed] [09:15] * jakov notes that we have a very useful bot... [09:23] I also asked here http://askubuntu.com/questions/144052/how-to-file-a-bug-report-for-a-specific-ubuntu-release [09:47] Hi all [09:48] is somebody know how to create bug report about acpi in ubuntu ? [09:56] i've created launchpad account and ready to create bug report with workaround but tool "ubuntu-bug" doesn't have any options about kernel or acpi system, any advises? [10:19] anatrof, you'll find info about reporting acpi bugs at https://wiki.ubuntu.com/DebuggingACPI#Filing_a_Bug_Report [10:20] the package is linux [10:20] i know the problem and found related bug [10:21] and already got all info that you said [10:21] but don't know where to send [10:33] anatrof, attach your patch to the bug report or attach an LP branch with your patch, then you'll need to find a sponsor. Best bet for acpi is to ask on #ubuntu-kernel [10:33] there are guidelines on the sponsorship process at https://wiki.ubuntu.com/SponsorshipProcess === ara is now known as Guest64238 === jbicha is now known as Guest70781 === Guest70781 is now known as jbicha_ === elleuca_ is now known as Guest20629 === jacob_ is now known as jacob === Pici is now known as Guest55530 === Pici` is now known as Pici [17:22] anyone who has an in-depth understanding of the bugcontrol application process online? [17:25] TheLordOfTime: The application process is described here: https://wiki.ubuntu.com/UbuntuBugControl [17:25] roadmr: i know, but i have a very specific question not answered there :P [17:25] TheLordOfTime: oh! [17:26] hence the "in-depth understanding" part [17:26] TheLordOfTime: I suggest you just ask (unless it's something sensitive) and if someone know they'll answer [17:26] TheLordOfTime: I'd try to, but I'm on my way out (should be back in about an hour though) [17:28] roadmr: i'm already on bugcontrol for nginx, as i work upstream triaging bugs from Ubuntu to upstream and vice versa (where applicable). While that in theory gives me access to bugcontrol for everything (due to jcastro explaining the LP permissions limitations), should I still apply if i want to be able to have bugcontrol outside of `nginx`? And if so, is there a different application format/procedure? [17:29] TheLordOfTime: I see no application for you even for nginx, not sure how you were added [17:29] micahg: talked to jcastro directly [17:29] micahg: talk to him if you want. [17:29] or remove me from the access (either is fine, i've been planning applying anyways for global) [17:30] If you are an upstream developer or bug triager for an upstream project contact Jorge Castro <-- (from the bugcontrol page) [17:30] * micahg is not an admin [17:31] micahg: i'll poke jorge then (or rather you should and I should too) [17:31] AIUI, jcastro was supposed to help with the application/process for getting access, not just add people, but I could be wrong [17:31] * micahg wonders where hggdh is [17:33] hi! [17:33] jcastro: the micahg is questioning the bugcontrol for nginx which you gave me (lack of application) [17:33] s/the// [17:34] ok [17:34] TheLordOfTime: not exactly what I said :) [17:34] also gave it to mtecknology, so we're not sure where to go with this :P [17:34] I don't think I flipped it for mktechnology yet [17:34] I ran out of time [17:34] indeed, he's been poking me, but it may be prudent to address this prior to that [17:34] (and if need be, revoke my access) [17:35] micahg: yeah so basically when people work with upstream projects and show good work we can just add them [17:35] but if you don't like that we can remove it [17:35] jcastro: I thought there was still some notice sent by someone to let the group know to watch for them touching things they shouldn't be [17:35] which group? [17:35] jcastro: but I could be totally wrong about that [17:36] jcastro: bugcontrol [17:36] not really [17:36] micahg: shortly after jcastro poked me up to bugcontrol, i've had a few other bugs addressed here that were outside the nginx purview :P [17:36] * TheLordOfTime sticks to policies pretty closely [17:36] we tell the person the typical "great power, great responsibility" spiel [17:36] and tell them not to touch things they're not working on [17:36] since LP doesn't really ACL like that (still?) [17:36] (it SHOULD have better ACL) [17:36] TheLordOfTime: it's open source, have at it :) [17:37] micahg: kinda got my hands full with the ASP.NET from work :/ [17:37] (yes, i said ASP.NET, and I said work.) [17:38] speaking of which.. [17:38] * TheLordOfTime goes to the meeting he's 7 minutes late for [17:38] * micahg pretends that's a reference to mono and moves on [17:40] ok so no problem then? [17:41] apparently, they rescheduled the meeting and didn't tell me >.> [17:41] nope, just wanted you to explain for micah and I the circumstances and policies :P [17:41] jcastro: ^ [17:41] jcastro: I'd personally like there to be a paper trail of some sort (but if that's not how it's been, you don't have to remove the access) [17:41] * micahg will petition for that in a future meeting [17:42] micahg: for all intents and purposes, i agree a paper trail would be fine (although there's public logs of me and jcastro discussing this on the Ask ubuntu chat rooms) [17:42] * TheLordOfTime returns to being omnipresent but silent === yofel_ is now known as yofel === jbicha_ is now known as jbicha