[Python-apps-team] Bug#753780: picard: creates excessive cachedir when started with file argument
Bob Bib
bobbib at ukr.net
Fri Jul 4 23:38:55 UTC 2014
Package: picard
Version: 1.2-2+b1
Severity: normal
Dear Maintainer,
Picard creates excessive cachedirs when started with file arguments.
a) Normal behaviour:
- picard started without arguments;
- files imported or not imported into Picard.
~/.cache
└── picard
├── data7
│ ├── 0
│ ├── 1
│ ├── 2
│ ├── 3
. . .
. . .
. . .
│ ├── d
│ ├── e
│ └── f
└── prepared
b) Wrong behaviour:
- picard started with a file argument (no matter if valid one):
$ picard /path/to/file_or_dir_name foobar111
~/.cache/file_or_dir_name
└── picard
├── data7
│ ├── 0
. . .
. . .
. . .
│ └── f
└── prepared
(Please note that fortunately no cachedir is created for 'foobar111').
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages picard depends on:
ii libc6 2.19-3
ii libchromaprint-tools 1.1-1+b1
ii libdiscid0 0.6.1-2
ii python 2.7.6-2
ii python-mutagen 1.23-1
ii python-qt4 4.11+dfsg-2
ii python2.7 2.7.7-2
pn python:any <none>
picard recommends no packages.
Versions of packages picard suggests:
ii hicolor-icon-theme 0.13-1
-- no debconf information
----
Best wishes, Bob
More information about the Python-apps-team
mailing list