Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 56649 - useless xsltproc return code
useless xsltproc return code
Product: Red Hat Raw Hide
Classification: Retired
Component: libxslt (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Veillard
Depends On:
  Show dependency treegraph
Reported: 2001-11-23 06:12 EST by Tim Waugh
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-11-27 14:02:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2001-11-23 06:12:38 EST
Description of Problem:
The return code of xsltproc is often zero even when there is an error.

Version-Release number of selected component (if applicable):

How Reproducible:

For example:
1. xsltproc no-file no-file; echo $?
2. xsltproc \
http://docbook.sourceforge.net/release/xsl/current/fo/docbook.xsl \
no-file; echo $?

There are many other cases too.

This makes it hard to use xsltproc from a script.
Comment 1 Daniel Veillard 2001-11-26 15:49:12 EST
Okay I commited a fix to this. The list of xsltproc return
codes are now the following:
0: normal
1: no argument
2: too many parameters
3: unknown option
4: failed to parse the stylesheet
5: error in the stylesheet
6: error in one of the documents
7: unsuppoted xsl:output method


I will push a package with this update soon,

Comment 2 Tim Waugh 2001-11-27 13:38:42 EST
Great, work fine.  Thanks.
Comment 3 Daniel Veillard 2001-11-27 14:01:57 EST
Okay, will close when John Fleck will have updated the man page
(expected today),

Comment 4 Daniel Veillard 2001-11-29 04:10:58 EST
Okay next version will have complete fix and docs for this
The current rawhide has the fix

  thanks !


Note You need to log in before you can comment on or make changes to this bug.