From: Fabrice Niessen <fni-news-TA4HMoP+1wHrZ44/DZwexQ@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Publishing on Worg succeeds or fails? -- I can't say!
Date: Wed, 22 Apr 2015 21:46:10 +0200 [thread overview]
Message-ID: <86fv7svtdp.fsf@example.com> (raw)
In-Reply-To: 87vbgoc60b.fsf@nicolasgoaziou.fr
Hello,
Nicolas Goaziou wrote:
> Fabrice Niessen writes:
>
>> I tried to add a section on Worg (about the ReadTheOrg HTML theme).
>> The Git commit was successfull, the Git push (for which I do have
>> access on Worg) ended with an error code of 0 (hence, successfully?),
>> but it's not visible on Worg!
>
> The push succeeded, i.e., the ".org" file is probably up to date on
> the server. However the publishing process failed.
Could that be stated clearly in the output?
>> remote: Unknown cross-reference "#field-coordinates-in-formulas-transpose-table" in file "org-hacks.org"
>> remote: Unknown cross-reference "#transpose-table" in file "org-hacks.org"
>> remote: Unable to resolve link "org-capture"
>> remote: worg publish process 24723 exited at 04/22/15@11:35:28
>> To worg-NGzghNk++c5AfugRpC6u6w@public.gmane.org:worg.git
>> 4103052..2015bcd master -> master
>> $
>>
>> It seems there are warnings or errors, but the status is not clear (to
>> me).
>
> "org-hacks.org" has some invalid links, which result in an export
> error. You may want to fix them and republish (try to export locally
> first).
The thing is that I did not touch those links, as you can see in my
commit. So, somehow, Org became more strict. And the fact that that file
wasn't modified for some time means it wasn't re-exported for the same
period; hence, the problem was never found -- until someone modifies
whatever in the file...
IOW, shouldn't all files be published each time, to spot such problems
as soon as they become problems (because of syntax changes, for
example), instead of being much later, whenever the file is changed (if
it ever is)?
> I implemented a tool that may help you in the process. See
> <http://permalink.gmane.org/gmane.emacs.orgmode/97082>
OK, I'll see whether it can help.
Thanks,
Fabrice
--
Fabrice Niessen
Leuven, Belgium
http://www.pirilampo.org/
next prev parent reply other threads:[~2015-04-22 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 18:37 Publishing on Worg succeeds or fails? -- I can't say! Fabrice Niessen
2015-04-22 19:33 ` Nicolas Goaziou
2015-04-22 19:46 ` Fabrice Niessen [this message]
2015-04-22 20:00 ` Nicolas Goaziou
2015-04-22 20:11 ` Fabrice Niessen
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=86fv7svtdp.fsf@example.com \
--to=fni-news-ta4hmop+1whrz44/dzwexq@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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.
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).