[00:11] <Mizutsuki> hello, I was wondering if there is anything I could do to increase the oddds that a developer might spare some attention for a particular bug that affects me?
[00:12] <Mizutsuki> It's a java swing bug, it probably has something to do with x11, though I'm not sure
[00:27] <bdmurray> nullack: what show stopper bug is this?
[00:27] <nullack> Brian one moment pls
[00:28] <nullack> bdmurray: Bug 261995
[00:28] <james_w> Mizutsuki: hi, if you give the bug number it helps with people giving advice.
[00:29] <Mizutsuki> 240818
[00:29] <james_w> bug 240818
[00:29] <Mizutsuki> james_w: that one's not mine, mines the one set to this one as a duplicate, 'cause there was more interest in this one, it sems
[00:29] <james_w> Mizutsuki: if you can hang on for half an hour I'll have a bit of time
[00:30] <james_w> otherwise someone else might
[00:30] <Mizutsuki> james_w:unfortunately, in half an hour work ends and I'll be out of here ^_^
[00:30] <james_w> you could try
[00:30] <james_w> #ubuntu-java
[00:30] <james_w> but it's a *really* bad time right now
[00:30] <Mizutsuki> why's that?
[00:31] <james_w> there's a freeze in 28 minutes, so it's a bit of a rush
[00:34] <Mizutsuki> ah, the feature freeze for 8.10... I see
[00:34] <Mizutsuki> alright, well then I'll just leave it for tomorrow
[00:38] <ogasawara> bdmurray:  dunno, but the last comment makes it seem to be hal related
[00:38] <ogasawara> bdmurray: sheesh, I didn't expect people to be testing 2.6.27 already!  now I gotta tweak my call for testing script
[00:39] <nullack> Its in Intrepid now mate youll get lots of em using it :)
[00:40] <ogasawara> ah nullack:  can you attach some logs files for debugging hal
[00:40] <nullack> Sure, anything to help. What ones you want?
[00:40] <bdmurray> There should be a DebuggingHal page
[00:40] <ogasawara> nullack: yah, lemme find the link for ya
[00:40] <nullack> ok will take a look
[00:40] <nullack> While were at it, anyone want to look at another one I raised? lesser priority :)
[00:41] <nullack> bug 26027
[00:41] <ogasawara> nullack: https://wiki.ubuntu.com/DebuggingHal
[00:41] <nullack> bug 262027
[00:41] <ogasawara> nullack: additionally dmesg output might be good too
[00:41] <nullack> Im on it, will ping when its attached to LP
[00:42] <ogasawara> nullack: k, thanks
[00:42] <nullack> bug 262027 erked me in particular cos I dont like the system saying its ok when it failed
[02:06] <mrooney> hggdh: I don't know, it is weird
[02:06] <mrooney> It really worked flawlessly with 0 errors when I ran it
[02:13] <qwerty6523> hi
[02:13] <qwerty6523> how to find bugs to help fix
[02:13] <mrooney> qwerty6523: hi
[02:13] <qwerty6523> how do i*
[02:13] <mrooney> well, you want to look in the topic, specifically, http://wiki.ubuntu.com/HelpingWithBugs
[02:14] <qwerty6523> thanks
[02:14] <mrooney> hggdh_: I don't know, it is truly a mystery
[02:15] <hggdh_> mrooney, I will have a look at it tomorrow. This sounds more like some sort of python thing than really network
[02:15] <hggdh_> under the same LAN, same firewall(s), my xchat session usually stays up until I reboot
[02:15] <mrooney> hggdh_: yes, it is strange
[02:15] <hggdh_> indeed...
[02:16] <mrooney> it worked fine on my eeepc and this laptop, but they were both on the same network
[02:16] <bdmurray> Isn't the problem connecting to Launchpad though?
[02:16] <mrooney> so it might be some particular of my network that let it work fine
[02:16] <hggdh_> bddebian, we are not yet sure
[02:16] <hggdh_> maybe LP, maybe freenode
[02:16] <hggdh_> dammit, not bd debian, but bdmurray ^^
[02:17] <bdmurray> I thought it was announcing more than one at time which sounded to me like a connectivity to find out about new bugs issue but...
[02:17] <hggdh_> mrooney, can I su - to your account later on? (on xibiu, I mean)
[02:18] <hggdh_> it seems it loses the connection, and then the python code automatically retries it
[02:18] <hggdh_> mrooney, you are running it under screen, and I do not have a log on disk to look at
[02:18] <mrooney> ooooh
[02:18] <mrooney> it isn't http
[02:19] <mrooney> it is getting an error 110 on sending to the IRC socket
[02:19] <mrooney> hggdh_: sure, you can do whatever you want, it's your machine :D
[02:20] <hggdh_> mrooney, its my machine, but it is your account :-)
[02:20]  * mrooney grants hggdh_ full access :)
[02:20] <mrooney> it is getting a timeout on sending to the socket, how mysterious
[02:21] <hggdh_> yes, but which socket? the LP one, or the freenode?
[02:22] <mrooney> freenode
[02:22] <hggdh_> ah
[02:22] <mrooney> I am using a raw socket for that one, for the http I am using feedparser
[02:22] <mrooney> which seems to be working fine
[02:22]  * hggdh_ wonders about timing
[02:23] <hggdh_> mrooney, how often it gets hit by the timeout? You know?
[02:24] <mrooney> well, every time EeeBotu leaves the channel...unfortunately I didn't put timestamps in the error output
[02:24] <hggdh_> np. I will set it up on a different channel and will monitor it as needed. This is a standard Hardy server, no special drivers/kernel
[02:42] <mrooney> hggdh_: okay it is logging all stdout and stderr to logFile
[02:42] <mrooney> with timestamps, now
[02:44] <mrooney> oh hehe I can't commit, my SSH key isn't on that server :}
[02:47] <mrooney> bdmurray: though even if I logged everything, to be honest, I really feel something odd is going on with that atom feed
[03:00] <mrooney> bdmurray: since the feed constantly changes, here is a snapshot: http://img517.imageshack.us/img517/7879/bugsatomfeedtx4.png , notice the bottom three are in reverse order contrary to the overall chronologically ascending order, though the second to top is also off.
[03:03] <mrooney> okay, bedtime for me, let me know what you think though, I should see it
[06:35] <tuxmaniac> LaserJock: still around? I tried maxima from Debian unstable. Fails to build in intrepid.
[06:36] <LaserJock> yeah, needs newer gcl
[06:36] <LaserJock> it really is too bad that maxima requires gcl. It's such a great app but hard to keep updated
[06:37] <tuxmaniac> so I left it and went off to sleep. Saw your mesage at #u-motu. Now that freeze is over, am not sure whether we will be able to get maxima in :-(
[06:37] <tuxmaniac> good morning everybody btw :-)
[06:38] <dholbach> good morning
[06:39] <LaserJock> hi dholbach
[06:39] <tuxmaniac> dholbach: hi
[06:39] <dholbach> hi LaserJock, hi tuxmaniac
[08:39] <mcas> i have a question about todays bugday
[08:40] <mcas> i am looking for a bug report but this one should be fixed upstream but i still have this problem...
[08:40] <mcas> now i don't know if it is a problem with the german locale
[08:41] <mcas> it's about bug 120672
[09:05] <gnomefreak> mcas: hold on
[09:05] <gnomefreak> i know we didnt fix it yet
[09:06] <gnomefreak> mcas: we cant really fix it in Hardy
[09:06] <gnomefreak> only INtrepid will get it
[09:06] <mcas> ok
[09:06] <mcas> thats why i ask for it ;-)
[09:07] <gnomefreak> mcas: unless asac slips it past but its not a SRU
[09:07] <gnomefreak> mcas: i can always build it for my PPA for hardy
[09:07] <gnomefreak> but i would like to wait to find out what asac plans on doing
[09:08] <mcas> ok than i'll wait, too
[09:08] <gnomefreak> ok i pinged him but hes most likely still sleeping
[09:08] <gnomefreak> he will reply when he gets here
[09:08] <mcas> if there is something new just ping me
[09:09] <gnomefreak> mcas: will do
[09:09] <mcas> thx
[09:12] <mcas> can someone tell me how i can edit the wiki page so that my nick is directly linked?
[09:13] <mcas> is there a special tag?
[09:43] <gnomefreak> mcas: no feature work on 2.0 branch in hardy
[10:07] <mcas> thank you gnomefreak
[10:07] <mcas> i change it to won't fix?
[10:13] <mcas> or better fix commited and a comment that there will no feature work on 2.0 branch in hardy, gnomefreak?
[10:13] <gnomefreak> asac: would you like that tbird bug closed or target for 3.0
[10:14]  * gnomefreak should really keep his pings to one channel 
[10:14] <mcas> :-)
[10:16]  * gnomefreak just waits for console-tools to get fixed
[10:16] <asac> which bug in particular?
[10:17] <mcas> bug 120672
[10:17] <mcas> hi asac
[10:19] <asac> unlikely that that gets fixed in 2.0
[10:20] <asac> you should try out 3.0 and if its not there report it upstream
[10:20] <mcas> is there a thunderbird 3.0 version?
[10:20] <mcas> the report looks like it was fixed upstream
[10:33] <geser> thekorn: should py-lp-bugs 0.3 work with edge? because I get an parse error about BugReport.__nickname
[10:45] <thekorn> geser: it should work, but I just found out that things on edge changed again,
[10:45] <thekorn> will look at it in a bit, and run some tests
[10:46] <geser> thanks
[10:47] <geser> do you need the traceback?
[10:51] <thekorn> geser: no, thanks
[10:51] <thekorn> it's enought to know that it fails at parsing the nickname
[11:01] <thekorn> geser: I can reproduce it, filed bug 262192
[11:30] <thekorn> geser: commited fix as revision 158 of the .main branch
[12:32] <slhk> Hi, I need assistance in marking bugs as duplicate
[12:33] <slhk> they have a different "affects" project
[12:34] <slhk> should I add the missing project as  also affected?
[12:36] <knorr> slhk: Well, I guess that depends if the projects affected both are correct?
[12:38] <slhk> knorr: I'm not sure, but I think the one actually present is wrong, and the one on the duplicate bug is the right one
[12:39] <knorr> slhk: What are the bug numbers?
[12:40] <slhk>  Bug 224774 is a duplicate of  Bug 212388
[12:43] <slhk> knorr: Bug 224774 is a duplicate of  Bug 212388
[12:43] <knorr> slhk: It's not the same traceback
[12:44] <slhk> knorr: do you mean different python version?
[12:46] <knorr> slhk: No different DbusExceptions. Look at the last line in both tracebacks. One seems to be a permission/policy issue. The other I don't know.
[12:47] <slhk> knorr: Oh, ok! I'm sorry
[12:48] <knorr> slhk: But that's just my 2 cents. I'm new to the bugsquad.
[12:50] <slhk> knorr: I'm newer than you, thanks for your help
[12:52] <knorr> slhk: Didn't think that was possible. ;) But in general, you should look for the info in the bug report and not just the title when marking duplicates.
[12:53] <slhk> knorr: I looked at the description but I missed the traceback, maybe it could be suggested on the wiki
[13:02] <snadge> has anyone else experienced not being able to finish bootup after installing the new kernel update? :P
[13:02] <snadge> i had to kill some dkms processes for it to continue booting.. and now nvidia driver isnt loading ;)
[13:05] <Hobbsee> snadge: where's your nvidia driver from?
[13:08] <snadge> its the ubuntu restricted nvidia driver
[13:09] <knorr> snadge: I had the same problem, but a simple disable/enable in the Restricted Drivers GUI fixed it.
[13:12] <snadge> the dkms part is hanging, on installing the previous kernel
[13:12] <snadge> and it seems to do that on bootup now as well
[13:15] <popey> does anyone know the name of the program that pops up when you insert a cdrom containing a repository? I'd like to file a bug agsinst it but dont know what it is
[13:15] <popey> and i dont have a cd with a repo on to hand to _make_ it pop up
[13:29] <snadge> ok so now i have nvidia back (by reverting to kernel -20) but sound doesnt work :/
[13:30] <snadge> and dkms still causes the bootup to hang until i kill the dkms_autostart process
[14:12] <snadge> ok, so after latest nvidia driver and kernel update.. -rt kernel fails to load nvidia
[14:13] <snadge> -generic is ok.. but im still getting the strange dkms problem, and also shutdown also hangs.. after stopping samba processes.. have to sysrq sync, unmount, boot
[14:13] <snadge> blows :(
[14:15] <snadge> (hardy proposed)
[14:39] <tuxmaniac> any user of matplotlib around to test bug 246239. If someone could give me the code to test I can do that on my hardy too.
[14:47] <rbrunhuber> Is bug 261147 a duplicate of bug 259278?
[15:06] <bddebian> Boo
[16:35] <mrooney> okay time to get back on the bay!
[17:15] <ckyle> x
[17:24] <bdmurray> pedro_: What do you think of bug 253118?
[17:24] <pedro_> bdmurray: looking
[17:26] <pedro_> well network-manager now has the "edit connections" dialog so i don't see why it should depends on gnome-network-admin...
[17:28] <bdmurray> pedro_: ah, and I don't see "Manual Configuration" as a menu item either
[17:29] <pedro_> bdmurray: that's correct it was removed, network manager (nm-connection-editor)  handle those now
[17:29] <bdmurray> pedro_: Okay, they probably just saw it at an odd time, I'll follow up with them
[17:30] <james_w> yeah, check they've got nm 0.7 installed
[17:30] <pedro_> bdmurray: yup, rock thanks
[17:34]  * pedro_ editing his location on launchpad
[17:35] <bdmurray> pedro_: hmm?
[17:35] <pedro_> that's a pretty neat new feature
[17:35] <pedro_> bdmurray: look at your profile
[17:35] <pedro_> now launchpad has an integration with google maps
[17:36] <pedro_> edge only i guess
[17:36] <bdmurray> ah! I see now
[17:43] <Ampelbein> hi! could some member of bug-control please check on bug #260910 ? I added the upstream-bugwatch and think the bug could be set to triaged.
[17:43] <Ampelbein> Thanks.
[17:47] <pedro_> Ampelbein: done, thanks you
[17:48] <Ampelbein> pedro_: thanks.
[18:04] <Ampelbein> Now, I have a question on bug #105818 . First of all I think it could be set to triaged/low, now the questions: 1. Is the tag "packaging" correct, since a change in "debian/control" would fix the problem? 2. Is there any team/person to subscribe the bug to?
[18:05] <Ampelbein> Oh and 3. Should this also be reported to debian?
[18:07] <techno_freak> Ampelbein, if you know how to fix it, you can volunteer to make a debdiff for the same and attach it  ;)
[18:09] <Ampelbein> techno_freak: ok, i'll try that. i guess ubuntu-main-sponsors is then to be subscribed since it is published in main?
[18:11] <techno_freak> Ampelbein, righto
[18:11] <Ampelbein> techno_freak: ok, thanks.
[18:11] <techno_freak> Ampelbein, thanks for trying to help us :)
[18:16] <Ampelbein> And another one ;-) : Bug #155765 - I think it could be set to status triaged, but i'm unsure what importance to suggest. I tend to "low" since the loss of usability is not severe.
[18:19] <chrisccoulson> i've just reported a compiz crash using Apport. It's assigned to Compiz at the moment, but I think the problem is my video driver (it started happening after fitting a brand new nvidia card yesterday). could someone take a quick look and tell me what they think? I'll reassign it to the correct package then
[18:19] <chrisccoulson> bug 262334
[18:19] <chrisccoulson> seems its already been re-assigned!
[18:20] <james_w> Ampelbein: "packaging" is right I think. "bitesize" may be appropriate if it looks easy
[18:21] <james_w> Ampelbein: but in this case I'm not sure a conflict is appropriate.
[18:23] <Ampelbein> james_w: why not? seahorse and gnupg-agent provide the same functionality and i see no need for having both of them installed.
[18:23] <james_w> but no reason is not justification for a conflict
[18:24] <james_w> perhaps they shouldn't be installed together, but I imagine it's more likely there is just a bug to fix
[18:26] <Ampelbein> james_w: ok, then i will report the issue upstream. it just seemed as the easiest way to avoid having this issue.
[18:32] <Ampelbein> Ok, now i added the upstream-report and removed the packaging tag. Now i think it could be set to triaged/low? (bug #105818)
[19:42] <mattik> Hello, I have Asus Laptop with Finnish keyboard and arrow keys doesn't work in Kubuntu Intrepid. I have tried keyboard layouts as Asus Laptop and 105-buttons keyboard. Is this reported bug?
[19:43] <mattik> and at-character diesn't work, too
[19:43] <mattik> doesn't
[19:43] <knorr1> mattik: There was a reported issue some while ago about the up-arrow being mapped as printscreen. I had it as well, but it have been resolved.
[19:44] <mattik> knorr1: do you use KDE4?
[19:45] <Knorr> mattik: Nope, that was in Gnome. Sorry, didn't see the (K)ubuntu. ;)
[19:45] <mattik> Ubuntu keyboard works right
[19:47] <mattik> In Kubuntu I selected Finnish for Keyboard language and after this it doesn't work
[19:48] <Knorr> Okay, so it's layout specific. Well I don't really know anything about that I'm sorry. But haven't seen any bugs about it. Not the same as saying there isn't one.
[19:48] <yuriy> mattik: I have run into that before and it went away. somebody else has reported a bug on it, check launchpad
[19:49] <mattik> Knorr: Thank you. It is reported that firefox crashed in paypal-page?
[19:50] <mattik> yuriy: thank you :) Do you get a crash
[19:51] <yuriy> what crash?
[19:51] <mattik> firefox in paypal.com
[19:52] <yuriy> mattik: do you know about lanuchpad, the bug tracker?
[19:52] <yuriy> mattik: no, haven't had any such problem
[19:52] <yuriy> *launchpad
[19:52] <mattik> yes, I know but I have reported really much bugs what are duplicate and I don't trust myself
[19:53] <yuriy> mattik: use the search...
[19:53] <mattik> I have tried
[19:53] <yuriy> mattik: https://bugs.launchpad.net/ubuntu/+bug/255861
[19:54] <mattik> yuriy: thank you :)
[20:08] <mattik> yuriy: I found it paypal error what is founded in Hardy first
[20:09] <mattik> has found
[20:10] <mattik> I try will it crash on Gnome. Thank you :)
[20:57] <CarlFK> how can I see what files are in a .deb?
[20:57] <jpds> CarlFK: dpkg -L
[20:57] <CarlFK> guessing it is some kind of archive - tar and zip didn't like it
[20:59] <jpds> CarlFK: No, wait, it's dpkg-deb --contents filename.deb
[20:59] <CarlFK> bingo.  thanks
[21:07] <mouz> I just marked 4 bugs as duplicates of bug 150252. Is there anything else I can do for the bug? Should I for instance nominate it for releases?
[21:08] <mouz> https://bugs.launchpad.net/ubuntu/+source/tasksel/+bug/150252
[21:29] <CarlFK>  dpkg-deb --contents linux-restricted-modules-2.6.27-1-generic_2.6.27-1.1_i386.deb|grep ath_pci
[21:29] <CarlFK>  -rw-r--r-- root/root     20304 2008-08-27 08:37 ./lib/linux-restricted-modules/2.6.27-1-generic/ath_pci/ath_pci.mod.o
[21:29] <CarlFK> that may be a mistake
[21:44] <Knorr> Just got bug 260931 marked as a duplicate of bug 257376 based on the traces being similar. Am I the only one who finds those traces nothing like each other?
[21:45] <Knorr> https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/260931
[21:45] <Knorr> https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/257376
[21:48] <pedro_> Knorr: may you reply on the bug then?
[21:50] <Knorr> pedro_: Is that a trick question? (If you mean I should just ask in the bug, the answer would be that I just wanted a second opinion before doing so)
[21:50] <pedro_> Knorr: no is not
[22:03] <james_w> bdmurray: hi, are you around? I need the bugmaster.
[22:03] <bdmurray> james_w: Here I come to save the day!
[22:03] <bdmurray> ;-)
[22:04] <james_w> calm down everyone, bdmurray is here.
[22:05] <james_w> bdmurray: we're going to have to be paying more attention to escalating bugs and adding them to the RC list as we get closer to release. Do we have guidelines on the best way to do this?
[22:05] <james_w> are people asked to nominate bugs as they see fit, and then the list of nominations will be processed accordingly?
[22:06] <bdmurray> james_w: the list of nominations is a bit long at the moment, ~300ish, and the number of people who review the nominations is quite small
[22:07] <james_w> is it small as we want it to be small, because there aren't many people qualified, or because we haven't added anyone recently?
[22:07] <bdmurray> james_w: One thing we'd talked about at UDS was using the bugsquad mailing list
[22:07] <bdmurray> after establishing criteria for escalation
[22:08] <bdmurray> the group is small due to Launchpad organization
[22:09] <bdmurray> The group that can manage nominations includes Uploaders and Drivers
[22:09] <james_w> I can see the benefits of using the mailing list, but it's a bit of a concern that it would be more work than just nominating, and so we would punish the people that were doing it properly
[22:10] <james_w> and lots of users nominate just in an effort to get their bug looked at or worked on
[22:11] <james_w> when is the next QA meeting?
[22:12] <bdmurray> I believe that nomination would be the ideal process however, from a practical standpoint only 4 people could be said to regularly reviewing those
[22:13] <bdmurray> The QA meetings are every Wednesday
[22:14] <james_w> would this be a suitable agenda item for the next one?
[22:14] <james_w> it may be that this is all pretty clear, and so a meeting wouldn't really help.
[22:16] <Ampelbein> Sorry to interrupt. Could some member of bug-control please check on bug #257415 ? I think it could be set to triaged/low importance.
[22:16] <bdmurray> I think talking about it could help.  To me it seems that there may be 2 separate issues though.  1) how to escalate bugs and 2) how to deal with the quantity of nominations
[22:17] <Knorr> Ampelbein: It's already tagged as Confirmed and filed upstream?
[22:18] <Ampelbein> Knorr: yes.
[22:18] <Ampelbein> Knorr: did confirm it and filed upstream
[22:18] <Knorr> Ampelbein: No need to tag it as triaged then. ;)
[22:19] <Knorr> Ampelbein: Actually it's already fixed upstream it seems. Could be tagged as Fix Released then
[22:19] <hggdh> bug 257415
[22:20] <hggdh> Knorr, only if the fix is already available on our repositories
[22:20] <Knorr> hggdh: Okay, I see.
[22:20] <Ampelbein> Knorr: Hmm. From the wiki: <Triaged> Use this when you are confident that it should be looked at by a developer and has enough information. So I thought this should be the status to set when everything is done and the developers are looking at it.
[22:21] <Ampelbein> ubottu seems dead... https://bugs.edge.launchpad.net/ubuntu/+source/seahorse/+bug/257415
[22:21] <bdmurray> james_w: Does that make some sense?
[22:21] <james_w> bdmurray: I agree that there are two issues.
[22:22] <james_w> bdmurray: I think we should have guidelines soon, and make them clear to everyone so that people know what to do. For whether this involves a meeting or not I'll defer to you.
[22:22] <bdmurray> james_w: It'd be interesting to try and find out how frequently bugs are nominated - so if the number of nominations became 0 how many there would be to deal with.
[22:23] <james_w> bdmurray: if you think so then can I suggest dropping a mail to -devel inviting the release team and other interested parties to the next meeting to discuss it?
[22:23] <james_w> bdmurray: yeah, do you know of a way of doing that?
[22:23] <hggdh> Ampelbein, as soon as we are guaranteed the fix has made it to SVN, we can mark fix committed
[22:24] <Ampelbein> hggdh: ups. just marked it fix commited because upstream-developer said it was fixed.
[22:24] <bdmurray> james_w: I imagine its in the db somewhere but I don't recall looking at nomination dates before
[22:24] <Knorr> Ampelbein: My mistake. I ment ofcourse Fix Committed instead of Fix Released
[22:25] <Ampelbein> Knorr: you were right, i didn't notice before that upstream already took care of it.#
[22:25] <james_w> bdmurray: as for the question about how to deal with the quantity I think we should have a discussion at some point, and then work with lp to get what we want implemented for the next freeze.
[22:25] <Ampelbein> Knorr, hggdh: and its already in the trunk-changelog.
[22:26] <Ampelbein> http://svn.gnome.org/viewvc/seahorse/trunk/ChangeLog?view=log
[22:26] <bdmurray> james_w: the quantity of nominations or the quantity of reviewers?
[22:26] <james_w> bdmurray: cool, that will be useful information. Can you also get the percentage accepted?
[22:26] <hggdh> Ampelbein, good!
[22:27] <james_w> bdmurray: well, deal with the quantity of nominations, which may involve increasing the number of reviewers.
[22:27] <bdmurray> james_w: for Intrepid? probably
[22:28] <james_w> bdmurray: focusing on nominations for the development release is important I think, SRUs are a different thing in this case I think.
[22:30] <bdmurray> so any information about the rate of nominations could be misleading if more people start using it
[23:38] <CarlFK> what is the package name for the .27 kernel?
[23:40] <hggdh> linux-image-2.6.27-1-*
[23:40] <CarlFK> kernel-image-2.6.27-2-generic-di  what is the -di ?
[23:41] <CarlFK> linux-image-2.6.27-1-generic  there we go.
[23:41] <hggdh> I do not know about this package