[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: toolchain/57075 (nbctfmerge looped)
The following reply was made to PR toolchain/57075; it has been noted by GNATS.
From: Luke Mewburn <luke%mewburn.net@localhost>
To: Andreas Gustafsson <gson%gson.org@localhost>
Cc: Luke Mewburn <luke%mewburn.net@localhost>, gnats-bugs%netbsd.org@localhost
Subject: Re: toolchain/57075 (nbctfmerge looped)
Date: Fri, 26 May 2023 02:53:18 +1000
On 23-05-25 19:46, Andreas Gustafsson wrote:
| 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".
And I didn't intend to minimise the issue by any means.
Main Index |
Thread Index |