[00:43] Good Evening All. [00:45] I have some questions about sponsorship, I have read through the wiki, and I have some questions if someone is willing to help me. [00:56] jcastro: you see the video of the new rythmbox plugin? Browse artists is kind of cool [01:06] * Hobbsee waves [01:16] hey Hobbsee [01:16] hiya ajmitch [01:16] how's it going? [01:16] exams suck. [01:16] physics should die. [01:16] apart from that, fine! [01:17] yay :) [01:18] have you finished exams now? [01:18] hah. no. [01:18] 2 more [01:18] Huh. I hope physics lives fine. === tritium_ is now known as tritium [01:52] I have some questions on sponsorship, I have read the wiki's information and would like to talk to someone about it. [01:52] shoot : [01:53] Your following me :) [01:53] Hobbsee: mind if I pm you? [01:53] * Hobbsee is omnipotent :) [01:53] Jimerson: would prefer you to ask in here, then multiple people can answer [01:53] * Hobbsee is a bad mentor, tbh. [01:53] Jimerson: It's generally best to ask any questions in-channel, and not to specific people, so everyone can learn. [01:53] we are trying to relaunch the Ubuntu Home Server project as it seems death [01:54] UHS would be analog to the windows home server [01:54] * Hobbsee wonders how that fits in with ubuntu server. [01:54] persia: Your make foo fails! [01:54] however, we need help specially in the management [01:54] Fair enough. I have not really found any information on how to find a sponsor, I am new to this, and am interested in helping, just need a kick in the right direction. [01:54] persia: make says "The directory exists, so I don't need to do anything" [01:54] StevenK: Hrm? Which part? [01:54] Jimerson: got a bug in particular, or wanting to know in general? [01:54] persia: The $(MAKE_DIRS) bit [01:55] Hobbsee: general. [01:55] StevenK: Did you not add $(MAKE_DIRS) as a dependency of .PHONY? [01:55] Jimerson: you usually just make sure the patch is correct, and subscribe ubuntu-universe-sponsors [01:55] stupid GPG question: can I have GPG show "info" about an encrypted file or signature (i.e. who signed it, who's it encrypted to, etc) [01:55] persia: Oh, was I supposed to? :-) [01:55] Jimerson: You don't need to find a sponsor: the sponsors need to find your patches. This is done with bug subscriptions. [01:55] anyone is experienced managing an open source sw prject? [01:55] jdong: you can do gpg --validate-sig or something, for the first. [01:55] StevenK: Sorry: I was tired last night. Yes, if you don't want it to block on timestamps :) [01:56] jdong: i dont think that's right, but it's close enough that the man page should help [01:56] persia: where is a good place to get started. [01:56] eneko_tab: we're MOTU's. we manage universe ;) [01:56] Hobbsee: hmm I'm perusing thru the manpage currently [01:56] silly question. [01:56] Jimerson: What do you seek to accomplish? [01:56] jdong: gpg --verify [01:57] i was close :) [01:57] persia: to help in any way that I can, does not matter to me what I accomplish, I would just like to give something back wherever it is needed. [01:57] Hobbsee: ah, ok [01:57] jdong: no idea on who it's encrypted to. i've not had to use it. [01:58] Jimerson: If you want to help MOTU, the best ways are 1) bug triage, 2) patches, and 3) Preparing candidate revisions with the patches to close the bugs. There's an overview at https://wiki.ubuntu.com/MOTU/Contributing [01:59] Jimerson: I'd suggest starting with #1, doing #2 when there's an obvious solution, and doing #3 when you've a package where you can close a few of the bugs due to #2. [02:00] persia: Thank you for your answers and time. [02:08] Heya gang [02:45] TheMuso: for u-u-s fun - all of http://tinyurl.com/2nynzm [02:45] TheMuso: that's a list fo bugs that have patches associated. the users presumably havent subscribed the sponsorship team. just if you get bored [02:45] persia: ^ bluekuja [02:46] Hobbsee: Yep. There's a link there from qa.ubuntuwire.com :) Part of the issue is that most of those patches aren't debdiffs. I'd say they aren't appropriate for sponsorship, although they are certainly appropriate for regular MOTU updates (just a different hat). [02:47] persia: might be a good thing for new people to do [02:47] that way they don't have to write the code themselves, but take the patch and apply it. [02:47] Heya persia, Hobbsee [02:47] Hobbsee: Absolutely. [02:47] hi bddebian [02:47] Hi bddebian [02:47] bddebian: right, youv'e got a job. [02:48] bddebian: 1500 patches that need debdiffs & uploads (or just flat rejection) :) [02:48] no, not quite that [02:48] to write the documentation, and help new people out with applying them. [02:48] Huh? [02:49] bddebian: hop to it, before you get beaten [02:49] * persia suggests that editing https://wiki.ubuntu.com/MOTU/Contributing might be a good way to do that, but thinks most of it is already there [02:50] What am I doing? [02:50] everything [02:50] bddebian: You're the new meta-MOTU: you get to make sure everything gets done :) [02:50] more specifically, taking patches that aren't on the u-u-s watchlist [02:51] hahaha [02:52] bddebian: you seem to think that we're joking? [02:52] You must be since you all know that I suck :) [02:53] no, this is a way to shut you up & keep you so busy that you can't complain about sucking or being stupid :) [02:54] hah [03:02] Hobbsee: Thanks. === _czessi is now known as Czessi [03:34] man I love merging hugemongous packages :/ [03:34] heh [03:34] As much as I love reviewing crappy ones? :-) [03:35] running grab-merge.sh on gcompris is gonna take almost 400MB [03:35] Mmmm, yummy [03:35] LaserJock: Ponies! === rob1 is now known as rob [03:35] * StevenK works on giving LaserJock a complex some more [03:36] yay, ponies! [03:40] * LaserJock twitches [03:53] Jesus, could we get a few more packages on REVU please? [03:54] Sure. [03:54] I'm sure that could be arranged [03:55] * imbrandon uploads 40 more [03:55] That's just 40 more that will get ignored ;-P [03:56] maybe REVU should be wiped at every FF ( e.g. start clean for the next release ) [03:56] atleaste all packages "archived" , thus a new upload will bring them back [03:58] imbrandon: that was the plan [03:58] but people started uploading stuff for hardy, during gutsy. [03:59] ahh then those people need to have gotten a "too bad" when they asked what happened :) [03:59] lol [03:59] btw hiya * [04:00] greetings :) [04:00] wtf: aswvdial_0.1patch2.dsc [04:01] heh [04:05] Well that was worth wasting my time on [04:12] for uploads to REVU, do we have to change debian/changelog to use hardy now, or can it remain as gutsy? [04:12] Hardy [04:13] mdomsch: If you upload as Gutsy, Soyuz will yell at you. [04:14] mdomsch: Just to make sure, are you considering an upload of a candidate for hardy, or a candidate for gutsy? [04:14] hardy most likely, though Dell will likely publish the packages for feisty and gutsy too [04:14] firmware-tools and firmware-addon-dell for flashing BIOS [04:15] mdomsch: Hmm... Is there a backporting / update policy for the Dell repos? [04:15] i would target hardy then -backport it [04:15] Dell has seperate repos? why [04:15] * persia tends to agree with imbrandon, but it may depend on Dell policies [04:16] imbrandon: Special add-ons which we don't have or want yet. [04:16] we don't have policies yet, we haven't published debs yet [04:16] but we do publish rpms for other distros/versions [04:16] * bddebian covers his ears [04:16] :-) [04:16] mdomsch: assuming your part of the DELL team i would closely follow the Ubuntu policy ( or atleaste have a good reason not to ) [04:17] imbrandon, yes, which is why I'm asking and trying to understand [04:17] mdomsch: this is the problme that you need to sign with the dell key, isnt it? [04:17] I believe no more new packages will be accepted for feisty and gutsy via MOTU [04:17] mdomsch: I'm generally in favor of using distro releases when feasible, so in this case, I'd suggest an upload to hardy, and performing the backport for the others. [04:17] :) mdomsch normaly it would be targeted at the current development release, then semi automaticly added to -backports after a but of testing [04:17] yet those are the releases we're shipping now or will soon [04:18] mdomsch: correct, but you're dell. so it's probably possible to mangle things. [04:18] assuming soyuz doesnt blow up. [04:18] mdomsch: technicly yes, but new {feisty,gusty}-backports can happen [04:18] ahh, -backports - I hadn't seen that [04:18] :) [04:18] mdomsch: would the hardy/gutsy/feisty packages be the same? [04:19] imbrandon: except that a lot don't use backports, so -updates might be smarter. [04:19] Hobbsee, certainly same source; most likely different packages due to different python versions [04:19] Hobbsee: this is for dell, theey can enable -backports if they want :) [04:19] * persia votes for -updates with special pleading to the archive-admins [04:19] which is fine by me [04:19] imbrandon, Hobbsee, if it's not enabled by default, we haven't enabled it in our factory images [04:19] mdomsch: will python-central python-support not take care of the versioning diffrences ? [04:20] imbrandon: then i dont want to see a repeat of the flashplugin fiasco. [04:20] imbrandon: True, but it's "Community Support": do you want backports by default? [04:20] oh, that's right - debs build the .pyc files at install time [04:20] persia: personaly since i'm on the backports team it wouldent bother me, but i see your point [04:20] then the same package will probably work on all [04:20] mdomsch: Right. .py is distributed, and .pyc is local. [04:20] mdomsch: right. then throw it into hardy, and then get the archive admins to copy it to the other releases. [04:20] persia, fedora does that different, fwiw [04:20] abuse of power, but oh well. [04:21] mdomsch: So does everyone not debian-derived :) [04:21] heh yea ubuntu == <3 [04:21] * mdomsch tries to understand and follow the rules before discarding them [04:21] well you've come to the correct place :) [04:21] mdomsch: the rules are "no new packages to released versions, unless they fit !sru, unless there's a damned good reason. assuming the build system wont curl up in a ball and die" [04:22] in a nutshell, that's the rule [04:22] easiest way to get something in is to get it into the development version, then get it backported. [04:22] or, in special cases as this, copied, so it appears in -updates [04:22] and persia fwiw i did do a fresh install of gutsy for my step-dad tonight ( converting him from vista w00t ) and multiverse is indeed on [04:22] does the help? [04:23] now for backports, do I or do I not have to edit debian/changelog to s/hardy/gutsy/ ? [04:23] if it's just a file copy on the archive, I assume no [04:23] you dont, its automagic [04:23] cool [04:23] mdomsch: it would be to gutsy-backports anyway. [04:23] assuming no source changes are needed etc etc etc [04:24] i dont think you *can* upload to gutsy anymore, without the build system blowing up. [04:24] i think it has to be -updates or -backports [04:24] if source changes are needed then a direct upload to -backports is required and alot of a$$ kissing to the archive team [04:24] imbrandon: chocolate accepted. :) [04:24] heh [04:24] other bribes also accepted. [04:25] imbrandon: Thanks for the confirmation. I think that's broken, but will wait until I'm organised to complain. [04:25] imbrandon: just none of multiverse is used by default. [04:25] correct [04:25] i guess that makes sense - the first step in any ubuntu script is to enable universe, do an update, then install the required codec [04:25] nothing is used, and i 1000% agree with the way it is [04:25] Hobbsee: right [04:26] but we had this "disscussion" the other nigth [04:26] night* [04:26] ah right. i was probably "studying" [04:26] i 1000% agree it should be on but nothing installed from it, saves tons of support [04:26] heh [04:27] * Hobbsee just wants to know how people randomly manage to remove parts of their kernel. [04:27] Whereas I believe that due to the questionable nature of some of the contents, there should be a click-through at least. [04:27] Hobbsee: rm? [04:27] Hobbsee: Wielding sudo mv/rm ? [04:27] Hobbsee: I dd zeros in the middle of it. [04:27] * StevenK high fives persia [04:27] persia: thats easy to fix, if its questionable dont put it in the archive :) [04:27] Tonio_: That's living dangerously :) [04:27] haha [04:28] no, they seem to remove the generic kernel package. and then whine that they have no l-u-m, so their card doesnt work. [04:28] the stuff is seeded, it's on installs, it's mandatory to have it for upgrades...yet somehow people still file bugs due to not having it. *sigh* [04:29] they might be manualy installing a -rt or kernel image , e.g. linux-image-2.X.X-rt not the meta package [04:29] that woudl do it [04:29] hm, yeah, could do. [04:30] imbrandon: I'll also agree with that, but https://lists.ubuntu.com/archives/motu-council/2007-November/000512.html is authoritative today. [04:30] sure [04:39] persia: authoritative regarding what? [04:39] LaserJock: Multiverse inclusion policy [04:39] persia: there wasn't much said [04:40] LaserJock: To give context, last week imbrandon and I were debating whether multiverse should be configured by default. [04:40] ah [04:41] I thought mayber we were back to Windows binaries [04:41] *maybe [04:41] heh [04:41] Essentially, imbrandon's position is that it's a support nightmare to explain to each and every user how to enable multiverse, and it's my position that parts of multiverse are possibly inappropriate for some uses. We're both right, but it doesn't help that there are no restrictions on multiverse inclusion. [04:42] LaserJock: Related, but not the current topic of debate. The policy I cited applies in both cases. [04:42] well, kinda [04:43] somebody really needs to respond to that thread [04:43] I don't think anybody knows what it was about [04:43] what thread? [04:43] LaserJock: I disagree that the thread needs a response. Someone needs to define a reasonable goal for multiverse, and promote that set of criteria. [04:43] imbrandon: https://lists.ubuntu.com/archives/motu-council/2007-November/000498.html [04:43] If approved, the thread can be revisited. [04:44] persia: they don't know about it [04:44] I talked to dholbach [04:44] LaserJock: Who doesn't know about it? [04:44] and he didn't know what was going on [04:44] he thought it was just non-free stuff [04:44] Right. And pq has an advocate on REVU. [04:44] which of course is fine fore Multiverse [04:44] *for [04:44] the question is specifically about Windows binaries [04:44] and that *hasn't* been brought up [04:45] LaserJock: Thanks for the heads-up: I thought this was intentional. I've a draft I've been not posting, and will send it wiithin the next 12 hours. [04:45] LaserJock: what makes a diffrence if its a windows binary or a BSD binary etc ? if its distributable [04:45] and dholbach was like, "why hasn't anybody said anything then?" [04:45] imbrandon: some MOTUs are concerned about security, viruses, etc. [04:46] ok then take wine out, wtf [04:46] Because Toni reported it as a Windows binary in the blob post. [04:46] that makes no sense [04:46] imbrandon: I'm not opposed to wine, or windows binaries, but I can't support them. That's the essence of my point. [04:46] imbrandon: because it's a slipper slope according to crimsun [04:47] *slippery [04:47] LaserJock: the slope was choosen when we put wine in, i mean you cant give somone a tool and expect them not to use it [04:47] no [04:47] but that doesn't mean we have to have packages for it [04:47] we have 0install [04:48] Yay. Storm coming. [04:48] but we don't provide 0install packages [04:48] * persia still thinks there is a difference between supporting user-insalled Windows software and distributing Windows software. [04:48] in any case, the objection was brought up [04:48] several MOTUs had problems with it [04:48] TheMuso: Really? Still bright and sunny here [04:49] so we should have some sort of discussion and resolution of the issue [04:49] StevenK: Yeah. Cloudi is building up, and thunder can be heard. [04:49] persia: i think you mix up supporting the packaging and supporting a program, very few is ANY programs we support as the coomunity, i've seen you make that statement before and it baffles me [04:50] LaserJock: i thought the resolution was pretty clear when mdz said "if its distributeable" [04:50] I honestly don't care what the resolution is, I just think we should have some sort of policy [04:50] imbrandon: When I have time, I try to fix all the bugs I can. I further try to help users to use the software, and make sure it works. 90% off the stuff I investigate is for packages I will never use, sometimes in languages I do not know. [04:50] imbrandon: well, not exactly [04:50] I try to provide support. I do not require you to do so, but I do expect that you will not make it harder for me to do so. [04:50] LaserJock: how is that not clear ? seems cut and dry to me [04:51] TheMuso: Neat. Hopefully it won't end up as muggy as it was yesterday [04:51] LaserJock: We do have a policy. The last message in the thread is authoritative. [04:51] StevenK: Yeah. [04:51] persia: I don't think it exactly is [04:51] persia: and i also like to make the end user experince for adding new software easy, i dont ask you to support it either [04:51] same other reverse [04:51] only* [04:51] it was stated that Debian wouldn't take it [04:52] imbrandon: Actually, you do :), but that's a different issue (and I don't mind) [04:52] and since that was the criteria for the policy we have [04:52] LaserJock: how is it not, its from the CEO of canonical and a member of ..... [04:52] LaserJock: Ah. Good point. That means it's not acceptable to us. [04:52] imbrandon: if they didn't know the specifics [04:52] bah [04:53] LaserJock: You might want to leave a comment on the REVU entry... [04:53] we have firmware and other bits ( firefox ) that debian wont take, we're != debian [04:53] LaserJock: they dont have to know the specifics [04:53] you think someone will change their mind because its a BSD or SUNOS or $other binary ? wtf [04:53] yes [04:54] well many MOTUs felt so [04:54] so it's worth addressing [04:54] from mdz: My implicit policy for multiverse has always been that it must be [04:54] distributable, and little else. It was modeled after Debian non-free, which [04:54] I don't think the source of the binary matters: I'd be just as opposed to a new BSD or SunOS binary. [04:54] wtf so inclusion would read "if its distributable but not built on Windows" [04:54] is similarly defined (everything which doesn't meet the DFSG but is still [04:54] what if its a reactos binary? [04:54] distributed by Debian). [04:55] the point being that Multiverse is modeled after Debian non-free [04:55] and several people said that Debian would never take this package [04:55] yes but not byte for byte, just as ubuntu != debian [04:55] so it's *worth* discussing for goodness sakes [04:55] I honestly don't care about the outcome [04:56] but I really feel like we need so real resolution [04:56] and it was, and because the awnser wasent liked it has to be driven out, thats what i'm getting at, a specific question was asked "what is the inclusion policy" and one was give, it falls in that so whats the problem [04:56] imbrandon: the question is specifically about Windows binaries [04:56] LaserJock: I'm not sure we don't have real resolution at this point. I don't understand how the last message isn't clear, and I don't understand why only Windows is bad. [04:57] because when I talked with dholbach he was like "oh, I didn't know that that was about" [04:57] I think they thought it was just the usual thing [04:57] which we all know [04:57] LaserJock: Check with elmo: that's the only person who needed to know. [04:57] omfg listen to the words i'm saying LaserJock , one second, listen to me , the specific question was "what is the multiverse inclusion policy" and that windows binary falls into it, NOW if you want to bring up a second question or exception fine, but the decision is very clear IMHO [04:58] imbrandon: but that was *not* the question [04:58] * persia agrees with imbrandon despite not agreeing with the decision [04:58] LaserJock: it WAS https://lists.ubuntu.com/archives/motu-council/2007-November/000498.html [04:58] ^^ READ [04:58] imbrandon: that was the guy who's trying to push his stuff [04:58] and? [04:58] he *nowhere* mentions the stuff that crimsun and the other guys talked about [04:59] err shit wrong link [04:59] they know the multiverse policy as much as everybody else [04:59] LaserJock: So, what does that matter. Interested party asks project leader. Project leader identifies delegate. Delegate publishes policy. [04:59] bahhhh [04:59] screw it [04:59] LaserJock: mdz stated "any thing thats distributweable" [04:59] * mdomsch uploads firmware-tools and firmware-addon-dell to REVU [04:59] imbrandon: I know, but I don't feel like he looked at the issue [05:00] I just want to be sure [05:00] but well, it's not my package and I don't care about this at all [05:00] I just want to make sure that the objections that people had are addressed [05:00] LaserJock: Please, I do agree that the policy needs to be redefined, I just don't think that is the place to argume about it. I think a wiki draft policy, review by MC, and presentation to TB would have a greater chance of accomplishing something. [05:00] * mebrown says thanks to mdomsch... [05:00] LaserJock: what issue, i think he looked at it very clearly, its not a question if X can be included, its a question of what can be, you cant do every package on a case by case you have to follow or change the policy [05:01] persia: that's what I'm trying to do!!!!! [05:02] LaserJock: Ah. My misunderstanding. From your notes above, I had the impression you were arguing with the process for establishing the current policy. [05:02] LaserJock: and if that is the case then all firmware will have to be removed because it was built on and for windows to be used by those drivers [05:02] I'm saying that this hasn't been properly addressed [05:02] the guy sent an email to Mark [05:02] who then CCd the MC [05:03] it's not addressing the issue that MOTUs had [05:03] LaserJock: you are looking at the wrong email, you should be looking at the one titled "multiverse inclusion policy" [05:03] imbrandon: I am looking at it [05:03] LaserJock: ok then you see where mdz said "ok" ? [05:03] i'm not seeing your point here [05:03] LaserJock: Ah. Right. I think that comes from no activity on part of MC: I'm not sure how we are intended to prod them to action. [05:03] anyone know a good resource for setting gconf settings via the shell/scripts? [05:04] persia: I talked to dholbach last night [05:04] LaserJock: as the policy stands right this second the package is ready for multiverse [05:04] he wondered why the MOTUs who objected didn't reply to the email [05:04] imbrandon: I would agree with you, other MOTUs didn't [05:05] LaserJock: Right. Based on that, I'm of the opinion there is more to be said, but I'm just not sure that continuing that thread is the way to do it, nor do I know that the final decision is not an infomed decision. [05:05] persia: I'm just not sure [05:05] that's why I'm trying to get people to write something up, get it going [05:06] my goodness [05:06] man-o-man but firmware built for and on windows is "OK" wtf is the diffrence [05:06] LaserJock: Regarding replies, I suspect most MOTU don't follow MC closely, and I also suspect that most would not feel obliged to respond to queries directed to MC. [05:06] I'm just trying to get us to get this thing resolved [05:07] imbrandon: No difference. Personally, I'd like to see all acceptable binary blobs restricted to "restricted", where an NDA can be signed, and followed. [05:07] LaserJock: i dont and dident volenteer to because i whole heartly agree with mdz's statement "anything thats distributable" and that falls into that category IMHO so why do i need to reply or write something ? [05:08] in other words it IS resolved untill someone oposing brings up an issue and gets a new policy [05:08] imbrandon: I didn't say you did [05:08] bahhhhhhhhh [05:08] imbrandon: I'll agree to that: I think LaserJock is only trying to start the opposition at this point. [05:09] right [05:10] all I'm saying is that it looks like the opposition to the policy was not getting heard [05:10] I'm just trying to make sure we get proper resolution to the issue [05:11] I personally agree with imbrandon, but the specific issue should be addressed by MC/TB IMO [05:11] sure i can agree to that since they dident email anyone they cant be heard, but on the other hand saying "Windows" binarys cant be in multiverse wont fly i can 1000% tell you that [05:11] you might find some other way to get that package not included but it wont be for that because all other binary only packages could be removed using the same arguments [05:12] well, I'm not going to argue about it [05:12] LaserJock: mdz is still on the TB afaik [05:12] but there were some well-respected MOTUs who disagree [05:12] imbrandon: and? [05:13] seemed like a official response to me [05:13] no it's not [05:13] mdz != TB [05:13] it dident say it was a personal opinion and it came from his ubuntu adrress to the -devel ML [05:13] pretty official [05:14] * persia doesn't think it matters, and suggests forgetting about the history of that thread, and that those interested draft an alternate policy. [05:15] * imbrandon agrees [05:15] *sigh* [05:16] * imbrandon packages Photoshop CS [05:16] and runs [05:16] that only took half an hour :/ [05:17] LaserJock: What sort of response do you seek? Do you want us to all agree with the undefined position, and argue that the current policy was badly generated, never applied, and something else should? [05:20] * bddebian packages Wolfenstein: Enemy Territory [05:20] imbrandon: That doesn't even meet the current policy :) [05:20] persia: no, I was trying to say exactly what you just said [05:20] * StevenK makes a movie called "imbrandon and bddebian must die" and then packages it. [05:20] hahaha [05:20] LaserJock: Ah. OK. I misinterpreted "*Sigh*". My apologies. [05:20] LOL [05:20] StevenK: At least mine is "free" :) [05:20] can i package Photoshop CS2 as Gimp-NG ? [05:20] bddebian: Mine can be under whatever license I want, so there [05:20] heh [05:20] imbrandon: With permission from Adobe, yes. === xopher- is now known as xopher [05:48] Gnight gang [05:48] Hey, anyone know if it's safe to build gecko-embedding packages against libxul1.9-dev yet? [05:51] Ok, given we don't *have* a 1.9 libxul package, I'll call that "no". === asac_ is now known as asac [06:37] Hi all! [06:44] RAOF: hehe [06:45] good morning [06:45] * Hobbsee stomps on midi files. [06:45] Hobbsee: Why? What did they do to you? [06:45] persia: they wont play in wine. [06:45] i dont know why. [06:45] * Hobbsee wants aoe music. [06:46] Hobbsee: Do you have a MIDI device defined in WINE? [06:46] Hobbsee: Alternately, might I suggest timidity? [06:46] persia: afaics, yes. but i may be looking in th wrong place [06:46] timidity is running - but i still never get music. [06:47] Hobbsee: Right. Do you have a soundfont installed? [06:47] persia: taht would not be in conjunction with "Just Working", i'm sure. [06:47] ie, no. [06:48] Hobbsee: I forget. I have heaps of soundfonts, and don't actually know if one is installed by default. Open a bug, and subscribe me, and I'll take a look this weekend. [06:48] okay [06:49] persia: oh, hmm, i presume i follow http://frankscorner.org/index.php?p=mid or something? [06:50] Hobbsee: I thought that timidity had an init.d that did the last step, I'm just not sure about the soundfont. That page should work though. [06:51] dholbach's here, that's my que to go to bed [06:51] * dholbach hugs LaserJock [06:51] LaserJock: sleep tight! [06:51] Hobbsee: I still want the bug, as I'll forget to investigate otherwise. [06:51] * LaserJock hugs dholbach [06:51] persia: will do [06:51] night MOTU Land! [06:51] persia: any idea wht the init.d was? [06:52] Hobbsee: /etc/init.d/timidity I think. I'm not near a useful machine now, and it was back in Dapper / Edgy I was chasing that. [06:52] ok === asac_ is now known as asac [06:56] persia: looking at the ggobi merge: can you recall by xdg/ggobi.png is converted to xpm ? [06:56] Lutin: s/by/why/ ? [06:57] If so, it's to support the Debian menu system, for e.g. fluxbox users. [06:57] persia: yep, sorry :) [06:57] persia: ah ok [06:58] Lutin: Just in the spirit of full disclosure, I don't remember ggobi specifically at all, but that's true for everything. Ideally, every GUI package has a debian menu file with a 32x32 xpm as well as a .desktop file. [06:59] ( even some non gui apps , e.g. nano do ) [06:59] :) [06:59] hehe :) [07:00] imbrandon: True. I've never really understood that. Does it call x-terminal-emulator and execute inside? [07:00]