The strange thing is that you get this error running it with sudo. I can
reproduce the same error now running it without sudo, with and without
--no-cache-dir. In both cases it works fine with sudo.
Maybe you have some strange permissions on /tmp ?
Debian Buster with KDE was installed just a few days ago, and certainly I did not play with the permissions of /tmp.
And the error message seems to indicate not an access problem, but simply a file not found error...
Tried with and without sudo, but same behavior....
I bet the problem is in some changes of directories structure between different releases of the distribution, a frequent error that plagues Linux ...
Alberto
Alberto I2PHD