[00:06] <asac> maco: huh?
[00:07] <asac> it should show up in tray if you start it manually
[00:07] <asac> nm-applet --disable-sm
[00:07] <asac> maco: so how feature complete is the plasma applet?
[00:18] <maco> asac: it works. it has some gui bugs. like the vpn has jumped to the top of list so that all but the first network visible is cut off right now. its supposed to look just like nm-applet basically
[00:18] <maco> asac:  nm-applet --disale-sm
[00:18] <maco> ** (nm-applet:11425): WARNING **: <WARN>  applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service as it is already taken.  Return: 3
[00:19] <yuriy> maco: I think you need to quit knetworkmanager before nm-applet will start
[00:19] <yuriy> i'm using nm-applet because knetworkmanager makes nm crash when connecting to our WPA2 network
[00:21] <maco> oh
[00:24] <maco> apparently need to lose the plasmoid too
[00:41] <asac> maco: disable your kde applet ... should be possible in kde
[00:44] <maco> asac: ill try that next time networking decides to hate me. at the moment i'm online and going "if i dont touch it, it wont break"
[00:45] <nhandler> Has there been any news on 5-a-day recently? I thought I heard that they were planning on releasing a new version of it before the Global Bug Jam
[00:47] <bdmurray> nhandler: we are still working on it
[00:48] <nhandler> bdmurray: Are you still planning on releasing prior to the global bug jam? Or is it going to take some more time?
[00:48] <bdmurray> nhandler: I'm not certain dholbach is doing most of the work now
[00:48] <nhandler> bdmurray: Ok, I'll send Daniel a message tomorrow when he is online
[03:23] <mrooney> what is the proper thing to do for a bug, suggesting that a package be installed by default
[03:23] <mrooney> and what package should that be against?
[03:23] <mrooney> specifically this is bug 311389
[03:25] <nhandler> mrooney: I think you want ubuntu-meta
[03:35] <mrooney> nhandler: cool
[03:35] <mrooney> I sure do agree with that bug :)
[07:13] <dholbach> good morning
[07:14] <sfturn2009> morning :)
[07:15] <dholbach> hi sfturn2009
[07:15] <sfturn2009> hrllo
[08:16] <Rafik> hello, I want to participate a bit in todays bugday
[08:16] <Rafik> this is my first time :)
[08:31] <thomasdelbeke_> Hi
[08:31] <thomasdelbeke_> the medubuntu rep is down
[08:32] <thomasdelbeke_> http://paste.ubuntu.com/117171/
[08:32] <thomasdelbeke_> the jaunty-alternate rep is finally fixed
[08:32] <thomasdelbeke_> where to report this?
[08:33] <maco> thomasdelbeke_: to whomever is in charge of medibuntu
[08:34] <maco> that's 3rd party
[08:34] <thomasdelbeke_> thanks
[08:34] <thomasdelbeke_> how to lookup
[08:34] <maco> *shrug*
[08:34] <thomasdelbeke_> google it?
[08:34] <Rafik> thomasdelbeke_> https://bugs.edge.launchpad.net/medibuntu/+filebug
[08:34] <maco> if the site was up they'd probably have a contact link
[08:34] <maco> they use launchpad?
[08:35] <thomasdelbeke_> file a bug now?
[08:35] <maco> its probably that they're rebooting the server after updating it and if you wait like a half hour itll be back
[08:35] <thomasdelbeke_> ok
[08:35] <thomasdelbeke_> I do that first
[08:35] <thomasdelbeke_> thanks
[08:36] <thomasdelbeke_> I will see in half an hour
[08:36] <thomasdelbeke_> I only used it to install skype anyway
[08:37] <thomasdelbeke_> deceptive name
[08:37] <thomasdelbeke_> med ubuntu
[08:37] <thomasdelbeke_> http://paste.ubuntu.com/117174/
[08:37] <thomasdelbeke_> cu
[08:37] <maco> medibuntu
[08:37] <maco> for media
[08:38] <maco> theyre some people who decided to package up useful media things for ubuntu
[08:38] <maco> skype.com has a deb though, doesn't it?
[08:38] <thomasdelbeke_> yeah
[08:38] <thomasdelbeke_> i know
[08:38] <thomasdelbeke_> I will do it that way
[08:38] <thomasdelbeke_> in the future
[08:39] <thomasdelbeke_> their deb is still not signed!
[08:39] <thomasdelbeke_> ridiculous
[08:39] <thomasdelbeke_> but i need them
[08:39] <thomasdelbeke_> tx
[08:39] <thomasdelbeke_> cu
[10:00] <askand> Is there a need to file a bug for versions to get upgraded in Jaunty?
[10:02] <maco> askand: if you know there's been a new upstream version and its in debian, file a merge request. if its not in debian, file a needs-packaging (i think) bug
[10:02] <maco> theres only a week left for these to be filed and packaged though
[10:02] <maco> also check the Needs Packaging report
[10:03] <maco> http://qa.ubuntu.com/reports/needs-packaging/needs-packaging-popularity.html
[10:04] <maco> if you see it on there, go to the bug page for it and click "change" next to "does not affect me" so youll be voting for it by marking it as affecting you
[10:11] <askand> maco: debian does not have the latest version but Ubuntu have a version that is newer then debian
[10:11] <askand> but not the latest still
[10:11] <maco> ok
[10:11] <maco> file a bug asking that it be updated to lastest stable. start the bug title with [needs-packaging] and tag it needs-packaging
[10:12] <maco> or hmm
[10:12] <maco> i think it should count as needs-packaging even if its an update
[10:12] <maco> dholbach: ping?
[10:19] <jpds> maco: I'm testing building spim, if successful, I'll upload the package.
[10:19] <maco> jpds: ok. thanks. i did pbuilder, install, remove, check all files were gone, and purge before uploading to revu though ;)
[10:20] <maco> er, test was between install and remove
[10:20] <jpds> maco: I like to double check ;-)
[10:20] <maco> thats fine
[10:23] <BUGabundo> hi maco
[10:23] <BUGabundo> good morning, girl
[10:23] <BUGabundo> and everyone else too
[10:23] <BUGabundo> (or late night if that is your timezone) hehe
[10:24] <maco> 530am = late night
[10:25]  * ogra would call that (way too) early morning 
[10:25] <ogra> :)
[10:27] <maco> ogra: yeah but i start class at 11 so i get out of bed at roughly 10:52am
[10:27] <BUGabundo> ehehe
[10:27] <BUGabundo> she's a batgirl
[10:27] <BUGabundo> or uses all her time to be EVERYWHERE
[10:27] <ogra> heh
[10:28] <BUGabundo> I don't know how maco manages to be on so many IRC channels, LP bugs, and still manage the ubuntu-users ML
[10:28] <BUGabundo> I subcribe to it, but just read some email from the headers!
[10:28] <BUGabundo> 300-400 new emails per day goes WAY behond my limit
[10:30] <maco> BUGabundo: i dont
[10:30] <maco> BUGabundo: im not even subscribed to that list
[10:30] <maco> think i want *more* tech support?
[10:30] <maco> yeesh
[10:31] <BUGabundo> eheh
[10:31] <BUGabundo> I've seen a few emails from you there!
[10:31] <BUGabundo> but I guess you now ascended to higher tecnological lists
[10:32] <BUGabundo> aka devel-disc and stuff
[10:32] <maco> if i sent any mails there they were responses to cross-posts
[10:33] <maco> im on -qa, -devel-discuss, -devel, kernel-team...i think that's all. the last 2 i rarely talk because i dont really fit in there
[10:34] <BUGabundo> yeah
[10:34] <BUGabundo> same as me
[10:34] <BUGabundo> but I finally got (close) to zero inbox on the Ubuntu lists
[10:34] <maco> hahaha. i have like 3000 mails in my inbox
[10:34] <maco> thats after i deleted about 5000
[10:34] <BUGabundo> left are users (60k emails) and markting (500 emails)
[10:35] <BUGabundo> I just make users ML expire after 15 days or something to a subfolder
[10:35] <BUGabundo> that's why Kmail says I have 85k unread emails
[11:00] <dholbach> maco: pong
[11:41] <andresmujica> didn't knew that something like this could be done: http://www.delhage.se/rhelstats/
[11:42] <andresmujica> something like irc support stats... good thing for our LP friens and the karma thingie
[12:04] <pedro_> folks remember that today we're having another Hug day, this time based on the bugs without a package: https://wiki.ubuntu.com/UbuntuBugDay/20090212
[13:54] <pedro_> come on Bugsquad we still have a few bugs to assign to the right package: http://wiki.ubuntu.com/UbuntuBugDay/20090212
[13:55] <pedro_> triage them soon or the mangilic and Mrkanister machines are going to left nothing for you
[14:22] <thekorn> happy hugday everybody!
[14:22]  * thekorn hugs channel
[14:25] <pedro_> happy hug day to you too thekorn!
[14:27] <thekorn> pedro_: hi, what's the correct package for translation bugs in kde
[14:27] <thekorn> german language
[14:27] <thekorn> hmm looks like language-pack-kde-de-base
[14:28] <pedro_> language-pack-kde-locale ?
[14:28] <pedro_> right
[14:41] <thekorn>  /hugday close 323802
[14:41] <thekorn> sorry
[15:06] <bddebian> Boo
[15:06] <BUGabundo> foo
[15:08] <bddebian> :)
[15:09] <BUGabundo> ohh Pici didn't reply back with "bar"
[15:10] <Pici> baz
[16:39] <maco> dholbach: i was going to check with you that i was telling askand the right thing about requesting version upgrades before feature freeze
[16:39] <maco> they logged off though
[16:43] <bdmurray> Does anybody know what they mean by 'root terminal' in bug 326158?
[16:51] <charlie-tca> Alt+F2 ?
[16:51] <charlie-tca> gksu terminal
[16:52] <charlie-tca> just a guess
[16:52] <maco> what are you trying to do?
[16:55] <bdmurray> maco: triage bug 326158
[16:57] <maco> oh. yeah. that's kinda useless on the info...
[16:57] <bdmurray> I do seem to recall a menu entry like that somewhere
[16:58] <BUGabundo> bdmurray: it is still there
[16:58] <charlie-tca> That's right, Add/Remove allows a root terminal to be added to the menu, doesn't it?
[16:58] <BUGabundo> SystemTool -> Root terminal
[17:01] <maco> i thought automatix was how people went about getting those things. were they duplicating effort (again)?
[17:01] <BUGabundo> maco: I don't have automatix
[17:01] <BUGabundo> and I have it in there
[17:10] <awsoonn> There are quite a few bugs relating to a lack of wireless connection after suspend, I am wondering if there is a meta bug or some other bit of tidbit I should know before filing yet another one?
[17:11] <bdmurray> awsoonn: there should be no metabug for that because it is driver specific
[17:12] <bdmurray> it's highly dependant on your hardware
[17:13] <maco> i'm not in gnome right now, so no idea what that .desktop looks like
[17:16] <bdmurray> mvo: I noticed add/remove programs has 2 update-manager entries, one of which is for hildon udpate-manager - this seems rather confusing to me
[17:16] <mvo> bdmurray: oh, good catch
[17:16] <mvo> that needs to be fixed
[17:17] <mvo> bdmurray: fixed in bzr now
[17:17] <bdmurray> mvo: great!
[17:17] <bdmurray> What did it get fixed in?
[17:18] <mvo> bdmurray: app-install-data-ubuntu (source package)
[17:26] <awsoonn> Bug 264683 - Seems like we could automate the workaround as part of jockey, would this be a bad idea?
[17:26] <maco> awsoonn: its just that its not re-listening for beacons
[17:27] <maco> it could be changed to re-listen and re-populate on each resume, but then thatd mean having to wait for the network list even when you're in the same place
[17:27] <awsoonn> but it fails even when I'm in the same place
[17:28] <awsoonn> and the wait was not unbearable, it took about 7 seconds to finish reconnecting, in any case your way seems to be 'the right way" (TM)
[17:29] <awsoonn> is that a simple thing to fix? I would love to know more about how to fix such issues. :)
[17:31] <awsoonn> mvo: what say you? in effort to have this issue resolved for Jaunty, what would be best?
[17:40] <mvo> awsoonn: network-manager? sorry, I do not know a lot about it :/
[17:45] <awsoonn> mvo: I was thinking more along the lines of making jockey produce one text file when it installed the Atheros drivers. I thought that you were a major force behind Jockey and so I wanted to get your input there.
[17:46] <pennerjudas_> hi
[17:46] <pennerjudas_> hi
[17:47] <mvo> awsoonn: pitti is probably a better person, my involvement with jockey is relatively small
[17:47] <awsoonn> noted, sorry 'bout that mvo
[17:48] <mvo> awsoonn: no problem
[18:11] <LaserJock> I've got a bit of a "how do I say this nicely?" question
[18:11] <LaserJock> I got a bug report about a package failing to install correctly
[18:12] <LaserJock> when I talked to the reporter I found out that he intentionally aborts installs at the configuration stage
[18:12] <LaserJock> so that he can configure them by hand apparently
[18:13] <LaserJock> is it bad for to mark the bug Invalid and say "please don't abort package installs"
[18:13] <LaserJock> *for me
[18:14] <hggdh> that's a good question...
[18:14] <hggdh> I would go with "please do not do that again" but, still...
[18:14] <LaserJock> I don't want to be rude, but I don't see how you can expect to abort installations and have it come out OK
[18:14] <hggdh> what is the bug #?
[18:15] <LaserJock> bug #325450
[18:16] <hggdh> how did the reporter cancel the dialog?
[18:16] <hggdh> reason I am asking: package installation should be able to survive users' screw-ups...
[18:16] <hggdh> and it seems it did not this time
[18:16] <maco> i like the title
[18:17] <maco> "Fails to uninstall after failing to install"
[18:17] <hggdh> yeah. Cool. And straight to the point
[18:17] <LaserJock> hggdh: this is what i got in an email from the reporter "As far as I can recall, there were none, but I did abort the configuration procedure for Moodle.  I prefer to separate the installation of a package from its configuration."
[18:17] <maco> can you just put "PEBKAC status invalid"?
[18:17] <LaserJock> the "there were none" was in response to my question about installation errors
[18:18] <LaserJock> I do think there is a problem with the package where if the installation fails you are unable to uninstall cleanly
[18:18] <hggdh> the way I see it, the user messed up. Nevertheless, now he has an inconsistent apt DB
[18:18] <LaserJock> but I believe I already have a bug for that
[18:18] <LaserJock> so maybe I should just dup it?
[18:18] <hggdh> LaserJock, the problem may be with the package or with apt
[18:18] <maco> i want to know how re-configuring manually is any more difficult than configuring manually to start with. why should he have to abort the install just to edit a couple config files?
[18:19] <hggdh> hear, hear
[18:19] <hggdh> maco, seems to be a preference issue with the reporter...
[18:19] <LaserJock> maco: he says he doesn't like packages setting things up like daemons, etc.
[18:20] <LaserJock> he told me he'd like it if I made it so that configuration is completely separate from installation
[18:20] <LaserJock> which I obviously can't do
[18:20] <maco> but i dont understand *why*
[18:20] <LaserJock> because he wants to configure it himself
[18:20] <hggdh> this, I think, is an unreasonable expectation. This is how we do; if the reporter does not like it, a brainstorm, or building from source, are currently the options
[18:20] <maco> what's the use-case where him configuring manually after dpkg does its thing makes life harder than configuring it manually to start with does?
[18:21] <maco> hggdh: or gentoo
[18:21] <LaserJock> maco: because presumabely he doesn't know what all the package configuration is going to do
[18:21] <hggdh> yes, indeed. But even gentoo will set up
[18:21] <LaserJock> in any case, it's something we can't do or support
[18:22] <hggdh> back to the issue: the package DB should not be left in an inconsistent status. This is a bug
[18:22] <LaserJock> hggdh: ok, so dup it then?
[18:23] <hggdh> LaserJock, perhaps explaining this is The Way Things Are Currently Done, and then dupping it to the other bug, yes
[18:23]  * hggdh thinks about reproducing the issue, and then shudders at the possible consequences
[18:24] <LaserJock> nah, it happens fairly often
[18:24] <LaserJock> though a VM might be more "safe"
[18:24] <hggdh> I already have all the VMs my current harddrive can hold...
[18:25] <LaserJock> this package makes me had .debs :-)
[18:25] <LaserJock> *hate
[18:25] <hggdh> this is probably not an issue with .debs per se, but more with unexpected user behaviour
[18:26] <bdmurray> ogasawara: is there a master bug for bug 324213?
[18:26] <LaserJock> hggdh: well, about 50% of the bugs for this package are from failed installation/upgrade
[18:27] <LaserJock> the packaging is a pain in the backside
[18:27] <ogasawara> bdmurray: for ath9k, not that I'm aware of
[18:27] <LaserJock> and its forked from Debian so I can't exactly report bugs upstream
[18:28] <hggdh> ugh
[18:29] <hggdh> then it would stand to reason that something should be done on the packaging
[18:29] <LaserJock> yep :-)
[18:30] <maco> ogasawara: can you answer what i just asked slangasek on bug 268429?
[18:30] <maco> (asking you because you're like the human incarnation of kdbg)
[18:30] <ogasawara> heh
[18:32] <ogasawara> bdmurray: I posted a comment to bug 324213
[18:34] <bdmurray> ogasawara: thanks, I'll mark you down on the hug day list
[18:34] <ogasawara> cool
[18:34] <maco> ogasawara: ive located slangasek, so nevermind
[18:34] <ogasawara> maco: ok
[18:47] <bdmurray> mvo: can you look the DkpgTerminalLog.txt in 323605?
[18:48] <mvo> bdmurray: sure, sec
[18:48] <mvo> bdmurray: the infamous dpkg trigger bug in intrepid :(
[18:48] <mvo> Processing triggers for gxine ...^M
[18:48] <mvo> Segmentation fault^M
[18:48] <mvo> dpkg: subprocess post-installation script returned error exit status 139^M
[18:49] <bdmurray> Is gxine the start of the problem?
[18:49] <mvo> bdmurray: yes, it segfaults in a trigger and that makes dpkg rather unhappy
[18:49] <mvo> https://bugs.edge.launchpad.net/ubuntu/+source/dpkg/+bug/323894
[18:49] <mvo> it contians workaround instructions
[18:49] <bdmurray> is that the bug we were talking about at the sprint?
[18:50] <mvo> bdmurray: yes
[18:50] <mvo> bdmurray: feel free do duplicate to either gxine or the dpkg one
[18:50] <mvo> bdmurray: its pulled from -proposed (and was there only for ~2 days or so)
[18:51] <mvo> but its really bad because it does not allow apt updates anymore
[18:54] <bdmurray> mvo: okay, so I want to look for other bug reports with gxine post-installation script errors?
[18:55] <mvo> bdmurray: yeah, if there is this message ("Processing triggers for gxine ...^M
[18:55] <mvo>  Segmentation fault^M") chances are nearly 1.0 that its this problem and causing more trouble afterwards
[18:56] <bdmurray> okay, I'll see what I can find
[19:23] <bdmurray> mvo: still around?
[19:23] <mvo> yes
[19:24] <bdmurray> in bug 326416 the Mainlogpartial.gz looks strange to me
[19:24] <bdmurray> 'DEBUG dir '/boot' needs '25165824' of '<DistUpgradeController.FreeSpace object at 0xa04812c>' (143247278080.000000)'
[19:52] <mvo> bdmurray: that line looks ok, but the term log looks a bit strange
[19:52] <mvo> bdmurray: or am I overlooking something here?
[20:47] <maxb> What's the proper thing to do when I provide the requested feedback on an "Incomplete" bug? Set it back to "New"?
[20:51] <bdmurray> maxb: no action is necessary the triager should have subscribed themselves to the bug report in which case they will see your response.
[22:29] <andol> I have a question regarding bug #256366 and its duplicate bug #253464. Would it be possible to switch which one is the "real" and which one is the duplicate? All the comments are in the duplicate, and I guess it would feel more natural to make further commens there.
[22:41] <maco> andol: just unmark the dup (set the bug # for dup to blank) and then mark the current master as dup of the one with all the info
[22:41] <BUGabundo> maco: LP could improve that!!!
[22:45] <andol> maco: Yeah, that could work :) Now I only have to figure out if that is actually the right thing to do. The dup is strictly speaking a backport request, which isn't excatly what I'm about to comment.
[22:45] <andol> maco: Never mind, I'll take a moment or two and see if I can un-confuse myself :)
[22:48] <DBO> I want to do the 5 a day
[22:48] <DBO> what must i do? =)
[22:48] <maco> DBO: install the client and get crackin'
[22:48] <DBO> client?
[22:48] <maco> DBO: https://wiki.ubuntu.com/5-A-Day
[22:48] <DBO> thank you
[22:48] <maco> there's a PPA with the 5-a-day command line client and gnome-panel applet
[22:49] <maco> tell it what bugs you triaged, and itll report them
[22:49] <maco> that webpage shows you how to get setup
[22:49] <DBO> i guess I create enough ubuntu bugs by now with Do, I might as well help =P
[22:51] <DBO> so I run this client after I triage a bug?
[22:51] <DBO> or before and it assigns them to me?
[22:52] <DBO> maco ^^
[22:58] <maco> DBO: after
[22:59] <DBO> maco, thank you =)
[22:59] <maco> you triage it, then tell 5-a-day that you did so by running "5-a-day --add 12345" or whatever bug number it is
[22:59] <maco> you can list multiple bugs at a time
[22:59] <DBO> cool
[23:00]  * DBO wonders if there are open bugs to GNOME Do
[23:00] <BUGabundo> ei maco if I had one of those for reported (new) bugs, it would be called 10 a day
[23:00] <BUGabundo> eheh
[23:00] <maco> hey!
[23:00] <maco> i do not
[23:01] <maco> maybe 10 per release cycle
[23:01] <maco> i dont reboot after a kernel update til i find out in #ubuntu+1 if it broke other people's stuff :P
[23:04] <BUGabundo> eeheheheheheh
[23:04] <BUGabundo> even non-Buntu stuff
[23:04] <BUGabundo> I was trying GO-OO on Win32 and after 15 min already had a bug filed
[23:06] <geser> maco: re bug 217270: gpg-agent can also act as a ssh-agent when started with --enable-ssh-support.
[23:07] <geser> maco: have you tried setting the different cache-ttl options in ~/.gnupg/gpg-agent.conf? perhaps even "ignore-cache-for-signing" is the right option
[23:10] <maco> geser: ah good to know. in kde both gpg-agent and ssh-agent run
[23:10] <maco> no i havent looked in that file. i just know that when i use gpg-agent intead of seahore-agent, i get a KDE password box ("pinentry" title) which lacks a remember/don't remember checkbox
[23:11] <hggdh> maco, this is indeed the case... for me to get seahorse functionality I had to rename gpg-agent
[23:12] <hggdh> which, of course, makes KDE sort of unhappy
[23:14] <geser> I would really be good if not every programm would use it's own agent
[23:15] <geser> I need gpg-agent both as gpg agent and ssh agent. Unfortunately gnome-keyring-daemon sets himself as ssh agent.
[23:16] <hggdh> weird. I have k-kr *and* ssh-agent running
[23:19] <maco> hggdh: when i use seahorse-agent in KDE it breaks evolution and kmail
[23:19] <maco> they both reject all passphrases if seahorse-agent is running in kde
[23:20] <maco> and evo jumps to somewhere between 98% and 101% of cpu for at least a minute before it brings up the passphrase dialog
[23:21] <hggdh> this is why I said that disabling gpg-agent makes KDE sort on unhappy
[23:21] <geser> does seahorse-agent set the GPG_AGENT_INFO environment variable?
[23:21] <maco> didnt know that env existed...
[23:22] <hggdh> that's a good question... time to follow the source...
[23:23] <geser> there is also SSH_AUTH_SOCK used by ssh agent(s)
[23:23] <geser> having running different agents is probably not a problem as long as the environment variables point to the one one wants to use
[23:24] <maco> two cannot run at a time
[23:24] <hggdh> which does not quite seem to be the case here
[23:24] <maco> execution will abort if there's already one running
[23:25] <geser> I didn't try it out
[23:25] <geser> but I know if I want to use gpg-agent as my ssh-agent I need to set SSH_AUTH_SOCK to the right gpg-agent socket
[23:26] <hggdh> the source does not seem to have any reference to either of the env variables
[23:27] <hggdh> looking at g-keyring now
[23:27] <hggdh> g-kr has SSH_AUTH_SOCK
[23:29] <geser> ssh-agent uses SSH_AUTH_SOCK
[23:30] <geser> gpg-agent uses GPG_AGENT_INFO and SSH_AUTH_SOCK (when --enable-ssh-support is used)
[23:34] <geser> seahorse-agent uses also GPG_AGENT_INFO
[23:35] <geser> you need to look into the source for seahorse-plugins to get the source of seahorse-agent
[23:35] <maco> i have it
[23:35] <maco> ive been talking to sadam
[23:36] <maco> i think he's going to try setting the gpg.conf to use-agent by default, and then we'll see what happens
[23:38] <hggdh> darn, I did not expect seahorse-plugins to be a different source
[23:59] <kees> bdmurray: how should I handle the "stock reply" in DebuggingSecurity (which should at least move to SecurityTeam/BugTriage) with regard to the lists in https://wiki.ubuntu.com/Bugs/Responses ?