Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#47537 - [xalan-c] PLEASE ENTER SUMMARY

Attached to Project: Community Packages
Opened by Serge Medvedev (NeoDaVinci) - Saturday, 26 December 2015, 16:32 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 28 December 2015, 15:16 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

It seems to me that Xalan-C package contains code which does not correspond to the latest version of the library.
For example: header file XalanTransformer.hpp contains only 2 overloads of function setStylesheetParam but there must be 8.

Additional info:
* package version(s)
* config and/or log files etc.

community/xalan-c 1.11_pre1153059-3

Steps to reproduce:

Open the file /usr/include/xalanc/XalanTransformer/XalanTransformer.hpp and compare it with corresponding file from the original Xalan distribution.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 28 December 2015, 15:16 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Sunday, 27 December 2015, 04:55 GMT
Are you looking at the correct version? The packaged version is over 4 years old, but is a snapshot newer than the latest release
Comment by Serge Medvedev (NeoDaVinci) - Sunday, 27 December 2015, 10:11 GMT
I compared package content with the latest sources I've downloaded from http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c/sources .
I've noticed the difference because of absence of one of the key features of 1.11 release in package-provided headers (node sets as top-level parameters for XSLT transformation).
Comment by Doug Newgard (Scimmia) - Monday, 28 December 2015, 15:16 GMT
And as I said, that is not what's packaged. This comes down to the package being out of date, which is not a bug. The

Loading...