[01:22] ok forgive my ignorance and being lazy for a moment if you will and will someone give me the 1 - 2 sentance explination as to what "Zeitgeist" as it pertains to gnome ? [01:22] a program ? language ? abstration layer ? .... === nobawk is now known as nobawk|away [02:14] Time sequenced activity history. [02:47] imbrandon: awesomeness! (ScottK's answer is short and to the point), It's (afaik) a back-end that creates associations, time, program, place, activity, so that you later on could find out, say, what Kind of music you listened to whilst chatting with a particular person... Is one of the things it can do. === nobawk|away is now known as nobawk [03:13] ScottK / arand : ahh like a personal google, sorta [03:13] seems intrusive and expensive ... maybe i'm wrong [03:14] imbrandon: Yea, but so is google And that has it's uses. [03:14] :) [03:14] imbrandon: really up to you if you use it or not. [03:15] very true, just was curious i have seen alot of blogs about pieces of it lately but not much on what "it" was [03:15] something i can poke into more later ;) [03:25] * imbrandon yawns [03:25] ugh i have code to write tonight but i just cant motivate myself [03:25] hum de dum === zehrique-away is now known as zehrique === baddog_ is now known as baddog === nobawk is now known as nobawk|away === nobawk|away is now known as nobawk === Amaranth is now known as c === c is now known as Amaranth === nobawk is now known as nobawk|away === nobawk|away is now known as nobawk [08:58] how can I delete an old deactivated key from the ubuntu's keyserver? [08:59] BlackZ: That's impossible. [09:01] jpds: ok, BTW I have updated the key (e-mail), but I can still seen the old e-mail on ubuntu's keyserver, is that normal? [09:01] Did you remove the old email? [09:01] yeah [09:01] Yep, that's also impossible. [09:02] You can only add to keyservers, never remove. [09:02] jpds: also, I have signed some uploaded packages with the old key and e-mail, is that a problem? [09:03] Shouldn't be. [09:03] jpds: however that is updated in my launchpad's page === ogra_ is now known as ogra [12:22] chrisccoulson: Hia, talked on friday, BitlBee.. got time over to sponsor Bug #581331 ? [12:22] Launchpad bug 581331 in bitlbee (Ubuntu Karmic) "error message while trying to use my MSN account in bitlbee" [High,Triaged] https://launchpad.net/bugs/581331 [12:22] arand - oh yeah, sorry, i forgot about that one [12:22] has nobody else done it yet? [12:22] i will look at that in a bit [12:23] chrisccoulson: Nope :( seems few sponsors are around here on the weekends, or they just didn't like me.. [12:28] arand: I'm sure your work will be sponsored soon, keep in mind you're in a queue :) [12:33] BlackZ: Yea, true. # of bugs with patches are a hefty amount. [12:34] ara: I know and I think they will be sorted out ASAP [12:34] err, arand - sorry, ara === nobawk is now known as nobawk|away [12:43] arand: why is the bug still assigned to you? why is it "Fix Released" instead of "Confirmed", for example? [12:46] BlackZ: Fixed in maverick with version 1.2.7, this is for hardy..lucid, what's the policy as far ass assignments go actually, I though, since I was "in charge" of packing the SVN fix, it would be appropriate, no? [12:47] *as *thought [12:50] arand: since ~ubuntu-sponsors is subscribed, you have to follow https://wiki.ubuntu.com/SponsorshipProcess [12:50] for example. "Do not assign a bug to anyone if it needs sponsorship." [12:52] s/./, [12:54] BlackZ: Ah, hmm, I was going by that I've had been assigned to bugs (by others) in similar cases before. Right, so unassigning then. === nobawk|away is now known as nobawk [13:15] don't know if this is the right channel, but I would like to inform you that Boinc in the default repositories is horribly out of date, and that I'm forced to install the latest version manually === am_ is now known as mase_home === nobawk is now known as nobawk|away === nobawk|away is now known as nobawk === nobawk is now known as nobawk|away === nobawk|away is now known as nobawk [16:32] greetings. I packaged my app and it compiles fine. I just need to figure out how to get it to place the compiled files into /usr/bin and such. Do I do it in debian/rules? Please advise === andreas_ is now known as anoteng [16:52] kobrien: So, there's two ways to do it. If you're the upstream developer, it's best to do it in your build script, with an install rule. For example, `make install` [16:52] If you're not upstream, you can work around a buggy set of build scripts with dh_install === gnomefreak76 is now known as gnomefreak === RoAk is now known as andreserl === nobawk is now known as nobawk|away === nobawk|away is now known as nobawk [19:15] siretart: should I reassign the gxine bug to you? [19:21] siretart: wrapper looks fine I think it should go to maverick first though [19:24] One of my mails was flagged as possible spam to the mailing list. Shouldn't we set SpamAssassin to look kindly on GPG-signed mails? :) [19:28] micahg: feel free to do so. what about copying it from lucid-proposed to maverick? [19:31] how do ppl feel breaking maverick's ffmpeg at this point? ;-) [19:32] siretart: I currently cannot push packages yet. As for copying, idk what the current policy is, but I think that fixes are supposed to go into the devel release first again [19:32] siretart: what will break with ffmpeg? [19:33] micahg: upload ffmpeg 0.6 will probably break quite some applications that link against it [19:33] siretart: ah [19:33] no idea how severe the breakage will be, I did not do testbuilds [19:33] but I guess I should do so in any case. soon. [19:34] siretart: so, do you want me to find a sponsor for gxine, or do you want to push/ [19:35] I can do the upload later today [19:35] siretart: k, thanks, I'll reassign to you [19:37] siretart: I'll subscribe to the package to watch for regressions [19:37] great, thanks! [19:38] siretart: thanks for making the wrapper :) === kobrien is now known as Guest6663 [20:14] hi [20:15] i want to build a package with pbuilder but have a dependecy on a local package version. how to solve this? [20:16] toabctl: easiest way around that is to create a simple local package repository [20:17] ok [20:17] thx [20:17] or login into pbuilder, copy all needed files inside and build there manually [20:18] yes, that's easier for once-off [20:18] I do it when I need to do it only once (was too lazy to setup a repo for just one build) [20:20] geser, where is the pbuilder .tgz file extracted? [20:20] i got the following error when i use "pdebuild": Aptitude couldn't satisfy the build dependencies [20:20] usually below /var/cache/pbuilder/build/ (see the output when calling pbuilder) [20:21] geser, /var/cache/pbuilder/build is empty [20:21] yes as it gets cleaned up after pbuilder has finished [20:21] Reading task descriptions... [20:21] Aptitude couldn't satisfy the build dependencies [20:21] E: pbuilder-satisfydepends failed. [20:21] I: Copying back the cached apt archive contents [20:21] I: unmounting dev/pts filesystem [20:21] I: unmounting proc filesystem [20:21] I: cleaning the build env [20:21] I: removing directory /var/cache/pbuilder/build//11519 and its subdirectories [20:22] geser, tumbleweed : that's my output. i try to build a new version of syncevolution for DIST=sid under ubuntu lucid [20:22] "pbuilder login" and you get a directory below /var/cache/pbuilder/build as long as don't exit the pbuilder [20:23] geser, ah. that works. thanks. and do you know what i can do against the error? [20:24] check which dependency couldn't get resolved (and why) and fix it [20:25] pbuilder-satisfydepends-dummy: Depends: libsynthesis-dev (>= 3.4.0.5~) but it is not going to be installed. [20:25] geser, what does the 4.3.0.5~ mean (especially the ~) ? [20:26] this is a versioned dependency on libsynthesis-dev. The package needs a version greater than the specified [20:27] and the ~ has a special meaning in Debian version numbers (it sorts below any other char) [20:28] the ~ allows it to be satisfied by a backport. Backports have ~ to make 3.4.0.5~bpo a lower version htan 3.4.0.5 === xfg is now known as zul [20:29] hm. then i don't understand the error. libsynthesis-dev is available in version 3.4.0.5 in debian sid. [20:31] login into your sid pbuilder and try to install it. don't know about aptitude, but apt doesn't tell the real error (down the dependency chain) but only that a dependency of the package you want installed, can't get installed [20:33] geser, i had to do a "apt-get update" before i can install the package. pbuilder doesn't do this automatically? [20:33] no, "pbuilder update" does it (updates the whole base.tgz including the Packages files) [20:34] ah. "pbuilder update" does this. [20:34] geser, thanks!:) [20:35] you can add a pbuilder hook to apt-get update before each build [20:35] there's such a script in the examples directory, IIRC [20:36] ari-tczew: ping [20:44] bdrung: pong [20:51] ari-tczew: am i allowed to do the fakesyncs (bug #512430) under my name? this would be faster for me. [20:51] Launchpad bug 512430 in geronimo-jpa-3.0-spec (Ubuntu) "Fake sync geronimo packages (main) from Debian testing (main)" [Undecided,New] https://launchpad.net/bugs/512430 [20:52] bdrung: I'm not happy for hearing this. [20:52] ari-tczew: the alternative would be patch dch [20:52] dch is not able to sponsor a changelog [20:53] but i am not a perl hacker [20:54] bdrung: you know, I need these uploads this time. I'll be owe to you. [20:54] ari-tczew: you need them? [20:54] bdrung: DEBFULLNAME="foo bar" DEBEMAIL="foo@baz" dch ... doesn't work? [20:54] Nobody ever needs uploads. [20:55] bdrung, I had to add a -k option to the ack-sync script to pass the signing key to syncpackage [20:55] Upload count isn't especially meaningful, especially if those are from syncs. [20:56] yea, same method like uploading merges [20:56] geser: DEBFULLNAME and DEBEMAIL should be only set for this command. let me look at the code... [20:57] and if one needs those fakesyncs for the sponsored upload count, then I'm not sure if one is ready to apply [20:57] geser: he has done enough (sponsored 40 - 50 packages for him) [20:59] it was more generally speaking [20:59] bdrung, should I push the change or you have something similar locally? [20:59] and in this case the few not counted fakesyncs shouldn't matter [20:59] fabrice_sp: you can push - i have no local changes [21:00] ok [21:04] geser: I could be late for tomorrow's meeting, because we have flood in country and can be public communication problems. [21:04] s/geser/persia [21:06] * micahg hopes they get to my item in the meeting :) [21:07] micahg: the "Mozilla Uploaders Package Set"? it's on the agenda [21:08] geser: yes, but the mail to the list wasn't approved till Friday so I was worried that it might not be on the actual agenda === emma_ is now known as emma [21:21] \sh: zf 1.10.5 most likely tomorrow, so I guess you don't have to push 1.10.4 [21:31] bdrung: what's next about fakesyncs? [21:55] ari-tczew: i have to improve the syncpackage script and use your bug for testing [21:56] bdrung: okay! fine! [23:13] guidance for naming a perl package.. if the CPAN module is Memcached::libmemcached ... the package still must be named this rather silly name: libmemcached-libmemcached-perl .. yes? [23:15] I have seen libxml-libxml-perl in the archive [23:16] So there is precedent, even if it is silly [23:18] I actually like it [23:19] I've installed many a perl module just by typing the transformed name after apt-get install.. its like a pleasnt surprise "yes, this is going to work today" [23:21] SpamapS: libmemcached-libmemcached-perl is correct. If you want to get it into Ubuntu, it would probably be easier to talk to the pkg-perl people in Debian since they sponsor new perl stuff all the time. [23:25] ScottK: will do. [23:37] In metacity, (and other gnome packages?) If you add a patch, should it be added before 90_autotools.patch and 99_ltmain_as-needed.patch in the series? [23:42] arand: yes [23:44] 90_autotools is to regenerate autotools file because of other patches, so it goes last, and 99_ltmain_as-needed goes after 90_autotools because it modifies a file autogenerated by 90_autotools, so if it went before, it would have no effect [23:44] pochu: aha, hm, is this documented anywhere? (news to me at least) [23:51] pochu: Right, it makes a lot of sense with the numbering, although, I've so far simply followed the ubuntu packaging guide by the letter, and used "quilt push -a && quilt new" regardless (slightly annoyed that some evil person had already taken all numbers in the patch prefixes :D), do over and do right, it seems... [23:54] you don't want to do that in these cases then :)