Re: r353029 broke net-mgmt/zabbix2*-server options
On 5/14/2014 12:54 AM, John Marino wrote: On 5/14/2014 09:42, Pavel Timofeev wrote: Hi! After this commit to regular ports tree both zabbix (2.0 and 2.2) ports was messed. For example: Options available for the single DB: you have to select exactly one of them MYSQL=on: MySQL database support PGSQL=off: PostgreSQL database support SQLITE=off: SQLite database support ORACLE=off: Oracle database support ODBC=off: Support for database checks via ODBC === Use 'make config' to modify these settings ODBC shouldn't be in DB section. See in 2014Q2 - that's how it has to look. Please, fix it I am somebody completely unfamiliar with this port. So I am curious why ODBC shouldn't be in DB section. ODBC is a database driver, so why shouldn't it be in the database section? You state it needs to be a certain way, but the justification is that it was that way before rather than stating the real reason for those of us that aren't familiar with this particular port. ODBC isn't a back end DB option for Zabbix, it's an option for Zabbix to test/monitor ODBC connections. Totally different from the n database support options. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
rubygem-nokogiri error: \xE2 from ASCII-8BIT to UTF-8
Hello, I just attempted to upgrade Ruby Redmine and one of the gems, nokogiri, (and a few others) die with the same ASCII-8BIT to UTF-8 error durring the doc install phase which prevents the port from completing the install. I've searched and search and cannot find anything that relates to this specifically, anyone have any ideas? Let me know if I can provide more info, here is the error lead up: === Building for rubygem-nokogiri-1.5.0 Successfully built RubyGem Name: nokogiri Version: 1.5.0 File: nokogiri-1.5.0.gem === Installing for rubygem-nokogiri-1.5.0 === rubygem-nokogiri-1.5.0 depends on file: /usr/local/bin/gem19 - found === rubygem-nokogiri-1.5.0 depends on file: /usr/local/bin/ruby19 - found === rubygem-nokogiri-1.5.0 depends on file: /usr/local/lib/ruby/1.9/amd64-freebsd9/iconv.so - found === Generating temporary packing list === Checking if textproc/rubygem-nokogiri already installed Building native extensions. This could take a while... Successfully installed nokogiri-1.5.0 1 gem installed Installing RDoc documentation for nokogiri-1.5.0... ERROR: While generating documentation for nokogiri-1.5.0 ... MESSAGE: \xE2 from ASCII-8BIT to UTF-8 ... RDOC args: --op /usr/local/lib/ruby/gems/1.9/doc/nokogiri-1.5.0/rdoc --main README.rdoc lib Manifest.txt README.ja.rdoc CHANGELOG.rdoc CHANGELOG.ja.rdoc README.rdoc ext/nokogiri/xml_sax_push_parser.c ext/nokogiri/xml_relax_ng.c ext/nokogiri/html_sax_parser_context.c ext/nokogiri/html_entity_lookup.c ext/nokogiri/xml_text.c ext/nokogiri/nokogiri.c ext/nokogiri/xml_element_decl.c ext/nokogiri/xml_encoding_handler.c ext/nokogiri/html_document.c ext/nokogiri/xslt_stylesheet.c ext/nokogiri/xml_attribute_decl.c ext/nokogiri/xml_io.c ext/nokogiri/xml_document_fragment.c ext/nokogiri/xml_namespace.c ext/nokogiri/xml_libxml2_hacks.c ext/nokogiri/xml_sax_parser_context.c ext/nokogiri/xml_comment.c ext/nokogiri/xml_sax_parser.c ext/nokogiri/html_element_description.c ext/nokogiri/xml_xpath_context.c ext/nokogiri/xml_syntax_error.c ext/nokogiri/xml_document.c ext/nokogiri/xml_entity_decl.c ext/nokogiri/xml_node.c ext/nokogiri/xml_node_set.c ext/nokogiri/xml_reader.c ext/nokogiri/xml_processing_instruction.c ext/nokogiri/xml_element_content.c ext/nokogiri/xml_dtd.c ext/nokogiri/xml_attr.c ext/nokogiri/xml_schema.c ext/nokogiri/xml_cdata.c ext/nokogiri/xml_entity_reference.c --title nokogiri-1.5.0 Documentation --quiet *** [do-install] Error code 1 Stop in /usr/ports/textproc/rubygem-nokogiri. *** [run-depends] Error code 1 Stop in /usr/ports/devel/rubygem-capybara. *** [run-depends] Error code 1 Stop in /usr/ports/www/redmine. *** [install] Error code 1 Stop in /usr/ports/www/redmine. -- Adam Strohl http://www.ateamsystems.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: rubygem-nokogiri error: \xE2 from ASCII-8BIT to UTF-8
On 6/14/2013 1:10, Steve Wills wrote: Hello, I just attempted to upgrade Ruby Redmine and one of the gems, nokogiri, (and a few others) die with the same ASCII-8BIT to UTF-8 error durring the doc install phase which prevents the port from completing the install. I've searched and search and cannot find anything that relates to this specifically, anyone have any ideas? I've seen errors like this, although not with this specific port. I haven't come up with a good solution yet, but often setting LC_LANG or LANG or LC_ALL to en_us.utf-8 (or whatever is appropriate for you) helps. FWIW, bsd.ruby.mk sets LC_CTYPE=UTF-8, but maybe it needs to set more. The problem is it's generating docs and needs this, but we don't set a LANG by default. BINGO. Thank you both Michael Gmelin (who replied privately) and Steve. My defaults were C or blank when I ran locale, and per both of your suggestions setting this let nokogiri build: export LANG=en_US.UTF-8; export LC_ALL=en_US.UTF-8; Awesomeness: Building native extensions. This could take a while... Successfully installed nokogiri-1.5.0 1 gem installed Installing RDoc documentation for nokogiri-1.5.0... === Registering installation for rubygem-nokogiri-1.5.0 I also want to note (in case anyone else searches for this) that rubygem-net-ldap port also had the same issue for me and this fixed that port as well. Thanks again! -- Adam Strohl http://www.ateamsystems.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Install of devel/pear hangs
On 6/12/2012 19:18, Colin Baker wrote: Hello, Been having some trouble installing devel/pear on a server after migrating PHP packages from php5-* to php53-*. Regardless of whether I use portmaster or 'make install', it hangs at the same spot: # make install === Installing for pear-1.9.4_1 === pear-1.9.4_1 depends on file: /usr/local/include/php/main/php.h - found === pear-1.9.4_1 depends on file: /usr/local/lib/php/20090626/xml.so - found === Generating temporary packing list === Checking if devel/pear already installed where it will happily sit for days if I don't intervene. Is there any way to see what it's trying to do at this stage? Or is this something anybody else has run into? Try using truss (ie; truss make install) -- Adam Strohl http://www.ateamsystems.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Retro-actively adjust port's deinstall operations?
Hello, I've just submitted a PR to update the CouchDB port from 1.1.0 to 1.2.0: http://www.freebsd.org/cgi/query-pr.cgi?pr=168923 Background: CouchDB's local.ini file stores all overridden options and default.ini the defaults, similar to /etc/rc.conf /etc/defaults/rc.conf. While updating the port I discovered that the existing port lists local.ini directly in pkg-plist instead of installing a local.ini.sample file and doing proper comparisons/tests for changes. So it blindly removes this file on deinstall. If my diff in the above PR is accepted when people uninstall the existing 1.1.0 port it will remove their config file. The new port will see that there is no local.ini and copy in the sample for them but this is really awful for obvious reasons. Is there a way to reach people with a warning about this _before_ they uninstall/reinstall so they can back up the file before upgrading? Or is /usr/ports/UPDATING it? (and do I need to do anything special to have this listed there?) P.S. Any other feedback on the PR/diff is welcome. -- Adam Strohl http://www.ateamsystems.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Retro-actively adjust port's deinstall operations?
On 6/11/2012 4:30, Bryan Drewery wrote: On 6/10/2012 4:27 PM, Adam Strohl wrote: Where/when would this trigger? This could block the upgrade as soon as they try to build it if they already have the ini and do not have a sample file. The issue is that most things (ie; people or portupgrade) do a deinstall first, then a reinstall. By the time the Makefile gets called for reinstall its too late and in my testing everything is ignored for deinstall because it uses the package's archived actions. Or would this somehow hook on make deinstall too? -- Adam Strohl http://www.ateamsystems.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Retro-actively adjust port's deinstall operations?
On 6/11/2012 4:36, Bryan Drewery wrote: portupgrade builds the port first, then deinstalls and installs. So I think crees' suggestion will work. Ah yes, that's right! It only deinstalls after a successful build! Excellent. Not sure about portmaster, but I imagine it would do the same, as it could take *hours* to build and you would be left without the port in the meantime. Good call. -- Adam Strohl http://www.ateamsystems.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On 6/4/2012 18:07, Erich wrote: yes, you installed bash and screen first. Can you try it without? Doesn't tinderbox do this every night? I really try to install X as the first thing after I finished installation. I wonder why you need bash from the ports at that stage? Because that is what I use as my shell, and I use GNU Screen so if my connection terminates I can reattach. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On 6/4/2012 18:36, Adam Strohl wrote: On 6/4/2012 18:07, Erich wrote: yes, you installed bash and screen first. Can you try it without? From a 100% clean install: - portsnap fetch extract update - compiled x-org + VMware driver No issues, works fine.
Re: Why Are You NOT Using FreeBSD?
On 6/4/2012 21:59, Erich wrote: Hi, On 04 June 2012 21:10:31 Adam Strohl wrote: On 6/4/2012 18:36, Adam Strohl wrote: On 6/4/2012 18:07, Erich wrote: yes, you installed bash and screen first. Can you try it without? From a 100% clean install: - portsnap fetch extract update - compiled x-org + VMware driver No issues, works fine. I was not that lucky. For 8.0, it was with the NVidea driver, in the first week of my, it was with 9.0 and the Intel driver. Let me arrive back home to have another try. Sure, and if you do have issues post what the specific error and port is where it happened. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On 6/3/2012 17:24, Etienne Robillard wrote: Technical debt perhaps counts when upstream vendor new versions breaks things unexpectingly ? For this to happen though that means one of two things: 1. The port maintainer has updated the port to grab this new version, and tested it (and it worked) then committed the change. And now it doesn't work for some people/setups. They need to know and fix it. 2. Then the upstream vendor, behind everyone's back, changes the code inside the distro file(s). This then breaks the MD5/SHA256 check. The port maintainer needs to know so they can fix it. For #1 I see it as delaying the fix (I won't report my problem, I'll just use an old version). For #2 Having an old version of the ports tree wouldn't solve this issue since it was prompted by a change by the vendor to begin with. I feel like this thread is grossly overstating how often ports are broken which is super rare in my experience. Proposing a version'd ports tree seems like a bad-practice-encouraging-solution to a problem that doesn't really exist [in my experience]. And it is bad practice. There is a constant stream of security issues being discovered and ignoring them is totally inappropriate. Yes there are rare situations where you have to make a trade off on security to fit some highly specialized need but I wouldn't want that to be encouraged and it certainly isn't the solution to broken ports. P.S. Not subbed to -ports, CC me on replies. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On 6/3/2012 19:19, Erich Dollansky wrote: do a simple thing. Install a naked 8.3, 9.0 or 10.0 on a fresh hard disk. Get then the ports tree and start compiling X. I did not get a running system since at least 2007 when I did this. There was always at least one manual intervention needed. I did this the last time in the first week of May. Yes, I know how to fix this. Yes, I reported things like this at the beginning. After getting always the answer that it is working on my machine, I stopped reporting it. Just built a VM and installed 9.0-R from the ISO. Installed gnu-screen and bash (from ports). Built and installed xorg-server from ports without issue: === Compressing manual pages for xorg-server-1.7.7_5,1 === Registering installation for xorg-server-1.7.7_5,1 === SECURITY REPORT: This port has installed the following binaries which execute with increased privileges. /usr/local/bin/Xorg This port has installed the following files which may act as network servers and may therefore pose a remote security risk to the system. /usr/local/bin/Xorg If there are vulnerabilities in these programs there may be a security risk to the system. FreeBSD makes no guarantee about the security of ports included in the Ports Collection. Please type 'make deinstall' to deinstall the port if this is a concern. For more information, and contact details about the security status of this software, see the following webpage: http://www.freedesktop.org/Software/xorg - root - xwintest.dsn - /usr/ports/x11-servers/xorg-server - 23:20:59 ICT ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
