Your message dated Mon, 03 Nov 2008 17:38:28 +0100
with message-id <[EMAIL PROTECTED]>
and subject line pidgin-facebookchat
has caused the Debian Bug report #504156,
regarding RFP: pidgin-facebookchat -- Facebook Chat plugin for Pidgin
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
504156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504156
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist

* Package name    : pidgin-facebookchat
  Version         : 1.38
  Upstream Author : Eion Robb <[EMAIL PROTECTED]>
* URL             : http://code.google.com/p/pidgin-facebookchat/
* License         : GPLv3
  Programming Lang: ?
  Description     : Facebook Chat plugin for Pidgin
This is a Facebook chat plugin for Pidgin and libpurple messengers. It connects 
to the new Facebook Chat IM service without the need for an API key.

Currently the plugin can log into the Facebook servers, grab the buddy list, 
send/receive messages, add/remove friends, receive notifications, search 
for Facebook friends and set your Facebook status.



--- End Message ---
--- Begin Message ---
Hi,
There already is a pidgin-facebookchat in Debian unstable.
Version 1.35 only so far though, which has some annoying bugs (sending
messages 3 times etc.). Anyway, this WNPP bug is outdated.

best regards,
Erich Schubert
-- 
   erich@(vitavonni.de|debian.org)    --    GPG Key ID: 4B3A135C    (o_
     Which is worse: ignorance or apathy? Who knows? Who cares?     //\
               Für jedes Problem gibt es eine Lösung,               V_/_
                 die einfach, klar und falsch ist.



--- End Message ---

Reply via email to