Control: owner -1 !
Control: tags -1 moreinfo
Hi Wesley,
Thanks for the report.
What's weird is that I have exactly the same version as you do but
don't have the same things:
> The following error messages appear, which points to the problem:
> asciidoc: WARNING: xxx.txt: line 53: {sys:"/usr/bin/python" -u -c "import
> base64,sys; base64.encode(sys.stdin,sys.stdout)" <
> "/etc/asciidoc/images/icons/important.png"}: non-zero exit status
I have:
$ asciidoc -a data-uri -a icons /tmp/test.adoc
$ asciidoc -a data-uri -a icons -v /tmp/test.adoc
asciidoc: reading: /etc/asciidoc/asciidoc.conf
asciidoc: reading: /tmp/test.adoc
asciidoc: reading: /etc/asciidoc/xhtml11.conf
asciidoc: include1: /etc/asciidoc/stylesheets/asciidoc.css
asciidoc: test.adoc: line 9: ifeval: "source-highlight"=="pygments": False
asciidoc: include1: /etc/asciidoc/javascripts/asciidoc.js
asciidoc: reading: /etc/asciidoc/filters/graphviz/graphviz-filter.conf
asciidoc: reading: /etc/asciidoc/filters/source/source-highlight-filter.conf
asciidoc: test.adoc: line 9: ifeval:
"source-highlight"=="source-highlight": True
asciidoc: test.adoc: line 9: ifeval: "source-highlight"=="highlight": False
asciidoc: test.adoc: line 9: ifeval: "source-highlight"=="pygments": False
asciidoc: reading: /etc/asciidoc/filters/music/music-filter.conf
asciidoc: reading: /etc/asciidoc/filters/code/code-filter.conf
asciidoc: reading: /etc/asciidoc/filters/latex/latex-filter.conf
asciidoc: reading: /etc/asciidoc/lang-en.conf
asciidoc: writing: /tmp/test.html
asciidoc: test.adoc: line 21: evaluating:
{eval:os.path.join(r"/tmp",r"/etc/asciidoc/images/icons/warning.png")}
asciidoc: test.adoc: line 21: evaluating: {sys:"/usr/bin/python" -u -c
"import base64,sys; base64.encode(sys.stdin,sys.stdout)" <
"/etc/asciidoc/images/icons/warning.png"}
asciidoc: test.adoc: line 21: shelling: "/usr/bin/python" -u -c
"import base64,sys; base64.encode(sys.stdin,sys.stdout)" <
"/etc/asciidoc/images/icons/warning.png" > "/tmp/tmpsCVwMV"
asciidoc: test.adoc: line 58: evaluating: {counter:table-number}
And the icons are showing correctly.
Could you send me the same command result using "-v" option please?
Could you attach the xxx.txt file you used and the backend
configuration file too please?
> /etc/asciidoc/images is a symlink to /usr/share/asciidoc/images, which
> sounds correct. However, /usr/share/asciidoc/images/icons is completely
> empty.
I have:
$ ll /usr/share/asciidoc/images/icons
lrwxrwxrwx 1 root root 8 Mar 11 22:46 /usr/share/asciidoc/images/icons
-> ../icons
$ ll /usr/share/asciidoc/images/icons/
total 48K
drwxr-xr-x 2 root root 4.0K Mar 30 19:14 callouts
-rw-r--r-- 1 root root 2.7K Mar 7 2009 caution.png
-rw-r--r-- 1 root root 2.6K Mar 7 2009 example.png
-rw-r--r-- 1 root root 1.4K Oct 29 2007 home.png
-rw-r--r-- 1 root root 3.0K Mar 7 2009 important.png
-rw-r--r-- 1 root root 1.3K Oct 29 2007 next.png
-rw-r--r-- 1 root root 2.5K Mar 7 2009 note.png
-rw-r--r-- 1 root root 1.4K Oct 29 2007 prev.png
-rw-r--r-- 1 root root 226 Oct 29 2007 README
-rw-r--r-- 1 root root 2.7K Mar 7 2009 tip.png
-rw-r--r-- 1 root root 1.3K Oct 29 2007 up.png
-rw-r--r-- 1 root root 3.2K Mar 7 2009 warning.png
> The icons are actually found in /usr/share/doc/images/icons, which
> doesn't seem to be the correct location for them, since although they
> are referenced by the asciidoc documentation, they also need to be
> available in order to use "-a data-uri -a icons"
I have:
$ ll /usr/share/doc/images/icons
ls: cannot access /usr/share/doc/images/icons: No such file or directory
But I think you mean:
$ ll /usr/share/doc/asciidoc/images/icons
lrwxrwxrwx 1 root root 23 Mar 11 22:46
/usr/share/doc/asciidoc/images/icons -> ../../../asciidoc/icons
So it's /usr/share/doc/asciidoc/images/icons that points to
/usr/share/asciidoc/icons
There has been a lot of modification of symlinks in the last packages
steps. Could you try and reinstall asciidoc (using purge):
sudo apt-get purge asciidoc
sudo apt-get install asciidoc
and tell me if the issue is still there please?
Thanks in advance,
Joseph
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
