[00:10] <wgrant> pwnguin: It's not too crazy. Just adding another two limitations on top of the GPL.
[00:10] <wgrant> (which GPL? we'll never know)
[00:11] <wgrant> Multiverse or loony-bin material at any rate.
[00:29] <azzco> Isn't it Gnu general public license and not Gnu public license?
[00:52] <wgrant> azzco: Neither. It's the GNU General Public License.
[00:53] <azzco> Sorry bout that wgrant, I usually spell it like that though..
[00:57] <Ng> wgrant: loony-bin, it's invalid, GPL says no additional restrictions
[00:57] <Ng> imho, ianal, etc
[00:58] <emgent> geta wgrant Ng
[01:00] <wgrant> Ng: Doesn't the GPL just say that derivatives of the licensed body cannot have additional restrictions?
[01:01] <Ng> wgrant: I'm looking at section 10, paragraph 3 of the GPL
[01:01] <wgrant> I've not come across such a strange case as this before, so don't remember the wording of that bit.
[01:02] <wgrant> Hmm.
[01:02] <wgrant> I think the licensor is permitted to do it, but it might not be redistributable.
[01:03] <wgrant> That seems odd, though.
[01:04] <Ng> if it's not redistributable then it's not free software aiui :)
[01:04] <wgrant> Right, it would belong in multiverse if anywhere.
[01:05] <wgrant> Loony-bin it is, I think.
[01:21] <emgent> Ng: do you have an access to manage ubuntu.com mail alias?
[02:15] <pwnguin> technically, i think you can redistribute it to other people under the gpl
[02:15] <pwnguin> it'd take a lawyer to figure out whether the non commercial clause came along with it
[02:16] <pwnguin> it's so batshit insane that I'm going to write him
[04:48]  * cody-somerville is at last home from Prague.
[04:48] <johanbr> Nice. Long flight?
[04:50] <cody-somerville> 17 hours
[04:55] <johanbr> Pretty long, but still in the tolerable range.
[04:56] <jdong> that's what *cough* *resist.....*
[05:35] <wasssups> just ah .... with ubuntu hardy did you lock down the amount of threads / forks a user can do--- my crashme testing suggest this to be the case..
[05:40] <jdong> wasssups: no, that's up to the individual system administrator to set
[05:41] <jdong> maswan: there's really no global values that suit everyone's workloads.... limits.conf makes it easy for an admin to make such decisions locally
[05:42] <wasssups> that is my default apparently ...
[05:42] <jdong> wasssups: the default does not.
[05:42] <jdong> wasssups: you can definitely forkbomb the default to death.
[05:42] <jdong> unless the CFS scheduler in the non-patched kernel sucked *THAT* much (grin)
[05:43] <wasssups> well it seems to fork out
[05:44] <jdong> ok I just DoS'ed a hardy VM to make sure.... it definitely forks enough that sshd no longer talks to me
[05:44] <jdong> just a simple bash forkbomb too
[05:47] <wasssups> jdong: yeah but you can still run stuff
[05:47] <wasssups> crashme hits a limit way below what it should
[05:47] <wasssups> i will try again
[10:39] <lifeless> the gnash mozilla plugin doesn't register itself for mozilla 3
[10:39] <lifeless> asac: ^
[10:40] <cyberix> About the development process. A certain bug for a package in main component has been confirmed to exist on various platforms and a fix has been released to the bug thread. What should happen next? Who is responsible for releasing an update for a package?
[10:40] <lifeless> asac: seems to be trivially fixed by adding firefox-addons into the list of things to add alternatives for
[10:43] <persia> cyberix: If the fix is not yet in the form of a candidate update, anyone is welcome to continue the process to make it so.  If the fix is in the form of a candidate update, it falls to ubuntu-main-sponsors to review the candidate and upload (for most bugs) or ubuntu-sru to review and approve (for bugs in previously releases)
[10:43] <cyberix> There are actually two fixes. A patch and an updated package from Debian.
[10:44] <cyberix> Which one should be preferred?
[10:44] <persia> cyberix: Depends entirely on the content of each.  There is no rule about the source.  Use of the Debian patch is often easier in terms of later maintenance, so it is preferred if it is also correct for Ubuntu.
[10:46] <cyberix> persia: May I quote this discussion directly in a follow-up comment?
[10:47] <persia> cyberix: If you really, really want to.  Which bug?
[10:47] <cyberix> https://bugs.launchpad.net/ubuntu/+source/obex-data-server/+bug/211252
[10:48] <juliux> hey persia
[10:48] <persia> juliux: Good day
[10:49] <tseliot> ﻿persia: hi ;)
[10:58] <persia> cyberix: No point adding to that conversation.  slytherin seems on top of it.  It likely ran against a freeze block, and will be modified to work for intrepid soon.
[10:59] <persia> cyberix: Given the mixed responses in the thread, I'm really not sure it would be best for all users to apply as an SRU, but that's something that could be tested once it is fixed in intrepid.
[11:02] <tseliot> emgent: are you there?
[11:43] <lifeless> anyone with an x86 care to test the better-stack-traces patch in an ubuntu build?
[11:43] <lifeless> https://bugs.edge.launchpad.net/ubuntu/+source/gdb/+bug/111869
[11:44] <lifeless> and with that, /wave
[11:44] <StevenK> lifeless: Come find us!
[11:45] <lifeless> StevenK: I shall; where are you lurking ?
[12:19] <Samsemilia> !seen dholbach
[12:27] <jdavies> !seen > Samsemilia
[12:28] <Samsemilia> jdavies: thanks
[12:54] <yannick> Is it the right channel to discuss packaging issue? or should i try #ubuntu ?
[12:55] <Festor> yannick, #ubuntu-motu
[12:55] <yannick> ok thx
[13:27] <emgent> heya
[13:41] <tseliot> emgent: check your email
[13:52] <emgent> tseliot: Yeah i saw :)
[13:52] <emgent> just a moment ehehe :P
[13:52] <tseliot> no problem
[13:55]  * emgent sending..
[14:01] <emgent> tseliot: done :)
[14:04] <tseliot> ﻿emgent: thanks :-)
[14:04] <emgent> np
[14:05] <emgent> tseliot: http://en.emanuele-gentili.com/wp-content/uploads/2008/05/img_2655.jpg
[14:06] <tseliot> five a day!!! In all senses
[14:07] <tseliot> :-P
[14:07] <emgent> hahahah sure
[16:02] <siretart> pitti: I'm currently working on the cryptsetup merge
[20:57] <Riddell> pitti, doko: mind about the KDE 4 MIRs if you're not on holiday tomorrow, pretty important that we can get started on KDE 4 properly