Bug#319081: mono: Seriously out of date build full of problems unusable
Package: mono Version: 1.1.6-4 Severity: normal This version of mono has fundamental garbage collection bugs that have since been fixed. I highly recommend upgrading to at least mono 1.1.7, which is what wikipedia has deployed. 1.1.8.2 would be even better, of course. Please upgrade this ASAP as mono is useless to many serious developers. Thanks for your time! -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.11.5y Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages mono depends on: ii mono-common 1.1.6-4common files for Mono ii mono-jit 1.1.6-4fast CLI (.NET) JIT compiler for M -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319081: [Pkg-mono-group] Bug#319081: mono: Seriously out of date build full of problems unusable
Dear Mirco Bauer, You are using debian/testing, means you are using older packages than the most current in the debian distribution (debian/unstable). debian/unstable contains 1.1.8.2 a while now, but it does not meet debian criteria to be updated in debian/testing yet. 1.1.6 does not contain any serious bugs that prevent using Mono applications, since we used that version over a month in debian/unstable. See http://packages.qa.debian.org/m/mono.html for more details. Soon 1.1.8.2 will enter debian/testing though. While I am happy that 1.1.8.2 will be in testing soon, it's a bug that it currently isn't in testing. Our use case involved a web service and ASP.NET application that is long-running and does many large transactions. Our use case triggers the GC (and other performance) bugs that are present in mono 1.1.6. I am sure that once you test with this use case, you will understand the urgency in getting the latest mono version into testing. Consider this a release critical bug as it makes the testing version broken for this use case. When do you think the push for 1.1.8.2 to testing will take place? Thanks for your help! -- Jake Appelbaum [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319081: [Pkg-mono-group] Bug#319081: mono: Seriously out of date build full of problems unusable
On Tue, 2005-07-19 at 14:19 -0700, Jake Appelbaum wrote: Dear Mirco Bauer, Consider this a release critical bug as it makes the testing version broken for this use case. When do you think the push for 1.1.8.2 to testing will take place? 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. This bug could be serious for ASP.NET services indeed but it doesn't make Mono unusable in debian/testing at general. 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/ but this is now becoming now off topic.. Thanks for your help! -- Regards, Mirco 'meebey' Bauer PGP-Key: http://keyserver.noreply.org/pks/lookup?op=getsearch=0xEEF946C8 -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d s-:+ a-- C++ UL$ P L++$+++$ E- W+++$ N o? K- w++! O M- V? PS PE+ Y- PGP++ t 5+ X++ R tv+ b+ DI? D+ G++ e h! r-++ y? --END GEEK CODE BLOCK-- signature.asc Description: This is a digitally signed message part
Bug#319081: [Pkg-mono-group] Bug#319081: mono: Seriously out of date build full of problems unusable
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]
