[01:37] <ScottL> TheMuso, ubuntustudio-look
[01:37] <TheMuso> ScottL: Yes, but your branch, the ubuntustudio-dev branch, which one?
[01:50] <ScottL> TheMuso, revision 35 should be mine, is that the information you need?
[01:50] <ScottL> under lp:ubuntu/ubuntustudio-look
[01:55] <ScottL> i tried to answer quick like before I took a shower and I realized I was being an idiot in the shower, sorry 'bout that
[02:03] <TheMuso> ScottL: ah ok
[02:07] <TheMuso> ScottL: the branch you mentioned does not have your changes. lp:ubuntu/ubuntustudio-look is a bzr mirror of the ubuntu archive.
[02:23] <ScottL> TheMuso, ah, so I'll have to use the ubuntustudio-dev branch, okay...i'll try to get it later tonight after all the kids are in bed
[02:23] <TheMuso> ok
[02:24] <TheMuso> ScottL: no I just need to know where to pull your changes from.
[02:24] <ScottL> that explains why only members of Ubuntu Branches could only push to it
[03:26] <TheMuso> ScottL: Seems you didn't add the files needed for the plymouth theme.
[03:26] <TheMuso> You added the bits to install the plymouth theme, but not the theme itself.
[03:26] <ScottL> hold on, let me go back upstairs
[03:27] <TheMuso> sure
[06:36] <astraljava> TheMuso: Thanks for adding me to the LP team! :)
[08:01] <jussi01> Our default settings page, what does that ch
[08:01] <jussi01> Our default settings package, what does that change?
[08:02] <TheMuso> jussi01: The theme for the desktop, terminal colours, wallpaper.
[08:03] <jussi01> TheMuso: ok. so it actually changes config files? (Im thinking of suggesting it as a template for a group who need to change the default IRC channel on their distro, suitable?)
[08:03] <TheMuso> jussi01: Depends on the IRC client.
[08:04] <jussi01> s/distro/derivative/
[08:04] <jussi01> TheMuso: xchat
[08:04] <TheMuso> jussi01: Because it mostly deals with setting gconf keys.,
[08:04] <jussi01> oh
[08:04] <TheMuso> jussi01: Not sure this would help then, as this is mostly gconf
[08:04] <jussi01> TheMuso: bug 513915
[08:04] <TheMuso> jussi01: Right don't know xchat.
[08:28] <astraljava> jussi01: xchat stores the default channel in .xchat2/servlist_.conf, in server section, under J=<channel> option.
[08:29] <astraljava> jussi01: So, I would guess that creating such a file under /etc/skel should take care of the problem.
[08:34] <TheMuso> astraljava: thats a hacky solution.
[08:34] <TheMuso> The defaults need to be set somehow in the package itself, or a default configuratino file that can be owned by different packages.
[08:35] <astraljava> TheMuso: I know, but I don't know xchat that well to come up with a better one. :)
[08:40] <jussi01> hrm: was asked "Can you recommend a good Linux native audio plugin for real time glitch effects?"
[08:40] <jussi01> anyone?
[08:44] <astraljava> No idea, sorry.
[10:36] <persia> jussi01: You can't do it for xchat, unless you patch xchat to have more system defaults.
[10:37] <persia> Specifically, there's a default config in the package and per-user config, but no per-host config, and no means of adjusting the default config on a per-host basis.  It is a requirement for a working foo-default-settings package for there to be such a mechanism.
[11:04] <ScottL> jussi01, ladspa has an "scratchy" effect, like the sound of an old record playing on a turn table, don't remember the actual name of the effect but I could find it pretty quickly i think if you would like
[11:08] <ScottL_> i see that TheMuso merged the plymouth theme into ubuntustudio-looks    yay!
[11:11] <astraljava> Good morning ScottL_! :)
[11:12] <ScottL_> good morning astraljava , how are you this morning?
[11:14] <astraljava> I'm good, thanks for asking. Debugging some stuff at work atm. Gonna have lunch soon. And you?
[11:15] <ScottL_> just got up and dressed for work, have fifteen minutes before getting kids up and then leaving for work
[11:15] <astraljava> Right'o. Have fun!
[11:15] <ScottL_> jussi01, the ladspa effect that I mentioned is VyNil I believe
[11:26] <ScottL_> astraljava, do yo work on ubuntu or linux at work?
[11:45] <astraljava> ScottL_: linux, mostly. Maemo stuff.
[13:15] <Scott-work> quadrispro, way to go on the sooperlooper bug!
[13:16] <Scott-work> after reading you and persia talk I didn't think it would get fixed
[13:18] <persia> It won't.
[13:18]  * persia files a bug for archive removal
[13:19] <persia> Ohy, nifty.  Can just move to multiverse :)
[13:20] <quadrispro> ehya guys! nice to see you
[13:21] <quadrispro> what's the problem?
[13:21] <persia> Non-commercial in universe
[13:21] <quadrispro> sooperlooper?
[13:22] <persia> Yeah.
[13:23] <Scott-work> so, we have the latest version of sooperlooper but it will probably move out of universe into mulitverse?
[13:24] <Scott-work> and will this effect Ubuntu Studio release in any way?
[13:24] <quadrispro> ah yep, now i get it! sorry, but the fever doesn't allow me to understand things quickly :)
[13:24] <persia> Scott-work: Yeah, I just filed the bug to move it.
[13:24] <persia> I don't believe we can include it on the CD, although I may be mistaken.
[13:24] <persia> Err, DVD
[13:26] <persia> quadrispro: Are you sure none of the GPL stuff links against that file?
[13:26] <quadrispro> just a moment please
[13:30] <quadrispro> doing some checks
[13:31] <astraljava> quadrispro: Do write with my name on it. :D
[13:31] <astraljava> one
[13:33] <quadrispro> persia, I'm not sure, we should investigate
[13:34] <persia> quadrispro: Would you file an RC bug in the BTS about it?  That usually gets someone to investigate.
[13:34] <persia> Because if it does, it needs to get removed or patched away.
[13:34] <quadrispro> yep
[13:35] <persia> Thanks.
[13:36] <persia> And we'll just stick in multiverse until it gets sorted.
[13:37] <Scott-work> a few questions please:   what does RC and BTS stand for?
[13:37] <Scott-work> is this something that _might_ be sorted before lucid release?
[13:38] <persia> Scott-work: RC is Release Critical.  BTS is the Bug Tracking System.  These usually reference Debian terms.
[13:38] <Scott-work> ok, thanks!
[13:38] <persia> So quadrispro is filing a bug regarding the Debian squeeze release.
[13:38] <persia> And I filed a *diffeent* bug to put it in multiverse for lucid.
[13:40] <Scott-work> if things are not sorted before lucid then I take it that sooperlooper cannot be released in lucid, even an older version that might be considered in the universe?
[13:41] <persia> The newer version was already published.
[13:41] <quadrispro> make[6]: Entering directory `/build/buildd-sooperlooper_1.6.14-1-amd64-wwBn5r/sooperlooper-1.6.14/libs/pbd'
[13:41] <persia> We can't go back without a lot of pain.
[13:41] <quadrispro> g++ -DHAVE_CONFIG_H -I. -I. -I.     -D_REENTRANT -Os -fomit-frame-pointer -mmmx -msse -mfpmath=sse -pipe -Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/build/buildd-sooperlooper_1.6.14-1-amd64-wwBn5r/sooperlooper-1.6.14/libs/pbd -I/build/buildd-sooperlooper_1.6.14-1-amd64-wwBn5r/sooperlooper-1.6.14/libs/midi++ -I/usr/include/libxml2   -I/usr/lib/sigc++-1.2/include -I/usr/include/sigc++-1.2   -c -o basename.o basename.cc
[13:41] <quadrispro> g++ -DHAVE_CONFIG_H -I. -I. -I.     -D_REENTRANT -Os -fomit-frame-pointer -mmmx -msse -mfpmath=sse -pipe -Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/build/buildd-sooperlooper_1.6.14-1-amd64-wwBn5r/sooperlooper-1.6.14/libs/pbd -I/build/buildd-sooperlooper_1.6.14-1-amd64-wwBn5r/sooperlooper-1.6.14/libs/midi++ -I/usr/include/libxml2   -I/usr/lib/sigc++-1.2/include -I/usr/include/sigc++-1.2   -c -o dmalloc.o dmalloc.cc
[13:41] <quadrispro> [....]
[13:41] <persia> Ugh.
[13:41] <quadrispro> ar cru libpbd.a basename.o dirname.o dmalloc.o ftw.o mountpoint.o pathscanner.o pool.o pthread_utils.o receiver.o textreceiver.o transmitter.o undo.o unescape.o version.o xml++.o 
[13:41] <Scott-work> persia: that's what I figured :(
[13:42] <quadrispro> g++ -I/usr/lib/sigc++-1.2/include -I/usr/include/sigc++-1.2       -I/usr/include/libxml2      -g -O2 -D_REENTRANT -Os -fomit-frame-pointer -mmmx -msse -mfpmath=sse -pipe -Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/build/buildd-sooperlooper_1.6.14-1-amd64-wwBn5r/sooperlooper-1.6.14/libs/pbd -I/build/buildd-sooperlooper_1.6.14-1-amd64-wwBn5r/sooperlooper-1.6.14/libs/midi++   -o sooperlooper  sooperlooper.o libsldrivers.a lib
[13:42] <quadrispro> slcore.a /build/buildd-sooperlooper_1.6.14-1-amd64-wwBn5r/sooperlooper-1.6.14/libs/midi++/libmidipp.a /build/buildd-sooperlooper_1.6.14-1-amd64-wwBn5r/sooperlooper-1.6.14/libs/pbd/libpbd.a -ljack -lpthread -lrt   -llo -lpthread   -lsigc-1.2   -lrubberband    -lsndfile   -lsamplerate   -lasound -lxml2   /build/buildd-sooperlooper_1.6.14-1-amd64-wwBn5r/sooperlooper-1.6.14/libs/midi++/libmidipp.a /build/buildd-sooperlooper_1.6.14-1-
[13:42] <quadrispro> amd64-wwBn5r/sooperlooper-1.6.14/libs/pbd/libpbd.a
[13:42] <persia> quadrispro: Please reimplement dmalloc.cc :)
[13:42] <quadrispro> persia, eh eh, we need to :)
[13:42] <persia> Yeah.  That's a license violation right there.
[13:42] <persia> :(
[13:43] <quadrispro> persia, ok, 1 principle: I love sooperlooper but 2 things to do: 1. contact upstream 2. re-implement dmalloc.cc
[13:43] <persia> Unfortunately :(
[13:44] <persia> sooperlooper is *lots* of fun.
[13:44] <persia> But this whole "NON-COMMERCIAL" concept in linux-audio has got to go.
[13:44] <persia> open-source just doesn't work that way.
[13:44] <quadrispro> sure
[13:45] <persia> Making money is about being good at what one does, and having a good solution, and selling it, not about collecting rent for what one did last month.
[13:47] <quadrispro> unbelievable, this chaos is due to 4 functions...
[13:47] <quadrispro> 4 f*****g and "NON-COMMERCIAL" functions...
[13:48] <persia> Yeah.
[13:51] <quadrispro> persia, ok, now please help me: should I replace dmalloc.cc with my version and repack the tarball?
[13:52] <quadrispro> sorry, I mean substitue the files after repacking
[13:52] <quadrispro> * substitute
[13:53] <persia> I'd probably repack and delete the offending file, and then add a replacement in a patch.
[13:55] <quadrispro> excellent, working on it
[13:55] <quadrispro> hope to release a new package soon
[13:55] <persia> Thanks for the quick turn-around.
[13:56] <persia> You might want to comment on bug #545066 before an archive-admin gets to it.
[13:59] <Scott-work> quadrispro: I've added you to my list of people who rock!
[13:59] <Scott-work> sorry, that was sooo Jono
[14:00] <quadrispro> lol
[14:15] <quadrispro> persia, found a newer revision, which has been released under different terms
[14:15] <persia> heh, and after you reimplmented it :)
[14:15] <persia> Saves the discussion with upstream though.
[14:17] <quadrispro> no, I've found a new revision of dmalloc.cc 
[14:17] <quadrispro> same author, different license
[14:18] <persia> Oh, even better!
[14:18] <quadrispro> http://paste.ubuntu.com/399997/
[14:18] <persia> You had to change it?
[14:18] <quadrispro> persia, now I have to adapt the code, then testbuilding etc etc
[14:18] <persia> Ah, makes sense.
[14:19] <persia> I'd recommend changing the license: let me post:
[14:20] <persia> Oh, do you claim copyright for your changes, or do you assign Grant copyright for your changes?
[14:21] <quadrispro> doesn't matter, I can leave the copyright to the original author
[14:21] <quadrispro> no problem
[14:24] <persia> OK.  If you don't claim copyright, then no license change.
[14:25] <quadrispro> can we consider it as GPL-compatible?
[14:25] <persia> Yes.
[14:25] <persia> http://paste.ubuntu.com/400003/ would be the license if you wanted to assert copyright.
[14:26] <quadrispro> ah sure, ok
[14:28] <persia> If you don't, what you wrote is also correct.
[14:37] <quadrispro> persia, I solved the problem but not changing the source: just dropping it :)
[14:38] <quadrispro> and this is because it's unnecessary :)
[14:39] <quadrispro> persia, Scott-work -> http://home.alessiotreglia.com/unstable/pool/sooperlooper_1.6.14-2/
[14:40] <Scott-work> Applying patch 02-disable_dmalloc.patch?
[14:41] <quadrispro> yep, now i'm working on the packaing, I should add the tags to that patch
[14:41] <quadrispro> packaging *
[14:51] <quadrispro> Scott-work, I'd append .dfsg to the current upstream version number, debian release changes from 1.6.14-1 to 1.6.14.dfsg-1
[14:52] <quadrispro> Scott-work, is it correct? is it enough? (obviously, I will upload a new orig.tar.gz)
[14:53] <Scott-work> I will have to defer to persia since he is more knowledgeable about licenses than I but I think it sounds good
[14:53] <Scott-work> off note, I learned today that Dan from Linux Outlaws uses Ubuntu Studio apparently :)
[14:54] <quadrispro> :)
[15:46] <quadrispro> uploading
[15:48] <quadrispro> persia, Scott-work: uploaded
[16:06] <Scott-work> sooperlooper updated and kept in universe?  sooperdooper!  :P
[16:07] <quadrispro> Scott-work, I update the report
[16:09] <quadrispro> updated
[16:13] <Scott-work> thanks quadrispro for the quick response
[16:15] <quadrispro> you're welcome! 
[16:18] <abogani> Scott-work: Finally an Italian (=quadrispro) that do a good work! :-)
[16:18] <quadrispro> lol
[16:18] <quadrispro> the second 'Alessio'!
[16:19] <quadrispro> :)
[16:19] <quadrispro> abogani, I mean, you are the first one! :)
[16:20] <Scott-work> abogani: on the contrary, I think you do good work as well!
[16:20] <Scott-work> your chosen field of work is contentious though (i.e. politics of choosing and support kenerls)
[16:23] <quadrispro> ehy abogani, do you need a sponsor again?
[16:23] <abogani> quadrispro: No thanks anyway!
[16:25] <quadrispro> you're welcome, feel free to ask me when you need!
[16:28] <abogani> quadrispro: Thanks (again).
[17:39] <Scott-work> is anybody objectionable to including the hydrogen drumkits along with hydrogen (bug #528100)?
[17:41] <Scott-work> I'll let this set for a day or so, but if no one objects then I'll mark it confirmed and see about adding Recommends: hydrogen-drumkits to hydrogen
[17:45] <jussi01> Scott-work: whyever would we not?
[17:52] <astraljava> I would agree with jussi01.
[17:55] <Scott-work> not include the drumkits or not object? :P   if it's the former then I agree also with jussi01 and that's why I filed the bug
[17:56] <Scott-work> errr s/not/ why not
[17:57] <Scott-work> on a more serious note, I ask because sometimes there's history I don't know about since I've only been working with ubuntustudio-dev for a couple of months
[17:57] <astraljava> not including, just to clear any confusion :)
[17:58] <Scott-work> a good example would be the window selector, I thought it would be immensely useful but apparently there had been discussion not to inlcude it
[17:58] <astraljava> understood
[17:59] <Scott-work> i know that I always install the drumkits and i find that annoying, my opinion is that anyone who uses hydrogen either a) installs the drumkits also or b) doesn't know they exist
[18:00] <astraljava> I don't know that much myself, for instance I have no idea what you're on about re: the window selector :)
[18:01] <quadrispro> it would be good adding the drumkits to the hydrogen recommended pkgs
[18:02] <Scott-work> it's like the bar of tabs in firefox that show you the open webpages, but it's for open windows on the desktop
[18:02] <Scott-work> to swtich between applications you can click the bar that says "hydrogen" or "ardour" and move between them, but if they are not displayed and you minimize one then you can't easily select a tab to open it again
[18:02] <Scott-work> but you can alt-tab to it though
[18:03] <astraljava> Oh okay.
[18:05] <Scott-work> quadrispro: how will the recommends affect if one were to 'apt-get install hydrogen', are they installed automatically?
[18:05] <Scott-work> it is my understanding that in germinating the seeds during iso building it will grab the recommended files
[18:08] <astraljava> I think apt-get nowadays installs recommends automatically.
[18:08] <Scott-work> astraljava: thanks, i thought so also but didn't defintively know
[18:11] <Scott-work> of course I'm basing this on old web classes that i've read where they always seem to have people install things with the "--no-install-recommends" option (or whatever it is)
[18:11] <astraljava> That's what I'm thinking too.
[19:38] <stochastic> Scott-work, I was under the impression that the new 0.9.4 hydrogen has a built-in drumkit downloader, effectively making the hydrogen-drumkits package obsolete (I notice hydrogen-drumkits is still at version 0.9.3x in Lucid)
[19:39] <Scott-work> hmmm, interesting.  i'll play with it when i get home and see :)
[19:49] <Scott-work> i remember playing with the drumkit manager before but i think the manager was more for moderating or adjusting each kit rather than the whole library, but i'm not definitive
[21:16] <Scott-work> hmmm, the 64 bit beta-1 ISO isn't found   http://iso.qa.ubuntu.com/qatracker/info/3805
[21:17] <Scott-work> and only i386 ISO available here   http://cdimage.ubuntu.com/ubuntustudio/releases/lucid/beta-1/
[23:14] <ScottL> stochastic, I checked into the hydrogen drumkit downloader, you are right!
[23:14] <ScottL> under instruments -> import library
[23:14] <ScottL> it brings up a page that you can either import from a file or from the web
[23:15] <ScottL> my quick, cursory glance showed that more drumkits are available online than in the drumkits package :)
[23:16] <ScottL> the drumkits available from the hydrogen URL (that is autofilled) is what I meant above ^^^
[23:24] <ScottL> of course, the user still has to do download the drumkits manually, if the hydrogen recommends the -drumkits package then most are preinstalled....hmmm