SourceForge.net
2012-03-03 20:02:29 UTC
Bugs item #3198241, was opened at 2011-03-03 00:43
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3198241&group_id=10127
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Private: No
Submitted By: Olivier Salaun (cru-ct)
Initial Comment:
I'm using expat 1.95.8 on Red Hat Enterprise Linux Server release 5.6.
We are using the RPM.
While running xmlwf from a script, I noticed that checking the return code does not allow detecting errors. It seems that xmlwf always return 0 even when error occur while checking a file.
----------------------------------------------------------------------
Message:
Seems to be a duplicate of bug #2517938, which is fixed now.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3198241&group_id=10127
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3198241&group_id=10127
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Resolution: Duplicate
Priority: 5Resolution: Duplicate
Private: No
Submitted By: Olivier Salaun (cru-ct)
Assigned to: Karl Waclawek (kwaclaw)
Summary: xmlwf does not return an appropriate status code when errorsInitial Comment:
I'm using expat 1.95.8 on Red Hat Enterprise Linux Server release 5.6.
We are using the RPM.
While running xmlwf from a script, I noticed that checking the return code does not allow detecting errors. It seems that xmlwf always return 0 even when error occur while checking a file.
----------------------------------------------------------------------
Comment By: Karl Waclawek (kwaclaw)
Date: 2012-03-03 12:02Message:
Seems to be a duplicate of bug #2517938, which is fixed now.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3198241&group_id=10127