[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#584606: marked as done (nmu: insighttoolkit_3.18.0-2)



Your message dated Sat, 12 Jun 2010 15:27:03 +0200
with message-id <20100612132703.GP2030@patate.is-a-geek.org>
and subject line Re: Bug#584606: nmu: insighttoolkit_3.18.0-2
has caused the Debian Bug report #584606,
regarding nmu: insighttoolkit_3.18.0-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 owner@bugs.debian.org
immediately.)


-- 
584606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584606
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

nmu insighttoolkit_3.18.0-2 . ALL . -m "Rebuild with gccxml 0.9.0+cvs20100501-2"

Thanks,
-Steve

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
On Fri, Jun  4, 2010 at 19:49:08 -0500, Steve M. Robbins wrote:

> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> 
> nmu insighttoolkit_3.18.0-2 . ALL . -m "Rebuild with gccxml 0.9.0+cvs20100501-2"
> 
Looks like there was a new sourceful upload, so closing this bug.

Note that the new version ftbfs with a gcc ICE on ia64, and a gcj bus
error on fasch (kfreebsd-amd64).

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply to: