Publishing on Worg succeeds or fails? -- I can't say!

Publishing on Worg succeeds or fails? -- I can't say!

[Fabrice Niessen]

Hello,

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!

Any idea why?

--8<---------------cut here---------------start------------->8---
$ git push
Enter passphrase for key '/cygdrive/d/Users/fni/.ssh/id_repo.or.cz_rsa':
remote: From /home/worg/worg
remote:  * branch            master     -> FETCH_HEAD
remote: Merge made by recursive.
remote:  org-hacks.org |   21 ++++++++++++++++-----
remote:  1 files changed, 16 insertions(+), 5 deletions(-)
remote: worg publish process 24723 started at 04/22/15@11:35:23
remote: Loading 00debian-vars...
remote: Loading /etc/emacs-snapshot/site-start.d/00emacs-snapshot-common.el (source)...
remote: Loading /etc/emacs/site-start.d/50git-core.el (source)...
remote: Loading /home/emacs/.emacs.el (source)...
remote: Loading /home/emacs/.emacs-custom.el (source)...
remote: Source file `/home/emacs/git/org-mode/lisp/org.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/org-macs.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/org-compat.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ob-emacs-lisp.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ob-eval.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ob-core.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ob-comint.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ob-exp.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/org-src.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ob-keys.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ob-table.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ob-lob.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ob-ref.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ob-tangle.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/org-entities.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/org-faces.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/org-list.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/org-pcomplete.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/org-footnote.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/org-macro.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ox-org.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ox.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/org-element.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ox-ascii.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ox-publish.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ox-html.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ox-icalendar.el' newer than byte-compiled file
remote: Source file `/home/emacs/git/org-mode/lisp/ox-latex.el' newer than byte-compiled file
remote: Emacs 24.2.50.1
remote: Loading /home/emacs/.org-timestamps/worg-org-faq.cache...
remote: Source file `/home/emacs/git/org-mode/lisp/org-agenda.el' newer than byte-compiled file
remote: Skipping unmodified file /home/emacs/git/worg/org-faq.org
remote: Resetting org-publish-cache
remote: Loading /home/emacs/.org-timestamps/worg-pages.cache...
remote: Skipping unmodified file /home/emacs/git/worg/worgmap.org
[...]
remote: Skipping unmodified file /home/emacs/git/worg/org-info-js.org
remote: Publishing file /home/emacs/git/worg/org-hacks.org using `org-html-publish-to-html'
remote: Source file `/home/emacs/git/org-mode/lisp/org-table.el' newer than byte-compiled file
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
$                           
--8<---------------cut here---------------end--------------->8---

It seems there are warnings or errors, but the status is not clear (to
me).

Note that all the above messages are outputted on stderr, which does not
feel right, but that's how Emacs outputs messages in batch mode.

Best regards,
Fabrice

-- 
Fabrice Niessen
Leuven, Belgium
http://www.pirilampo.org/

Re: Publishing on Worg succeeds or fails? -- I can't say!

[Nicolas Goaziou]

Hello,

Fabrice Niessen <fni-news-TA4HMoP+1wHrZ44/DZwexQ@public.gmane.org>
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.

> 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).

I implemented a tool that may help you in the process. See
<http://permalink.gmane.org/gmane.emacs.orgmode/97082>


Regards,

-- 
Nicolas Goaziou

Re: Publishing on Worg succeeds or fails? -- I can't say!

[Fabrice Niessen]

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/

Re: Publishing on Worg succeeds or fails? -- I can't say!

[Nicolas Goaziou]

Fabrice Niessen <fni-news-TA4HMoP+1wHrZ44/DZwexQ@public.gmane.org>
writes:

> Could that be stated clearly in the output?

You should ask to whom implemented Worg.

> 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...

Correct.

> 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)?

So you get 50-100 files to fix instead of the one you modified?

IMO, it would be a waste to re-publish unmodified files. You only have
to consider syntax changes when updating a file.

> OK, I'll see whether it can help.

Note that you need to have a very recent Org (less than 7 hours) to use
it.


Regards,

Re: Publishing on Worg succeeds or fails? -- I can't say!

[Fabrice Niessen]

Nicolas Goaziou wrote:
> Fabrice Niessen writes:
>
>> Could that be stated clearly in the output?
>
> You should ask to whom implemented Worg.

And that is?  Bastien?

>> 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...
>
> Correct.
>
>> 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)?
>
> So you get 50-100 files to fix instead of the one you modified?

No much fun, that's right.

> IMO, it would be a waste to re-publish unmodified files. You only have
> to consider syntax changes when updating a file.

OTOH, I find it uncomfortable to have a "project" (in the publishing
sense) which is, in fact, not publishable anymore, because many files
won't export anymore -- some could even still rely on Org 7...

But I understand your point. The question comes down to what we want:
a uniform, coherent set of Org files (all up-to-date, and exportable) or
a set of HTML pages which we don't touch anymore if their Org
counterpart is not touched either.

> Note that you need to have a very recent Org (less than 7 hours) to use
> it.

Fixed the problems. Now that page is up-to-date on Worg again. Thanks.

Best regards,
Fabrice

-- 
Fabrice Niessen
Leuven, Belgium
http://www.pirilampo.org/