Dear Aaron, Thanks for bringing this to my attention.
> I just installed the suricata-update package from the Debian buster repo. > Before that, I used the github version which worked fine. I see. > > The "suricata-update" command of the Debian package tries to execute a file > /usr/local/bin/suricata-update which doesn't exist (even the folder > /usr/local/bin doesn't exist). > The right path should be /usr/bin/suricata-update (without local!). Indeed the package installs suricata-update into that directory. I just tried a clean install on buster and all I get is exactly that file [1], which executes perfectly. The package never makes any reference to /usr/local/bin. My first suspicion was that there might be a leftover script from your old GitHub install in your /usr/local/bin directory. /usr/local/bin is a typical install path for non-distribution installations, e.g. via pip/setup.py or the like, and comes before /usr/bin in the $PATH search dir. However, as you are mentioning that the directory does not even exist at all, I am a bit puzzled. Can you probably share the output of your ‘which suricata-update’ and the exact error message you get when trying to execute the command? Have you tried executing the command in a new shell or after doing a ‘hash -r’ (assuming you are using bash)? This could help find out where the problematic path comes from. Cheers Sascha [1] https://packages.debian.org/buster/amd64/suricata-update/filelist
