Your message dated Mon, 06 Jan 2014 07:50:31 +0100
with message-id <[email protected]>
and subject line Re: Bug#734321: nmu: 
qtbase-opensource-src_5.2.0+dfsg-5/experimental
has caused the Debian Bug report #734321,
regarding nmu: qtbase-opensource-src_5.2.0+dfsg-5/experimental
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.)


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

Please take note this if for experimental.

nmu qtbase-opensource-src_5.2.0+dfsg-5 . ALL . -m "Rebuild against newer 
libxcb-sync."

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12.6+edid (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message ---
On 2014-01-05 23:10, Lisandro Damián Nicanor Pérez Meyer wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: binnmu
> 
> Please take note this if for experimental.
> 
> nmu qtbase-opensource-src_5.2.0+dfsg-5 . ALL . -m "Rebuild against newer 
> libxcb-sync."
> 
> [...]

Scheduled, thanks.


Re: my remark on IRC: The extra "experimental" goes after the
architectures - so for future reference:

  nmu qtbase-opensource-src_5.2.0+dfsg-5 . ALL . experimental . \
     -m "Rebuild against newer libxcb-sync."

~Niels

--- End Message ---

Reply via email to