[Thijs Kinkhorst] > While I can understand that it's good if the package names are all > according to some specified scheme, I don't think that the wrong name > makes the package in such a broken state that we should prevent it > from being released.
I've renamed the package to libsvn-java for the 1.4.0 release (not released upstream yet), unless someone from the debian-java list (or elsewhere) convinces me that this violates the spirit of the Java Policy too much. It does violate the letter of the law, if you read it strictly, but the name 'libsvn-javahl-java' is ugly. I hope 1.4.0 will make it into etch, though at the moment all I can see ahead of us is the bleak prospect of getting caught in the middle of the python 2.4 transition. And that's assuming the perl FTBFS gets fixed soon.
signature.asc
Description: Digital signature
