Your message dated Thu, 29 Aug 2019 00:59:30 +0200
with message-id <654d5b29-0684-4ef5-9567-24de561aa...@debian.org>
and subject line Re: Bug#935917: suricata-update: cannot use suricata-update
command
has caused the Debian Bug report #935917,
regarding suricata-update: cannot use suricata-update command
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
935917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: suricata-update
Version: 1.0.3-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I just installed the suricata-update package from the Debian buster repo.
Before that, I used the github version which worked fine.
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!).
best regards
Aaron
-- System Information:
Debian Release: 10.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages suricata-update depends on:
ii ca-certificates 20190110
ii python3 3.7.3-1
ii python3-yaml 3.13-2
suricata-update recommends no packages.
suricata-update suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Aaron,
[…]
>>> 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.
>
> You are right!!! After restarting my shell/ssh connection,
> suricata-update works as expected! ;)
Excellent, nice to hear that! :)
> I apologise for the bug report and thank you for your help!
No need to apologise, happy to help!
Cheers
Sascha
> Am 28.08.2019 um 00:05 schrieb Sascha Steinbiss:
>> 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
>>
--- End Message ---
