Package: bazaar Version: 1.1.1-1 Severity: important when i attempted a commit which failed, and then attempt to commit on totally unrelated files, it silently grabbed the commit log from the old failed commit for one set of files and used it without any user intervention.
for example, if file foo does not exist and file bar does... baz commit foo (my editor is spawned and i edit the message) error finding file id (2: No such file or directory) path: foo PANIC: arch_inventory_id baz commit bar (silently grabs the unrelated commit message and finishes the commit) it would make sense to grab the old log as a template for the new one and re-spawn the editor, but to use it automatically without any user-intervention or even checking that it applies to the same files seems like very flawed behaviour to me. i understand that many baz users make use of the make-log feature, and that's largely where this bug comes from. if it could be a configuration option to enable/disable this behavior (defaulting to disabled), that would be a good thing. live well, vagrant -- System Information: Debian Release: 3.1 Architecture: i386 (i586) Kernel: Linux 2.6.8-2-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages bazaar depends on: ii diff 2.8.1-11 File comparison utilities ii gawk 1:3.1.4-2 GNU awk, a pattern scanning and pr ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libneon24 0.24.7.dfsg-2 An HTTP and WebDAV client library ii patch 2.5.9-2 Apply a diff file to an original -- no debconf information
signature.asc
Description: Digital signature
