I don't know how to handle this: My swig package in frozen has a small, but `important' bug dealing with version numbers (#20068, swig: dpkg thinks 1.1p5-1 < 1.1.b5.p2-1).
I thought about simply rebuilding the package with a changed revision number "1.1.p5-1" which would fix the bug in a very transparent way. But when I compared the resulting packages, I found that the old package had been built with a g++/libstdc++ based on 2.7.2, while nowadays g++ 2.90 is the official C++ compiler, going with libstdc++2.8. Now I don't know: When I recompile the package using the official g++ 2.90 / libstdc++ 2.80 combo, this may introduce new bugs, therefore I'm sure Brian won't allow this to go into frozen. The alternative is faking an build environment that installs g++272 as c++ and uses libstdc++272. Is this the accepted way to go ? Gregor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]