Can you investigate why the checksum changed? We might also want to add a list_url so that url can point to the latest release (4.91) and list_url can point to older releases. This is how we handle CRAN packages.

Md5 checksum of lsof tarball obtained from “https://www.mirrorservice.org/sites/lsof.itap.purdue.edu/pub/tools/unix/lsof/OLD/lsof_4.89.tar.gz” matches the md5 checksum before being fixed in October, so I think that the tarball wasn't changed.
17ace14

If the above assumption is correct, I think the current sha256 checksum is correct. : 5d08da7ebe049c9d9a6472d6afb81aa5af54c4733a3f8822cbc22b57867633c9
What do you think about this?

We might also want to add a list_url so that url can point to the latest release (4.91) and list_url can point to older releases. This is how we handle CRAN packages.

I will fix about it .