Your message dated Thu, 18 Sep 2014 14:24:51 +0100
with message-id <[email protected]>
and subject line Re: Bug#762100: nmu: libvtk-dicom0.5_0.5.5-1
has caused the Debian Bug report #762100,
regarding nmu: libvtk-dicom0.5_0.5.5-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.)
--
762100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762100
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
I cannot reproduce the JNI issue on kfreebsd and sparc from a buildd
machine (smetana & falla). I guess the issue was fixed in the java
package.
So please schedule a binNMU:
nmu libvtk-dicom0.5_0.5.5-1 . kfreebsd-amd64 kfreebsd-i386 sparc . -m
"jni issue"
Thanks
--- End Message ---
--- Begin Message ---
On 2014-09-18 13:37, Mathieu Malaterre wrote:
I cannot reproduce the JNI issue on kfreebsd and sparc from a buildd
machine (smetana & falla). I guess the issue was fixed in the java
package.
So please schedule a binNMU:
nmu libvtk-dicom0.5_0.5.5-1 . kfreebsd-amd64 kfreebsd-i386 sparc . -m
"jni issue"
You need to specify the source package, and you want a give-back, not
an NMU. Scheduled.
(gb vtk-dicom kfreebsd-amd64 kfreebsd-i386 sparc)
--
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 ---
