Your message dated Tue, 14 Feb 2012 22:53:40 +0000
with message-id <[email protected]>
and subject line Re: Bug#659919: nmu: alsa-plugins_1.0.25-1
has caused the Debian Bug report #659919,
regarding nmu: alsa-plugins_1.0.25-1
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.)
--
659919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659919
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
Please schedule the following, to fix a bogus dependency on libavutil for
libasound2-plugins/amd64. I still have no idea of how that dep ended up
like that in my environment.
nmu alsa-plugins_1.0.25-1 . amd64 . -m "rebuild on amd64 to fix broken
libavutil dependency (see #659665)"
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ca_ES.UTF-8@valencia, LC_CTYPE=ca_ES.UTF-8@valencia (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Tue, 2012-02-14 at 23:29 +0100, Jordi Mallach wrote:
> Please schedule the following, to fix a bogus dependency on libavutil for
> libasound2-plugins/amd64. I still have no idea of how that dep ended up
> like that in my environment.
>
> nmu alsa-plugins_1.0.25-1 . amd64 . -m "rebuild on amd64 to fix broken
> libavutil dependency (see #659665)"
Scheduled (with s/on amd64//, as I mentioned on IRC).
Regards,
Adam
--- End Message ---
