Re: toolchain/57075 (nbctfmerge looped)

[Andreas Gustafsson <gson%gson.org@localhost>]

The following reply was made to PR toolchain/57075; it has been noted by GNATS.

From: Andreas Gustafsson <gson%gson.org@localhost>
To: Luke Mewburn <luke%mewburn.net@localhost>
Cc: gnats-bugs%netbsd.org@localhost
Subject: Re: toolchain/57075 (nbctfmerge looped)
Date: Thu, 25 May 2023 19:46:55 +0300

 Luke Mewburn wrote:
 >   |  > Have you seen this recently?
 >   |  
 >   |  I don't recall seeing it happen again.  But even if the bug was fixed
 >   |  by the referenced commit, it could still happen on the TNF testbeds
 >   |  since it affects the nbctfmerge tool, which is linked with the host
 >   |  libpthread and therefore may still have the bug even if the system
 >   |  being built doesn't.
 > 
 > Whether or not this specific bug is fixed, as a matter of GNATS
 > convention, do we hold up closing a bug after a fix because there might
 > be a system with the old code still deployed?  This is a bit rhetorical,
 > because we can't use that as our convention because we'd never close
 > bugs!
 
 My intended meaning was not "the bug cannot be closed because the
 testbeds are still affected", but rather "since my experience is with
 testbeds that are not running -current, I'm afraid the question of
 whether or not I have seen the problem recently is not actually
 relevant to determining whether or not the bug has been fixed".
 -- 
 Andreas Gustafsson, gson%gson.org@localhost