From owner-freebsd-mono@FreeBSD.ORG Mon Sep 17 11:08:19 2012 Return-Path: Delivered-To: mono@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 287361065757 for ; Mon, 17 Sep 2012 11:08:19 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 81D108FC1C for ; Mon, 17 Sep 2012 11:08:18 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q8HB8IeE005455 for ; Mon, 17 Sep 2012 11:08:18 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q8HB8HSY005453 for mono@FreeBSD.org; Mon, 17 Sep 2012 11:08:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 17 Sep 2012 11:08:17 GMT Message-Id: <201209171108.q8HB8HSY005453@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 Cc: Subject: Current problem reports assigned to mono@FreeBSD.org X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Sep 2012 11:08:19 -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/164364 mono New port: multimedia/banshee-devel Music management an o ports/162320 mono lang/mono doesn't build a ports/144224 mono [PATCH] lang/mono Fix build with new GCC 3 problems total. From owner-freebsd-mono@FreeBSD.ORG Mon Sep 17 14:25:52 2012 Return-Path: Delivered-To: mono@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07E0A106564A; Mon, 17 Sep 2012 14:25:52 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from marvin.blogreen.org (marvin.blogreen.org [109.190.4.139]) by mx1.freebsd.org (Postfix) with ESMTP id B87418FC14; Mon, 17 Sep 2012 14:25:51 +0000 (UTC) Received: by marvin.blogreen.org (Postfix, from userid 1001) id 5816F46A47; Mon, 17 Sep 2012 16:25:49 +0200 (CEST) Date: Mon, 17 Sep 2012 16:25:49 +0200 From: Romain =?iso-8859-1?Q?Tarti=E8re?= To: Koop Mast Message-ID: <20120917142549.GA92810@blogreen.org> References: <1344769606.22792.13.camel@crashalot.rainbow-runner.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1344769606.22792.13.camel@crashalot.rainbow-runner.nl> X-PGP-Key: http://romain.blogreen.org/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Cc: mono@freebsd.org Subject: Re: new gmime26-sharp port X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Sep 2012 14:25:52 -0000 Hello! On Sun, Aug 12, 2012 at 01:06:46PM +0200, Koop Mast wrote: > I'm working on a PR to make a mail/gmime26 port, and I noticed the 2.4 > port has a sharp slave port. So I was thinking of making one for 2.6 > also at the same time. So I would like for approval to assign the -sharp > port to mono@ like the current 2.4 version is. > > Attached is my current working copy of the new 2.6 port. Sorry for the late answer (vacations...). I have no objection for mono@ becoming MAINTAINER of this port. Feel free to do this. Thanks! Romain From owner-freebsd-mono@FreeBSD.ORG Mon Sep 17 14:34:05 2012 Return-Path: Delivered-To: mono@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 024F1106566B; Mon, 17 Sep 2012 14:34:05 +0000 (UTC) (envelope-from kwm@rainbow-runner.nl) Received: from fep13.mx.upcmail.net (fep13.mx.upcmail.net [62.179.121.33]) by mx1.freebsd.org (Postfix) with ESMTP id E37358FC14; Mon, 17 Sep 2012 14:34:03 +0000 (UTC) Received: from edge01.upcmail.net ([192.168.13.236]) by viefep13-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20120917143402.UDCK3518.viefep13-int.chello.at@edge01.upcmail.net>; Mon, 17 Sep 2012 16:34:02 +0200 Received: from [127.0.0.1] ([178.84.132.32]) by edge01.upcmail.net with edge id 0Ea11k00Q0i5fp601Ea1Jw; Mon, 17 Sep 2012 16:34:02 +0200 X-SourceIP: 178.84.132.32 Message-ID: <505734DA.6030104@rainbow-runner.nl> Date: Mon, 17 Sep 2012 16:34:02 +0200 From: Koop Mast User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Romain_Tarti=E8re?= References: <1344769606.22792.13.camel@crashalot.rainbow-runner.nl> <20120917142549.GA92810@blogreen.org> In-Reply-To: <20120917142549.GA92810@blogreen.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 120917-0, 17-09-2012), Outbound message X-Antivirus-Status: Clean Cc: Koop Mast , mono@freebsd.org Subject: Re: new gmime26-sharp port X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Sep 2012 14:34:05 -0000 On 17-9-2012 16:25, Romain Tartière wrote: > Hello! > > On Sun, Aug 12, 2012 at 01:06:46PM +0200, Koop Mast wrote: >> I'm working on a PR to make a mail/gmime26 port, and I noticed the 2.4 >> port has a sharp slave port. So I was thinking of making one for 2.6 >> also at the same time. So I would like for approval to assign the -sharp >> port to mono@ like the current 2.4 version is. >> >> Attached is my current working copy of the new 2.6 port. > Sorry for the late answer (vacations...). I have no objection for mono@ > becoming MAINTAINER of this port. Feel free to do this. > > Thanks! > > Romain Thanks. From owner-freebsd-mono@FreeBSD.ORG Fri Sep 21 08:28:25 2012 Return-Path: Delivered-To: mono@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 97DA91065689 for ; Fri, 21 Sep 2012 08:28:25 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from portsmonj.FreeBSD.org (portsmonj.freebsd.org [69.147.83.46]) by mx1.freebsd.org (Postfix) with ESMTP id 78AC78FC16 for ; Fri, 21 Sep 2012 08:28:25 +0000 (UTC) Received: from portsmonj.freebsd.org (portsmonj.freebsd.org [69.147.83.46]) by portsmonj.FreeBSD.org (8.14.5/8.14.4) with ESMTP id q8L8SPfk049323 for ; Fri, 21 Sep 2012 08:28:25 GMT (envelope-from linimon@FreeBSD.org) Date: Fri, 21 Sep 2012 08:28:25 GMT Message-Id: <201209210828.q8L8SPfk049323@portsmonj.FreeBSD.org> From: linimon@FreeBSD.org To: mono@FreeBSD.org Cc: Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 21 Sep 2012 08:28:25 -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/mono-tools broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=mono-tools portname: devel/monodevelop-java broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=monodevelop-java portname: devel/monodevelop-vala broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=monodevelop-vala portname: irc/smuxi broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=irc&portname=smuxi portname: lang/boo broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=boo 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 Fri Sep 21 08:29:24 2012 Return-Path: Delivered-To: mono@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9FD9E1065687 for ; Fri, 21 Sep 2012 08:29:24 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from portsmonj.FreeBSD.org (portsmonj.freebsd.org [69.147.83.46]) by mx1.freebsd.org (Postfix) with ESMTP id 5E4B98FC1E for ; Fri, 21 Sep 2012 08:29:24 +0000 (UTC) Received: from portsmonj.freebsd.org (portsmonj.freebsd.org [69.147.83.46]) by portsmonj.FreeBSD.org (8.14.5/8.14.4) with ESMTP id q8L8TOwQ056090 for ; Fri, 21 Sep 2012 08:29:24 GMT (envelope-from linimon@FreeBSD.org) Date: Fri, 21 Sep 2012 08:29:24 GMT Message-Id: <201209210829.q8L8TOwQ056090@portsmonj.FreeBSD.org> From: linimon@FreeBSD.org To: mono@FreeBSD.org Cc: Subject: FreeBSD ports that you maintain which are currently scheduled for deletion X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 21 Sep 2012 08:29:24 -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: lang/boo description: A CLI-targeted programming language similar to Python maintainer: mono@FreeBSD.org status: BROKEN deprecated because: BROKEN for more than 6 month expiration date: 2012-05-10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=boo 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.