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