Your message dated Fri, 19 Oct 2012 17:36:36 +0200
with message-id <[email protected]>
and subject line Re: Bug#690457: RM: twidge/1.0.8.1+nmu1
has caused the Debian Bug report #690457,
regarding RM: twidge/1.0.8.1+nmu1
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.)


-- 
690457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690457
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: rm

twidge needs to be migrated to a modified hoauth API but the
RC bug #665254 has had no maintainer input since it was
opened in March. (Maintainer is also upstream.)

Please remove twidge from testing.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armel
i386

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

--- End Message ---
--- Begin Message ---
On 2012-10-14 16:32, Neil Williams wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: rm
> 
> twidge needs to be migrated to a modified hoauth API but the
> RC bug #665254 has had no maintainer input since it was
> opened in March. (Maintainer is also upstream.)
> 
> Please remove twidge from testing.
> 
> [...]
> 
> 

Hi,

twidge is now listed in "will remove soon" list[1], so I will let it
stay till the end of the deadline (just in case).

I am taking the liberty of closing this bug now, so I won't forget to do
it at the end of the deadline.

~Niels

[1] <[email protected]>

--- End Message ---

Reply via email to