ought i upload a -4 with a changelog entry marking the bug closed? i didn't mark it closed in the changelog because i explicitly wanted the bug left open.
sorry for any confusion -- i'm certainly not trying to work around this issue in the long term by reducing testing =]. i just know that it's not going to be fixed until growlight 1.2.38 moves to unstable from experimental, which requires notcurses3, which is in the NEW queue awaiting FTPteam approval. at that point, i'll be reenabling the test. so i don't consider 1.2.37-3 as having "closed" the bug whatsoever. but it ought be closed shortly after notcurses3 hits unstable =].
