Your message dated Fri, 24 May 2013 18:12:36 +1000
with message-id <[email protected]>
and subject line Re: Bug#709546: bitlbee: Please merge fix to bug #1064 
(twitter login error 403 forbidden) from upstream.
has caused the Debian Bug report #709546,
regarding bitlbee: Please merge fix to bug #1064 (twitter login error 403 
forbidden) from upstream.
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.)


-- 
709546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709546
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bitlbee
Version: 3.2-1.1
Severity: normal

Dear Maintainer,

When trying to log onto Twitter, Bitlbee receives an error "Logging in:
Error: Could not retrieve /1.1/users/lookup.json: 403 Forbidden." This
issue has been fixed upstream: see ticket #1064.
http://bugs.bitlbee.org/bitlbee/ticket/1064

Would you consider to include this tiny fix in?
Thanks for your work!

-- System Information:
Debian Release: 7.0
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bitlbee depends on:
ii  bitlbee-common  3.2-1.1
ii  debianutils     4.3.2
ii  libc6           2.13-38
ii  libevent-2.0-5  2.0.19-stable-3
ii  libgcrypt11     1.5.0-5
ii  libglib2.0-0    2.33.12+really2.32.4-5
ii  libgnutls26     2.12.20-6

bitlbee recommends no packages.

bitlbee suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Close bug. The login problem seemed to be at Twitter's end and the issue is
fixed (see http://bugs.bitlbee.org/bitlbee/ticket/1064).

--- End Message ---

Reply via email to