On Tue, 2013-01-29 at 17:21 +0000, Jo Shields wrote: > On Sun, 2013-01-27 at 21:45 +0000, Adam D. Barratt wrote: > > Assuming that supporting mono/armhf in a stable release is still not > > practical, is there anything we can do to help move this forward? [...] > 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.
Thanks; I've unblocked that as an aid to showing us what's still broken. virtuoso-opensource has been uploaded and unblocked and #699542 filed for the tidy-up. I've just filed #699568-72 for the binary removals for mod-mono, activiz.net, mono-fuse, fsgateway and mummy. That'll just leave us with gdcm. Regards, Adam -- 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/1359756540.10585.32.ca...@jacala.jungle.funky-badger.org