[00:00] * minghua wonder if he should make it RC or not. [00:01] That sounds RC. [00:02] The thing is, all packages that use this library is from the same source package. [00:02] minghua: if they're in separate binary packages, that's no excuse :) [00:03] minghua: RC? [00:03] release critical [00:03] afaik [00:05] slangasek: Right. But only a small group of people use this package. I doubt if I don't report, anyone else will. And stopping the new version from migrating into testing is really worse than having this hypothetical "old version of executable segfaults with new library" issue... [00:05] mok0: TheMuso is correct. [00:05] thx [00:05] Anyway, enought (sort of) off-topic ranting. [00:05] minghua: we love rants [00:09] Google said: "Did you mean: dpkg-gang symbols " :-) [00:09] lol [00:10] Haha. [00:11] Hmm, which policy section I should cite to justify my bug's RC status... [00:12] Let's just use 8.6 and a blanket. [00:23] minghua: have you had a chance to try out torque? [00:28] mok0: No. I don't really have an cluster system to try it on, actually. [00:29] minghua: ah, you need at least two machines :-) [00:29] minghua: but the more you have, the more fun [00:30] minghua: anyway, I will fix the issues on REVU (all minor) and upload it again [00:30] minghua: It would be good to get it into hardy [00:30] mok0: That would be very nice. [00:31] mok0: You still need to persuade people about the license issue, though. [00:31] minghua: you think so? The most strange parts of the license have expired [00:31] keescook, ping [00:32] emgent: pong [00:32] keescook, weel patch is done but i have some problem with phpbb package. [00:32] minghua: "After December 31, 2001, only conditions 3-6 must be met" [00:32] mok0: Yes, I feel it's good for universe, but I'm no license expert. [00:32] keescook, http://rafb.net/p/5MIUqV62.html [00:33] minghua: neither am I [00:33] mok0: And my opinion hardly matters. [00:33] emgent: I'd communicate with upstream first, and once there is an approved upstream patch, then worry about package builds. === macd_ is now known as macd [00:33] minghua: but there must be somebody who can make a qualified decision? [00:33] ok cool. [00:33] minghua: perhaps an Ubuntu member? [00:34] i go to mail phpbb's people [00:37] mok0: An archive admin, usually. [00:38] minghua: perhaps I can ping one and discuss it [00:38] * minghua doesn't think it's a good idea. [00:38] why? [00:40] They are busy, and they may not be acting archive admin duty today. [00:41] Just IMHO anyway, feel free to ping one if you want. [00:44] minghua: It's probably better to get the package in good shape, and get it processed the normal way. [00:49] mok0: Yes, that's my preference. You can always ask an archive admin to review the license before uploading (or once it's in NEW queue). [00:49] minghua: great. [00:50] mok0: By the way, "Ubuntu member" is a group with very low threshold: https://launchpad.net/~ubuntumembers [00:50] mok0: You can become one if you want. [00:50] minghua: Ah, i thought that was the exclusive group of canonical employees [00:51] * minghua thinks that group is simply called "Canonical employees". :-P [00:52] mok0: minghua; heh, I will try to join the ubuntu-member team, then [00:53] 352 active members, 852 proposed members :-) [00:53] lol [00:53] mok0, good luke :P [00:53] emgent: thanks I need it :-/ [00:53] i will try to motu [00:54] me too [00:54] motu include ubuntumembers [00:55] mok0, I think that is good Continue on this road [00:55] emgent: by the time the team adminstrators get through the list of 852 applicants, I will be a developer, lol [00:55] ahahahaha [00:55] * emgent nod [00:56] mok0: that's handled differently. You need to present your application to the Community Council, and they will either approve you or not. [00:56] pochu: yes I know, just kidding [00:56] but in this council meeting there are news about approvation [00:56] mok0: heh, ok :) [00:57] pochu: I plan to submit my motu-application later this spring [00:57] Good luck! :) [00:57] pochu: heh, thanks [00:57] pochu: it takes more hard work than luck I'm afraid [00:58] mok0, https://wiki.ubuntu.com/CommunityCouncil/Delegation [00:58] mok0: You're afraid? That's a good thing! [00:58] fast procedure [00:59] pochu: nothing to motivate like fear [00:59] dholbach++ [00:59] * pochu goes to study [01:00] bye pochu [01:00] bye === gnomefre2k is now known as gnomefreak === tritium_ is now known as tritium [01:35] Hiya, I'm trying to make a .deb with checkinstall for vmware-tools so I don't have to install the build-deps on a JEOS. I don't suppose anyone has already succeeded in doing that? [01:36] checkinstall is not supported in here. [01:36] Hopefully, it isn't supported anywhere, but that isn't likely. [01:37] StevenK: Is there a better way? [01:37] StevenK: well, you were the one who stopped it segfaulting. [01:37] owh: There is, but I've not managed to get vmware-tools packaged sanely. [01:38] It makes lovely assumptions, and fails if builder != host [01:38] If I recall correctly, it's been a while since I looked. [01:38] Ah, niiice :| [01:39] So, I get to install the build-deps, mount the .iso, extract the .gz, build it, delete the extracted dir, unmount the .iso and purge the build-deps? [01:39] owh: the tools do a bit of host-specific kernel module compilation too so checkinstall will also NOT be able to deal with it [01:40] owh: it's going to be complex to repackage and it might not even be legal for us to mangle their sources in this fashion [01:40] All I really care about is that I can sanely shutdown a vm-guest, don't care about anything else. [01:40] jdong: who said anything about us building it? [01:40] What Hobbsee said. [01:41] As opposed to powering it down :) [01:41] * Hobbsee notes one can do that with virtualbox with no problem [01:41] Hobbsee: checkinstall implies it. I'm just giving another reason why checkinstall will fail miserably in this application [01:41] jdong: We're talking about the guest tools here, not the server tools right? [01:42] Hobbsee: Yes, but then I'd have to deploy a whole new range of tools and given where I am right now, that's not an option :_( [01:42] owh: right, the guest tools [01:42] jdong: I didn't see any kernel module stuff going on. [01:42] owh: ah right [01:42] owh: I could've sworn there's kernel modules involved... [01:43] owh: maybe I'm wrong and it's just binary Xorg drivers [01:43] jdong: sure you're not confused with virtualbox? that has kernel modules [01:43] owh: do the terms of licensing permit repackaging? [01:43] jdong: AFAIK that's the vmmon/vmnet stuff for the server. Could be the X stuff. [01:43] Hobbsee: no, I was thinking of some redhat clients I deployed last summer [01:43] jdong: Dunno, this is in-house between guests on one server. [01:43] jdong: ahhh [01:44] owh: why can't you just install linux-headers-generic build-essential and proceed from there? [01:44] I don't see why it has to be rolled into an awful deb package [01:45] jdong: I can, but I'm trying to keep my jeos deployment simple. If I need to build a vm, then install depends, extract stuff, compile and remove things, my 4 minute automatic new machine deployment becomes a manual nightmare. [01:45] owh: why not deploy the systems as tarballs of preconfigured systems? [01:45] owh: or other forms of image cloning.... I don't see how deb packages would even simplify your life :) [01:46] owh: or modify the install script (perl) to automatically apt-get the dependencies and remove them afterwards [01:46] jdong: Because deploying tarballs makes maintaining the tarball a manual mess. [01:46] I think you'll waste more time trying to package the tools sanely compared to just rolling it out [01:46] jdong: Modifying the perl script is an idea. [01:47] Sigh, so much to do and so much time being wasted in mundania :( [01:47] you will need a custom package of some sort. A custom deb package you have to craft vs modifing a perl script and re-rolling the tools tarball? [01:47] I think the latter is much much easier [01:47] jdong: Thanks for your thoughts, I'll take a break and have another look at it. [01:48] owh: sure thing, good luck :) [01:48] :) [02:04] Heya gang [02:05] Aloha bddebian. [02:05] Hi RAOF [02:13] Ok it built. [02:13] Now to disect the debs. [02:13] woops wrong channel [02:18] TheMuso: I think you mean dissect. I'm pretty sure disecting involves cutting in half.... [02:18] TheMuso: though if they were automatix debs... [02:19] jdong: Whatver. :p Basically pulling them appart. [02:19] dict doesn't know about disect [02:19] Well my typing hasn't been the best on this keyboard lately. I think it needs replacing. [02:39] Yay, cool. Looks like monodevelop can be sync'd soon. [02:45] RAOF_: yay! === RAOF_ is now known as RAOF [02:47] is there a LP dgettable URL that's aliased to the latest version of source package foo for distro bar? [02:47] or am I still gonna have to regex-scrape for that? *grumble* [02:57] jdong: There isn't one for the latest, but one can add /+files on the end of any SourcePackageRelease URL to get dgettable .dsc. [02:58] Fujitsu: mmmkay I'll just navigate to $release/+source/pkgname and scrape for a dsc to dget :) === tritium_ is now known as tritium === xhaker is now known as xhaker_ === bigon is now known as bigon` [03:33] Can I regexp the search expression in grep? I want to find every instance of SDL_*.h ? [03:34] That's a glob, not a regex [03:35] its a regex [03:35] OK, can I use globs then? :) [03:35] but the regex won't do what you want :) [03:35] Oh right. [03:35] Unless you want to find e.g. SDL.h and SDL____________________________________.h :-) [03:35] and SDLKh [03:35] Oh, and SDL__Xh [03:35] bddebian: grep -E 'SDL_[A-Za-z]*.h [03:36] ' [03:36] OK, OK, I get it, how can I do it.. Sheesh :) [03:36] Ah, thx StevenK [03:36] egrep 'SDL_[\w]+\.h' [03:36] * StevenK recommends bddebian actually read grep(1) [03:36] perhaps [03:37] No need to put [] around \w [03:37] bleh true [03:37] StevenK: Well I knew I could, I just completely suck at regexp :-( [03:37] actrually, 'SDL_.+\.h' is really what is wanted [03:38] Also, to avoid matching fooSDL_bar.hz, add \< \> around the expression. [03:39] 399 files changed, 26415 insertions(+), 107889 deletions(-) [03:39] * StevenK sobs [03:39] Hehe. What is that? [03:40] A diff between two Pidgin trees [03:42] StevenK: Is that a micro-release? [03:42] Nope. [03:42] Ah. Boring then. [03:50] morning * [04:01] Goddamnit, why does adonthell have it's own SDL headers.. Grrr [04:52] StevenK: Still around? [05:09] ScottK: I might be. [05:10] StevenK: I need a core-dev to do a source backport for clamav to close a remote execution vulnterability. It's a small change. Would you be up for an upload in ~20/30 minutes after I'm done testing? [05:15] ScottK: I could be convinced. [05:15] OK. [05:15] * ScottK will finish testing and then work on convincing. [05:16] heh [05:23] You have: 900000000000000 seconds [05:23] You want: millennia [05:23] * 28519.888 [05:23] I don't think so, dmb [05:24] lol [05:28] hahaha [05:30] StevenK: The debdiff (from the current version in gutsy-security) for feisty-backports is in Bug #181830. [05:30] Launchpad bug 181830 in feisty-backports "CVE-2007-6337 Unknown impact remote attack" [Undecided,Confirmed] https://launchpad.net/bugs/181830 [05:31] StevenK: Would you please be so kind as to upload that? === mdomsch is now known as mdomsch_zZ [05:47] good morning [05:48] Hey dholbach. [05:48] Good mornging dholbach. [05:48] morning even [05:49] hey TheMuso, hey ScottK! [05:49] how are you doing? [05:49] dholbach: The other MC members +1'ed \sh while you were out, so you can give him a nice birthday present today. [05:49] morning dholbach :) [05:49] ScottK: working on it [05:49] hey emgent [05:49] Cool [05:50] Rock and Roll! (an beer) [05:50] heheh [05:50] Good night all. I'm off to bed. [05:50] sleep tight! [05:50] ScottK, see you later [05:52] \sh_away: Congratulations and Happy Birthday. [05:53] Good night again. This time really. [05:53] \sh_away: and the same from me - and welcome back to the team :) [05:54] dholbach: I'm great thanks. === _czessi is now known as Czessi [07:25] p/c [07:25] ugh === DarkMageZ_ is now known as DarkMageZ [07:27] hello, how do I make a patch for a diff.gz ? [07:27] I mean a diff between 2 diff.gz files [07:28] apologies if this is off-topic, but can anyone check if sourceforge cvs is broken? I'm getting "cvs [checkout aborted]: connect to cvs.sourceforge.net(66.35.250.207):2401 failed: No route to host" on 2 different hosts... [07:28] AnAnt: gunzip them and then interdiff them [07:28] Hello. I have uploaded a package to revu and I'm wondering if i made any mistake beause the package is not comment by anyone [07:28] ok [07:28] The name of package is gnomecatalog [07:29] Chipzz: telnet: Unable to connect to remote host: No route to host [07:29] Chipzz: aren't they phasing out CVS in favor of SVN ? [07:29] AnAnt: no idea really... [07:30] the weird thing is [07:30] tcptraceroute 66.35.250.207 2401 actually *does* work [07:31] wierd [07:31] StevenK: thx, same as I was getting apparently [07:31] svn isn't working even [07:32] what I was actually trying to do is checkout the cvs version of gitk [07:33] because I was wondering if there was a reason we ship the tcl/tk version when gitk cvs has a gtk+ front-end [07:33] (was going to look into what version gitk cvs was etc...) [07:34] hrrrrm [07:34] * Chipzz slaps self [07:36] ignore what I just said [08:06] Fujitsu: could you please enable a "Ruby-related packages" list on http://qa.ubuntuwire.com/~fujitsu/mdt/? [08:07] Fujitsu: and a "Java-related packages" list... [08:08] Fujitsu: listing all packages that have binary packages that (indirectly) depends on libruby1.8 or libruby1.9 would be enough [08:13] man-di: How would I determine that? [08:13] lucas: Doing so. [08:13] Hello. I have uploaded a package /to revu and I'm wondering if i made any mistake beacuse the package is not comment by anyone. The package is http://revu.tauware.de/details.py?package=gnomecatalog [08:16] josesanch, no mistake... I'm too waiting for someone to review my package [08:16] this one btw: http://revu.tauware.de/details.py?package=speed-game [08:16] amarillion Thanks. I'm a newbie in this [08:17] me too :) [08:17] But it seems that it takes a while to get your package reviewed [08:22] lucas: That's a lot of packages. [08:24] Fujitsu: a few hundreds, no? [08:25] josesanch, I'm looking at your package right now [08:25] lucas: The recursive rdepends of libruby1.8 are enormous. [08:25] is it in Debian already? [08:25] No, is not in debian. [08:25] ok, then you need to use 0ubuntu1 as package version number [08:25] ahh. [08:26] Also, is this a native package? I don't see an orig.tar.gz [08:26] You can ignore the linda error: gnomecatalog; 3.7.3 is a newer Standards-Version. [08:26] everyone is getting that [08:26] But you definitely need to fix this one: E: gnomecatalog_0.3.1-1.2_source.changes: bad-distribution-in-changes-file hardy [08:27] amarillion gnomecatalog-0.3.1-0ubuntu1 ? [08:27] I suspect that it goes away once you use "ubuntu" in the version number [08:27] Ahhh.. [08:27] josesanch, exactly. Whenever gnomecatelog is added to debian, it will get gnomecatalog-0.3.1-1 which is higher than 0.3.1-0 [08:28] so it will be automatically overriden when added to debian [08:28] I don't know why then orig.tar.gz is not there [08:28] It must be there [08:28] :) [08:28] Well, it looks like i have work todo with the package [08:28] Did you package with debuild -S -sa [08:28] ? [08:28] Yes, i think so [08:28] morning dears motus [08:29] oh then I don't know why that is happening [08:29] hi huats [08:29] I'll make the chages you comment me and will submit again [08:30] josesanch, ok, good luck [08:31] amarillion Thanks a lot [08:31] I will be back :) [08:32] nxvl: ping [08:34] Fujitsu: a good start would be to look in Maintainer and XSBC-Original-Maintainer for "Debian Java" [08:34] Fujitsu: that doesnt find all of them as some are not maintained by debian java team [08:35] Fujitsu: in debian you can search the tags for "lang:java" but I dont know if Ubuntu has that tagging yet too [08:36] GOod point. Anybody know why we don't have such tags? === \sh_away is now known as \sh [09:15] <\sh> moins [09:15] <\sh> and THANKS A LOT good to be back :) [09:40] <\sh> was someone working on the final debdiffs from che regarding the libgif transitions? [09:42] \sh: Congratulations! Great to have ou back! [09:43] <\sh> TheMuso: thx :) [09:45] <\sh> cool....all my libgif stuff uploaded... [09:46] <\sh> thx dholbach [09:51] StevenK: AnAnt: interdiff has a -z option to save on the unpack. [09:51] Aww [09:52] * StevenK will have to remember that [09:52] Fujitsu: If you're updating mdt feeds, could you also look at the links on the main mdt page? Some of them seem odd. [10:03] amarillion. I have uploaded a new version, now with orig.tar.gz [10:08] * rzr fixed http://revu.tauware.de/details.py?package=jaaa [10:11] josesanch, yeah. looks better [10:11] rzr: Could you do a quick bounce of -0ubuntu1 in preference to -1ubuntu1? I'd be happy to take a look, but know that needs to be fixed before even digging in. [10:11] btw, my package speed-game (http://revu.tauware.de/details.py?package=speed-game) has been fixed too [10:12] * josesanch fixed http://revu.tauware.de/details.py?package=gnomecatalog === cassidy_ is now known as cassidy [10:14] persia: sure [10:15] * persia recommends that josesanch review speed-game whilst amarillion reviews gnomecatalog. persia will review whichever one of the packages that escapes unscathed [10:15] hehe, so I have to find a fault in gnomecatalog otherwise you won't review my package? [10:16] dirty tricks... [10:16] well, let me take a look then [10:16] amarillion: Something like that. I like to think of it as an incentive for collaboration :) [10:17] persia: Ok.. i am going to review it right now [10:18] Excellent! The game is on... [10:18] btw I already did one quick review of gnome-catalog earlier. Just so you know that I really am willing to help out. [10:19] amarillion: I don't doubt it. Few without that attitude come here :) I just only feel like a couple reviews this evening, and so proposed this to pick the second of them. [10:20] It's actually not a bad way to go about this. A little machiavellian... but with good results. [10:21] superm1: I don't suppose I could convince you to move more of the mythbuntu packages to multiverse to make debcheck happy, could I? [10:24] if some kind soul would care to look over http://revu.tauware.de/details.py?upid=1212 I believe I have addressed all of the comments now :) [10:24] * persia wonders if anyone would like to pair with Ng [10:24] Ah. A clue to find more. [10:24] amarillion: the game is very cool [10:24] persia: well I have this warning "Description: The menu file has section Applications, which is unknown." [10:25] it has two warning that have mine package too Maintainer: does not have Ubuntu address and there is no XSBC-Original-Maintainer field [10:25] rzr: That's because revu isn't using the newest lintian (I suspect). Check again against lintian 1.23.41 [10:26] /exec -o lintian --version [10:26] Lintian v1.23.41 [10:26] on my system .. [10:26] debian tough [10:27] Uploads unique to Ubuntu should have an @ubuntu.com maintainer. You can assign maintenance to the MOTU team with Maintainer: Ubuntu MOTU Developers (but we like XSBC-Original-Maintainer when assigned maintenance, and appreciate help) [10:27] josesanch: Maybe it needs to be Applications/Something? [10:27] I don't suppose there is a google calender version of the gutsy release schedule, I see there is a iCal version [10:27] s/gutsy/hardy [10:27] grep section debian/jaaa.menu [10:27] section="Applications/Sound"\ [10:28] persia: application/accesories [10:28] josesanch: s/Application/Applications/, I suspect. [10:28] josesanch, thanks, I didn't write it myself [10:29] thanks persia i'm going to do that changes [10:29] persia: do you know how can I make a custom automake rule available system wide? [10:30] promag: No. Also, why me? Also, why #ubuntu-motu? Also, why would that even be interesting? [10:31] rzr: Umm. I asked for "0.4.2-1ubuntu1" -> "0.4.2-0ubuntu1". The new candidate is "0.4.2-1ubuntu2". [10:32] why you? because you're a nice person :P why #ubuntu-motu? becase #devtools is like a dead channel and because here are intelligent ppl... and it would be interesting to me :) [10:32] it's because of the distortion in the channel :) [10:33] sorry [10:33] Aha. Always be sure the communication channels are at right angles to the power channels, and you'll be safe. [10:33] now I open my eyes :) [10:34] let me fix this [10:34] rzr: Oh, goot catch on the security issue. -13 looks much nicer :) [10:34] yea [10:35] I waited it to enter testing to comment the bug [10:35] i wanted to wait .. [10:36] persia: in what file have to change application by applications/ ? [10:36] josesanch: menu [10:36] josesanch: w/ a "A" [10:37] persia: should I also upload whitedune to revu ? [10:37] section is now Apps/Tools i have to change by Applications/Tools? [10:37] rzr: Isn't that in Debian? [10:38] it is [10:38] I did the job [10:38] josesanch: Right. There was a policy change between gutsy and hardy for menu structure. [10:38] rzr: I thought I remembered a sync request. No need to send to REVU. [10:38] ok [10:39] anyway my priority is on jaaa, and will be unicorn before whitedune [10:39] rzr: Just watch the sync request, and make sure it gets synced in the next couple weeks, or it likely won't make hardy. [10:41] Hey josesanch, I get a few lintian errors when I try to build your package [10:41] e.g E: gnomecatalog: extended-description-is-empty [10:42] and E: gnomecatalog: copyright-should-refer-to-common-license-file-for-gpl [10:42] for the last one you can simply refer to /usr/share/common-licenses/GPL3 [10:42] amarillion: Thanks, i'll to review that [10:43] jdong: s/disect/bisect/ [10:47] how long does it take for an uploaded package to appear on the REVU website? [10:47] rulus, a few minutes usually [10:47] ah, thanks :) [10:47] rulus: between 2 and 12 minutes. [10:47] provided that your GPG key is added to the revu list [10:48] I had that problem a few days ago [10:48] I think it is, dput said that the upload was succesfull [10:49] it depends on when you subscribed to the Universe contributors team [10:49] I am [10:49] :) [10:50] already a few weeks, so that should be not problem [10:51] rzr: jaaa commented. [10:51] amarillion: josesanch: did either of your packages survive? [10:52] I'm making a new one with the Maintainer set to the motu list [10:52] persia: > I like ALL_CAPS for make variables. [10:52] then I can set XBC-Original-Maintainer set to me right? [10:52] inkblot, which passed REVU, was rejected on the grounds that it lacked the text of the LGPL for eggtrayicon.{c,h}. I was asked to repackage the orig.tar.gz and add it. Now here's the question: [10:53] persia: UPCASE_VAR are for conventional vars ... locase_one are for private usage [10:53] If it's "LGPL 2 or later", which version should I add - 2, 2.1 or 3? [10:53] s/XBC/XSBC/ [10:53] FYI, I've read that somewhere on the wide internet :) [10:53] rzr: Depends on how one defines "private" :) [10:54] LucidFox: Depends on how you want to license it to others (based on the license you received). -2 grants your endusers (the distribution, and it's users) the most flexibility. [10:54] for me private refer to something isnt wrote on some public paper .. [10:54] persia, can I ignore this: warning, `debian/speed-game/DEBIAN/control' contains user-defined field `Original-Maintainer'? [10:55] amarillion: Yes. I thiought that was taken away for -XubuntuY. Hrm. [10:55] The license headers mention "Lesser GPL 2 or later", but version 2 is called "Library GPL" - it was renamed to Lesser in version 2.1. Does this affect anything? [10:56] josesanch, did you find more problems with my package? [10:56] LucidFox: That might deserve clarification with upstream. If there is no "Lesser GPL 2", then you may not have a good guide as to what license you received, which may impact your ability to extend a license to Ubuntu. [10:57] No.. [10:57] But i'am not an expert :) [10:57] * persia notes that this technicality of the packager providing the license to the distribution, which the distribution then uses to provide licenses to end-users is why having the name of the original packager in debian/copyright is useful. This doesn't apply in all jurisdictions of course... [10:58] But the author of inkblot is not the author of eggtrayicon. It's found in many sources. [10:58] josesanch: Don't worry that you're not an expert. I learned half of what I know about reviewing from lintian and linda. [10:58] jejeje [10:59] this reminds me: persia, why did you suggest the ISC license earlier? [10:59] LucidFox: In that case, it may be that the author of inkblot needs clarification regarding the license extended to you. Such recursion may be even more levels, depending. This is why precision in licensing is important. [10:59] amarillion, persia: it has appeared :) [10:59] When I needed to add the text, I couldn't find a good source for it [10:59] ISC doesn't seem to be very well documented [10:59] amarillion: For people without an existing relationship with the Regents of the University of California, it's easier to use than BSD. [11:00] amarillion: The full license is three paragraphs, quoted entire in the wikipedia entry. [11:00] Well... I couldn't find exactly how to do it so I just copied the text from the dhcp package [11:00] Now looking at the rhythmbox source, and it only includes the text of the GPL, even though it also includes eggtrayicon.{c,h} [11:00] amarillion: Also, I don't recommend ISC as a blanket license. It's not right for everyone. I just think it's a better choice when people are considering a BSD license. [11:01] It's just that after googling I found this: http://ictlab.tyict.vtc.edu.hk/pub/tarball/dhcp-3.0b2pl3/ISC-LICENSE which confuses me. It's a lot more text [11:01] LucidFox: Write up your research, and forward it with your rejection note to cjwatson. A test case was sought earlier on this. [11:01] persia: from lintian i don't have warnings but for linda i have a 3.7.3 is a newer standards-version [11:02] There doesn't seem to be documentation from the ISC itself [11:02] amarillion: When I say "ISC license", I mean that listed at http://en.wikipedia.org/wiki/ISC_licence [11:02] ok [11:02] but I don't think you should recommend that one over BSD [11:02] not anymore [11:02] it's too unclear [11:03] josesanch: linda is currently experiencing the bends (issues with decompression), and has not yet become aware of the new standards version. [11:04] amarillion: The "BSD" license requires copyright assignment to the Regents of the University of California, which is not even possible in many jurisdictions. I think using ISC is preferable to drafting a new license based on the BSD license. [11:04] Also, I don't see what is unclear. It states who holds copyright, what the licensee is entitled to do with the work, and provides a disclaimer of liability. [11:07] The text on wikipedia is very clear. To me, what is unclear is: who is the ISC? Why is it a good idea to use their text when almost nobody else uses it? Which text do I use exactly (you didn't refer to the wikipedia entry explicitly before, and just googling for ISC license comes up with contradictory results) [11:08] mpeg4ip rejected again? Nnnnnoooooo [11:10] amarillion: Internet Systems Consortium. (#2 in Google for "ISC"), and the wikipedia entry is #1 in Google for "ISC license". It's used by heaps of stuff, but it is fairly new, so there's not so much talk about it, and a lot of people consider it a "modified BSD", so it falls into the "BSD-style" licenses in many discussions. [11:10] * persia grumbles at ISC for being "Internet Systems Consortium" and "Internet Software Consortium" both housed at isc.org :( [11:11]