Hi Ivo, I admit I'm not very happy with the way we are cooperating on libsbml maintenance. When trying to squash bugs in our advent bug squashing effort I intended to check the bugs of libsbml (1 RC tagged patch, 1 important tagged patch and 1 important where bug submitter requested confirmation). So in principle all these bugs are quite simple - but no reply has hit the BTS. While I assume that you are subscribed to the maintainer list or at least to the package in the Package Tracking System (which was now moved to tracker). Please confirm that you are at least aware of the three open bugs.
The next thing I'm not happy about is that you are feeding SVN from time to time with commits all stating libsbml (<new version>) UNRELEASED; urgency=medium and there is no signal for me if this is worth sponsering or not. Moreover we do not leave paragraphs targeting at UNRELEASED at all - if there is a new version please take over the changes to have only one single paragraph targeting at UNRELEASED "distribution" and this should be the top most paragraph. (I intended to tell you previously but may be I forgot to mention this.) Finally at least your latest commit was not ready to build. I needed to refresh the quilt patches from some fuzz - please make sure that all quilt patches apply cleanly. To fix things up I applied the patches submitted in BTS and adapted these to the latest upstream version. Sorry for the mass-commit - may be we should switch to Git for libsbml which would be sensible to my personal policy anyway to use Git in case changes to the upstream tarball are necessary. Unfortunately my commit does not build but I'm running out of ideas now how to tell cmake where to find JAVA_INCLUDE_PATH. I'm struck by ... -- Found Doxygen: /usr/bin/doxygen (found version "1.8.9.1") CMake Warning at docs/CMakeLists.txt:40 (message): Creating Documentation with CMake is experimental. Please consider configuring with gnumake, to generate documentation. CMake Error at docs/CMakeLists.txt:212 (message): Cannot generate java documentation, please specify the Java_JAVADOC_JAR. -- Configuring incomplete, errors occurred! ... and I wonder whether you might have an idea how to fix this. Please be so kind to tell me if you also have no idea or no time to fix this to let me try other means / ask somewhere else for help. I'd be also happy if you could make suggestions in general how we could enhance the sponsee - sponsor relation to guarantee a proper maintenance according to the standards we have set in the Debian Med team. Kind regards Andreas. -- http://fam-tille.de