Your message dated Sun, 9 Apr 2017 00:57:51 +0200
with message-id <20170408225749.ga8...@ugent.be>
and subject line Re: nmu: gtk-sharp3_2.99.3-2
has caused the Debian Bug report #859896,
regarding nmu: gtk-sharp3_2.99.3-2
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 ow...@bugs.debian.org
immediately.)
--
859896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: binnmu
nmu gtk-sharp3_2.99.3-2 . ANY . unstable . -m "Rebuild against mono 4"
gtk-sharp3 was last built in 2014 against mono 3.2.8+dfsg (in jessie) ...
adequate reports
libmono-profiler-gui-thread-check: missing-symbol-version-information
/usr/lib/libmono-profiler-gui-thread-check.so.0.0.0 =>
/usr/lib/libmonoboehm-2.0.so.1
(that's the only package in sid getting this tag)
Rebuilding it against the current mono in sid/stretch (4.6.2.7+dfsg-1)
fixes this, it also switches a dependency from libmonoboehm-2.0-1 to
libmonosgen-2.0-1 (both from src:mono). It's probably better if that
happens before the release than by a security upload later on (if such
should happen). libmono-profiler-gui-thread-check is also the only
package outside src:mono still having a dependency on
libmonoboehm-2.0-1, while libmonosgen-2.0-1 has some users.
Andreas
--- End Message ---
--- Begin Message ---
Hi,
On Sun, Apr 09, 2017 at 12:41:12AM +0200, Andreas Beckmann wrote:
> nmu gtk-sharp3_2.99.3-2 . ANY . unstable . -m "Rebuild against mono 4"
Scheduled.
Cheers,
Ivo
--- End Message ---
