Your message dated Mon, 18 Jan 2016 18:14:11 +0000
with message-id <[email protected]>
and subject line Re: Bug#811413: nmu: gobby_0.5.0-7 for mips64el
has caused the Debian Bug report #811413,
regarding nmu: gobby_0.5.0-7 for mips64el
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.)
--
811413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811413
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
User: [email protected]
Usertags: binnmu
Severity: normal
Please rebuild gobby for mips64el, as it failed to build due to
libgtkmm of stdc++11 problem.
Now the problem has been resolved.
nmu gobby_0.5.0-7 . mips64el . -m 'Rebuild with libcairomm-1.0-1v5'
--
YunQiang Su
--- End Message ---
--- Begin Message ---
On 2016-01-18 17:53, YunQiang Su wrote:
Package: release.debian.org
User: [email protected]
Usertags: binnmu
Severity: normal
Please rebuild gobby for mips64el, as it failed to build due to
libgtkmm of stdc++11 problem.
Now the problem has been resolved.
nmu gobby_0.5.0-7 . mips64el . -m 'Rebuild with libcairomm-1.0-1v5'
A package can't get a binNMU until it has built; you need it to be
"given back" to be retried. Normally you'd ask on
[email protected] but I've done it this time.
--
Jonathan Wiltshire [email protected]
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
<directhex> i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits
--- End Message ---
