From owner-freebsd-mono@FreeBSD.ORG Mon Dec 16 11:07:43 2013 Return-Path: Delivered-To: mono@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 26B9162D for ; Mon, 16 Dec 2013 11:07:43 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 13072144E for ; Mon, 16 Dec 2013 11:07:43 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rBGB7gl8020447 for ; Mon, 16 Dec 2013 11:07:42 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rBGB7gKD020443 for mono@FreeBSD.org; Mon, 16 Dec 2013 11:07:42 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Dec 2013 11:07:42 GMT Message-Id: <201312161107.rBGB7gKD020443@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: mono@FreeBSD.org Subject: Current problem reports assigned to mono@FreeBSD.org X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 11:07:43 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/184033 mono Add staging support to mail/gmime2-sharp gmime24-sharp o ports/183396 mono [PATCH] devel/monodevelop: update to 4.0.13 o ports/182943 mono [patch] www/mod_mono won't build if Apache 2.4 is inst o ports/181361 mono Update lang/fsharp to 3.0.27 4 problems total. From owner-freebsd-mono@FreeBSD.ORG Sat Dec 21 08:28:14 2013 Return-Path: Delivered-To: mono@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D00356F4 for ; Sat, 21 Dec 2013 08:28:14 +0000 (UTC) Received: from portsmon.freebsd.org (portsmon.freebsd.org [IPv6:2001:1900:2254:206a::50:3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A60A912A0 for ; Sat, 21 Dec 2013 08:28:14 +0000 (UTC) Received: from portsmon.freebsd.org ([127.0.1.104]) by portsmon.freebsd.org (8.14.7/8.14.7) with ESMTP id rBL8SENO045587 for ; Sat, 21 Dec 2013 08:28:14 GMT (envelope-from linimon@FreeBSD.org) Date: Sat, 21 Dec 2013 08:28:14 GMT Message-Id: <201312210828.rBL8SENO045587@portsmon.freebsd.org> From: linimon@FreeBSD.org To: mono@freebsd.org Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Dec 2013 08:28:14 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: devel/hyena broken because: Does not build with recent mono build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hyena portname: graphics/f-spot broken because: Does not build with latest Mono build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=f-spot If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. From owner-freebsd-mono@FreeBSD.ORG Sat Dec 21 08:28:43 2013 Return-Path: Delivered-To: mono@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D55E940 for ; Sat, 21 Dec 2013 08:28:43 +0000 (UTC) Received: from portsmon.freebsd.org (portsmon.freebsd.org [IPv6:2001:1900:2254:206a::50:3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8DAC512E8 for ; Sat, 21 Dec 2013 08:28:43 +0000 (UTC) Received: from portsmon.freebsd.org ([127.0.1.104]) by portsmon.freebsd.org (8.14.7/8.14.7) with ESMTP id rBL8Shvh049678 for ; Sat, 21 Dec 2013 08:28:43 GMT (envelope-from linimon@FreeBSD.org) Date: Sat, 21 Dec 2013 08:28:43 GMT Message-Id: <201312210828.rBL8Shvh049678@portsmon.freebsd.org> From: linimon@FreeBSD.org To: mono@freebsd.org Subject: FreeBSD ports that you maintain which are currently scheduled for deletion X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Dec 2013 08:28:43 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: graphics/f-spot description: Personal photo management to the GNOME desktop maintainer: mono@FreeBSD.org status: BROKEN deprecated because: Broken for more than 6 month expiration date: 2013-12-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=f-spot If this problem is one that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Thanks for your efforts to help improve FreeBSD.