Package: tailor
Version: 0.9.28-1
Severity: normal

  Say I have a darcs repository called "head" and I use the following
configuration, which is approximately what the tailor README suggests:

=============== CUT HERE ================
[DEFAULT]
verbose = True

[project]
target = darcs:target
start-revision = INITIAL
root-directory = /tmp/tailor
state-file = tailor.state
source = darcs:source
subdir = tailortmp

[darcs:target]
repository = /tmp/tailor/foo

[darcs:source]
repository = /tmp/tailor/head
============================================

  Running this through tailor produces the following output:

11:57:42 [I] Bootstrapping "project" in "/tmp/tailor"
11:57:42 [I] /tmp/tailor/tailortmp $ darcs initialize
11:57:42 [I] [Ok]
11:57:42 [I] $ darcs changes --xml-output --repo /tmp/tailor/head --reverse
11:57:42 [I] [Ok]
11:57:42 [I] /tmp/tailor/tailortmp $ darcs changes --last 1 --xml-output
11:57:42 [I] [Ok]
11:57:42 [C] Checkout of project failed!
Traceback (most recent call last):
  File "/usr/bin/tailor", line 35, in ?
    main()
  File "/var/lib/python-support/python2.4/vcpx/tailor.py", line 339, in main
    tailorizer()
  File "/var/lib/python-support/python2.4/vcpx/tailor.py", line 144, in 
__call__    self.bootstrap()
  File "/var/lib/python-support/python2.4/vcpx/tailor.py", line 74, in 
bootstrap    actual = dwd.checkoutUpstreamRevision(revision)
  File "/var/lib/python-support/python2.4/vcpx/source.py", line 253, in 
checkoutUpstreamRevision
    last = self._checkoutUpstreamRevision(revision)
  File "/var/lib/python-support/python2.4/vcpx/repository/darcs/source.py", 
line 536, in _checkoutUpstreamRevision
    return last.next()
StopIteration

  The problem seems to be that tailor is doing the following:

    (1) Create a new, empty darcs repository (presumably to store the
        pristine upstream tree).
    (2) Read the information of the first change in that repository,
        which doesn't exist since it's empty.
    (3) Explode.  BOOM!

  It appears that manually doing a "darcs get" to create the pristine copy
works around the bug, but I don't think this should be necessary?

  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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to