Your message dated Sat, 21 Oct 2006 20:59:48 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixing version-tracking for already fixed-in-NMU 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: verse
Version: 0.22
Priority: serious

Filing this serious because hppa plans to release with woody.  As the
Debian Architecture Bug Squash party continues this weekend, it is quite
likely that additional info and/or patches may be added to this defect.

The following build failure occured on ia64 (using gcc 2.96):
See http://people.debian.org/~willy/common_bugs.html for more background
information, and some additional information on deciphering the sometimes
cryptic buildd database entries.

If the bug is gcc 3.0 errors, then it is quite likely reproducable on
other platforms.  With gcc 3.0, of course.

If the comment is about config.{guess,sub} then they're out of date,
see the current autotools-dev package.

-- System Information
Debian Release: testing/unstable
Kernel Version: Linux ia 2.4.5rgh1 #1 Sun Jun 24 20:39:18 MDT 2001 ia64 unknown

doc/verse_0.22 by bdale-ia64 [optional:uncompiled]
  Reasons for failing:
    [Category: none]
    permission problems in build tree


--- End Message ---
--- Begin Message ---
Version: 0.22.1

This bug was fixed in an NMU five and a half years ago, but never
closed. I'm closing it with the correct version so that its status can
be properly version-tracked.

For reference:

 verse (0.22.1) frozen unstable; urgency=low
 .
   * NMU
   * Add build-depends:  Closes: #105111

Regards,

Adam

--- End Message ---

Reply via email to