Action against software patentsGnome2 LogoW3C LogoRed Hat Logo
Made with Libxml2 Logo

The XML C parser and toolkit of Gnome

Reporting bugs and getting help

Main Menu
Related links

Well, bugs or missing features are always possible, and I will make apoint of fixing them in a timely fashion. The best way to report a bug is touse the Gnomebug tracking database(make sure to use the "libxml2" module name). Ilook at reports there regularly and it's good to have a reminder when a bugis still open. Be sure to specify that the bug is for the package libxml2.

For small problems you can try to get help on IRC, the #xml channel onirc.gnome.org (port 6667) usually have a few person subscribed which may help(but there is no garantee and if a real issue is raised it should go on themailing-list for archival).

There is also a mailing-list xml@gnome.orgfor libxml, with an on-line archive(old). To subscribe to this list,please visit the associated Webpage andfollow the instructions. Do not send code, I won't debug it(but patches are really appreciated!).

Please note that with the current amount of virus and SPAM, sending mailto the list without being subscribed won't work. There is *far too manybounces* (in the order of a thousand a day !) I cannot approve them manuallyanymore. If your mail to the list bounced waiting for administrator approval,it is LOST ! Repost it and fix the problem triggering the error. Also pleasenote that emails witha legal warning asking to not copy or redistribute freely the informationsthey containare NOTacceptable for the mailing-list,such mail will as much as possible be discarded automatically, and are lesslikely to be answered if they made it to the list, DO NOTpost to the list from an email address where such legal requirements areautomatically added, get private paying support if you can't shareinformations.

Check the following beforeposting:

  • Read the FAQand use thesearch engineto get information related to your problem.
  • Make sure you are using a recentversion, and that the problem still shows up in a recent version.
  • Check the listarchivesto see if the problem was reported already. In this casethere is probably a fix available, similarly check the registeredopen bugs.
  • Make sure you can reproduce the bug with xmllint or one of the testprograms found in source in the distribution.
  • Please send the command showing the error as well as the input (as anattachment)

Then send the bug with associated information to reproduce it to the xml@gnome.orglist; if it's really libxmlrelated I will approve it. Please do not send mail to me directly, it makesthings really hard to track and in some cases I am not the best person toanswer a given question, ask on the list.

To be really clear about support:

  • Support or help requests MUST be sent tothe list or on bugzillain case of problems, so that the Questionand Answers can be shared publicly. Failing to do so carries the implicitmessage "I want free support but I don't want to share the benefits withothers" and is not welcome. I will automatically Carbon-Copy thexml@gnome.org mailing list for any technical reply made about libxml2 orlibxslt.
  • There is no garantee of support, ifyour question remains unanswered after a week, repost it, making sure yougave all the detail needed and the information requested.
  • Failing to provide information as requested or double checking firstfor prior feedback also carries the implicit message "the time of thelibrary maintainers is less valuable than my time" and might not bewelcome.

Of course, bugs reported with a suggested patch for fixing them willprobably be processed faster than those without.

If you're looking for help, a quick look at the list archivemay actuallyprovide the answer. I usually send source samples when answering libxml2usage questions. The auto-generated documentationisnot as polished as I would like (i need to learn more about DocBook), butit's a good starting point.

Daniel Veillard