Your message dated Fri, 19 Oct 2012 08:41:23 -0500
with message-id <50815883.50...@complete.org>
and subject line Closing
has caused the Debian Bug report #690486,
regarding twidge: gives a user error (Bad response: 404)
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 ow...@bugs.debian.org
immediately.)
--
690486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: twidge
Version: 1.0.8.1+nmu1
Severity: grave
Since 13th October 2012, the twidge client gives a user error
(Bad response: 404) and is unable to tweet via the update command.
-- System Information:
Debian Release: wheezy/sid
APT prefers stable
APT policy: (990, 'stable'), (50, 'unstable'), (1, 'experimental')
Architecture: i386 (i486)
Kernel: Linux 3.2.0-1-486
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages twidge depends on:
ii curl 7.21.0-1 Get a file from an HTTP, HTTPS or
ii libc6 2.13-24 Embedded GNU C Library: Shared lib
ii libcurl3-gnutls 7.21.0-1 Multi-protocol file transfer libra
ii libffi5 3.0.9-3 Foreign Function Interface library
ii libgmp10 2:5.0.1+dfsg-7 Multiprecision arithmetic library
twidge recommends no packages.
twidge suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Mark,
Thank you for the update. I have received one other report from a user
with this issue as well, and for that person removing ~/.twidgerc fixed
it. It seems like this issue is on the Twitter end. I have not been
able to reproduce it.
-- John
--- End Message ---
