[00:00] an empty build target, not an empty build [00:03] azeem, what is it? [00:03] what is what? [00:03] azeem, an empty build target [00:04] Legendario: what is a non-empty build target? [00:04] or rather, what is a build target? [00:04] azeem, maybe both [00:04] no, I'm asking you [00:05] azeem, sorry. English is my second language, i don't program, and that does not make sense to me... [00:05] Legendario: why do you want to pack the source yourself then? [00:06] Legendario: or maybe otherwise asked, what would you do if the source had more than just an install script? [00:06] azeem, because I want to learn... and help [00:06] ok, then what kind of research did you do so far about "debian/rules build target"? [00:07] azeem, i have created 3 packages so far by following the packaging guide [00:07] that's all i know [00:08] ok [00:09] Legendario: the Debian Policy Manual probably discusses the various debian/rules targets, including the build target [00:09] gotta go now, bye [00:09] Legendario, a target in a makefile is a name for the collection of commands it runs [00:09] if you look in a debian/rules (or and Makefile), you will see it is formatted like this: [00:09] : [00:09] [00:10] if have not been run when is called, they are run first, in the order listed, and then are executed [00:10] "build" is one of the targets required in a debian/rules file, and it generally builds the sources into binaries [00:11] it could have a "configure" rule as a dependency, which would configure the build process to run [00:11] if the package has no sources that need building, you need not specify any rules, or any dependencies, but the target must still exist to comply with policy. [00:14] tsmithe, thanks for such a detailed explanation! [00:14] no problem. it's good to have new contributors willing to learn :) [00:17] slomo__, superm1: gmyth out of Debian NEW \o/ [00:17] next step --------> syncing! [00:18] * tsmithe can't wait to go through the same process for fluid-soundfont. that would be my first debian package :D [00:18] tsmithe, is there an easy way to edit the debian/rules in order to achieve it, or a model to follow. My bash scrit habilities are few... [00:19] Legendario, just do some research on makefiles, look at the debian policy and debian/ubuntu packaging guides/new maintainers guides, and play around with the files that are already there [00:19] i presume you used dh-make? [00:20] (to create a skeleton package) [00:20] Legendario: Also, try some non-CDBS packages. CDBS conceals all these targets. [00:20] use dh_make [00:20] RAOF, i realized that [00:20] yeah, don't use cdbs until you know how the system works ;) [00:26] morning all [00:27] hola Hobbsee [00:28] thanks tsmithe [00:28] and RAOF [00:28] no problem [00:30] hiya Hobbsee and LaserJock [00:30] any suggestion on a makefile "tutorial"? [00:30] * nixternal pets kdevelop for doing the makefiles for me [00:31] tsmithe, a good one... [00:31] Legendario, sorry, but i'm sure google can [00:32] Legendario: what specifically are you having trouble with? [00:32] each line is a command executed in its own shell [00:32] the rest seems self-explanatory... [00:33] tsmithe, google has lots of those. I was hoping there is a reference one [00:34] LaserJock, i am trying to pack a program that has only an install script [00:34] * tsmithe just learned by example, so he doesn't have much to recommend [00:34] got to know i have to learn more about makefiles... [00:35] Legendario: it's really easy thought [00:35] *thought [00:35] bah [00:35] hehe [00:35] *though [00:35] there [00:35] ;) [00:35] Legendario: as azeem said you need an empty build rule [00:35] I'm new and I read that I could help out by compiling programs, where do I find the programs (packages) that need to be compiled? [00:35] Legendario, what don't you get about makefiles? i explained the structure... [00:36] MECU: are you familiar with Debian/Ubuntu packaging? If not, check out https://wiki.ubuntu.com/PackagingGuide for some information on that [00:36] Legendario: each rule (the unindented part that has a :, like configure:, build:, etc.) has the lines that are need to build the package [00:36] sigh. how does one make wine behave now? [00:37] MECU: https://wiki.ubuntu.com/MOTU has a todo list and more information as well for you [00:37] yes, I just read though that, okay, thanks nixternal [00:37] Hobbsee: you think you are jesus or something? You think you can make wine do whatever you want? :p [00:37] hehe [00:37] or at least run [00:38] wouldn't that be: cp water wine ? [00:38] I haven't tried running the ie4linux stuff..let me see [00:39] Hobbsee: You browbeat \sh until he fixes it. [00:39] yup, wine isn't working here [00:41] LaserJock, it has a build and a build-stamp section. How do i call the install script? [00:41] * Hobbsee sighs [00:41] why give me an executable to unzip something, anyway... [00:41] Legendario: you do that in the install: rule [00:41] could someone upload https://bugs.edge.launchpad.net/ubuntu/+source/mscore/+bug/195179 please? (to clarify, i don't think it requires a FFe) [00:41] Launchpad bug 195179 in mscore "Please update mscore to 0.9.1d+dfsg-0ubuntu2 (debdiff attached)" [Undecided,New] [00:45] LaserJock, like adding $(CUR_DIR)/install.sh [00:45] right [00:45] LaserJock, should i erase the build and build-stamp sections? [00:46] keep build: it's required [00:46] Hobbsee: By installing the Gutsy package from winehq, sadly. Or possibly rebuilding our package locally with an older gcc. [00:46] but it can be empty [00:46] RAOF: right [00:46] Hobbsee: It hasn't been all bad. I learnt about aptitude forbid-version :) [00:46] RAOF: Wine doesn't like gcc 4.2? [00:46] LaserJock, what about the build-stamp one? [00:47] StevenK: Apparently building with an older gcc makes wine not segfault immediately. [00:47] Legendario: you can remove it and any references to it [00:47] StevenK: I haven't tested this personally. [00:48] Legendario: The build-stamp target is there to make sure the source gets built exactly once; you'll notice that the last thing it does is to create a file called "build-stamp". [00:48] Legendario: This means that if someone calls the build: target again, build: will see that the build-stamp file already exists, and so won't call the target again. [00:50] LaserJock, thanks... I learn a lot every time i get here. And by packaging, i learn a lot of computing too... ;-) [00:51] LaserJock, but i think this could be added on the packaging guide [00:51] well, it's a wiki, everybody is more than welcome to help :-0 [00:51] :-) rather [00:53] LaserJock, after i get good on it... I may try it. :-P [00:53] geser: bug #195453 - should xen-unstable also be blacklisted for sync? [00:53] Launchpad bug 195453 in xen-source "Please remove xen-{source,unstable} from hardy" [Undecided,Fix released] https://launchpad.net/bugs/195453 [00:56] LaserJock, the install section has a build option. Am I supposed to erase it too? [00:57] Legendario: By "build option" you mean "declares a dependency on build", right? Since you don't actually need to build anything, you can either leave that in (since build is empty), or preferably remove it. [00:58] Legendario: As in: the makefile contains a line "install: build", right? [00:59] RAOF, that's it [00:59] Right. So that says "you have to run the build target before the install target". Since your build target does nothing, this is harmless but unnecessary. [01:01] ok [01:03] dang, I can't figure out why my old laptop is sooooo slow === ogra_cmpc_ is now known as ogra_cmpc [01:04] I did a fresh Gutsy install and it seems way slower than before [01:15] huh? qa.ubuntuwire.com is still not operational [01:17] haven't seen imbrandon around either for a bit [01:21] He was seriously sick in bed a few days ago (I called him). [01:21] superm1: so someone really run gnome-lirc-properties. seems i've got a victim of having a symlink to my working copy in /usr/lib/python2.5/site-package [01:22] superm1: so i forgot to update Makefile.am, when renaming the module === Spec is now known as x-spec-t [01:22] superm1: strange that automake didn't complain [01:23] tbf, well the project is of particular interest to me :) [01:23] tbf, so i wanted to see how well it worked [01:25] tbf, you had some comments somewhere in the package about the confusion about only debian/ubuntu using lirc.hwdb [01:26] that's because we (Ubuntu) are the first to adapt using it [01:26] the idea is supposed to be that eventually everyone will though [01:26] https://code.fluendo.com/remotecontrol/trac/browser/trunk/data/receivers.conf [01:27] yup that's where I was reading :) [01:27] superm1: lirc.hwdb was a good idea, but it doesn't provide the information needed for auto-detection [01:27] tbf, well the spec can still be changed upstream [01:27] have you talked to Chris B. about it already? [01:27] on the lirc-list [01:28] superm1: currently i try to get code package ready before the hard beta freeze... :-/ [01:28] tbf, ah. [01:29] superm1: but the file format i have now seems to work for me... [01:29] well if you need some help, someone on my team (~mythbuntu), will probably be willing to help [01:29] he wanted to do a similar spec [01:29] but never got around to it [01:29] https://code.fluendo.com/remotecontrol/trac/browser/trunk/bin/build-receiver-list [01:29] tbf, you should know though, inside ubuntu we have a special patch (that upstream hasn't accepted yet) [01:30] tbf, that allows a lircd.conf to be "included" in the system wide one [01:30] this script generates a slight variation of that receivers.conf by scaning the source code of lirc [01:32] superm1: guess i really should send a mail about that script and the file-format to the lirc-list tomorrow [01:32] tbf, yeah, sometimes Chris is a little slow responding [01:32] so that would be worthwhile [01:33] superm1: i'd also highly appreciate (manual?) updates to the receivers.conf file.... [01:33] superm1: currently it is quite empty [01:34] superm1: i say "manual", cause of the timeframe needed, to get annotations into the lirc code [01:34] tbf, well let me put you in touch with the chap on my team that was looking to work on this [01:34] tbf, if hang around #ubuntu-mythtv-dev and idle for a bit, his name is foxxbuntu [01:58] Heya gang [03:05] ember_: I've got orca covered. [03:09] TheMuso, ah you were the one that pre-empted all the changes to ubiquity not running as root right :) [03:09] for orca? [03:09] superm1: Yep, haven't been able to test them so far, but hope to do that this afternoon. [03:09] TheMuso, well they broke the mythbuntu frontend i found out :) [03:09] superm1: So I saw, but it was an easy fix, again from what you wrote to -installer. [03:09] yeah it was [03:10] just had to track down any possible points of failure [03:10] Yeah. [03:13] Why isn't libgnutls26 in Hardy? [03:21] Wow! The motu release bug list is quite long. [03:21] TheMuso: Are you in the release team? [03:23] TheMuso: Ah! You are! [03:23] mok0_: Yes I am, and I'm having a look over it, after neglecting it for a while, due to other work. [03:25] mok0_: I'm assuming that collect4 has not yet been uploaded yet? [03:25] TheMuso: I have 2 acks on 194219 but I don't know why it's still on the list, or what has happened to it [03:25] gah bad english [03:25] bug 194219 [03:25] Launchpad bug 194219 in collectd "[needs-merge] collectd (4.3.0-1)" [Undecided,Confirmed] https://launchpad.net/bugs/194219 [03:25] Heh two minds... [03:25] ah yes, looking atht ath now [03:25] I'll review and upload it then. [03:26] mok0_: ummm. No bug number in teh changelog, there is a placeholder for one, but... Its not there. [03:27] Ach. [03:27] Forgot, can you put it in? [03:27] mok0_: And, the only two files touched by the debdiff are debian/control, and debian/changelog. Should there be more? === zakame__ is now known as zakame [03:28] TheMuso: That's it iirc [03:28] Well what is being changed? [03:28] TheMuso: It is basically taking over Debians new pacakge [03:28] So shouldn't it be a sync? [03:28] Well, yes, if possible at this time [03:29] mok0_: Well, I suggest you re-examine the bug, and the package, and if so, change the package description to a sync request. [03:29] TheMuso: arair I noted in the changelog that it should be synced next time [03:30] mok0_: I'm confused... Why next time? [03:30] I assumed this was the way to do a FFE [03:30] I didn't know I could just do a sync request [03:31] An FFE can still be a sync, as long as the requested information is given, and 2 acks are given. It doesn't have to be a merge/upload. [03:31] TheMuso: and I need some uploads :-) [03:31] An FFE is just that, an FFE, a request to change the package in a major way, whether it be via a sync, or a upload/merge etc. [03:31] mok0_: When a package is synced, you still get credit for requesting it. [03:32] TheMuso: cool :-) [03:32] TheMuso: How does the sync happen in practice? [03:33] TheMuso: someone has to fetch it and upload [03:33] mok0_: The archive admins have powers to directly copy the package from Debian. [03:33] Nobody uploads it. [03:33] mok0_: I'm assuming you have never requested a sync before. [03:33] TheMuso: that's right [03:34] TheMuso: so, I just change the bug description? Is there a tag? [03:34] mok0_: No. Let me find the wiki page describing the sync process. [03:35] Thx [03:35] mok0_: https://wiki.ubuntu.com/SyncRequestProcess [03:37] TheMuso: looks easy enough... most of the requested info is already attached to the bug [03:37] mok0_: Well, have a look over the bug as it is now, and change the description to a sync request and you'll find out soon enough whether you've given enough information. [03:38] TheMuso: ok [03:38] TheMuso: I have 1 ack on another package: 156100 [03:39] bug 156105 [03:39] Launchpad bug 156105 in moblin-multimedia "prompt error message when start playbacking wma media" [Medium,Fix released] https://launchpad.net/bugs/156105 [03:40] mok0_: Ok will have a look now. [03:40] TheMuso: great, I can answer questions [03:42] mok0_: err, is that the correct bug number? [03:42] oh i got it wrong [03:42] bug 156100 [03:42] Launchpad bug 156100 in storm "[hardy] please upgrade storm to version 0.12" [Undecided,Incomplete] https://launchpad.net/bugs/156100 [03:42] yes [03:42] heh [03:42] TheMuso: 0.12 closes a bunch of bug reports [03:43] TheMuso: ... and besides, when we bitch at Canonical for not opensourcing their stuff, we should be on top of it when they publish updates to storm [03:43] mok0_: You need to attach everything else relating to an FF, diffstat, changelog, build and install logs... [03:44] TheMuso: ok [03:44] TheMuso: install logs? [03:44] mok0_: Yes. We need to know that the package installs and updates correctly. [03:45] mok0_: https://wiki.ubuntu.com/FreezeExceptionProcess explains everything., [03:45] TheMuso: thx [03:45] TheMuso: it's getting time for bed for me, I'll do it tomorrow [03:46] TheMuso: but the other bug I will change in a minute [03:47] mok0_: Ok thanks. [03:49] Well goodnight, see you later! [03:50] persia: around? [03:59] hello. [03:59] how do i use dh_intallman? [03:59] how do i use dh_installman? [04:05] man dh_installman and man debhelper will give useful pointers, but generally the answer is to just call dh_installman in the appropriate debian/rules target. [04:07] And like the rest of debhelper, having a debian/$packagename.manpages should make it just work. === boomer` is now known as boomer [04:13] RAOF, i've read the man pages, but it didn't make any clear. There is even a bug about it (Bug #184156). I am calling it on debian/rules but the package created doesn't have the man page. [04:13] Launchpad bug 184156 in debhelper "man page of dh_installman incomplete for newbie" [Undecided,New] https://launchpad.net/bugs/184156 [04:17] RAOF, am i the one supposed to create the packagename.manpages or does the dh_installman the one who handles it? [04:21] leonel: You create that file. [04:21] gah === _Apollo_2 is now known as _Apollo_ [04:50] pochu: I just uploaded a (hopefully) fixed pychecker. Your turn to work on SPE. [05:14] pochu: i'll upload new gst-plugins-bad tomorrow probably... i want the things available everywhere to prevent failing builds again and get it into testing soonish [05:49] superm1: http://buildd.debian-ports.org/status/package.php?p=gmyth <--- fails on kfreebsd, might want to notify upstream about that or give a patch ;) [05:50] kfreebsd?, didn't even know that it would automatically be added to different ports [05:50] i'll bring it up with upstream [05:50] still waiting to hear back on the -upnp stuff [06:00] superm1: the kfreebsd patch is probably easy, will take a look at it later if you didn't before :) [06:00] slomo__, do you have a kreebsd env to work from? [06:01] can one be created in a pbuilder directly? [06:01] superm1: no idea, i assume it's an obvious bug :) [06:01] hehe === lando_ is now known as lando [07:03] good morning [07:03] good morning to you sir [07:04] hey nixternal - how are you doing? [07:04] not to shabby...coming down off of my busy spell at the uni [07:04] installing Ubuntu on my desktop so I can test some of the Gnome/KDE4 issues that I have been reading about [07:05] oh... what are they about? [07:05] nixternal: great to see you're in 5-a-day as well :-) [07:05] some reason people are seeing klauncher crashes when logged into Ubuntu [07:05] ugh :/ [07:05] oh ya, trying to take the lead in 5-a-day :) [07:05] I noticed :-))) [07:06] it started out as 5-a-day, but as I sat in on classes at the uni, I started doing 20 to 60 a day listening to boring lectures :) [07:06] it seems the project grew so much that committing bugs you've worked on takes a while :) [07:06] I noticed that today [07:06] I'll try to work something out to fix that [07:06] so everybody commits to their own branch [07:07] which will make the statistics a bit more complicated, but it's going to befine [07:07] actually, I did my add-5-a-day, and it updated the branch, and between the time it finished updating the branch and committing mine, someone had committed, which caused add-5-a-day to crash out because the branch was out of date [07:07] in 5 seconds I would say [07:07] oh... crash? [07:07] yup [07:07] wasn't it just bzr complaining? [07:07] please give me the backtrace if that happens again [07:07] it was [07:07] wasn't a backtraceable crash [07:07] Why not have people commit to their own branch, then have some script running somewhere that watches lots of branches and merges them into the main one? [07:07] ah ok [07:08] someone had committed in between the update and my commit, in between the 1st and 2nd stage of add-5-a-day [07:08] Fujitsu: probably not even necessary to merge them into a main branch [07:08] Good morning! [07:08] Fujitsu: but yeah, that'S the basic idea [07:09] we could even make it so that people push their changes to multiple branches (I'd commit to dholbach and ubuntu-berlin for example) so that teams could compete against each other :) [07:09] it makes statistics a bit hard to figure out, but I somehow like the general idea :) [07:09] that sounds like fun [07:10] * Fujitsu declares universe to be too big. [07:13] according to einstein there's nothing bigger... [07:14] Heh. [07:15] you may splitt it up into multiple galaxies, but their number would be endless [07:15] :-) [07:15] [08:19] can someone help me with a booting problem? [08:19] * Hobbsee suggests #ubuntu for support [08:20] i've asked in there and no-one seems to be responding [08:20] i've asked questions before and got directed here so i thought i would cut out the middleman [08:21] for packaging? [08:21] yes, before it was a .deb packaging problem [08:22] which is why that was on topic. this isn't, sorry... [08:22] this time though, no kernel since 2.6.24-2 has got past "loading kernel drivers" [08:22] i didn't know this was a packaging channel, sorry [08:23] * Hobbsee suggests reading the /topic [08:23] just read the wiki, sorry === rraphink is now known as raphink [09:00] slangasek: re xen-unstable: it should probably be also added to the sync blacklist as it build-depends on linux-support-* which isn't available in Ubuntu (and xen-3.0 and xen-3 are also on the sync blacklist) === Amaranth_ is now known as Amaranth [09:32] hi === Amaranth_ is now known as Amaranth [10:19] superm1: kfreebsd fixed ;) [11:10] TheMuso: ping [11:10] Hobbsee: Yes, what can I do for you? [11:11] TheMuso: how do you want to handle https://bugs.edge.launchpad.net/ubuntu/+source/ubuntustudio-icon-theme/+bug/192535 which now has it's MOTU-uvf ack? [11:11] Launchpad bug 192535 in usplash-theme-ubuntustudio "FF: General exception for Ubuntustudio packages." [Wishlist,Confirmed] [11:11] pochu: I finally filed the freeze exception, sorry for the delay. #195733 [11:12] Hobbsee: What do you mean exactly? [11:13] Don't bugs of that class just get closed at BetaFreeze / ArtworkFinalDeadline? [11:25] Ng: I'm not in motu-release, but I'd like the updates: remember to include the installation log and testing report. [11:25] TheMuso: in particular, i'm about to unsubscribe us - are you intending to mark it as fix released or anything? [11:27] <\sh> guys...netbeans is crashing on hardy amd64...can someone prove this? [11:28] \sh: Give me a test case, and I'll give it a shot (and try to arrange a patch). [11:29] <\sh> persia: just start it with sun-java6 installed [11:29] <\sh> /usr/share/netbeans/6.0.1/bin/../platform7/lib/nbexec: line 440: 4491 Aborted (core dumped) [11:29] * persia tends to avoid multiverse java, but tests [11:29] Hobbsee: No, was just hoping to get a standing freeze exception, and its also documented on the wiki page, so feel free to close/unsubscribe. [11:30] \sh: Do I need the jdk, or just the bin & jre? [11:31] persia: is the installation log literally just the output of me installing the build and it not doing anything out of the ordinary? [11:32] Ng: Yes. For extra points, provide logs for all of install, upgrade from current hardy, remove, and purge. [11:32] <\sh> persia: just jre [11:32] <\sh> and who forced me to upload xdebug? [11:33] TheMuso: that's what i'm thinking we're giving, yeah [11:33] \sh: Got it: that's bug #87947 [11:33] Launchpad bug 87947 in libx11 "xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed." [Medium,Fix released] https://launchpad.net/bugs/87947 [11:33] right, from 51 to 42. excellent [11:35] and down to 28. [11:36] * persia isn't convinced 87947 should be "Fix Released" as I'm currently finding about 8 dupes. [11:40] persia: what would be useful for the testing report? I'm not sure that "well there are probably half a dozen people using 0.8.1 or later and in regular contact with the project who haven't reported any serious bugs" will do ;) [11:41] Ng: Depends on the nature of the update. My previous testing reports have varied from "doesn't segfault on startup for me" to arranging for people with three different architectures to follow two use cases and report the results (odd issue with failing to render only some Youtube videos). [11:42] hmm [11:42] My understanding (and I'm not authoritative on this) is that you want to include enough information to convince the release team that the updates package (and any dependencies) work well enough to be released after the update. For terminator, it ought be fairly easy. [11:45] persia: ok thanks, I'll whip something up [11:51] Ng: I usually just cat all of the install/upgrade/remove/purge logs together in a single attachment. [11:53] persia: very wise, I realise I'm spamming the motu-release folks, for which I apologise [12:26] Hi [12:27] hey Iulian [12:28] Hi there thekorn === ember_ is now known as ember [12:38] ScottK: nothing to do in spe, it just was uninstallable as it depends on pychecker >= someversionthatwasftbfs ;) [12:38] ScottK: thanks for fixing pychecker [12:39] slomo_: re: gst-bad - no hurry, that's fine :) [12:39] ScottK: I setted it as high importance because it was uninstallable and not because it was spe. we do the same for ftbfs independently of the package [12:40] pochu: For everything? I thought most universe packages couldn't qualify for "High" except for license issues. [12:43] persia: hmm, I don't know, but infinity's MBF was done at high importance I think. Perhaps his check was done for main only [12:44] pochu: For main, failure-to-install or FTBFS is typically High. For universe, typically Medium, although some packages might have enough users to qualify for high. [12:45] persia: ok, thanks [12:48] pochu: Reviewing https://wiki.ubuntu.com/Bugs/Importance, I'd think that for universe it would have to be something like a significant component of one of the universe derivatives being broken in order to qualify for "Has a severe impact on a small portion of Ubuntu users", as I don't think anything is really popular enough for "Has a moderate impact on a large portion of Ubuntu users". [12:52] persia: wxwidgets ftbfs would qualify ;) [12:53] pochu: Ah. Maybe, at least for 2.6. There's likely a few other major universe libraries as well. [12:54] * ScottK thinks clamav and spamassassin would potentially qualify. [12:55] pochu: In that case (for spe) after you test it, I'd suggest it's fix released, not invalid. [12:55] Probably. There's a lot of dependencies, and a fair number of users. On the other hand, it's not likely true for spe :) === lionel_ is now known as lionel [13:21] http://www.paeps.cx/weblog/Linux/fuck_ubuntu WTF [13:32] He's entitled to his opinion. [13:40] I was asked to submit an install log to LP. Any particular way that needs to be done? [13:45] Hey [13:45] Do you know any good tools to import ~150 signed gpg keys reasonably quickly? [13:47] amarillion: Depends on what format you have the keys in... what problems does gpg --import give you? [13:48] hello there... i just saw tcl/tk 8.5 entering the repositories lately and an updated amsn compiled against 8.5 ... (first thing, make sure latest amsn package is marked incompatible with tcl/tk 8.4, ok?) but i found a problem [13:48] Ah I forgot to tell you, they are in my email right now, thunderbird [13:48] mok1: I've generally used the script command to capture my entries and the output. I typically do all of install, upgrade, remove, and purge to demonstrate that all the maintainer scripts do the right thing. [13:48] if someone has tcl/tk 8.5 and tcllib from the gutsy repositories, amsn won't start [13:48] Is there a tool that can sort them out from a mbox or something? [13:49] it's a bug in snit 2.1 that is contained in the current tcllib package [13:49] mutt should be able to do it (open the mbox, tag everything and tell it to snarf the keys) [13:49] they told me that the latest snit release fixes it. but snit 2.1 contained in tcllib 1.9.dfsg1-1 is VERY problematic with tcl/tk 8.5 [13:49] snarf? Ok I'll look into it [13:49] so it should cause problems to other applications too, not just amsn [13:49] vivia: You likely want either #ubuntu-bugs, or to report a bug from https://launchpad.net/ubuntu/+source/tcllib/+bugs [13:50] persia: sure, going to report it there... thanx ;) [13:50] vivia: Thanks for tracking it down, it's just that we're ill prepared to handle bug reports in IRC. [13:51] persia: it's ok, we often have it on amsn too, and amsn is a MUCH smaller project.. :) [13:51] persia: the script command, thank you! Never heard of it before. You're never to old to learn something new.. [13:52] * persia thinks the script command is older than several developers :) [13:53] how can i check whether my current amsn package is incompatible with tcl8.4 ? === neversfelde_ is now known as neversfelde [13:53] heya people [14:07] https://bugs.launchpad.net/ubuntu/+source/tcllib/+bug/195785 there you go, i filed it... i'd appreciate it if anyone could check it and tell me quickly whether more info is needed [14:07] Launchpad bug 195785 in tcllib "snit 2.1 contained in tcllib 1.9.dfsg1-1 incompatible with tcl/tk 8.5" [Undecided,New] [14:08] wow, thanx ubotu [14:08] nice bot you've got there :) [14:10] broonie, did you ever participate in a key signing party? [14:12] Has anyone here participated in a key signing party? [14:14] amarillion: yes [14:15] So how did you learn how it works? [14:15] I don't really understand it [14:15] I mean, I understand the theory, but the documentation is very skimpy on the details [14:16] You mean the actual process for doing things? That differs depending on how the event is organised. Whichever way it's just a way to do an individual signing in bulk. [14:17] If I'm going to do this with thunderbird, I now have to open 150 emails, save the attachment, (type in a different name for each of them or thunderbird will overwrite) unencrypt and then import [14:18] Probably I can find a way to automate things with mutt but then I'd have to learn to use mutt first [14:18] amarillion: the main problem with KSPs is: how do you get a bulk of people to check each others identities in an ordered way and in a minimum of time [14:18] geser, yeah, it was reasonably efficient at fosdem this year [14:18] heya geser :) [14:18] amarillion: mutt has a direct command for "import key from this e-mail" [14:18] I hear it was a mess in previous years [14:19] broonie, ah, which is it? I can't find it in the help [14:19] amarillion: Debian people have expierence at doing a KSP, I was at the FOSDEM KSP last year [14:19] There is a command in mutt to decrypt it [14:19] amarillion: C-k [14:19] amarillion: ^K extract-keys extract supported public keys [14:20] great, thanks [14:21] I suppose everybody uses mutt for this? Doing this in thunderbird seems impossible [14:21] <\sh> whoever proposed php5-xdebug THANK YOU SOO MUCH ! [14:22] <\sh> amarillion: enigmail is your friend I think [14:23] \sh: is it with enigmail as easy as in mutt to import keys from a KSP? [14:24] amarillion: install signing-party and use caff [14:24] man-di, I used caff to send out the signed keys [14:24] yes, for sending out signatures caff is really good [14:24] <\sh> geser: for this you use caff and a local smtp [14:25] <\sh> geser: and for importing keys...I'm using a shell script...adding sigs to my key I do it manually... [14:27] Ok, I have everything imported. Thanks broonie [14:28] amarillion: don't forget to update your key on the keyservers [14:28] stani: Is everything in good shape for SPE in Hardy now? [14:28] geser, I will, thanks [14:30]