[00:23] <MTecknology> Who maintains the drupal package for the ubuntu repos?
[00:23] <MTecknology> !info drupal6 jaunty
[00:24] <MTecknology> The current version is 6.12
[00:24] <cody-somerville> !info drupal6 karmic
[00:24] <cody-somerville> fancy that
[00:26] <MTecknology> cody-somerville: ... drupal will only be updated with ubuntu releases?
[00:26] <cody-somerville> !backports
[00:27] <MTecknology> cody-somerville: I understand that much, but the drupal updates usually include security patches too
[00:29] <cody-somerville> MTecknology, I can imagine
[00:31] <MTecknology> cody-somerville: I suppose for my case then it might be a better idea to keep drupal in /var/www/ :P
[00:31] <cody-somerville> Personally, I never use web based apps from the repo
[00:32] <MTecknology> I was trying to move to doing it
[00:32] <MTecknology> but ya, probably a good decision to keep w/ what I was doing then :P
[00:32] <MTecknology> anyway - It's bed time - I get up to go to work 0100, makes for a fun night
[00:32] <MTecknology> ttyl
[00:32] <cody-somerville> bye
[01:11] <SirDerigo> un derigo para encontrarlos a todos, un derigo para engañarlos, un derigo para atraerlos a todos y atarlos al S.L
[04:38] <kklimonda> when I work with package (i.e. making changes and using UNRELEASED pocket) what should I do with package version? Bump debian revision or use the same?
[04:52] <xnox`> my package is in the debian import queu / accepted
[04:53] <xnox`> do new pacakges from debian get synced into ubuntu? or do I need to file a sync bug in launchpad?
[04:58] <jmarsden> xnox`: They get synced.  sword just got synced into Karmic :)
[04:59] <jmarsden> SWORD was manual, but a new package that has no package-w.x-yubuntuz already in Karmic is supposed to autosync,
[05:19] <xnox`> jmarsden: ok =D
[05:20] <jmarsden> Is xiphos ready to get into Debian unstable?
[05:20] <xnox`> hmmm it's already in the queue/accepted
[05:21] <xnox`> http://incoming.debian.org/
[05:21] <jmarsden> Cool!
[05:22] <xnox`> after it will all both bibletime & xiphos land in karmic & get compiled we can start filling out requests for backporting ;-)
[05:23] <xnox`> did we tell sword people that we have sliced and diced their tarball?
[05:25] <jmarsden> Well, we told the ones in the pkg-crosswire list at least :)
[05:27] <xnox`> yeah there are about 15 people signed up to the list is it all the upstream bibletime / xiphos / sword lurking?
[06:38] <Fenix|home> Greetings
[06:38] <Fenix|home> TheMuso: Are you available?
[06:47] <artfwo> Hi! Has there been any progress with bug 372243?
[08:16] <kklimonda> what is current debian policy about asking questions during package upgrades? is there any?
[09:17] <maxb> I don't know of anything official, but I imagine it's something like "Only do it if you really really need to "
[09:40] <gaspa> can someone please give-back alt-ergo and pxp ? (they build fine in my ppa, so at least amd64,i386 and lpia)
[09:42] <geser> gaspa: done
[09:43] <gaspa> geser: :)
[10:47] <hyperair> when a bug is marked for expiration, should i change its status to invalid?
[10:47] <hyperair> or should i just leave it as incomplete?
[10:48] <aboSamoor> Hi, this is my first time to think about packaging, usually everything is available in repositories with updated versions. Now, I found that bpython is not in jaunty and I want to package it and add it to my own repository, is there any specific tutorial for python packaging ?
[10:58] <loic-m> !packaging
[10:58] <loic-m> aboSamoor: bpython |    0.9.2-1 |      unstable | source, all
[10:58] <loic-m> aboSamoor: so it's in debian
[10:59] <loic-m> aboSamoor: and karmic, see: bpython |    0.9.1-1 | karmic/universe | source, all
[11:00] <aboSamoor> loic-m: I tried the debian package and it is installed without problems but it crashs before starting, so I thought I may have to package it against ubuntu
[11:01] <loic-m> aboSamoor: just get the source package first, and build it for Jaunty or use a pp
[11:01] <loic-m> s/pp/ppa
[11:02] <loic-m> or use prevu bpython for a quick look at karmic's 0.9.1
[12:01] <bencrisford> I have been working on a bug, I fixed it so I made a debdiff
[12:01] <bencrisford> but all that appeared in the debdiff was the changelog entry
[12:01] <bencrisford> none of the important stuff that actually needed to be changed
[12:01] <bencrisford> i have tried again and again...  help :'(
[12:12] <loic-m> bencrisford: what was the fix?
[12:12] <randomaction> are you taking debdiff of .dsc files?
[12:13] <bencrisford> loic-m: It was really simple, it was a matter of adding a dependency
[12:16] <loic-m> bencrisford: so the control file was changed
[12:16] <bencrisford> loic-m: Yes
[12:16] <bencrisford> but the debdiff didnt show it
[12:16] <bencrisford> loic-m: http://launchpadlibrarian.net/27556542/pellusus_2.26.0-0ubuntu2.debdiff
[12:17] <loic-m> bencrisford: are you sure the debian/control was change when making the diff.gz?
[12:18] <loic-m> bencrisford:did you manually check the diff.gz before doing the debdiff?
[12:18] <bencrisford> loic-m: Well I edited the control,  did a dch -i then debuild -S, then from the new package i made the debdiff
[12:19] <loic-m> bencrisford: check the resulting diff.gz
[12:19] <bencrisford> ok
[12:20] <bencrisford> loic-m: Its not in the diff.gz either, but if i was to add my change to the diff.gz and did my debdiff again..
[12:21] <bencrisford> would that work?
[12:22] <loic-m> bencrisford: dunno. Is saving 2 seconds worth the trouble?
[12:22] <loic-m> bencrisford: I think there's a way to do it, or you can resign afterwards, but does the debuild take _that_ long?
[12:22] <bencrisford> loic-m: ?  I don't understand..
[12:22] <bencrisford> how can i fix this?
[12:24] <loic-m> bencrisford: just make sure debian/control has the dependency, then run debuild again
[12:24] <bencrisford> i have done that several times now loic-m
[12:24] <loic-m> bencrisford: for the other solution, I've never used it, so I can't explain ;)
[12:25] <loic-m> bencrisford: if you debian/control has the dependency, it should show up in the diff.gz
[12:25] <bencrisford> loic-m: Hmm, ok, ill try, ty for your help btw ;) :)
[12:25] <loic-m> bencrisford: unless you didn't save, use the wrong directory, or there's something I can't imagine
[12:26] <loic-m> bencrisford: hope it works
[12:28] <bencrisford> loic-m: I'll be back in a bit
[12:29] <loic-m> no pb
[12:41] <thekorn> hi,
[12:41] <thekorn> I'm packaging a python application, using cdbs
[12:41] <thekorn> and I would like to add a .desktop file
[12:42] <thekorn> waht's needed to get this .desktop file registered?
[12:43] <thekorn> appart from installing this file into /usr/share/applications
[12:43] <loic-m> thekorn: put the file package.desktop in debian folder (package=name of pkg)
[12:44] <loic-m> thekorn: oh, so it's should be enough if you lready install it
[12:44] <loic-m> thekorn: just check you're also installing an icon
[12:44] <loic-m> in /usr/share/pixmaps
[12:44] <loic-m> and check your .desktop file with desktop-file-validate
[12:45] <thekorn> loic-m, yes, ok, so there is no need to add gnome.mk to debian/rules?
[12:45] <thekorn> or run dh_desktop?
[12:46] <thekorn> that's what the packaging guide says, but if I add this, the builder complains about missing ./configure
[12:47] <loic-m> dh_desktop too
[12:47] <pochu> hi thekorn :)
[12:47] <loic-m> if I read the man page correctly
[12:47] <thekorn> hi pochu
[12:48] <thekorn> oh man, packaging is so easy, but obviously way too hard for me ;)
[12:48] <pochu> thekorn: gnome.mk is not needed
[12:48] <thekorn> hmm, ok, let me try whithout it
[12:49] <pochu> dh_desktop is not needed anymore since jaunty
[12:49] <pochu> but it will do no harm
[12:49] <loic-m> pochu: I didn't know that, thanks
[12:50] <thekorn> super, thanks pochu and loic-m, it worked
[12:50] <thekorn> pochu, can we fix it in https://wiki.ubuntu.com/PackagingGuide/Complete#.desktop%20Files ?
[12:51] <pochu> thekorn: yeah, can you do it?
[12:51] <thekorn> pochu, sure
[12:52] <pochu> dh_desktop is not needed anymore since Jaunty because desktop-file-utils 0.15-2 register /usr/share/applications/ as a trigger
[12:52] <pochu> so whenever you install a file there, update-desktop-database will be called
[12:52] <pochu> so you don't need to manually call it
[12:52] <pochu> (which is what dh_desktop does)
[12:53] <alex-weej> anyone know how i can programmatically enable the universe repo? or am i going to have to butcher sources.list "manually"?
[12:55] <thekorn> pochu, ah ok, thanks for the explaination, I quoted you in the comment of my edit
[12:55] <pochu> :)
[12:58] <thekorn> else, nobody would trust a packaging n00b like me ;)
[13:09] <bencrisford> loic-m: No matter how many times I try, or what I try, nothing seems to be working :'(
[13:22] <AnAnt> Hello, can someone sponsor those:  LP #359436 , LP #359444 , LP #359446 ?
[13:45] <bencrisford> loic-m: What im doing is simple as this:
[13:45] <bencrisford> vi debian/control
[13:45] <bencrisford> dch -i
[13:45] <bencrisford> debuild -S
[13:45] <bencrisford> cd ..
[13:45] <bencrisford> debdiff  file.dsc file-new.dsc > file-new.debdiff
[14:21] <gaspa> can someone please give-back galax?
[14:26] <jpds> gaspa: By your command: http://paste.ubuntu.com/189600/
[14:28] <gaspa> jpds: thanls
[14:28] <gaspa> thanks
[14:34] <binarymutant> if someone has the time to do a revu on this package http://revu.ubuntuwire.com/p/pidgin-mbpurple I would be very appreciative :)
[14:50] <pi-meson2> A colleague and I are trying to package the latest HDF5 libraries and pytables to a PPA. Both build fine locally, and pytables (which depends on hdf5) builds the deb, but the deb doesn't install, claiming that "Package libhdf5-serial" is not installed. Is there any way to get additional debugging information from dpkg -i to help us figure out where we're going wrong?
[14:51] <StevenK> dpkg won't install dependancies for you
[14:51] <StevenK> apt will, however
[14:51] <pi-meson2> right, I know that
[14:51] <pi-meson2> we built (and installed) the dependency ourselves
[14:52] <pi-meson2> that is, we built the deb that provides the dep ourselves (that's one of the things we're trying to package)
[14:52] <StevenK> So it seems you need to install libhdf5-serial first
[14:52] <pi-meson2> right, we did! or thought we did
[14:53] <pi-meson2> http://paste2.org/p/250097 claims it's "installed"
[14:54] <StevenK> That's your problem
[14:54] <StevenK> libhdf5-serial-1.8.3-0 != libhdf5-serial
[14:55] <pi-meson2> so our libhdf5 deb should also list "libhdf5-serial" under its "provides"?
[14:56] <StevenK> That would solve that particular issue, yes
[15:00] <penguin42> Does anyone here understand the origin and versioning of cryptsetup? The changelog in the source ends in 2007
[15:04] <pi-meson2> StevenK: okay, that ended up working, thank you very much for the help
[15:29] <penguin42> anyone know about the _( and N_( macros - what's the difference?
[18:33] <nixternal> wgrant: when are you going to put the synaptics package into karmic? need my tapping back :p  in the mean time I will test out your PPA one
[18:41] <nixternal> wgrant: vote of confindence from me, that gives me my tapping back :)
[19:08] <loic-m> slangasek, ping
[19:11] <slangasek> loic-m: hi
[19:11] <loic-m> slangasek, hi
[19:12] <loic-m> slangasek: about http://dep.debian.net/deps/dep5/ I've got a few questions
[19:12] <loic-m> slangasek: don't know if you'ge got the time though
[19:13] <loic-m> slangasek: mainly for the Files: section, this bit "indicating files that have the same licence and share copyright holders."
[19:14] <loic-m> slangasek: it gets overly messy on big src/ with each files having diferent mix of authors
[19:15] <loic-m> slangasek: wouldn't it just be better to just group the files with the same License, and group the copyrights even if they're not all the same on each file?
[19:15] <slangasek> loic-m: the format doesn't dictate how you group authors; if you have twenty authors across 60 files and you want to list a single Files section for them, the format allows you to do that
[19:15] <slangasek> this should probably be clarified in the draft
[19:15] <loic-m> slangasek; Thanks. That's not clear from the description (see the citation)
[19:16] <loic-m> slangasek: that would be great
[19:17] <loic-m> slangasek: I think the other question I had was about multiple year copyright, since all the example are one year only (not so clear then)
[19:18] <loic-m> slangasek: I remember reading (don't know if it was FSF or Debian) that we should detail each year, like 2001, 2002, 2003, 2004
[19:18] <loic-m> slangasek: and not 2001-2004
[19:18] <slangasek> loic-m: correct representation of multiple-year copyrights is dictated by law, I don't think we should make any claims about this one way or the other in the spec :)
[19:18] <loic-m> What's the specification take on that?
[19:19] <loic-m> slangasek: ok. Maybe state what the law is then for more clarity (or add multiple years example)
[19:19] <slangasek> we might refer people to the law, or to a faq someone else has already written
[19:19] <slangasek> stating what the law is would be out of scope for this
[19:22] <loic-m> slangasek: last question -  when there's many files in a folder, and only a few have a different License
[19:23] <loic-m> since the format should also be human-readable
[19:23] <loic-m> Isn't there a way to cover all files minus a few files other than glob, which isn't really human-readable?
[19:24] <slangasek> I'm not sure why you say globs aren't human readable; they're more readable than anything else I can think of for doing this
[19:24] <slangasek> and they're also machine-readable
[19:25] <loic-m> I'll try to point you to an example in a minute
[19:25] <jmarsden> loic-m: Remember you can do a straight somedir/* glob and then later Files: sections take care of the exceptions.
[19:26] <jmarsden> So there is little need for a complex glob...
[19:31] <jmarsden> Incidentally, there is a typo in the dep5 spec: "If multiple Files declaratioun match the same file, then only the last match counts."
[19:32] <jmarsden> declaratioun should be declarations, I think :)
[19:34] <loic-m> jmarsden: here's what mess I'm thinking about http://paste.ubuntu.com/189767/
[19:34] <loic-m> oversimplified of course ;)
[19:35] <loic-m> "Remember you can do a straight somedir/* glob and then later Files: sections take care of the exceptions." that sounds exactly like what I'd like - src/* then list the files in src/ that aren't included
[19:35] <loic-m> unless of course we use the ""If multiple Files declaratioun match the same file, then only the last match counts."
[19:36] <jmarsden> Which is exactly what you should do.  So you can simplify the first Files to Files: src/* -- which is human readable.
[19:37] <loic-m> Ok, thanks. I wasn't sure about it.
[19:37] <jmarsden> I'm no expert, but that's how i read the spec, anyway :)
[19:37] <loic-m> jmarsden: can anybody edit the DPE-5 page?
[19:38] <jmarsden> I'm not sure.  Anyone could, when it was a wiki, but now it is a DEP... try it, I guess :)
[19:40] <loic-m> I don't think I'd dare though ;)
[19:41] <loic-m> It's probably editable on the VCS
[19:41] <loic-m> I'd just like to see that you group files with the same licenses, not the same exact copyrights
[19:47] <slangasek> you can create a bzr branch of it and push changes
[19:47] <slangasek> but it's deliberately not a wiki at this point, because that resulted in lots of drive-by edits without any discussion among the larger Debian community
[19:48] <slangasek> by "push changes", I mean "email the DEP drivers and ask them to merge"; but there are some internal administrativa to sort out yet before we're actually ready to do that, fwiw
[19:51] <loic-m> slangasek: i may just edit a patch and send them to somebody that can edit the page, or just send the questions needing to be clarified and a few modified paragraph proposing a way to clear them
[19:51] <bencrisford> loic-m: Just fyi, i managed to fix that problem from earlier with LaserJock's help :), i just needed to edit the .in rather than
[19:51] <stefanlsd> Something i've done in dep5 recently. I feel its quite readable and also helped me to get the licensing more correct - http://bazaar.launchpad.net/~stefanlsd/+junk/gears/revision/18
[19:51] <bencrisford> than just the control*
[19:52] <slangasek> loic-m: honestly, I would recommend waiting until the discussion process starts on debian-project
[19:52] <slangasek> right now there's far *too much* private discussion going on of the DEP, which I'm trying (weakly) to wrap up
[19:53] <loic-m> bencrisford: good to know
[19:53] <loic-m> bencrisford: Althoug I don't know what's the .in ;)
[19:54] <bencrisford> loic-m: I think its what debuild reads
[19:54] <bencrisford> it doesnt read the control, but the control.in
[19:54] <bencrisford> apparently anyway
[19:54] <loic-m> stefanlsd: thanks, it looks good!
[19:55] <loic-m> slangasek: ok, it's just that some of us are trying to use it esp. for new packages
[19:56] <loic-m> well, thanks a lot slangasek, stefanlsd and jmarsden
[19:58] <nhandler> If I run piuparts with the -p flag (to have it use pbuilder), shouldn't it parse my ~/.pbuilderrc file to determine the location of the tarball?
[20:06] <loic-m> bbl
[20:15] <kklimonda> nhandler: well, it would be nice. unfortunately it has /var/cache/pbuilder/... hardcoded
[20:33] <warp10> Is there someone with an amd64 machine with debian sid installed available? I need it for a small test.
[20:38] <jmarsden> warp10: I have a sid amd64 pbuilder chroot (under Ubuntu 9.04) if that is sufficient for your test...but can't you run sid amd64 in a VM or chroot yourself to do such testing?
[20:39] <warp10> jmarsden: your chroot should be enough. You should install python-vtk, launch python and type "import vtk"
[20:40] <jmarsden> OK...
[20:40] <warp10> jmarsden: regarding to your question: I could, but my connection is really slow this evening, so I was looking for a faster solution.
[20:44] <jmarsden> Hmmm.  I'm updating it now... pbuilder-sid login got me everything up to "entering the shell" ... and then something that sucked up input but never displayed a shell prompt!
[20:44] <warp10> jmarsden: oh, weird
[20:48] <jmarsden> Definitely... and it still does it after an update.  I'll try creating a new one (I have FIOS 10mbps download speed here, so it shouldn't take *that* long...)
[20:49] <ajmitch> sorry, I only have i386 sid at the moment
[20:49]  * warp10 really, really envys jmarsden's connection
[20:49] <ajmitch> so do I :)
[20:50] <jmarsden> :)  if I paid a little more I could get 20mbps up and down... I have not succumbed to that temptation yet 10 down and 2 up is plenty for now :)
[20:51] <warp10> jmarsden: ok, I'm starting to hate you :D
[20:57] <jmarsden> It's done with the download part of the pbuilder create already ...
[20:58] <warp10> jmarsden: If I had created the chroot, it would still downloading the package list right now. Don't know why, it is incredibly slow and lagged here. Network issues, probably
[20:58] <RoAkSoAx> heya guys how can I update the headers of a patch?
[20:59] <jmarsden> sounds like it.  There it's done, 547 seconds start to finish.
[20:59] <jmarsden> RoAkSoAx: If it uses quilt, use quilt refresh ?
[20:59] <RoAkSoAx> jmarsden, ok thanks:)
[21:00] <jmarsden> warp10: Hmmm, I'm guessing I have something bad in my .pbuilderrc .. the new one has the same behaviour the old one did regarding pbuilder-sid login
[21:01] <warp10> jmarsden: oh, too bad. Can't understand what's the problem could be
[21:02] <jmarsden> I'll get there... but this "quick test" isn't turning out as quick as you hoped... sorry about that :)
[21:03] <warp10> jmarsden: no problem, rather thank you for your helpfulness
[21:03] <jmarsden> Ah... it *is* a shell... just no prompt... echo $SHELL typed into the void gets me /bin/bash... now I need to figure out where the shell prompt went...
[21:04] <ajmitch> warp10: what was the vtk problem you were having anyway?
[21:04] <warp10> ajmitch: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529961
[21:04] <warp10> ajmitch: I have found that bug is still present on i386
[21:05] <ajmitch> ok
[21:05] <warp10> and I would like to know if the amd64 is really fixed. I would like to see it actually fixed ASAP, I can't merge mayavi2 without a working vtk
[21:05]  * ajmitch would check it out, but has to run out now for a bit :)
[21:06]  * jmarsden is trying to do the test in his somewhat impaired chroot shell... :)
[21:06] <jmarsden> at-get import python-vtk is bring in 47 other packages with it...
[21:06] <jmarsden> s/bring/bringing/
[21:07] <warp10> jmarsden: probably the whole python stuff and something more
[21:07] <jmarsden> Yes, lots of fonts and X libraries and so forth.  It's done now :)
[21:08] <jmarsden> warp10: test gets me a tracebackm last line of which is ImportError: No module named libvtkCommonPython
[21:09] <warp10> jmarsden: and now I'm wondering why the debian maintainer thinks his latest upload fixed this issue
[21:09] <warp10> jmarsden: thanks a lot for your time & bandwith, your help has been remarkable
[21:09] <jmarsden> Sorry, I can't help you with that question :)
[21:09] <jmarsden> No problem.
[21:10] <ajmitch> warp10: I can confirm it broken on i386 also
[21:11] <warp10> ajmitch: indeed. looks like there is a missing link
[21:31] <contrast> Greets, everyone...
[21:32] <contrast> Would someone here be so kind as to re-package GJay ( http://launchpadlibrarian.net/3400922/gjay_0.2.8.3-5_amd64.deb ) for Jaunty? The name of a library the package depends on has changed, and this is one of my favorite apps. :)
[21:39] <RoAkSoAx> jmarsden, when updating a patch header, should I specify it in the changelog??
[21:40] <jmarsden> I'm not a MOTU... I'd say yes, just to be safe -- but if you update 20 of them don't add 20 lines to the changelog :)
[21:41] <RoAkSoAx> jmarsden, haha k thanks :)
[21:41] <contrast> Sorry if this is the wrong place for making that kind of request, but could someone point me in the right direction?
[21:41] <jmarsden> contrast: The better way to request that would be to file a needs-packaging bug in launchpad, I think.
[21:42] <contrast> jmarsden: That's normally what I'd do, but this package was deleted from the repositories since it's no longer maintained (following Debian's lead).
[21:44] <vorian> contrast: it will still need a needs-packaging bug
[21:44] <contrast> jmarsden: It's a tiny change that needs to be made to the last version that was package - s/libgsl0/libgsl0ldbl/ in the control file - but I'm not sure how to do this while still maintaining the integrity of the package.
[21:44] <contrast> vorian: got cha. thanks for the heads up.
[21:44] <contrast> packaged*
[21:44] <jmarsden> contrast: Hmmm, then you need to find it a new maintainer, not just a one time update of an existing package... I'm not sure how best to proceed in that case... I'd be tempted to file the needs packaging bug anyway and indicate why you feel this is a useful package to have in Debian/Ubuntu
[21:45] <contrast> point taken... so would anyone here be interested in maintaining the package for the most amazing playlist creator ever? :P
[21:45] <contrast> j/k - i'm filing the report now.
[21:46] <RoAkSoAx> vorian, heya!! gotta question... if I updated the patch headers (quilt refresh patch.diff).. should I put that in the changelog
[21:47] <vorian> yes, put every-little-thing you change in the changelog (even if it's 20 patches)
[21:47] <vorian> but you could do it like
[21:47] <vorian> * frefresh patches:
[21:47] <vorian> - patch.1
[21:48] <vorian> - patch.2
[21:48] <vorian> so on, and so forth
[21:48] <RoAkSoAx> contrast, I think that package is not longer on debian either.. and it has been deprecated because it depends on xmms...
[21:48] <RoAkSoAx> vorian, ok cool thanks
[21:49] <jmarsden> vorian: Why not do:   * debian/patches/*: Refreshed all 20 patches      instead?
[21:49] <contrast> RoAkSoAx: yeah, that's kind of what i was thinking... this probably means it's not going to make it back into the official repos, right?
[21:49] <RoAkSoAx> contrast, right
[21:50] <vorian> depends
[21:50] <contrast> so umm... what now? :)
[21:52] <jmarsden> contrast: Looks like you'll need to find someone to package it and put it in a PPA for you, or learn packaging yourself so you can repackage it... see https://wiki.ubuntu.com/PackagingGuide/Complete
[21:53] <contrast> cool. thanks
[21:54] <jmarsden> No problem.
[21:55] <RoAkSoAx> contrast, or just download the source package, change add a jaunty entry on the changelog, and put it in a PPA
[21:56] <contrast> RoAkSoAx: tried that, couldn't get it to build after installing all dependencies
[21:56] <RoAkSoAx> contrast, why it would not build?? because of xmms i would guess...
[21:57] <contrast> nope, i installed xmms via a ppa. one sec, i'll try again and pastebin the output
[22:01] <RoAkSoAx> ok
[22:03] <contrast> http://pastebin.ca/1450088
[22:04] <contrast> i should note this is after applying the diff found here - https://launchpad.net/ubuntu/hardy/+source/gjay/0.2.8.3-5build1 - by running the command "patch -p1<../gjay_0.2.8.3-5build1.diff" in the orig directory.
[22:08] <RoAkSoAx> contrast, you would have to take a look in prefs.c line 338 and see why it's failing to build
[22:09] <contrast> yeah, tried that... given i'm not a programmer, it didn't help much. :P
[22:10] <RoAkSoAx> contrast, well what I  would try to do is download xmms and gjay from dapper, add a changelog entry from jaunty on each, and then try to build them
[22:11] <contrast> will do. thanks for the info.