On Sun, 2013-01-27 at 21:45 +0000, Adam D. Barratt wrote: > On Sat, 2012-12-08 at 15:46 +0000, Adam D. Barratt wrote: > > On Wed, 2012-08-08 at 18:38 +0100, Jo Shields wrote: > > > ===== > > > Bug#682284: mono-runtime: SIGSEGV while executing native code on armhf[0] > > > ===== > > > > This got solved via: > > > > > 2) remove armhf as an architecture for Mono, > > > > in the end. CVE-2012-3543 came along just afterwards and things seem to > > have fallen off the radar a little after that. :-( Currently, wheezy > > still has a version of mono that generates armhf binaries. > > That was approaching a couple of months ago now and from a quick look > using today's archive data it doesn't appear that the situation has > changed. > > Assuming that supporting mono/armhf in a stable release is still not > practical, is there anything we can do to help move this forward?
Sorry about the lack of updates. I should stop listening to "I'm gonna upload a fix" comments from other people too. I've uploaded a -7 package, which addresses CVE-2012-3543 and #695743 (the outstanding armhf issue affecting various non-mono-team leaf packages). It's built fine on all arches, although since it's a day with a Y in it the ia64 build hasn't been uploaded yet. With any luck, that should allow outstanding armhf packages (mostly from debian-med) to drop out of the archive, and let us move this forwards. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1359480097.7292.23.camel@barnabas