[00:38] laga: I asked slangasek, but never got an answer on myth-control-center [00:39] ScottK: hi, what was the question? I seem to have misplaced it in the flood [00:40] slangasek: You have (had last I looked) myth-control-center sitting in unapproved for the release pocket [00:40] correct [00:40] What I suggested was how about if you reject that and then some mythbuntu person re-uploads to -proposed. [00:41] I gather they need it. [00:41] ah, did I not ack that? yes, please [00:41] laga: ^^^ [00:41] Go for it. [00:41] It's possible I missed the ack too. [00:42] * ScottK was sitting in a rare $WORK meeting where he had internet access and may have been distracted. [00:45] ScottK: do you want to accept that last upload you wanted me to do? [00:45] the quodlibet one [00:46] It's accepted IIRC. [00:46] oh nvm then :D [00:47] probably total noob like question, but what is ack? [00:48] ACKnowledged [00:48] Short for Acknowledge [00:49] Ah ok, that makes all sorts of sense now. === kitterma is now known as ScottK2 [01:18] slangasek, re " What I suggested was how about if you reject that and then some mythbuntu person re-uploads to -proposed.", i just uploaded it to proposed too [01:18] superm1: ok, cheers [01:19] superm1: you're not expecting it to be approved through before release, right? :) [01:19] slangasek, well i guess this is the reason we have the option of using a PPA in our build system :) that will be fine. i'll push it through the ppa for now and then shortly after release hopefully it can clear -proposed and -updates [01:20] ok [02:44] evening everybody [02:46] Evening. [02:46] LaserJock: You're on motu-sru, right? [02:46] yep [02:46] want me to look at something? [02:46] Last release motu-release (because there was no motu-sru) suspended the must in the development release first rule and got people moving early on SRUs. [02:47] I'm figuring that's out of scope for use this time. [02:47] suspended the what? [02:47] I recommend it and would encourage motu-sru to conspire and make an early announcment. [02:47] The rule that you have to fix something in the development release before you do the SRU. [02:48] ohhh, right [02:48] Since there is no development repository right now. [02:48] I'm not very fond of that rule [02:48] I mentioned this to jdong last night too. [02:48] was the nvidia 5200 and 5500 drivers changed from nvidia-glx-new to -glx? [02:48] it's a good idea, but often doesn't really help the quality of the SRUs particularly [02:48] I would think it's a good general policy anyway to avoid accidentally regressing again in the /next/ release... [02:49] Agreed. [02:49] It worked out last time for getting started early. [02:50] Although I think that most of our preventable regressions come from incompletely documented merges and then some Ubuntu specific change gets dropped. [02:50] well, it would make more sense to me if we did more new upstream releases in -updates [02:51] There's a rule for that too. [02:51] hello [02:51] LaserJock: In that case, you might want to look into Bug 220723 [02:51] Launchpad bug 220723 in wesnoth "Please sync wesnoth 1:1.4.1-2 (universe) from Debian unstable (main)." [Wishlist,Invalid] https://launchpad.net/bugs/220723 [02:51] ajmitch: Hello. [02:51] but often times the code in the devel release is very different than in the stable release so requiring a fix in the devel release first is just a way of making sure we're getting things fixed in the devel release [02:52] ajmitch: Thanks again for the RC bug page. [02:52] which is all good, but not something we should really block on, IMO [02:52] ScottK2: I hope it was useful [02:52] ajmitch: It was. [02:52] I'd like to keep it on hardy for awhile, and have another page for intrepid [02:52] I wish we'd had more QA effort in Universe for Hardy, but RC bugs page was a key part of what we got done. [02:52] Sounds smart. [02:53] LaserJock: Then you need some process for knowing the problem is still open in the developmental release. [02:54] ScottK: like a bug report? [02:54] #ubuntu-release-party is interesting today [02:54] like how hard is it to just leave the main task open on a bug and just close stable release tasks for SRUs? [02:55] I don't see why we necessarily have to have a fix in the devel release for a fix to get into a stable release [02:55] LaserJock: That'd work. I'm just saying someone needs to champion changing the process. [02:55] well, is there concise documentation on what combination of Severity and tasks constitute SRU fixes? [02:55] nope [02:55] last I checked in -devel, there was discrepancy [02:56] the only real documentation I have is that it needs to be "very important", already fixed in the devel release, and "minimal" [02:56] "minimal" is for the fix, not the bug [02:57] ScottK2: you do -backports some don't you? [02:58] Yes [02:58] what's your feeling on people trying to get stuff into -backports to fix bugs? [02:58] rather than just trying to get latest crack [02:59] LaserJock: I see no reason to discourage it personally though I don't want it to be an execuse not to do a proper SRU [02:59] which is what happened when Backports DID allow SRU-like fixes [02:59] i.e. backporting 1.2.3-15 to 1.2.3-9 [03:00] LaserJock: I generally wont fix requests to fix SRU bugs. [03:00] I personally feel like the SRU process should be such that people aren't trying to get things fixed via -backports [03:00] Actually as I understand it the backports charter from the tech board is pretty specific about this. [03:00] but how often do you guys get requests for bug fixes? [03:00] One of the problems is that developers often recommend it to people. [03:01] It's a significant fraction of the requests, but certainly not the majority. [03:01] ~10 or 20 percent maybe. [03:01] k [03:01] ScottK2: it's probably considered as a 'safer' option for getting fixes in [03:02] I need to talk with slangasek more, but I think we should be able to come up with a way to deal with those kinds of requests [03:02] though you probably just end up with more people unnecessarily enabling backports [03:02] ScottK2: it's more common than that [03:02] The "OK to backport" threshold is very low. Builds/Installs/Runs. [03:03] jdong: Probably more common in the desktop ones you tend to deal with. [03:03] ScottK2: and I'm getting feedback from users wanting to file such backports to do SRUs that "they rather not" [03:03] because it's "not gonna happen anyway" [03:03] :-/ [03:03] I sometime tell them to ask again, but ask for the features in the release and don't mention the bug fixes. [03:04] SRUs are seen as having a rather large barrier? [03:04] Yes. [03:04] Particularly in Main. [03:05] I don't think I've ever got an SRU in [03:05] I guess I'm particularly interested in how many times we say "we won't fix it" vs. "we can't reasonably fix it" [03:05] I've gotten several in Universe. I don't think I've gotten one in Main. [03:05] I got I think 2 or 3 in Main [03:05] not sure if I've done any in Universe really [03:06] like, this wesnoth bug is interesting to me [03:07] I thought you'd like that one. [03:07] I don't mind saying things like "we're unable to sufficiently test this update" or something technical [03:07] but if it's just "oh, there's a lot there, we better not do it" [03:08] well, that just ends up seeming lazy, IMO [03:08] I think that bug is trivially significant for -proposed->-updates [03:08] it's all fixes [03:09] Modulo dropping debian's packaging changes [03:09] yeah [03:09] it seems to me that given sufficient testing things like that shouldn't be a problem [03:09] LaserJock: So there you go. Test case for point release SRU. [03:09] ScottK: I've already emailed the TB about it [03:10] waiting until after release to pick slangasek's brain [03:10] It's not like it hasn't happened before. [03:10] LaserJock: Go look at the clamav version in dapper-updates. [03:10] LaserJock: be sure to wait a few days so the cells have a chance to regrow ;) [03:10] slangasek: heh, yeah [03:11] this may not be the best example, but I've been running Fedora a fair bit recently [03:12] LaserJock: fedora has an EXTREMELY lenient update policy [03:12] and their policy is to do new upstream release in preference to backporting fixs [03:12] LaserJock: everything from a typo in a helpfile to OpenOffice or an ABI-incompatible libgpod [03:12] LaserJock: including new kernel releases [03:12] yep [03:12] that's a bit scary for us [03:12] IMO. [03:12] at least unless we evolve -backports into -volatile [03:12] which I have no fundamental objection to ;-) [03:12] but they're able to keep a reasonably stable OS [03:13] LaserJock: kind of [03:13] LaserJock: users have rioted over things like unison breaking overnight [03:13] LaserJock: and spurious updates too [03:13] so if you take Fedora as one extreme [03:13] and our current policy as sort of the other [03:13] I don't want 350MB of updates because of a new icon for openoffice [03:13] perhaps somewhere in the middle we can find a usable way to provide stable updates to our users [03:13] bbiab [03:16] This time around we have a .1 release pre-planned a month out. [03:17] I'd tend to say be really lenient about bugfix releases and beta or RC to final updates until then. [03:21] Heya gang [03:21] Heya bddebian [03:21] Hi ScottK2 [03:21] LaserJock: We were a lot more lenient about bugfix releases post FFe this time around and it seemed to work out well. [03:21] This is for motu-uvf/release [03:24] What's the name of the Gnome gui for apt (adept equivalent)? [03:25] synaptic [03:25] Thanks. [04:05] back [04:05] Heya LaserJock [04:05] hiya bddebian [04:06] ScottK2: yeah, maybe something along the lines of letting more things through until .1 would make sense [04:07] * ScottK2 didn't volunteer for motu-sru, so good luck with it ;-) [04:08] It would end us up with less "You've got an RC in the final release, how awful" kind of comments. [04:09] * StevenK could do without those comments for Haryd [04:09] Hardy [04:09] * ScottK2 departs #ubuntu-release-party due to getting dizzy. [04:09] that bad? [04:10] nah, just ruffians. [04:10] It in combination with averaging about 4 hours of sleep per night for the last about 5 days. [04:10] well, I think people generally don't realize how much we change compared to upstream [04:10] so if we have an rc version then it must not have the fixes in the final [04:10] etc. [04:10] Right. [04:11] same thing happens with SRUs [04:11] i.e. I must have a new upstream version to get upstream bug fixes [04:11] I know for Postfix lamont chose to patch 2.5.1 with all the 2.5.2 fixes rather than release with 2.5.2~rc1 [04:12] right [04:12] I guess I just wonder if we need or can get that info to users better [04:13] I suspect the ones that most need the information are the least likely to listen. [04:14] good point [04:15] yo yo you freakazoids! [04:17] hi nixternal [04:17] wasabi LaserJock [04:18] chillin', discussing SRUs, working on a Fedora 9/Hardy blog post [04:18] * nixternal holds back the giggles on F9/Hardly post [04:18] err, Hardy [04:18] got some kick butt data today at work [04:19] but of course nobody would understand it if I described it [04:19] so I won't [04:19] ahh thought so :) [04:19] it's like being at the CIA [04:19] except I don't get the cool shades [04:20] More like heavy duty industrial goggles? [04:20] yeah, just bought some [04:20] $300 a pop [04:20] but they're nice [04:21] don't look welding goggles from the 80s anymore [04:22] so, I'm a bit confused; does motu do any development on the packages, or just build packages? [04:22] development, maintenance [04:22] things like that [04:23] teaching, sponsoring, reviewing as well [04:23] I've been trying to find a way to contribute more to open source, looking around on launchpad now, but I was a little confused on that point [04:24] since most of what I saw was specific to building/fixing packages [04:24] well, that is a lot of what we do [04:24] making sure the archive is in good shape [04:24] StevenK: ping [04:24] LaserJock? [04:26] so, if I want to primarily do more on the development side, as opposed to building packages, should I look more toward core (assuming I want to work on ubuntu) then? [04:28] miyako: what do you mean by "development"? [04:28] LaserJock: writing code, either adding new features or fixing bugs [04:28] ah, I see [04:29] since everything ends up in a package it's often a bit difficult to distinguish between code development and package development [04:29] well, it kind of depends on what kind of things you want to do [04:30] if it's working on specific software for Ubuntu then you might perhaps find a relevant team [04:30] for bug fixing you might want to hook up with the Bug Squad [04:30] yeah, what I would really like is to have a specific project or application, something that I can get comfortable with the code base, etc, and work on that, fixing bugs and adding features [04:31] I was originally looking to contribute to things upstream (especially since ubuntu isn't the only distro I use) but I've had really bad luck with that so far [04:32] well [04:32] do you have any projects you're specifically interested in? [04:33] LaserJock: well, I've thought about it a bit, but I havent gotten any specific programs in mind [04:33] miyako: If you're interested in KDE at all, kde4 right now is an interesting mix of packaging brand new stuff, fixing bugs to mature it, and writing new stuff to fill the gaps. [04:33] yeah [04:34] ScottK2: hmm, I'm a gnome user, but that might be something to look at anyway; I've done a bit with Qt a couple of years ago [04:34] miyako: The best channel for that is #kubuntu-devel (although it's pretty quiet right now). [04:34] I was looking at compiz, upstream, but I found it really hard to get into the codebase and the developers weren't all that helpful [04:34] As an example, I'm pretty sure we're missing a qt4/kde4 program to control display brightness. [04:35] Kubuntu is very welcoming. [04:35] and I was working on Planeshift, the people were nice, but there was too much structure there, it was like working a second job [04:36] Here's it's more about being open to you volunteering the way you want. [04:36] You do need to show you know something/are trustworthy before you get upload rights to the archive. [04:36] ScottK2: yeah, that's understandable [04:36] yo yo!! [04:37] Kubuntu will rock your socks right off your cousins feet! [04:37] I tried contributing a couple of kernel patches, but you want to talk about an obtuse system to work through to get something accepted [04:37] Yep. [04:37] nixternal: I even tried kde4 the other day [04:37] nixternal: how's Vista going? [04:37] I haven't run Vista in a couple of months now, so I wouldn't know :) [04:37] kde4, vista, same thing [04:38] miyako: Even small stuff is welcome. My first contribution to Kubuntu core development was to get GPG and S/MIME encryption working out of the box with Kmail for Gutsy. [04:38] I got a new laptop that shipped with vista, it never had a chance to boot up [04:38] ajmitch: pretty much [04:39] well, back when I fiddled around with KDE4, I did start writing a GUI program to edit containments [04:39] whose bright idea was it to remove the Epiphany icon from the menus? [04:40] remove? I still see mine [04:40] I just installed Hardy, then installed epiphany-browser and there is no icon under Internet [04:41] * ajmitch only has an upgraded system, not a new install [04:41] nixternal: We provide you with a proper standards compliant browser when you install. [04:41] * ScottK2 has only one server as a new install. [04:42] nixternal: you have epiphany-gecko installed, I expect? [04:42] anybody happen to know if libgsf is still libgsf or if it was incorporated into something else? [04:42] That one due to a sad story involving me using apt-get dist-upgrade instead of using the official upgrader, a software raid array, and things upgrading in the wrong order. [04:43] ScottK2: on Firefox sucks, and if I am using Gnome I want Epiphany [04:43] uggg [04:43] heresy [04:43] Ah. I've never gone down that choice in the logic tree. [04:43] I never get to if I have Gnome. [04:43] epiphany is from the devil ;-) [04:43] haha, me either usually [04:44] Epiphany is love [04:44] * ajmitch hugs epiphany [04:44] They have Ubuntu at the library, but that's the only place I've ever used it. [04:45] for me epiphany does nothing better than firefox and a number of things worse [04:45] so ... [04:45] I just want a fast, non-bloated browser, that will do what I want it to do [04:45] lynx? [04:45] You want mozilla 1.0 then. [04:46] firefox 3 is pretty darn fast [04:46] ahh, I got the icon now, you have to log out of gnome and back in for it to show up [04:46] isn't that lovely! [04:46] no [04:46] I just had to [04:46] on a fresh install [04:46] that is a bad thing [04:47] miyako: In any case feel free to drop in on #kubuntu-devel if you want to get involved in a great project that's open to new contributors. [04:47] * ajmitch wonders if anyone else will strike his bug of the desktop disappearing [04:47] I can't seem to control my touchpad, that's my latest "what the ..." [04:48] I didn't have that, but I learned today that restarting X with ctrl alt backspace while the laptop is connected to an external display doesn't lead to happiness. [04:50] Though not nearly as welcoming as Debian eh ScottK2? :) [04:50] I think they're just mean to you. [04:51] heh [04:53] "quick, everybody get your mean face on, bddebian is coming!" [04:54] Aye :) === Syntux__ is now known as Syntux [05:13] grr, I wonder who decided touchpads need to be able to scroll [05:14] People who thought having a dedicated scroll area on the touchpad would be useful. [05:15] I guess so [05:15] it's so annoying and I can't turn it off :( [05:15] I would think you can turn it off. [05:15] ah [05:16] well, for some reason my touchpad stopped responding to configuration programs [05:16] I tried even turning it off in xorg.conf with no luck [05:16] Right. [05:16] but every time I go to my task bar it keeps jumping through screens [05:16] really annoying [05:17] s/screens/windows/ [05:55] good morning [06:02] hello dholbach :) [06:02] hi ajmitch :)) [06:02] ready for the celebrations? :) [06:05] what are we celebrating? [06:07] let's celebrate my successful disassembly and reassembly of a new fridge to get it through the door [06:07] now that's an achievement [06:07] * ajmitch is just glad that there's a rather wide kitchen door at home [06:07] Haha [06:10] Estimated build start: in 27 seconds [06:11] The problem is, it's been saying that for 5 minutes. [06:12] something blocked or disabled? [06:12] I wouldn't know, that's from Launchpad [06:15] * ajmitch shrugs [06:15] Estimated build start: 0 seconds ago [06:15] You win, Launchpad [06:15] I'd better walk home now anyway :) [06:21] what up MOTUs... I'm back in linux after my ~2 yr hiatus, now that the audio drivers on my new lappy work :P [06:28] G'morning. [06:31] morning =) === asac_ is now known as asac === happinessturtle is now known as nenolod [06:54] hi, i don't know why but my resulting package is empty === Sebast1an is now known as Sebastian [08:41] Does anybody here have experience with python-central + dh_pycentral ? [08:41] I'm trying to create a python package, which works well for $PYSHARED/mypackage _except_ for $PYSHARED/mypackage/subfolders [08:42] When I install my package, only files directly into the mypackage dir in the pycentral-dir will be available in [08:42] /usr/lib/python2.x/site-packages/mypackage [08:42] I can't figure out why [08:42] Do I really need to manually make my package install files in /usr/lib/python2.4/site-packages/foo/ AND /usr/lib/python2.5/site-packages/foo/ ? [08:45] Flawless: You shouldn't. [08:45] RAOF: And I don't want to :) [08:45] RAOF: Can you help me avoid it? [08:45] I mean you shouldn't have to :) [08:45] agreed :) [08:45] But it doesn't seem like pycentral works in 7.10 [08:45] My experience with dh_py* has been Just Working, but let's give it a shot :) [08:46] My experience so far has been "can't make it work for the life of me" :) [08:49] RAOF: when you used dh_pycentral, where did you install the files in your debian package? [08:49] I mean, in the DESTDIR. I think that might be the issue [08:50] LEt me check. [08:51] thanks [08:56] RAOF: any luck? :) [09:00] Flawless: SOrry; distracted :) [09:00] :) [09:01] So, this setup.py just puts stuff in python2.5/site-packages [09:01] Which is probably wrong, now, unless cdbs' python-distutils package has been updated. [09:03] ok, so I'm not the only one [09:03] I did figure out the problem, btw [09:03] I create a multi-binary package from a single source [09:04] and each package installs things into /usr/share/pycentral/foo/site-packages/foo/ [09:04] which is right [09:04] files from A are installed and compiled, but files from B are not compiled, because the install script runs "pycentral pkginstall B", but B's files are in A's folder [09:05] they have to be in A's folder, because the python script searches for them there [09:27] RAOF: It consistently doesn't work properly. I'm going to have to install into /usr/lib directly [09:28] * RAOF shrugs. I dunno, sorry. [09:28] thanks though :) [11:03] <\sh> siretart, thx again for the nice tuesday evening :) [11:03] heya \sh ! :) [11:04] <\sh> hey emgent [11:07] * norsetto doesn't want to know what \sh and siretart did on a nice tuesday evening [11:08] <\sh> norsetto, having one or two beer and a nice dinner :) [11:08] lol [11:09] \sh: I thought cigarettes were involved too at some point ;-) [11:09] <\sh> norsetto, nicotine yes...but that's only me :) [11:10] \sh: don't let warp10 hear you or he will give you a lecture on it .... [11:11] norsetto: eheh :D [11:12] norsetto: too late [11:13] he already did it... [11:13] \sh: just curious, how do you say in Germany for someone that smoke too much? I know in France they say "smoke like a fireman" and in Italy "smoke like a turk" [11:13] \sh: it was a pleasure to me! [11:14] norsetto: it's "smoke like a chimney" [11:14] in german [11:14] siretart: makes sense to me :-) [11:15] italian are racists :) [11:15] norsetto: well, "smoking like a chimney" is common in Italy too :) [11:16] norsetto: in German, they have no concept of smoking too much ;P [11:16] slangasek: makes even more sense to me :-) [11:23] slangasek: wasn't that in Greece? :) [11:24] dholbach: I don't know, I've never been to Greece, but I have been through Frankfurt airport where people smoke in the terminal under no smoking signs. :) [11:25] ah... well *shrug* :) [11:25] we smoke in hospitals, is it worse? [11:25] slangasek, not anymore :( [11:25] ogra: since when? [11:25] frankfurt is smokefree env now [11:25] it wasn't a year ago [11:26] slangasek: These are the final links and won't change right? http://torrent.ubuntu.com/releases/hardy/release/ [11:26] dunno, last time i flew you couldnt smoke anywhere inside but in a casino where you had to buy a club card first [11:26] about two months ago [11:27] ogra: I do remember they had some reserved rooms in the lounges [11:27] YokoZar: I can't say I know much about the structure of torrent.u.c; I just know the .torrent files sit alongside the .iso's everywhere that counts [11:27] they recently changed all german airports to that [11:27] norsetto, well, i live in germany, i rarely have a reason to use a lounge in frankfurt :) [11:28] YokoZar: that appears to be only the set of torrents corresponding to what's distributed on cdimage.ubuntu.com; but yes, they're not changing further now [11:28] ogra: why not? Beer is free :-) [11:29] slangasek: so the DVD image has been released ;) Hooray! [11:38] norsetto, ah, well, i'm fine to pay the 3 bucks on the train and actually move forward towards home usually if i hit frankfurt :) [11:39] ogra: ah, its your home airport :-) Are you in Darmstadt by any chance? [11:39] (3 € for the beer, not the ride indeed :) ) [11:39] no, saldy i dont have any home airport [11:40] :( [11:40] i live half way between frankfurt and hannover (kassel) [11:40] ogra: ok [11:40] and my favorite airline sits in cologne sadly [11:41] you mean airport? [11:41] Has w.u.c been sacrificed for the release? [11:42] the wiki usually takes a hit on release days.it comes and goes, I think it must be getting huge amount of traffic. [11:43] <\sh> ogra, oh well, train stations and smoking is even worse.. [11:44] <\sh> ogra, they have now yellow lined square somewhere on the platforms it's only 2 squarmeters and it looks like a ghetto [11:44] yeah, i'm waiting for little fences [11:45] <\sh> ogra, actually is sinnfrei ;) [11:45] so i can scare the train workes with my "beeeeh beeeh" [11:45] *workers [11:45] waering a sheep costume :) [11:45] <\sh> ogra, colleague of mine had the idea yesterday, to eat a lot of onions and beans to see if smoking disturbes other guests or the beans/onions mixture ,-> [11:47] heh [11:48] <\sh> ogra, anyways...nuernberg -> karlsruhe : departure: 9:27pm and we reached karlsruhe 2:07am [11:51] fun [12:19] hi folks [12:20] * cody-somerville waves. [12:20] Everyone pumped?! :D [12:22] cody-somerville, have a look in #ubuntu-release-party if you look for pumped ppl :) [12:24] * sistpoty|work tries to not ask the question :P === ivoks_ is now known as ivoks [12:33] sistpoty|work: Thanks for having a good sense of humor about libitpp [12:34] heh [12:34] ScottK: thanks for finding out that that was still missing [12:35] No problem. Glad it was sub'ed to motu-release so I could. [12:40] <\sh> I wonder when the behaviour of cluelessness of bug triager stops... [12:40] <\sh> obviously is counterstrike not a software which is in our archive..but the bug is against wine and a non working wine in combination with CS... [12:41] <\sh> but setting it to invalid is also wrong [12:46] \sh: This is the sort of case that "Won't Fix" was designed to handle. Making wine fully compatible with counterstrike is beyond the typical role of the distro developer. [12:47] back in the good old days, cs did work with wine though... (but I didn't test it after 1.5 or so later on, and not with the hl2 engine at least) [12:47] <\sh> persia, first, we need to identify if it's a regression of wine on ubuntu or in general...so before someone didn't find a clue that ubuntu is not at fault and it's wine package, it can't be set to invalid... [12:48] \sh: Hmm. True. [12:48] <\sh> persia, and the explanation of this triager is even more andventurous [12:48] <\sh> "However, it seems that you are not using software (Counterstrike) provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug." [12:49] <\sh> I mean, it's so strange that when using wine you are mostly using software which is in no linux distro archive [12:49] That's perhaps a little overconservative, although I can understand how it came to be written. [12:49] <\sh> persia, it's totally crap [12:50] On the other hand, wine is very much a special case (while not an emulator, it is best triaged like one). [12:50] \sh: For wine, I agree. For something like konqueror, I'd be less sure. [12:51] \sh: maybe you can kindly tell the triager that he was wrong, so that he won't do it next time ;) [12:51] <\sh> sistpoty|work, honestly I'm sick and tired of those greatful drive-by pros who don't have a clue about the problem at all...I mean, this is not the first time...and it won't be the last time... [12:51] \sh: That's a standard bugsquad answer. I've seen it before when someone asked for a lib to be added to ia32 libs so Skype would work. [12:52] <\sh> if someone doesn't understand the problem of the bug report he should not comment on it and move along [12:52] <\sh> ScottK, yeah [12:52] <\sh> ScottK, a drive-by [12:52] I think that particular issue is a bugsquad policy problem that could be fixed. [12:52] <\sh> totally useless [12:52] I think they are doing what they are being told and being told wrong. You could fix this with bdmurray. [12:52] See ya. Gotta run [12:53] cya ScottK [12:53] The trick is describing a policy that works for all cases. It was appropriate to reject a bug in feisty for automatix, but not for hardy for wine. Someone has to describe the rules to govern the responses. [12:54] <\sh> persia, well, I think being a member of bugsquad needs more then just a script and some good rules... [12:54]