Package: targetcli-fb
Version: 1:2.1.53-1.2
Severity: normal
Dear Maintainer,
* What led up to the situation?
I saw something had created a literal /~ directory in the root and
investigated it. When I
investgated, there was a directory .targetcli inside it containing log.txt
and prefs.bin
* What exactly did you do (or not do) that was effective (or
ineffective)?
Used targetcli command line to save the config using the saveconfig command
* What was the outcome of this action?
Config files were written to /\~/.targetcli (literal directory ~)
* What outcome did you expect instead?
Config files should be written to .targetcli directory in the home
directory, and ~ should be expanded properly.
-- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.22-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages targetcli-fb depends on:
ii python3 3.13.2-2
ii python3-configshell-fb 1:2.0.0-1
ii python3-gi 3.50.0-4+b1
ii python3-rtslib-fb 2.1.76-3
ii python3-six 1.17.0-1
targetcli-fb recommends no packages.
targetcli-fb suggests no packages.
-- no debconf information
