From: Bastien <bzg@gnu.org>
To: Jay Kerns <gjkernsysu@gmail.com>
Cc: Marc-Oliver Ihm <marc@ihm.name>, emacs-orgmode@gnu.org
Subject: Re: Org sources and PDF files on Worg
Date: Wed, 22 May 2013 09:04:48 +0200 [thread overview]
Message-ID: <87ppwja41b.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAFiLVrapEwAhs1AxLhireiwS=h9g6Q_govmQuRAEt0aUZY+PcA@mail.gmail.com> (Jay Kerns's message of "Tue, 21 May 2013 17:37:12 -0400")
Hi Jay and Marc,
Jay Kerns <gjkernsysu@gmail.com> writes:
> I believe I can give a partial answer: it looks like Worg isn't
> publishing right now, which suggests that there was a recent commit
> which broke things.
Apparently things broke because Org in ~/git/org-mode on the server
was not compiled (and autoloads not created etc.) I compiled Org
again and republished it. It should publish correctly now.
> The search for the problem begins. Once the
> error is identified and fixed, then things should get back to normal.
Don't want to steal your work :) Just thought I would fix this
because I may be the one who broke things by forgetting to compile
at some point. I checked the scripts in ~/bin/ and they do compile
normally. Also, I removed the FORCE flag in (defun publish-worg ...)
so that publishing does not republish everything.
HTH,
--
Bastien
next prev parent reply other threads:[~2013-05-22 7:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 18:13 Org sources and PDF files on Worg Viktor Rosenfeld
2013-05-21 21:37 ` Jay Kerns
2013-05-22 7:04 ` Bastien [this message]
2013-05-22 13:03 ` Jay Kerns
2013-05-22 15:04 ` Viktor Rosenfeld
2013-05-23 7:51 ` Bastien
2013-05-23 8:02 ` Viktor Rosenfeld
2013-05-23 8:21 ` Bastien
2013-05-23 15:48 ` Suvayu Ali
2013-05-23 17:54 ` Bastien
2013-05-23 18:09 ` Suvayu Ali
2013-05-24 0:46 ` Rasmus
2013-05-24 17:31 ` Bastien
2013-05-23 17:06 ` Viktor Rosenfeld
2013-05-23 17:52 ` Bastien
2013-05-23 18:07 ` Viktor Rosenfeld
2013-05-23 7:57 ` Viktor Rosenfeld
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppwja41b.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=gjkernsysu@gmail.com \
--cc=marc@ihm.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).