On Sat, 2023-04-15 at 21:02 +0200, Omar Polo wrote: > > Yep, it comes since some dependency of nuclei is calling syscall() > directly. Don't know how to tell which it is. However, that doesn't > imply that the port is broken, it's just a hint that it *might* be > so. > I haven't tested, beside a very brief test, so can't say for sure. > If > you've tested it throughfully then it's fine. > > (this error may even go away when upstream updates their deps.) > >
Thank you. I'm test is ok. OK?
