From owner-freebsd-ruby@FreeBSD.ORG Sun Oct 7 08:28:36 2012 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 343FD10656C3 for ; Sun, 7 Oct 2012 08:28:36 +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 15AC88FC1A for ; Sun, 7 Oct 2012 08:28:36 +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 q978SaqO061437 for ; Sun, 7 Oct 2012 08:28:36 GMT (envelope-from linimon@FreeBSD.org) Date: Sun, 7 Oct 2012 08:28:36 GMT Message-Id: <201210070828.q978SaqO061437@portsmonj.FreeBSD.org> From: linimon@FreeBSD.org To: ruby@FreeBSD.org Cc: Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2012 08:28:36 -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: databases/ruby-kyotocabinet broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=ruby-kyotocabinet portname: databases/rubygem-delayed_job_data_mapper broken because: delayed_job_data_mapper requires delayed_job (~> 2.1) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=rubygem-delayed_job_data_mapper portname: databases/rubygem-dm-core broken because: unable to resolve dependencies build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9.20120929073003/rubygem-dm-core-1.2.0.log (_Aug_10_14:37:37_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=rubygem-dm-core portname: japanese/rubygem-myrurema broken because: unable to resolve dependencies build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20120812220927/ja-rubygem-myrurema-0.3.0.log (_Aug_19_05:48:13_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=rubygem-myrurema 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-ruby@FreeBSD.ORG Sun Oct 7 08:29:40 2012 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F0D1B10656C2 for ; Sun, 7 Oct 2012 08:29:39 +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 DF3348FC12 for ; Sun, 7 Oct 2012 08:29:39 +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 q978Tduo067931 for ; Sun, 7 Oct 2012 08:29:39 GMT (envelope-from linimon@FreeBSD.org) Date: Sun, 7 Oct 2012 08:29:39 GMT Message-Id: <201210070829.q978Tduo067931@portsmonj.FreeBSD.org> From: linimon@FreeBSD.org To: ruby@FreeBSD.org Cc: Subject: FreeBSD ports that you maintain which are currently scheduled for deletion X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2012 08:29:40 -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: databases/ruby-kyotocabinet description: Ruby (1.9.1+) binding to Kyoto Cabinet maintainer: ruby@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=databases&portname=ruby-kyotocabinet 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.