Package: bash Version: 4.2+dfsg-0.1 Severity: grave Justification: causes non-serious data loss
Dear Maintainer, I ran out of disk space last night. Today I'm greeted with an (almost) empty bash history. The only commands left in ~/.bash_history start with the command that caused the full-disk situation. The only explanation I can think of as being the cause of this behaviour is that bash is trying to overwrite ~/.bash_history rather than writing to a temporary file and renaming it appropriately (as would have been good practice I believe). Naively trying to overwrite will lose data in a wide variety of situations including but not limited to loss of power, over-quota and full-disk situations. Severity set to grave as this causes data loss and, in my case, losing a year of history is clearly not fun (TM). Cheers, Rene -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bash depends on: ii base-files 7.1 ii dash 0.5.7-3 ii debianutils 4.3.2 ii libc6 2.13-38 ii libtinfo5 5.9-10 Versions of packages bash recommends: ii bash-completion 1:2.0-1 Versions of packages bash suggests: pn bash-doc <none> -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
