Your message dated Mon, 13 Jun 2016 17:04:59 +0000
with message-id <[email protected]>
and subject line Bug#827166: Removed package(s) from unstable
has caused the Debian Bug report #428349,
regarding Generates deletes in Mercurial repositories instead of renames.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
428349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428349
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tailor
Version: 0.9.28-1
Severity: normal

  I'm trying to convert a darcs repository to mercurial, using tailor to
preserve history.

  After a long run, tailor produced a repository whose working directory
was identical to my starting repository.  Great!  ... or so I thought.
So, I cloned the output repository, and almost immediately banged up against
the following problem:

    When files are renamed in a darcs repository, tailor follows the
    rename *in the working copy*, but treats it as a *deletion* from
    the repository.

  Here's the simplest test case I could produce:

========== SNIP HERE ===========
cd /tmp
mkdir tailor-test
cd tailor-test
mkdir foo

cd foo
darcs init
echo "This is some data" > A
darcs add A && darcs record -a -m "Adding A"
darcs mv A B && darcs record -a -m "Renaming A"

cd ..

cat > foo.tailor << EOF
[DEFAULT]
verbose = True

[foo]
target = hg:target
start-revision = INITIAL
revision = HEAD
root-directory = /tmp/tailor-test/wd
state-file = tailor.state
source = darcs:source

[hg:target]
repository = /tmp/tailor-test/bar
subdir = hg

[darcs:source]
repository = /tmp/tailor-test/foo
subdir = darcs
EOF

tailor -c foo.tailor
hg clone wd/hg hg2
================== CUT HERE ================

  After you run these commands, /tmp/tailor-test/wd/hg will be an
apparently identical copy of /tmp/tailor-test/foo.  However, if you
cd into it and check the status of B, you'll see that it isn't actually
added to the repository:

daniel@emurlahn-sid:/tmp/tailor-test/wd/hg$ hg status B
? B

  And indeed, the final "clone" creates a clone that has A in the
history, but only records its deletion, not a rename patch.

  Daniel

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-xen-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages tailor depends on:
ii  python                        2.4.4-6    An interactive high-level object-o
ii  python-support                0.6.4      automated rebuilding support for p

Versions of packages tailor recommends:
ii  rsync                         2.6.9-3    fast remote file copy program (lik

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 0.9.35+darcs20090615-1.1+rm

Dear submitter,

as the package tailor has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/827166

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to