[00:17] ahhh my pillow called... she wants me back. see you tomorrow µfriends [00:18] good night, BUGabundo [02:16] hmm.. thats pretty fail, when you dist upgrade to maverick.. it says welcome to ubuntu 10.10! then underneath it it says.. Welcome to Ubuntu 10.04.1! [02:17] so which is it? :P [02:28] whats the name of the program which is supposed to update the login banner? [02:29] ahh /etc/motd [02:31] https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/400462 [02:31] Launchpad bug 400462 in update-motd (Ubuntu) "package update-motd (not installed) failed to install/upgrade: no package named `update-motd' is installed, cannot configure (affects: 36) (dups: 5) (heat: 9)" [High,Fix released] [02:48] can someone explain to me how to get the fixed version of update-motd for maverick? [02:49] on the launchpad bug page, it says it was fixed in version 3.4-0ubuntu1 [02:50] but the version that comes with maverick is 3.5-0ubuntu1 [02:55] oh i see the problem.. its a regression that hasn't been reported yet :| [03:40] where the fuck did the fucking update-motd script go? :P [03:40] i want a god damned refund ;) [03:40] !ohmy | snadge [03:40] snadge: Please remember that all Ubuntu IRC channels share the same attitude of providing friendly and polite interaction with all users of all ages and cultures. Basically, this means no foul language and no abuse towards others. [03:42] i consider myself a reasonably advanced linux user of so many years.. and between launchpad, google, and trying to figure things out for myself.. im kind of blank here [03:42] whenever i run into a problem, i never get as far as actually being able to identify it and fix it.. its so annoying :P [05:06] https://bugs.launchpad.net/ubuntu/+source/php-memcached/+bug/658939 does that have enough information? [05:06] Launchpad bug 658939 in php-memcached (Ubuntu) "php5-memcached does not work (affects: 1) (heat: 6)" [Undecided,New] [05:48] Hello [05:48] Can someone help me with a bug report? I found the procedure online to follow [05:48] but this 'feature' is causing ubuntu to completely crash and log me out [05:50] hmm.... [05:51] anyone around? [05:55] lou1234: ubuntu-bug is crashing? [06:02] no [06:03] when i try to reproduce the bug [06:03] ubuntu [06:03] completely crashes and logs me out [06:05] sorry I am completely new to the bug reporting game. should I still try ubuntu bug? [06:06] lou1234: which package is crashing the system? [06:06] so when i open up a pdf [06:06] in firefox [06:06] and then try to print it [06:06] ubuntu completely crashes [06:07] I have the samsung universal print driver installed for my laser printer [06:07] so I am not sure where the problem is [06:07] lou1234: maybe try ubuntu-bug xorg [06:07] When you say "ubuntu completely crashes", could you describe that in a bit more detail? [06:08] Sure. I select print and then a box pops up I select print and then my screen goes black and goes to the login menu [06:08] I login and every window I had opened is closed [06:09] it is like a clean login when I restart firefox it comes up with the 'uh oh' firefox crashed screen and wants to restore tabs [06:09] Oh, excellent. That is an xorg crash. [06:09] oh [06:09] * lou1234 has no idea what it is [06:09] `ubuntu-bug xorg` and answer the questions and you'll file the right sort of bug. [06:10] micahg, What made you know it was xorg that I missed? [06:10] persia: Ubuntu completely crashed implied it, we've had a few of those submissions for Firefox, I'm looking for the bug now [06:11] micahg has this been an issue in 10.10 or has it been there previously? [06:11] bug 539772 [06:11] Launchpad bug 539772 in xorg-server (Ubuntu Maverick) (and 3 other projects) "[MASTER] Lucid 2.6.32-16 crashed to login screen - miCopyRegion (affects: 48) (dups: 22) (heat: 290)" [High,Fix released] https://launchpad.net/bugs/539772 [06:12] micahg, Ah, I see. I'm just never sure if it's xorg or kernel for "completely crashed". [06:12] (depending on the defintion of "completely) [06:12] lou1234: can you please file a new bug with ubuntu-bug xorg and mention that bug number I just put in the channel? [06:13] sure! [06:13] lou1234: thanks [06:13] so im reading the reporting bugs page... [06:13] lou1234: BTW, just out of curiosity, what type of video card do you have? [06:13] do i need to do any more research or is that it? [06:13] one sec [06:13] let me get the model number [06:14] lou1234: brand is sufficient in this case [06:14] ati radeon hd 4670 [06:14] ah, yes, ok [06:15] is this a security vulnerability? [06:16] Likely only in the denial-of-service sense, and even then, with easy workarounds, so probably not. [06:16] lou1234: probably not [06:16] oh okay ... im still reading the page [06:19] what exactly are gdm log files ... and is there a way i can view what information it contains? [06:21] /var/log/gdm/* [06:21] Should be text files: so use your favorite test reader [06:22] im in /var/log [06:22] and when I try to cd/gdm it says permission denied... when I try sudo cd/gdm I'm getting told cd command not found [06:25] any idea what I am doing wrong? [06:27] lou1234: cd gdm? [06:27] although that shouldn't work... [06:27] lou1234: try ls /var/log/gdm [06:28] Only root can see those logs. [06:28] `sudo ls /var/log/gdm` and similar [06:29] right [06:29] basically i just don't want my username posted out there [06:29] so if there is a quick way for me to edit that out [06:30] i would have no problem handing the logs out to help peeps with this bug [06:34] lou1234, If your username is "wakk0", you've already indicated that in a public manner. If not, feel free to edit the logs to claim it is :) [06:34] haha [06:35] fair enough [07:00] If I am doing a backtrace do I need to completely backout of the bug report - do the backtrace and then refile it? [07:01] No. [07:01] You can attach the stacktrace to the bug later. [07:02] oh ok [07:02] does this title work - firefox causes xorg to crash [07:03] I'd recommend something involving the printing action. [07:03] Once the PDF is open, firefox is no longer the primary application. [07:04] oh [07:22] now that i submitted it do i need to do anything else? [07:28] Wait, mostly. [07:29] Ideally, someone will either find a solution or ask for more information. [07:35] if they ask for more info [07:36] will i get an email? [07:36] If LP has your email address, you ought, yes. [07:38] LP? [07:38] oh nevermind [07:38] okay [07:38] thanks for all of the help! [07:38] have a good one! [07:38] bye bye! === AbhiJit_ is now known as AbhiJit [09:31] i'm looking for an issue in which a dist-upgrade kills the window decorator task resulting in a dialogue being in the background that cannot be brought to the front, thus failing the dist-upgrade process. i've searched launchpad and didn't fint it [10:55] persia: I see you're in a helpful mood this morning with regards to bugs :) [10:56] persia: any chance someone (anyone) could tell me how we get bug 619663 as an SRU for maverick? basically dual screen on intel is broken, fixed in xorg-edgers. [10:56] Launchpad bug 619663 in libdrm (Ubuntu) (and 2 other projects) "[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor (affects: 28) (dups: 6) (heat: 172)" [High,Fix committed] https://launchpad.net/bugs/619663 [10:56] debdiff available too https://bugs.edge.launchpad.net/ubuntu/+source/libdrm/+bug/619663/+attachment/1679043/+files/libdrm_2.4.21-1ubuntu2.1.debdiff [10:57] Launchpad bug 619663 in libdrm (Ubuntu) (and 2 other projects) "[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor (affects: 28) (dups: 6) (heat: 172)" [High,Fix committed] [10:58] that would be helpful to resolve, that's been quite a keen one in #ubuntu recently [10:58] Anyone tested the debdiff? [10:59] Ah, yes, it is tested. [11:00] OK. Bug needs to be subscribed to the sponsors team (ubuntu-sponsors). [11:00] Someone needs to upload it (who can upload X) [11:00] then it goes into -proposed, and we need folk both affected and unaffected to try it to verify it fixes the issue and doesn't cause regressions. [11:00] If that's true, it drops into -updates in about a week. [11:06] should I be looking for someone who can upload to x ? [11:06] That's what subscribing "ubuntu-sponsors" does. I can do the subscription if you don't want. [11:07] ah [11:07] There's a report generated every few minutes based on all the bugs that are subscribed to sponsors (which are supposed to have debdiffs), and developers are encouraged to review that, and sponsor some fixes for stuff they can upload regularly. [11:09] popey, So, I'm kinda blind to how opaque all these processes are, as I'm intimately involved in many of them. Do you think it's worth trying to prepare some guidance on how to get things moving from the viewpoint of someone less familiar? I imagine it would help you, but, as ikonia mentioned elsewhere, also reduces the bar for folks to maybe push things that aren't ready. [11:10] popey: I would be happy to help you with that [11:11] yes [11:11] i have found that some bugs I can "fire and forget" such as those relating to CUPS [11:11] Till is massively _on_ the ball there [11:12] whereas others, X, kernel, nautilus.. I can file a bug and see no action other than a bugsquad person pasting a boilerplate repy [11:12] *reply [11:12] I can hang out in channels and poke people, but that's suboptimal, doesn't scale and places more 'importance' on 'my' bugs relative to other peoples who dont have direct access to developers [11:12] that burns me [11:14] is there currently a guide/process/work-flow for bugsuad members on dealing with a bug ? [11:17] Hi ikonia. Here are some of the pages that are useful when triaging bugs [11:17] BugSquad : https://wiki.ubuntu.com/BugSquad [11:17] How To Triage https://wiki.ubuntu.com/Bugs/HowToTriage [11:17] Common Tasks : https://wiki.ubuntu.com/Bugs/CommonTasks [11:18] responses https://wiki.ubuntu.com/Bugs/Responses [11:18] Checklist https://wiki.ubuntu.com/Bugs/Checklist [11:18] nice [11:18] thanks [11:18] Be sure you have a Launchpad account [11:18] I do [11:18] I just want to read what the process is [11:19] I also suggest watching this video tutorial: Bug Triage 101 http://blip.tv/file/3219368 [11:19] always work a look [11:20] :-) [11:20] popey, Till is an example of the sort of monomanaically-focused developer that gets as close to "maintainer" as we have :) [11:21] ikonia, I'm happy to be a counterparty to be asked questions for any process/procedure that's tricky over the bug management/development range, the more so if the result is a document that is useful to people who aren't me. [11:33] well thats the game, get a process in place that allows people to contribute, but also puts some form of quality control in place [11:33] and also makes sure the bugs are filled with useful information and the correct status [11:35] Yep :) [11:38] bug controllers, bug #659075 is a wishlist [11:38] Launchpad bug 659075 in libaugeas-ruby (Ubuntu) "Please backport 'clear' into lucid - puppet claims support for it (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/659075 [11:40] is there a bug status for wishlist or request ? [11:41] ikonia: 'wishlist' is a value for importance [11:42] ah [11:43] only members of bug-control team can change it, so I am requesting them [11:44] mistrynitesh, It5's not wishlist: it's filed against the wrong project. [11:44] needs to be filed against the lucid-backports project. [11:45] https://bugs.launchpad.net/lucid-backports [11:45] :S oh, ok [11:47] what should be done for Bug #659074 , it is written in polish and the reporter asks to speak Polish :( [11:47] Launchpad bug 659074 in firefox (Ubuntu) "margorlik@gmail.cm (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/659074 [11:51] mistrynitesh, We usually turn those into questions (in polish), hoping the support team can file a bug on their behalf. [11:51] mistrynitesh, if you happen to know polish, or can understand the bug without further coordination with the submitter, may as well just translate the bug, and move forward towards resolution. [11:53] persia: I had no idea what it meant. Just found it was polish by trial at translate.google.com 8-) [11:53] If you're up for it, maybe grab someone in #ubuntu-pl to help integrate with the local support team. [11:54] I suspect that they have a procedure (I know there is one for a few other LoCo support teams) to handle these, and if we align with it, we'll provide best service for the user. [11:54] hmmm will check out [11:54] I guarantee there is at least one person in #ubuntu-pl able to communicate in English (as it is a requirement to set up the channels properly with the LoCo Council), although they may not be online at the moment. [12:02] persia: is there something by the name of lucid-backports? Nearest search I could find was ubuntu-ruby-backports-ppa [12:03] https://bugs.launchpad.net/lucid-backports [12:05] then why doesn't it show up in the search list when I click on 'choose' alongside the package name and type 'backports' or 'lucid-backports' [12:06] Because launchpad doesn't have a working search facility for terms that are subsets of other terms. [12:06] So if you search for "foo" and "foobar" happens to exist, you'll probably never find "foo" [12:07] is it okay if I manually type 'lucid-backports' in the package field of bug report? [12:08] sounds misterious :) will change the package to 'lucid-backports' [12:12] persia: oopsie, when I type 'lucid-backports' in the package field and click 'Save Changes' launchpad gives the error "Launchpad doesn't know of any source package named 'lucid-backports' in Ubuntu" [12:12] You need "Also Affects Project" [12:13] Not "Also affects Distribution" [12:13] Source package is correct. [12:14] okay! [12:22] persia: thanks for guiding :) [12:23] mistrynitesh, Thanks for helping put bugs in the right place, and asking if you weren't sure. [12:23] my pleasure === zyga is now known as zyga-break === bladernr is now known as bladernr_ === ogra_ is now known as ogra === zyga-break is now known as zyga === yofel_ is now known as yofel [14:26] Sorry, when will by the meeting [14:29] Olivier_Blaziken: 17:00 UTC we currently have 13:29 UTC [14:29] (use 'date -u' in a terminal to get the UTC time) [14:29] ok Thx [15:01] charlie-tca: entertaining the crowd, I'm from classroom team :) [15:01] Oh, okay! Great job on it [15:02] * charlie-tca thought nigelb was just trying to confuse him [15:02] charlie-tca: heh :) === zyga is now known as zyga-afk === ivoks-afk is now known as ivoks [15:48] bdmurray, hi, do you know if the number of people affected by a specific bug is increased when the report matches a bug pattern ? [15:50] My X session crashes whenever I run "gitk" on another system using my 10.10 laptop as the DISPLAY. [15:56] jibel: No, I don't believe so due to the order of apport operations. The duplicate notification would be displayed before there is an Oauth token for apport so writing to the bug isn't possible yet. I believe I reported a bug about wanting to increase the user affected count. === deryck is now known as deryck[lunch] [15:58] jibel: bug 487316 [15:58] Launchpad bug 487316 in apport (Ubuntu) "apport should metoo bug reports that match a pattern (affects: 1) (heat: 10)" [Wishlist,Triaged] https://launchpad.net/bugs/487316 [15:58] elder: please open a bug on this [16:05] bdmurray, we could use login_anonymously starting from lucid and make authentication transparent to the user ? [16:06] bdmurray, the problem is that a bug with a bug pattern associated just vanishes [16:06] jibel: the affects_user call requires a user [16:06] :/ [16:07] jibel: there is some talk of permissions redesign for launchpadlib but I'm not on top of that at the moment [16:10] hggdh: did you extend xttejx? [16:10] hggdh: er xteejx [16:11] bdmurray: yes, I did, he is back and was going to expire in 2 days, I think [16:12] hggdh: cool, thanks [16:13] bdmurray: BTW -- yofel gave us two patches for the responses. The first one (additional looks good [16:14] bdmurray: the second -- updating the dev release to N -- I am not sure it is already time [16:14] hggdh: right so just don't use it! ;-) [16:15] bdmurray: heh. The actual question is... let's accept the first one? [16:15] hggdh: they've both been merged and push [16:16] yeee! [16:16] * hggdh bows to the bugmeister === zyga-afk is now known as zyga [16:37] would someone send an e-mail reminder to the list about the meeting at 1ET or 17UTC [16:37] * bcurtiswx_ is in the middle of something, but wanted to get one out [16:37] bcurtiswx_: I think pedro did yesterday === simar__ is now known as simar [16:41] * bcurtiswx_ has a lot of mail to check.. thx micahg === zyga__ is now known as zyga [16:57] Afternoon all === deryck[lunch] is now known as deryck [17:11] cheers xteejx [17:11] hggdh: ?? What did I do lol [17:12] wow, we have a meeting chair now, cool [17:12] micahg: Am I interrupting a meeting here?? [17:12] xteejx: you are back :-) [17:13] xteejx: not by ~47min [17:13] * xteejx didn't realise he was missed *that* much ;) [17:14] ahh 5pm UTC duh - I should've worked that our is 6pm here (UK) [17:14] oh well it'll be back to normal UTC=my time in a few weeks [17:16] https://wiki.ubuntu.com/BugSquad/Meeting/Minutes are minutes not being kept now or have we missed 10 months or meetings? [17:16] *of [17:19] micahg, does that mean you want to chair our next meeting? [17:19] :P [17:19] * charlie-tca hs missed not quite 10 months of meetings [17:19] :P [17:20] * micahg hopes to be sitting in a chair for the next meeting bcurtiswx [17:20] [17:21] * xteejx will be sitting on a sofa [17:29] meeting is in here, right? === ivoks is now known as ivoks-afk [17:33] charlie-tca: I assume so :) [17:34] yes indeed [17:34] charlie-tca, yup :) [17:34] Dammit, how do you import .flv audio into audacity [17:35] Oops, should've said that to #ubuntu :) [17:35] o/ [17:35] hello all :) [17:36] * bcurtiswx_ takes a giant blade of grass and slaps xteejx with it :P [17:37] lol bcurtiswx_ :P [17:37] I'm trying to make a funny video, I'll link my youtube in when its done ;) [17:49] * micahg will be back in about 40 minutes [17:50] no meeting for you 'eh [17:50] bcurtiswx_: like I said, I hope to be sitting in a chair ;) [17:51] haha, OK micahg :) [17:52] vish, did you want to lead the mentor subject? [17:53] bcurtiswx_: No, I'll be here, my expertise is in video/audio production [17:53] Done it in time...just [17:54] ? [17:54] Sorry, thoguth you meant I woon't be here cuz I was mesing with videos :) [17:55] OK [17:59] ~ô~ [17:59] 1 minute [17:59] 20 seconds [18:00] OK, WHo's Ready for some meeting fun?!?!?!? [18:00] #startmeeting [18:00] Meeting started Tue Oct 12 16:57:38 2010 UTC. The chair is bcurtiswx_. Information about MeetBot at http://wiki.ubuntu.com/AlanBell. [18:00] Useful Commands: #topic #action #link #idea #voters #vote #chair #action #agreed #help #info #endmeeting. [18:00] Yup [18:00] I forgot it! :p [18:00] * charlie-tca waves [18:00] * devildante waves too [18:00] * xteejx waves back [18:00] Welcome all. I will be your chair today. [18:00] I want to make sure that if you add a topic to the meeting wiki, you put your name next to it, so the next chair knows who's going to be talking about what [18:01] * charlie-tca notes we got us a meeting bot too [18:01] So Today I plan on posting the topic and if the person who added it is here , they can speak up at that time [18:01] First things first: [18:02] #topic Intro to new meeting bot. -bcurtiswx [18:02] TOPIC: Intro to new meeting bot. -bcurtiswx [18:02] I lol'd at the name :p [18:02] So , for those who aren't using text to speech, should be able to see that we have a meeting bot :) [18:03] * xteejx wonders how we would use TTS for IRC (one for another day I guess) [18:03] Please use the following link to check out the commands in detail (it's not the exact commands, but it's quite close) [18:03] #link https://wiki.ubuntu.com/ScribesTeam/MootBot [18:04] Future chairs should use this bot, as it simplifys the meeting minutes (posts the log to a website) [18:04] when I end the meeting it will post a link to the log [18:05] Any questions on the bot? [18:05] * xteejx thinks it seems pretty effective [18:05] +1 nice idea [18:05] +1 [18:05] You have to preceed all commands with # ? [18:05] +1 [18:05] if anyone has an idea they need to do the following, for it to be logged [18:05] #idea , note that this command adds an entry into the log [18:06] well it should... i can say it is still in beta. [18:06] we'll have to see, lol [18:07] is the bug squad meeting going on?? [18:07] yes [18:07] #topic Mentorship program update from Mentors. [18:07] TOPIC: Mentorship program update from Mentors. [18:07] did someone want to lead this? [18:07] vish? ^^ [18:07] its for all mentors [18:07] We need all mentors to give us an update, please. [18:08] all present mentors o/ [18:08] +1 [18:08] i will proceed [18:08] o/ [18:08] Go ahead, simar [18:08] simar_ go ahead and start [18:08] charlie-tca, :) [18:08] All Present mentors who haven't o/ please do so i can come to you [18:09] \o [18:09] stanley_robertso has been online two days back only. He was out of country and busy so I finally able to cantact him after two months [18:09] * nisshh doesnt think his mentor is around right now :| [18:10] otherwise ahmed my other student is doing well .. he working on touchpad [18:10] great, simar_ [18:10] That will be nice [18:10] drew212: update? [18:11] * devildante can do an update [18:11] jibel: here? [18:11] hes finding the topic a bit harder but interresting .. and stanley is also interested in kernel .. i hope he will also work on the same package [18:11] over for me.. [18:11] thanks :) [18:12] hggdh: ?? [18:12] * nigelb coughs [18:12] * devildante coughs too [18:12] I have not seen kangorooo for quite a while [18:13] nigelb, devildante, charlie's taken this segment :) [18:14] hggdh: any update on your other two? [18:14] oops [18:14] heh [18:14] hold on, let me check them [18:15] * charlie-tca wishes people were not always logged in to IRC [18:15] lol [18:15] holstein has asked to be temporarily dropped, too busy with school right now [18:15] ojap is going nicely on :-) [18:16] Good to hear [18:16] yes indeed. One out of three, but at least one [18:16] will you update the wiki and launchpad on holstein ? [18:16] Is a meeting going on here? [18:16] yep [18:16] bilalakhtar, ya [18:16] * bilalakhtar joins === simar_ is now known as simar [18:17] nigelb: next? [18:17] ok [18:17] I've been assigned 2 students who're finally showing some signs of interest in working [18:17] :-) [18:17] flipe is going well, he's asking me or asking in the channe when he has doubts [18:18] He's very much interested in learning and helping out :) [18:18] gigacore got it touch with me the day he was assigned, not heard from him since [18:18] that's about it from me [18:18] devildante: [18:19] ok [18:19] samwho is doing progress, even though he's busy at times with IRL university work [18:19] my other assigned student, I sent him an email but he has not responded yet [18:20] I should probably send him another e-mail [18:20] that's it for me, thanks :) [18:20] bdmurray: here?? [18:21] bcurtiswx: [18:21] you may as well take it [18:21] cagordon hasn't gotten back to my e-mails. it's onyl been a week, since my last two assigned both dropped out. I will email cagordon again soon. [18:22] charlie-tca: yes, I'm here [18:22] any update on your mentee? [18:22] davely has shown interest, and i then told him to meet me in IRC and start reading guides.. but no show on IRC so far.. and no emails since then [18:23] both i will email soon for a follow up [18:23] excellent. [18:23] I didn't think I was on the list with my launchpad work ... [18:24] heh, looks like someone gave you a mentee again [18:24] We will work on that one [18:24] bcurtiswx: we will need anyone not present to send an update to the mailing list [18:25] Eveybody is doing a really super job with this program. Keep up the great work! [18:25] #action Mentors not at meeting need to report to the mailing list on their mentees [18:25] ACTION: Mentors not at meeting need to report to the mailing list on their mentees [18:25] Thanks charlie-tca [18:26] (and don't let the "drop me" 's mess with you.) [18:26] OK moving on [18:26] #topic Regression tags and workflow. [18:26] TOPIC: Regression tags and workflow. [18:26] nobody assigned. who wanted to talk about this? [18:26] jibel: there? [18:27] Otherwise I can talk about it [18:27] We have discussed regression tags on our last meeting [18:27] hggdh, go ahead, and jibel can pipe in if he gets in [18:28] We have also sent an email to -devel talking about it, and asking for feedback [18:28] Quick summary for those not present before? [18:28] liky to the thread? [18:28] yes please :) [18:28] Now, with the feedback we received we are going to start implementing it [18:29] the change: we are dropping the 'regression-potential' tag [18:29] It only created more work (mostly when a development release got promoted to stable, like right now with Maverick [18:29] +1 [18:30] i see, +1 [18:30] so what would be the tag that will replace it? [18:30] instead we are going to mark regressions as 'regression(release|proposed|update)' followed by the version we found it in [18:30] like maverick, lucid, etc [18:30] hggdh: Can we have an example? [18:30] +42 then :) [18:30] regression-proposed-maverick for instance? [18:30] no. 'regression-release maverick' [18:31] actually ['regression-proposed', 'maverick'] [18:31] two different tags: one identify a regression, the other identify the version it was *found* on [18:31] so 2 separate tags [18:31] OK [18:31] Got it [18:31] there are some reasons [18:31] any questions on this topic? [18:31] "regression-release natty" for unstable releases? [18:31] - we identify a regression on Maverick, but it was present since Jaunty [18:32] devildante: yes [18:32] as we find releases affected, we *nominate* them on the bug [18:32] So essentially, is a regression or not, no more "could be"'s? [18:32] yes, essentially. If it is not a regression, no nomination, or the nomination is rejected [18:33] Ok [18:33] hggdh, anything else? [18:33] most regression-potential never got changed to -release [18:33] we will start to implement it now, for the Natty cycle. [18:33] bug day! [18:33] Is this being removed from LPGM script and LP? [18:34] bdmurray would know about LPGM [18:34] yes. And it will be removed from the regression wiki pages [18:34]