From bugmaster at FreeBSD.org Mon Aug 3 11:08:33 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 3 11:11:48 2009 Subject: Current problem reports assigned to ruby@FreeBSD.org Message-ID: <200908031108.n73B8SvE090241@freefall.freebsd.org> 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/136722 ruby ports-mgmt/portupgrade - portversion issues Stale lock o ports/136056 ruby ports-mgmt/portupgrade 2009-06-25 breaks textproc/meld o ports/135691 ruby ports-mgmt/portupgrade Wrong example in man page of pk o ports/135466 ruby ports-mgmt/portupgrade leaves orphaned lock files sinc o ports/135201 ruby ports-mgmt/portupgrade: doesn't upgrade lang/tcc s ports/134714 ruby ports-mgmt/portupgrade deletes user data without quest o ports/134182 ruby ports-mgmt/portupgrade incorrectly handles manual reje o ports/131111 ruby ports-mgmt/portupgrade-devel: completely removes packa o ports/129930 ruby ports-mgmt/portupgrade - portinstall tries to install o ports/129891 ruby ports-mgmt/portupgrade fails to recognize variations o o ports/128881 ruby ports-mgmt/portupgrade backtrace o ports/127889 ruby ports-mgmt/portupgrade detects spurious failures and s o ports/127019 ruby ports-mgmt/portupgrade does not recognize fail conditi o ports/126140 ruby ports-mgmt/portupgrade runtime error o ports/125936 ruby ports-mgmt/portupgrade -R fails if BUILD_DEP's are not o ports/125823 ruby [PATCH] ports-mgmt/portupgrade does not use custom ECH o ports/112818 ruby ports-mgmt/portupgrade -a fails with database error o ports/100776 ruby ports-mgmt/portupgrade: Failure to update devel/mico b 18 problems total. From pgollucci at p6m7g8.com Thu Aug 6 05:39:56 2009 From: pgollucci at p6m7g8.com (Philip M. Gollucci) Date: Thu Aug 6 05:40:03 2009 Subject: changes in ruby_dbb_pg In-Reply-To: <7fX59rRu5S@dmeyer.dinoex.sub.org> References: <7fX59rRu5S@dmeyer.dinoex.sub.org> Message-ID: <4A7A6A44.4070400@p6m7g8.com> enotime to ponder it until after 08/11. It looks okay in principle, but if you change it, all similiar ruby_dbd* gems should match with the .so s. http://portscout.org/ruby@freebsd.org.html an upgrade would be nice too while your there but might be more then you bargained for. Dirk Meyer wrote: > Hello, > > I want to switch the dependecies of database/ruby_dbb_pg > > Current: > rubygem-postgres>=0:${PORTSDIR}/databases/rubygem-postgres > > Problem is that any ruby application needs an explict change in source: > [...] > require 'rubygems' # needed Postgres-gem backend > require 'dbi' # Postgres backend > [...] > > I like to revert this to the old behaviour. So the code needs only: > [...] > require 'dbi' # Postgres backend > [...] > > The new dependecy will be: > ${RUBY_SITEARCHLIBDIR}/postgres.so:${.CURDIR}/../ruby-postgres > > Please voice any objection you do have here or in private mail. > > kind regards Dirk > > - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany > - [dirk.meyer@dinoex.sub.org],[dirk.meyer@guug.de],[dinoex@FreeBSD.org] > http://people.freebsd.org/~dinoex/errorlogs/ > _______________________________________________ > freebsd-ruby@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ruby > To unsubscribe, send any mail to "freebsd-ruby-unsubscribe@freebsd.org" From stas at FreeBSD.org Thu Aug 6 07:06:17 2009 From: stas at FreeBSD.org (Stanislav Sedov) Date: Thu Aug 6 07:06:23 2009 Subject: changes in ruby_dbb_pg In-Reply-To: <4A7A6A44.4070400@p6m7g8.com> References: <7fX59rRu5S@dmeyer.dinoex.sub.org> <4A7A6A44.4070400@p6m7g8.com> Message-ID: <20090806110614.e648d154.stas@FreeBSD.org> On Thu, 6 Aug 2009 01:29:40 -0400 "Philip M. Gollucci" mentioned: > enotime to ponder it until after 08/11. > > It looks okay in principle, but if you change it, all similiar ruby_dbd* > gems should match with the .so s. > What do you meen. I think this change will not require any changes in dependent ports at all, as both -gem and not gem ports will just work using the proper 'require' clause that they already use. -- Stanislav Sedov ST4096-RIPE -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 801 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ruby/attachments/20090806/f3df5a13/attachment.pgp From linimon at FreeBSD.org Fri Aug 7 06:28:41 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Fri Aug 7 06:28:48 2009 Subject: FreeBSD ports that you maintain which are currently marked broken Message-ID: <20090807062840.836351CC91@mail.droso.net> 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 6.x/7.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: x11-toolkits/ruby-panelapplet broken because: does not build with GNOME 2.26. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=ruby-panelapplet 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 bugmaster at FreeBSD.org Mon Aug 10 11:08:29 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 10 11:10:40 2009 Subject: Current problem reports assigned to ruby@FreeBSD.org Message-ID: <200908101108.n7AB8Rh6026725@freefall.freebsd.org> 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/136722 ruby ports-mgmt/portupgrade - portversion issues Stale lock o ports/136056 ruby ports-mgmt/portupgrade 2009-06-25 breaks textproc/meld o ports/135691 ruby ports-mgmt/portupgrade Wrong example in man page of pk o ports/135466 ruby ports-mgmt/portupgrade leaves orphaned lock files sinc o ports/135201 ruby ports-mgmt/portupgrade: doesn't upgrade lang/tcc s ports/134714 ruby ports-mgmt/portupgrade deletes user data without quest o ports/134182 ruby ports-mgmt/portupgrade incorrectly handles manual reje o ports/131111 ruby ports-mgmt/portupgrade-devel: completely removes packa o ports/129930 ruby ports-mgmt/portupgrade - portinstall tries to install o ports/129891 ruby ports-mgmt/portupgrade fails to recognize variations o o ports/128881 ruby ports-mgmt/portupgrade backtrace o ports/127889 ruby ports-mgmt/portupgrade detects spurious failures and s o ports/127019 ruby ports-mgmt/portupgrade does not recognize fail conditi o ports/126140 ruby ports-mgmt/portupgrade runtime error o ports/125936 ruby ports-mgmt/portupgrade -R fails if BUILD_DEP's are not o ports/125823 ruby [PATCH] ports-mgmt/portupgrade does not use custom ECH o ports/112818 ruby ports-mgmt/portupgrade -a fails with database error o ports/100776 ruby ports-mgmt/portupgrade: Failure to update devel/mico b 18 problems total. From linimon at FreeBSD.org Thu Aug 13 02:09:06 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu Aug 13 02:09:12 2009 Subject: ports/137708: ports-mgmt/portupgrade: portupgrade -cRn is broken Message-ID: <200908130209.n7D295ff023386@freefall.freebsd.org> Old Synopsis: portupgrade -cRn is broken New Synopsis: ports-mgmt/portupgrade: portupgrade -cRn is broken Responsible-Changed-From-To: freebsd-ports-bugs->ruby Responsible-Changed-By: linimon Responsible-Changed-When: Thu Aug 13 02:08:13 UTC 2009 Responsible-Changed-Why: Fix synopsis and assign. http://www.freebsd.org/cgi/query-pr.cgi?pr=137708 From marka at isc.org Thu Aug 13 05:30:10 2009 From: marka at isc.org (Mark Andrews) Date: Thu Aug 13 05:30:16 2009 Subject: ports/137708: portupgrade -cRn is broken Message-ID: <200908130530.n7D5U90O080698@freefall.freebsd.org> The following reply was made to PR ports/137708; it has been noted by GNATS. From: Mark Andrews To: FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: ports/137708: portupgrade -cRn is broken Date: Thu, 13 Aug 2009 15:23:41 +1000 To make it easier to debug this minimal invokation fails. Both net-im/psi and graphics/qt4-iconengines succeed individually. Note net-im/psi depends on graphics/qt4-iconengines. I suspect something is not handling a null set. Mark drugs# portupgrade -cRn net-im/psi graphics/qt4-iconengines ---> Session started at: Thu, 13 Aug 2009 15:03:22 +1000 [Gathering depends for net-im/psi ................................................................................................................................................................................................................................................................................................................................................................................................................................................................ done] [Exclude up-to-date packages .......................................................................................................................... done] ---> Session ended at: Thu, 13 Aug 2009 15:04:11 +1000 (consumed 00:00:48) /usr/local/lib/ruby/site_ruby/1.8/pkginfo.rb:74:in `initialize': : Not in due form: - (ArgumentError) from /usr/local/sbin/portupgrade:614:in `new' from /usr/local/sbin/portupgrade:614:in `main' from /usr/local/sbin/portupgrade:613:in `each' from /usr/local/sbin/portupgrade:613:in `main' from /usr/local/sbin/portupgrade:588:in `catch' from /usr/local/sbin/portupgrade:588:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:1310:in `call' from /usr/local/lib/ruby/1.8/optparse.rb:1310:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1306:in `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1306:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1248:in `order!' from /usr/local/lib/ruby/1.8/optparse.rb:1241:in `order' from /usr/local/sbin/portupgrade:565:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:791:in `initialize' from /usr/local/sbin/portupgrade:229:in `new' from /usr/local/sbin/portupgrade:229:in `main' from /usr/local/sbin/portupgrade:2208 drugs# -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org From bugmaster at FreeBSD.org Mon Aug 17 11:08:23 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 17 11:11:00 2009 Subject: Current problem reports assigned to ruby@FreeBSD.org Message-ID: <200908171108.n7HB8MZX077310@freefall.freebsd.org> 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/137708 ruby ports-mgmt/portupgrade: portupgrade -cRn is broken o ports/136722 ruby ports-mgmt/portupgrade - portversion issues Stale lock o ports/136056 ruby ports-mgmt/portupgrade 2009-06-25 breaks textproc/meld o ports/135691 ruby ports-mgmt/portupgrade Wrong example in man page of pk o ports/135466 ruby ports-mgmt/portupgrade leaves orphaned lock files sinc o ports/135201 ruby ports-mgmt/portupgrade: doesn't upgrade lang/tcc s ports/134714 ruby ports-mgmt/portupgrade deletes user data without quest o ports/134182 ruby ports-mgmt/portupgrade incorrectly handles manual reje o ports/131111 ruby ports-mgmt/portupgrade-devel: completely removes packa o ports/129930 ruby ports-mgmt/portupgrade - portinstall tries to install o ports/129891 ruby ports-mgmt/portupgrade fails to recognize variations o o ports/128881 ruby ports-mgmt/portupgrade backtrace o ports/127889 ruby ports-mgmt/portupgrade detects spurious failures and s o ports/127019 ruby ports-mgmt/portupgrade does not recognize fail conditi o ports/126140 ruby ports-mgmt/portupgrade runtime error o ports/125936 ruby ports-mgmt/portupgrade -R fails if BUILD_DEP's are not o ports/125823 ruby [PATCH] ports-mgmt/portupgrade does not use custom ECH o ports/112818 ruby ports-mgmt/portupgrade -a fails with database error o ports/100776 ruby ports-mgmt/portupgrade: Failure to update devel/mico b 19 problems total. From miwi at FreeBSD.org Wed Aug 19 10:30:13 2009 From: miwi at FreeBSD.org (miwi@FreeBSD.org) Date: Wed Aug 19 10:30:19 2009 Subject: ports/137958: portupgrade fails with recursive dependency error Message-ID: <200908191030.n7JAUCra064165@freefall.freebsd.org> Synopsis: portupgrade fails with recursive dependency error Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-ruby Responsible-Changed-By: miwi Responsible-Changed-When: Wed Aug 19 10:30:12 UTC 2009 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=137958 From linimon at FreeBSD.org Wed Aug 19 14:51:24 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Aug 19 14:51:34 2009 Subject: ports/137958: ports-mgmt/portupgrade fails with recursive dependency error Message-ID: <200908191451.n7JEpN4k073967@freefall.freebsd.org> Old Synopsis: portupgrade fails with recursive dependency error New Synopsis: ports-mgmt/portupgrade fails with recursive dependency error Responsible-Changed-From-To: freebsd-ruby->ruby Responsible-Changed-By: linimon Responsible-Changed-When: Wed Aug 19 14:50:50 UTC 2009 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=137958 From linimon at FreeBSD.org Wed Aug 19 14:51:24 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Aug 19 14:51:35 2009 Subject: ports/137958: ports-mgmt/portupgrade fails with recursive dependency error Message-ID: <200908191451.n7JEpN4k073967@freefall.freebsd.org> Old Synopsis: portupgrade fails with recursive dependency error New Synopsis: ports-mgmt/portupgrade fails with recursive dependency error Responsible-Changed-From-To: freebsd-ruby->ruby Responsible-Changed-By: linimon Responsible-Changed-When: Wed Aug 19 14:50:50 UTC 2009 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=137958 From linimon at FreeBSD.org Fri Aug 21 06:39:52 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Fri Aug 21 06:40:27 2009 Subject: FreeBSD ports that you maintain which are currently scheduled for deletion Message-ID: <20090821062950.278B31CDA4@mail.droso.net> 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-dbd_interbase description: InterBase driver for DBI-for-Ruby maintainer: ruby@FreeBSD.org deprecated because: no longer under development expiration date: 2009-10-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=ruby-dbd_interbase portname: databases/ruby-dbd_msql description: mSQL driver for DBI-for-Ruby maintainer: ruby@FreeBSD.org deprecated because: no longer under development expiration date: 2009-10-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=ruby-dbd_msql portname: databases/ruby-dbd_proxy description: Proxy/Server driver for DBI-for-Ruby maintainer: ruby@FreeBSD.org deprecated because: no longer under development expiration date: 2009-10-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=ruby-dbd_proxy 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 linimon at FreeBSD.org Fri Aug 21 06:45:08 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Fri Aug 21 06:45:34 2009 Subject: FreeBSD ports that you maintain which are currently marked broken Message-ID: <20090821062850.496C81CD58@mail.droso.net> 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 6.x/7.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: x11-toolkits/ruby-panelapplet broken because: does not build with GNOME 2.26. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=ruby-panelapplet 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 edwin at FreeBSD.org Sun Aug 23 13:40:15 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Sun Aug 23 13:40:21 2009 Subject: ports/138100: [Update]databases/ruby-dbi:update to 0.4.2 Message-ID: <200908231340.n7NDeF6P012450@freefall.freebsd.org> Synopsis: [Update]databases/ruby-dbi:update to 0.4.2 Responsible-Changed-From-To: freebsd-ports-bugs->ruby Responsible-Changed-By: edwin Responsible-Changed-When: Sun Aug 23 13:40:14 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=138100 From edwin at FreeBSD.org Sun Aug 23 13:50:14 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Sun Aug 23 13:50:20 2009 Subject: ports/138101: [REPOCOPY]databases/ruby-dbi --> databases/rubygem-dbi Message-ID: <200908231350.n7NDoDZD022006@freefall.freebsd.org> Synopsis: [REPOCOPY]databases/ruby-dbi --> databases/rubygem-dbi Responsible-Changed-From-To: freebsd-ports-bugs->ruby Responsible-Changed-By: edwin Responsible-Changed-When: Sun Aug 23 13:50:13 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=138101 From stas at FreeBSD.org Sun Aug 23 21:38:32 2009 From: stas at FreeBSD.org (Stanislav Sedov) Date: Sun Aug 23 21:38:38 2009 Subject: ports/138100: [Update]databases/ruby-dbi:update to 0.4.2 Message-ID: <20090824014005.c921cfda.stas@FreeBSD.org> Hi Wen! Thanks for your patch! Personally, I'd prefer to stay back from switching to gem version as I don't see much benefit for this step. Why have you decided to switch to gem? Besides introducing new dependency on the old gem version, this will also possible break application that people use as this will require changes to this application sorce code to function properly with gems (require gems). Can you please, submit the patch against the current version without changing it to using gems? Thanks! -- Stanislav Sedov ST4096-RIPE From stas at FreeBSD.org Sun Aug 23 21:40:03 2009 From: stas at FreeBSD.org (Stanislav Sedov) Date: Sun Aug 23 21:40:08 2009 Subject: ports/138100: [Update]databases/ruby-dbi:update to 0.4.2 Message-ID: <200908232140.n7NLe2FT096601@freefall.freebsd.org> The following reply was made to PR ports/138100; it has been noted by GNATS. From: Stanislav Sedov To: Wen Heping Cc: ruby@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: ports/138100: [Update]databases/ruby-dbi:update to 0.4.2 Date: Mon, 24 Aug 2009 01:40:05 +0400 Hi Wen! Thanks for your patch! Personally, I'd prefer to stay back from switching to gem version as I don't see much benefit for this step. Why have you decided to switch to gem? Besides introducing new dependency on the old gem version, this will also possible break application that people use as this will require changes to this application sorce code to function properly with gems (require gems). Can you please, submit the patch against the current version without changing it to using gems? Thanks! -- Stanislav Sedov ST4096-RIPE From wenheping at gmail.com Sun Aug 23 23:20:03 2009 From: wenheping at gmail.com (wen heping) Date: Sun Aug 23 23:20:10 2009 Subject: ports/138100: [Update]databases/ruby-dbi:update to 0.4.2 Message-ID: <200908232320.n7NNK3ss094451@freefall.freebsd.org> The following reply was made to PR ports/138100; it has been noted by GNATS. From: wen heping To: bug-followup@FreeBSD.org, wenheping@gmail.com Cc: Subject: Re: ports/138100: [Update]databases/ruby-dbi:update to 0.4.2 Date: Mon, 24 Aug 2009 07:16:35 +0800 --0016e646b592e355740471d74a14 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, stas@ : With its previous Makefile and Makefile.common, ruby-dbi and other ruby-dbd_* is some dificult to update. And in my plan, I shall update all the ruby-dbd_* ports which require ruby-dbi to the newest version and use gem and modify the depends. I do not know which one is welcomed more for ruby port: gem or not gem. If not gem, I will try to update it without gem and then submit the new patch and close this PR. Cheers, wen --0016e646b592e355740471d74a14 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, stas@ :

=A0=A0 With its previous Makefile and Makefile.common, ruby-dbi and
other ruby-dbd_*=A0 is some dificult to update. And in my plan, I shall upd= ate
all the ruby-dbd_* ports which require ruby-dbi to the newest version
and use gem and modify the depends.

=A0=A0 I do not know which one is welcomed more for ruby port: gem
=A0or not gem. If not gem, I will try to update it without gem and then
submit the new patch and close this PR.

Cheers,
wen=20 --0016e646b592e355740471d74a14-- From bugmaster at FreeBSD.org Mon Aug 24 11:08:21 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 24 11:10:50 2009 Subject: Current problem reports assigned to ruby@FreeBSD.org Message-ID: <200908241108.n7OB8KTu050118@freefall.freebsd.org> 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/138101 ruby [REPOCOPY]databases/ruby-dbi --> databases/rubygem-dbi o ports/138100 ruby [Update]databases/ruby-dbi:update to 0.4.2 o ports/137958 ruby ports-mgmt/portupgrade fails with recursive dependency o ports/137708 ruby ports-mgmt/portupgrade: portupgrade -cRn is broken o ports/136722 ruby ports-mgmt/portupgrade - portversion issues Stale lock o ports/136056 ruby ports-mgmt/portupgrade 2009-06-25 breaks textproc/meld o ports/135691 ruby ports-mgmt/portupgrade Wrong example in man page of pk o ports/135466 ruby ports-mgmt/portupgrade leaves orphaned lock files sinc o ports/135201 ruby ports-mgmt/portupgrade: doesn't upgrade lang/tcc s ports/134714 ruby ports-mgmt/portupgrade deletes user data without quest o ports/134182 ruby ports-mgmt/portupgrade incorrectly handles manual reje o ports/131111 ruby ports-mgmt/portupgrade-devel: completely removes packa o ports/129930 ruby ports-mgmt/portupgrade - portinstall tries to install o ports/129891 ruby ports-mgmt/portupgrade fails to recognize variations o o ports/128881 ruby ports-mgmt/portupgrade backtrace o ports/127889 ruby ports-mgmt/portupgrade detects spurious failures and s o ports/127019 ruby ports-mgmt/portupgrade does not recognize fail conditi o ports/126140 ruby ports-mgmt/portupgrade runtime error o ports/125936 ruby ports-mgmt/portupgrade -R fails if BUILD_DEP's are not o ports/125823 ruby [PATCH] ports-mgmt/portupgrade does not use custom ECH o ports/112818 ruby ports-mgmt/portupgrade -a fails with database error o ports/100776 ruby ports-mgmt/portupgrade: Failure to update devel/mico b 22 problems total. From barbara.xxx1975 at libero.it Wed Aug 26 13:54:47 2009 From: barbara.xxx1975 at libero.it (barbara) Date: Wed Aug 26 13:54:53 2009 Subject: portupgrade deleting pacakges Message-ID: I was upgrading some of my ports after the upgrade of gnutls using portupgrade. I wasn't doing it using what's recommended in /usr/ports/UPDATING, but with a script I've done which computes dependencies and track upgraded packages and then run portupgrade -fp on one port at a time. That's because the upgrade of gdm always caused me troubles on the currently running session and stopping it wasn't a option at that moment. Then I noticed some problem with pkgdb and then I realized that portupgrade refused to upgrade firefox because of portaudit entry, but it nonetheless removed the installed version leaving inconsistencies. IMHO this should never happen. You can try it by yourself fetching the last portaudit db with portaudit -aF and then running portupgrade -f www/firefox. This is what's happening: # portupgrade -f www/firefox ---> Reinstalling 'firefox-2.0.0.20_9,1' (www/firefox) ---> Building '/usr/ports/www/firefox' with make flags: WITH_OPTIMIZED_CFLAGS=1 ===> Cleaning for firefox-2.0.0.20_9,1 ===> firefox-2.0.0.20_9,1 has known vulnerabilities: => mozilla -- multiple vulnerabilities. Reference: => Please update your ports tree and try again. *** Error code 1 Stop in /usr/ports/www/firefox. *** Error code 1 Stop in /usr/ports/www/firefox. ---> Backing up the old version ---> Uninstalling the old version ---> Deinstalling 'firefox-2.0.0.20_9,1' pkg_delete: package 'firefox-2.0.0.20_9,1' is required by these other packages and may not be deinstalled (but I'll delete it anyway): alacarte-0.12.1_1 compiz-0.8.2_1 compiz-fusion-0.8.2 compiz-plugins-extra-0.8.2_1 compiz-plugins-main-0.8.2_1 emerald-0.8.2_1 eog-2.26.3_1 epiphany-2.26.3_3 file-roller-2.26.3_1,1 gdm-2.26.1_6 gegl-0.0.22_6 gimp-2.6.6,2 gimp-app-2.6.6_3,1 gnome-applets-2.26.3_1 gnome-control-center-2.26.0_2 gnome-netstatus-2.26.0_1 gnome-panel-2.26.3_1 gnome-system-monitor-2.26.2_1 gnome-system-tools-2.22.2_1 gnome-utils-2.26.0_2,1 gnome2-lite-2.26.3 librsvg2-2.26.0_1 meld-1.3.0_1 mplayerplug-in-3.55_3 nautilus-2.26.3_1 nautilus-cd-burner-2.24.0_2 netspeed_applet-0.15.2_1 py26-gnome-desktop-2.26.0_1 swt-devel-3.5.m6_1,1 totem-2.26.3_1 vuze-4.2.0.2_1 yelp-2.26.0_1 [Updating the pkgdb in /var/db/pkg ... - 752 packages found (-1 +0) (...) done] ---> Installing the new version via the port with make flags: WITH_OPTIMIZED_CFLAGS=1 ===> firefox-2.0.0.20_9,1 has known vulnerabilities: => mozilla -- multiple vulnerabilities. Reference: => Please update your ports tree and try again. *** Error code 1 Stop in /usr/ports/www/firefox. *** Error code 1 Stop in /usr/ports/www/firefox. *** Error code 1 Stop in /usr/ports/www/firefox. ===> Cleaning for firefox-2.0.0.20_9,1 ---> Cleaning out obsolete shared libraries # pkg_info -Ix firefox firefox-3.5.2,1 Web browser based on the browser portion of Mozilla As you can see,firefox-2.0.0.20_9,1 is now gone. Thanks Barbara From stas at FreeBSD.org Thu Aug 27 09:00:15 2009 From: stas at FreeBSD.org (Stanislav Sedov) Date: Thu Aug 27 09:00:27 2009 Subject: ports/138100: [Update]databases/ruby-dbi:update to 0.4.2 Message-ID: <200908270900.n7R90ErY092466@freefall.freebsd.org> The following reply was made to PR ports/138100; it has been noted by GNATS. From: Stanislav Sedov To: wen heping Cc: bug-followup@FreeBSD.org Subject: Re: ports/138100: [Update]databases/ruby-dbi:update to 0.4.2 Date: Thu, 27 Aug 2009 12:51:00 +0400 On Mon, 24 Aug 2009 07:14:02 +0800 wen heping mentioned: > Hi, stas@ : > > With its previous Makefile and Makefile.common, ruby-dbi and > other ruby-dbd_* is some dificult to update. And in my plan, I shall update > all the ruby-dbd_* ports which require ruby-dbi to the newest version > and use gem and modify the depends. > > I do not know which one is welcomed more for ruby port: gem > or not gem. If not gem, I will try to update it without gem and then > submit the new patch and close this PR. > > Cheers, > wen > > On Mon, Aug 24, 2009 at 5:40 AM, Stanislav Sedov wrote: > > > Hi Wen! > > > > Thanks for your patch! Personally, I'd prefer to stay back > > from switching to gem version as I don't see much benefit > > for this step. Why have you decided to switch to gem? > > Besides introducing new dependency on the old gem version, > > this will also possible break application that people use > > as this will require changes to this application sorce code > > to function properly with gems (require gems). > > > > Can you please, submit the patch against the current version > > without changing it to using gems? > > Yeah, I think that staying away from gems for this module is the preferrable way to go. You may submit the new patch to update ruby-dbd* ports as followup to this PR. Thanks! -- Stanislav Sedov ST4096-RIPE From stas at FreeBSD.org Thu Aug 27 11:42:15 2009 From: stas at FreeBSD.org (stas@FreeBSD.org) Date: Thu Aug 27 11:42:37 2009 Subject: ports/138100: [Update]databases/ruby-dbi:update to 0.4.2 Message-ID: <200908271142.n7RBgEHn067476@freefall.freebsd.org> Synopsis: [Update]databases/ruby-dbi:update to 0.4.2 State-Changed-From-To: open->closed State-Changed-By: stas State-Changed-When: Thu Aug 27 11:42:14 UTC 2009 State-Changed-Why: Close per submitter request. http://www.freebsd.org/cgi/query-pr.cgi?pr=138100 From stas at FreeBSD.org Thu Aug 27 11:42:30 2009 From: stas at FreeBSD.org (stas@FreeBSD.org) Date: Thu Aug 27 11:42:37 2009 Subject: ports/138101: [REPOCOPY]databases/ruby-dbi --> databases/rubygem-dbi Message-ID: <200908271142.n7RBgUT2067582@freefall.freebsd.org> Synopsis: [REPOCOPY]databases/ruby-dbi --> databases/rubygem-dbi State-Changed-From-To: open->closed State-Changed-By: stas State-Changed-When: Thu Aug 27 11:42:29 UTC 2009 State-Changed-Why: Close per submitter request. http://www.freebsd.org/cgi/query-pr.cgi?pr=138101 From edwin at FreeBSD.org Mon Aug 31 02:37:06 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Mon Aug 31 02:37:12 2009 Subject: ports/138356: ports-mgmt/portupgrade: pkgdb -F + ALT_PKGDEP => broken logic Message-ID: <200908310237.n7V2b5Ia013626@freefall.freebsd.org> Synopsis: ports-mgmt/portupgrade: pkgdb -F + ALT_PKGDEP => broken logic Responsible-Changed-From-To: freebsd-ports-bugs->ruby Responsible-Changed-By: edwin Responsible-Changed-When: Mon Aug 31 02:37:05 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=138356 From bugmaster at FreeBSD.org Mon Aug 31 11:08:48 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 31 11:11:02 2009 Subject: Current problem reports assigned to ruby@FreeBSD.org Message-ID: <200908311108.n7VB8kor072097@freefall.freebsd.org> 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/138356 ruby ports-mgmt/portupgrade: pkgdb -F + ALT_PKGDEP => broke o ports/137958 ruby ports-mgmt/portupgrade fails with recursive dependency o ports/137708 ruby ports-mgmt/portupgrade: portupgrade -cRn is broken o ports/136722 ruby ports-mgmt/portupgrade - portversion issues Stale lock o ports/136056 ruby ports-mgmt/portupgrade 2009-06-25 breaks textproc/meld o ports/135691 ruby ports-mgmt/portupgrade Wrong example in man page of pk o ports/135466 ruby ports-mgmt/portupgrade leaves orphaned lock files sinc o ports/135201 ruby ports-mgmt/portupgrade: doesn't upgrade lang/tcc s ports/134714 ruby ports-mgmt/portupgrade deletes user data without quest o ports/134182 ruby ports-mgmt/portupgrade incorrectly handles manual reje o ports/131111 ruby ports-mgmt/portupgrade-devel: completely removes packa o ports/129930 ruby ports-mgmt/portupgrade - portinstall tries to install o ports/129891 ruby ports-mgmt/portupgrade fails to recognize variations o o ports/128881 ruby ports-mgmt/portupgrade backtrace o ports/127889 ruby ports-mgmt/portupgrade detects spurious failures and s o ports/127019 ruby ports-mgmt/portupgrade does not recognize fail conditi o ports/126140 ruby ports-mgmt/portupgrade runtime error o ports/125936 ruby ports-mgmt/portupgrade -R fails if BUILD_DEP's are not o ports/125823 ruby [PATCH] ports-mgmt/portupgrade does not use custom ECH o ports/112818 ruby ports-mgmt/portupgrade -a fails with database error o ports/100776 ruby ports-mgmt/portupgrade: Failure to update devel/mico b 21 problems total. From bms at incunabulum.net Mon Aug 31 19:01:05 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon Aug 31 19:01:28 2009 Subject: portupgrade not passing BATCH? [Fwd: Re: ports/mail/nullmailer: nudge re BATCH] Message-ID: <4A9C19E2.2090200@incunabulum.net> Hi guys, I noticed nullmailer's deinstall script was prompting for input, during a portupgrade -a. Greg looked at the issue and found that portupgrade wasn't even passing BATCH in the environment, during deinstallation. Are you already aware of the issue? Do any patches exist? thanks, BMS -------------- next part -------------- An embedded message was scrubbed... From: Greg Larkin Subject: Re: ports/mail/nullmailer: nudge re BATCH Date: Mon, 31 Aug 2009 14:38:03 -0400 Size: 3701 Url: http://lists.freebsd.org/pipermail/freebsd-ruby/attachments/20090831/81e46809/nudgereBATCH.eml