From owner-freebsd-ruby@FreeBSD.ORG Mon Jan 2 11:08:47 2012 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B31D71065678 for ; Mon, 2 Jan 2012 11:08:47 +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 87C108FC0C for ; Mon, 2 Jan 2012 11:08:47 +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 q02B8llf006577 for ; Mon, 2 Jan 2012 11:08:47 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q02B8kM1006575 for ruby@FreeBSD.org; Mon, 2 Jan 2012 11:08:46 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 2 Jan 2012 11:08:46 GMT Message-Id: <201201021108.q02B8kM1006575@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: ruby@FreeBSD.org Cc: Subject: Current problem reports assigned to ruby@FreeBSD.org X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2012 11:08:47 -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/162994 ruby www/redmine fails to start o ports/162895 ruby [PATCH] devel/ruby-gems: add MASTER_SITES o ports/162212 ruby ports-mgmt/portupgrade: portversion -r doesn't work o ports/160291 ruby devel/rubygem-rake 0.9.2 update breaks redmine s ports/156066 ruby [NEW PORT] databases/rubygem-xapian-full (self contain o ports/151662 ruby ports-mgmt/portupgrade: upgrade of autoconf leaves old o ports/149817 ruby [wishlist] ports-mgmt/portupgrade: portinstall -p opti o ports/147242 ruby ports-mgmt/portupgrade incorrectly remove old port whe o ports/144769 ruby [PATCH] ports-mgmt/portupgrade should have a configura o ports/140364 ruby [patch] ports-mgmt/portupgrade-devel: #! line substitu o ports/140273 ruby ports-mgmt/portupgrade-devel chokes on bsdpan pkgs o ports/140008 ruby ports-mgmt/portupgrade: many papercut omissions on por o ports/137958 ruby [patch] ports-mgmt/portupgrade fails with recursive de s ports/134714 ruby ports-mgmt/portupgrade deletes user data without quest o ports/132294 ruby [PATCH] lang/ruby18: Add option to build with Profile- o ports/132293 ruby [PATCH] lang/ruby19: Add option to build with Profile- o ports/131111 ruby ports-mgmt/portupgrade-devel: completely removes packa o ports/129930 ruby ports-mgmt/portupgrade - portinstall tries to install s ports/129891 ruby ports-mgmt/portupgrade fails to recognize variations o o ports/127889 ruby ports-mgmt/portupgrade detects spurious failures and s o ports/127019 ruby ports-mgmt/portupgrade does not recognize fail conditi f ports/126140 ruby ports-mgmt/portupgrade runtime error o ports/112818 ruby ports-mgmt/portupgrade -a fails with database error 23 problems total. From owner-freebsd-ruby@FreeBSD.ORG Sat Jan 7 08:28:33 2012 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1732C106567A for ; Sat, 7 Jan 2012 08:28:33 +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 E45348FC16 for ; Sat, 7 Jan 2012 08:28:32 +0000 (UTC) Received: from portsmonj.freebsd.org (portsmonj.freebsd.org [69.147.83.46]) by portsmonj.FreeBSD.org (8.14.4/8.14.4) with ESMTP id q078SWD6065581 for ; Sat, 7 Jan 2012 08:28:32 GMT (envelope-from linimon@FreeBSD.org) Date: Sat, 7 Jan 2012 08:28:32 GMT Message-Id: <201201070828.q078SWD6065581@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: Sat, 07 Jan 2012 08:28:33 -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: devel/rubygem-ruby-debug-ide broken because: incomplete plist build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20111229011106/rubygem-ruby-debug-ide-0.4.16.log (_Jan__7_01:41:53_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=rubygem-ruby-debug-ide portname: www/redmine broken because: Does not work with RubyGems 1.8 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=redmine 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.