Your message dated Thu, 03 Oct 2013 21:43:55 +0100
with message-id <[email protected]>
and subject line Re: Bug#723911: nmu: tangerine_0.3.4-3
has caused the Debian Bug report #723911,
regarding nmu: tangerine_0.3.4-3
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.)
--
723911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723911
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
nmu tangerine_0.3.4-3 . ALL . -m "Rebuild against taglib-sharp 2.1"
-- System Information:
Debian Release: wheezy/sid
APT prefers raring-updates
APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500,
'raring'), (400, 'raring-proposed'), (100, 'raring-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.11.0-hyper1 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Kind regards,
Loong Jin
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On Sat, 2013-09-21 at 16:06 +0800, Chow Loong Jin wrote:
> nmu tangerine_0.3.4-3 . ALL . -m "Rebuild against taglib-sharp 2.1"
That's technically a transition, fwiw, not a binNMU request.
Scheduled.
Regards,
Adam
--- End Message ---
