[00:00] <wolfe> the scalies would all start using ubuntu for the name, heh
[00:00] <sistpoty> RainCT: I could try with fdupes for the moment... but not today though
[00:03]  * RainCT decides to do something productive and starts preparing the gnome-voice-control 0.3 package
[00:04] <RainCT> (well, if that can be considered productive :D)
[00:04] <sistpoty> go, fix some bugs :P
[00:10] <sistpoty> bdrung: mind to update recommends of audacity due to ffmpeg transition from *-unstripped-* to *-extra-*?
[00:11] <sistpoty> superm1: same for mythexport... ^^
[00:12] <prefrontal> sistpoty my vm has libglu1-mesa-dev and libglu1-xorg-dev
[00:13] <sistpoty> prefrontal: than compare that to pbuilder?
[00:14] <sistpoty> prefrontal: I assume only one of the two is getting drawn in
[00:15] <prefrontal> there is only one file in that package, and it is irrelevant.. http://packages.ubuntu.com/jaunty/all/libglu1-xorg-dev/filelist
[00:15] <prefrontal> oh, it depends on the mesa version.
[00:16] <prefrontal> i don't get all this mesa stuff - mesa is a software implementation of opengl... i suppose everything that needs opengl compiles against mesa, but then the actual implementation is provided by whatever opengl library is loaded into memory at runtime?
[00:16] <bdrung> sistpoty: http://git.debian.org/?p=pkg-multimedia/audacity.git;a=commitdiff;h=a2700651beb136c291d0852a6ab6c4d5faa8feaf and https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/423801
[00:16] <ubottu> Ubuntu bug 423801 in audacity "Sync audacity 1.3.9-1 (universe) from Debian unstable (main)." [Wishlist,New]
[00:18] <sistpoty> bdrung: oh, nice, thanks!
[00:19] <bdrung> np
[00:20] <bdrung> sistpoty: bug #423845 needs to be fixed before the sync
[00:20] <ubottu> Launchpad bug 423845 in wxwidgets "conflict with glib 2.21 in GSocket" [Unknown,Fix released] https://launchpad.net/bugs/423845
[00:21] <sistpoty> bdrung: yep, just read it... I'll eventually upload this, but I guess not before tomorrow (since I don't want to look at wx being tired)
[00:22] <bdrung> :)
[00:47] <LaserJock> kinda quiet around here, everybody off for the weekend?
=== funkyHat is now known as splatHat
[00:49] <sistpoty> hey LaserJock
[00:49] <sistpoty> LaserJock: how are you?
[00:50] <LaserJock> sistpoty: hi! doing pretty good
[00:51] <sistpoty> LaserJock: cool! Dr. Laserjock ;)
[00:51] <LaserJock> I finished my PhD, got a job near Boston, and moved clear across the US (3,500 miles), all in ~ 1 month
[00:51] <sistpoty> wow
[00:52] <sistpoty> LaserJock: have you heard, that we (as in motu-release) would like to see you as a delegate for edubuntu again?
[00:52] <LaserJock> ah, I did see that email. I was going to reply, but got a little side-tracked
[00:52] <LaserJock> I think I'm fine with doing that
[00:53] <sistpoty> cool, excellent :)
[00:53] <LaserJock> I'm not sure yet how involved I'm going to be given my job, but I think I can do the delegation OK
[00:53] <LaserJock> I'd even like to get back into MOTU a bit if I can
[00:53] <sistpoty> and now, where are you're working at?
[00:54] <LaserJock> I'm a bit rusty with all the policies
[00:54] <sistpoty> heh
[00:54] <LaserJock> I'm working at the Air Force Research Laboratory
[00:54] <LaserJock> at the Hanscom Air Force Base
[00:54] <LaserJock> I'm sort of officially a rocket scientist now ;-)
[00:54] <sistpoty> woohoo... I assume I mustn't ask further then :P
[00:54] <sistpoty> heh
[00:55] <LaserJock> I'm honestly not sure how much I can and can't say
[00:55] <LaserJock> it's nothing secret, but you never know with these military types :-)
[00:55] <sistpoty> hehe
[00:55] <sistpoty> are you involved in these stargate missions, LaserJock? :P
[00:55] <LaserJock> heh
[00:56] <shriekout> oh
[00:56] <LaserJock> I'm in space vehicles
[00:56] <shriekout> stargate!
[00:56] <LaserJock> no stargates for me
[00:56] <LaserJock> I'm just a chemist
[00:56] <sistpoty> :( *g*
[00:56] <sistpoty> that's what they all say *g*
[00:56] <LaserJock> of course ;-)
[00:57] <LaserJock> the paperwork is tremendous
[00:57] <sistpoty> oh boy
[00:57] <LaserJock> I'm really starting to wonder how the military can possibly *do* anything
[00:58] <LaserJock> took me almost a month to get the badge to get on the base
[00:58] <LaserJock> I still don't have official computer access
[00:58] <LaserJock> and I *have* to run windows :(
[00:58] <RainCT> And I thought the military is something serious.. :P
[00:58] <sistpoty> haha
[00:59] <LaserJock> I wondered what would happen if I reformated one of there computers and put Ubuntu on it
[00:59] <LaserJock> I'd probably go to the firing squad :-)
[01:00] <sistpoty> or they wouldn't notice if you use kde :P
[01:01] <LaserJock> even worse than Windows is I have to use Outlook
[01:07] <LaserJock> so, how is MOTU handling the archive reorganization?
[01:08] <sistpoty> well, it's not there yet
[01:09] <sistpoty> but afaik many MOTUs have voted to be generalists... I can only speculate what that means for archive reorg
[01:11] <LaserJock> that should give them all-but-seeded-packages upload access I'd think
[01:32] <RainCT> dyfet`: Uhm.. I can't get 0.3 to build. The version from SVN (which has recent changes, unlike 0.3 which is from 2007) works though
[01:33] <RainCT> (well, the recognition accuracy is *awful*, but I guess I need to tweak my settings a bit more)
[01:34] <RainCT> (uhm.. if I shout it gets better :P)
=== warner is now known as warner_afk
[02:57] <trip0> my package has multiple .so library files.  what's the right way to specify 'version' and 'major' for them?
[02:57] <trip0> in the rules file...
=== s8n is now known as vorian
[04:31] <ripps> Hello, I'm the maintainer of the gmpc-trunk ppa, and I was wondering if it would be possible to give gmpc-0.19 a freeze exception? It's gonna be released in a week or two and I was wondering how likely it was.
[04:36] <ScottK> ripps: As long as it's well tested and seems reasonable, it's quite possible.  We're fairly early in feature freeze at this point.  No guarantees.
[04:37] <ripps> Well, the version to be released should be pretty similar to the git version in my ppa. It's been in freeze for about 2 weeks and I've heard very little problems with it.
[04:42] <ScottK> Then I'd suggest file for an FFe after the release and we'll look at it.
=== keylocker is now known as leleobhz
[06:00] <_theWarrior> hello everyone
[06:02] <_theWarrior> i want to get involved in the ubuntu pkg management and got to know about motu through one of my friends...i would like to know about the basic knowledge one should have to get involved and the minimum amount of time one is supposed to spend for that, I can spend 6/8 hrs per week...
[06:03] <ScottK> You can spend as little or as much as you want.
[06:05] <_theWarrior> ScottK, thank you...can you provide me some links to get started my self with the basic knowledge....i've partially gone through the ubuntu motu wiki pages....
[06:05] <ScottK> That's the best place to start.
[06:05] <ScottK> !development
[06:05] <ubottu> Interested in becoming an Ubuntu Developer? Get started here: https://wiki.ubuntu.com/UbuntuDevelopment
[06:05] <ScottK> _theWarrior: ^^
[06:06] <RoAkSoAx> ScottK, let me ask you something.. don't you ever sleep?? :)
[06:07] <_theWarrior> thank you, ScottK
[06:07] <ScottK> RoAkSoAx: I do every now and then.
[06:07] <RoAkSoAx> ScottK, I always see you around... :)
=== leleobhz is now known as metilfenidato
=== ejat is now known as e-jat
=== e-jat is now known as ejat
=== jussi01 is now known as _
=== _ is now known as jussi01
[10:30] <LLStarks> hi
[10:30] <LLStarks> we have a serious packaging problem for python-zope-interface
[10:30] <LLStarks> other packages like python-lazr-restfulclient are looking for it
[10:30] <LLStarks> but the actual package is python-zope.interface
[10:34] <geser> python-zope-interface is provided by python-zopeinterface (main)
[10:34] <geser> but there is also a python-zope.interface in universe
[10:36] <hyperair> python-zope.interface should provide python-zope-interface as well, imo
[10:37] <hyperair> or not. maybe it's the other way round.. packages should be depending on python-zopeinterface rather than python-zope-interface
[10:38] <geser> I don't know the current (and future) naming policy for the zope.* packages so can't tell which package should depend on what name
[10:38] <geser> but I guess the zope.* names are the current one
[10:39] <LLStarks> https://bugs.launchpad.net/ubuntu/+source/python-launchpadlib/+bug/424751
[10:39] <ubottu> Ubuntu bug 424751 in zope.interface "python-zope.interface package is sometimes mistakenly called python-zope-interface" [Undecided,New]
[10:39] <LLStarks> here's the bug
[10:39] <LLStarks> python-apport has been un-updateable for over a week
[10:40] <LLStarks> unless you use python-zopeinterface
[10:40] <geser> what error do you get exactly as the bug doesn't mention it
[10:41] <geser> I had no problem to upgrade python-launchpadlib
[10:41] <LLStarks> no error
[10:41] <LLStarks> python-apport can't be updated
[10:41] <LLStarks> ignore the url labeling of python-launchpadlib
[10:42] <LLStarks> here: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/424751
[10:42] <ubottu> Ubuntu bug 424751 in zope.interface "python-zope.interface package is sometimes mistakenly called python-zope-interface" [Undecided,New]
[10:42] <LLStarks> better?
[10:42] <LLStarks> python-zope.interface dependency is sometimes mistakenly called python-zope-interface
[10:42] <geser> what happens if you try it?
[10:43] <LLStarks> try what? using python-zopeinterface?
[10:43] <LLStarks> it'll upgrade.
[10:43] <LLStarks> the python-apport package
[10:43] <geser> upgrading python-apport
[10:43] <LLStarks> yeah, but it was stuck for over a week
[10:43] <geser> stuck?
[10:43] <LLStarks> version stuck
[10:43] <LLStarks> and this was a fresh install
[10:44] <geser> I still don't understand the actual problem you have
[10:44] <LLStarks> python-apport updates were held back
[10:44] <LLStarks> because of the python-zope-interface conflict
[10:45] <LLStarks> launchpadlib, restfulclient, and the like were also affected
[10:45] <LLStarks> if i tried to update python-apport, it would throw a conflict in those packages
[10:45] <geser> ah, you have python-zope.interface installed because an other package needed it?
[10:46] <LLStarks> no
[10:46] <LLStarks> that's how the alphas were shipped
[10:46] <LLStarks> with a broken zope-interface setup
[10:46] <geser> can't believe it
[10:46] <LLStarks> the error cascade in synaptic was like this
[10:47] <LLStarks> python-apport > launchpadlib > restfulclient > zope.interface
[10:47] <geser> I've tried installing python-apport in my karmic pbuilder and it worked fine
[10:47] <LLStarks> we'll your setup is lying
[10:48] <LLStarks> i had to uninstall python-zope.interface and install python-zopeinterface to upgrade python-apport
[10:48] <LLStarks> and python-zope.interface was installed by default.
[10:49] <kwadronaut> i know about the karmic freeze, but i couldn't find the answer: upstream released a security fix (+other bugfixes), would it be ok to bump the package?
[10:49] <geser> that would be an interesting error as python-zope.interface is in universe
[10:49] <kwadronaut> or does it require a debdiff and only fix the security issue?
[10:49] <LLStarks> well, that's how it was
[10:50] <geser> kwadronaut: it's still possible to upgrade the package, and given that it's only bug-fixes no feature freeze exception is needed (but check the changes if that's the case)
[10:50] <LLStarks> earlier this week i fresh-installed from my jaunty liveusb and reupgraded to karmic since usb-creator was busted as of a few days ago due to an inability to use iso files with the new devicekit backend.
[10:51] <geser> which alpha do you use?
[10:51] <LLStarks> upgrade-manager -d
[10:51] <LLStarks> python-apport was never upgraded
[10:52] <LLStarks> or it was, but a lesser version
[10:52] <LLStarks> and then version-locked
[10:53] <LLStarks> at 1.5-0ubuntu2
[10:53] <geser> which alpha did you test to get this problem as I don't have it on my system (the python-zope-interface one)?
[10:53] <LLStarks> what do you mean?
[10:54] <kwadronaut> geser: thanks for the info. I'm not the maintainer of the package in question though, could you point me to documentation on how to proceed?
[10:54] <LLStarks> i went from jaunty release to karmic current
[10:54] <kwadronaut> i could package it, but where should i dump it then..
[10:54] <LLStarks> i've been using karmic for months though
[10:54] <LLStarks> i did a reinstall last week
[10:55] <geser> kwadronaut: https://wiki.ubuntu.com/PackagingGuide/Recipes/PackageUpdate should be a good start
[10:55] <kwadronaut> thanks
[10:56] <geser> LLStarks: just I understand it correctly: you did a fresh install of jaunty and upgraded it to karmic?
[10:56] <LLStarks> yes
[10:56] <LLStarks> BUT ONLY BECAUSE I COULDN'T MAKE A KARMIC LIVEUSB
[10:57] <LLStarks> usb-creator was busted
[10:57] <LLStarks> and it still is
[10:59] <geser> and after the upgrade from jaunty to karmic you had python-zope.interface installed (instead of python-zope-interface)?
[10:59] <LLStarks> apparently
[11:01] <geser> I assume some of the upgraded packages pulled it in through recommends
[11:04] <LLStarks> i don't know
=== Kmos_ is now known as Kmos
=== Kmos is now known as Guest14733
[11:11] <LLStarks> geser, unrelated note. why is gparted default for live but optional for install?
[11:13] <geser> sorry don't know
=== Guest14733 is now known as Kmos
[11:42] <christoph_debian> heya all! I don't need a FFe for a new debian/ubunt revision? would it be possible to sync linux-libertine -2 or -3 from debian to fix lp bugs 421550 200204 ? If so I'll fill a sync request after rebuilding on karmic
[11:42] <ubottu> Launchpad bug 421550 in linux-libertine "[Karmic] Linux Libertine fonts wrongly defined/set up" [Undecided,New] https://launchpad.net/bugs/421550
[11:43] <sebner> christoph_debian: shouldn't need a FFe since it's -2 and -3
[11:44] <sebner> christoph_debian: yeah, doesn't need a FFe, just checked
[11:45] <christoph_debian> ok just filling a sync request then
[11:47] <christoph_debian> -3 is a maintainer change so -2 would be ideal but I doubt you can sync something that is no longer in unstable
[11:48] <christoph_debian> and it won't hurt
[11:49] <sebner> christoph_debian: syncs get the newest version automatically
[11:53] <christoph_debian> jep it's not a problem anyway I think
[11:59] <christoph_debian> sebner: done 424772
[12:23] <sebner> christoph_debian: ACKed, if the sync is processed and really fixes the issue please close the specific bug report
[12:24] <christoph_debian> sure :) thanks
[12:24] <sebner> welcome :)
[12:48] <geser> anyone from ~motu-release around?
[12:48] <AnAnt> seems that Debian is considering to use upstart :)
[12:49]  * christoph_debian wants to see all the flames on d-devel@
[12:50] <AnAnt> flames ?
[12:51] <geser> iulian, nhandler, ScottK, vorian: do I need a FFe for this http://paste.ubuntu.com/265525/ ?
[12:53] <c_korn> is there a way to find the build dependencies for a python package ? like checking the configure.ac for autoconf based build systems ?
[12:54] <mzz> assuming distutils: anything setup.py imports needs to be there at build time (recursively)
[12:54] <mzz> I don't know of a convenient way to check for that (grep isn't all that convenient but may suffice)
[12:55] <mzz> oh, and also any -dev packages it needs if it builds extensions
[12:56] <mzz> (again setup.py is where you'd look for those)
[12:58] <c_korn> mzz: ok, thanks.
[13:03] <doctormo> Hey, if there is an up to date package in debian, what's the best way to a) check to see what version is in karmic and b) pull from debian to upload to my own ppa for ubuntu?
[13:04] <kwadronaut> or maybe you should request a sync?
[13:08] <AnAnt> doctormo: rmadison -u debian <source package name>
[13:10] <doctormo> AnAnt: does that work for ubuntu too?
[13:10] <doctormo> kwadronaut: Can I have a sync please?
[13:10] <AnAnt> doctormo: oh, if you want to check the latest in ubuntu, just drop the '-u debian'
[13:11] <doctormo> Great, looks up to date in karmic, job done
[13:11] <AnAnt> doctormo: the only way that I know for pulling from debian, is find the package on packages.debian.org, then dget <url of dsc file>
[13:12] <doctormo> AnAnt: Yes that sounds familar
[13:13] <AnAnt> doctormo: maybe there's something better in devscripts
[13:14] <porthose> ubuntu-dev-tools  'pull-debian-source <package name>"
[13:16] <AnAnt> porthose: thanks !
[13:16] <porthose> np you can also pull-lp-source :)
[13:17] <iulian> geser: Yes, because of strip_versions.  Please file a bug if you didn't already and subscribe motu-release.  As far as I can see, a few vulnerabilities have been fixed. You'll surely get an exception.
[13:17] <iulian> geser: Please ping me with the bug # and I'll ack it.
[13:20] <AnAnt> cool
[13:36] <iulian> Who is Artur Rona?
[13:38] <iulian> i.e. what is his nickname?
[13:50] <ScottK> geser: +1 from me based on the changelog (feel free to put that in the bug when you write it).
[13:55] <RoAkSoAx> morning
[13:59] <moldy> hi
[13:59] <randomaction> iulian: https://launchpad.net/~ari-tczew
[14:00] <moldy> hi
[14:00] <moldy> while trying to upload to my ppa, i am having trouble with his error: File <UPLOADED_FILE> already exists in <LOCATION>, but uploaded version has different contents.
[14:01] <zooko> Good morning, folks! (UTC-6)
[14:16] <moldy> hey zooko
[14:19] <geser> iulian, ScottK: bug #424820
[14:19] <ubottu> Launchpad bug 424820 in zodb "[FFe] Update zodb to 1:3.8.3-1 from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/424820
[14:21] <iulian> geser: Approved.
[14:40] <c_korn> if a python package based on setuptools as build system does not have --prefix or --destdir support is it better to patch the setup script to support those arguments or to just install everything manually using the install files in the debian directory ?
[14:43] <POX> c_korn: --root is DESTDIR equivalent and --prefix for PREFIX
[14:45] <POX> c_korn: ./setup.py --help install
[14:45] <c_korn> --root is also not known: python setup.py --root=$(CURDIR)/debian/python-tpprotolib install this gives: "error: option --root not recognized"
[14:45] <iulian> RainCT: Could you please take another look at python-zfec (http://revu.ubuntuwire.com/p/zfec) and advocate if OK?  My knowledge about Python packaging is at a low level, unfortunately.
[14:45] <POX> c_korn: you're missing "install"
[14:45] <POX> take a look at random DPMT / PAPT package
[14:47] <c_korn> POX: oh, the order of the arguments are important: I did "setup.py --root=$(CURDIR)/debian/python-tpprotolib install" instead of "setup.py install --root=$(CURDIR)/debian/python-tpprotolib"
[14:47] <c_korn> POX: thank you.
[14:48] <RainCT> iulian: Sure. Why is it still on REVU though, was it rejected?
[14:48] <RainCT> ah I see
[14:50] <POX> RainCT: force iulian to do it via DPMT (zooko will be happy :)
[14:52] <iulian> :)
[14:53] <loic-m> btw, RainCT, shouldn't gnome-scan be removed from REVU/Needs Work?
[14:54] <loic-m> It's been renamed as gnomescan and the version uploaded is in Karmic now
[14:54] <RainCT> loic-m: yeah, archived it
[14:56] <loic-m> thanks RainCT
[14:56] <RainCT> iulian: Looks good to me.
[14:58] <RainCT> iulian: If you're in reviewer mood, http://revu.ubuntuwire.com/p/pocketsphinx is looking for reviews :).   (there's a pending FFe for it)
[15:15] <iulian> RainCT: OK, thank you.  I'll take a look at pocketsphinx later on.
=== asac__ is now known as asac
=== metilfenidato is now known as leleobhz
=== splatHat is now known as funkyHat
[16:24] <moldy> argh argh argh, launchpad is driving me crazy
[16:44] <geser> why?
=== keylocker is now known as leleobhz
[18:52] <pace_t_zulu> hey guys ... is it too late to sync a package from squeeze?
[18:54] <Laney> depends what for
[18:54] <pace_t_zulu> open-vm-tools
[18:55] <pace_t_zulu> karmic version is 2009.07.22-179896-2
[18:56] <pace_t_zulu> squeeze version is 2009.08.24-187411-1
[18:56] <pace_t_zulu> should i file a bug?
[18:57] <Laney> depends for what reason
[18:57] <pace_t_zulu> new version?
[18:57] <geser> we are in Feature Freeze
[18:58] <geser> so you should have a better reason than just "new version", e.g. important bug fixes, security fixes, etc.
[19:14] <pace_t_zulu> geser, i'll build the new version and put it on my ppa... see if it fixes some issues i'm experiencing
[19:14] <pace_t_zulu> Laney and geser, ty
[19:38] <pace_t_zulu> is there a problem with debian's git repository?
[19:38] <pace_t_zulu> http://git.debian.net/?p=debian/open-vm-tools.git
[19:40] <DktrKranz> pace_t_zulu: that package has been moved, http://git.debian-maintainers.org/?p=vmware/open-vm-tools.git
[19:41] <pace_t_zulu> DktrKranz: ty ... would be nice if that had been noted
[19:41] <DktrKranz> It has been in recent upload in Debian, I guess it hasn't been synced in Ubuntu yet
[19:48] <pace_t_zulu> would that be a reason to sync with the squeeze version for karmic? to prevent confusion?
[19:53] <pochu> pace_t_zulu: no, you gotta check if the new version introduces new features, and if so you need an exception
[19:54] <pace_t_zulu> pochu: ty
[19:54] <pochu> pace_t_zulu: see if there's an upstream ChangeLog or NEWS file and see what changed
[19:56] <pace_t_zulu> pochu: http://paste.ubuntu.com/265702/ ... the NEWS file
[19:59] <DktrKranz> pace_t_zulu: it seems it provides some new features, so an exception is required. See wiki.ubuntu.com/FreezeExceptionProcess
[19:59] <pace_t_zulu> pochu: http://paste.ubuntu.com/265704/ ... the ChangeLog file
[19:59] <pace_t_zulu> DktrKranz: ty
[20:17] <dhillon-v101> hi everyone
[20:18] <pace_t_zulu> hi dhillon-v101
[20:18] <dhillon-v101> pace_t_zulu: how are you
[20:19] <pace_t_zulu> dhillon-v101: ok... trying to work out an issue where my karmic VM doesn't sync with the host
[20:19] <pace_t_zulu> think a bug report might be in order
[20:19] <dhillon-v101> pace_t_zulu: ah, I am new to this place but I have read about MOTU
[20:20] <pace_t_zulu> dhillon-v101: welcome... ubuntu is a great community
[20:20] <pace_t_zulu> much friendlier than freebsd or opensolaris... in my experience
[20:20] <dhillon-v101> pace_t_zulu: oh I have been working with the ubuntu-doc team for a while now and yah it is really friendly
[20:21] <dhillon-v101> pace_t_zulu: can you get me started here
[20:31] <dhillon-v101> pace_t_zulu: are you there
[20:31] <pace_t_zulu> dhillon-v101: yes
[20:31] <pace_t_zulu> dhillon-v101: sorry... didn't see your last msg
[20:32] <dhillon-v101> pace_t_zulu: that's okay so can you get me started
=== dyfet` is now known as dyfet
[20:32] <pace_t_zulu> dhillon-v101: sure... here is an excellent video... http://www.youtube.com/watch?v=VyEl3w7SFK4
[20:33] <dhillon-v101> I have seen those before
[20:33] <pace_t_zulu> dhillon-v101: and here is a good wiki page https://wiki.ubuntu.com/MOTU/GettingStarted
[20:33] <pace_t_zulu> dhillon-v101: i'm not a motu btw
[20:33] <dhillon-v101> alright I will look at it
[20:33] <dhillon-v101> so how can I help here
[20:34] <pace_t_zulu> dhillon-v101: if you figure that out... let me know... i'm still trying to work that out myself
[20:34] <dhillon-v101> :)
[20:34] <ScottK> It depends a lot on what your interests and experience are.
[20:37] <ScottK> LucidFox: I have what I think is a qconf problem and I see your name in the copyright for the script in question.  I'd appreciate a spot of help if you are willing?
[20:39] <LucidFox> ScottK> That's weird... I'm not an author of qconf
[20:39] <ScottK> LucidFox: You show up in the qink qconf scripts.
[20:39] <LucidFox> Or perhaps it is qink?
[20:39] <ScottK> It is
[20:39] <LucidFox> Yes, right :)
[20:39] <LucidFox> I wrote that
[20:40] <ScottK> Ah.  Perhaps you could look at why it can't find liblinklevel on several archs.
[20:40] <ScottK> https://launchpad.net/ubuntu/+source/qink/0.3.5-2build1
[20:40] <ScottK> LucidFox: I built it in my PPA with dephelper in verbose mode.  Here's the log for amd64: https://launchpad.net/~kitterman/+archive/ppa/+build/1204291/+files/buildlog_ubuntu-karmic-amd64.qink_0.3.5-2build1+ppa2_FAILEDTOBUILD.txt.gz
[20:41] <ScottK> Currently libinklevel4 is NBS and the build failures are blocking it from being removed from the archive.
[20:42] <ScottK> My guess from the other archs is that if configure would succeed then the builds would work.
[20:44] <LucidFox> To be frank, perhaps it would be better to remove qink. I stopped developing it, and there are better alternatives.
[20:44] <LucidFox> Such as inq.
[20:47] <ScottK> If it's dead upstream, that's a reasonable position.
[20:48] <LucidFox> I am upstream. :)
[20:50] <ScottK> Right, so if you think it should be removed, then please file a removal bug.
[20:50] <ScottK> You might also do the same with Debian.
[20:52] <trip0> what's the best way to package a qmake based project?
[20:52] <pace_t_zulu> any vmware users in here?
[20:53] <runasand> pace_t_zulu: yeah
[20:54] <trip0> i don't think dh_make understands qmake...
[20:54] <pace_t_zulu> runasand: do you use open-vm-tools?
[21:05] <LucidFox> CDBS has a qmake class
[21:05] <LucidFox> but not qconf
[21:05] <LucidFox> qconf is similar to autoconf in terms of invocation, though
[21:06] <LucidFox> ScottK> I'll file the removal request then.
[21:26] <pace_t_zulu> reporting a bug in debian seems like a pain in the ass
[21:27] <binarymutant> pace_t_zulu, it is, unless you use reportbug :D
[21:31] <pace_t_zulu> binarymutant: on it
[21:31] <kwadronaut> hmmm 'Since Debian Policy 3.8.0, embedded code copy are officially not allowed in Debian anymore.[snip] has been discontinued.' is that a problem for ubuntu?
[21:31] <pace_t_zulu> binarymutant: who the hell are you anyway :P
[22:04] <AnAnt> Hello, is Rolf Leggewie here ?
[22:06] <ScottK> kwadronaut: Yes.  That's a problem for Ubuntu.  We don't like code copies either.
[22:09] <kwadronaut> ScottK: aha. it is gpl 2 code, included in a different package which has other functionality. Should i request removal, or only file a bug against that problem?
[22:10] <ScottK> kwadronaut: File a bug.  The ideal would be to teach it to use the external library.
[22:10] <RainCT> didrocks: I guess you already know by now but quickly is failing on postinst here, syntax error in quicklyconfig.py ("__version__ = 0.2.1" is wrong, converting 0.2.1 into a string fixes it)
[22:11] <didrocks> RainCT: yes, 0.2.2 is now released :)
[22:11] <didrocks> RainCT: I got catch by some automation that replaces variables during executing setup.py :/
[22:11] <kwadronaut> ScottK: thanks. That would mean writing an external library :-/
[22:11] <ScottK> kwadronaut: Well what's the code a copy from?
[22:12] <ScottK> If there are two packages with copies of the same code, then it should be split out and they should both use it.
[22:13] <kwadronaut> ScottK: that's not likely to happen. it's about silc-client and irssi.
[22:14] <ScottK> Ah.
[22:14] <ScottK> Well file the bug anyway.  Maybe someone will get motiviate.
[22:19] <AnAnt> what is "embedded code copy" ?
[22:38] <kwadronaut> AnAnt: i think it refers to the chapter of convenience copies of code
[22:39] <kwadronaut> (referring to debian-policy)
[22:40] <AnAnt> oh, I found it
[22:40] <AnAnt> kwadronaut: thanks
[22:41] <AnAnt> ok, let's say that there are two packages: covered & verilog
[22:41] <AnAnt> both packages have those files in their source: lxt2_read.c & lxt2_write.c
[22:41] <AnAnt> is that too a problem ?
[22:43] <kwadronaut> i'm not the right person to judge that, i'm just a simple user
[22:46] <AnAnt> ok
[22:47] <AnAnt> am I supposed to put up with this sort of conduct (even if I had done a mistake) LP 375148 ?
[22:47] <ubottu> Launchpad bug 375148 in sl-modem "no more /dev/ttySL0 device node" [Medium,Confirmed] https://launchpad.net/bugs/375148
[22:48] <AnAnt> am I asking in the proper channel ?
[22:48]  * ScottK looks
[23:03] <ScottK> AnAnt: I made a comment in the bug.
[23:03] <AnAnt> thanks
[23:05] <AnAnt> superm1: Hello, dkms in jaunty used to accept pushd & popd, and not work with cd, yet in karmic it is the opposite. Why's that  ? I tried to figure out from the changelog if there is any mention of it, but there wasn't
[23:23] <AnAnt> ok, it's late here
[23:23] <AnAnt> bye