From owner-freebsd-ruby@FreeBSD.ORG Sun Nov 18 04:40:28 2012 Return-Path: Delivered-To: freebsd-ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 67A2E434 for ; Sun, 18 Nov 2012 04:40:28 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.120]) by mx1.freebsd.org (Postfix) with ESMTP id 178D98FC12 for ; Sun, 18 Nov 2012 04:40:27 +0000 (UTC) X-Authority-Analysis: v=2.0 cv=KMfY/S5o c=1 sm=0 a=+L5dYfeubEW4PLvjDgtIXQ==:17 a=WAZfUmVf-EkA:10 a=EstpEZKyg6gA:10 a=05ChyHeVI94A:10 a=kj9zAlcOel0A:10 a=ayC55rCoAAAA:8 a=jhTWPf-NVpgA:10 a=bhHEUyJqAAAA:8 a=cIJ4of8vVMpmSA6RAu0A:9 a=CjuIK1q_8ugA:10 a=CChrTwsDDsUA:10 a=994rJZO4AJXS3l9X:21 a=ptBjTiHIRctmTjbR:21 a=+L5dYfeubEW4PLvjDgtIXQ==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 76.184.157.127 Received: from [76.184.157.127] ([76.184.157.127:65462] helo=[10.0.0.7]) by cdptpa-oedge02.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id E2/8E-01425-AB668A05; Sun, 18 Nov 2012 04:40:27 +0000 Date: Sat, 17 Nov 2012 22:40:25 -0600 From: Paul Schmehl To: FreeBSD Ruby List Subject: Re: More problems than I care to think about Message-ID: In-Reply-To: <50A57292.5050005@shatow.net> References: <76BB3E3F07A4F68477B30C11@utd71538.campus.ad.utdallas.edu> <50A57292.5050005@shatow.net> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Bryan Drewery X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Paul Schmehl List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 04:40:28 -0000 --On November 15, 2012 4:54:10 PM -0600 Bryan Drewery wrote: > On 11/15/2012 1:03 PM, Paul Schmehl wrote: >> I've been trying to port Snorby to FreeBSD. Emphasis on trying. I run >> into problems at every turn, and some seem unresolvable. Snorby >> requires ruby 1.9.2 or better. The default version on FreeBSD is 1.8. >> Putting RUBY_DEFAULT_VER=1.9 in /etc/make.conf breaks some of the >> rubygem ports that will only build on 1.8. >> >> sysutils/rubygem-bundler was giving me fits. I discovered that while >> the port version is 1.1.5, the current version, which fixes the problems >> I was having, is 1.2.2. I created a port update for that and was going >> to submit it, but then I discovered devel/rubygem-eventmachine "blows >> up" with a core dump if built with 1.9. >> >> This is beyond discouraging and has caused me to abandon the project >> entirely. >> >> It seems that we need a massive effort to update ruby and rails and all >> gems to the latest versions. Who is responsible for that? How can we >> get that done? >> > > I've had similar endeavors with the ruby ports. It's not that someone is > dropping the ball necessarily. Gems really do not work well as ports, in > their current form, due to their hard version dependencies. I've twice > now tried adding ports and given up, as it would mean adding multiple > new ports, copying some others for specific versions, and even > specifically for 1.9. It's all more trouble than it is worth. > > Note that I've had similar experiences with Debian as well. On my > production rails sites, I usually just give up and use gem/bundler > directly. > > I can envision this being fixed by letting gem do its own thing, and > registering those as packages, similar to bsdpan, but I don't think this > idea is popular, and I myself do not have time to implement even a > proof-of-concept. > I gave up on a port and resorted to installing gem directly, then running gem install rails and bundle install to download everything the app needs. After all that, the command 'bundle exec rake snorby:setup' failed because I had the wrong libmysqlclient.so.num file installed. (I had libmysqlclient.so.18, and the do_msql gem required libmysqlclient.so.15. Even symlinking the file failed, which is an old trick that often works.) That's beyond ridiculous. So I uninstalled the mysql client and installed the correct version. I ran the 'bundle exec' command again and got an error message that some function returned nil. At that point I REALLY gave up. Snorby might be the world's greatest app, but it is not worth the pain of rails and gem hell. Whoever designed that system had their head so far up their tookus they won't see daylight for years. Rule number one of programming is to write your programs so they're very forgiving of build dependencies. Anything above a certain version should work so long as the software is being actively maintained. But the do_mysql gem had a *hard-coded* dependency on mysql 5.0. Totally nuts. Who was the genius who decided that having hundreds of independently maintained gems was a good idea? Talk about begging for failure! I don't think there's any way the rails-gems mess could be made to work in the FreeBSD ports system. In fact, I think what's there should be stripped out. I understand the (FreeBSD ports) concern of wanting to make sure that the checksums match what you're downloading, but the rails-gems hell is not worthy of even running on FreeBSD and will never work in the FreeBSD ports system. That's the last time I'll ever try to port that mess to FreeBSD. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell From owner-freebsd-ruby@FreeBSD.ORG Sun Nov 18 15:02:58 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 12F1ABA6 for ; Sun, 18 Nov 2012 15:02:58 +0000 (UTC) (envelope-from portscout@portscout.freebsd.org) Received: from null.zi0r.com (null.zi0r.com [71.245.171.204]) by mx1.freebsd.org (Postfix) with ESMTP id C00748FC1A for ; Sun, 18 Nov 2012 15:02:57 +0000 (UTC) Received: from null.zi0r.com (localhost [127.0.0.1]) by null.zi0r.com (8.14.5/8.14.5) with ESMTP id qAIF2vf1023727 for ; Sun, 18 Nov 2012 10:02:57 -0500 (EST) (envelope-from portscout@portscout.freebsd.org) Received: (from portscout@localhost) by null.zi0r.com (8.14.5/8.14.5/Submit) id qAIF2vss023601; Sun, 18 Nov 2012 10:02:57 -0500 (EST) (envelope-from portscout) Message-Id: <201211181502.qAIF2vss023601@null.zi0r.com> MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain Date: Sun, 18 Nov 2012 10:02:57 -0500 From: portscout@portscout.freebsd.org To: ruby@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 15:02:58 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ruby@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/rubygem-minitest | 3.3.0 | 4.3.0 ------------------------------------------------+-----------------+------------ www/redmine | 1.3.1 | 2.1.3 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portscout@portscout.freebsd.org Thanks. From owner-freebsd-ruby@FreeBSD.ORG Mon Nov 19 11:07:57 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 49323502 for ; Mon, 19 Nov 2012 11:07:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 1525B8FC08 for ; Mon, 19 Nov 2012 11:07:57 +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 qAJB7uTm014776 for ; Mon, 19 Nov 2012 11:07:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qAJB7uFu014774 for ruby@FreeBSD.org; Mon, 19 Nov 2012 11:07:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 Nov 2012 11:07:56 GMT Message-Id: <201211191107.qAJB7uFu014774@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 Subject: Current problem reports assigned to ruby@FreeBSD.org X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 11:07:57 -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/173648 ruby [PATCH] security/rubygem-net-ssh: update to 2.2.2,2 o ports/173647 ruby [PATCH] devel/rubygem-highline: update to 1.6.15 o ports/173646 ruby [MAINTAINER] devel/rubygem-mixlib-authentication: upda o ports/173384 ruby New port: devel/rubygem-glib2 o ports/173382 ruby New port: graphics/rubygem-gdk_pixbuf2 o ports/173381 ruby New port: textproc/rubygem-rttool o ports/173380 ruby New port: textproc/rubygem-hikidoc o ports/173379 ruby New port: accessibility/rubygem-atk o ports/173378 ruby New port: x11-toolkits/rubygem-gtk2 o ports/173377 ruby New port: x11-toolkits/rubygem-pango o ports/173376 ruby New port: x11-toolkits/rubygem-poppler o ports/173375 ruby New port: textproc/rubygem-rdtool o ports/173374 ruby New port: graphics/rubygem-rsvg2 o ports/173373 ruby New port: graphics/rubygem-cairo o ports/172118 ruby [NEW PORT] www/rubygem-eventmachine_httpserver - Event o ports/172117 ruby [NEW PORT] www/rubygem-async_sinatra - Async plugin to o ports/172116 ruby [NEW PORT] devel/rubygem-pry-remote-em - Connect to Pr o ports/172115 ruby [NEW PORT] databases/rubygem-mysql2 - Ruby bindings fo o ports/171705 ruby [MAINTAINER] www/gist: add converters/ruby-iconv depen o ports/171010 ruby Updated port security/rubygem-net-ssh o ports/171008 ruby Updated port devel/rubygem-highline o ports/170916 ruby Mk/bsd.ruby.mk: setting RUBY variable fails to set RUB o ports/170777 ruby [PATCH] Not LIBS but LDFLAGS in Makefile of lang/ruby1 23 problems total. From owner-freebsd-ruby@FreeBSD.ORG Mon Nov 19 15:13:10 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 9A333B92 for ; Mon, 19 Nov 2012 15:13:10 +0000 (UTC) (envelope-from portscout@portscout.freebsd.org) Received: from null.zi0r.com (null.zi0r.com [71.245.171.204]) by mx1.freebsd.org (Postfix) with ESMTP id 521858FC1C for ; Mon, 19 Nov 2012 15:13:10 +0000 (UTC) Received: from null.zi0r.com (localhost [127.0.0.1]) by null.zi0r.com (8.14.5/8.14.5) with ESMTP id qAJFD4RN047410 for ; Mon, 19 Nov 2012 10:13:04 -0500 (EST) (envelope-from portscout@portscout.freebsd.org) Received: (from portscout@localhost) by null.zi0r.com (8.14.5/8.14.5/Submit) id qAJFD4KT047355; Mon, 19 Nov 2012 10:13:04 -0500 (EST) (envelope-from portscout) Message-Id: <201211191513.qAJFD4KT047355@null.zi0r.com> MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain Date: Mon, 19 Nov 2012 10:13:04 -0500 From: portscout@portscout.freebsd.org To: ruby@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 15:13:10 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ruby@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/rubygem-uuid | 2.3.5 | 2.3.6 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portscout@portscout.freebsd.org Thanks. From owner-freebsd-ruby@FreeBSD.ORG Mon Nov 19 20:29:20 2012 Return-Path: Delivered-To: freebsd-ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 438139F; Mon, 19 Nov 2012 20:29:20 +0000 (UTC) (envelope-from prvs=663f0640a=pschmehl_lists@tx.rr.com) Received: from ip-002.utdallas.edu (ip-002.utdallas.edu [129.110.20.108]) by mx1.freebsd.org (Postfix) with ESMTP id 01ABF8FC14; Mon, 19 Nov 2012 20:29:19 +0000 (UTC) X-Group: None X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsgEAC2WqlCBbgogTmdsb2JhbABFwmkBASNLgh4BAQU4Aj8QCxguQxQGExmHdMAxjDSELGEDiFqgcw X-IronPort-AV: E=Sophos;i="4.83,280,1352095200"; d="scan'208";a="100641769" Received: from zxtm01.utdallas.edu (HELO utd71538.utdallas.edu) ([129.110.10.32]) by ip-002.utdallas.edu with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Nov 2012 14:28:58 -0600 Date: Mon, 19 Nov 2012 14:28:56 -0600 From: Paul Schmehl To: FreeBSD Ruby List Subject: Re: More problems than I care to think about Message-ID: In-Reply-To: <138C62E5-F2ED-439F-AFA8-777A48B2A87B@freebsd.org> References: <76BB3E3F07A4F68477B30C11@utd71538.campus.ad.utdallas.edu> <138C62E5-F2ED-439F-AFA8-777A48B2A87B@freebsd.org> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=2620 X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Paul Schmehl List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 20:29:20 -0000 --On November 15, 2012 3:59:36 PM -0800 Stanislav Sedov wrote: > > All the ruby ports are already at the latest version and we do generally > a very good job to keep them updated (and we backport fixes and patches > regularly). Rubygems a lot more complicated as there're a lot of messy > dependencies between them and a lot of times you cannot just update > something because a lot of other stuff that depend on a particular > version will break as a result. That's why my recommendation always was > to try to keep all gems out of the ports tree unless absolutely > necessary. Frankly, it does not make much sense at all to put gems into > ports, as gems, unlike ports, support multiple versions being installed, > and a lot of ruby software depend on that feature. > > I don't know what kind of problem you're experiencing with event machine, > but I guess it is not ruby related. It'd be helpful if you can post more > info. I use eventmachine both from ports and gems for several production > application with ruby 1.9 and have not seen any segfaults (except the one > that was housed by my own C extension library). > There isn't anything wrong (that I'm aware of) with the ruby ports, but ruby-gems are a disaster. They're not up to date, and as you point out even fixing that wouldn't fix everything that's wrong with them. After completely giving up on the port I downloaded the app, downloaded gems and installed it, ran gem install rails, then went to the directory where I put the program and ran bundle install. This (supposedly) downloaded everything I needed to run the app. The next step was to create the database by running 'bundle exec rake snorby:setup'. Rake wasn't installed, so I had to install that. Running it again gave me an error that libmyslqclient.so.15 was not found. That's because I'm running 5.5, not 5.0. After fixing that, I got another error and that's when I said screw this - i've got better things to do with my time than beat a damn app into submission while taking 15 years off my life. Gems sucks. Rails sucks. The whole idea is stupid and sucks. Someone else will have to do it. I'm done with gems, rails and snorby. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell From owner-freebsd-ruby@FreeBSD.ORG Mon Nov 19 21:45:14 2012 Return-Path: Delivered-To: freebsd-ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6A552B5; Mon, 19 Nov 2012 21:45:14 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (backbone.deglitch.com [78.110.53.255]) by mx1.freebsd.org (Postfix) with ESMTP id D62D38FC08; Mon, 19 Nov 2012 21:45:13 +0000 (UTC) Received: from freebsd.corp.qc (unknown [72.5.114.2]) by mx0.deglitch.com (Postfix) with ESMTPA id 0E00F8FC2B; Tue, 20 Nov 2012 01:45:04 +0400 (MSK) Date: Mon, 19 Nov 2012 13:45:00 -0800 From: Stanislav Sedov To: Paul Schmehl Subject: Re: More problems than I care to think about Message-Id: <20121119134500.4e2ccea68e6b161f18b2efae@FreeBSD.org> In-Reply-To: References: <76BB3E3F07A4F68477B30C11@utd71538.campus.ad.utdallas.edu> <138C62E5-F2ED-439F-AFA8-777A48B2A87B@freebsd.org> Organization: The FreeBSD Project X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Ruby List X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 21:45:14 -0000 On Mon, 19 Nov 2012 14:28:56 -0600 Paul Schmehl mentioned: > --On November 15, 2012 3:59:36 PM -0800 Stanislav Sedov > wrote: > > > > All the ruby ports are already at the latest version and we do generally > > a very good job to keep them updated (and we backport fixes and patches > > regularly). Rubygems a lot more complicated as there're a lot of messy > > dependencies between them and a lot of times you cannot just update > > something because a lot of other stuff that depend on a particular > > version will break as a result. That's why my recommendation always was > > to try to keep all gems out of the ports tree unless absolutely > > necessary. Frankly, it does not make much sense at all to put gems into > > ports, as gems, unlike ports, support multiple versions being installed, > > and a lot of ruby software depend on that feature. > > > > I don't know what kind of problem you're experiencing with event machine, > > but I guess it is not ruby related. It'd be helpful if you can post more > > info. I use eventmachine both from ports and gems for several production > > application with ruby 1.9 and have not seen any segfaults (except the one > > that was housed by my own C extension library). > > > > There isn't anything wrong (that I'm aware of) with the ruby ports, but > ruby-gems are a disaster. They're not up to date, and as you point out > even fixing that wouldn't fix everything that's wrong with them. > > After completely giving up on the port I downloaded the app, downloaded > gems and installed it, ran gem install rails, then went to the directory > where I put the program and ran bundle install. This (supposedly) > downloaded everything I needed to run the app. > > The next step was to create the database by running 'bundle exec rake > snorby:setup'. Rake wasn't installed, so I had to install that. Running > it again gave me an error that libmyslqclient.so.15 was not found. That's > because I'm running 5.5, not 5.0. > > After fixing that, I got another error and that's when I said screw this - > i've got better things to do with my time than beat a damn app into > submission while taking 15 years off my life. > > Gems sucks. Rails sucks. The whole idea is stupid and sucks. > > Someone else will have to do it. I'm done with gems, rails and snorby. > I understand your frustration, I've been there too. Most of the rails/ruby stuff is intended for developers who will have to adjust stuff for their use, and not for end users. Hence a lot of utils in ruby land is optimised for development and not for deployment/delivery. I discovered too that using gems directly through bundle or rbenv or similar is much easier and productive than try to make ports work. This is mostly due to the fact that ports do not support multiple versions of the same gem installed and have no way to support the notion of a "gemset" as well. I should note though, that most gem maintainers are very nice and responsive, so you might consider submitting a patch for the mysql gem upstream that fixes the problem. -- ST4096-RIPE From owner-freebsd-ruby@FreeBSD.ORG Wed Nov 21 00:40:09 2012 Return-Path: Delivered-To: ruby@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0EA68B65; Wed, 21 Nov 2012 00:40:09 +0000 (UTC) (envelope-from edwin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id D1CE18FC1D; Wed, 21 Nov 2012 00:40:08 +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 qAL0e8R4046582; Wed, 21 Nov 2012 00:40:08 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qAL0e8jM046578; Wed, 21 Nov 2012 00:40:08 GMT (envelope-from edwin) Date: Wed, 21 Nov 2012 00:40:08 GMT Message-Id: <201211210040.qAL0e8jM046578@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, ruby@FreeBSD.org From: edwin@FreeBSD.org Subject: Re: ports/173748: [maintainer] math/ruby-narray_miss: update to 1.2.8 X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 00:40:09 -0000 Synopsis: [maintainer] math/ruby-narray_miss: update to 1.2.8 Responsible-Changed-From-To: freebsd-ports-bugs->ruby Responsible-Changed-By: edwin Responsible-Changed-When: Wed Nov 21 00:40:08 UTC 2012 Responsible-Changed-Why: ruby@ wants this port PRs (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=173748 From owner-freebsd-ruby@FreeBSD.ORG Wed Nov 21 00:40:14 2012 Return-Path: Delivered-To: ruby@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4A2ECB94; Wed, 21 Nov 2012 00:40:14 +0000 (UTC) (envelope-from edwin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 187858FC1F; Wed, 21 Nov 2012 00:40:14 +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 qAL0eDWJ046668; Wed, 21 Nov 2012 00:40:13 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qAL0eDgc046664; Wed, 21 Nov 2012 00:40:13 GMT (envelope-from edwin) Date: Wed, 21 Nov 2012 00:40:13 GMT Message-Id: <201211210040.qAL0eDgc046664@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, ruby@FreeBSD.org From: edwin@FreeBSD.org Subject: Re: ports/173749: [maintainer] science/ruby-gphys: update to 1.2.2. X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 00:40:14 -0000 Synopsis: [maintainer] science/ruby-gphys: update to 1.2.2. Responsible-Changed-From-To: freebsd-ports-bugs->ruby Responsible-Changed-By: edwin Responsible-Changed-When: Wed Nov 21 00:40:13 UTC 2012 Responsible-Changed-Why: ruby@ wants this port PRs (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=173749 From owner-freebsd-ruby@FreeBSD.ORG Wed Nov 21 08:29:02 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 5B0DCAB2 for ; Wed, 21 Nov 2012 08:29:02 +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 39CDF8FC1C for ; Wed, 21 Nov 2012 08:29:02 +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 qAL8SaBk007113 for ; Wed, 21 Nov 2012 08:28:36 GMT (envelope-from linimon@FreeBSD.org) Date: Wed, 21 Nov 2012 08:28:36 GMT Message-Id: <201211210828.qAL8SaBk007113@portsmonj.FreeBSD.org> From: linimon@FreeBSD.org To: ruby@FreeBSD.org Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 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: Wed, 21 Nov 2012 08:29:02 -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/i386-errorlogs/e.7.20120910204647/rubygem-dm-core-1.2.0.log (_Aug_18_17:45:00_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 Wed Nov 21 08:30:02 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 E762ACF6 for ; Wed, 21 Nov 2012 08:30:02 +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 D33738FC12 for ; Wed, 21 Nov 2012 08:30:02 +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 qAL8TbgV013453 for ; Wed, 21 Nov 2012 08:29:37 GMT (envelope-from linimon@FreeBSD.org) Date: Wed, 21 Nov 2012 08:29:37 GMT Message-Id: <201211210829.qAL8TbgV013453@portsmonj.FreeBSD.org> From: linimon@FreeBSD.org To: ruby@FreeBSD.org Subject: FreeBSD ports that you maintain which are currently scheduled for deletion X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 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: Wed, 21 Nov 2012 08:30:03 -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. From owner-freebsd-ruby@FreeBSD.ORG Thu Nov 22 15:59:27 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 86BC2E5 for ; Thu, 22 Nov 2012 15:59:27 +0000 (UTC) (envelope-from portscout@portscout.freebsd.org) Received: from null.zi0r.com (null.zi0r.com [71.245.171.204]) by mx1.freebsd.org (Postfix) with ESMTP id 4226F8FC0C for ; Thu, 22 Nov 2012 15:59:27 +0000 (UTC) Received: from null.zi0r.com (localhost [127.0.0.1]) by null.zi0r.com (8.14.5/8.14.5) with ESMTP id qAMFcX5K003986 for ; Thu, 22 Nov 2012 10:38:33 -0500 (EST) (envelope-from portscout@portscout.freebsd.org) Received: (from portscout@localhost) by null.zi0r.com (8.14.5/8.14.5/Submit) id qAMFcXtp003779; Thu, 22 Nov 2012 10:38:33 -0500 (EST) (envelope-from portscout) Message-Id: <201211221538.qAMFcXtp003779@null.zi0r.com> MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain Date: Thu, 22 Nov 2012 10:38:33 -0500 From: portscout@portscout.freebsd.org To: ruby@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 15:59:27 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ruby@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/rubygem-icalendar | 1.1.6 | 1.2.1 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portscout@portscout.freebsd.org Thanks.