After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 710636 - xmllint doesn't always terminate with a non-zero exit status in case of bad usage
xmllint doesn't always terminate with a non-zero exit status in case of bad u...
Status: RESOLVED OBSOLETE
Product: libxml2
Classification: Platform
Component: xmllint
git master
Other Linux
: Normal normal
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2013-10-22 11:49 UTC by Vincent Lefevre
Modified: 2021-07-05 13:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vincent Lefevre 2013-10-22 11:49:19 UTC 
In case of bad usage, xmllint should terminate with a non-zero exit status (more precisely, 1), but this is not always the case. For instance, while "xmllint" fails, "xmllint --nonet" doesn't, though the error by the user is very similar.

My Debian bug report:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727075

with libxml2-utils 2.9.1+dfsg1-3
Comment 1 GNOME Infrastructure Team 2021-07-05 13:20:48 UTC 
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/libxml2/-/issues/

Thank you for your understanding and your help.