Hi, My QuantLib packages in testing are in an inconsistent state:
Name testing unstable ---------------------------------------------------------- quantlib 0.3.8.rc.20050412-1 0.3.9-1 quantlib-python 0.3.8-2 0.3.9-1 quantlib-refman 0.3.8-1 0.3.9-1 quantlib-refman-html 0.3.8-1 0.3.9-1 quantlib-ruby 0.3.8-1 0.3.9-1 Here QuantLib is the binary library, -ruby and -python depend on it. We now have a pre-relesae of 0.3.9 in testing which is __incompatible__ with the quantlib-ruby and quantlib-python versions in testing as the API still changes between releases. I would suggest to move the whole 0.3.9 block into testing once the ten day window is up. The packages are all bug-free and "mostly" built. We currently lack a) a few m68k builds and b) quantlib-python on mipsel . For m68k, Rick Younie and I hashed out that we should stop providing QuantLib. For mipsel, I wish we could agree on the same -- the build simply timed out after 150 mins in the heavy C++ template code (which would have completed). However, I think mipsel wasn't part of the previous release and is generally behind as per http://packages.debian.org/cgi-bin/search_packages.pl?keywords=quantlib-python&searchon=names&subword=1&version=all&release=all so maybe we can overlook this as a showstopper? Lastly, and for completeness r-cran-rquantlib 0.1.12 is the only other dependency of QuantLib, and it could be pulled in too. Please email back if there are questions. Thanks, Dirk -- An economist is an expert who will know tomorrow why the things he predicted yesterday didn't happen today. -- Laurence J. Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
