On Thu, 2007-01-11 at 02:07 +0100, Lele Gaifax wrote:
> > According to the man page this should work:
> >
> > [EMAIL PROTECTED]:~/monotone$ tailor --debug old/vacation.tailor
> > Traceback (most recent call last):
> > File "/usr/bin/tailor", line 35, in ?
> > main()
> > File "/var/lib/python-support/python2.4/vcpx/tailor.py", line 363, in main
> > config.set(source, 'repository', options.source_repository)
> > File "/usr/lib/python2.4/ConfigParser.py", line 639, in set
> > raise TypeError("option values must be strings")
> > TypeError: option values must be strings
> > [EMAIL PROTECTED]:~/monotone$ tailor -D old/vacation.tailor
> > Traceback (most recent call last):
> > File "/usr/bin/tailor", line 35, in ?
> > main()
> > File "/var/lib/python-support/python2.4/vcpx/tailor.py", line 363, in main
> > config.set(source, 'repository', options.source_repository)
> > File "/usr/lib/python2.4/ConfigParser.py", line 639, in set
> > raise TypeError("option values must be strings")
> > TypeError: option values must be strings
>
> Uhm, no, at least, I cannot see where the man page fails: the
> configuration file is introduced by an option (now by the -c shortcut
> too). To support shebang, tailor catch the case of only one argument,
> and assume it to be a configuration file, but that's an exception (and
> maybe undocumented).
>From the man page:
=== cut ===
DESCRIPTION
usage: tailor [options] [project ...]
OPTIONS
-D, --debug
Print each executed command. This also keeps temporary
files with the upstream logs, that are otherwise removed after use.
-v, --verbose
Be verbose, echoing the changelog of each applied
changeset to stdout.
=== cut ===
Neither of these options work. I believe --debug is the option, and
old/vacation.tailor is the project.
--
Brian May <[EMAIL PROTECTED]>
Victorian Partnership for Advanced Computing
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
