git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustav Hållberg" <gustav@gmail.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [stgit] Documentation build error in proposed branch
Date: Mon, 8 Feb 2010 14:00:03 +0100	[thread overview]
Message-ID: <a1e915351002080500u74e4878fy500713ddb25aa750@mail.gmail.com> (raw)

As of recently, I cannot compile documentation in
git://repo.or.cz/stgit.git proposed:

lux:~/devel/stgit$ git ls-files -o | xargs rm
lux:~/devel/stgit$ git rev-parse HEAD
c7506039d0299c093140857b7a617ec6bcdbfc13
lux:~/devel/stgit$ make all doc
   :
cd Documentation && make all
make[1]: Entering directory `/home/gustav/devel/stgit/Documentation'
rm -f doc.dep+ doc.dep
perl ./build-docdep.perl >doc.dep+
mv doc.dep+ doc.dep
make[1]: Leaving directory `/home/gustav/devel/stgit/Documentation'
make[1]: Entering directory `/home/gustav/devel/stgit/Documentation'
../stg-build --cmd-list > command-list.txt
Traceback (most recent call last):
  File "../stg-build", line 41, in <module>
    main()
  File "../stg-build", line 31, in main
    commands.get_commands(allow_cached = False), sys.stdout)
  File "/home/gustav/devel/stgit/stgit/commands/__init__.py", line 89,
in asciidoc_command_list
    for kind, cmds in _command_list(commands):
  File "/home/gustav/devel/stgit/stgit/commands/__init__.py", line 72,
in _command_list
    yield kind, sorted(kinds[kind].iteritems())
KeyError: 'Alias commands'
make[1]: *** [command-list.txt] Error 1
make[1]: Leaving directory `/home/gustav/devel/stgit/Documentation'
make: *** [doc] Error 2

- Gustav

             reply	other threads:[~2010-02-08 13:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08 13:00 Gustav Hållberg [this message]
2010-02-09 23:07 ` [stgit] Documentation build error in proposed branch Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a1e915351002080500u74e4878fy500713ddb25aa750@mail.gmail.com \
    --to=gustav@gmail.com \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).