[12:03] <sistpoty> andrewski: what is the last message you get from inside pbuilder?
[12:04] <andrewski> pbuilder: debootstrap failed
[12:04] <andrewski>  -> Aborting with an error
[12:04] <andrewski>  -> cleaning the build env
[12:04] <andrewski>     -> removing directory /var/cache/pbuilder/build//5987 and its subdirectories
[12:04] <andrewski> that's right after the warning.
[12:04] <sistpoty> andrewski: the interesting stuff is just before deboostrap failed, what's there?
[12:05] <andrewski> ok... pastebinning... brb. :-P
[12:05] <sistpoty> :)
[12:06] <andrewski> http://paste.ubuntu-nl.org/9078
[12:08] <sistpoty> andrewski: oh nice... my first guess is, that you did everything right
[12:08] <andrewski> that's good to hear. :)
[12:09] <sistpoty> andrewski: yep... archive.ubuntu.com seems to have problems atm
[12:09] <andrewski> hm.  so i could change my mirror and probably be good to go?
[12:09] <sistpoty> andrewski: you could try that, or just wait until a.u.c is fixed
[12:09] <andrewski> i'll try changing my mirror.
[12:14] <andrewski> sistpoty: and you said that dapper is usable now?  i'm tempted to go ahead and upgrade, but this is on my laptop, which i want to work.
[12:15] <sistpoty> andrewski: I've been using it for quite some time, and I didn't notice any big problems recently
[12:15] <andrewski> sistpoty: this close to release, it's only likely to be small updates, right?
[12:15] <TheMuso> I must say I have found GNOME a little sluggish on my P4, whereas Breezy runs fine.
[12:16] <sistpoty> andrewski: we're almost at feature-freeze, so mostly bugfixing
[12:16] <andrewski> hmm... and i could justify upgrading so that i could help find and squash bugs too. :)
[12:17] <andrewski> TheMuso: hmm, odd.  i wonder why?
[12:18] <ajmitch> andrewski: some of us have run dapper since it opened :)
[12:18] <ajmitch> so it's obviously not too bad
[12:27] <trappist> it's had its moments
[12:41] <mae> i can vouch that the "alpha" experience with dapper was much nicer than it was with breezy
[12:41] <mae> lol
[12:41] <jahraztah> hello i was wondering whether the version of gtk-gnutella in dapper willbe upgraded to the latest stable version since the verison in dapper is expired and will not function
[12:41] <jahraztah> this also goes for breezy backport
[12:42] <jahraztah> current stable working version is 0.96 and version in repository is 0.96b b for beta
[12:43] <TheMuso> jahraztah: We are currently in upstream version freeze, but a request may have been made to update it, I don't know.
[12:43] <jahraztah> but this is very important
[12:44] <jahraztah> a new version of dapper comming with an expired version of a software
[12:44] <jahraztah> and the version was expired many days ahead of upstream version freeze
[12:44] <jahraztah> 24 January 2006, Version 0.96 Released
[12:44] <lfittl> jahraztah: do you know which version is in debian?
[12:44] <jahraztah> 0.96
[12:46] <TheMuso> The debian version is 0.96cvs200602040801-2
[12:47] <jahraztah> ok
[12:47] <lfittl> we should wait for debian to get the final, and then request an UVF exception
[12:47] <TheMuso> c/
[12:47] <TheMuso> Note that feature freeze is only days away.
[12:48] <lfittl> days? just ~20 hours
[12:48] <jahraztah> normally i wouldn't request like this, but this upgrade is important, because the software doesn't function if not upgraded, do you know what i mean?
[12:48] <LaserJock> we can get a UVF  exception after FF can't we?
[12:48] <ajmitch> LaserJock: yes
[12:49] <jahraztah> the offical website does provide a deb, and the deb is fully working so far on my ubuntu
[12:51] <jahraztah> will dapper include software to allow easy installation of debs without opening a terminal. like a gui front using dpkg
[12:53] <ajmitch> like synaptic?
[12:53] <lfittl> jahraztah: yes, we have got gdebi for that now
[12:53] <ajmitch> or do you mean gdebi for the single packages?
[12:53] <tseng> or gdebi
[12:54] <jahraztah> yes, like when u download a deb file from the net you u just double click it and the applicaton launches and installs for you
[12:54] <jahraztah> and show all the things that are happening, like where it'll install and package info, and also dependencies
[12:55] <jahraztah> because dpkg does nothing about dependency. and you have to manually downlaod tha packages and then re-install the deb
[12:55] <tseng> not really
[12:55] <tseng> apt-get -f install resolves dependancies on partially installed debs
[12:56] <jahraztah> oh i did not know that
[12:57] <fbond> crud
[12:58] <LaserJock> fbond: man, that thing loves you ;-)
[12:58] <fbond> i know jesus i already got the authorities involved
[12:58] <LaserJock> I don't know if Jesus had anything to do with it, but ok. ;-)
[12:59] <fbond> i should hope he wouldn't be getting involved here
[01:00] <TheMuso> From a glance, gtk-gnutella is probably just a straight sync.
[01:00] <TheMuso> Going by the changelogs. Haven't looked any deeper though.
[01:01] <sistpoty> TheMuso: debdiff (and filterdiff) or diff for the debian-dir is your friend ;)
[01:01] <mr-russ> When packaging, how do you get different file ownership than the default, do you have to adjust postinst?
[01:01] <TheMuso> sistpoty: I know.
[01:01] <sistpoty> :)
[01:02] <sistpoty> mr-russ: afaik yes.
[01:02] <mr-russ> okay.
[01:02] <sistpoty> mr-russ: just look in the debian-policy, I bet there is s.th. about file ownership in there ;)
[01:03] <sistpoty> wow, s.o. is working on the new-queue :)
[01:04] <mr-russ> sistpoty: thanks.  10.9 :)
[01:05] <sistpoty> hehe
[01:06] <TheMuso> Gee. The changelog has had a lot of editing done to it since universe got 0.96b.
[01:07] <ajmitch> sistpoty: good, so a few things should work again - hopefully syncs get handled also
[01:07] <sistpoty> ajmitch: yes... hopefully I will be more successful in getting an answer right now than with my previous tries ;)
[01:09] <ajmitch> hehe
[01:09] <ajmitch> sounds like it was more fun with soyuz
[01:10] <sistpoty> definitely ;)
[01:10] <fbond> hmm...pbuilder is failing to update with md5 errors
[01:10] <fbond> anyone seen this?
[01:11] <ajmitch> wouldn't surprise me
[01:11] <ajmitch> archive.u.c is having issues today
[01:12] <fbond> is there a mirror?
[01:15] <sistpoty> fbond: sure... iirc there was a list of mirrors in the wiki
[01:15] <TheMuso> Although now I am not having such luck, even though there is a good chance there is nothing to update.
[01:15] <hub> w00t. exifprobe is in
[01:15] <TheMuso> heh. Just to show you how bad the issues are, one ofo my i386 builders completed successfully, whereas the other one failed.
[01:15] <dolson> fbond: hey... sorry, I thought you went on vacation so I did qsampler. I started doing linuxsampler, but I can't get that gcc crap to go away. I read the FAQ, but that didn't work for me
[01:16] <sistpoty> hub: congrats :)
[01:16] <hub> hugin will wait because of the license
[01:16] <hub> but they'll fix the problem upstream
[01:16] <hub> by using vigra 1.4 that is MIT licensed
[01:17] <dolson> fbond: so thanks :)
[01:17] <fbond> i just finished linuxsampler
[01:17] <fbond> qsampler is done
[01:17] <fbond> ?
[01:18] <fbond> sistpoty: do all ubuntu package repos also contain current dapper?
[01:18] <fbond> dolson: yeah i was sick for a few days, needed sleep more than anything
[01:19] <dolson> sleep? what's that? ;)
[01:19] <dolson> fbond: yeah, I did qsampler yesterday
[01:19] <dolson> I think... or maybe earlier today? geez, I don't even know now
[01:19] <sistpoty> fbond: no idea... if these are complete mirrors, they do
[01:19] <fbond> ah
[01:20] <fbond> dolson: ok, then that should be good to go
[01:20] <sistpoty> dolson: btw.: vcf-plugins uploaded... I guess my concern wasn't really justified... :)
[01:20] <fbond> where can I monitor status of dssi sync from debian?
[01:20] <sistpoty> fbond: is the sync requested already?
[01:20] <dolson> fbond: it didn't rely on linuxsampler, so I was able to do it first. and I think the dapper-changes list
[01:21] <dolson> sistpoty: cool deal! please upload anything with fbond's name on it ;)
[01:21] <fbond> sistpoty: i am in revu as forest@alittletooquiet.ent
[01:21] <sistpoty> dolson: I'm already reviewing like a mad man ;)
[01:21] <fbond> sistpoty: siretart had said it was on his todo list
[01:22] <dolson> fbond: if we do get all these music apps in, we'll be my heroes!
[01:22] <TheMuso> hehehe
[01:22] <sistpoty> fbond: ah... good, but I think it will be a few days until syncs will be progressed again (due to the statement on -dev some minutes ago)
[01:22] <fbond> dolson: just like i'd always dreamed...
[01:23] <dolson> fbond: I am not sure I am comfortable knowing that you dream of me.
[01:23] <sistpoty> fbond: you could always subscribe to the changes-mailing list, and check for dssi-accepted message
[01:23] <fbond> sistpoty: ok.  there are some packages in revu that depend on dssi
[01:23] <dolson> some important packages!
[01:23] <fbond> dolson: don't get too uncomfortable.  i was mostly being polite.
[01:23] <dolson> lol
[01:24] <sistpoty> I guess I will build dssi locally for reviewing pending packages...
[01:24] <fbond> that, of course, would be appreciated.  don't kill yourself, though.
[01:25] <fbond> dolson, sistpoty: i'd like to get dssi-vst in, but wondered if anyone had thoughts on the licensing issues
[01:25] <TheMuso> fbond: That is a curly one.
[01:26] <fbond> yes, it would have to be an automated download
[01:26] <fbond> during build
[01:26] <TheMuso> I think it has been discussed a lot of linux audio dev and user, but I am not aware of what the conclusion was.
[01:26] <fbond> or create a separate package called vstsdk
[01:26] <fbond> right
[01:26] <fbond> i had created a vstsdk package that downloaded the SDK at install time
[01:26] <dolson> fbond: I did om and omins too. wasnt hard at all...  firstly, the libs were already in dapper, and the FlowCanvass thing I guess is distributed in the source, not a separate lib to package
[01:26] <TheMuso> I know it would be nice to ship, but the license is a tough one.
[01:26] <fbond> dolson: terrific
[01:26] <fbond> TheMuso: not really
[01:27] <fbond> it's this simple: you can not distribute source of VST SDK in any form
[01:27] <fbond> dssi-vst makes an exception from the GPL in its license that allows distribution of dssi-vst without VST SDK source
[01:27] <fbond> at least for dssi-vst, licensing is pretty cut-and-dry
[01:27] <TheMuso> Right.
[01:28] <fbond> it's just a simple matter of making dssi-vst buildable by an automated build machine
[01:28] <sistpoty> fbond: is dssi-vst on revu? can't find it there
[01:28] <fbond> i.e.
[01:28] <fbond> sistpoty: no, not ATM
[01:28] <fbond> i've not uploaded my previous
[01:28] <fbond> package
[01:28] <sistpoty> fbond: can you point me to the licence / upstream tarball?
[01:28] <fbond> cause Steinberg, in the meantime, released a new version of the SDK
[01:28] <fbond> sure
[01:29] <fbond> http://www.steinberg.net/sdk_downloads/vst_29468/index.php
[01:29] <dolson> dssi-vst is a very important thing for musicians, especially anyone coming from Win32 who invested any money or time into certain VSTs.. I sure hope something can be worked out
[01:29] <fbond> the new version of the SDK does not compile cleanly with dssi-vst
[01:29] <fbond> will probably require some tweaking
[01:29] <fbond> and Steinberg doesn't make old versions available after new releases
[01:29] <fbond> and old versions are not redistributable
[01:29] <fbond> so some work is in order
[01:30] <TheMuso> fbond: There is also the chance that they completely change the URL.
[01:30] <dolson> is there a CVS of dssi-vst?
[01:30] <fbond> TheMuso: yes, we had considered this
[01:30] <fbond> the URL looks very phony
[01:30] <sistpoty> fbond: I get a file not found
[01:30] <fbond> dolson: yes, i haven't checked it yet
[01:30] <fbond> sistpoty: might've moved, or maybe that's an old link
[01:30] <fbond> sistpoty: hang on a sec...
[01:31] <sistpoty> thx
[01:31] <fbond> dssi-vst is on sourceforge as a part of dssi package
[01:31] <fbond> use soruceforge CVS if necessary
[01:31] <dolson> cvs hasn't been updated for over a year
[01:32] <fbond> to download VST SDK, Steinberg makes you agree to a license, and then send you an email with a link to the goods
[01:32] <fbond> so i suspect the actual location does change from time to time
[01:33] <TheMuso> They are trying to prevent the very thing you want to implement I guess.
[01:33] <fbond> http://www.steinberg.de/sdk_downloads/vst_29468/index.php
[01:33] <fbond> TheMuso: yes, they are trying to thwart my noble efforts
[01:34] <fbond> sistpoty: crap
[01:34] <fbond> i think i just pasted the same link
[01:34] <fbond> it is
[01:34] <fbond> ha!
[01:34] <fbond> they are watching IP addresses
[01:34] <sistpoty> fbond: found it already on sourceforge
[01:35] <fbond> sistpoty: you found VST SDK?
[01:35] <fbond> just license?
[01:35] <sistpoty> fbond: no, dssi-vst... is this s.th. different?
[01:35] <fbond> sistpoty: probably not
[01:35] <fbond> can't just diff it cause the Steinberg version is a .rtf
[01:35] <sistpoty> fbond: http://dssi.sourceforge.net/download.html
[01:36] <dolson> fbond: that link works for me
[01:37] <fbond> sistpoty, dolson: yes, i've been there before.  where is the VST SDK license on that page?  are you sure it is there?
[01:37] <fbond> sistpoty: or did you just want the dssi-vst license?
[01:37] <sistpoty> fbond: I'm looking through the tarball actually
[01:38] <fbond> yes, the README in the tarball has the dssi-vst licensing info
[01:40] <fbond> dolson: oh, BTW, don't get too down on yourself over linuxsampler package.  it wouldn't compile with anything except gcc-3.3 for me.  <3.3 = bad; >3.3 = bad; =3.3 = good
[01:40] <fbond> i had to force gcc-3.3 in debian/rules with environment vars to configure step
[01:40] <fbond> and adding appropriate build-depends
[01:40] <dolson> fbond: cuse told me it is "known to work with gcc 4.0"
[01:40] <fbond> dolson: not from what I can tell
[01:41] <LaserJock> ajmitch: I saw a black helicopter land in the middle of nowhere in Montana once. But I don't think that had anything to do with Linux ;-)
[01:41] <dolson> I think it has similar asm issues as Mx44, which Willem van Engen patched
[01:42] <sistpoty> fbond: oh... that licensing is a real pita... I guess the only way to do it might be to have a package vst-headers that downloads the header-files in postinst and have dssi-vst depend on that
[01:42] <dolson> fbond: by the way: http://rivironline.com/ubuntu-6.10.png
[01:42] <fbond> LaserJock: but it might've been related to VST!  You know how those Germans get...
[01:42] <fbond> jk
[01:42] <ajmitch> LaserJock: they're out to get you, you know
[01:42] <sistpoty> fbond: however it's not even guaranteed to work, since you cannot assume to have networking on the buildds (inside the build-environment)
[01:43] <fbond> sistpoty: ouch.
[01:43] <LaserJock> but in Montana? there is nothing but crazy bombers and cowboys out there. ;-)
[01:43] <TheMuso> That crossed my mind earlier.
[01:44] <fbond> sistpoty: well, without downloads, it's definately not feasible...
[01:44] <fbond> maybe just a source package...
[01:45] <sistpoty> fbond: we can't make a sourcepackage, if these files are not redistributable :(
[01:45] <sistpoty> fbond: I'm not sure about downloading though... maybe infinity or lamont could give a hint there
[01:45] <fbond> i mean dssi-vst source, and require user to manually download VST SDK
[01:45] <fbond> apt-get install dssi-vst-source
[01:45] <sistpoty> fbond: ah, sure... that would work
[01:45] <fbond> wget vstsdk.zip
[01:46] <ajmitch> still sounds nasty
[01:46] <fbond> fancy-debian-build-command make-my-dssi-vst
[01:46] <fbond> yes
[01:46] <fbond> nasty
[01:46] <ajmitch> I doubt the buildds have external net access
[01:46] <fbond> how lonely!
[01:46] <ajmitch> so the user would need to build this
[01:46] <fbond> dolson: yeah, i tried to rebuild linuxsampler with gcc-4.0.  no such luck...
[01:47] <fbond> gcc-3.3 is the only one that works for me
[01:49] <dolson> that's weird..
[01:49] <sistpoty> fbond: gcc-3.3 is a nogo unfortunately... it needs to built at least with 3.4 (and c++ stuff depending on c++ with >4.0)
[01:50] <dolson> oh crap
[01:50] <fbond> um
[01:50] <fbond> gcc-3.3 is in current dapper repos.  this will change?
[01:50] <fbond> 3.4 is likely ok.
[01:50] <fbond> hmm just a sec
[01:51] <fbond> dolson, sistpoty: i might've been wrong about gcc-4.0 failing...
[01:51] <fbond> oops, no i was right
[01:51] <sistpoty> fbond: yes, that will change, maybe for dapper +1... but new packages mustn't use 3.3 any longer
[01:51] <fbond> ok
[01:51] <lfittl> gn8 everybody
[01:52] <dolson> fbond: we should figure out how to patch that code I guess.. I don't know where to start, really
[01:52] <fbond> well, let's give 3.4 a shot first
[01:52] <fbond> so, g++-3.4 is not okay?
[01:53] <sistpoty> fbond: if it's c++ depending on c only, it's ok... but as soon as you've got a dependency on c++ it won't work since c++-abi was changed between 3.4 and 4.0
[01:54] <fbond> "depending on" = "links against" ?
[01:54] <sistpoty> exactly
[01:54] <fbond> never really understood this abi stuff :)
[01:55] <sistpoty> fbond: it will just segfault, if you try to link these together
[01:55] <fbond> ok
[01:56] <fbond> sistpoty: is it okay to compile C with gcc-3.4 and C++ with g++-4.0 and then link them?
[01:57] <sistpoty> fbond: c abi didn't change, so you can mix up c-code from 3.4 and 4.0
[01:57] <fbond> and mixing 4.0 C++ with 3.4 C is okay?  just not to familiar with these kinds of compiler issues...
[01:58] <sistpoty> fbond: yes... c++ linking with c can see only c-interfaces (as there are only c-interfaces) and thus is ok
[01:58] <fbond> okay, thanks!
[01:58] <sistpoty> np
[02:00] <fbond> crud.  g++-4.0 is the problem
[02:04] <fbond> dolson: linuxsampler will not compile with g++-4.0, and links against libgig, which has C++.  as a result, g++-4.0 must be used.  Where is the info on patching?
[02:05] <dolson> fbond: you mean on patching in debs or patching this specific code problem?
[02:05] <fbond> patching this problem.  did you have some info?
[02:06] <dolson> I don't... all I know is that whatever changed between g++ 3 and g++ 4 surely broken ASM stuff, because I had similar issues in Mx44
[02:08] <dolson> fbond: I will try building the latest CVS
[02:08] <sistpoty> dolson: congrats, qamix is in
[02:08] <fbond> dolson: ok
[02:08] <dolson> sistpoty: cool :)
[02:08] <sistpoty> dolson: next thing to do is also check the build-logs (as soon as there are any)
[02:08] <TheMuso> Any others motus around that could have a look at My few packages? :)
[02:08] <sistpoty> dolson: know where you can find these?
[02:09] <TheMuso> Sorry dolson, I just feel that a11y is just as important as audio. :)
[02:09] <dolson> sistpoty: not as of yet, but you are surely going to tell me :)
[02:09] <dolson> TheMuso: indeed it is
[02:10] <TheMuso> dolson: But you were there first. :)
[02:10] <LaserJock> can I get somebody to look at the debian/copyright file at http://tiber.tauware.de/~laserjock/copyright ?
[02:10] <sistpoty> dolson: https://launchpad.net/people/adolson/+packages, then just click on the version-link and then on the link under release to get to the buildlogs
[02:11] <dolson> sistpoty: sweet.
[02:11] <LaserJock> dolson: yeah, I just found out about the +packages today. very cool.
[02:11] <TheMuso> Ah! Finally got all pbuilders updated.
[02:13] <sistpoty> LaserJock: I would put the "you should have received a copy of the gpl..." paragraph in the copyright... but it's also good the way it is (imo)
[02:13] <dolson> LaserJock: I saw it before, didn't know it would be so integrated though. pretty awesome
[02:14] <dolson> wb apacheLAGger
[02:14] <dolson> wb poningru
[02:14] <dolson> wb j^
[02:14] <marcin`> hi guys
[02:14] <dolson> wb Fuddl
[02:14] <dolson> wb everyone else
[02:15] <marcin`> got a problem
[02:15] <marcin`> I got an webapplication and this webapp has /cache directory
[02:15] <marcin`> and this directory has to be writable to webserver users
[02:15] <marcin`> to put uploads there and cache files
[02:16] <marcin`> where should I install this directory?
[02:16] <marcin`> in /usr/share/mywebapp/cache or maybe in /var/cache/mywebapp and symlink to /usr/share/mywebapp?
[02:17] <fbond> dolson: i gotta run for a bit.  let me know how things go with linuxsampler CVS?
[02:17] <sistpoty> marcin`: did you take a look at fhs for this (in package debian-policy)?
[02:17] <dolson> fbond: k, thanks for reminding me, lol
[02:17] <fbond> later
[02:17] <marcin`> sistpoty: kind of...
[02:18] <marcin`> sistpoty: it's pretty unusual situation so there is no simple answer..
[02:18] <marcin`> sistpoty: I think that user files should go to /var/cache...
[02:19] <marcin`> sistpoty: but I'm not sure so I ask here...
[02:19] <sistpoty> marcin`: not really sure... if you delete one of these files, what happens then?
[02:20] <marcin`> sistpoty: well there is no files currently
[02:20] <marcin`> sistpoty: this webapp creates only directory structure
[02:20] <marcin`> sistpoty: to keep user files there in future
[02:21] <marcin`> sistpoty: it's for user uploads
[02:21] <sistpoty> marcin`: so if a user uploads a file, it will end up there? what if these file is deleted afterwards... will you get data-loss, broken links or s.th.?
[02:22] <marcin`> sistpoty: propably not
[02:23] <marcin`> sistpoty: it's: /cache/images /cache/import /cache/upload
[02:23] <marcin`> sistpoty: with 'fake' index.html files in each directory
[02:23] <sistpoty> marcin`: if a manual deletion of a file there is fully recoverable, /var/cache/mywebapp is the place to go
[02:23] <marcin`> sistpoty: and these html files contains only 'This directory must be writable by the webserver user.'
[02:24] <sistpoty> marcin`: if not, probably /var/lib/mywebapp
[02:24] <marcin`> ok - and symlink to /usr/share/mywebapp ?
[02:24] <sistpoty> marcin`: if you really need these, yes
[02:25] <sistpoty> (if you can change the path directly, please avoid putting symlinks in there)
[02:25] <marcin`> well I need this unfortunately
[02:26] <marcin`> this path is hardcoded in php code
[02:26] <marcin`> to /$webappdir/cache
[02:26] <sistpoty> then either patch the code or use symlinks ;)
[02:27] <marcin`> so if I keep webapp files in /usr/share/webapp then cache has to be there
[02:27] <marcin`> yup
[02:27] <LaserJock> do all files in the source need to be covered under debian/copyright or just the ones installed?
[02:30] <sistpoty> phew... no idea really... if these aren't installed, you wouldn't need to have info on the copyright about them. and if you use the sourcepackage you'll have the copyright information anyway... but OTOH it's convenient to have them all in debian/copyright, thus you can easily install another file w.o. having a messed up copyright
[02:30] <sistpoty> brb
[02:38] <dolson> fbond|away: no luck.. I fear this is going to be a no-go
[02:53] <shelagh> Hello, dolson; how can I help? I don't know how to start.
[02:53] <dolson> help what
[02:53] <TheMuso> shelagh: What do you want to help with?
[02:53] <LaserJock> hi minghua
[02:53] <shelagh> I wrote to you the other day (e-mail) to say I would help if I could
[02:54] <dolson> shelagh: ah, I was thinking your name looked familiar
[02:54] <shelagh> with learning how to make packages or testing or whatever.
[02:54] <minghua> evening LaserJock
[02:54] <dolson> shelagh: do you know how to progran at all?
[02:54] <odla> hey i no longer need espresso or casper installed if i have dapper installed to my harddrive do i?
[02:55] <shelagh> in theory, but not in practice yet.
[02:55] <odla> shelagh: oh...so if i purge them...that's bad?
[02:55] <shelagh> odla, sorry iwas replyting to something else.
[02:56] <odla> ok
[02:57] <shelagh> Where do I find out about using the packaging utilities? the documentation seems a little sparce on my harddrive.
[02:58] <dolson> shelagh: check the links in the topic
[02:58] <dolson> shelagh: right now I'm not really doing anything... I'm just waiting with baited breath to see if there are any fixes I need to make to my packages before feature freeze which is on the 23rd. but I am looking up stuff about trying to get LinuxSampler's compilation errors resolved so forest can fix his package in time
[02:58] <zakame> hi all
[02:58] <dolson> zakame! :)
[02:59] <zakame> heya dolson! :D
[03:00] <shelagh> dolson: got it. I'll do some reading and practicing.
[03:01] <dolson> shelagh: are you familiar with any music software yet? if so, could you write some quick tutorials, like a quick-start guide? for instance, if you did one for Audacity, just show how to record multiple tracks, mute tracks, solo, volume levels, time shift, envelope editor, and plugins. just real quick, to the point, intros. not real advanced stuff
[03:03] <shelagh> dolson: hmm... my experience has been struggling with midi and rosegarden, lilypond stuff. They have pretty good documentation. If I could work out how to get midi going reliably in ubuntu, I would happily do a tute on that!
[03:07] <LaserJock> what is the state of lilypond? do you guys use it much?
[03:09] <fbond> dolson: I'm not seeing much useful info
[03:09] <fbond> one guarranteed fix is to disable MMX/SSE asm optimizations
[03:09] <fbond> is it worth dropping to get the package in, for now?
[03:09] <dolson> hmm... sounds good to me
[03:09] <fbond> ok
[03:09] <fbond> i'll get it rolling
[03:10] <dolson> actually, Mx44 has MMX disabled, I think
[03:11] <fbond> ah
[03:11] <fbond> well that solves things pretty easily, although it is less than ideal
[03:12] <fbond> i will see if i can work with upstream to get the problem resolved
[03:12] <fbond> but for now, no asm optimizations
[03:12] <dolson> thanks man
[03:12] <dolson> I appreciate your work
[03:12] <fbond> not a problem :)  and you've done well yourself
[03:13] <dolson> thanks :)   we should look at building a 2.6.15-ck
[03:14] <TheMuso> dolson: That will very likely break a lot of other stuff that depends on particular kernel patches/drivers in the distro if the user chooses to install that kernel.
[03:14] <dolson> TheMuso: it is required for realtime audio... so there is not really any option. this is outside of ubuntu anyhow
[03:15] <TheMuso> dolson: I know. But what about the extra drivers that have been patched into the current kernel. Users just might need them.
[03:15] <fbond> TheMuso: my package is based on ubuntu's.  those drivers are there.
[03:15] <fbond> the config is nearly identical, insomuch as it can be
[03:15] <dolson> until Ingo's patch is accepted into mainline, there's not a lot we can do
[03:15] <fbond> i just modified the patch list
[03:15] <fbond> took out incompatible patches, added -ck6
[03:16] <fbond> (to my 2.6.12-ck6 package)
[03:16] <TheMuso> Righto then.
[03:16] <TheMuso> You will be lucky if you can get it in, or are you not trying to get it in?
[03:16] <marcin`> I have been asking about this today here but I'll try again
[03:16] <fbond> i don't anticipate that a non-MOTU will be submitting a kernel package, no
[03:16] <TheMuso> Fair enough.
[03:16] <marcin`> does anyone here know if are there any plans to implement conditional dependencies in dpkg/apt?
[03:16] <fbond> besides, there are loose strings WRT patched PAM, bash, etc, no?
[03:17] <fbond> marcin: I doubt it
[03:17] <dolson> fbond: I haven't heard anything back from Mark about a -rt kernel ever since the last thing I sent you
[03:17] <fbond> you would have to check with Debian to know for sure though
[03:17] <TheMuso> fbond: Yeah. IIRC dolson asked about that in #ubuntu-devel and kamion said he would have a look.
[03:17] <TheMuso> the pam stuff that is.
[03:17] <dolson> that's right.. he assigned the bug to himself
[03:17] <marcin`> fbond: ok I'll try on debian channel
[03:17] <fbond> this is not very useful info to me... I'm a bit out of the loop
[03:18] <fbond> marcin: good luck...sorry couldn't be more help
[03:18] <marcin`> fbond: but it's really strange that there is no such feature in dpkg yet..
[03:18] <dolson> I sure hope that it gets into dapper in time.. the PAM patch at least. it's very small, even I understand what happens in the patch, and that's saying something
[03:18] <fbond> marcin: i would guess that it is not useful that often. most packaging scenarios are pretty straight-forward
[03:18] <marcin`> fbond: so I hope there is a chance to make at least feature request
[03:19] <TheMuso> Cnditional deps?
[03:19] <marcin`> fbond: most - yes...
[03:19] <fbond> dolson: me too.  linuxsampler is done-and-done
[03:19] <marcin`> fbond: but there are more complicated packages
[03:19] <dolson> nice. I'll dl it and try it out here, along with my qsampler
[03:19] <fbond> okay gotta run to grocery store before... sorry to take off in such a flash
[03:19] <marcin`> TheMuso: yes - related with debconf
[03:19] <fbond> marcin: hmmm, i'd have to think about it.  maybe there is an alt. solution.
[03:20] <fbond> i'll be back, anyhow
[03:20] <marcin`> TheMuso: for example you got webapp that can use mysql or postgresql database or remote database
[03:20] <TheMuso> marcin`: A bit more explanation please. Not really up on what you are talking about.
[03:20] <TheMuso> marcin`: Right.
[03:20] <marcin`> TheMuso: then you could make a choice in debconf dialog and it could install dependency of your choice
[03:20] <TheMuso> Yep I am wiwth you.
[03:21] <marcin`> TheMuso: currently you have to do weird things with packages to provide this functionality
[03:21] <TheMuso> Right.
[03:22] <marcin`> TheMuso: I know that could be complicated but pretty usefull too
[03:22] <marcin`> TheMuso: I think that this straight forward is just something from pre-debconf era...
[03:27] <dolson> fbond|away: big diff.. I'd recommend adding in libjack0.100.0-dev as well
[03:27] <LaserJock> hi bmonty
[03:28] <bmonty> hey LaserJock
[03:28] <zakame> heya LaserJock bmonty
[03:28] <LaserJock> hi zakame
[03:28] <TheMuso> dolson, fbond|away, do you use pbuilder to test packages?
[03:28] <dolson> TheMuso: I do
[03:29] <bmonty> hows it going zakame?
[03:29] <zakame> doing great, still adjusting a bit to dapper (and xchat-gnome ;)
[03:30] <bmonty> I don't think I'll be using xchat-gnome for much longer
[03:30] <zakame> heya sistpoty
[03:30] <bmonty> the only thing I like about it is the popups if someone sends me a message
[03:30] <TheMuso> Go Irssi!
[03:31] <sistpoty> hi zakame
[03:31] <sistpoty> hehe, I just though, why is it so quiet, until I noticed that I got disconnected ;)
[03:31] <LaserJock> bmonty: yeah, I'm using this cool OSX chat app that has a nice notify bubble.
[03:32] <TheMuso> Hey guys. I have just been reading a bit about soyuz, and noticed something about RSS feeds. Anybody know where to find them?
[03:33] <LaserJock> TheMuso: where were you reading about soyuz?
[03:33] <TheMuso> On the launchpad wiki.
[03:33] <TheMuso> They probably ahven't implemented it yet.
[03:33] <TheMuso> I like the sound of it though.
[03:38] <odla> is there something funk with mp3 support in dapper with rhyhmbox?  i have all the proper packages installed but i can't seem to get mp3s to play
[03:41] <LaserJock> grrr I wish I could figure out a way to make a dapper chroot in OSX
[03:42] <zakame> huh? you can't?
[03:42] <crimsun> odla: dpkg -l gstreamer0.10-plugins-ugly |grep ^ii
[03:42] <LaserJock> zakame: how could I?
[03:43] <minghua> LaserJock: vmware, I suppose :-P
[03:43] <odla> crimsun: nothing
[03:43] <minghua> if vmware works in OS X, that is...
[03:43] <crimsun> odla: so install it.
[03:43] <LaserJock> minghua: oh my gosh, I never thought of that
[03:43] <zakame> LaserJock: there you go
[03:44] <odla> crimsun: the multiverse package or the regular one?
[03:45] <LaserJock> minghua: there isn't anything OSX specific but do you think the linux vmware-player would work?
[03:45] <crimsun> odla: the exact package I named.
[03:45] <minghua> LaserJock: I seriously doubt it, considering it's most likely i386
[03:45] <minghua> LaserJock: oh did you have an intel mac?
[03:46] <LaserJock> I'm running i386 ;-)
[03:46] <minghua> ok, slightly higher change, but still very close to zero in my opinion
[03:46] <odla> crimsun: thanks
[03:47] <crimsun> odla: np
[03:47] <odla> crimsun: maybe that should be added to the unofficial dapper guide?
[03:47] <crimsun> odla: sure?
[03:48] <crimsun> (don't know what the unofficial guide is)
[03:48] <odla> http://easylinux.info/wiki/Ubuntu_dapper
[03:48] <odla> someone in #ubuntu+1 showed that to me
[03:48] <whiprush> there's an #ubuntu+1?
[03:48] <whiprush> heh
[03:52] <fbond> dolson: libjack0.100.0-dev for which package?
[03:52] <dolson> fbond: linuxsampler?
[03:52] <fbond> TheMuso: yes, I use pbuilder
[03:52] <fbond> dolson: hmm...
[03:53] <fbond> does it depend on libjack-dev?
[03:53] <crimsun> it should _not_ build-depend on libjack-dev
[03:53] <dolson> no, it doesn't.. and the diff > orig
[03:53] <crimsun> always use the versioned build-dep for apps that require jackd
[03:53] <fbond> right, i was saving keys
[03:53] <fbond> saving have now been lost
[03:53] <crimsun> (libjack0.100.0-dev explicitly)
[03:53] <fbond> dolson: i'm not following
[03:54] <fbond> (yes i get it...thanks)
[03:54] <dolson> fbond: the diff file is larger than the orig source tarball.. did you do that on purpose?
[03:54] <fbond> um
[03:54] <fbond> hang on
[03:54] <dolson> k
[03:55] <fbond> oh, i ran the autotools stuff so that it wouldn't build-depend on autotools-dev
[03:55] <fbond> hmm this is not ideal
[03:55] <fbond> but the tarball would've contained configure
[03:55] <fbond> i just had to grab from CVS instead, since downloads are gone
[03:55] <fbond> can I fake the tarball?
[03:56] <fbond> that should be okay...
[03:57] <crimsun> just make sure you clearly denote in the source version that it's a snapshot. Don't generate configure before debuild -S ; instead build-depend on automake1.{8,9} and libtool
[03:57] <fbond> crimsun: the only reason I'm using CVS is because the source tarball is temporariliy unavailable
[03:58] <fbond> you recommend I do not reconstruct source tarball as it would've existed?
[03:58] <fbond> i've exported the CVS revision that corresponds to that release
[03:59] <crimsun> fbond: no, because the release tarball may differ in md5sum, which will throw off any sync attempts from Debian (if the package is in Debian, which I presume it isn't?)
[03:59] <fbond> (correct it is not) so I should treat this as a CVS snapshot, then?
[04:00] <fbond> dolson: what version of qsampler did you package
[04:00] <crimsun> if you checked it out from cvs, yes
[04:00] <dolson> fbond: one sec
[04:00] <fbond> dolson: CVS HEAD?
[04:00] <dolson> fbond: I used the latest stable qsampler
[04:00] <fbond> was it available on site?
[04:00] <dolson> fbond: you can generate the last release tarball of linuxsampler from CVS
[04:00] <dolson> yeah, qsampler has its own sf.net page
[04:01] <fbond> i exported from CVS because downloads had been unavail for about two months due to outage
[04:01] <dolson> fbond: Christian sent me the instructions to make the .orig.tar.gz file, I'll fwd to you
[04:01] <fbond> dolson: who?  what instructions?
[04:02] <dolson> fbond: you've got male
[04:02] <fbond> i should hope not
[04:02] <dolson> hehe
[04:02] <fbond> okay i gotta run real quick, i'll deal with this in a bit
[04:02] <dolson> Christian is the project lead.. I figured there was a way to generate their official release from the CVS, and I was right, he sent the instructions
[04:03] <fbond|away> ok
[04:03] <fbond|away> i'll be back
[04:03] <dolson> k cool
[04:06] <sistpoty> dolson, fbond|away: please only "fake" the release, if it really is bit-identical to the official tarball (caveats e.g. timestamp of files), otherwise just use a version-number for a cvs-checkout instead
[04:06] <sistpoty> s/checkout/export/ ;)
[04:06] <dolson> sistpoty: well, there is no way to ever know because their server failed and has been down since December 3rd
[04:07] <sistpoty> dolson: then I guess it's better to tag the version as CVS-version
[04:09] <dolson> so co -r  release0_3_3 linuxsampler, make dist, and then give it a CVS version (0.3.3-cvs?) in debian/control
[04:11] <dolson> btw, fbond|away, the way it is now, I try to install and it doesn't go. libgig is not installable. for whatever reason, it's libgig3c2 that it has to depend on
[04:11] <sistpoty> dolson: yes
[04:11] <dolson> I shouldn't have deleted my packaging work from earlier
[04:12] <crimsun> the beauty of maintaining packaging in svn/bzr/$yadda
[04:12] <dolson> I just deleted it because forest put his on revu
[04:13] <dolson> but my diff was really a lot smaller
[04:13] <sistpoty> dolson: (you must ensure that version numbers can always be increased for higher version, where 0.3.3-cvs is higher than 0.3.3 and you usually name the version differently... but in this special case 0.3.3-cvs is good as well)
[04:13] <dolson> I'd like to know what the proper way is
[04:14] <sistpoty> dolson: listed in https://wiki.ubuntu.com/MOTU/Packages/Reviewing
[04:18] <LaserJock> hmm, this might be a stupid question but does anybody know if the new Intel macs are 64bit?
[04:19] <TheMuso> LaserJock: I don't *think* so, but don't hold me to that.
[04:20] <LaserJock> hmm, I think somewhere I saw that they "secretly" are but Intel doesn't market them as 64bit or something stupid like that
[04:21] <crimsun> they're core duos afaik, which are 32-bit
[04:21] <dolson> sistpoty: so "0.3.2.99+0.3.3-cvs" is proper
[04:23] <sistpoty> dolson: probably 0.3.2.99+cvs-20062202 for usual checkouts, I would use 0.3.2.99+0.3.3-cvs only if it's tagged in cvs
[04:23] <sistpoty> dolson: so that you can easily verify which checkout the one for the tarball was
[04:23] <dolson> it is tagged. the latest cvs will require the latest cvs of qsampler, libgig, liblscp, etc, which we don't want at this time
[04:23] <sistpoty> dolson: sounds sane to me then ;)
[04:24] <dolson> cool deal
[04:35] <fbond> dolson: no worries, it will just take me a second
[04:36] <dolson> fbond: did you base your package on the release checkout, or did you get the source elsewhere?
[04:36] <dolson> like.. mentors?
[04:36] <fbond> mine was based on release checkout
[04:36] <fbond> i have followed instructions as per your email
[04:36] <dolson> cool.
[04:36] <dolson> I am not impressed with a lot of the stuff I've looked at in mentors
[04:36] <fbond> i haven't really checked it out
[04:37] <dolson> I assume that removing libgig from the depends list will allow the magic stuff to pick the correct libgig
[04:39] <fbond> that's what i did
[04:40] <dolson> I wonder why they don't use sourceforge instead of relying on their own servers
[04:40] <fbond> sourceforge goes down too
[04:41] <fbond> but not for two months, generally
[04:41] <fbond> :)
[04:41] <dolson> hehe, I know, but qsampler is downloadable thanks to sourceforge :)
[04:41] <fbond> sistpoty, dolson: the tarball is usually distributed as a .tar.bz2, not a .tar.gz, does MD5 even matter then?
[04:41] <dolson> I'm pretty sure sf does backups of some kind
[04:41] <fbond> oh, nm
[04:41] <fbond> it does
[04:41] <dolson> they're both there heh
[04:41] <fbond> sorry, stupid q
[04:45] <sistpoty> dolson: just looking at qsampler... you should link to config.guess/config.sub in the config.status-target instead of the clean target (and remove them in the clean-target) to get these files out of the .diff.gz
[04:45] <dolson> sistpoty: I'm opening up the rules now
[04:46] <sistpoty> (and ask upstream to provide a tarball w.o. debian-directory ;)
[04:47] <TheMuso> Rhythmbox in GNOME 2.14 is going to be really cool!
[04:47] <TheMuso> Using it now.
[04:49] <dolson> sistpoty: what the? I didn't put those in the diff on purpose, I don't even know what they are for lol
[04:50] <sistpoty> dolson: they sometimes are more up to date on the buildds (e.g. for porting to new architectures), but afaik aren't that much useful for ubuntu
[04:50] <sistpoty> at least I that's what I think they are for ;)
[04:51] <TheMuso> I remember reading something about them in the autoconf documentation, I think in the README.Debian file.
[04:51] <TheMuso> When I first started putting a package together a few months ago.
[04:51] <minghua> the README.Debian.gz file in autotools-dev
[04:51] <dolson> I have it installed in 3 places, /usr/share/{misc,libtool,automake-1.7}/config.guess
[04:52] <dolson> same with the .sub
[04:52] <minghua> I suppose dolson used dh-make and didn't touch the debian/rules it generated
[04:52] <TheMuso> minghua: That sounds like the one.
[04:52] <fbond> dolson, sistpoty: linuxsampler should be looking quite a bit better at this point
[04:52] <fbond> (updated)
[04:53] <fbond> minghua, TheMuso: actually, dolson's package included a debian dir
[04:53] <fbond> from upstream
[04:53] <fbond> and upstream could use a few tweaks
[04:53] <TheMuso> fbond: Was it useful
[04:53] <fbond> well, yes
[04:53] <fbond> still needed tweaking
[04:54] <sistpoty> sorry, but I really need to go to bed now... will try to do some reviews tomorrow
[04:54] <dolson> I tried to make the least amount of changes as possible
[04:54] <fbond> night sistpoty!
[04:54] <fbond> thanks!
[04:54] <sistpoty> you're welcome ;)
[04:54] <dolson> sistpoty: sleep tight :)
[04:54] <TheMuso> sistpoty: Night, and thanks.
[04:54] <sistpoty> good night
[04:54] <fbond> i gotta run, too
[04:55] <fbond> dolson: if you want, give linuxsampler a shot
[04:55] <fbond> i have not tried to install under dapper, but it does build
[04:55] <dolson> I will for sure, going to sort qsampler and try them both
[04:55] <fbond> great
[04:55] <fbond> send me an email if something looks fishy, but I believe it shouldbe good to go now
[04:55] <fbond> diff is quite small
[04:55] <fbond> i'll talk to you tomorrow, probably
[04:55] <fbond> night :)
[04:55] <dolson> will do
[04:55] <dolson> cya man
[05:59] <zakame> afternoon MOTUs
[06:08] <dolson> hi zakame
[06:09] <zakame> ei dolson :D
[06:09] <dolson> don't make fun
[06:09] <Hobbsee> hi zakame
[06:09] <dolson> I didn't choose to get laid off :(
[06:11] <zakame> hi Hobbsee! :D
[06:11] <Hobbsee> :)
[06:11] <zakame> dolson: ???
[06:12] <Kyral> Okay. Deskbar Applet owns
[06:12] <Kyral> -ERANDOM
[06:12] <dolson> zakame: ei = imployment insurance :)
[06:13] <zakame> dolson: ah :) didn't know that
[06:13] <dolson> ok, I just fixed the complaint about qsampler. should be good to go
[06:13] <dolson> zakame: got laid off as a Christmas gift, thanks to off-shoring jobs from Canada to Pakistan
[06:14] <dolson> ok, I think I will fix linuxsampler now and send a patch to forest
[06:15] <zakame> dolson: awww :(
[06:16] <dolson> zakame: I think it was a blessing.. I have learned a bit about packaging now
[06:16] <zakame> dolson: good for you! :D at least there's a positive side in that :)
[06:17] <dolson> there's a positive side in everything
[06:17] <dolson> except perhaps hemorroids
[06:18] <zakame> gaah
[08:31] <dholbach> good morning everybody
[08:31] <dolson> hi dholbach
[08:31] <dolson> my alarm instantly wakes me when you sign on
[08:31] <dholbach> hey dolson
[08:31] <dholbach> :-)))
[08:31] <dholbach> ROCK ON
[08:55] <dolson> dholbach: qsampler is good to go I think. linuxsampler needs a bit of work..
[08:56] <dholbach> NIce one!
[10:27] <dholbach> ROCK'N'ROLL - how did it go? :)
[10:28] <minghua> quite well, the installation is smooth, the result system is nice
[10:29] <dholbach> super!
[10:29] <minghua> the Chinese font is still far from satisfactory though, but that's my only complaint
[10:30] <sladen> minghua: we'd like to deal with that one compliant and get it sorted :)
[10:30] <sladen> minghua: have you used any other Linux distros/installs (eg. a previous version) that had better looking fonts
[10:30] <sladen> minghua: maybe we can track down a better font from there if it's free enough to ship
[10:30] <minghua> sladen: sure, I know exactly what font I need
[10:31] <minghua> I even sort of know how to configure it to the desired effect
[10:31] <minghua> the package in ubuntu is unfortunately very crappy
[10:32] <minghua> I am refering to bug 31149
[10:32] <Ubugtu> malone bug 31149 in ttf-arphic-uming "Bold fonts smudged" [Normal,Unconfirmed]  http://launchpad.net/bugs/31149
[10:32] <minghua> and I am opening a new one in a second
[10:34] <dholbach> minghua: do you know where and how to configure those default fonts?
[10:35] <minghua> dholbach: more or less yes
[10:36] <dholbach> minghua: where? because I'd like to change the arabic fonts too, they suck too.
[10:36] <minghua> dholbach: and I think I can always ask (on fontconfig upstream mailing list, for example) in case I don't know
[10:36] <minghua> dholbach: almost everything can be configured by fontconfig
[10:37] <minghua> dholbach: I don't know which TTF font is best for arabic though
[10:37] <dholbach> I'd try some different ones
[10:37] <dholbach> I'll have a look.
[10:37] <minghua> dholbach: and it depends if you want to map it to sans/serif/monospace or not
[10:38] <dholbach> i see
[10:38] <minghua> dholbach: the file to look at is /etc/fonts/fonts.conf, but the best way is not to modify it
[10:39] <minghua> dholbach: put a file in /etc/fonts/conf.d instead, using a filename starting with two digits
[10:39] <dholbach> ah cool
[10:39] <dholbach> I'll have a look at those
[10:39] <minghua> dholbach: and fontconfig will pick it up automatically
[10:39] <dholbach> Nice.
[10:39] <minghua> dholbach: man fontconfig and that's probably all (and so much more) you need to know
[10:39] <dholbach> Some bug report complained about arabic fonts and when I tried an arabic installation, I saw what he meant. :-)
[10:41] <minghua> sladen: back to your first question, though - as I've only used Debian and Ubuntu, I haven't seen a distro with nice looking out-of-box Chinese fonts, although I've heard of a lot
[10:50] <dolson> I remember when all fonts in general sucked
[10:50] <lfittl> dholbach: ping
[10:50] <dholbach> lfittl: pong
[11:12] <tepsipakki> slomo: thanks for making gstreamer0.10-plugins-bad* like you promised :)
[11:12] <slomo> tepsipakki: np :) but please file bugs whenever something doesn't work so we get at least some of these plugins ready for good/ugly...
[11:13] <tepsipakki> sure. they even managed to get 0.10.1 out just in time. I'm still running my own version of -bad but as soon as your packages hit the servers I'll try them
[11:14] <slomo> tepsipakki: they're already on archive.ubuntu.com... at least the universe variant, multiverse should be there in some minutes
[11:16] <tepsipakki> great
[11:16] <tepsipakki> if someone could take a final look at gtkpod-aac, it already got one advocate ;) http://revu.tauware.de/details.py?upid=1908
[11:17] <tepsipakki> and it's naturally meant for multiverse
[11:17] <slomo> it will get to multiverse anyway because it b-d on faad or faac ;) but sure, i'll take a look now
[11:18] <tepsipakki> thanks!
[11:19] <slomo> it is based on gtkpod?
[11:19] <tepsipakki> yes
[11:20] <slomo> ok... hm, can you keep care that all new changes to gtkpod are also applied to your package? :)
[11:20] <tepsipakki> sure
[11:20] <tepsipakki> it would be easier if they all used the same patch-system, but it's pretty simple as it is
[11:22] <slomo> tepsipakki: when it's based on that package please include all changelog entries in there, not only your own
[11:22] <tepsipakki> hmm, read the comments above ;)
[11:23] <tepsipakki> it has it's own source-tarball, so it was suggested to start from a clean table
[11:24] <slomo> tepsipakki: ok, fine with me... but i would've included the old changelog :)
[11:26] <slomo> either you made changes outside of debian or there were any before and you reverted them... why? it will make your life harder when you try to stay in sync with debian
[11:27] <slomo> and apparently you missed some bits that were changed before... for example in src/prefs.c
[11:28] <slomo> or in scripts/
[11:28] <tepsipakki> in gtkpod there is debian/ubuntu_patch.diff which patches the path /mnt/ -> /media in various places. When you run 'rules clean' the patch is not reverted, so it results in a bigger diff.gz, so I made it to use dpatch.
[11:29] <slomo> ok fine with me but when doing a debdiff between gtkpod and gtkpod-aac there were changes in the mountpath in src/prefs.c and in the scripts directory that are not in your package anymore
[11:30] <tepsipakki> hmm, I'll check
[11:31] <tepsipakki> true..
[11:31] <tepsipakki> duh
[11:31] <slomo> and in gtkpod the ubuntu.diff is only for reference... it was applied to the sources to not invent a new patch system over the debian package
[11:32] <slomo> so just do the same please to keep the delte between gtkpod and gtkpod-aac as low as possible
[11:35] <tepsipakki> I need to pach configure to change PACKAGE=gtkpod -> gtkpod-aac, so if I just add a patch for that?
[11:35] <tepsipakki> and keep the rest as in upstream?
[11:36] <tepsipakki> it's just confusing to have different kind of comments on revu ;)
[11:36] <tepsipakki> I mean, someone told to clean up the diff etc
[11:37] <slomo> yes i know... i'll talk to dholbach and sistpoty :)
[11:37] <slomo> dholbach: ping?
[11:38] <tepsipakki> but I can talk to the debian maintainer and give patches to make it cleaner, and be happy if he accepts them?
[11:39] <dholbach> slomo: pong?
[11:39] <slomo> dholbach: see http://revu.tauware.de/details.py?upid=1908
[11:39] <slomo> dholbach: you said that it would be better to use a patch system instead of having the changes in diff.gz
[11:40] <slomo> dholbach: but as this package is derived from one in debian i think it's better to make as less changes as possible
[11:40] <dholbach> ok makes sense
[11:40] <dholbach> maybe include the diff in   debian/applied-patches
[11:40] <dholbach> so it's easier to extract and to re-apply, for a new version
[11:40] <slomo> yes... that's how it was before :)
[11:40] <dholbach> ok
[11:40] <dholbach> sounds good
[11:41] <slomo> ok, tepsipakki so just do it this way and you get my vote... and maybe dholbach's too :)
[11:42] <tepsipakki> ok, will do :)
[11:42] <slomo> tepsipakki: ok, ping me when you're ready and it's uploaded :)
[11:46] <tepsipakki> yeah
[11:47] <lionelp> slomo: can you have a look on http://revu.tauware.de/details.py?upid=1899
[11:49] <tepsipakki> a question: I'd like to get libgssapi1 in dapper, but it contains /usr/lib/libgssapi.so.1 and it apparently conflicts with heimdal-dev which has /usr/lib/libgssapi.so. They both should be installable at the same time, says upstream. This conflict is the reason why the library is not yet in debian and upstream does not know how to resolve it..
[11:53] <minghua> tepsipakki: does libgssapi1 ships /usr/lib/libgssapi.so as well (usually a symlink)?
[11:54] <tepsipakki> minghua: no..
[11:54] <minghua> tepsipakki: I am pretty sure the /usr/lib/libgssapi.so in heimdal-dev is a symlink to /usr/lib/libgssapi.so.4 in libgssapi4-heimdal
[11:55] <minghua> (at least in Debian, don't know how to check ubuntu as they say packages.u.c is outdated)
[11:55] <tepsipakki> hmm, I'll try
[11:55] <minghua> tepsipakki: then I see no reason why libgssapi1 conflicts with heimdal-dev
[11:56] <minghua> tepsipakki: Debian apparently doesn't have libgssapi1 in sid
[11:56] <tepsipakki> yes, heimdal-dev pulls in libgssapi4-heimdal..
[11:56] <minghua> tepsipakki: while in sarge they have libgssapi1-heimdal which provides /usr/lib/libgssapi.so.1
[11:57] <minghua> tepsipakki: that's all I can get from the dependencies, I don't know about libgssapi at all though
[12:02] <tepsipakki> hmm, if I install heimdal-dev, it links libgssapi.so -> libgssapi.so.4.0.0 which is from libgssapi4-heimdal, but libgssapi1 wanted to link /usr/lib/libgssapi.so -> libgssapi.so.1.0.0
[12:02] <tepsipakki> so there's the conflict
[12:03] <tepsipakki> they install ok, but I'm not sure that the applications that expect to have a specific libgssapi.so are happy
[12:06] <minghua> tepsipakki: looking at the practice of Debian maintainer it seems the API is compatible, which means if you compile your program against the heimdal-dev in dapper it should work with the libgssapi.so.4.0.0 provided by libgssapi4-heimdal
[12:06] <minghua> tepsipakki: you need to ask someone who know libgssapi about this though
[12:07] <tepsipakki> I'll ask upstream..
[12:26] <TheMuso> Hey all MOTUs and MOTU hopefuls. :)
[12:27] <monzie> hi all
[12:29] <dolson> hey again TheMuso
[12:29] <dolson> hey monzie
[12:31] <TheMuso> dolson: SOmething I was meaning to ask you earlier today. Did you ever manage to download the titanicsf soundfont? Whenever I try to get that file recently I got a 404.
[12:32] <dolson> TheMuso: someone sent it to me over AIM. they have bandwidth issues or something... I asked them if we could get permission to redistribute in Ubuntu because Mark said he wanted sound samples and such included in Ubuntu, but no reply. that was a while back.
[12:32] <TheMuso> Ah right.
[12:33] <TheMuso> Is it worth it?
[12:33] <TheMuso> As in, attempting to get a copy from somewhere?
[12:33] <dolson> no idea yet.. I don't have enough RAM to load it at this point
[12:33] <dolson> it is highly recommended by others though
[12:34] <dolson> did you listen to the three demo files there?
[12:35] <TheMuso> Actually, I don't think I have.
[12:35] <TheMuso> Must grab them and listen to them.
[12:35] <dolson> they sound near movie-quality, to me...
[12:35] <TheMuso> Right.
[12:35] <dolson> there are 4 demos actually
[12:36] <TheMuso> The demo page is a 404.
[12:36] <dolson> TheMuso: the links in the wiki work: http://www.ubuntustudio.com/wiki/index.php/SoundFonts
[12:37] <TheMuso> Thanks.
[12:37] <dolson> the only thing I don't really like are the drums.. but I've heard a couple nice snares. just not enough variety between each sample playback. I imagine this can be fixed with a good software soundfont synth that allows randomization
[12:44] <atie> minghua, ping
[12:45] <minghua> hi, atie, just got your mail about 10 mins ago
[12:46] <minghua> atie: please have a read about my comments in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=335426 first
[12:46] <Ubugtu> debian bug 335426 in scim-pinyin "should add im-switch support for zh_CN" [Wishlist,Open] 
[12:46] <minghua> atie: I am all for adding im-switch support in scim-hangul, but I am against your (actually scim-anthy's) approach
[12:49] <atie> minghua, so scim-anthy is bad example?
[12:49] <minghua> atie: I need to go sleep soon and can't really think clearly right now :-P  will give you a detailed reply tomorrow
[12:49] <atie> minghua, ok.
[12:50] <minghua> atie: not really "bad", but not good enough, in my opinion
[12:50] <minghua> it's a maintainer's burden thing
[12:50] <minghua> adding such a patch is probably 10 min's work, but later I probably need 5 hours to keep supporting it
[12:50] <atie> I wanted to keep all scim packages in same. :)
[12:51] <minghua> atie: well, my debian packages won't use that approach, which are scim-uim, scim-pinyin, scim-tables
[12:52] <minghua> for scim-hangul I am just co-maintainer, so it's kind of in the middle
[12:53] <TheMuso> dolson: That orchestral demo has MIDI written all over it :)
[12:53] <TheMuso> Dont like either the band mix or the orchestral demo.
[12:53] <TheMuso> Got the others to try yet.
[12:53] <atie> minghua, do you remember I sent you and Mr. Yang a mail to check current scim-hangul?
[12:54] <minghua> atie: yes
[12:56] <atie> minghua, go to bed, talk later. I am feeling sorry. :)
[12:56] <minghua> atie: sure, good night
[12:57] <atie> minghua, it's too early to me saying "good night". bye.
[12:57] <minghua> :-)
[01:02] <dholbach> TheMuso: I packaged dogtail :)
[01:02] <TheMuso> dholbach: What is that package again?
[01:02] <dholbach> automated a11y testing
[01:02] <TheMuso> Thats right.
[01:03] <TheMuso> I have just replied to Henrik's email on the list to see whether we can get something moving re the speech implementation. I suggested he come onto IRC so we can bug Kamion about it.
[01:03] <TheMuso> I know it is close to feature freeze, but we need either a yes or no.
[01:03] <dholbach> yeah
[01:04] <TheMuso> Ok he has just joined.
[01:06] <tepsipakki> slomo: ok, new version of gtkpod-aac is now in REVU
[01:07] <slomo> tepsipakki: url? :)
[01:07] <tepsipakki> http://revu.tauware.de/details.py?upid=1944
[01:08] <slomo> tepsipakki: fine with me :)
[01:08] <tepsipakki> yeehaw! :)
[01:09] <slomo> when it builds ;)
[01:10] <tepsipakki> cosmetic..
[01:10] <slomo> dholbach: do you have some time to review this one too? just do an debdiff to the gtkpod package... the changes are really small
[01:10] <dholbach> slomo: not at the moment, later
[01:10] <dholbach> or somebody else can review it
[01:11] <slomo> dholbach: ok :)
[01:14] <slomo> tepsipakki: search for another vote :) maybe ask sistpoty again
[01:15] <tepsipakki> slomo: ok, np
[01:24] <tepsipakki> how should I handle a package which has it's own debian-hierarchy, and the latest version is not in debian/dapper?
[01:24] <tepsipakki> I mean, which version should I use
[01:25] <tepsipakki> upstream has -1, do I use -1ubuntu1 or -0ubuntu1?
[01:26] <Yagisan> tepsipakki: I suggest -1ubuntu1
[01:26] <slomo> dito
[01:26] <slomo> but you can keep the -0ubuntuX version as well
[01:26] <slomo> your decision... debian will never get this package so you could use a -X version too
[01:26] <tepsipakki> oh, and I believe that the libgssapi/heimdal-conflict is easy to solve.. since libgssapi build-depends on libkrb5-dev which conflicts with heimdal-dev, so libgssapi1 should Conflicts with libgssapi4-heimdal?
[01:27] <Yagisan> yes, but if someone adds upstreams repo, the -1 will be higer then the -0ubuntu
[01:27] <tepsipakki> slomo: yes, I believe they'll release a new version before it hits debian :)
[01:27] <lfittl> slomo: do you have time to look at http://revu.tauware.de/details.py?upid=1945?
[01:29] <slomo> lfittl: yay a game :) i'll review it now
[01:29] <lfittl> :)
[01:31] <Yagisan> slomo: I'll get you more games - hopefully by dapper +1 ;)
[01:32] <slomo> lfittl: upstream is insane, yes? ;) "-funroll-loops -fomit-frame-pointer -pipe -O9"
[01:32] <Yagisan> slomo: the -O9 actually does not work - heh
[01:33] <slomo> Yagisan: it should work... but it does the same as -O3
[01:33] <lfittl> slomo: yep, will send him a mail about my changes
[01:33] <Yagisan> IIRC it was ignored, as it wasn't int the accepted range
[01:33] <slomo> lfittl: in debian/control... you have 3 times "Section: games" in there... one time for the source package is sufficient :)
[01:34] <lfittl> oh, did not know that, will re-upload after you have finished reviewing :)
[01:34] <slomo> lfittl: anagramarama-data should not have shlibs:depends as it's a) arch: all and b) doesn't contain binaries anyway
[01:35] <slomo> lfittl: just delete the Depends line for -data
[01:35] <lfittl> copy and paste is sometimes really bad ;)
[01:35] <lfittl> anything else?
[01:35] <slomo> lfittl: and add ${misc:Depends} to the other package just to be on the safe side :)
[01:35] <dolson> I packaged orbital eunuchs sniper, but it crashes and deploys an SDL parachute... segmentation fault
[01:36] <lfittl> slomo: what would be added by misc:Depends?
[01:36] <slomo> lfittl: standards-version... 3.6.2 is enough, 3.6.2.X only adds cosmetic changes
[01:36] <slomo> lfittl: most probably nothing yet... but when you use gconf for example gconf would be added there
[01:36] <lfittl> k
[01:40] <slomo> looks sane... what about a .desktop file for it? :)
[01:42] <lfittl> right, I forgot that one, will re-upload after adding it
[01:42] <Yagisan> lfittl: please, please include a .desktop file. It is such a pain in the arse to not have one. You could probally copy one out of another game on revu
[01:43] <lfittl> Yagisan: I hate games without .desktop files too ;)
[01:44] <slomo> lfittl: the game is fun :)
[01:44] <lfittl> :)
[01:45] <Yagisan> lfittl: I have so many installed with a .desktop file, I can't remember which ones to file bugs on!
[01:45] <Yagisan> s/with/without
[01:45] <slomo> lfittl: ping me when you uploaded a new version :)
[01:45] <lfittl> yep
[01:48] <slomo> hmm... wordlists in other languages would be nice :)
[01:49] <Yagisan> slomo: what sort of wordlists >:) ?
[01:51] <slomo> Yagisan: just random words with lenghts from 1 to 7
[01:51] <slomo> Yagisan: no names
[01:52] <Yagisan> slomo: I'm sure I have something that fits in my massive passwords collection. What do you need it for
[01:52] <Yagisan> ?
[01:52] <slomo> lfittl's game ;)
[01:53] <slomo> you get 7 letters and have to find all possible words you can build with these letters
[01:53] <Yagisan> hmm, I'm not sure he needs a 300MB compressed data file
[01:53] <Yagisan> english letters only ?
[01:54] <slomo> yes
[01:54] <slomo> A-Z,a-z
[01:55] <slomo> well... other national letters would work too i guess
[01:55] <slomo> but i guess there are names in your password collection
[01:57] <Yagisan> yes, all sorts, not just english characters either
[01:59] <Yagisan> you really need just random characters ? that could probally hacked up in a script
[02:02] <slomo> Yagisan: no... words :P you get 7 random chars in that game and need to find all words you can build with them
[02:04] <Yagisan> slomo: script it. cycle from a-z then overflow. actually better idea is to have the game do it in code. probally can get some code to do that from john the ripper
[02:05] <slomo> Yagisan: you don't understand me :) the game has a wordlist with real words from lenght 1 to 7
[02:05] <Yagisan> ah - so typical of me.
[02:06] <Yagisan> as usual it has gone over my head
[02:12] <marcin`> raphink: vtigercrm and vtigercrm-mysql-local are in REVU now please review them if you will have time
[02:22] <lfittl> dholbach: ping
[02:23] <dholbach> lfittl: pong
[02:40] <atie> Can someone here bring a new version of ttf-fonts package from Debian to Dapper directly? I could build them with source files in Debian.
[02:40] <atie> s/them/it/
[02:40] <freeflying> atie: hi
[02:41] <atie> freeflying, hi.
[02:49] <atie> freeflying, thanks for fixing the xim issue.
[02:49] <freeflying> atie: it's my horour , hehe
[02:58] <segfault> i have a slapd module which i got from openldap2.3, and compiled for openldap2.2 and packaged it. how am i supposed to upload to revu, since there's no .orig source?
[02:58] <dolzzzon> fbond|away: good job
[03:00] <dolzzzon> fbond|away: ohhh, except the address for the FSF is outdated in the copyright file
[03:01] <zakame> evening MOTUs!
[03:01] <dolzzzon> zakame: WAZZZZUPP!!?
[03:01] <Gloubiboulga> heya zakame
[03:02] <dolzzzon> argh. ok, I will sleep now, as my left eye hurts a lot :( bbl
[03:04] <zakame> heya dolzzzon Gloubiboulga :D
[03:08] <tepsipakki> guys, the libgssapi.so conflict I was talking about earlier is ancient history, doesn't apply to sid/dapper anymore
[03:08] <tepsipakki> upstream cannot reproduce it anymore
[03:15] <phanatic> hi people
[03:16] <zakame> hello phanatic
[03:17] <Tonio_> Gloubiboulga ping ?
[03:17] <Tonio_> hi everyone
[03:18] <Gloubiboulga> Tonio_, pong
[03:19] <Tonio_> Gloubiboulga, netswitch and knetswitch have a chance to be uploaded
[03:19] <Gloubiboulga> cool :)
[03:19] <Tonio_> Gloubiboulga, Riddell tested gnetswitch and got a big error "segmentation fault" while launching it
[03:19] <Tonio_> works for me.......
[03:19] <Gloubiboulga> hum...
[03:19] <Tonio_> can, you eventually test ?
[03:20] <Gloubiboulga> yes, I do it now
[03:20] <Tonio_> okay
[03:20] <Tonio_> take the package on revu
[03:20] <Tonio_> even there are still problems, upstream have worked hard last week to clean toe package for ubuntu
[03:20] <Tonio_> it would be a pain not to get them in universe :)
[03:21] <Tonio_> Gloubiboulga, what is important is to test gnetswitch with the svn version of netswitch that is on revu too
[03:21] <Tonio_> not version 0.3 of course :)
[03:21] <Gloubiboulga> of course :)
[03:22] <Tonio_> Gloubiboulga thanks ;)
[03:23] <Gloubiboulga> I had an issue too with 0.3
[03:24] <Gloubiboulga> The default debhelper Cflags were not ok
[03:37] <freeflying> looking for review http://revu.tauware.de/details.py?upid=1957
[04:05] <Kyral> Morning
[04:05] <phanatic> hi Kyral
[04:16] <tepsipakki> ok, any main-uploaders available for a package-review? I have a new version of libnfsidmap packaged, should I upload it to REVU?
[04:17] <allee> Hi, there a new rsibreak release that fixes major bug/annoyance. I've uploaded to REVU http://revu.tauware.de/details.py?upid=1930 and added a comment there.
[04:18] <allee> The release is not a minimal bug fix, as is rsibreak will sooner or later turned of because it gets the timer wrong
[04:19] <allee> Anyone to ping here for ask for an UVF, or better post to -motu ml?
[04:21] <jpatrick> allee: https://lists.ubuntu.com/archives/ubuntu-motu/2006-January/000177.html
[04:21] <raphink> dholbach: if I want to ask for a sync exception request, what shall I attach to the mail?
[04:24] <jpatrick> wb allee
[04:26] <allee> jpatrick: uhm, konversatoin was suddenly frozen :(  didn't like you URL? ;)
[04:26] <jpatrick> odd
[04:26] <allee> jpatrick: yeah. First time that this happend.
[04:27] <raphink> anyone knows what I shall put in my mail for a sync request?
[04:27] <jpatrick> allee: have you thought of joining the Debian Collaboration Team? https://launchpad.net/people/dct (for what you discussed at #ubuntu-meeting)
[04:28] <tseng> raphink: Please sync foo, uvf approved by {mdz,kamion}. Thanks.
[04:28] <raphink> tseng: in english?
[04:29] <allee> jpatrick: no, did now about it.  I only watch the alioth counterpart ;)  I'll look at it.
[04:29] <tseng> raphink: what
[04:29] <raphink> tseng: can you explain to me again, using sentences with subjects and verbs ?
[04:29] <tseng> "what shall I put in my mail for a sync request"
[04:30] <raphink> I know how to make a UVF request
[04:30] <tseng> Please sync package foo from Debian
[04:30] <raphink> but this is a sync request
[04:30] <raphink> hmm
[04:30] <tseng> ...
[04:30] <raphink> I mean
[04:30] <raphink> for UVF exceptions request, we have to join a diffstat and the upstream changelog
[04:30] <raphink> is it the same for a sync request?
[04:30] <tseng> no
[04:30] <raphink> that is my question
[04:31] <tseng> if your sync changes upstream version
[04:31] <tseng> you should point out to elmo that it was approved by $approver
[04:31] <tseng> and give him a link to the motu list mail even
[04:31] <raphink> my question is how do I ask for approval ...
[04:31] <raphink> what do I have to put in my mail to ubuntu-motu
[04:31] <tseng> of the uvf change, or the sync?
[04:31] <tseng> oh jeez
[04:31] <raphink> instead of the diffstat+changelog
[04:31] <raphink> sync
[04:32] <raphink> it's a sync from Debian that I request
[04:32] <tseng> sync of debian version, not new upstream?
[04:32] <tseng> please start from the begining
[04:32] <raphink> oook let's start from the beginning
[04:32] <raphink> I want to request a sync from Debian of Wesnoth 1.1.1
[04:32] <raphink> since we have 1.1
[04:32] <raphink> which doesn't work anymore on the official server
[04:32] <tseng> so, that is not requesting a sync
[04:32] <raphink> for gaming
[04:32] <raphink> huh?
[04:32] <tseng> which is what you asked an I answered
[04:33] <tseng> you are requesting a UVF exception
[04:33] <tseng> if you get it, you can request a sync
[04:33] <raphink> a UVF exception for a sync
[04:33] <tseng> sure
[04:33] <tseng> but a sync request is totally seperate
[04:33] <tseng> so please dont call it the same thing :)
[04:33] <raphink> as you wish
[04:33] <raphink> my point is
[04:34] <raphink> for a UVF exception, we have to join a diffstat and the upstream changelog
[04:34] <raphink> is it the same if I request a UVF exception for a sync from Debian?
[04:34] <tseng> yes, its still a uvf exception
[04:34] <tseng> just note that the version is alreayd in debian
[04:34] <raphink> ok
[04:34] <tseng> and its a clean sync
[04:34] <tseng> no ubuntu changes
[04:34] <raphink> so I run the diffstat on the package?
[04:34] <tseng> on the orig tarballs
[04:35] <raphink> ah
[04:35] <raphink> I have yet to see if it's a merge actually
[04:59] <raphink> dholbach: could you approve my message to the list please?
[05:00] <dholbach> sure
[05:00] <raphink> :)
[05:00] <raphink> thanks
[05:00] <raphink> it says it's too big a body
[05:00] <raphink> cause there are lots of attachment, although i've tried to make them as small as possible ;)
[05:01] <dholbach> 322K? HOLY COW!
[05:01] <raphink> heh
[05:01] <jpatrick> must go to india then
[05:01] <raphink> this is a new version of wesnoth
[05:01] <raphink> with lots of changes
[05:01] <dholbach> I feel we have to find a new process for this.
[05:02] <raphink> dholbach: and I've even run diffstat on it
[05:02] <raphink> otherwise the debdiff was 50MB lol
[05:03] <jpatrick> ok that's huge
[05:03] <raphink> indeed
[05:03] <raphink> that's as big as the orig
[05:03] <raphink> which I guess explains why the 1.1.1 official server requires to use wesnoth 1.1.1 and not 1.1
[05:05] <raphink> dholbach: did you approve it though?
[05:05] <dholbach> yes i did
[05:05] <raphink> dholbach: thanks
[05:14] <raphink> siretart: do you think it would be possible to have a local repo on tiber that can be used to test packages that depend on one another in REVU?
[05:17] <siretart> raphink: in principle, yes. But I'd rather spend time on revu2
[05:18] <raphink> siretart: well for REVU2 too of course
[05:18] <raphink> siretart: if I can work on REVU2, I'd be happy to do it
[05:18] <raphink> siretart: if there is something that is needed now
[05:19] <siretart> raphink: well, the svn is open, and I guess you can already commit to it ;)
[05:20] <raphink> yes
[05:20] <raphink> but I don't really know what is the plan
[05:20] <raphink> who is working on what
[05:20] <raphink> where there is a need for more work
[05:27] <hub> http://geekz.co.uk/lovesraymond/archive/cancomical-lynchpad
[05:27] <hub> LOL !
[05:52] <apachelogger> re
[05:53] <jpatrick> hello
[06:08] <jpatrick> Tonio_: you around?
[06:10] <jpatrick> apachelogger: libqt3-compat-headers (>= 3:3.2.3) and libqt3-mt-dev (>= 3:3.2.3) ?
[06:10] <apachelogger> jpatrick: later has been removed
[06:10] <apachelogger> compat is needed for building
[06:11] <jpatrick> odd, I'm build 1903
[06:11] <jpatrick> building*
[06:11] <apachelogger> 1903 still includes mt-dev
[06:11] <apachelogger> next revision will not ;-)
[06:11] <jpatrick> well, where is it? ;-)
[06:12] <apachelogger> shell I really upload for that little depend?
[06:12] <jpatrick> yep
[06:12] <apachelogger> ok
[06:13] <jpatrick> otherwise I can't upload
[06:14] <apachelogger> the package is _that_ perfect? O.o
[06:14] <jpatrick> we'll see
[06:14] <apachelogger> up it is
[06:41] <sistpoty> hi folks
[06:41] <Gloubiboulga> hey sistpoty
[06:41] <sistpoty> hi Gloubiboulga
[06:42] <jpatrick> hello sistpoty
[06:42] <sistpoty> hi jpatrick
[06:43] <sistpoty> time for another reviewing round... /me looks at gnome-orca
[06:45] <atie> bye all
[06:45] <jpatrick> apachelogger: this is going to take forever
[06:46] <apachelogger> jpatrick: the building?
[06:46] <jpatrick> yep
[06:46] <jpatrick> it's still unpacking dep
[06:46] <apachelogger> hasn't took that long here
[06:46] <apachelogger> O.o
[06:46] <apachelogger> lame server :P
[06:51] <sistpoty> TheMuso: for gnome-orca, it might be prudent to split the binary package to an arch:all (python-stuff) and arch:any (the library) pacakge
[06:51] <marcin`> raphink: ping
[06:53] <slomo> sistpoty: would be nice, yes... btw, for gtkpod-aac... your suggestions were all correct for a new package but keep in mind that this package is derived from one we already have and has to be kept in sync with that one... so minimal changes
[06:53] <slomo> TheMuso: for gnome-orca... copyright is wrong... i find at least "Copyright 2005 Sun Microsystems Inc." und "Copyright 2005 Google Inc." und "Copyright 2001, 2002 BAUM Retec, A.G." but you mention two names in debian/copyright
[06:55] <sistpoty> slomo: so gtkpod-aac will always be merged from gtkpod-versions? Had the impression that it was a fork here... ;)
[06:55] <sistpoty> slomo: hehe, you just wrote "und" ;)
[06:56] <slomo> sistpoty: it's only changed packaging :) one new build-dependency from multiverse... so it should be kept in sync with the default package, yes
[06:56] <sistpoty> slomo: ah... thx for clarifying
[06:57] <sistpoty> slomo: did you upload gnome-orca right now?
[06:57] <slomo> sistpoty: nope... i aborted the upload ;)
[06:57] <slomo> sistpoty: copyright is wrong
[06:58] <sistpoty> slomo: ah... just saw your comment... I removed your advocacy ;)
[06:58] <slomo> sistpoty: thanks :) but i think the splitting would be overkill in this case
[06:59] <slomo> sistpoty: it's only a 6544 bytes library... it doesn't deserve an own package ;)
[06:59] <sistpoty> slomo, TheMuso: I could live with the package in the current shape (maybe I should have commented that), splitting would be a nice extra imo :)
[07:00] <sistpoty> slomo: but the python-stuff will be around 4 instead of only 1 times on the ftp-servers
[07:00] <hub> what can't I reupload to REVU a package
[07:00] <sistpoty> hub: .upload file left lying around?
[07:00] <hub> the version hasn't changed but the package did
[07:00] <hub> ah right
[07:00] <jpatrick> dput -f *.changes
[07:00] <hub> works now
[07:00] <hub> .upload
[07:00] <slomo> sistpoty: but it would make our Packages files bigger too... twice as big
[07:01] <hub> dholbach: that pandora package I fixed it. I did the mistake  :-/
[07:01] <dholbach> hub: ah ok
[07:02] <hub> I don't know how it didn't go thru
[07:02] <hub> I always check the binary package
[07:02] <sistpoty> slomo: yep... and a *library* package would be total overkill, but imo I still think the split to a -base (or s.th.) package might be good
[07:02] <apachelogger> jpatrick: still building?
[07:03] <slomo> sistpoty: it would be cleaner... yes... but the tradeoff doesn't justify it imho :)
[07:03] <jpatrick> apachelogger: now it's going though ./configure
[07:03] <apachelogger> oioi :|
[07:03] <sistpoty> slomo: hehe... well I'm still learning some lessons... last lesson was "misc:depends" is good ;)
[07:03] <slomo> sistpoty, TheMuso: i'll change the copyright for gnome-orca and upload it then
[07:04] <sistpoty> slomo: go ahead ;)
[07:05] <dholbach> hub: still no love on amd64
[07:06] <hub> mmm
[07:06] <dholbach> let me doublecheck
[07:06] <hub> there was a problem on i386
[07:06] <dholbach> maybe i did something wrong
[07:06] <dholbach> it's building and i'll be off cooking for some time
[07:06] <hub> the uid changed :-0
[07:06] <hub> http://revu.tauware.de/details.py?upid=1966
[07:08] <dholbach> hub: better
[07:09] <lucas> is it me, or a spam went through on ubuntu-announce@ ?
[07:09] <stratus> lucas: check the headers
[07:10] <dholbach> lucas: yes, it was a mistake
[07:10] <lucas> stratus: I did
[07:10] <lucas> stratus: but I can easily send you an email with the good List-Id header :-)
[07:10] <sistpoty> dolzzzon: you'll need to update debian/copyright for omins, since there are files that contain copyright info (authors) not listed copyright
[07:11] <slomo> hub: copyright is wrong in pandora
[07:11] <stratus> lucas: sure, but spammers don't give a fuck about them, so if they look coming from ubuntu.com smtp, wee..
[07:11] <slomo> hub: "Copyright (C) 1995 Spencer Kimball and Peter Mattis" is missing
[07:11] <hub> ah well, yeah
[07:12] <slomo> hub: shall i fix it? and "Software is licensed under GPL version 2 (see COPYING file)." can be left out imho
[07:12] <slomo> hub: it's only confusing
[07:12] <hub> slomo: I'll do it
[07:12] <slomo> hub: ok, ping me when you uploaded a new version :)
[07:14] <stratus> is it just me that sometimes look at slomo nick and read elmo ?
[07:14] <hub> stratus: just you
[07:14] <stratus> damn, i need to upgrade something in my eyes
[07:15] <hub> stratus: yeah, new firmware"
[07:15] <slomo> stratus: lol... no i'm not elmo ;P why? because i'm so picky about copyright?
[07:15] <stratus> hub: the same thing with you switch, err i mean hub. :-)
[07:16] <stratus> slomo: heh i really know that you're not elmo. There's just something funny about slomo and elmo that my eyes mess up sometimes.
[07:16] <slomo> hub: pandora is fine except copyright... good work :)
[07:16] <stratus> hub: yes, i need a new firmare that fix keratoconus. :-|
[07:17] <hub> slomo: http://revu.tauware.de/details.py?upid=1967
[07:17] <slomo> hub: ok, fine with me :)
[07:18] <jpatrick> apachelogger: done
[07:19] <apachelogger> hoooray :)
[07:19] <slomo> hub: uploaded
[07:19] <hub> slomo: thanks.
[07:19] <hub> slomo: I could have too :-)
[07:20] <slomo> oh, yes... sorry :)
[07:20] <hub> np
[07:21] <stratus> dholbach: news about UVFStatus processing?
[07:22] <dholbach> stratus: matt asked me to change the process, we're still discussing, I'll give an update, once we're done
[07:23] <stratus> dholbach: oh, ok let me know. :-)
[07:26] <dholbach> sistpoty: go, make the a11y happy! :)
[07:26] <sistpoty> hehe
[07:31] <pef> hello
[07:31] <slomo> does someone know where one could subscribe to the motu-reviewers mailing list? :)
[07:32] <fbond|away> http://tauware.de/cgi-bin/mailman/listinfo/motu-reviewers
[07:33] <slomo> thanks :)
[07:33] <fbond|away> np
[07:36] <sistpoty> TheMuso: please look at speechd-up comments
[07:37] <fbond|away> sistpoty: linuxsampler?
[07:37] <fbond|away> qsampler has been ok'ed, and is useless without linuxsampler...
[07:37] <sistpoty> fbond|away: will take a look
[07:37] <lfittl> sistpoty: ping
[07:37] <fbond|away> thanks!
[07:37] <sistpoty> lfittl: pong
[07:38] <lfittl> dholbach: ping
[07:39] <slomo> wb lfittl :)
[07:39] <lfittl> hi slomo :)
[07:40] <slomo> lfittl: anagramarama built fine everywhere... good work :)
[07:40] <fbond|away> sispoty: actually, can you hold up 5 minutes on linuxsampler?
[07:40] <lfittl> slomo: saw that, I really like the launchpad way to manage builds :)
[07:41] <Gloubiboulga> Riddell, ping
[07:41] <slomo> fbond|away: a question for linuxsampler...
[07:41] <fbond|away> sistpoty: had to make a quck change
[07:41] <fbond|away> slomo: yes?
[07:42] <slomo> fbond|away: why do you install the libs to /usr/lib/linuxsampler
[07:42] <fbond|away> oy, you had to ask
[07:42] <fbond|away> i didn't make that decision, that is the default for the package
[07:42] <slomo> fbond|away: put them in /usr/lib... make an liblinuxsampler0 and liblinuxsampler-dev package
[07:42] <fbond|away> should i change it?
[07:42] <slomo> imho yes
[07:42] <Riddell> Gloubiboulga: hi
[07:42] <Gloubiboulga> hi Riddell
[07:43] <Gloubiboulga> Riddell, I've tested gnetswitch, it segfaults in a chroot, but not on my dapper box
[07:43] <Riddell> spooky
[07:43] <Gloubiboulga> did you test it in a chroot too ?
[07:43] <Riddell> no
[07:44] <Gloubiboulga> Riddell, I've changed some little things, could you test my package ?
[07:44] <Gloubiboulga> I can upload it to REVU
[07:45] <sistpoty> fbond: yes, please change that and also remove the postrm, postinst (dh_makeshlibdeps will care for that)
[07:46] <Riddell> Gloubiboulga: yes, but not just now
[07:46] <Gloubiboulga> ok, I'll upload it, test it when you want Riddell :)
[07:47] <sistpoty> fbond: wait a minute plz, I want to take a look at what exactly is in the linuxsampler package
[07:52] <jpatrick> can someone advocate http://revu.tauware.de/details.py?upid=1964 so I can upload?
[07:52] <sistpoty> jpatrick: /me looks
[07:52] <jpatrick> sistpoty: pbuilds and all and lintian's happy with it
[07:53] <sistpoty> jpatrick: ok, will take just a few minutes
[07:53] <jpatrick> all problems are on apachelogger
[07:55] <sistpoty> apachelogger: please just bunzip2 and gzip -9 tar.bz2 you downloaded, but don't repackage it
[07:56] <marcin`> sistpoty: hello
[07:56] <sistpoty> hi marcin`:
[07:56] <marcin`> sistpoty: could you tell me how can I remove some package from REVU?
[07:56] <sistpoty> marcin`: you can't... only revu-admins can do that
[07:57] <sistpoty> marcin`: you can tell me, I'll remove them
[07:57] <jpatrick> I think thats planned for revu2
[07:57] <marcin`> sistpoty: are you one of them?
[07:57] <sistpoty> marcin`: yes
[07:57] <marcin`> sistpoty: ok then please remove vtiger-crm and vtiger-crm-mysql-local
[07:57] <marcin`> sistpoty: we changes naming convention and now package name is vtigercrm
[07:58] <marcin`> sistpoty: you can also remove vtigercrm-mysql-local
[07:58] <sistpoty> marcin`: will take a few clicks ;)
[07:58] <marcin`> sistpoty: because now vtigercrm-mysql-local will be integrated in vtigercrm source
[07:58] <sistpoty> ok
[07:58] <marcin`> so keep only vtigercrm
[07:59] <marcin`> thanks and sorry about this mess ;)
[08:00] <sistpoty> no problem
[08:01] <sistpoty> fbond: for linuxsampler - it's a little bit tricky if you want to build a library and a binary from the same sourcepackage
[08:01] <sistpoty> fbond: are the shared-objects used/usefule for anything but linuxsampler binary?
[08:01] <apachelogger> sistpoty: what's changed in my orig?
[08:02] <sistpoty> fbond: if not, I would suggest you remove them and the static library and do static linking
[08:02] <sistpoty> apachelogger: mom
[08:03] <jpatrick> :/
[08:04] <sistpoty> apachelogger: if I gunzip your orig.tar.gz and bunzip2 what I can download, the tar's should be bit-identical (unless there is a really, really good reason to change the upstream tar)
[08:04] <sistpoty> apachelogger: and unless I downloaded the wrong file, the md5sums of the tar's don
[08:04] <fbond> sistpoty: I don't believe the libraries are useful for anything else, but I could be wrong
[08:04] <sistpoty> +'t match
[08:04] <fbond> and I guess you never really know
[08:05] <apachelogger> sistpoty: I'll check
[08:05] <fbond> is it a good idea to deviate so drastically from a package's standard install?
[08:05] <fbond> I don't know if doing static linking is the best way to go...
[08:06] <sistpoty> fbond: still another possibility is to make linuxsampler load the shared objects from /usr/lib/linuxsampler, but then you can't change ld.so in postrm/postinst
[08:07] <sistpoty> fbond: but I wouldn't really know how to do that right for myself ;)
[08:07] <fbond> why not just put libs in /usr/lib, and pretend they may be useful for other binaries, even if they actually aren't?
[08:08] <sistpoty> fbond: if you put them into /usr/lib, you'll need build a complete library-package (with -dev package)
[08:08] <fbond> hmpf, -dev is not currently installed by 'make install'
[08:08] <fbond> (no headers are installed)
[08:09] <apachelogger> sistpoty: that's really odd, as there is actually no diff according to diff ;-)
[08:09] <apachelogger> anyway I'll re gzip the orig
[08:10] <sistpoty> apachelogger: than it should be the same, right?... if that's the only problem, you don't need to reupload, I can exchange the orig then for uploading... (but I'm not completely done with reviewing)
[08:10] <fbond> sistpoty: so going the static-link route, all I need to do is CFLAGS += "-static"; CXXFLAGS += "-static" ?
[08:10] <sistpoty> fbond: and it's a little bit tricky, since you build a binary package and a library package from the same sourcepackage (see the debian library packaging guide for hints about how to do it)
[08:11] <apachelogger> sistpoty: ok, I'll check md5 for future packages :-)
[08:11] <sistpoty> fbond: just try it out... maybe there is some configure-flag there as well, like --disable-shared?
[08:12] <fbond> hmm...
[08:12] <sistpoty> apachelogger: :)
[08:13] <sistpoty> apachelogger: is /usr/share/apps/kicker/menuext the right place for the desktop file? (ha, i use kde... but my knowledge is rather limited on it *g*)
[08:13] <apachelogger> yup
[08:13] <apachelogger> menuext is for menu buttons
[08:14] <apachelogger> like the system or remote button
[08:14] <apachelogger> contactsmenu is such a button ;-)
[08:15] <sistpoty> apachelogger: ok, then I'll retry building with exchanged tarball and upload if it's still working ;)
[08:15] <apachelogger> hooray :-D
[08:20] <sistpoty> apachelogger: args... your debian/copyright is wrong... you'll need to change this
[08:20] <sistpoty> apachelogger: there is at least one file with a different license: contactsmenu/librss/article.h
[08:21] <jpatrick> just one....
[08:22] <sistpoty> apachelogger: and the COPYING file is LGPL while the sourcecode says it is GPL, please check all source-code files what license applies
[08:23] <sistpoty> jpatrick: doesn't matter if it's one or a dozen... if debian/copyright doesn't match the license of the files, it usually results in a reject from the new-queue
[08:23] <jpatrick> I know
[08:26] <apacheLAGger> well
[08:27] <apacheLAGger> unghost ;-)
[08:27] <apachelogger> better
[08:27] <sistpoty> apachelogger: did you read the issues? or were already off?
[08:27] <jpatrick> I think he did
[08:28] <apachelogger> the license?
[08:28] <sistpoty> apachelogger: yep
[08:28] <apachelogger> I checked that
[08:28] <apachelogger> it's lgpl
[08:28] <apachelogger> though
[08:28] <apachelogger> the packages includes librss from akregator
[08:28] <apachelogger> and that's gpl2 and later
[08:28] <apachelogger> dunno which one I should use
[08:29] <sistpoty> apachelogger: both ;)
[08:29] <apachelogger> ah :-D
[08:29] <apachelogger> sistpoty: reupload?
[08:30] <sistpoty> apachelogger: either explicitely state which files fall under which license (or if it's all files in one dir with a different license, you can also list this)
[08:30] <sistpoty> apachelogger: please do
[08:30] <apachelogger> k
[08:32] <sistpoty> apachelogger: actually it appears to be even 3 licenses: LGPL (for most files), GPL for librss and BSD-like for parts of librss by Frerich Raabe
[08:34] <sistpoty> hehe
[08:35] <apachelogger> sistpoty: shell I call it lesser?
[08:35] <apachelogger> library is kinda outdated, isn't it?
[08:35] <sistpoty> apachelogger: call it the way it's referred to in the sourcecode... that's never wrong
[08:35] <apachelogger> ok
[08:37] <sistpoty> jpatrick: just in case you review contactsmenu again, if the two points I mentioned are fixed (and there is no dramatic change in the debdiff) feel free to take this as advocacy from me
[08:37] <jpatrick> sistpoty: okay
[08:38] <jpatrick> apachelogger: fix it
[08:38] <sistpoty> jpatrick: (you can always do this if I write s.th. like "fix these things and you have my vote")
[08:38] <apachelogger> anyone knows a copyright file I can use as example for the super-multi-licensing?
[08:39] <jpatrick> apachelogger: I'll get one
[08:39] <sistpoty> apachelogger: quake3 on revu does it pretty good...
[08:40] <apachelogger> ok, thx
[08:46] <fbond> sistpoty: hope you enjoyed your smoke.  i have just uploaded reworked linuxsampler.
[08:46] <fbond> the new source package generates one binary package that installs a statically linked binary
[08:47] <fbond> seems to work well...i stripped some garbage out of upstream's debian dir
[08:47] <fbond> gave me "ignoring deletion of XXX" messages when running debuild -sa -S
[08:48] <fbond> i think i want those changes to stay in diff.gz, though...thoughts?
[08:50] <sistpoty> fbond: you'll need to make sure files you deleted are gone during build time as well (so you'll need to delete them in the clean-rule)
[08:51] <sistpoty> fbond: the best way to handle this, is to talk to upstream and ask if they can make a release w.o. a debian-directory
[08:51] <dolson> fbond: I have the same issue with qsampler
[08:51] <fbond> yeah, it's not as helpful as it might seem :)
[08:51] <sistpoty> fbond: you could also repack the orig-tarball for one release, but I don't like this as a permanent solution
[08:52] <fbond> ok
[08:52] <fbond> can i repack and then chat with upstream?
[08:52] <sistpoty> fbond: yes... you needed to repack linuxsampler anyway didn't you?
[08:52] <fbond> yeah, i already did ... i will do it again
[08:53] <fbond> stay posted
[08:53] <sistpoty> fbond: then please delete the complete debian-dir for repacking, makes the diff.gz more readable ;)
[08:55] <fbond> sistpoty: done, uploading momentarily
[08:55] <sistpoty> fbond: ok, will take a look once it's there
[08:55] <fbond> please note that I also had to remove references to debian dir from e.g. Makefile.in
[08:56] <dolson> what are the chances any packages in REVU that rely on dssi being sync'd will be successfully reviewed and uploaded in time?
[08:57] <sistpoty> dolson: no idea really... maybe we could ask for exceptions
[08:57] <sistpoty> dolson: I locally built dssi last night, so I can do reviewing, but I can't upload yet, because of the dependency
[08:57] <apacheLAGger> wooh
[08:57] <apacheLAGger> unghost
[08:58] <dolson> ah
[08:58] <dolson> sistpoty: you need an exception to upload, even if they are marked as ready for upload prior to FF. correct?
[08:59] <apachelogger> sistpoty, jpatrick: http://paste.ubuntu-nl.org/9134 usable?
[09:00] <jpatrick> apachelogger: you scared him away
[09:00] <sistpoty> bah... always these disconnects *G*
[09:00] <jpatrick> ah! wb sistpoty
[09:00] <sistpoty> re ;)
[09:00] <apachelogger> wb I say
[09:01] <jpatrick> apachelogger: looks good
[09:01] <apachelogger> that has to be sarcastic
[09:01] <apachelogger> oh
[09:01] <apachelogger> again meeting?
[09:02] <fbond> sistpoty: new linuxsampler just uploaded, may take a min to appear
[09:02] <sistpoty> fbond: k
[09:02] <jpatrick> sistpoty: did you get apachelogger's copyright thing?
[09:02] <sistpoty> jpatrick: no
[09:02] <apachelogger> http://paste.ubuntu-nl.org/9134
[09:03] <sistpoty> apachelogger: nice
[09:04] <apachelogger> woot
[09:04] <apachelogger> I'll upload
[09:04] <sistpoty> anybody else having problems with the revu page?
[09:04] <sistpoty> oh, works again :)
[09:06] <fbond> sistpoty: why is dssi not currently sync-able?
[09:06] <sistpoty> fbond: because nothing is syncable atm
[09:06] <dolson> hmm, my omins pkg was based on someone else's work, so that's why it's fuxxored
[09:06] <sistpoty> fbond: there seem to be problems with soyuz (our new build-system) and syncs...
[09:07] <sistpoty> fbond: but the last comments I got look promising... maybe we have syncing back online in a few days
[09:08] <fbond> sistpoty: the timing is less than convenient, no?
[09:09] <Se7h> hi
[09:09] <sistpoty> fbond: the only appropriate timing would have been right after a release... when everybody is on holidays ;)
[09:09] <sistpoty> hi Se7h
[09:10] <fbond> sistpoty: :)
[09:10] <fbond> okay, time to get back to what i'm paid to do
[09:10] <sistpoty> Gloubi_Aw: I'm not entirely happy with new netswitch world order... did you get any comments from other motu's about package layout yet?
[09:10] <fbond> sistpoty, i'll check back in on linuxsampler in a bit
[09:10] <sistpoty> fbond|away: ok, I'll be looking at it now
[09:13] <apachelogger> sistpoty: http://revu.tauware.de/details.py?upid=1974
[09:14] <sistpoty> apachelogger: queued ;)
[09:14] <apachelogger> aye, thx :-)
[09:15] <jpatrick> should I upload?
[09:16] <sistpoty> jpatrick: if you're happy with it, go ahead
[09:16] <jpatrick> :)
[09:18] <jpatrick> apachelogger: one second
[09:25] <jpatrick> apachelogger: done: https://launchpad.net/people/apachelogger/+packages
[09:26] <apachelogger> arrr :D
[09:26] <apachelogger> jpatrick: thanks a lot
[09:26] <jpatrick> no problem
[09:28] <sistpoty> Tonio_: I just glimpsed over new netswitch... I'm not entirely happy with everything being in one package
[09:29] <jpatrick> sistpoty: I don't think Tonio_'s actually..... here
[09:29] <sistpoty> ah, k
[09:29] <marcin`> raphink: ping
[09:33] <jpatrick> marcin`: he's in a meeting
[09:41] <marcin`> jpatrick: ok
[09:41] <sistpoty> marcin`: vtigercrm-mysql-local should stay on revu or go as well?
[09:42] <marcin`> sistpoty: remove this one too
[09:43] <marcin`> sistpoty: there will be package vtigercrm-mysql-local but only 'binary'
[09:43] <marcin`> sistpoty: this package will be created from vrigercrm source
[09:44] <sistpoty> marcin`: ok, just a sec and it's gone as well
[09:44] <marcin`> I'll upload new vtigercrm soon and I hope it will go to dapper..
[09:46] <sistpoty> ok... only vtigercrm left :)
[09:46] <marcin`> thanks
[09:46] <marcin`> btw got a question - how to resolve this problem...
[09:47] <marcin`> vtigercrm is collaborative work
[09:47] <TheMuso> sistpoty: Thanks... I will have a look.
[09:47] <TheMuso> slomo: thanks.
[09:47] <marcin`> and there is a guy that wants to maintain this package in debian
[09:47] <marcin`> and vtiger is also ubuntu bounty
[09:48] <marcin`> and we did this package together - let's say it's 50% his job and 50% mine
[09:48] <marcin`> then problem is that Maintainer field in control can contain only 1 name
[09:49] <marcin`> and I would like to maintain this package in ubuntu and he wants to in debian...
[09:49] <marcin`> how to resolve this problem and what should I put into control/copyright and changelogs?
[09:50] <fbond|away> sistpoty: saw your comments, uploaded new linuxsampler package with very slight changes
[09:51] <sistpoty> marcin`: you did the package together, so why not collaborate in the future?
[09:51] <sistpoty> marcin`: are there changes that need to be done for the ubuntu-version only?
[09:52] <sistpoty> fbond|away: ok
[09:55] <sistpoty> fbond|away: the debdiff is ok, so unless it suddenly FTBFS you still have my vote ;)
[09:55] <marcin`> sistpoty: I don't think so
[09:56] <marcin`> sistpoty: it's webapp so there is nothing 'distrospecific'
[09:56] <sistpoty> marcin`: then I guess it might be a good idea to work together on *one* package instead of having two ppl. caring for two distinct packages
[09:56] <marcin`> sure - we work together
[09:57] <marcin`> question is who should be mentioned in Maintainer field
[09:57] <sistpoty> marcin`: you could then use e.g. alioth and set the maintainer to vtigercrm-devs (mailing list)
[09:57] <sistpoty> marcin`: and changelog entries: whoever does a specific change should be listed there
[09:57] <marcin`> sistpoty: pretty nice idea
[09:57] <sistpoty> marcin`: imo there is also the possibility of a co-maintainer field, can't find a reference for it now though
[09:58] <sistpoty> marcin`: at leasts that's the way it's done for collaborative maintenance projects in debian (using list as maintainer-field=
[09:58] <sistpoty> ususally ;)
[09:59] <marcin`> ok and what about this: different maintainer or ubuntu and different for debian?
[09:59] <marcin`> is this possible?
[10:00] <sistpoty> marcin`: it is... but that would imply to care for two different sourcepackages
[10:00] <sistpoty> marcin`: so I wouldn't recommend it
[10:01] <dholbach> sistpoty: fancy another look at linuxsampler?
[10:01] <sistpoty> dholbach: just at it... and I think it compiled well
[10:02] <dholbach> *highfive sistpoty*
[10:02] <sistpoty> dholbach, fbond|away: no, still going... the automake issue isn't solved, but since it didn't FTBFS last time with the issue, I'm fine with it (but I just like to see the package being built though)
[10:03] <fbond|away> sistpoty: yes, I did 'touch configure' in my package dir, rather than in my faked tarball
[10:04] <fbond|away> i just realized it, and a new upload is on its way
[10:04] <fbond|away> i am a bit of a perfectionist
[10:04] <sistpoty> fbond|away: hehe... ok, if you want to be perfectionistic, I'll try another build with that upload. If it builds, I'm more than happy with it
[10:05] <fbond|away> alrighty
[10:06] <dolson> MOTUs++
[10:07] <sistpoty> as in we need more motus for reviewing? *g+
[10:07] <dolson> lol
[10:07] <dolson> no, you guys are kicking royal rump
[10:07] <sistpoty> thx
[10:07] <dolson> I'm trying to fix omins now
[10:07] <dolson> I really do need sleep soon though :\ 4pm here
[10:17] <sistpoty> dholbach: did you just review an old version of linuxsampler or just made your comment to the wrong version? *g*
[10:19] <dholbach> erm
[10:19] <dholbach> there were so many versions now :)
[10:19] <sistpoty> hehe
[10:20] <sistpoty> dholbach: if it builds (and I'm 99.9% sure it does) my vote still counts ;)
[10:20] <dholbach> ok i test-build again and see
[10:21] <dholbach> gphotofs has two silly changes waiting, i'd nearly do them myself and get it up :)
[10:21] <dholbach> gopersist looks good too
[10:21] <dholbach> (to poke hub's packages a bit)
[10:21] <dholbach> (let's see if etl builds this time)
[10:22] <TheMuso> dholbach: Has speech-dispatcher 0.6 gone through yet?
[10:22] <TheMuso> If so, I have the grounds to upgrad speechd-up as well.
[10:22] <dholbach> TheMuso: should have
[10:22] <TheMuso> Righto.
[10:22] <dholbach> TheMuso: i uploaded it some hours ago
[10:22] <TheMuso> right
[10:23] <TheMuso> btw what is the variable used in the control file to represent the source package version?
[10:23] <sistpoty> TheMuso: version in changelog entry
[10:24] <Gloubiboulga> sistpoty, have you tested gnetswitch ?
[10:24] <TheMuso> sistpoty: Yes.
[10:25] <Gloubiboulga> btw Tonio_ has made the *netswitch packages :)
[10:25] <sistpoty> Gloubiboulga: no, I just built it and looked at the results
[10:25] <sistpoty> Gloubiboulga: yes, found that out later ;)
[10:25] <sistpoty> TheMuso: that's the field ;)
[10:25] <Gloubiboulga> sistpoty, could you test it ?
[10:25] <Gloubiboulga> gnetswitch segfault on Riddell's box, but not on mine
[10:26] <sistpoty> Gloubiboulga: I'd like to review some more packages right now if you don't mind
[10:26] <Gloubiboulga> sistpoty, np
[10:26] <TheMuso> sistpoty: Ok let me explain. I want to take the package version and use it in the debian/control file as a version for a dependancy. What s the variable that I use?
[10:27] <marcin`> well guys.. ArmeBosse and me are working on vtigercrm package
[10:27] <marcin`> and we still don't know for 100% what to do with 'maintainer issue'
[10:28] <sistpoty> TheMuso: ah, got it now... it's ${Source-Version}
[10:28] <stratus> marcin`: why?
[10:28] <TheMuso> Thanks.
[10:28] <stratus> marcin`: you're free to use "foo maintainers <groupemail@...>" and list the two in uploaders field.
[10:30] <marcin`> hmmm but what if we would like to have different maintainers for debian and ubuntu?
[10:30] <TheMuso> sistpoty: BTW, I originally didn't upgrade speechd-up because it was incompatible with one of it's dependancies, but now that has been updated, we are all clear.
[10:30] <sistpoty> dholbach: what's wrong with the maintainer field/config.log in gphotofs?
[10:30] <stratus> marcin`: is there anyone working on the same package for debian?
[10:31] <ArmeBosse> hoyes me
[10:31] <ArmeBosse> -ho
[10:31] <stratus> ArmeBosse: i would like to suggest you request a project in alioth, you can include marcin`in the project there.
[10:31] <dholbach> sistpoty: .et -> .net
[10:31] <stratus> ArmeBosse: you can use the same approach as pkg-zope group
[10:31] <dholbach> sistpoty: config.log is a generated file, but a very minor nuisance
[10:32] <sistpoty> TheMuso: the version is alright for me... if you have the time you can go for a newer version, but that's just an additional bonus
[10:32] <dholbach> sistpoty: talked to hub about it
[10:32] <stratus> apt-cache show zope3, do you see the maintainer field?
[10:32] <hub> config.log is in the upstream tarball
[10:32] <stratus> marcin`: alioth.debian.org, it's gforge' debian installation
[10:32] <sistpoty> dholbach: lol, I looked half a minute at it and didn't see that it's written wrong ;)
[10:32] <hub> I remove ti in clean
[10:33] <sistpoty> hub: and you might want to set the section to s.th. else than unknown ;)
[10:33] <stratus> marcin`: you're free to not use alioth, but you should cooperate in the maintainership thing as pkg-zope (they're using alioth) guys are doing.
[10:33] <hub> sistpoty: yep, was doing that oo
[10:33] <stratus> marcin`: apt-cache show zope3
[10:33] <marcin`> stratus: well but what if I don't want to be debian maintainer ;) ?
[10:33] <ArmeBosse> stratus: i'm ok for this, and know the procedure
[10:34] <ArmeBosse> stratus: the problem is that marcin don't want to be involved in debian
[10:34] <marcin`> stratus: another funny part is that why to hell there is 'This package was debianized... ' in copyright file in ubuntu package :) ?
[10:34] <stratus> marcin`: you don't need to be a debian maintainer to be listed in a project there (alioth) and you don't need to be a debian maintainer to share the "debian/ubuntu ..." thing in the maintainer field, really!
[10:35] <stratus> marcin`: deb is the package format too, see man 5 deb
[10:36] <marcin`> ok forget it.. but it's pretty weird that ubuntu looks like subdebian distro...
[10:36] <ArmeBosse> stratus: another problem is claiming debian/ubuntu package :) as you can see marcin is only interested by ubuntu part
[10:36] <marcin`> not like something independent
[10:36] <stratus> ArmeBosse: He won't be involved directly, it's just a cooperative issue, he's not forced to be a debian maintainer, as you know. If he has a problem with the Debian name he should move away from FLOSS, because he can't stop anybody merge his packages back to any deb based distribution.
[10:36] <stratus> ArmeBosse: there are some pkg-zope members that are only interested in Ubuntu part, i still fail to see the point.
[10:37] <sistpoty> hub: did you repack the orig-tarball?
[10:37] <dholbach> sistpoty: linuxsampler ready to go, sir!
[10:37] <marcin`> stratus: I don't have any problem with Debian - the thing is that I don't use Debian and I don't want to
[10:37] <dholbach> sistpoty: it was in the upstream tarball :)
[10:37] <sistpoty> dholbach: what was in the upstream tarball?
[10:37] <dholbach> config.log
[10:38] <marcin`> stratus: and this particular package is not something that will be different in debian and ubuntu
[10:38] <stratus> marcin`: great, you won't be involved with Debian just sharing the maintainer field with "them"
[10:38] <dholbach> if you refer to that
[10:38] <sistpoty> dholbach: will you upload linuxsampler, or shall i
[10:38] <dholbach> sistpoty: i don't mind either way
[10:38] <sistpoty> dholbach: but that's no reason to modify the orig-tarball
[10:38] <sistpoty> dholbach: ok, I'll go for it
[10:38] <dholbach> sistpoty: i upload, you comment and archive
[10:38] <sistpoty> dholbach: fine for me as well ;)
[10:38] <dholbach> ROCK :)
[10:39] <dholbach> hub: you got etl building! NICE!
[10:39] <marcin`> stratus: but I would like to make few new packages and then for example I don't want to get 'debianspecific' question etc.
[10:39] <tepsipakki> hi, I sent an email on u-d and asked if someone could review some packages (libgssapi, librpcsecgss, libnfsidmap). they should be an easy task, because upstream has already made packages of them, so the changes are minimal...
[10:39] <marcin`> stratus: I think that currently we will leave debian maintainer credentials but I just wonder how these debian/ubuntu relations work
[10:40] <stratus> marcin`: you'll get questions and bug reports through ubuntu malone.
[10:40] <stratus> marcin`: you can setup a list to discuss general deb (debian, ubuntu, ...) specifics stuff about that package and point "debian/ubuntu foo maintainers <put the list mail here>", if you want
[10:41] <hub> dholbach: I have the rest waiting
[10:41] <stratus> marcin`: so it will be safe to you treat that list as low priority, because the bug reports will go through malone.
[10:41] <hub> dholbach: like synfig
[10:41] <hub> dholbach: but I held on it I don't remember why
[10:41] <TheMuso> When one links config.guess/config.sub, where does one link them from?
[10:41] <dholbach> hub: i tried it too
[10:41] <stratus> marcin`: i'm sure that a user here and there will send bug reports to the list, but the list itself will ask the guys to use malone or debian BTS when necessary. Do you see?
[10:41] <hub> sistpoty: no I didn't tocuh the orig tarball
[10:41] <hub> dholbach: and it didn't work?
[10:42] <dholbach> hub: no, world breakage
[10:42] <dholbach> hub: but that was a while ago
[10:42] <hub> uh oh
[10:42] <sistpoty> hub: hm... where did you get it from? (found only .tar.bz2 on on page)
[10:42] <marcin`> stratus: ok but what if we have ArmeBosse as debian maintainer and his package
[10:42] <stratus> marcin`: if you're in doubt just take a look how the pkg-zope and some other teams are doing it, i think ArmeBosse can guide you through these part of Debian internals, but alioth.debian.org is a good start point
[10:42] <hub> sistpoty: ah maybe I did bunzip -c | gzip -9c
[10:42] <marcin`> stratus: and then I would like to create some improvements or changes that ArmeBosse will not want to implement in debian package?
[10:42] <hub> sistpoty: but not more than that
[10:43] <sistpoty> hub: the md5sums of the bz2 didn't match (and the size didn't as well)... maybe I dl'd the wrong thing again ;)
[10:43] <hub> sistpoty: :-/
[10:43] <ArmeBosse> marcin`: you keep it in your branch/patch of the debian package
[10:43] <stratus> marcin`: if the package will be the same (no ubuntuX revisions), it's sane let the MoM do its work automatically and get rid of differences, even in the maintainer field, IMHO. It's how i handled gdebi package with mvo, until UVF.
[10:44] <marcin`> stratus: too many abbreviations :)
[10:44] <stratus> marcin`: heh you described exactly what's going on with gdebi right now.
[10:44] <stratus> marcin`: they're all in wiki.ubuntu.com, i think.
[10:45] <marcin`> ArmeBosse: btw my questions are not vtigercrm related now.. I'm just curious
[10:45] <Gloubiboulga> sistpoty, when you got time, could you tell me what's the problem with the *switch packages ?
[10:45] <sistpoty> Gloubiboulga: give me 5 mins, ok?
[10:45] <Gloubiboulga> sistpoty, ok
[10:45] <stratus> marcin`: once you decide to diverge from debian package you can keep that stuff in a different branch than ArmeBosse, as he said.
[10:46] <stratus> marcin`: I'm using bazaar-ng to keep the gdebi' debian tree and mvo has the main repository that is the same for Ubuntu.
[10:47] <ArmeBosse> marcin`: you can look pkg-kde and Riddell related work on alioth
[10:47] <sistpoty> hub: isn't the universe-part of the section usually set by the ftpmaster? (actually I only heard rumors about it, though I'm really curious)
[10:47] <stratus> marcin`: We used to have the same trees almost in sync, but once Ubuntu started the Upstream Version Freeze (UVF), he started to add some changes to his repository that i don't need yet.
[10:48] <stratus> marcin`: before the UVF, we uploaded gdebi for Debian and waited Ubuntu sync that automagically. :-)
[10:48] <hub> sistpoty: I took the one from fuse-utils
[10:48] <marcin`> stratus: ok and then what do you have in Maintainer field?
[10:48] <hub> sistpoty: but if that is wrong, well.
[10:48] <hub> sistpoty: is there any documentation about that?
[10:49] <stratus> marcin`: i think actually we've my name in the maintainer field and mvo in uploaders field, since we don't need that mailing list for discussion. :-)
[10:49] <sistpoty> hub: I guess it's wrong... imo that's part of that override-file-thingy, but actually I don't have a real clue about it ;)
[10:49] <marcin`> ok
[10:49] <hub> sistpoty: okay
[10:49] <sistpoty> hub: and no idea where to find documentation
[10:49] <stratus> marcin`: i never received a bug report related with ubuntu in my own email or through debian bts
[10:49] <hub> what do you think is best I put on this one?
[10:50] <marcin`> stratus: ok thanks.. now we need to finish this package and put it in dapper :)
[10:50] <stratus> marcin`: np, good luck.
[10:50] <hub> sistpoty: I'll just put utils
[10:51] <sistpoty> hub: yes... I'll just take a look at the result... you won't need to upload again only for that change (imo)
[10:52] <sistpoty> hub: we could ask elmo (I saw him chatting in LP), but I guess he'll kill us cause he's busy with getting syncs back online ;)
[10:52] <hub> sistpoty: I just put "utils"
[10:52] <sistpoty> ok
[10:52] <hub> sistpoty: if it is OK I cna upload to the archive
[10:53] <sistpoty> hub: looks good... just a smal moment and I'm through it
[10:53] <hub> ok
[10:54] <sistpoty> hub: +1 from me
[10:54] <siretart> n'evening
[10:54] <siretart> hi sistpoty!
[10:54] <sistpoty> hi siretart
[10:54] <siretart> sistpoty: how are you? long time no see :)
[10:54] <hub> dholbach: so shall I upload gphotofs?
[10:54] <hub> allo siretart
[10:54] <siretart> huhu hub!
[10:54] <dholbach> hub: you got two votes? then go for it
[10:54] <dholbach> hub: nice one
[10:55] <dholbach> hey siretart
[10:55] <siretart> dolson: we are at the same university. our nicknames are our loginnames at uni
[10:55] <sistpoty> siretart: fine, what about you?
[10:55] <siretart> huhu dholbach
[10:55] <siretart> sistpoty: lerning stress, getting into the hot phase. but in general, fine :)
[10:55] <hub> dholbach: i would be #2 :-)
[10:55] <sistpoty> siretart: oh, good luck then!
[10:55] <hub> dholbach: sistopy gave his
[10:55] <dolson> siretart: ah. I just have a hard time with things... see, I never learned to read
[10:55] <hub> sistpoty I meant
[10:55] <dholbach> i gave mine too
[10:56] <hub> ah ok
[10:56] <hub> done
[10:57] <sistpoty> hub: btw.: there seems to be s.th. strange with libfuse... there is no versioned dependency on it in the gphotofs-binary-db
[10:57] <sistpoty> s/db/deb/
[10:57] <hub> sistpoty: oh
[10:57] <sistpoty> hub: but it's from shlibs:depends, so gphotofs is not at fault
[10:58] <hub> sistpoty: a bug shall be filed
[10:58] <hub> :-)
[10:58] <sistpoty> hub: I'm not sure if it's a bug even... it's just strange ;)
[10:58] <hub> yeah
[10:59] <cyberserver> Hi people. Anyone is facing strange behaviour from mysql+apache with dapper? It seems mysql places the shared pipe inside a directory which apache cannot read....
[11:00] <cyberserver> .. the result is that apache+php+mysql apps cannot bind to dabatase
[11:00] <Gloubiboulga> cyberserver, it's a known bug iirc
[11:00] <sistpoty> cyberserver: known bug, will be resolved soon
[11:01] <cyberserver> Oh, ok. I have come around it chmodding /var/whatever..   ok, thx, no need to fill a bug report then :-)
[11:01] <TheMuso> slomo: Around?
[11:01] <slomo> TheMuso: yes
[11:01] <TheMuso> Is it possible for me to accesss the changed copyright file for the uploaded orca pacage?
[11:01] <TheMuso> btw sistpoty I have split the package into two, what should I do with it if orca is already waiting for upload?
[11:01] <sistpoty> cyberserver: 755 are the intendended rights, if you want to fix it locally ;)
[11:02] <cyberserver> sistpoty: ok, but the fix is not persistent... I need to reapply after a reboot...
[11:02] <slomo> TheMuso: nope... i deleted it already :/ wait for it to leave NEW
[11:02] <sistpoty> cyberserver: then just wait for updated packages ;)
[11:03] <sistpoty> TheMuso: I'd suggest waiting till it hit the archives... it's easier to update it then
[11:03] <cyberserver> sistpoty: maybe I should turn that "lock" bit on? I dont remember exactly how, but I know there is a way... "immutable bit" is the name, IIRC .....
[11:04] <sistpoty> cyberserver: never heard of that one
[11:04] <TheMuso> Ok.
[11:05] <Kyral> the Sticky bit?
[11:05] <cyberserver> chattr +i , IIRC
[11:05] <sistpoty> Gloubiboulga: for the netswitch package
[11:06] <sistpoty> Gloubiboulga: it's all going into one big package
[11:06] <cyberserver> Kyral: no... IIRC, the sticky bit is one thing, the immutable bit is another thing
[11:06] <sistpoty> Gloubiboulga: I don't really see, where the shell-script makes use of the shared objects
[11:06] <cyberserver> http://linuxhelp.blogspot.com/2005/11/make-your-files-immutable-which-even.html
[11:07] <Kyral> Ah I remember reading about chatter in my copy of Linux in a Nutshell
[11:07] <Gloubiboulga> sistpoty, yep, that's why my package was split
[11:07] <TheMuso> Ok guys, new speechd-up is uploaded.
[11:07] <sistpoty> Gloubiboulga: and since there is stuff installed into /usr/lib, the package needs to conform to library packages (package matching soname, distinct -dev and lib package)
[11:08] <sistpoty> Gloubiboulga: yes, and imo the way you did it, is the way to go
[11:09] <Gloubiboulga> Tonio_ has certainly a good reason for it
[11:09] <cyberserver> Anyway we can propose the change of adept's behaviour so it does not stands in the traybar stating "there is 1 updated package available" when that package is in state "will be kept" ?
[11:10] <sistpoty> Gloubiboulga: but imo it's plain wrong to put shared objects into /usr/lib (or /lib) and not to follow the library packaging policy...
[11:10] <cyberserver> That notifiers irritates... cause one will click on it to do the update ... and then adept will say "nothing to do"
[11:10] <TheMuso> /c/
[11:10] <sistpoty> cyberserver: please file a wishlist bug about that
[11:10] <cyberserver> .. and keeps in the traybar stating there is 1 package to upgrade
[11:10] <cyberserver> sistpoty: ok
[11:12] <cyberserver> Well guys, I'm rebooting into the new kernel....
[11:12] <cyberserver> ... be back in a sec... or a minute...
[11:12] <TheMuso> time for some breakfast... finally. :)
[11:13] <sistpoty> time for a cigarette *g*
[11:14] <tepsipakki> is there now someone available for reviews? =)
[11:18] <tepsipakki> utter silence.. :/
[11:19] <Pygi> hehe :)
[11:19] <cyberserver> :-( chattr is not working with directories :-(
[11:20] <phanatic> hi people
[11:21] <cyberserver> Strange.... about this chattr problem : http://seclists.org/lists/linux-kernel/2001/Jul/2804.html
[11:22] <cyberserver> This should be fixed by now... unless it showed up again in 2.6
[11:27] <tepsipakki> it's a pity I'm possibly the only Finn here.. so offering a pint won't help getting reviews :)
[11:28] <sistpoty> tepsipakki: what package?
[11:28] <tepsipakki> sistpoty: i love you :)
[11:29] <sistpoty> hehe
[11:29] <tepsipakki> sistpoty: http://revu.tauware.de/details.py?upid=1959 http://revu.tauware.de/details.py?upid=1956
[11:29] <sistpoty> tepsipakki: queued... may take a little bit ;)
[11:29] <tepsipakki> those are the ones I'd like to see in universe
[11:29] <tepsipakki> thanks
[11:30] <tepsipakki> they are basically unchanged
[11:30] <hub> tepsipakki: first, there are config.sub and config.log in the digff
[11:30] <tepsipakki> hub: yes, how to get rid of them? note that the current libnfsidmap_0.8 also has them
[11:31] <tepsipakki> I mean, upstream has packaged them already, but they are not in debian yet
[11:31] <Gloubiboulga> sistpoty, I'll see discuss the netswitch issue tomorrow avec Tonio_
[11:32] <Gloubiboulga> I hope we'll find a great solution
[11:32] <sistpoty> Gloubiboulga: ok, thanks... though it seems to have been uploaded already
[11:32] <hub> tepsipakki: what I do is moving the rule where they are copied that are in clean:: to conf.status:
[11:32] <hub> tepsipakki: and delete them in clean::
[11:32] <Gloubiboulga> sistpoty, didn't know that...
[11:33] <LaserJock> hub: do you have an example debian/rules on that? I'm also interested in  how to get rid of config.{sub,log}
[11:34] <Gloubiboulga> good night :)
[11:35] <hub> LaserJock: not really, I do cdbs usually
[11:35] <hub> but what I said should work
[11:36] <sistpoty> hub: two things to fix for gopersist: debian/copyright should have the reference to GPL
[11:36] <sistpoty> hub: and W: libgopersist-1-0: package-name-doesnt-match-sonames libgopersist-1-1 (typo?)
[11:36] <hub> sistpoty: ah uh. will look into it
[11:38] <tepsipakki> hub: but wouldn't that leave the directory without those files, so the diff would still be big?
[11:38] <hub> tepsipakki: no. removal is ignored
[11:38] <tepsipakki> ack
[11:39] <hub> sistpoty: right, the package-soname is incorrect. damn
[11:39] <hub> sistpoty: will fix and update
[11:41] <sistpoty> hub: if you want, you can fix that locally and upload, since everything else is ok
[11:41] <hub> sistpoty: okay, thx
[11:42] <hub> sistpoty: raphink did comment
[11:42] <hub> sistpoty: I'll check that too
[11:43] <raphink> hub: if you can correct your package tonight, I'll upload it
[11:43] <SEJeff> How do I rebuild a source package after editing compile options in debian/rules ?
[11:43] <hub> raphink: I can upload too :-)
[11:43] <hub> raphink: just tell me :-)
[11:43] <hub> raphink: but yes, I'll fix it
[11:44] <raphink> sure
[11:44] <raphink> hub: j'ai upload etl
[11:44] <hub> later tonight
[11:44] <hub> raphink: vu
[11:44] <sistpoty> raphink: the library name is fine, it just doesn't match the soname ;)
[11:44] <raphink> mhm
[11:44] <sistpoty> raphink: or what's your concern especially?
[11:45] <hub> raphink: rejected
[11:45] <hub> etl is already in the archive
[11:46] <raphink> etl?
[11:46] <ajmitch> morning all
[11:46] <raphink> ben j'ai rien reu moi
[11:46] <hub> libetl-dev
[11:46] <sistpoty> hi ajmitch
[11:46] <hub> etl-dev it is named
[11:46] <hub> synced from debian
[11:47] <hub> *sigh*
[11:49] <sistpoty> raphink: congrats for root on tiber
[11:50] <raphink> sistpoty: hmm I'm not root... I'm REVU admin only...
[11:50] <siretart> raphink: please read /etc/motd
[11:50] <siretart> :)
[11:50] <sistpoty> raphink: that's unrestricted root access ;)
[11:51] <LaserJock> that reminds me, I was glad to see revu-tools float by on dapper-changes, twice ;-)
[11:51] <sistpoty> hm... but I didn't see an UVF-exc. request :P
[11:51] <siretart> sistpoty: pssst. that s3cr1t ;)
[11:51] <sistpoty> h3h3
[11:51] <raphink> sistpoty: ooh nice :)
[11:52] <siretart> raphink: -> query
[11:53] <hub> raphink: that etl-dev package is a violation of the debian policy IMHO
[11:53] <hub> raphink: I'll file a bug in BTS
[11:53] <raphink> hub: why?
[11:55] <hub> raphink: it is library and is not named libetl-dev but etl-dev
[11:55] <hub> raphink: that is why the upload got rejected and we didn't notice
[11:55] <hub> binary package is improperly named
[11:56] <raphink> oh yes
[11:56] <dholbach> good night revu-ers :)
[11:57] <dholbach> and everybody else of coues
[11:57] <LaserJock> cya dholbach
[11:57] <dholbach> course
[11:57] <hub> 'night dholbach
[11:57] <dholbach> night guys
[11:57] <hub> and thank you for the fish
[11:57] <hub> :-)
[11:57] <dholbach> haha :)
[12:01] <tseng> dholbach: hugs
[12:01] <dholbach> *wave*