Your message dated Sat, 21 Oct 2006 20:58:21 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixing version-tracking for already fixed bug
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: nte
Version: 1.5.32-2.1
Severity: serious

Please remove the -Werror; it's really not appropriate.  And the
-D_intel_ is fairly evil too...

| Automatic build of nte_1.5.32-2.1 on vore by sbuild/sparc 1.159
| Build started at 20010708-1219
| ******************************************************************************

[...]

| ** Using build dependencies supplied by package:
| Build-Depends: debhelper (>= 2.0.40), tcl8.0-dev, tk8.0-dev, xlib6g-dev

[...]

| gcc -Wall -Werror -I/usr/X11R6/include -I/usr/include/tk8.0/generic/ 
-DPROTOTYPES -DHAVE_UNISTD_H -DDEFINED_ERRLIST -D_intel_ -c ../src/ui_fns.c
| cc1: warnings being treated as errors
| ../src/ui_fns.c: In function `uigetustimeofday':
| ../src/ui_fns.c:1440: warning: long unsigned int format, unsigned int arg 
(arg 4)
| make[1]: *** [ui_fns.o] Error 1
| make[1]: Leaving directory `/build/buildd/nte-1.5.32/linux'
| make: *** [build-stamp] Error 2

A complete build log can be found at
http://vore.debian.org/~buildd/logs/nte_1.5.32-2.1_20010708-1219

-- 
James


--- End Message ---
--- Begin Message ---
Version: 2.3-1

This bug was marked as fixed nearly five years ago, but never
closed. I'm closing it with the correct version so that its status can
be properly version-tracked.

Although the bug report logs do not indicate which version the issue was
fixed in, 2.3-1 is the only version with a relevant changelog (new
upstream version) between the version the bug was reported in and the
date it was tagged fixed.

Regards,

Adam

--- End Message ---

Reply via email to