FreeBSD ports that you maintain which are currently marked broken
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/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=databasesportname=rubygem-delayed_job_data_mapper portname: databases/rubygem-dm-core broken because: unable to resolve dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=rubygem-dm-core portname: devel/rubygem-celluloid broken because: does not build with ruby 1.8 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=rubygem-celluloid portname: japanese/rubygem-myrurema broken because: unable to resolve dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japaneseportname=rubygem-myrurema portname: x11-toolkits/ruby-gtk broken because: fails to build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=ruby-gtk 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to freebsd-ruby-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
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: archivers/ruby-bz2 description:Ruby extension to use libbz2 maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=ruby-bz2 portname: audio/ruby-vorbisfile description:A Ruby extension wrapping libvorbisfile maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ruby-vorbisfile portname: audio/ruby-xmms description:XMMS bindings for Ruby maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ruby-xmms portname: devel/ruby-fam description:FAM bindings for Ruby maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ruby-fam portname: devel/ruby-io-reactor description:Ruby module that implements an asynchronous multiplexed IO Reactor maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ruby-io-reactor portname: devel/ruby-jttui description:Textmode User Interface by Jakub Travnik maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ruby-jttui portname: devel/ruby-racc description:An LALR(1) parser generator for Ruby maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ruby-racc portname: devel/ruby-slang description:S-Lang extension module for Ruby maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ruby-slang portname: devel/rubygem-linecache description:Caches(Ruby source) Files as Might Be Used in a Debugger maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=rubygem-linecache portname: devel/rubygem-parsetree description:Ruby parse tree tools maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=rubygem-parsetree portname: devel/rubygem-rparsec description:Recursive descent parser combinator framework for Ruby maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=rubygem-rparsec portname: devel/rubygem-sdl description:Ruby extension library to use SDL library maintainer: r...@freebsd.org deprecated because: Does not work with Ruby 1.9 expiration date:2013-05-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=rubygem-sdl portname: games/ruby-exmars description:Ruby interface to the exMARS Memory Array Redcode
FreeBSD ports you maintain which are out of date
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/r...@freebsd.org.html Port| Current version | New version +-+ devel/rubygem-tins | 0.5.3 | 0.8.0 +-+ 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 portsc...@portscout.freebsd.org Thanks. ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to freebsd-ruby-unsubscr...@freebsd.org
