[00:33] <LaserJock> anybody offhand know the syntax for doing a "if previous package version is less than <current version> then run this" for a postinst?
[00:57] <TheMuso> LaserJock: an example from pulseaudio: dpkg --compare-versions "$2" lt-nl "0.9.14-0ubuntu9"; then
[00:57] <TheMuso> so if dpkg --compare-versions "$2" lt-nl "0.9.14-0ubuntu9"; then; then
[00:58] <LaserJock> TheMuso: 2 then's?
[00:58] <TheMuso> LaserJock: no
[00:58] <TheMuso> sorry meant one
[00:58] <TheMuso> I didn't realise I copied the then
[00:58] <LaserJock> k, I was just making sure I wasn't going insane
[01:06] <LaserJock> is that the only way to tell if a package is being upgraded as opposed to a new install?
[01:16] <TheMuso> LaserJock: There is checking what is passed to the script in $1
[01:17] <TheMuso> I think that can help some
[01:23] <leonel> can someone check  bug 446838  if I've did the diffs  correct ??
[02:35] <ScottK> zul: What's the story about ebox-dhcp?  Do you have an archive admin who will review it (I can't promise to have time)?
[02:57] <zul> ScottK: Im not exactly sure what happened with it, I thought I uploaded it
[03:02] <zul> ScottK: I got it now Im going to upload it
[04:12] <kirkland> okay it's late
[04:12] <kirkland> someone help me
[04:13] <kirkland> what's the recipe for moving a file from one package to another, when both packages are going to be installed at the same time on the same system
[04:13] <kirkland> conflicts/replaces i know
[04:13] <kirkland> more detail please
[04:39] <ScottK> kirkland: Replaces: kdebase-workspace-bin (<= 4:4.1.82-1) and Conflicts: kdebase-workspace-bin (<< 4:4.1.82) would be an example.
[04:39] <kirkland> ScottK: thanks muchly
[04:40] <ScottK> Note I edited that and they don't match exactlyu
[04:52] <superm1> ScottK, would you mind looking over bug 432669?  I'm getting some questions already from people about it
[04:57] <ScottK> superm1: How useful is this package outside Mythbuntu?
[04:57] <wrapster> apart from dpkg -S and apt-cache search is there any other way to find out info about the location of a particular file and see in which pkg it exists?
[04:58] <superm1> ScottK, afaik, only useful in media center boxes
[04:58] <superm1> so maybe it really should just be our call
[04:58] <ScottK> superm1: I'd say you're call with your Mythbuntu hat then.
[04:58] <superm1> ScottK, okay thanks
[07:07] <fabrice_sp> Hi. Is dbus supposed to work in a chroot? I've just installed a package, and I'm getting "dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.apertium.info was not provided by any .service files" but the service file exists...
[07:39] <dholbach> good morning
[07:47] <MTecknology> dholbach: G'MORNING!!
[07:47] <dholbach> hi MTecknology
[07:47] <MTecknology> dholbach: you should join me in my quest
[07:47] <dholbach> should I? :)
[07:48] <MTecknology> I'm trying to compile an Ubuntu kernel that's less than 2.5MB, prefere 2.1
[07:48] <MTecknology> but still giving me a fully usable system
[07:48] <dholbach> no no no no no no no
[07:48] <MTecknology> yes?
[07:48] <dholbach> I stopped building kernels like 5-6 years ago
[07:48] <dholbach> I'm happy thanks :)
[07:48] <MTecknology> :P
[07:49] <MTecknology> so far my .config is ~50% the ubuntu .config
[07:49] <MTecknology> but - I don't have ext2,3, btrfs, etc. support. Only ntfs, fat, and ext4
[07:51] <dholbach> good luck
[07:53] <MTecknology> :P - thanks
[07:54] <MTecknology> Do you know if there's much difference between vanilla kernel and ubuntu kernel branches aside from .configs?
[09:41] <leaf-sheep> Hello, I'm wondering if I can request for a package to be updated? It have been long time since it got updated.
[09:41] <azeem> is it updated in Debian?
[09:42] <leaf-sheep> azeem: I don't know. I'll try and find out.
[09:43] <leaf-sheep> azeem: Ubuntu + Debian --> Same package version.  I'm talking about the package -- cgoban
[09:44] <wrapster> i have a tar file which contains only libraries that needs to sit in the /usr/include dir...
[09:44] <wrapster> using this can i create a .deb pkg?
[09:44] <wrapster> its urgent could you please help me?
[09:45] <azeem> libraries don't sit in /usr/include
[09:48] <leaf-sheep> azeem: http://www.gokgs.com/download.jsp
[09:49] <leaf-sheep> azeem: It's at 3.3.26 -- I take it that it won't be updated until Debain do that?
[09:51] <azeem> leaf-sheep: well, if it was updated in Debian, it would automatically get updated in Ubuntu once karmic is released
[09:52] <leaf-sheep> azeem: Is there a particular debian-motu channel that I can request in?
[09:53] <azeem> no, you can file a wishlist bug in the Debian bug tracker after checking whether there is one already
[09:54] <leaf-sheep> azeem: I see. I'll do that.  Thank you. :)
[09:54] <wrapster> azeem: sorry ... its header files.
[09:55] <wrapster> this tarball only contains headerfiles that need to be in the above metioned dir.. i have a tar ball of it.. how can i create a pkg out of it..
[09:55] <wrapster> how do i use the debhelper scripts?
[11:11] <wrapster> whys is it that mkdir -p debian/mpsnexenta/usr/include/mps
[11:11] <wrapster>         tar -C debian/mpsnexenta/usr/include/mps -zxf ../mps.tar.gz
[11:12] <wrapster> if included in the rules file is creating something like this /usr/include/mps/usr/include/mps/
[11:15] <walterl> hi
[11:15] <walterl> python packagers: have anyone else run into the problem of data files being installed in dist-packages and source being installed in site-packages, causing pbuilder build to barf?
[11:31] <geser> wrapster: do the files inside your mps.tar.gz contain a path?
[11:31] <wrapster> geser: yeah.. and i resolved it.
[11:31] <wrapster> geser: that was infact the issue
[11:56] <sebner> huhu mok0 sistpoty|work :D
[11:56] <sistpoty|work> hi sebner
[12:11] <norax_> I am trying to look for a FTBFS bug, but http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20090909-karmic.html seems fallen. Any other list?
[12:13] <norax_> ok. http://qa.ubuntuwire.com/ftbfs/  I hadn't seen the topic.
[12:15] <wgrant> norax_: Sorry - the Launchpad issues earlier made it a bit angry. Fixing now.
[12:23] <wekt> where do bug reports on the 'alternative' debian install program go?  package debian-installer seems to be something different according to the description.
[12:27] <dholbach> wekt: that depends on which part of it is failing - the people in #ubuntu-installer will know
[12:28] <wekt> i think that puts me 1 step closer
[12:41] <LordMetroid> Why was ibus choosen?
[12:41] <LordMetroid> It lacks functionality, the katakana, hiragana, romaji change key for once doesn't seem to work
[12:42] <LordMetroid> Hmm, maybe I am at the wrong place for these comments
[13:17] <james_w> ScottK: did you decide on a date for final freeze for universe?
[13:18] <james_w> ScottK: if so then I think announcing it on the list would be a good idea to alleviate some panic today :-)
[13:18] <james_w> (apologies if you have and I missed it)
[13:18] <directhex> give me until this evening - banshee 1.5.1 is finally out ;)
[13:23] <ScottK> james_w: Good suggestion.  It'll be after the RC is out, so no need for people to panic.  I need to email the other motu-release people and get the exact time decided.
[13:23] <james_w> ScottK: great, thanks
[13:41] <sistpoty|work> ScottK: how about somewhen around 25th?
[13:42] <siretart`> is that the release date?
[13:42] <sistpoty|work> siretart`: no, release is 29th
[13:42] <siretart`> oh, ok
[13:43] <sistpoty|work> finalfreeze is just needing an ACK for each upload
[13:45] <bdrung_> sistpoty|work: from whom?
[13:46] <sistpoty|work> bdrung_: universe: motu-release
[13:47] <bdrung_> sistpoty|work: i wanted to hear irc nick names. :) seams so that you are on the list
[13:48] <sistpoty|work> bdrung_: that would be ScottK, iulian, vorian, nhandler and myself
[13:49] <bdrung_> sistpoty|work: eclipse-cdt is totally outdated and does not work. is it possible to upload a new upstream release after final freeze?
[13:49] <siretart`> bdrung_: do you manage to have a look at the mplayer-skin mess?
[13:50] <bdrung_> siretart: sorry, no. maybe it works if mplayer-skins provides mplayer-skin (note: missing s)
[13:50] <bdrung_> siretart: rl and eclipse consumes too much time.
[13:51] <sistpoty|work> bdrung_: I must admit that I'd prefer to have it done before final freeze (universe isn't final frozen yet)
[13:52] <bdrung_> sistpoty|work: there is only one problem: it's not packaged yet.
[13:52] <sistpoty|work> bdrung_: then get working on it ;)
[13:53] <bdrung_> sistpoty|work: we are still working on eclipse itself (will hopefully upload it today)
[13:53] <sistpoty|work> ah, k
[13:53] <siretart`> bdrung_: I don't think it's that easy :(
[13:53] <siretart`> but ok
[13:54] <bdrung_> siretart: cdt will probably easier than eclipse sdk.
[13:55] <bdrung_> sistpoty|work: we have to remove eclipse-cdt from the archive if we do not manage it to update the package
[13:56] <sistpoty|work> bdrung_: hm...
[13:56] <joaopinto> eclipse right now does not allow to install plugins, or how do you call it on eclipse :P
[13:57] <bdrung_> joaopinto: i will upload -0ubuntu3 which fixes this
[13:57] <joaopinto> bdrung, great :)
[13:59] <bdrung_> joaopinto: but there may be another issue...
[13:59] <bdrung_> with some md5sums
[14:13] <ScottK> sistpoty|work: I do think we want cdt updated if it's packaged.
[14:16] <sistpoty|work> ScottK: *nod*, the sooner the better
[14:29] <joaopinto> hum, did anyone test run grnotify before introducing it into the repository ?
[14:34] <james_w> joaopinto: bug 413816 or bug 370524? :-)
[14:36] <joaopinto> james_w, a new one, the source seems broken to me
[14:36] <james_w> does it need more bugs? :-)
[14:36] <james_w> failing to install and failing to start would seem to be enough
[14:37] <joaopinto> it fails to install due to a python-xml dependency
[14:38] <joaopinto> it will install and run without it
[14:38] <james_w> well it sounds like it doesn't follow the python policy correctly
[14:39] <joaopinto> AttributeError: 'grnotify' object has no attribute 'getUnreadFeeds'
[14:39] <joaopinto> now it misses a method definition
[14:41] <jdong> install: build
[14:41] <jdong>     python install.py local
[14:42] <jdong> the heck??
[14:42] <jdong> are we remotely supposed to package Python stuff this way?
[14:43] <jdong> well I suppose it was initially packaged for Jaunty
[14:43] <jdong> must've worked back then
[14:43] <joaopinto> it does not run from a jaunty schroot
[14:44] <jdong> lol ok then no more inventing excuses for the packager.
[14:46] <joaopinto> and I dond't understand how it ever run anywhere, getUnreadFeeds is not on the upstream source tarball either
[14:47] <joaopinto> oh wait, there is a getUnreadFeeds on GoogleReader.py
[14:53] <joaopinto> urllib2.HTTPError: HTTP Error 401: Unauthorized
[14:53] <joaopinto> next
[14:56] <sistpoty|work> hm... maybe we should remove it? doesn't look like there's upstream activity any longer
[15:00] <joaopinto> I am trying to fix it but I will probably give up :P
[15:01] <sistpoty|work> heh
[15:02] <joaopinto> for some reason it is not sending the cookies received from the login method
[15:03] <joaopinto> i's just trying to fetch https://www.google.com/reader/api/0/unread-count?all=true
[15:05] <joaopinto> anyone experienced with urllib2 and cookies :P ?
[15:05] <ScottK> iulian, vorian, nhandler, sistpoty|work: You have mail.
[15:07] <sistpoty|work> hm... only spam so far /me waits a little bit longer until the carrier pidgeon arrives
[15:08]  * iulian is waiting as well.
[15:08] <ScottK> Sent it to your ubuntu.com addresses, so Canonical may take a little while to forward it on.
[15:09] <ScottK> I checked my mail logs and they accepted it.
[15:10] <sistpoty|work> well, it's a long way, so... *g*
[15:10] <iulian> Indeed. :)
[15:12]  * sistpoty|work looks at the glassbowl and assumes the mail will be there in ~2 minutes
[15:17] <iulian> Ah-ha! It has just arrived.
[15:38] <bddebian> Heya gang
[15:39] <sistpoty|work> hi bddebian
[15:40] <sebner> huhu bddebian :D
[15:40] <bddebian> Hi sistpoty|work, sebner
[17:09] <juin> Hi :) I'm co-developer of the game "Plee the Bear". I've seen that the version of the package in Karmic is 0.2.1 but we have uploader version 0.4.1 in Debian a few weeks ago. Is there a chance to have 0.4.1 included in Karmic?
[17:18] <randomaction> !FFe | juin
[17:18] <joaopinto> juin, als you want to request  a sync from debian
[17:18] <joaopinto> also
[17:18] <randomaction> juin: today is a last day before FinalFreeze
[17:19] <joaopinto> it is ??
[17:20] <joaopinto> for universe ?
[17:20] <Laney> no
[17:20] <Laney> for main and restricted
[17:20] <sistpoty|work> no, universe finalfreeze deadline is still being discussed
[17:20] <joaopinto> ok :P
[17:21] <randomaction> ah, sorry
[17:21] <randomaction> today's u-d-a mail didn't make it totally clear for me
[17:21] <Laney> there was a link to some old information for universe
[17:22] <Laney> . o O ( should motu-release re-publish and update these documents each release?)
[17:22] <juin> I did not find on the website of Ubuntu when the syncs from Debian occur, do you have a link for me?
[17:23] <joaopinto> juin, https://wiki.ubuntu.com/SyncRequestProcess
[17:24]  * sistpoty|work heads home... cya
[17:25] <juin> thanks
[18:03] <Zhenech> .wi19
[18:03] <Zhenech> upsala :)
[18:04] <sebner> ScottK: do you know anything about a FFe for smuxi aka not needing one?
[18:04] <ScottK> sebner: Is there a bug?
[18:05] <sebner> ScottK: nope, bugfix (only?) release only
[18:05] <ScottK> sebner: Then it doesn't need an FFe is it's bugfix only.
[18:05] <sebner> ScottK: http://projects.qnetp.net/versions/show/9
[18:06] <ScottK> sebner: I'll trust your judgement of if it's bugfix only
[18:07] <sebner> ScottK: fine. thx
[19:36] <fabrice_sp> randomaction, ping
[19:36] <randomaction> fabrice_sp: hi
[19:36] <fabrice_sp> Hi :-)
[19:37] <fabrice_sp> I was having a look at bug #451332 and it seems that Debian already fixed the same bug in the next version of the package. Did you ahd a look at it?
[19:38] <randomaction> no, but I should have :(
[19:39] <randomaction> I think it's better to sync
[19:39] <fabrice_sp> yes :-)
[19:39] <fabrice_sp> it's not really a sync, I think that it seems some kubuntu patch has been there for a while, so perhaps it should be kept
[19:40] <fabrice_sp> we can also 'import' the debian patch, and say that it comes for there in the changelog, and make easier the merger life in next merge :-)
[19:41] <randomaction> ah, we also have a kubuntu-specific patch.
[19:41] <fabrice_sp> yes
[19:42] <ScottK> I'm gong to look at that
[19:42] <randomaction> shall I transform it into a merge request?
[19:43] <ScottK> Let me look at that patch first
[19:43] <randomaction> sure
[19:43] <fabrice_sp> ok
[19:44] <fabrice_sp> Super ScottK comes to the rescue :-)
[19:45] <ScottK> fabrice_sp and randomaction: The patch can be dropped now that kpowersave is in Universe.
[19:46] <randomaction> wow, it's from April 2004 :)
[19:46] <fabrice_sp> so it can be a sync request, then. I'll test build the Debian package
[19:46] <randomaction> ok, thanks fabrice_sp and ScottK
[19:47] <fabrice_sp> randomaction, you take care of updating the bug report?
[19:47] <randomaction> ok, just will test-build first
[20:01] <randomaction> fabrice_sp: updated
[20:02] <fabrice_sp> randomaction, ok. Can you just add the changelog entries since the actual version? This way, we will justify this sync :-)
[20:04] <randomaction> Done. I'm no replacement to requestsync :)
[20:09] <fabrice_sp> lol
[20:09] <fabrice_sp> you can run requestsync, and paste the output, withotu send it ;-)
[20:25] <leonel> can someone check bug 446838 if I've made the diffs  correct ??  thank  you
[22:50] <directhex> jono!
[22:51] <directhex> jono!jono!jono!jono!jono!jono!jono!
[22:51] <sebner> jono \o/
[22:57] <directhex> jonojonojonojonojono?
[23:06] <mrooney|w> Are there specific rules for compiled things in a source package? For example if the normal distribution method for a certain Java package is shipping a .war file, can a .deb just ship the war and appropriate init scripts to make deployment more automated?
[23:08] <mrooney|w> Obviously, it is possible to do that, for clarity my question is, can a package in say, universe do this
[23:09] <ScottK> Not knowing anything about Java stuff, is a .war file the preferred form for modification?
[23:11] <mrooney|w> ScottK: no that is the problem, it is basically a compiled Java package
[23:11] <ScottK> mrooney|w: Then no.
[23:11] <ScottK> It would need to go in multiverse
[23:11] <ScottK> Licensing would need to allow redistribution.
[23:12] <mrooney|w> I see, even if it points to the source which is properly licensed?
[23:12] <ScottK> Yes, even if.
[23:12] <directhex> mrooney|w, then the package can compile the .war at compile time, to build the deb
[23:12] <ScottK> The source needs to be in the source package and the binary needs to be built from that source
[23:13] <directhex> the only time it's acceptable to ship binaries in "source packages" is for bootstrapping (e.g. a c compiler is needed to compile a c compiler). this doesn't come under that heading
[23:13] <mrooney|w> I see, okay.
[23:14] <ScottK> And that's only OK as a temporary measure until you can upload one built from source.
[23:14] <ScottK> We could never release with that.
[23:14] <mrooney|w> I see, apparently it is challenging to build maven-based software according to debian policy, so that is why I was asking
[23:15] <directhex> maven is indeed troublesome, afaik
[23:15] <ScottK> Yep.
[23:16] <mrooney|w> So I guess PPA or multiverse are the best options?
[23:16] <directhex> there's one reason for mono adoption: our tools as packagers suck less
[23:16] <mrooney|w> haha, maven is actually pretty awesome
[23:17] <directhex> says the guy eyeing up multiverse!
[23:17] <mrooney|w> haha, it makes it super trivial to build
[23:17] <mrooney|w> not trivial to satisfy debian policy
[23:17] <mrooney|w> oh well, thanks for the advice, now I know the options :)