[00:09] Hi [00:09] I have problem with upgrade timezone in Ubuntu Dapper [00:12] This dont have tzdata package and i need upgrade Venezuelan timezone (like http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443202) [00:12] Debian bug 443202 in tzdata "Venezuelan time zone change, September 2007" [Normal,Fixed] [00:13] apostols__: do you have -proposed active on dapper ? [00:13] Kmos, No [00:13] 2007j-0ubuntu0.7.10 [00:14] this is the lat one in -updates and -propopsed [00:14] -proposed [00:15] it has the changes for venezuela [00:15] * Replace tzdata2007i.tar.gz with new version tzdata2007j: - Updates DST rules for Venezuela. [00:15] https://edge.launchpad.net/ubuntu/+source/tzdata [00:15] as you can see here [00:16] Kmos, This dont workfor Dapper [00:16] Kmos, tzdata package dont exist in Dapper [00:16] Kmos, Just exist locales package [00:19] apostols__: it must exist [00:20] Kmos, dont exist in Dapper [00:20] you have all repositories active? [00:20] Kmos: He's right. tzdata was introduced in Edgy. [00:20] Kmos: tzdata was split out from locales in Edgy [00:20] Kmos, http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=tzdata&searchon=names&subword=1&version=dapper&release=all [00:21] ups.. he's right.. [00:21] StevenK: you're right [00:21] as always =) [00:21] How to fixed its? [00:23] apostols__: Make sure a bug is filed in Launchpad and has a task open against locales in Ubuntu Dappper [00:23] Oh [00:23] :S [00:23] !info locales dapper [00:23] locales: common files for locale support. In component main, is required. Version 2.3.18.7 (dapper), package size 3208 kB, installed size 12788 kB [00:24] apostols__: have you checked whether version 2.3.18.7 of locales in dapper-updates includes this fix? [00:24] https://edge.launchpad.net/ubuntu/+source/langpack-locales [00:24] slangasek: that version has the fix.. [00:24] and it's at -updates [00:29] slangasek, I have installed Version: 2.3.18.7 [00:30] slangasek, in my source.lists have deb http://ve.archive.ubuntu.com/ubuntu/ dapper-updates main restricted [00:30] slangasek, this package is in main tree [00:30] apostols__: and this version has the wrong timezone data for Venezuela? [00:30] slangasek, yes [00:31] slangasek, one second. I try test the timezone [00:34] slangasek, This work [00:35] root@arismendi:~# date [00:35] Sun Dec 9 02:59:53 VET 2007 [00:35] root@arismendi:~# date [00:35] Sun Dec 9 02:30:01 VET 2007 [00:37] slangasek, Thanks for you help [00:37] apostols__: are you saying that it works now? I don't understand what you're showing, all I see is that your clock jumped back in time by a half hour. :) [00:38] sladen, Yeah, this change of timezone back in time half hour (the change is -04:00 to -04:30) === dendrobates is now known as dendro-away [00:38] slangasek, Yeah, this change of timezone back in time half hour (the change is -04:00 to -04:30) [00:38] sladen, excuseme [00:40] ok [01:04] slangasek, please come back w/ my vorlon! === tonyy is now known as tonyyarusso [02:01] geser: Have you filed a bug about the versioned build-dep thing? [02:01] geser: Would be nice to have a way to track it. === tonyy is now known as tonyyarusso [02:11] * Hobbsee waves [04:00] which is the best way to measure a program's memory usage in GNOME? === asac_ is now known as asac === jamesh_ is now known as jamesh === RAOF_ is now known as RAOF [06:11] good morning === Shely is now known as iE18 === LongPointyStick is now known as Hobbsee === \sh_away is now known as \sh [08:09] Good morning [08:11] hey pitti [08:15] <\sh> moins [08:18] hey seb128 [08:18] hello dholbach [09:31] pitti: can you give a build retry to evolution? [09:31] seb128: done [09:31] pitti: danke [09:39] pitti: ditto for nautilus? ;-) [09:39] done [09:39] thanks! [09:51] If an archive admin is around and doing duties, could they please promote python-pyatspi from universe? Its source package, at-spi is in main. Python-atspi is needed by gnome-orca to function. Otherwise, I assume I need to file a bug to get this taken care of? [09:51] TheMuso: no, that's fine [09:52] TheMuso: done [09:55] pitti: Thanks. [09:58] pitti: It seems gcrypt is still causing havoc [09:58] creating libqgis_core.la [09:58] /bin/sed: can't read /lib/libgcrypt.la: No such file or directory [09:58] meh; can libtool finally decide where it wants to look for the .la? [09:59] It seems not [09:59] Should we put the .la in /lib, and have a symlink from /usr/lib? [10:01] StevenK: I thought Riddell already did something like that? [10:01] He did? [10:01] ah, that was in libgpg-error [10:02] so, yes [10:02] (bwah) [10:03] So, should I do the same for gcrypt? [10:03] StevenK: either that, or we give up and revert all our patches *sigh* [10:04] pitti: I daresay adding a symlink should be simple-ish [10:04] it is [10:04] Is libtool just not realizing that .la files it needs to fnd or packages have moved or something? [10:04] find [10:04] pitti: I think we need to ask for battle pay, and go on a rampage hurting the libtool authors [10:04] TheMuso: it's behaving bizarre [10:05] TheMuso: the basic problem is that libtool seems to have no way to install a lib into /lib [10:05] pitti: No kidding. [10:05] so, if it's there, it sometimes looks for the .la in /usr/lib, and sometimes in /lib [10:05] Right. === seb128_ is now known as seb128 [10:06] * StevenK hacks libgcrypt11 [10:06] pitti: Real file in /lib or /usr/lib? [10:07] StevenK: /usr/lib, I'd say, but it shouldn't matter much [10:07] just for consistency with libgpg-error [10:13] dpkg uploaded. [10:13] * soren starts to sweat uncontrollably [10:13] wooo! [10:14] Hah [10:14] * pitti congratulates soren for being TIL now [10:14] * seb128 hugs soren [10:15] pitti: :p [10:17] pitti: Giving libgcrypt11 a nice hard test build before uploading [10:20] I've been looking into kvm and qemu a lot lately, and I've stumbled upon bug 64501. [10:20] Launchpad bug 64501 in openhackware "FTBFS" [Critical,Triaged] https://launchpad.net/bugs/64501 [10:20] It's an arch: all package that needs to be built on powerpc. [10:20] Would be acceptable to change that package to be arch: powerpc, build it, and make an arch: all package that ships the resulting files (kind of like ia32-libs for amd64)? [10:22] eww [10:22] I know :) [10:22] soren: why not just keep it as Arch: powerpc? [10:22] Better suggestions? [10:22] Because it's a BIOS image that qemu needs on other archs as well. [10:22] ah [10:22] ..to be able to emulate powerpc. [10:23] And it only builds on powerpc. [10:23] * pitti rolls back to "Eww" [10:23] Hah [10:23] soren: do you know why it can only be built on powerpc? [10:23] does it actually compile the bios? [10:23] AFAIR, yes. [10:24] soren: I can test build on PowerPC if you need it tested before you upload. [10:24] TheMuso: I have access to a powerpc machine, but thanks for the offer! [10:24] soren: Ok no problem then. [10:25] pitti: It might just be the case that my crossbuild-fu isn't strong enough. [10:25] Or that dpkg stole it [10:25] * StevenK sniggers, and feeds soren's complex [10:26] * soren whimpers [10:28] pitti: libgcrypt11 uploaded, and I've upped my bounty on the libtool developers. [10:28] great, thanks [10:28] /msg StevenK let's have a good beating at it in the afternoon [10:29] The bounty, the developers or libtool? :-) [10:29] StevenK: hmm.. are those devs in paris? [10:29] libtool; I'm not *that* cruel :) [10:29] Treenaks: I'm only naming the guilty party. [10:29] :-P [10:30] StevenK: for the developers, my evil plan is to lock them into a room with libgpg-error and libtool, and not allow them to come out again until they made it work right [10:30] pitti: Add libgcrypt11 and cryptsetup with /usr on a seperate partition, and you have my vote. [10:33] soren: how the *hell* did you manage to bork dpkg like that? [10:33] Hobbsee: :p [10:33] YOU BROKE IT! BAD SOREN! [10:34] Hobbsee: You should at least until the thing has actually built and been published before trying that :) [10:34] soren: haven't you heard that buildd admins can see, even before others can, and can smell breakage almost immediately? [10:35] Hobbsee: No, I must have missed the memo. [10:35] soren: now you know. [10:35] Noted :) [10:36] You know... One day, a long time from now, I'll stumble upon that note, and wonder why "buildd admins have superhuman sense of smell". [10:37] I could make it even more cryptic and make it say "buildd admins smell really well". [10:37] haha [10:37] * Hobbsee has uploaded dpkg before, and only just survived to tell the tale [10:38] soren: You could make it an in-joke and s/ really well// [10:38] * StevenK hides from Hobbsee, pitti and Mithrandir [10:38] * Hobbsee beats StevenK [10:38] Ouch! [10:38] Hobbsee: That's odd. I don't see your name in the changelog? [10:39] soren: i sponsored a change [10:39] Hobbsee: Oh. [10:39] then had iwwj attempting to eat me [10:40] Who's change did you sponsor? [10:40] Oh damn [10:40] pitti: Can you reject libgcrypt11? [10:41] StevenK: no [10:41] Drat [10:41] * StevenK quickly uploads a new version [10:41] StevenK: nowadays sources wander straight into DONE [10:41] no reject-from-accepted any more [10:42] Bad Soyuz [10:42] There we go, uploaded [10:42] StevenK: no, it's just more efficient now :P [10:43] * StevenK raises an eyebrow. [10:43] you're complaining about it being more efficient? [10:43] It introduces that you can't reject uploads, and besides, it seems to wait until sources are published before creating build records [10:45] * StevenK idly wonders if Soyuz deals with Pending -> Superseded [10:46] Hrm. So far both -2ubuntu6 and -2ubuntu7 are Pending [10:50] urgh, somewhitng really weird happened to my fonts since the last update [10:51] ah, restarting FF helps :) [10:51] StevenK: no, it doesn't; build records can be created immediately after upload [10:52] of course it actually takes eons, but it's not tied to publishing [10:52] Oh right, so it the build machinery just taking that long, and not waiting for the publisher [10:54] right [10:55] StevenK: ideally build records would be created immediately on accepting, and that's in fact the plan [11:07] Is it easy to run my own local CD builds, perhaps with locally modified packages or package lists, to have ISOs to run in emulators? [11:08] Or are you people using daily images and pushing changes via hardy to see how they affect the live CD? :) [11:09] Hmm... I'm trying to determine what changed in debian-policy between 3.7.2.2 and 3.7.3... The changelog lists only bugfixes afaics, but that would usually cause the version to be bumped to 3.7.2.3 rather than 3.7.3.0 wouldn't it? [11:10] soren: Well there are some changes in upgrading-checklist such as using ${binary:Version} instead of ${Source-Version} which are required by the new version [11:11] soren: Or the recommendation to link to the GFDL in /usr/share/common-licenses instead of copying it [11:12] lool: Hm.. Ok. That's it? [11:13] soren: There are other things as well; upgrade-checklist lists some stuff which you probably wouldn't want to care about, but it has some useful bits I think [11:14] I don't think it's very useful to mention "may do" stuff when it's already widely done for example :) [11:14] lool: I'm just looking for a list of functional changes (not just fixed typos or whatever), so that I can tell if I can update my package to "Standards-Version: 3.7.3". :/ [11:14] soren: Well upgrade-checklist is meant to be exactly this [11:15] lool: Ah... [11:15] lool: Ok, now I get it. :) Thanks. [11:15] It's a bit too long to my taste, but it's supposed to list effective things you should check when upgrading to a newer standard-versions [11:16] On my packages, I'd probably double-check binary:Version, check copyright for GPLv3 or GFDL, check menu sections (but probably lintian would tell me anyway), and that's probably all I'm using [11:16] * The Source field in a .changes file may contain a version number [11:16] in parentheses. [11:17] Yeah, that's really a lot of chatter for something probably two people care about [11:17] That sounds odd. [11:19] lool: Ok. Thanks for pointing out upgrade-checklist a sufficient number of times for me to actually get it. :) [11:19] soren: Ah you didn't know about the fiel? [11:19] lool: Nope. [11:20] I discovered it after a lot of time too; but it's mentionned in the changelog this time around :) === cprov-out is now known as cprov [11:20] Oh, really? [11:21] who can I speak with about whitelisting a laptop for acpi? [11:21] lool: it's unfortunately tedious to run one's own CD builds [11:21] the code's all there, but it's something of a pain to set up [11:21] if you need it, I can help you [11:22] you also need a full local mirror, at least of main and restricted [11:22] lool: Well, even if it did, I wouldn't have considered looking at it. I think I expected it to be a checklist for when upgrading packages, like: "Make sure if files move, you put conflicts: and replaces:" or something. I didn't put much thought into the matter, clearly. [11:22] the Source thing is support for dpkg experiments I think [11:23] someone resigned from triaging my bug and I've been waiting for nine months [11:23] https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/92806 [11:23] Launchpad bug 92806 in linux-source-2.6.22 "N340S8 laptop needs to have ACPI enabled" [Undecided,Confirmed] [11:23] cjwatson: Is it ok to have a http_proxy like squid? [11:23] lool: no, it really needs a mirror on disk [11:23] Ah [11:23] That sounds like many intermediate steps to reach the point where I can do actual tests; I think I'll defer that a little then [11:24] I suppose you could mount one with something to do with fuse over a squid proxy but argh [11:24] cjwatson: Is it easy to override packages or package lists -- bit still keeping the mirrors a clean true mirror? [11:24] s/bit/but [11:25] lool: the cdimage code has some (unused for some time) support for local packages [11:25] back when we were doing warty it took a while to get Ubuntu itself into shape, so I had local overrides of a few packages in cdimage in order to be able to build installable CDs [11:25] that would be easier than changing the mirror [11:26] Ok; perhaps I'll just boot a CD and use casper USB persistence if that's still available to install my experiments and see how to do that properly later [11:26] typically I just modify things on the fly if I need to do this sort of test, I must admit [11:26] Ok; thanks for the info [11:26] I do think it would be useful to have a facility for this eventually, but no capacity for it for hardy ... [11:27] (as in a proper user-oriented facility for customising CD images; we talked about it at UDS) [11:28] cjwatson: If I wanted to look into building hardy daily images, where should I start? I think it's "ubuntu-cd"? [11:28] http://people.ubuntu.com/~cjwatson/bzr/cdimage/mainline/ and also check out the bits listed in configs/devel [11:28] cjwatson: How do you usually test stuff like gfxboot and isolinux then? Extract an existing iso, replace the relevant files, re-mkisofs, test? [11:29] soren: I have a little manually-driven test suite for the gfxboot theme [11:29] cjwatson: Noted, thanks [11:29] it's just a thing where I can do 'make -C test' and it fishes stuff out of known places in my local directory layout [11:30] I don't use a full tree for it, just a few files that are enough to test the theme [11:30] cjwatson: Alright. [11:30] soren: http://people.ubuntu.com/~cjwatson/tmp/gfxboot-test.tar.gz [11:31] bit dated but hasn't changed much either === Hobbsee is now known as LongPointyStick [11:31] pitti: I assume you'll want another d-i for dapper-proposed? [11:31] * soren looks [11:32] cjwatson: yes, please; if that lbm ever condescends to build [11:32] but yeah, having d-i in the queue would be great [11:32] where's my supersonic jet? [11:33] cjwatson: Ah, clever. [11:33] pitti: heading queuewards now [11:33] LongPointyStick: Where are you going in that? === dholbach_ is now known as dholbach [11:50] Riddell: do you know about libkarma? the MIR (https://wiki.ubuntu.com/MainInclusionReportlibkarma) is almost useless [11:50] Riddell: does it actually work on a standard Ubuntu kernel? the cited pmount bug is long obsolete === jpatrick_ is now known as jpatrick [11:50] pitti: I'm told it does yes [11:55] TomaszD: the bug was confirmed so there was no longer a need for a triager anyway [11:55] TomaszD: odd though, the patch for your system still seems to be there [11:56] cjwatson, indeed, but it doesn't work :( [11:56] after dapper or edgy I have to acpi=force in menu.lst [11:57] TomaszD: yeah, it's just that you explicitly said the patch was removed and I don't see that it was [11:57] so trying to work out what happened [11:58] cjwatson, ok. You know IANAE, but I thought that once I don't have the functionality the patch must have been dropped by mistake [11:58] TomaszD: to be clear, we're talking about ACPI sleep, right? [11:58] asac: xulrunner MIR> when we will switch firefox to 3 by default? [11:58] (you just said "ACPI" in the bug) [11:58] cjwatson, we're talking about turning on ACPI at all [11:59] cjwatson, because I get the message about the bios being to old and going under the bios cut-off age [11:59] err, acpi-support doesn't have one of those [11:59] cjwatson, so it's not whitelisted then? [11:59] perhaps it would help if you copied the *exact* message you're seeing into the bug [12:00] pitti: in january i guess ... there is still too much work going on upstream to not cause any confusion ... for now i need xul 1.9 in main to update all the other rdepends. [12:00] mdke: any news about the yelp layout patch update? [12:01] pitti: maybe b2 will be good enough though (which will be next week i guess) [12:01] * pitti switches his desktop to ffox 3 for testing love [12:01] it appears just for a second, it says your bios falls under the bios cut-off age, because it's older than 1998 (which isn't true, it's 2002), so acpi functions will have to be forced to be enabled cjwatson [12:01] asac: ah, I see; but we'll definitively drop 2 for hardy [12:01] TomaszD: I've commented on the bug; it's not an acpi-support problem, it's a kernel problem [12:01] pitti: yes. we cannot support ffox 2 for such a long time [12:02] whenever I install a new version of ubuntu cjwatson I just go menu.lst and acpi=force there, I got used to it, but acpi was working in dapper [12:02] pitti: as proposed in https://wiki.ubuntu.com/XulrunnerGecko ... we will allow universe rdepends to switch to xulrunner 1.8 ... in case they don't get ready in time. [12:03] I imagine the kernel got stricter [12:03] asac: ah, so in ffox 3 I don't have those ugly typewriter fonts (as broken by recent fontconfig), but I don't have the smooth fonts either; but slightly better, I'd say :) === xerakko_ is now known as xerakko [12:04] pitti: yeah ... there is a request to patch xulrunner for subpixel stuff (bug 164640) ... maybe thats the problem? [12:04] Launchpad bug 164640 in xulrunner-1.9 "Build Firefox 3 against a subpixel-patched cairo" [Undecided,Confirmed] https://launchpad.net/bugs/164640 [12:04] asac: I guess so [12:05] asac: ok, promoted [12:05] pitti: rock! [12:06] asac: but what's wrong with switching to 3 early? after all, testing is why we all run hardy now? [12:07] xulrunner1.9 promoted? [12:07] which means we can build the GNOME packages using it now? [12:07] seb128: yeah ... if you apply the patches i have ;) [12:08] seb128: https://code.edge.launchpad.net/~mozillateam/xulrunner/xulrunner-porting [12:08] there is yelp, devhelp and epiphany ... though epiphany is against current trunk [12:09] i will add the python gtkmozembed today i hope (after cleaning things up) [12:09] seb128: ah ... totem is in that xulrunner-porting thing as well [12:10] cjwatson: WDYT about libssh? There's a MIR for it, but I have some concern about having two ssh implementations in main [12:10] pitti: i wanted to fix xulrunner to consider all the needed plugins/extensions directories before making firefox-3.0 default ... otherwise we will end up installing plugins in a place that is not ment to be the final one. [12:11] asac: ah, that's a good point, yes [12:11] asac: do you want to do the upload or should have a look to that? I've nothing special to do this afternoon so I'm fine looking at the changes and the wiki page I said I would read the other day and upload the xulrunner versions ;-) [12:12] seb128: i would prefer if you could take the uploading part and maybe even upstream submission [12:13] seb128: before you touch a package better ask me for any regression i know of ... so you can decide if its good enough for initial upload [12:14] to start with: yelp patch has no known regression for me === dendro-away is now known as dendrobates [12:17] asac: ok, will do that after lunch then, thanks [12:18] seb128: nothing to hurry ... you need to wait till the xulrunner-1.9 package i uploaded today is build because it changed the names of the .pc files to the final ones [12:22] asac: ok [12:24] pitti: since openssh is never likely to provide a library, it doesn't hugely bother me [12:24] cjwatson: yeah, but it just feels...wrong [12:25] your call [12:26] * gicmo yawns [12:46] for the love of the great green arklesneezer, this is absolutley ridiculous! [12:46] grr! [12:46] hmmm [12:47] LongPointyStick: what now? [12:47] my system has frozen 4 times in the past 10 minutes! [12:47] that's a new low for hardy. [12:48] tjaalton: where should i start looking as to why it's freezing? [12:48] MOTU Q&A session in 11 minutes in #ubuntu-classroom [12:52] LongPointyStick: well, there have been no updated x-packages lately, to my knowledge :) [12:53] tjaalton: this has happened for a while, but seems worse atm. [12:53] oh, interesting. compiz is showing 100% cpu [12:53] compiz was updated today :) [12:54] and yesterday [12:54] well, there you go :) [12:58] and now it behaves, with another machine ssh'd in [13:00] or not. [13:00] Heh [13:01] hmm on lpia i get a strange build failure for xulrunner-1.9 : http://paste.ubuntu.com/2524/ [13:01] compiz doesn't do the newer Intels yet, right? [13:03] Nafallo: this isnt' really a newer intel [13:03] Hobbsee: was more of a general question dear :-) [13:04] GM965 / X3100 or so. [13:04] oh [13:06] pitti: maybe the promotion in the mids of a xul build caused these "failed to upload" errors? https://edge.launchpad.net/ubuntu/+source/xulrunner-1.9/1.9~b1+nobinonly-0ubuntu2 [13:06] tjaalton: actually, i don't think you get blamed for this. it appears that compiz shows 100% CPU and locks up (while the programs all still run), when more than 1 active "notify me" window is there. [13:06] asac: right; let me give them back [13:06] asac: yes, that's correct [13:06] pitti: thanks! [13:07] Nafallo: they removed the blacklistning of 965 in -0ubuntu3 [13:07] * asac lunch [13:07] torkel: cheers. sounds scary 'nough to update according to Hobbsee though ;-) [13:08] ...and Fujitsu [13:17] Fujitsu: you still around? === cassidy_ is now known as cassidy [13:23] asac: is there a way to tell gnome to use ffox-3 as my prefered application? it opens ffox 2 on clicking on a link ATM, but ffox 2 doesn't appear in gnome-default-applications-properties [13:23] pitti: You can set a manual command? [13:24] pitti: %s for the URL [13:24] yeah, of course [13:24] but it shuold still appear there [13:24] It needs to be patched in control-center IIRC [13:24] pitti: how is the binary called? [13:24] firefox-3.0 [13:24] oh, it's hardcoded there? [13:24] Yeah [13:24] I thought it was some .desktop file somewhere [13:25] after all, even lynx appears there :) [13:25] I think it has a mapping [13:25] pitti: /usr/share/gnome-control-center/gnome-default-applications.xml has the list of known applications [13:25] seb128: aah, I understand; thanks [13:25] need to patch gnome-control-center [13:25] I'll do it [13:25] seb128: well, shouldn't be necessary in the end [13:26] seb128: once we ship 3 by default, the binary will be 'firefox' (hopefully :) ) [13:26] if the binary is renamed firefox no need to rename [13:26] right [13:26] I just wondered by which mechanism a package appears there [13:26] so I was concerned that ffox-3 needs to ship a .desktop file for that, or so [13:27] that would be a better way to do things [13:27] but at the moment the list is in gnome-control-center [13:27] seb128: ok; nevermind then [13:27] and thanks for the explanation [13:27] you are welcome === cjwatson_ is now known as cjwatson === Igorots is now known as Knightlust === Hobbsee_ is now known as Hobbsee === doko__ is now known as doko === \sh is now known as \sh_away [14:30] seb128, can i discuss default torrent client for Ubuntu with you? [14:32] xhaker: if you want too, I'm not sure I'm the best person for that discussion though since I don't know the alternatives nor use bittorrent [14:33] seb128, just thought you were appropriate since you are a "gnome" guy. My take is that gnome-btdownload + bittorrent should step back [14:34] I've been thinking to myself, that Transmission is very much the best for a default torrent client [14:36] While trying out fedora8 live through an usbkey, i noticed they have transmission there. :) I wish we could do the same. [14:36] xhaker: maybe mail ubuntu-desktop or ubuntu-devel-discuss list about some rational on why you think transmission is better [14:36] I think some people did in the past but other users replied that transmission was not stable and crash all the time, etc [14:37] seb128, it might be true.. but i've been following the development.. they're really active.. and they're running up for the 1.0 release.. last version on the repositories is 0.95 [14:37] Will send my rationale to ubuntu-desktop ml [14:37] xhaker: is there anybody looking at the launchpad bugs for transmission? like an upstream guy? [14:37] just because they call it 1.0 doesn't mean it's bug-free [14:38] that would show they have interest to have it used in ubuntu ;-) [14:38] xhaker: thanks [14:39] azeem, it means they're pretty confident it'll be good.. check their trac page.. they look into HIG, and there are lots of worrying with memory leaks :D [14:44] * ogra wonders if there is a way to compile dillo with xulrunner now :P [14:47] * xhaker is not smart enough to understand why debian and ubuntu build-depend differently in respect of xulrunner-dev and firefox-dev [14:47] xhaker please also add deluge to the possibility of default torrenting clients [14:48] poningru, don't get me wrong.. I'm using deluge right now.. I have both clients installed.. but Transmission is leaps ahead in ease of use [14:48] xhaker, lawyers will uderstand that :) [14:49] poningru, it just downloads, and does a good job at that. :) hence the proposal for shipping in the default install [14:49] xhaker, ah k === cprov is now known as cprov-lunch [14:50] someone also needs to solve the natting problem with those things [14:50] as in some client program that works with routers that automatically adds a port [14:50] forwarding [14:52] Transmission will use http://miniupnp.free.fr/ projects.. provides upnp and natpmp [14:52] It will maybe handle more routers than their solution now [15:33] seb128: I assume totem-pl-parser should go into main? [15:33] pitti: yes [15:33] pitti: totem will depends on it when it's accepted [15:34] pitti: danke ;-) [15:34] seb128: looks good to me, accepted [15:35] *whistle* NEW is empty again [15:37] * Hobbsee uploads more [15:37] pitti: Did you figure out how to remove crack from partner yet? [15:38] ScottK: yes, it's actually gone; I just didn't close the bug yet [15:38] pitti: Great. Thanks for that/ [15:38] /. === cprov-lunch is now known as cprov [16:00] ehrm [16:00] "remove crack for partner". that can be quite misunderstood ;-) [16:03] BenC: re lbm patch> I sent a mail about that this morning with a pointer to the patch [16:03] pitti: oops, must have missed that, sorry [16:04] BenC: no problem; it's attached to bug 164449, so you can grab it from there [16:04] Launchpad bug 164449 in linux-backports-modules-2.6.15 "undefined symbols in mptspi driver" [High,Fix released] https://launchpad.net/bugs/164449 [16:04] BenC: can i ask when we get l-u-m for .24? [16:04] Hobbsee: before monday [16:04] BenC: \o/ [16:30] cjwatson: wrt. getting the noptrace group into base-passwd; do you think we should discuss abusing an existing group and put that into a meeting (TB or whatever), or shall I file a bug about adding 'noptrace' to base-passwd? [16:32] I'd like it to be discussed on debian-devel [16:32] base-passwd is one package I really don't want to be out of sync [16:33] and I want complete propriety in how changes to the master files happen [16:33] ok, I'll send a mail there [16:34] thanks [16:37] Nafallo: Pick a better word that characterizes uploading software to a public repository with known remote code exploits unpatched? [16:40] mornin' [16:41] ScottK: foolness. what did I do now? [16:45] Nafallo: Not you. I was responding to your comment about crack and partner. [16:45] ScottK: ah :-) [16:47] I don't understande why some uploads to hardy-changes aren't signed [16:47] lool: syncs are unsigned [16:48] 3.16.0-4ubuntu1 => probably not a sync; I think the body of the mail has in fact a signature, but Mutt doesn't recognize it as such [16:48] we just copy those from Debian, and they're done on a trusted system and inserted through basically a back door in the queue system rather than inventing a fake key to sign them with [16:48] ah [16:48] Either an encoding issue or a Mutt bug [16:49] ScottK: not that it was the right thing to do; but we did know that the problems in openssl097 did not affect vmware [16:50] cjwatson: I understand that. That was no where publically documented and certainly doesn't help a bit when people (our competition) says ubuntu-server isn't secure enough to take seriously. The percpetion (if not the fact) was very poor. [16:50] It also pained me personally after investing a lot of time in getting it removed from Universe. [16:51] Ah it's UTF-8 [16:51] That's the data confusing Mutt [16:52] ScottK: I know, we still have work to do on a proper response that includes documentation on what will be allowed in partner; it's in progress ... [16:52] cjwatson: Good to hear. Thanks. [16:52] * ScottK grumbles again that it'd be better if Partner were more clearly a Canonical production than an Ubuntu one. [16:53] what can we do to make that clearer? [16:54] or, perhaps a fairer question, in what places is it currently unclear? [16:54] In LP it's not clear at all. [16:54] For example, bugs against things in Partner are described as "in Ubuntu" [16:54] hmm, I didn't realise that packages in partner showed up under Ubuntu [16:54] I agree that that's unfortunate === dendrobates is now known as dendro-away [16:55] (or perhaps I did know and forgot) [16:55] If you go to the front page for the 7.10 release, Partner is listed as just another repository. [16:55] cjwatson: There's an LP bug. Let me find it. [16:56] I don't see partner mentioned on /ubuntu/gutsy [16:56] cjwatson: Bug #153798 [16:56] Launchpad bug 153798 in soyuz "canonical partner repo packages showing as "in ubuntu"" [Undecided,Confirmed] https://launchpad.net/bugs/153798 [16:56] * ScottK looks again [16:57] ah, it's on /ubuntu [16:57] Yes. Sorry about that. [16:57] That's actually worse. [16:58] followed up to the bug [16:58] cjwatson: Thanks. [16:58] (not with good news, I'm afraid) [17:00] cjwatson: I understand your answer, but as a non-Canonical developer, it's very frustrating. [17:50] mjg59`: are you planning to merge powernowd? I've collected a whole bunch of fixes in the last days, which are attached to bug 67341. If you like, I could do the merge and include those - then you could just sponsor it. [17:50] Launchpad bug 67341 in powernowd "powernowd doesn't use /etc/default/powernowd anymore" [Low,Triaged] https://launchpad.net/bugs/67341 === cprov is now known as cprov-out [18:03] pitti: please give-back: compiz-fusion-plugins-extra === dendro-away is now known as dendrobates === cjwatson_ is now known as cjwatson [18:11] ScottK: some things are frustrating both inside and outside Canonical ... [18:14] ;-) [18:18] cjwatson: d-devel@ mail about ptrace() sent; let the flamefest begin :) [18:23] keescook: ^ I BCCed you to that FYI [18:23] pitti: cool; thanks. === mekius_ is now known as mekius [18:28] * pitti blinks [18:29] cjwatson: I just wanted to add a gutsy task to your SRU bug, but guess which release is missing on https://bugs.edge.launchpad.net/ubuntu/+source/finish-install/+bug/174689/+nominate [18:29] Launchpad bug 174689 in finish-install "hvc/hvsi consoles not handled" [Undecided,New] [18:29] cjwatson: any idea why? [18:29] because I targeted it myself 10 minutes ago or so [18:30] ah, heh; sweet race [18:30] thanks [18:30] I stared at the check boxes for at least 10 seconds until I realized :) [18:30] might be worth a Malone bug === dendrobates is now known as dendro-away === dendro-away is now known as dendrobates === pedro__ is now known as pedro_ [18:44] pitti: please give-back: gdome2-xslt [18:50] pitti: please give-back: ocamlgraph [18:50] geser: both done [18:55] pitti: please give-back: compiz-fusion-plugins-extra [18:57] done [18:58] thanks [19:06] Hello === jdong is now known as jdong2 === jdong2 is now known as jdong === mathiaz_ is now known as mathiaz === ember_ is now known as ember [20:01] hi folks [20:03] hiya sistpoty [20:03] hi pochu [20:14] should build-dependencies on gs-common be replaced with ghostscript or is build-depending on gs-common still ok (especially for a package in main)? [20:40] any hal experts around? [20:42] tjaalton: you might be better to ask in #hal or #gnome-hackers on gimpnet [20:44] Burgundavia: right, I'll do that if I can't figure it out myself eventually [20:44] the problem, that is === jdong is now known as jdong2 === jdong2 is now known as jdong === nixternal_ is now known as nixternal === Adri20001 is now known as Adri2000 [22:29] i've got a bug in the gnome power manager where the display brightness will "dim" to a value higher than what i manually set with the keyboard shortcut when it thinks i'm idle. i would like to fix this bug. what should i download to take a look? [22:29] AgentHeX: I have a vague recollection that there was a bug on this already. Dunno if it's been fixed in Hardy or not. [22:30] ScottK: i'm on gutsy right now. i was kind of looking for an introduction to developing in ubuntu. i'm a C++ coder but i have little experience coding in linux, and i'm looking for a way i can explore. any hints? [22:31] Sorry. I'm a KDE person. [22:31] ScottK: i'm pulling eclipse atm, so i'll have that soon, and i figured the gpm bug might be a good start [22:31] ScottK: how might i go about getting the source for the gnome power manager? [22:32] I'd suggest looking for the gdm bug and seeing what's already there (it had a proposed patch, dunno how good it is). [22:32] "apt-get source gnome-power-manager" [22:32] ah [22:32] slangasek: i was looking in synaptic. [22:33] AgentHeX: First lesson is developers will taunt you if you insist on using GUI tools and not command line. [22:33] they will? [22:34] * slangasek covers up his update-manager [22:34] hmm. I use sudo update-manager from a terminal ;-) [22:36] ScottK: i would *rather* use a GUI IDE, but i *could* use a CLI [22:37] You'll get over it ;-) [22:37] ScottK: i'm familiar enough with vim that i prefer it to a generic text editor (gedit, notepad, et al), and it's proably a good thing since i'm on a laptop and the touchpad is kinda annoying [22:37] Excellent. [22:38] I think your basic strategy of find stuff that annoys you and try to fix it is a good one. [22:38] ScottK: but i'd still rather use a gui. if there was a gui version of vim, i'd be in heaven. [22:38] I think there is, but I don't recall for sure. [22:38] pitti. hi [22:39] ScottK: i'm kinda kidding. what's the point of having a gui version of vim anyway? it's designed to be lightweight. that gui adds tons of cruft [22:39] ScottK: now once i actually have the source for the package, how do i go about compiling it? will i need source for all the dependencies as well? [22:39] * ScottK has no idea, but it's FOSS, so all it takes is one coder who feels liek it. [22:42] i'm pretty sure apt-get source will drop the source in my /usr/src path. can you confirm? [22:43] No, it'll drop it into the current working directory. [22:43] ah... do not want in home [22:43] https://wiki.ubuntu.com/PackagingGuide/Howtos/BuildingTheSourcePackage?highlight=%28build%29 is a start on how to compile it. It'll lead you to other quesitons, but I have to run. [22:44] n8 [22:48] has anyone used git instead of svn? [22:51] doko, did you upload hplip and hal-cups-utils for me? [22:53] tkamppeter: is the new dpkg already built? [22:53] tkamppeter: the current version of hplip needs the newer dpkg for building [22:53] ScottK: how might i go about running a modified gpm? do i need to replace the original and hope i don't bork my system? how might i debug something like gpm? [22:55] AgentHeX: anyway, "vim-gnome" :) [22:56] tkamppeter: yes [22:58] slangasek: hah. nice [23:00] doko_: Thank you very much [23:06] oh snap. i can't see my appearances window to turn off compiz. [23:06] HAH! i did it blind! [23:07] geser, I have taken HPLIP from the Debian RPM as I am working together with Mark Purcell from Debian on the maintenance and so our packages and Debian's are the same. [23:07] On this build I had a problem and I had to remove "--dpkg-shlibdeps-params=--ignore-missing-info" from dh_shlibdeps in debian/rules. [23:07] My system is a Hardy which I have updated today. [23:07] geser, would this mean that I can reintroduce this "--dpkg-shlibdeps-params=--ignore-missing-info" on dh_shlibdeps as soon as the newest dpkg hits Hardy? [23:07] dpkg --version [23:07] Debian `dpkg' package management program version 1.14.12ubuntu1 (i386) [23:07] s/Debian RPM/Debian SVN/ === Traxer is now known as Traxer|on === Traxer|on is now known as Traxer [23:12] tkamppeter_: if I understand it all correctly, yes [23:12] geser, so which version dpkg must be so that I can re-introduce "--dpkg-shlibdeps-params=--ignore-missing-info" on dh_shlibdeps? [23:12] --ignore-missing-info was introduced around .8 or .9 and .12 is getting build now [23:13] tkamppeter_: if you're working with hplip, how about fixing it so that it has a proper shlibs file and doesn't *need* the --ignore-missing-info? [23:13] according to the changelog --ignore-missing-info works since dpkg 1.14.8 [23:14] So strange that it did not work with 1.14.12ubuntu1 [23:14] I don't know what possessed the maintainer to do that instead of looking at the reason why dpkg-dev thought the package was wrong :P [23:15] Mark Purcell has introduced --ignore-missing-info. I do not even know for what that is good for. [23:15] it's to stop dpkg-shlibdeps erroring out with a message about missing shlibs for a library dependency [23:16] and the reason dpkg-shlibdeps was erroring out was because he has a library that's missing a shlibs file (required by policy), which means the package interdependencies are wrong [23:16] HPLIP seems to build and install fine without --ignore-missing-info. [23:17] not with the new dpkg [23:17] should build-dependencies on gs-common be replaced with ghostscript or is build-depending on gs-common still ok (especially for a package in main)? [23:18] geser, I think this can be moved to ghostscript. ghostscript has a transitional package gs-common, but things should depend on the main package. [23:20] note that the "ghostscript" package doesn't exist in dapper, so this will affect ease of backporting [23:22] slangasek: it's a change for graphviz, see bug #174749 [23:22] Launchpad bug 174749 in graphviz "[hardy] Drop libttf-dev from Build-Depends" [Undecided,New] https://launchpad.net/bugs/174749 [23:22] gs-common is in universe but ghostscript provides gs-common so build-depending on it should work, but to be on the safe side I changed it [23:24] there's no need here to be "on the safe side". It's perfectly valid to build-depend on virtual packages [23:24] and as I said, build-depending on "ghostscript" is an additional change that has to be made for backports (as well as increasing the size of the Ubuntu delta here, of course) [23:25] slangasek: If it doesn't exist in Dapper, then I'd just backport ghostscript first (no regression risk). [23:25] so I should revert it back to gs-common? [23:26] ScottK: uh? in what sense is there no risk of regression? it's a complete reorganization of the source packages [23:26] ScottK: I guess ghostscript was called gs-somehting in dapper [23:26] slangasek: I haven't actually looked at it, but generally if a package doesn't exist, it's good for backporting (I do check before I actually approve these things). Nevermind then. [23:28] ScottK: right; this isn't a "ghostscript doesn't exist in dapper", it's a "someone thought it would be clever to rename all the ghostscript-related packages in Debian because renaming is FUN" [23:28] slangasek: Ah. Yes. That'd be totally different. [23:29] slangasek: I'd say you got the first two letters right. [23:30] sorry for my hash collision [23:30] :) [23:32] geser, gs-common is in Universe? I thought we have taken it from the distro? It does not make sense any more with the new ghostscript. ghostscript contains everything now. So please remove gs-common from the Universe. [23:33] geser, in dapper the default ghostscript was gs-esp, as alternative there were also gs-gpl and gs-afpl. [23:34] tkamppeter_: Does it have any rdepends left? [23:35] slangasek, we decided on renaming it /the Debian maintainer and me) to make it searchable more easily. Searching for ghostscript gives better results than for gs. [23:36] and with the merger of ESP and GPL Ghostscript (http://www.cups.org/espgs/) which I have done this year all gs-... got obsolete. === tkamppeter_ is now known as tkamppeter [23:37] ScottK, what are rdepends? [23:37] tkamppeter_: a) gs-common is being built from the ghostscript source as a dummy package, to facilitate smooth upgrades; I'm not sure why it needs to be a transitional package instead of just the gs-gpl and gs-esp packages, but that's the rationale given. b) "apt-cache search ghostscript" already worked fine? [23:40] slangasek, is it not the case that for every package which my new package replaces I have to provide a transitional package? And ghostscript replaces gs-common. [23:40] tkamppeter: you just said "please remove gs-common from the Universe", how exactly do you expect it to be removed and still be a transitional package? [23:41] the gs-common package in universe /is/ the transitional package [23:41] as for whether every package needs a transitional package, no; you generally only want transitional packages for things that an end-user is likely to install directly [23:52] slangasek, so "apt-get dist-upgrade" would work also without transitional packages? Only "apt-get install gs-common" needs them? [23:53] slangasek, then with the gs-common in Universe being the transitional package everything is OK. Nothing needs to be removed. [23:54] tkamppeter_: "apt-get dist-upgrade" would not do what you want without /some/ transitional packages. But I think users are unlikely to have gs-common alone installed, right? They're likely to have gs-esp or gs-gpl installed? [23:54] tkamppeter_: in which case, you only need to provide transitional packages for gs-esp and gs-gpl, since gs-common would be sorted out according to dependencies [23:57] slangasek, I understand, gs-common is like a lib... package which does not make sense alone. So can I take it out on the next ghostscript packaging then? [23:58] tkamppeter_: since ghostscript also has a Provides: gs-common that will meet the needs of reverse-deps, that's what I would suggest, yes [23:58] slangasek, OK and thanks for the help. [23:59] sure