darcs

Issue 567 Bug#454193: Special case error for darcs mv x/y x/

Title Bug#454193: Special case error for darcs mv x/y x/
Priority bug Status resolved
Milestone Resolved in
Superseder Nosy List darcs-devel, dmitry.kurochkin, kowey, markstos, submit, thorkilnaur, tommy
Assigned To
Topics

Created on 2007-12-04.14:51:49 by droundy, last changed 2009-08-27.14:07:46 by admin.

Messages
msg2279 (view) Author: droundy Date: 2007-12-04.14:51:48
Package: darcs
Version: 1.0.9~rc1-0.1+b3
Severity: wishlist

I happened to type

    darcs mv etch/preseed.cfg etch/

When I meant to type

    darcs mv etch/preseed.cfg d-i/etch/

and got a confusing error message

    darcs: bug in darcs!
    There was an attempt to write an invalid pending!
    If possible, please send the contents of _darcs/patches/pending_buggy
    along with a bug report.
    Please report this to bugs@darcs.net
    If possible include the output of 'darcs --exact-version'.

This special case could be given a clearer error message along the
lines of GNU coreutils' mv:

    mv: `etch/preseed.cfg' and `etch/preseed.cfg' are the same file

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages darcs depends on:
ii  libc6                 2.6.1-1            GNU C Library: Shared libraries
ii  libcurl3              7.17.1-1           Multi-protocol file transfer libra
ii  libgmp3c2             2:4.2.2+dfsg-1     Multiprecision arithmetic library
ii  libkrb53              1.6.dfsg.3~beta1-2 MIT Kerberos runtime libraries
ii  libncurses5           5.6+20071013-1     Shared libraries for terminal hand
ii  zlib1g                1:1.2.3.3.dfsg-6   compression library - runtime

Versions of packages darcs recommends:
ii  nullmailer [mail-transport-ag 1:1.03-5   simple relay-only mail transport a

-- no debconf information
msg2377 (view) Author: markstos Date: 2008-01-09.03:28:49
I just 'sent' a test which confirms that this is "resolved in unstable", so I'm
marking it as such. 

The test name is: invalid_pending_after_mv_to_self.sh
History
Date User Action Args
2007-12-04 14:51:50droundycreate
2008-01-09 03:28:54markstossetstatus: unread -> resolved-in-unstable
nosy: + markstos
messages: + msg2377
2008-09-04 21:31:41adminsetstatus: resolved-in-unstable -> resolved
nosy: + dagit
2009-08-06 17:48:12adminsetnosy: + jast, Serware, dmitry.kurochkin, darcs-devel, zooko, mornfall, simon, thorkilnaur, - droundy, submit
2009-08-06 20:43:59adminsetnosy: - beschmi
2009-08-10 22:09:52adminsetnosy: + submit, - darcs-devel, zooko, jast, Serware, mornfall
2009-08-11 00:03:58adminsetnosy: - dagit
2009-08-25 17:59:55adminsetnosy: + darcs-devel, - simon
2009-08-27 14:07:46adminsetnosy: tommy, kowey, markstos, darcs-devel, thorkilnaur, submit, dmitry.kurochkin