Hi Wolfgang, On 07/29/2011 02:20 PM, Wolfgang Schulze-Zachau wrote: > Well, I happen to disagree with your explanation. The default Alias in > javascript-common.conf points to a folder that does not contain the > necessary javascript files for mantis, and therefore these files are not > found and that IS a problem.
All of them? Which ones? Please, help us to help you... Understand this.. first at all, a lot of people use mantis, nobody have this problem, because, if this was true, a lot of mantis functions will not be accessible if javascript directory could not be loaded. If you are getting troubles with the override directive, the only explanation I could understand or I could guess, with out more information on your side, is that you are using javascript-common with javascript files that override "some" mantis files, because (may be) they have the same mantis .js names. That's the only explanation I could guess. If this was the case, It means that you have a "not default configuration", then you have to understand that the "important" severity level of a bug it means that the package "it is completely unusable to everyone"[1] [1] http://www.debian.org/Bugs/Developer#severities > Only when I add another Alias into the mantis apache.conf file to point > at mantis' javascript folder, can these be found properly. Could you take a look into your /usr/share/javascript/ to ensure if there's some javascript files which are overriding some javascript mantis files? If this is true, from which packages? Or this a "custom" system configuration? If this is a custom system configuration.. then, a good solution is create an "Alias" in your mantis apache.conf file, as a solution for your customizing system, but not for the package default. If this is a conflict with another debian package, we need to understand what exactly is the problem, which packages are envolved in this issue to proceed as is was needed. You could modify your own files under debian as you needed, that is the intention of the /etc configuration files, but the default package needs to be distributed "by default".. When there's an interesting issue which improves the package functionality, it could be considered a wish, and we can investigate the profits of introduce it or not in debian packages. Could you help us a little more to understand your problem. Thanks in advance, Best regards Sils
signature.asc
Description: OpenPGP digital signature
