[12:25] <lionel> man-di: still arround ?
[12:25] <man-di> lionel: yes, but I found out
[12:26] <lionel> ok, sorry, I was afk 
[12:26] <man-di> lionel: when 1.2.23-1 has entered testing I will do an upload to unstable which incorporates all your changes
[12:26] <man-di> lionel: np at all
[12:27] <lionel> man-di: you rock :)
[12:28] <man-di> lionel: perhaps we should think about security updates for feisty and other dists
[12:29] <man-di> lionel: aka CVE-2007-1860
[12:29] <ubotu> mod_jk in Apache Tomcat JK Web Server Connector 1.2.x before 1.2.23 decodes request URLs within the Apache HTTP Server before passing the URL to Tomcat, which allows remote attackers to access protected pages via a crafted prefix JkMount, possibly involving double-encoded .. (dot dot) sequences and directly traversal, a related issue to CVE-2007-0450. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-1860)
[12:29] <man-di> lionel: that is a one-line fix
[12:30] <lionel> ah great, I did not look at the diff (a bit buzzy at work those days)
[12:36] <Emanon> I'm looking for alpha-testers for a package I'm writing (supposed to work a little like Apple's TimeMachine): http://ubuntuforums.org/showthread.php?t=469049
[12:39] <Emanon> Is there a pool of testers for Ubuntu somewhere online? Or is there another way of doing it?
[12:43] <lionel> Emanon: the best place for finding testers is probabily the forum
[12:46] <Emanon> lionel: You suggest just trying to generate some community interest?
[12:47] <lionel> yes
[12:47] <coNP> Emanon: I think people hanging around in #ubuntu+1 might want to alpha/beta test software :) not that I want to encourage you to off-topic some channel :)
[12:49] <yosch> hi guys
[12:49] <Emanon> Thanks guys. But I think it might be a good idea if there was a pool of a few dozen testers to be available for people trying to introduce new packages to Ubuntu - perhaps people that want to help with development but not interested in programming themselves...
[12:49] <Emanon> hi
[12:49] <yosch> trying to do my first revu upload and I get a connection refused
[12:49] <coNP> Emanon: based on the pacakge description people in #ubuntu-server might also be interested
[12:50] <lionel> Emanon: it's difficult to have a pool of people who are interested in testing all king of software
[12:50] <lionel> kind
[12:50] <Emanon> coNP: Sound like a good idea - thanks
[12:50] <persia> yosch: Do you only have a problem with dput, or can you also not reach http://revu.tauware.de?
[12:51] <yosch> I'm in ubuntu-universe-contributors, on the wiki page it says loging = anomymous for dput config
[12:51] <yosch> persia: I can reach the website with a browser
[12:52] <Emanon> lionel: What if there was a sub-forum under programming where developers could post test requests. That way, those with some willingness might be encouraged to pick and choose what they want to test.
[12:53] <persia> yosch: Great.  The machine is up, and you can route to it :)  Now, if you ftp to revu.tauware.de directly, can you log in with username "ftp" and a password matching the primary email address on the GPG key you have registered with launchpad?
[12:53] <lionel> Emanon: that was my idea
[12:53] <yosch> persia: I get this dput error: urllib2.URLError: <urlopen error (111, 'Connection refused')
[12:53] <Emanon> lionel: Didn't mean to steal it from you ;)
[12:53] <yosch> persia: OK, I'll try that, thanks
[12:56] <yosch> persia: yeah I'm in and I can see the incoming directory
[12:56] <yosch> persia: should I put my package in there directly then?
[12:58] <yosch> I'm packaging a nice open font with sources: http://www.levien.com/type/myfonts/inconsolata.html  (I have a Debian ITP on it too, just waiting for a sponsor there)
[12:59] <persia> yosch: Don't put it there directly: if there are timing issues with your upload, it could break, and require REVU admin intervention to fix.  A manual ftp was just to make sure that your connection worked.  I'd try dput again, making sure to use `dput revu ...`, as I don't see why you should get that error.
[12:59] <yosch> which makes me ask the following question: is it OK to keep unstable in the changelog? or does it need changing?
[12:59] <yosch> persia: OK
[01:00] <persia> yosch: Ah.  The latest changelog entry must target the current Ubuntu development environment, and the version should be an Ubuntu version.  Your statement of "keep unstable" makes me wonder: is this a new package, or an adjustment to an existing package?
[01:00] <yosch> persia: let's say this package will also be backported to dapper/edgy/feisty?
[01:00] <jrib> hi, anyone interested in reviewing a python module?  http://revu.tauware.de/details.py?upid=5444
[01:01] <persia> yosch: Backports don't happen through REVU.  If it's in the archives, follow the backport request process (see the wiki) to request a backport.
[01:02] <yosch> persia: it's a new package the Debian ITP: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396906
[01:02] <ubotu> Debian bug 396906 in wnpp "ITP: inconsolata -- Monospace font designed for code listings" [Wishlist,Open]  
[01:03] <jrib> Also, debuild seems to automatically create debian/pycompat even though the docs for pysupport say it isn't needed
[01:03] <persia> yosch: OK.  Just wanted to make sure REVU was the right place.  If it's likely to get into Debian in the next couple weeks, it might be easier to wait for a sync.
[01:04] <yosch> persia: OK, so in my changelog: instead of  (001.006-2) unstable   I'd have  (001.006-3ubuntu) gutsy ?
[01:04] <yosch> yes I'd rather not have too much of a delta
[01:04] <persia> yosch: "-3ubuntu1", but otherwise yes.  If you don't want delta, wait for it to get into Debian, and file a sync request.
[01:05] <yosch> I'm part both of the Debian Alioth and the LP fonts team, and I need to know the best way to handle this
[01:05] <persia> yosch: Sorry - that's "-2ubuntu1".
[01:05] <yosch> persia: so keep the current 2 for Debian release and add a sub release number after ubuntu
[01:06] <persia> yosch: I recommend syncs, because then the package only has to be maintained in one place.  It's only worthwhile generating an Ubuntu version if there are differences between the Debian and Ubuntu packages.
[01:06] <persia> yosch: Right.  That way, if -3 is published in Debian, and there is no important Ubuntu delta, a sync can be requested.
[01:07] <yosch> persia: Ok syncs then.
[01:07] <yosch> hat's the process for asking a sync again?
[01:07] <yosch> s/hat's/what's/
[01:09] <yosch> and what's the policy on importing changelog entries into upstream Debian: say an ubuntu devs modifies a synced package, produces a patch, increments the changelog, what do you recommend happens with these added changelog entries in upstream Debian?
[01:10] <persia> yosch: If it gets published to Debian before 21st June, the sync should be automatic.  If not, it's https://wiki.ubuntu.com/SyncRequestProcess.  A nice example sync request bug is https://bugs.launchpad.net/ubuntu/+source/thuban/+bug/114137
[01:10] <ubotu> Launchpad bug 114137 in thuban "Please sync thuban 1.2.0-1 (universe) from Debian unstable (main)" [Wishlist,Fix released]  
[01:11] <yosch> persia: OK, thanks a lot. You've been very helpful :)
[01:12] <persia> yosch: I've seen several ways of applying Ubuntu changes to Debian, but I recommend something like http://packages.debian.org/changelogs/pool/main/s/slashem/current/changelog with "Thanks to <Ubuntu person>".
[01:16] <yosch> persia: OK will do that
[01:17] <persia> yosch: Of course, only use "sync" when taking all the changes.  "merge" is better when only taking some changes.
[01:18] <yosch> persia: is the merge process described somewhere?
[01:20] <persia> yosch: I've never seen any docs for the process to merge Ubuntu changes into Debian.  Generally, Debian maintainers prefer that Ubuntu packagers add patches to the BTS when making changes.  For merging Debian changes into Ubuntu, see https://wiki.ubuntu.com/MOTU/Packages/Merging
[01:20] <persia> yosch: If you think documentation for merging Ubuntu changes into Debian would be useful, I'd recommend getting in touch with the utnubu team, and maybe getting something up in the alioth wiki.
[01:27] <minghua> utnubu project has a mailing list, BTW
[02:24] <persia> bug 118964 seems to have passed a couple ubuntu-archive runs without processing.  Would someone mind taking a look, and letting me know if I need more information?
[02:24] <ubotu> Launchpad bug 118964 in csound "Please drop csound & cecilia from ia64 and amd64" [Wishlist,Unconfirmed]  https://launchpad.net/bugs/118964
[02:32] <chillywilly> there's no resitricted modules for the Xen kernel?
[03:08] <chillywilly> if I have a router/firewa/gateway box running Dapper is it ok to go straight to Fesity ;P
[03:08] <chillywilly> firewall
[03:08] <chillywilly> or should I go to edgy first?
[03:08] <Nafallo> chillywilly: edgy first
[03:08] <chillywilly> I'd like to play with the Xen support
[03:08] <chillywilly> ok
[03:19] <octoberdan> Nafallo: Why go to edgy first?
[03:20] <joejaxx> reduces the chance of breakage? :)
[03:21] <Nafallo> octoberdan: since dapper -> dapper+2 isn't supported.
[03:50] <chillywilly> I am sure lots of stuff will break...that box also runs a mail server
[04:24] <joejaxx> chillywilly: are you sure you want to risk the chance of it breaking with it running so many vital services?
[04:24] <joejaxx> :P
[04:31] <chillywilly> joejaxx: it's my home gateway/firewall/router box
[04:33] <chillywilly> nice, a c++ exception thrown
[04:33] <chillywilly> courier-authdaemon
[04:34] <chillywilly> core dumped...
[04:34] <chillywilly> bah
[04:37] <chillywilly> it's not my fault
[04:43] <chillywilly> I know I dealt with this before
[09:03] <statik> hi! I just created my first package, and joined ubuntu-universe-contributors. I've read that the next step is to ask REVU admins to re-synce the REVU uploaders keyring so that I can upload to revu. Anyone around that do this for me?
[09:06] <crimsun> statik: running.
[09:06] <statik> thanks
[09:10] <Hobbsee> crimsun: it's kinda broken - or was yesterday
[09:10] <crimsun> yeah, he's going to check with newz2000 on Monday
[09:10] <statik> silly questions is there a tool or script to help format changelog entries?
[09:10] <ranf> hi
[09:11] <jmg> debchange
[09:11] <statik> jmg: thanks
[09:36] <man-di> good morning
[09:36] <man-di> when a sync is ACKed, is it done automatically?
[09:38] <persia> man-di: No.  An archive admin needs to process it manually.  They usually process the bugs once or twice a week.
[09:39] <man-di> persia: Thx
[10:27] <tritium> crimsun: the email account on my GPG key is no longer valid.  What's the best thing to do to update it?
[10:29] <crimsun> tritium: I would use gpg --edit-key D838A341
[10:29] <tritium> crimsun: and add a new account?  Revoke the old one?
[10:31] <crimsun> just use the `adduid' option, then use the `primary' option to toggle the newly created one as the primary one, then use the `deluid' option to remove the old one, then `save' and `quit'.
[10:31] <crimsun> then upload the amended key directly to keyserver.ubuntu.com
[10:32] <tritium> Hmm, okay.  Now, I just have to pick the new primary one.  I've got a yahoo and a gmail account.  All my other addresses are forwarding addresses only.
[10:32] <tritium> Thanks you, crimsun.
[10:32] <crimsun> well, yes revuid is useful in this case
[10:33] <crimsun> I don't use revuid because my accts don't expire; I don't want them disappearing under me
[10:34] <crimsun> if you mean that your email address no longer exists, then it's a better idea to use revuid
[10:34] <tritium> I guess it doesn't make sense to add one of my forwarding-only addresses, right?
[10:34] <crimsun> sure it does
[10:34] <tritium> Yes, my @purdue.edu no longer exists
[10:34] <persia> tritium: If you have a forwarding address that you are sure will always exist, it's probably the best choice for the primary key.
[10:34] <persia> s/key/uid/
[10:34] <tritium> No kidding?  I thought I couldn't sign anything with a forwarding-only address...
[10:35] <Hobbsee> *shit*
[10:35] <tritium> persia: if that's the case, I feel much better!
[10:35] <tritium> Hi Hobbsee
[10:35] <Hobbsee> hi tritium 
[10:36] <Hobbsee> bugger.
[10:36] <persia> tritium: Your key is about identity, not email.  On the other hand, if you can't send masquerading as your forwarding address, you should have your sending address as an alternate uid, or people may not believe you are really you, and instead thing your key has been compromised.
[10:36] <tritium> persia: thank you.  That clears up some of the confusion I had.
[10:38] <crimsun> it might be of interest to note that many MOTU use forwarding emails in debian/changelog entries
[10:38] <crimsun> (and of course, there're @debian.org)
[10:38] <Hobbsee> presumably there's no way to remove revoked UIDs off the key?
[10:38] <tritium> I believe gmail may allow me to send masquerading
[10:38] <Hobbsee> as in, to not show them?
[10:38] <tritium> (as my forwarding address)
[10:38] <crimsun> Hobbsee: it's problematic; you need to use revuid and ensure the propagation of the new key
[10:39] <persia> Hobbsee: Once you've uploaded a key to the keyservers, it's almost impossible to delete anything, and even if it were possible, the keyserver maintainers would try to stop you.
[10:39] <Hobbsee> crimsun: i've already used revuid, it's showin gas revoked.
[10:39] <crimsun> yes, that's the extent of it
[10:39] <Hobbsee> ah right, so you cant actually delete, and not show it on there at all
[10:40] <Hobbsee> okay then
[10:41] <persia> Hobbsee: That's by design.  The idea is that if you once used hobbsee@myfavoritewebmail.org, and later stopped, you would revoke the uid.  When someone else starts using that email address, everyone knows it's not you.
[10:41] <tritium> So, I'll use revuid, then.
[10:41] <Hobbsee> persia: fair enough
[10:42] <crimsun> speaking of which, it's about time for that yearly update
[10:43] <crimsun> expires: 2007-06-26.  Yep, right around the corner.
[10:44] <crimsun> I'm a bit paranoid about it; when I croak, I want it to invalidate automatically.
[10:44] <crimsun> Takes care of those pesky "premature death" situations.
[10:45] <tritium> oh, crimsun...
[10:45] <crimsun> hmm?
[10:45] <Hobbsee> i suspect that people will *notice* if i get killed.
[10:46] <crimsun> yes, but will your next of kin revoke your key(s) and upload in a timely fashion? ;)
[10:46] <Hobbsee> heh
[10:46] <Hobbsee> point
[10:47] <Hobbsee> i'm not sure hwo the ubuntu community would then find out about my death, unless one of them killed me, although i'd expect friends of mine from the ubuntu community to actually say something.  *shrugs*
[10:48] <tritium> I hope my wife would figure out how to send you all my regards, should I pass away.
[10:48] <tritium> But, if that doesn't happen, know now that I'd have wanted her to.
[10:48] <crimsun> I plan to be reinserted into the matrix.  Err, wrong universe.
[10:49] <Hobbsee> i think it would also be fairly obvious if one of the ubuntu-type people called my mobile, and got told that way.
[10:52] <StevenK> crimsun: So you attach the Revokation to your will and instruct your executur to make sure that it gets uploaded to a keyserver within 24 hours of hearing about it.
[10:52] <crimsun> oh, right.
[10:52] <AnAnt> Hello,
[10:52] <AnAnt> I am making a package for some software
[10:52] <StevenK> crimsun: I mean, that sounds sensible to me.
[10:53] <AnAnt> problem is that the orig. tarball contains binary file, how to deal with that situation ?
[10:53] <StevenK> Binary how?
[10:54] <StevenK> Binary as in blob of stuff, or binary as in pre-compiled binary for a specific platform?
[10:55] <AnAnt> StevenK: pre compiled
[10:55] <AnAnt> StevenK: for i386
[10:57] <RainCT> Hi
[10:57] <persia> AnAnt: Does the program work without that binary, or do you have source to regenerate the binary?
[10:58] <AnAnt> persia: I have the source to regenerate binary  in the same tarball
[10:58] <persia> AnAnt: Just delete the binary in the clean: rule.  Leave it in the orig tarball.
[10:58] <AnAnt> persia: and during build, the binary can be removed using make clean
[10:58] <AnAnt> ic, ok
[11:05] <jekil> hello
[11:08] <tritium> If I've designated a new uid as primary, it has a "*" next to it, correct?
[11:08] <Hobbsee> that just means "you've selected me"
[11:09] <Hobbsee> iirc
[11:09] <Hobbsee> ie, dont do a deluid or a revuid straight after - else it will revoke whatever you've said
[11:09] <tritium> okay, thanks, Hobbsee
[11:09] <AnAnt> persia: btw, the clean: rule you meant was in Makefile or debian/rules file ?
[11:11] <persia> AnAnt: If you're going to tell upstream that the files should be deleted, I'd recommend patching the Makefile, and sending the patch upstream.  If you're having trouble with upstream communication, or upstream doesn't accept patches, use debian/rules.
[11:16] <AnAnt> ok
[11:18] <persia> AnAnt: More verbosely: not deleting the binaries in the clean rule is a bug in the upstream build system (everything generated by the build system should be deleted in clean).  Patches are best for upstream bugs.  debian/rules allows one to work around broken upstream, but more people look at debian/rules, so fixing upstream mistakes should only be done there when upstream won't.
[11:19] <AnAnt> persia: ok, there is a clean rule in upsteam's Makefile that removes the binaries, so I don't need to do anything in debian/rules, right ?
[11:21] <persia> AnAnt: You need to call `make clean`, but that's recommended by default anyway, so you probably don't have to change it.
[11:21] <AnAnt> ok
[11:26] <tritium> Hobbsee: did you use seahorse when you deleted your UID?  I can't find a revuid option in seahorse.
[11:26] <Hobbsee> no
[11:26] <Hobbsee> i dont use gnome
[11:26] <tritium> oh, that's right...
[11:28] <tritium> okay, got it revoked via cli.  So, I don't want to delete it, eh?
[11:28] <Hobbsee> deleting doesnt seem to work
[11:28] <persia> tritium: If you delete it, the keyservers will restore it.
[11:29] <tritium> okay, thanks, persia
[11:30] <persia> tritium: For future note, if you ever use keys that are not public, deleting is useful.  It's just the public web of trust that prevents it.
[11:31] <tritium> gotcha, thanks
[11:42] <Hobbsee> persia: uploaded x3
[11:42] <ubotu> Launchpad bug 119016 in vlc "vlc-nox depends on missing libpostproc0d" [Medium,Needs info]  https://launchpad.net/bugs/119016
[11:43] <persia> Hobbsee: Enchained will be very happy.
[11:43] <Hobbsee> yep :)
[11:44] <persia> Hobbsee: Did you also archive them and send the REVU mail?
[11:44] <Hobbsee> yep
[11:44] <Hobbsee> well, almost
[11:44] <persia> Hobbsee: Excellent.  I won't worry about it then.  Thanks.
[11:45] <tritium> persia: can you please check my key on https://launchpad.net/~mrimbert, and see if it looks like I did it right?
[11:45] <persia> tritium: I'm about to run out of time, but I'll glance at it quickly.
[11:45] <tritium> thanks
[11:46] <persia> alumni looks to be the default, but I'm out of time.  Sorry.
[11:46] <tritium> no problem.  thanks
[11:46] <Hobbsee> persia: right.  done done ;)
[11:53] <jekil> someone can review please? http://revu.tauware.de/details.py?upid=5450
[11:54] <persia> tritium: Sorry about that.  Yes, alumni is default, and purdue is revoked.  You can see a nice report from http://keyserver.ubuntu.com:11371/pks/lookup?op=vindex&search=0x8B9A47A2D838A341
[11:54] <persia> Hobbsee: Thanks.
[11:54] <persia> jekil: sure
[11:55] <tritium> Thanks, persia :)
[12:02] <jekil> thank you persia 
[12:04] <persia> jekil: I still like it, but you might want to add a comment in debian/copyright detailing the license of the Debian packaging.
[12:04] <jekil> persia: ok, thanks
[12:05] <persia> jekil: If you plan to do that, I'll wait to advocate.  If you are assigning copyright for the packaging to upstream, and want to use their license, I'll hit this upload.
[12:06] <jekil> persia: yes i do it
[12:06] <persia> jekil: OK.  Let me know when you have a new upload :)
[12:06] <jekil> persia: thanks :)
[12:08] <jamyskis> hi everyone
[12:08] <jamyskis> hi again persia
[12:09] <jamyskis> does anyone know the version of liballegro that will be included in gutsy?
[12:09] <jamyskis> the existing one has the version number appended to the name which is a problem if 4.3 will be included
[12:16] <jamyskis> i've gotten the error configure-generated-file-in-source config.log from lintian but i can't find config.cache or config.status anywhere
[12:16] <man-di> jamyskis: rm config.log
[12:17] <jamyskis> man-di: doesn't exist
[12:18] <persia> jamyskis: Based on previous upstream history, probably 4.3.1, although past performance is not an indication of future releases.
[12:18] <jekil> persia: what is the format of the licenso of the debian packaging? Packaging license: blablabla? I can't found an example
[12:19] <jamyskis> persia: so what should i put in for build-depends because that will affect the liballegro4.2 or liballegro4.3 dependency
[12:19] <jamyskis> liballegro4.3 doesn't work anyway but if i put liballegro4.2 then gutsy will have problems
[12:19] <jamyskis> i can't count on there being a transitional package
[12:20] <man-di> jamyskis: it does somewhere
[12:20] <man-di> jamyskis: otherwise lintian wouldnt have complained
[12:20] <persia> jamyskis: For now, use liballegro4.2-dev.  When 4.3 is available, process as a library transition.  Based on the package naming, it looks like 4.2 and 4.3 will both be available in gutsy (unless we're all very busy trying to fix it).
[12:21] <jamyskis> persia: ok, got it
[12:22] <jamyskis> man-di: i've done a search twice on anything with config.log config.cache or config.status in the entire upstream source directory (including debian files) 
[12:22] <jamyskis> there's nothing there
[12:22] <man-di> jamyskis: perhaps its removed meanwhile
[12:22] <jamyskis> man-di
[12:23] <jamyskis> man-di: maybe
[12:23] <man-di> jamyskis: but its definitely in the sources checked by lintian
[12:23] <jamyskis> man-di: i've included rm -f config.log in the clean rule anyway
[12:23] <man-di> jamyskis: e.g. in the *.diff.gz
[12:23] <man-di> jamyskis: normally you should not need that
[12:24] <man-di> jamyskis: it only stays when you stop ./configure while its working
[12:24] <man-di> or when it fails in between
[12:25] <jamyskis> found em - they're in the upstream orig.tar.gz
[12:26] <man-di> jamyskis: oh, thats really evil
[12:26] <man-di> jamyskis: you should tell upstream to remove it for next release
[12:26] <jamyskis> note to self: remove config.log and config.status for next release
[12:26] <man-di> jamyskis: you are upstream?
[12:26] <jamyskis> man-di: yp
[12:27] <man-di> jamyskis: you are using autotools?
[12:27] <jamyskis> man-di: yep
[12:27] <man-di> use "make dist" to create a release tarball
[12:27] <man-di> this should create a clean tarball
[12:28] <AnAnt> are there issues with globbing in Makefiles ?
[12:29] <persia> AnAnt: Depends on ${SHELL}.  It7s safest to avoid bashisms.
[12:30] <jamyskis> ok i give up
[12:30] <AnAnt> persia: is *[^~]  bashism ?
[12:30] <jamyskis> i think i'll just stick to distributing my stuff in .tar.gz form
[12:31] <persia> AnAnt: I'm never sure - run `dash` to check :)
[12:31] <persia> jamyskis: Why?
[12:31] <AnAnt> ok
[12:31] <jamyskis> persia: i managed to fix the problem i had yesterday with it installing in /usr/doc from source
[12:32] <jamyskis> persia: it works fine installing in /usr/share/doc with ./configure make make install
[12:32] <persia> jamyskis: Great!
[12:32] <man-di> jamyskis: I dont like to say this but mostly such problem come when upstream has some issues
[12:32] <jamyskis> persia: but pbuilder insists on installing it in /usr/doc
[12:33] <man-di> jamyskis: send me your upstream tarball and I can have a look at it: konqueror@gmx.de
[12:33] <persia> jamyskis: There's probably still something funny with autotools then.  The advantage of having (or being) a maintainer of a debian-style package is that you'll get lots of feedback on how to make a clean tar.gz release.
[12:33] <persia> Of course, it's easier when someone else is the maintainer :)
[12:37] <jamyskis> persia: thanks...i'll just take another look through and then i'll send it
[12:38] <persia> jamyskis: Thank man-di - I'm just blathering :)
[12:38] <TheDumbo> !seen seveas
[12:38] <ubotu> Sorry, I don't know anything about seen seveas - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[12:38] <jamyskis> persia man-di: sorry my bad :)
[12:43] <jamyskis> man-di: bear with me i'm going to extract the source docs and data and build the anjuta project from scratch
[12:47] <man-di> jamyskis: take your time
[12:47] <man-di> jamyskis: I have plenty of other stuff to do ;-)
[12:49] <persia> Do comments in REVU notify the uploader in any way?
[12:49] <Hobbsee> no
[12:50] <persia> Hobbsee: OK.  Thanks.  You don't happen to know where to file wishlist requests for REVU2, do you?
[12:50] <StevenK> In siretart's head?
[12:50] <Hobbsee> persia: code is in bzr, i believe.  or siretart can give you access if you're interested in working on it
[12:51] <StevenK> I wonder if REVU2 would be better done in Rails.
[12:51] <persia> Hobbsee: Thanks, but I'm not that interested :)
[12:51] <StevenK> Given mod-python is hell to work with.
[12:51] <persia> StevenK: Thanks.  I'll file some bugs there then.
[12:52] <StevenK> persia: Hrm?
[12:52] <persia> (21:50:46) StevenK: In siretart's head?
[12:52] <StevenK> Ahhhh
[12:55] <jamyskis> BLOODY ANJUTA!
[12:55] <jamyskis> i've just figured out what it was doing the whole time
[12:56] <tsmithe> StevenK, python is great for web!!
[12:56] <jamyskis> i had Copying, README, AUTHORS etc. included in the docs section of the project when you're actually supposed to use the ones included in the upstream rootr
[12:56] <jamyskis> *root
[12:56] <tsmithe> i use lighttpd with scgi/fastcgi, and a wsgi framework; and it works swell!
[12:56] <persia> tsmithe: Don't bother.  StevenK actually understands apache :)
[12:57] <tsmithe> oh darn
[12:58] <tsmithe> but i'm saying you don't need to use mod-python... or apache!
[12:58] <tsmithe> i guess you already knew that though
[01:07] <DarkSun88> Hi
[01:07] <Hobbsee> hiya
[01:07] <DarkSun88> Hi Hobbsee 
[01:24] <jamyskis> persia, man-di: i got it - Anjuta was rewriting the Makefile.am which was installing the docs in /usr/doc/pkgname
[01:25] <jamyskis> i just locked the overwrite of the top level Makefile.am and it installed from source without a hitch
[01:25] <jamyskis> in all the right places
[01:28] <Kmos> StevenK: that will have problems with dash
[01:28] <Kmos> :)
[01:29] <jamyskis> i made that mistake often enough
[01:33] <jamyskis> how long do the extended description lines in control have to be again? 60 or 80?
[01:34] <DarkSun88> Long description 60 lines
[01:34] <jamyskis> DarkSun88: thanks
[01:36] <man-di> DarkSun88: I really wonder which packages have long descriptions with 60 or more lines
[01:37] <man-di> Where can I find an uptodate multidistrotools version?
[01:37] <DarkSun88> I don't know. Sorry
[01:38] <persia> man-di: Does `bzrbranchhttp://ox.blop.info/bazaar/multidistrotools/` not work?
[01:38] <man-di> persia: last time I looked it didnt
[01:39] <man-di> at least it was not uptodate
[01:39] <Fujitsu> man-di: http://tiber.tauware.de/~laserjock/multidistrotools/ is pretty much the main branch at the moment.
[01:39] <StevenK>   * Use bash to call extract_syms.sh, it's full of bashisms, and worse, was
[01:39] <StevenK>     pulled from libtool code.
[01:39] <Fujitsu> Mine might have a revision or two that that doesn't, but most are merged into LaserJock's.
[01:39] <man-di> Fujitsu: thanks
[01:40] <Fujitsu> StevenK: Which package?
[01:40] <StevenK> Fujitsu: libwibble
[01:41] <StevenK> It's sitting in accepted
[01:42] <xerosis> hi, i want to do my first package, is it better to do a normal package or a merge at the minute?
[01:42] <persia> xerosis: What do you want to learn from doing a package?
[01:43] <xerosis> persia: how to be a packager :p
[01:44] <man-di> Fujitsu: how am I supposed to download that? wget doesnt want to because of robots.txt
[01:44] <Fujitsu> man-di: bzr branch
[01:44] <man-di> Fujitsu: thx
[01:45] <persia> xerosis: I'd recommend starting with https://bugs.launchpad.net/ubuntu/+bugs?field.tag=packaging: You'll learn a lot from fixing these issues, and get to see a large number of different ways that packages are packaged, so you can develop a preference for certain styles.
[01:46] <persia> xerosis: Specifically, a new package is usually hard to start with, and a merge doesn't really teach much packaging, as most of the work is already done.
[01:46] <Hobbsee> persia: something KDElike is the idea...i just cant really think of anything little that there's to do
[01:47] <bmm> Any MOTU is welcome to comment or advocate http://revu.tauware.de/details.py?upid=5413 .ccbuild has one advocation at the moment.
[01:47] <jamyskis> persia: the manpage should be called manpage.1 in the debian directory and there should also be a file called manpages which has debian/manpage.1 listed right?
[01:47] <persia> Hobbsee: Umm.  That's harder, as y'all tend to be good about fixing KDE packaging issues.
[01:47] <Hobbsee> heh, exactly
[01:48] <persia> jamyskis: Depends.  In general, yes.  Given your situation, I'd recommend that upstream distribute the manpage and install it directly.
[01:49] <persia> jamyskis: $(PREFIX)/man/$(Section)/$program.$section
[01:51] <persia> xerosis: I still believe the best way to learn packaging is to fix other peoples packages, but if you really want to work on a KDE package, you might do best to search for the "needs-packaging" tag instead of the "packaging" tag.  Note that while most of the "packaging" bugs are not KDE packages, much of the software is usable in Kubuntu.
[01:52] <persia> bmm: That's an excellent request for review.  Thanks for both stating the status of the package and listing the name of the package.
[01:52] <xerosis> persia: i guess doing non-kde packages isn't too bad really
[01:52] <xerosis> persia: will have a look to see what i can do
[01:53] <bmm> persia: thanks
[01:53] <persia> xerosis: Usually I'd also recommend searching for KDE bugs with easy fixes, and submitting new revisions, but there was recently a massive KDE bug triage effort, and I don't know how many easy ones are left :(
[01:54] <xerosis> persia: damn efficient people, taking work away from noobs
[01:56] <man-di> Fujitsu: this version runs on current gutsy?
[01:56] <Hobbsee> persia: there's still enough, i'[m sure
[01:56] <man-di> Fujitsu: I ask because I get this: http://paste.debian.net/30101
[01:57] <Fujitsu> man-di: I haven't tried it in a couple of weeks.
[01:57] <persia> Hobbsee: Is there a tinyURL for the KDE bugs, or a team which has all the relevant packages subscribed?  It'd be nice if xerosis had an easy time searching.
[01:57] <man-di> I remember having the same problem with lucas' version somewhen in Feisty release cycle
[01:58] <Hobbsee> persia: xerosis the best i've found is https://launchpad.net/~kubuntu-team/+packagebugs
[01:58] <xerosis> Hobbsee: that's what i've been using
[01:59] <persia> Hobbsee: Thanks.
[02:00] <coNP> What command should I use if I want to update a package and have to include binary files (in fact png images) in the diff as well?
[02:01] <Fujitsu> coNP: You'll have to uuencode them, probably. Why do you need them?
[02:01] <persia> coNP: build-dep on sharutils, uuencode the files into debian/foo.uu, and uudecode during the build; rule (or some dependency thereof).
[02:02] <coNP> this seems a bit complicated :)
[02:02] <shawarma> coNP: It's the only way. Our diffs don't work with binary data.
[02:02] <coNP> actually I wanted to implement a feature but I might send it upstream
[02:02] <coNP> and then no need to diff binary files
[02:02] <jamyskis> persia: i think i finally have a compliant deb package complete with manpage :)
[02:02] <jamyskis> i didn't include the manpage upstream because it was far more complicated
[02:03] <persia> jamyskis: Congratulations!  Upload to REVU, and find out whether you're right :)
[02:11] <xerosis> persia: would https://bugs.launchpad.net/ubuntu/+source/blender/+bug/116540 be okay?
[02:11] <ubotu> Launchpad bug 116540 in blender "blender 2.44 package should use python 2.5" [Low,Confirmed]  
[02:11] <xerosis> persia: oops, just read that it's only at 2.44 in the repos, sorry
[02:14] <RainCT> debian maintainer field is XSBC-Original-Maintainer?
[02:14] <persia> RainCT: Yes.
[02:16] <jamyskis> persia: it's uploaded...does it take a while before it appears on the current uploads list?
[02:17] <persia> jamyskis: I think it happens every 5 minutes, so if you upload at the worst time, it should be no more than 300 seconds.
[02:18] <jamyskis> persia: ok i'll grab myself a cup of tetleys in the meantime ;)
[02:25] <jamyskis> ive just found out i can run lintian on the deb :S
[02:25] <jamyskis> anyone know the new FSF address?
[02:25] <jamyskis> never mind i got it
[02:27] <persia> jamyskis: See the Preparing New Revisions section of https://wiki.ubuntu.com/MOTU/Contributing for recommended flags for lintian and linda (to catch everything).
[02:31] <jamyskis> persia: right, it's definitely clean now (apart from the invalid distribution complaint because i entered gutsy)
[02:32] <persia> jamyskis: So, upload and ask for review :) (see above for a good request)
[02:32] <jamyskis> persia: i'll reupload in a second
[02:34] <jamyskis> persia: the thing is that lintian complains that my manpage has an error
[02:34] <jamyskis> although i've used man with it and it works fine
[02:35] <persia> jamyskis: Does lintian explain the error when you use the recommended flags?
[02:35] <jamyskis> persia: no
[02:35] <jamyskis> persia: only when i run lintian on the binary deb
[02:36] <jamyskis> like the reviewer did last time
[02:36] <persia> jamyskis: Right.  When you use the recommended flags on the binary .deb, it should tell you what the error is in sufficient detail to fix it.  If not, pastebin the fully expanded error, and ask for help here.
[02:39] <RainCT> can someone (persia?) please check the debdiff for bug 119683?
[02:39] <ubotu> Launchpad bug 119683 in qdacco "qdacco includes no .desktop file" [Undecided,Confirmed]  https://launchpad.net/bugs/119683
[02:40] <man-di> Fujitsu: any idea about multidistrotools?
[02:40] <persia> RainCT: No need to mention me :)  If I have time, I'll look anyway, and if I don't it just distracts me and delays any review.
[02:40] <Fujitsu> man-di: No, unfortunately. Seems that python-apt has changed its interface, and I haven't got time to look into fixing it now.
[02:40] <RainCT> ok sorry
[02:40] <man-di> Fujitsu: thanks for looking into it
[02:41] <Fujitsu> I'll probably have a look tomorrow or Tuesday.
[02:42] <persia> RainCT: Looks OK to me.  It will get picked up as soon as someone who isn't just interested in merges and syncs processes the U-U-S queue.  No need to ask here.
[02:43] <persia> RainCT: Don't forget to file the bug in Debian, and link to that bug in Launchpad.
[02:43] <RainCT> yes, doing that now
[02:44] <persia> RainCT: Sorry.  BTS is slow, I guess I looked too soon.
[02:47] <RainCT> eh.. does 'bugreport' send bugs to Debian or Ubuntu?
[02:48] <persia> RainCT: "bugreport"?
[02:48] <geser> default for reportbug is Ubuntu but you can say it to mail the Debian BTS
[02:49] <RainCT> sorry, reuportbu
[02:49] <RainCT> (* reportbug)
[02:49] <RainCT> geser: how can I do that?
[02:50] <geser> put "bts debian" in your ~/.reportbugrc
[02:50] <geser> cp /etc/reportbug.conf ~/.reportbugrc if you don't have already one
[02:52] <RainCT> ok thanks
[02:54] <tobiasschulz> is a revu admin inside this channel (im german, so sorry for my english)
[02:54] <tobiasschulz> ?
[02:55] <persia> tobiasschulz: Usually, but not always on the weekend.  What are you trying to accomplish?
[02:56] <tobiasschulz> i would like to upload a package using revu, and on https://wiki.ubuntu.com/MOTU/Packages/REVU?action=show&redirect=REVU  it says "Next, ask the REVU admins in #ubuntu-motu or at  keyring@tiber.tauware.de to re-sync the REVU uploaders keyring, which grants you upload rights to REVU."
[02:57] <tobiasschulz> but if there are no admins, i will try it tomorrow again
[02:57] <persia> tobiasschulz: OK.  If an admin is around, they'll probably start a sync soon (most read backscroll, even if they are away a bit).  If not, I think the keys are sync'd automatically each night (CET), so it should be fine by tomorrow, even if nobody gets to it now (although that's not ideal for you).
[02:58] <tobiasschulz> ok thank you
[03:00] <jamyskis> i think im going to scream
[03:01] <jamyskis> i now have to start from scratch because the arch-indep data is far too big
[03:01] <jamyskis> and i need to create two seperate packages for it
[03:01] <persia> jamyskis: Not from scratch.  You only need two binary packages.  This isn't too hard.
[03:02] <jamyskis> persia: two folders with the same upstream but with different rules files? 
[03:02] <persia> First, add a new Binary: section at the end of debian/control for naughts-and-crosses-common (or whatever your package name is + "-common".
[03:02] <persia> jamyskis: Nope.  One upstream, one rules file, etc.  Just two binary packages.
[03:02] <jamyskis> persia: ok...i'm reading
[03:03] <persia> Set the architecture of the -common package to "all"
[03:04] <persia> Make the regular package depend on the -common package.
[03:04] <persia> Rename debian/manpages, debian/install, etc. to debian/packagename.manpages, debian/packagename.install, etc.  (only for the debhelper helper files).
[03:04] <jussi01> good evening everyone :D
[03:04] <persia> Hi jussi01
[03:05] <jussi01> hello persia
[03:05] <persia> Add debian/packagename-common.install, and list all the arch-independent data there.
[03:06] <persia> This should give you two packages, with the right contents.  There's likely a bit more tweaking required, but linda & lintian should help (and I don't remember off the top of my head).
[03:06] <jamyskis> persia: i don't have a debian/install file
[03:07] <persia> jamyskis: That's OK.  If you don't have it, you don't need to rename it :)
[03:07] <jamyskis> persia: will it ignore the architecture independent stuff then when it builds naughts-and-crosses?
[03:08] <man-di> Fujitsu: I have got it to work now with replacing "mtd bin2src ..." with some grep-dctrl magic.
[03:08] <man-di> Fujitsu: but the output looks really simplistic to what lucas generated at http://tiber.tauware.de/~lucas/versions/java.html
[03:08] <Fujitsu> man-di: What command are you using to generate it now?
[03:09] <man-di> the srcpkg file?
[03:09] <Fujitsu> What does the output you get look like?
[03:09] <persia> jamyskis: My memory is that it will move everything you install into -common out of the base package.  Let me find you a doc.
[03:09] <man-di> its just a list with source package names
[03:09] <Fujitsu> You need to run it through mdt compare-versions and mdt versions2html or so.
[03:10] <man-di> Fujitsu: http://paste.debian.net/30111
[03:10] <man-di> Fujitsu: thats what I do
[03:10] <man-di> Fujitsu: my current script is http://paste.debian.net/30112
[03:11] <Fujitsu> "mdt compare-versions sid gutsy | mdt filter ../lists/science-all | mdt removals removals.txt A | mdt versions2html -t "Science package" -d -u -a Sid -b Gutsy > science.html" is what I use.
[03:12] <Fujitsu> man-di: What does the generated .html have in it?
[03:14] <man-di> Fujitsu: lucas version e.g. has links to patches.ubuntu.com and to bugs.launchpad.net
[03:14] <Fujitsu> I believe there are some options to versions2html that do that.
[03:14] <Fujitsu> Options: -d, --debian-links               Include Debian-related links in the output -u, --ubuntu-links               Include Ubuntu-related links in the output
[03:15] <persia> jamyskis: http://wiki.debian.org/PkgSplit is the clearest I could find about it.
[03:15] <Fujitsu> Bah, I am being told I must go to bed now.
[03:18] <man-di> Fujitsu: good nite and thx for your help
[03:18] <jamyskis> persia: i think i've sussed it
[03:18] <jamyskis> persia: thanks
[03:21] <jamyskis> i hope i'll be able to get my second game done quicker next time
[03:21] <jamyskis> this has taken the best part of three days
[03:21] <persia> Anyone seeking Membership and want more linkable stuff for their wiki page?
[03:21] <jamyskis> thanks for all the help persia
[03:21] <persia> jamyskis: As you become familiar, it becomes easy.
[03:26] <jamyskis> persia: ok, i have a naughts-and-crosses-common deb file which is 4K and a naughts-and-crosses file which is 324K (the same as the original)
[03:27] <jamyskis> persia: somethings gone astray
[03:27] <persia> man-di: sync'd from experimental
[03:27] <man-di> persia: aah, right, that makes sense
[03:28] <persia> man-di: Easiest way to check is to look at the Ubuntu changelog, either on LP, or on an Ubuntu system (or chroot) with `aptitude changelog foo`.
[03:29] <man-di> persia: yes, I know. I just looked at the output of multidistrotools without more checking and wondered
[03:31] <persia> man-di: `aptitude changelog libgnuinet-java` is fewer keystrokes than "/me wonders about libgnuinet-java which is 1.1.1-1 in unstable and 1.1.1-2 in gutsy" :)
[03:31] <polopolo> hello, can someone help my me with setting my gpg in launchpad?
[03:31] <persia> polopolo: Where are you stuck?
[03:32] <polopolo> wait, psb
[03:34] <polopolo> is Passphrase password???
[03:35] <persia> polopolo: Depends on the tools you used to generate your key.  Passphrase is the secret phrase you entered when generating your key.
[03:35] <RainCT> yes
[03:37] <polopolo> So I can type my password?
[03:38] <polopolo> ?
[03:39] <jamyskis> brb just getting food
[03:40] <polopolo> nobody as the answer?
[03:41] <persia> polopolo: When creating your key, you were asked for a secret phrase.  Do you remember what it was (don't tell me)?
[03:42] <polopolo> nevermind, it already done, wait for the next problem
[03:44] <polopolo> ok, when I getting send my code to lanchpad, I get a problem
[03:44] <polopolo> it says Ie not uploaded already to ubuntu
[03:44] <polopolo> When I do it
[03:45] <persia> polopolo: Did you already sync your key to the keyserver?
[03:46] <polopolo> no, I do it now
[03:46] <polopolo> I do it, but no massage
[03:46] <polopolo> then I go back and enter the same
[03:47] <polopolo> Then it says it not on the server
[03:47] <polopolo> that the problem
[03:48] <persia> polopolo: Can you find your key when you search from http://keyserver.ubuntu.com:11371/?
[03:50] <polopolo> Error handling request: No keys found
[03:50] <polopolo> That the error I get
[03:50] <persia> polopolo: When you uploaded your key to the keyservers, which keyserver did you use?
[03:51] <polopolo> today, keyserver.ubuntu.com
[03:51] <persia> polopolo: Hmmm.  For some reason it's not there (or your search terms don't work).
[03:52] <polopolo> I searched with my fingerprint
[03:52] <persia> polopolo: Try searching with your name.
[03:53] <polopolo> There it
[03:53] <polopolo> but the old one, not the new one
[03:53] <persia> polopolo: Do they have the same email address?  Is the old one valid?
[03:54] <polopolo> the old one as the old email I do not use anymore
[03:55] <persia> polopolo: Do you still have the secret key?  You can change the email address on the key.
[03:55] <polopolo> no, I don, it was on my remove partition
[03:55] <polopolo> BTW, i see now this on the error of lanchpad
[03:56] <polopolo> Keys sometimes take up to an hour to be synchronized between servers.
[03:56] <polopolo> maby wait?
[03:57] <persia> polopolo: Maybe, but usually if you upload to a speciific keyserver, the key should be on that server.  Check again in an hour, and if that doesn't work, paste the ASCII-armour'd version of your public key on the search form to force it.
[03:58] <polopolo> ok, I wait a hour, thank you, I go make further with my package
[04:01] <persia> gnomefreak: Is something still happening with bug 55782?
[04:01] <ubotu> Launchpad bug 55782 in kxdocker "doesnt open in edgy" [Medium,In progress]  https://launchpad.net/bugs/55782
[04:02] <gnomefreak> persia: dont know im not the one working on it but last i checked it didnt work
[04:02] <persia> gnomefreak: I just haven't seen the assingee in a while, and you were the reporter, so I thought you might know.
[04:03] <gnomefreak> persia: i wish i did. edgys should work from what i have heard but feisty didnt (not sure on gutsy i havent installed it yet
[04:05] <persia> gnomefreak: The package hasn't changed since edgy, so it's probably still broken.  I'll assign to noone, and ask for someone to generate a gutsy fix then.  Perhaps after that's done, a SRU can be considered.  Thanks.
[04:06] <gnomefreak> thank you
[04:06] <persia> gnomefreak: If you have some spare time, and want to respin the patch, I'd be happy to get it uploaded fairly soon.
[04:07] <polopolo> ohyeah, https://help.ubuntu.com/6.06/ubuntu/packagingguide/C/basic-scratch.html must be updated, some things are wrong here
[04:11] <gnomefreak> persia: if not ill do it this week. but i would like to see what he did first
[04:12] <persia> gnomefreak: The patches are in the bug :)
[04:12] <gnomefreak> oh nice :)
[04:12] <beuno> can anyone clarify to me the difference between "universe" and "multiverse"?
[04:12] <gnomefreak> mulyiverse holds nonfree packages
[04:12] <persia> gnomefreak: ping me if it doesn't get sponsored in a reasonable amount of time.  3 releases is too many to have an outstanding patch :)
[04:13] <gnomefreak> persia: ok ill try on gutsy tonihgt or tomorrow
[04:13] <persia> gnomefreak: Thanks.
[04:13] <gnomefreak> thank you for looking at it :)
[04:14] <persia> gnomefreak: We're slowly improving.  Soon, UUS reviews should be within a week or so.
[04:14] <gnomefreak> persia: im tempted to agree with the post before yours
[04:14] <gnomefreak> Additionally, kxdocker appears dead. As of April 23, 2007, the project is now XQDE...
[04:15] <beuno> gnomefreak: THANKS
[04:15] <gnomefreak> no sense in adding it to gutsy (keeping it in)
[04:15] <gnomefreak> if someone wants to build XQDE than i say go for it
[04:16] <gnomefreak> grabbing to build feistys
[04:16] <gnomefreak> beuno: yw
[04:17] <persia> gnomefreak: I'm not really familiar with the package.  If you think so, please reject this bug (with the appropriate comment), and open a new bug to remove it from Ubuntu.  It's probably a good idea to get the replacement in first :)
[04:17] <gnomefreak> well im gonna work on feistys build for it and ill file another bug but i cant close this one until feisty is fixed but i will comment on it
[04:19] <persia> gnomefreak: OK.  There's a bit of a procedural issue, that we're only supposed to SRU things that are fixed in gutsy.  If it is to be fixed in feisty, it needs to be fixed in gutsy first, even if the plan is to drop the package after the archive-admins approve the SRU.
[04:20] <gnomefreak> ok thats fine ill spin it in gutsy too than file bug :)
[04:20] <persia> gnomefreak: If you'd like the fix in feisty, don't open the drop bug first :)
[04:22] <gnomefreak> hmmmm
[04:23] <gnomefreak> persia: im leaning towards saying screw it for feisty. is it really worth it since it has been same version for 3 releases
[04:24] <gnomefreak> no upstream fixes
[04:25] <persia> gnomefreak: It's your bug, so it's your call.  If you decide it's not worth it, just retract (reject) the bug with a comment.  If one of the other subscribers really wants it, perhaps they can help get it done.
[04:25] <persia> (and reopen it)
[04:26] <gnomefreak> would this be a backport canidate?
[04:26] <persia> gnomefreak: Which?  The bugfix, or XQDE?
[04:26] <gnomefreak> xqde
[04:26] <persia> gnomefreak: If it builds on edgy or feisty, probably.  If it needs new libraries, probably not.
[04:27] <gnomefreak> ok well lets get one thing at a time done :)
[04:34] <persia> coNP: When requesting sponsorship, it's a good idea to review the sponsors queue guidelines at the top of https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue to make sure that it will be accepted.
[04:34] <StevenHarperUK> Hello : could a MOTU please re-sync the REVU uploaders keyring, so I can have upload rights to REVU?
[04:34] <gnomefreak> persia: should i subscibe anyone to the drop request of kxdocker?
[04:35] <persia> gnomefreak: You've decided not to fix it in feisty then?  From your comment to the bug, I thought you planned to get an SRU out.
[04:35] <coNP> persia: thanks, now should I ask someone to mentor?
[04:35] <gnomefreak> persia: i updated it
[04:36] <persia> coNP: No need.  If you've met all the criteria listed in "Notes for Contributors", subscribing the sponsors is sufficient.
[04:36] <gnomefreak> makes no sense to me that after 12 months no upstream updates. the project doesnt look all that great from thier links
[04:36] <coNP> thanks persia I guess everything is fine
[04:36] <gnomefreak> but that doesnt stop it from getting in
[04:41] <persia> gnomefreak: I'm caught up now.  Sounds good.  To get sponsorship for a drop, it's the same as sponsorship for anything else.  Before asking for sponsorship, I recommend getting in touch with the Debian maintainer.  They may agree with you, and make a package of xqde, and it's a lot easier to get a drop approved by the archive-admins when there's a RoM removal request outstanding in Debian.
[04:43] <persia> gnomefreak: Separtely, drops are easier when the replacement is already packaged and distributed in Ubuntu, as then there's a guarantee that there's no loss of functionality, without waiting for someone to get around to packaging the new software.
[04:48] <polopolo> persia, what do you mean with ascii, how can I do it?
[04:49] <persia> polopolo: gpg --export --armor should generate some pasteable text for you (I think).
[04:50] <polopolo> aha
[04:50] <polopolo> add, thank you very very much
[04:50] <polopolo> :D
[04:56] <StevenHarperUK>  Hello : could a MOTU please re-sync the REVU uploaders keyring, so I can have upload rights to REVU?
[04:58] <persia> StevenHarperUK: It appears that nobody who can is around right now.  I believe it syncs automatically each night, and many of the people who can read backscroll, so it may also be manually synced based on your last request.  There's no need to repeat yourself.
[05:00] <StevenHarperUK> Roger that
[05:03] <jonek> hi, I have problems with the package em8300-source. is here the right place to ask questions about it?
[05:03] <persia> jonek: Are you attempting to use the package, or patch it?
[05:04] <jonek> persia: use it - which seems impossible or at least very difficult on feisty - so I would like to help improve it
[05:07] <persia> jonek: I understand.  I stopped using it with dapper.  If you have questions about how it works, #ubuntu is your channel.  If you are trying to patch it, and need help making a new package, this is the right place.  For help with changing it, I recommend upstream - my memory is that they are fairly responsive and helpful.
[05:08] <polopolo> Can someone help my with the following problem?
[05:08] <jonek> persia: is an ubuntu specific bugzilla available for the em8300-source package?
[05:08] <polopolo> I  get the error
[05:08] <polopolo> ackage name "gVerse" is not in a valid format.
[05:08] <polopolo> Debian policy manual states:
[05:08] <polopolo>   "Package names must only consist of lower case letters, digits (0-9),
[05:08] <polopolo>    plus (+) or minus (-) signs, and periods (.)"
[05:08] <jonek> persia: do you mean debian by upstream?
[05:11] <geser> polopolo: what's the software name you want to package?
[05:11] <persia> jonek: https://bugs.launchpad.net/ubuntu/+source/em8300, but you might be interested in http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=em8300 as well.  Upstream is http://dxr3.sourceforge.net/
[05:11] <jonek> persia: thx
[05:11] <polopolo> geser: gVerse
[05:13] <geser> you need to use gverse as package name
[05:13] <geser> the orig.tar.gz needs also use gverse
[05:14] <polopolo> sorry, I have to eat
[05:19] <StevenHarperUK> Hi : i'm trying to make a Source package, my project is in Python, what's the difference between a source package and a binary one if its a Python based package?
[05:21] <StevenHarperUK> Oh, and what's the point of providing a binary package if its in Python?
[05:22] <geser> the source package contains as shipped by upstream (usually a tar.gz, tar.bz2, etc.) and the binary package contains the files as they end up after compilation and installation
[05:23] <StevenHarperUK> Ok so I have a tar.gz made by my Python setup.py
[05:23] <StevenHarperUK> how do I make that into  adeb source package
[05:23] <geser> the binary package installs the executables to /usr/bin/, the data to /usr/share/, the man pages to /usr/share/man, etc.
[05:24] <geser> a source package is the upstream archive (orig.tar.gz), Debian/Ubuntu changes (files in debian/ and modifications of upstream code) as diff.gz and a .dsc glueing both together
[05:25] <StevenHarperUK> Ok : Im the author of the Source.tar.gz : I have that bit made
[05:26] <StevenHarperUK> How do I make a Debian Source from that
[05:26] <geser> !packagingguide
[05:26] <ubotu> The packaging guide is at http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html - See https://wiki.ubuntu.com/MOTU/Packages/New for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/DeveloperResources - See also !backports
[05:26] <StevenHarperUK> I also have the final Package made : the bit im stuck on is the Source deb
[05:27] <geser> it's not a source deb, the source package contains of 3 files: the orig.tar.gz, the .diff.gz and the .dsc file
[05:28] <StevenHarperUK> Rigth
[05:28] <StevenHarperUK> so whats a sdc?
[05:28] <StevenHarperUK> ***dsc?
[05:28] <geser> if you have everything set up to build a binary deb correctly, you also get the source package
[05:28] <StevenHarperUK> Thats the problem I dont think I have
[05:29] <geser> the .dsc file contains the md5sum of the .orig.tar.gz and the md5sum of the .diff.gz and some meta information
[05:29] <StevenHarperUK> Im using dpkg-deb to make the deb
[05:29] <geser> it gets generated automatically during building
[05:29] <statik> hi, i did my first upload to revu last night, a new package called python-coverage. I don't see it showing up on http://revu.tauware.de/, should it?
[05:29] <StevenHarperUK> is dpkg-deb the right tool to use?
[05:30] <geser> not really, it is very, very low-level, you don't normally call it yourself
[05:31] <StevenHarperUK> Oh I have got it working with that
[05:31] <geser> the normal way is to use debian/rules and dpkg-buildpackage (or debuild)
[05:32] <StevenHarperUK> Yes but I don't have a rules file..... as its Python there's no compile
[05:32] <geser> dpkg-deb is used by the tools which help you at building the package
[05:33] <geser> but you have to copy the files to the correct location (e.g. setup.py install) which is also done in debian/rules by the install target
[05:34] <persia> statik: It should show up within about 5 minutes.  When it doesn't you should ask here why it didn't.  Are you a member of ubuntu-universe-sponsors?
[05:34] <geser> pick a python package which is similar to yours and look there how the packaging is done
[05:35] <statik> persia: I joined last night, yes. I think I got some of the details wrong on the source package that I uploaded, like the distro series in the changelog.
[05:36] <StevenHarperUK> I am finding that there is a lack of complete documentation on all This Packaging
[05:36] <StevenHarperUK> Making my App was easier
[05:36] <StevenHarperUK> which is wrong
[05:36] <persia> statik: Did someone sync the keyring since you joined? (I don't know your timezone, so "last night" doesn't tell me enough)
[05:37] <statik> persia: yes, I asked for a sync about 9 hours ago, and crimsun started one
[05:38] <StevenHarperUK> geser : if I get a source package (python based one) will that have all the structre and files I need?
[05:38] <geser> yes
[05:39] <geser> you get a unpacked upstream tar.gz with a debian/ dir. The important files for you are in debian/
[05:40] <StevenHarperUK> Basically you just call my setup.py  file to do the install : thats teh standard
[05:40] <StevenHarperUK> So that will go iin the Rukes file?
[05:40] <geser> persia: I remember Hobbsee have problems with keyring syncing yesterday (timeout or something) but I don't know if it got resolved.
[05:40] <StevenHarperUK> **rules?
[05:41] <persia> statik: Most of your package appears stuck in incoming, and your source.changes was rejected.  I'm not sure why.  I think you need to have the files deleted before you can upload again.
[05:41] <persia> geser: Yes, but REVU is working for some people.  I don't understand why (or why not).
[05:42] <geser> StevenHarperUK: as that it's common cdbs (a packaging tool) has a ready plugin for it
[05:42] <statik> persia: that makes sense, I've learned more in the last few hours and fixed several things in the source package (and even tested in a pbuilder). Do you know how I could get the files deleted so I can upload a new source package?
[05:42] <persia> statik: Someone has to delete them manually.
[05:43] <statik> persia: ok. is this something that I should send an email request about, or does it get handled automatically? (and thanks for all the help!)
[05:44] <persia> statik: It gets handled by asking here.  It's Sunday in most parts of the world, and those who tend to fix it aren't very active right now.  If you don't hear from someone else, try asking again tomorrow.
[05:45] <statik> persia: perfect, I'll do that. thanks again!
[05:53] <beuno> what's the policy on uploading packages from Ubuntu to Debian with patches from Ubuntu?
[05:53] <shawarma> Bump the debian version and just upload it, I suppose.
[05:54] <shawarma> IANADD, but I don't see what else there is to do.
[05:54] <persia> beuno: To get an official answer, you'd need to ask someone in Debian.  Ubuntu prefers that patches are applied in Debian.
[05:54] <shawarma> beuno: Removing the "ubuntuX" part from the version string in the process of course.
[05:54] <beuno> what's the policy on uploading packages from Ubuntu to Debian with patches from Ubuntu?
[05:54] <shawarma> ?
[05:54] <shawarma> Um..
[05:54] <persia> beuno: Personally, I like it when Debian maintainers do something like http://packages.debian.org/changelogs/pool/main/s/slashem/current/changelog
[05:54] <shawarma> Bump the debian version and just upload it, I suppose.
[05:54] <shawarma> IANADD, but I don't see what else there is to do.
[05:55] <shawarma> beuno: Removing the "ubuntuX" part from the version string in the process of course.
[05:55] <shawarma> this is going to be a long day. :)
[05:55] <beuno> persia, shawarma, these are new packages that aren't in Debian
[05:55] <beuno> (I'm add the debconf, btw)  :p
[05:55] <shawarma> beuno: Ah. That did not become much more obvious when you asked the exact same question the scond time :)
[05:56] <persia> beuno: I believe best practice is to file an ITP and contact the utnubu team.
[05:56] <beuno> shawarma: I didn't get that answer, they're still playing around with the APs
[05:57] <beuno> persia: I already have a sponsor, already pacakged it, and already have the ITP
[05:57] <beuno> I'm just wondering on how to handle the work done on the initialy packaging done in Ubuntu
[05:58] <persia> beuno: Then it gets uploaded.  It should follow Debian policy (Debian versions, dedicated maintainer, etc.), but otherwise Ubuntu doesn't impose anything.  Thereafter, Debian should become the default source of new upstreams, etc.
[05:58] <beuno> as in acknowledgeing it
[05:59] <beuno> great then, I'll dedicate my next 2 weeks here to packaging Ubuntu apps into compying with Debian plicy and uploading them  :D
[05:59] <persia> beuno: Ah.  In debian/copyright, leave the "This package was originally debianized by J. Random Hacker", and in the Debian Packaging is copyright foo section, list the original packager.
[05:59] <beuno> persia: right, that's the answer I was looking for, thanks
[06:00] <persia> beuno: TO clarify, something like "The packaging is (C) 2003-2005 Enrique Roblefo Arnuncio <era@debian.org>, 2007, Emmet Hikory <emmet.hikory@gmail.com> and is licensed under the GPL, see above.", except the other way around.
[06:12] <persia> beuno: Just a note; you probably don't want to put everything back in Debian.  There are a number of packages that have been separately packaged for Debian (with different names) and should be removed from Ubuntu.  There are also a number of packages that don't integrate well, or don't provide new functionality.  My memory is that Debian prefers to only have the best two or three apps for each function, and prefers integration.
[06:31] <jamyskis> hi everyone...am back
[06:33] <jamyskis> persia: did you catch the problem i was having earlier on with two deb packages (naughts-and-crosses, naughts-and-crosses-common) being created but only naughts-and-crosses actually containing the stuff?
[06:33] <polopolo> Can someon help my package a program with debhelper like gVerse
[06:34] <persia> jamyskis: Sorry, I missed it.  Could you pastebin debian/naughts-and-crosses-common.install?
[06:34] <jamyskis> persia: sure hold on
[06:36] <jamyskis> persia: http://paste.ubuntu-nl.org/25011/
[06:38] <beuno> I'm having trouble packaging with CDBS, the Ubuntu docs aren't clear on how to actually build the package (http://doc.ubuntu.com/ubuntu/packagingguide/C/basic-cdbs.html)
[06:40] <persia> jamyskis: Ah.  You need a destination :)  Where are the files supposed to end up?  Also, is this the entire contents of the data/ directory?
[06:40] <jamyskis> persia: with the exception of Makefile, Makefile.am and Makefile.in yep :)
[06:40] <jamyskis> persia: can you post the format in the pastebin?
[06:40] <jamyskis> persia: the problem is that some of the graphic files are a little big
[06:41] <jamyskis> persia: im working on way to compress them without resorting to yet more libraries
[06:41] <persia> jamyskis: It's "source destination" for each line, space delimited.  Drop the initial / from the destination.
[06:42] <RainCT> I've a (a bit off-topic) question: I'm writting a Python application with many .py files, but only of them should be executed directly. So, would the main .py go to /usr/bin and the others to /usr/include/<program name>, or what?
[06:42] <persia> jamyskis: Also, you can use globs, so "data/*.bmp usr/share/naughts-and-crosses-common/" would work.
[06:43] <jamyskis> persia: ok got it thanks :)
[06:45] <geser> RainCT: yes, but /usr/share/<packagename>
[06:46] <daschl> hey guys, someone packaging-related here? :)
[06:46] <persia> jamyskis: geser ha just reminded me, you probably want "usr/share/naughts-and-crosses" (no -common).
[06:46] <RainCT> geser: ok, thanks. will Python automatically search there if I make an import or how to I write it?
[06:46] <persia> daschl: Very much so.
[06:46] <jamyskis> persia: good timing, i'd just finished debuild -S -sa and was about to build the binary :)
[06:46] <daschl> persia, hey. i found a problem here https://bugs.launchpad.net/ubuntu/+source/ruby-defaults/+bug/50480 and someone told me that this is very packaging-related, so i decided to come up with this issue here
[06:46] <ubotu> Launchpad bug 50480 in ruby-defaults "Reported version is incorrect" [Undecided,Confirmed]  
[06:47] <persia> daschl: Just to make sure I understand, this is a wishlist request for a no-changes version bump?
[06:47] <daschl> persia, i dont know what you are talking about, this is my first "bugfix" on ubuntu.. 
[06:48] <daschl> persia, but: yes, i think so.. the version numbers are inconsistent!
[06:48] <persia> daschl: OK.  To rephrase.  The request is to change the version of the package, but not anything els about the package?
[06:48] <daschl> persia, yes.
[06:49] <jamyskis> ok...here's hoping that this time it's right
[06:49] <daschl> jamyskis, do you mean my request?
[06:50] <jamyskis> daschl: sorry, no...i meant that i've been at trying to build a ubuntu repo compliant deb for the past three days and there's always been something wrong
[06:50] <jamyskis> daschl: but we've almost got it sorted
[06:50] <daschl> jamyskis, i c :D
[06:51] <persia> daschl: I don't think we want to fix that in Ubuntu without coordination with Debian.  You might be intersted in looking at debian bug 359810 as a possible link for your bug.
[06:51] <ubotu> Debian bug 359810 in ruby-defaults "ruby-defaults: please use less confusing package versionning scheme" [Wishlist,Open]  http://bugs.debian.org/359810
[06:51] <daschl> persia, why is this important? (really, im interested :))
[06:52] <jamyskis> persia: didn't work
[06:52] <persia> daschl: If we bump the version in Ubutu, and Debian uploads a newer package with new fixes, we won't be automatically notified, which means the fixes might take a long time to get to Ubuntu.
[06:53] <daschl> persia, oh, so it would be good if debian and ubuntu cooperate and bump the version together..
[06:53] <persia> daschl: Exactly, or to change the version scheme for ruby-defaults so it is less confusing.
[06:53] <daschl> persia, so what can i do?
[06:55] <persia> daschl: You could contact Ukai-san, but the Debian bug is a year old without response, so you shouldn't expect much.  You could also point the Ubuntu bug submitter to the Debian bug, and apologize for the confusion, but that doesn't fix it.
[06:55] <jamyskis> persia: i forgot to put the last / in
[06:55] <jamyskis> in the install file
[06:55] <jamyskis> don't know if that would make a difference
[06:55] <persia> jamyskis: Ah good.  I've been digging in http://wiki.debian.org/PkgSplit and not seeing anything that would explain the issue :)
[06:56] <daschl> persia, thx, brb
[06:58] <jamyskis> persia: didn't make a difference
[06:59] <jamyskis> if you'd like i can .tar.gz the entire folder if you'd like to take a look
[07:00] <persia> jamyskis: Better for me would be for you to upload the (broken) package to REVU, as I'm to bed very soon :)  Maybe someone else will see it quickly.
[07:01] <jamyskis> its fine...im just about wound up with it for today anyway
[07:01] <jamyskis> i can carry on tomorrow
[07:02] <jamyskis> because i think i'll end up smashing my keyboard in if this plays up any more
[07:02] <jamyskis> the debian lot really need to look at how this lot works because there really is no need for debian packaging to be this complicated
[07:03] <jamyskis> thanks for all your help persia :)
[07:06] <RainCT> is there any path where default config files are stored (if the users hasn't it's own)?
[07:08] <persia> RainCT: /etc/<packagename>
[07:09] <RainCT> thanks
[07:20] <jrib> would anyone like to review http://revu.tauware.de/details.py?upid=5444http://revu.tauware.de/details.py?upid=5444, a python module?
[07:21] <jrib> (you only have to review it once :P)
[07:36] <jamyskis> http://revu.tauware.de/details.py?upid=5454 <-- could someone take a look and find out why my attempts at creating split packages are resulting in everything going into one and nothing in the other? thanks
[07:47] <jamyskis> anyone there?
[07:51] <lionel> jamyskis: probabily:)
[07:51] <jamyskis> lionel: was just curious because it went dead
[07:52] <lionel> it's week-end, people are sometimes afk
[07:54] <jamyskis> lionel: you're capable of reviewing packages aren't you?
[07:55] <lionel> I'm not sure I have reviwer rights, and I have to go in few min. Could you drop me a mail?
[07:55] <jamyskis> lionel: no worries...i'll leave it until tomorrow
[07:56] <jamyskis> i've been trying to package something for three days now and somehow it always doesn't meet ubuntu repo requirements
[07:56] <jamyskis> i'm pretty much at the point now where i'm about ready to give up and just continue hosting it at my repo
[07:56] <lionel> keep trying to get your package in
[07:57] <lionel> it will nice for Ubuntu to have the package, and nice for you to learn always more
[07:57] <lionel> I know sometimes it can be frustrating to be reviewed
[08:00] <jamyskis> lionel: the problem is less the reviewers and more the fact that the debian lot neglected any kind of usability when they designed the package creation system
[08:01] <jamyskis> if they simplified the process of creating packages there might be more submitted
[08:06] <man-di> jamyskis: its complex, but when you are used to it its very flexible
[08:07] <jamyskis> man-di: maybe, but there needs to some kind of interface that sacrifices some of that flexibility for ease-of-use for beginners
[08:07] <jamyskis> man-di: maybe a GTK+ GUI :)
[08:07] <jamyskis> man-di: otherwise beginners just get swamped in the dozens of files and options
[08:07] <man-di> jamyskis: you are free to write such a tool ;-)
[08:08] <jamyskis> man-di: i was actually thinking about it but i need to know how the packaging system works first :)
[08:08] <man-di> jamyskis: I guess its easier to just learn all the files then writing such a tool
[08:08] <man-di> jamyskis: I do debian packaging since several years
[08:08] <jamyskis> man-di: true, most people write stuff that they themselves would need and once they know what they need to write such a tool, they don't need a GUI anymore
[08:09] <man-di> and I think such a GUI would be even more complex to use then just using a text editor to edit some files
[08:09] <jamyskis> man-di: that's the problem, the motivation to solve a lot of problems
[08:09] <jamyskis> i disagree - it depends on how you design the GUI
[08:09] <man-di> and there are always different ways to solve some issue
[08:09] <man-di> the GUI need to cope with all the different ways
[08:10] <daschl> i think the gui should only help during the first steps, not the whole way :) .. after some time you surely switch to CLI 
[08:10] <jamyskis> if you provide a user the means to select a PGP key and design the file structure that would be ample for beginners...it sacrifices the flexibility but is sufficient for most
[08:10] <jamyskis> daschl: you are right, of course
[08:11] <jamyskis> but a GUI would be a good start
[08:11] <jamyskis> i used synaptic almost exclusively at the start before i got to know how apt-get works
[08:11] <man-di> jamyskis: dh-make creates a good first skeleton, IMO
[08:11] <daschl> jamyskis, i agree with you. but i dont have the knowledge and skill to write such a gui .. and i really wonder that theres nothing out there
[08:11] <jamyskis> daschl: then maybe that's something i'll bring up
[08:12] <daschl> jamyskis, it would be great if i can assist you during the development progress, so i can learn it all from scratch 
[08:12] <jamyskis> daschl: i was considering learning and using glade for it
[08:13] <daschl> jamyskis, well i played around with gtk+ (especially ruby-gtk) 
[08:13] <jamyskis> daschl: too advanced for me :)
[08:13] <jamyskis> daschl: maybe wxWindows though
[08:14] <jamyskis> sorry wxWidgets
[08:15] <daschl> jamyskis, gtk+ is really easy! do you know any programming language quite well? 
[08:15] <jamyskis> daschl: i'm reasonably proficient in c++
[08:16] <jamyskis> still have a lot to learn
[08:16] <jamyskis> but i program my games in it
[08:16] <daschl> jamyskis, well.. you can have a look at the c++ bindings for gtk, but i prefer Qt for the moment.. it rocks :)
[08:16] <jamyskis> no experience with "serious apps" though
[08:16] <jamyskis> daschl: will do :)
[08:17] <jamyskis> actually if this is to become part of ubuntu wouldn't learning python be a better option and doing it in that?
[08:17] <jamyskis> python has gtk+ bindings
[08:17] <daschl> jamyskis, Qt really kicks ass.. i needed a gui for a network device configurator and i tried gtk+ first, but then i looked at Qt and i changed the whole app :)
[08:17] <juliank> Hi! Can somebody please upload the merged revision of ndisgtk (0.7.2-1ubuntu1) to universe? http://jak-linux.org/projects/ndisgtk/pkgs/ndisgtk_0.7.2-1ubuntu1.dsc (also at REVU)
[08:18] <jamyskis> daschl: i do like qt (and kde) but the whole look and feel of it is spoiled under gnome
[08:20] <daschl> jamyskis, i dont agree with you .. have you ever looked at amaroK for example?
[08:23] <polopolo> hello
[08:26] <jamyskis> daschl: not yet
[08:29] <jrib> polopolo: hi
[08:29] <jamyskis> polopolo: hello
[08:34] <polopolo> Is it a problem if I use http://www.debian.org/doc/maint-guide/ch-start.en.html to make my .deb?
[08:34] <polopolo> for ubuntu
[08:37] <man-di> polopolo: thats in fact the recommended way
[08:37] <man-di> polopolo: debian and ubuntu packaging is basically the same
[08:37] <polopolo> ok
[08:37] <man-di> polopolo: there are only some nuances that are different
[08:38] <polopolo> version numbers I alreadt knows
[08:42] <daschl> jamyskis, look here (amaroK under Gnome) .. my desktop: http://www.netfux.org/Screenshot.png
[08:44] <daschl> jamyskis, of course, only original cds ripped with "abdce" :)
[08:46] <jamyskis> daschl: you have your kcontrol well set up but you can recognise it isn't native :)
[08:46] <daschl> jamyskis, it is native.. i didnt change anything!
[08:47] <jamyskis> daschl: i mean the theme settings with qt are seperate from gtk+
[08:47] <daschl> jamyskis, yes they are separate, but what you see here is default :) .. i installed amarok at my girlfirends pc (gnome feisty) and nothing looked different
[08:50] <jamyskis> daschl: exactly...but if a user starts playing around with fonts and themes but doesn't know the difference between gtk+ and qt then you end up with something like this: http://www.jamyskis.net/Screenshot.png
[08:53] <jamyskis> oops
[09:07] <daschl> jamyskis, looks ugly :p
[09:07] <jamyskis> daschl: i rest my case :)
[09:07] <jamyskis> that's not my theme by the way
[09:07] <daschl> jamyskis, xD
[09:07] <daschl> jamyskis, i c
[09:07] <jamyskis> i just did it to make a point hehe
[09:07] <daschl> hehe
[09:16] <_Enchained> hi
[09:48] <_Enchained> Can someone remove this package from REVU please : http://revu.tauware.de/details.py?upid=5252
[10:19] <lionel> man-di: just for your information bug #119739
[10:19] <ubotu> Launchpad bug 119739 in libapache-mod-jk "libapache-mod-jk is vulnerable to CVE-2007-1860" [Undecided,Unconfirmed]  https://launchpad.net/bugs/119739
[10:20] <man-di> lionel: yes, I saw this in my mail already
[10:20] <man-di> lionel: thx for taking care of this
[10:20] <lionel> man-di: no pb!
[10:20] <man-di> lionel: should this be fixed for edgy, feisty and pre-dapper too?
[10:21] <lionel> I have just added patch for Dapper, Edgy, Feisty
[10:21] <lionel> (pre Dapper is not supported any more)
[10:35] <man-di> lionel: okay, thx
[10:36] <man-di> lionel: I have uploaded new version to unstable too, this can be merged to gutsy
[10:36] <RainCT> jamyskis: I've tried out Open Invaders but it didn't start up but let my PC at 640x480 resolution. Then when I pressed Ctrl + Alt + Backspace the PC restarted :S. I'll sue you ;P
[10:38] <lionel> man-di: yeah, I have seen on devel-changes, thanks!
[10:38] <jamyskis> RainCT: that's the first I've heard of that...especially since the game uses 800x600 natively
[10:38] <jamyskis> did you just try to use the package in MOTU?
[10:38] <jamyskis> its broken
[10:39] <RainCT> jamyskis: well then it was 800x600, fact is everything looked very big and I saw only like 1/3 of the screen
[10:39] <RainCT> jamyskis: I compiled the source from your web
[10:39] <RainCT> (and I don't know if it outputed something since the terminal window wasn't on my screen anymore, it was at the bottom :P)
[10:40] <jamyskis> RainCT: try starting with open_invaders -w
[10:40] <RainCT> jamyskis: well, not today :P
[10:40] <jamyskis> RainCT: Not feeling brave enough ;)
[10:42] <RainCT> jamyskis: I'd, but I don't what happened that Ctrl + Alt + Backspace restarted and I don't want to wait for it to restart again :P (well, I could just go to Ctrl + Alt + F1 and restart from there, but anyways.. perhaps tomorrow)
[10:43] <jamyskis> RainCT: it sounds like something is not right with your X server or video drivers
[10:44] <jamyskis> RainCT. do you have a 3D driver installed?
[10:44] <RainCT> jamyskis: no, I don't even think my video card has 3D.. It has just 8MB memory xDD
[10:45] <jamyskis> RainCT: interesting...
[10:48] <jamyskis> RainCT: could you do me a favour and type lshw >hardware.txt and then send me the contents of that file?
[10:48] <jamyskis> RainCT: I'd be very interested to know what part of the game caused the comp to crash
[10:50] <RainCT> jamyskis: as root?
[10:50] <jamyskis> RainCT: doesn't need to be
[10:50] <jamyskis> RainCT: works as normal user
[10:53] <_Enchained> Is there a revu admin here ?
[10:53] <_Enchained> (to remove a package)
[10:55] <RainCT> jamyskis: http://paste.ubuntu-nl.org/25025/
[10:57] <jamyskis> RainCT: to the best of my knowledge you do have 3D capability (i810 driver) although in this case that doesn't matter because OI doesn't use hardware acceleration
[10:57] <jamyskis> RainCT: but i'll see if i can find someone else i know with this graphics card and see if i can reproduce the problem
[10:57] <jamyskis> RainCT: thanks for the heads up
[11:00] <RainCT> jamyskis: okay. ping me tomorrow if you want and I'll try again
[11:00] <RainCT> going to bed now
[11:01] <jamyskis> RainCT: okey-doke good night
[11:02] <jamyskis> im off to bed too
[11:02] <jamyskis> good night everyone
[11:03] <RainCT> good night