On Tue, 2005-07-19 at 23:31 +0200, Mirco Bauer wrote: > The QA URL I pasted shows the state of updating mono in debian/testing. > Could be 1-2 weeks before it hits debian/testing, many on going > transistions in debian/unstable.
Alright. Thanks. > This bug could be serious for ASP.NET services indeed but it doesn't > make Mono unusable in debian/testing at general. Well, if you're writing helloworld.cs, sure, it's not a problem. If you're using a program in any serious fashion, you're unable to actually use mono. It will crash or hang or die in some mysterious way and the reason is related to the previous issues that I expressed. This is a release critical bug IMHO. The updates since then expressly fix these issues because of the performance of this use case. Anyway, this shouldn't be a wishlist bug. It's critical and should be tagged as such. The version in testing is broken for anyone using mono when it's running for a long period of time. The methods used for testing mono in debian aren't sufficiently able to find these memory management issues. That doesn't mean that mono isn't broken. That means it's also a bug in how you're testing mono. It doesn't exclude the fact that mono is also in need of a critical upgrade. > If you can't wait install the packages from debian/unstable (be warned, > debian/unstable is in a C++ transistion) or install the Mono 1.1.8.2 > debian/sarge backports (they should work for debian/etch). > > The backports you can find here > http://people.debian.org/~formorer/mono/ This will be useful to anyone else that has this problem. Thanks for including it in the email. Thanks, -- Jake Appelbaum <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
