Package: smbclient Version: 2:4.9.5+dfsg-5+deb10u1 Severity: normal Dear Maintainer,
I copied a script containing the recurse ON command. Instead of removing it I changed it to recurse OFF. To my surprise this didn't switch off the recursion. Only after removing the recurse OFF command did the recursion on the dir command stop. An explicit recurse ON;recurse OFF also worked. This behavior is unexpected and may confuse an unaware user who copies a script and modifies it. I tested it on another system with smbclient version 4.11.6-Ubuntu and this bug is still there. -- System Information: Debian Release: 10.8 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-14-amd64 (SMP w/48 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages smbclient depends on: ii dpkg 1.19.7 ii libarchive13 3.3.3-4+deb10u1 ii libbsd0 0.9.1-2 ii libc6 2.28-10 ii libpopt0 1.16-12 ii libreadline7 7.0-5 ii libsmbclient 2:4.9.5+dfsg-5+deb10u1 ii libtalloc2 2.1.14-2 ii libtevent0 0.9.37-1 ii samba-common 2:4.9.5+dfsg-5+deb10u1 ii samba-libs 2:4.9.5+dfsg-5+deb10u1 smbclient recommends no packages. Versions of packages smbclient suggests: ii cifs-utils 2:6.8-2 pn heimdal-clients <none> -- no debconf information
