Re: Updating ports that use FLAVOR with portmaster
--On December 8, 2017 at 3:16:19 PM -0700 Warren Block <wbl...@wonkity.com> wrote: On Fri, 8 Dec 2017, Paul Schmehl wrote: As my second post shows, I can't make FLAVOR=py27 install either. So, I guess I'm dead in the water. Until I can install py-setuptools, nothing else will work, including devel/llvm40. All I've had to do was py-setuptools. The default flavor is py27, which covered most of my systems. Then I had to make clean && make FLAVOR=py34 install clean (or 36 or whatever version of python 3 was the current fad for whatever needed it on that system) Thanks, Warren. That's helpful. Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating ports that use FLAVOR with portmaster
--On December 8, 2017 at 1:38:24 PM -0800 Chris H <bsd-li...@bsdforge.com> wrote: It doesn't appear that pkg recognized FLAVOR either. I believe that pkg(8) version 1.10.3 will give it to you. What revision of ports are you currently using? pkg is 1.10.3. I moved the patch that was causing the failure, and the port built without FLAVOR. Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating ports that use FLAVOR with portmaster
--On December 8, 2017 at 12:49:44 PM -0800 Freddie Cash <fjwc...@gmail.com> wrote: On Fri, Dec 8, 2017 at 12:31 PM, Paul Schmehl <pschmehl_li...@tx.rr.com> wrote: How do you do this? I have a number of py ports that need to be updated, but portmaster chokes on them. I don't see anything about FLAVOR in the man page. Do we actually have to update all these ports manually, one at a time? You wait patiently while portmaster is updated to support FLAVORs. The work is in progress, although there is no ETA on when it will be ready for testing. If you can't wait, then you can look into poudriere or synth. They both support FLAVOR already. Or, do manual "pkg remove; make install" for each one. As my second post shows, I can't make FLAVOR=py27 install either. So, I guess I'm dead in the water. Until I can install py-setuptools, nothing else will work, including devel/llvm40. It doesn't appear that pkg recognized FLAVOR either. Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
py-setuptools fails to build with FLAVOR
# cd ../py-setuptools [root@colo11 /usr/ports/devel/py-setuptools]# make distclean ===> Cleaning for py27-setuptools-36.5.0 ===> Cleaning for py35-setuptools-36.5.0 ===> Cleaning for py36-setuptools-36.5.0 ===> Cleaning for py34-setuptools-36.5.0 ===> Deleting distfiles for py27-setuptools-36.5.0 [root@colo11 /usr/ports/devel/py-setuptools]# make FLAVOR=py27 install ===> License PSFL accepted by the user ===> py27-setuptools-36.5.0 depends on file: /usr/local/sbin/pkg - found => setuptools-36.5.0.zip doesn't seem to exist in /usr/ports/distfiles/python. => Attempting to fetch https://files.pythonhosted.org/packages/source/s/setuptools/setuptools-36.5.0.zip setuptools-36.5.0.zip 100% of 704 kB 4447 kBps 00m00s ===> Fetching all distfiles required by py27-setuptools-36.5.0 for building ===> Extracting for py27-setuptools-36.5.0 => SHA256 Checksum OK for python/setuptools-36.5.0.zip. ===> Patching for py27-setuptools-36.5.0 ===> Applying FreeBSD patches for py27-setuptools-36.5.0 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to setuptools/command/install_egg_info.py.rej => FreeBSD patch patch-setuptools__command__install_egg_info.py failed to apply cleanly. *** Error code 1 Stop. make: stopped in /usr/ports/devel/py-setuptools Are we in a catch22? Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Updating ports that use FLAVOR with portmaster
How do you do this? I have a number of py ports that need to be updated, but portmaster chokes on them. I don't see anything about FLAVOR in the man page. Do we actually have to update all these ports manually, one at a time? Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Package database problems
--On November 17, 2017 at 9:39:15 AM +0100 Kurt Jaeger <li...@opsec.eu> wrote: Hi! >> I didn't setup this server to begin with. I recall, a >> while back, instructions for switching to pkgng. Is that what wasn't >> done? > Yes, something like that. Should I run pkg2ng now? Would that help? I'm not sure it would help. I managed to fix the problem by a combination of installing major languages (perl, php, ruby and python) and their dependencies, running pkg autoremove -n and deleting unwanted and unneeded ports, and then running portmaster to complete the updates of out of date ports. I do have one concern, however. (There may be others I'm unaware of.) When I ran pkg -r devel/oniguruma, it showed no dependencies. In fact, it was listed by autoremove. But I know php ports depend on it. Is there a way to update dependencies that are not listed? If not, I'll probably uninstall oniguruma and then reinstall php, which *should* force the reinstall of oniguruma and update the dependency tree. It sure would be nice if pkg could do this for me by simply relinking the dependencies. Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Package database problems
--On November 16, 2017 at 9:34:05 PM +0100 Kurt Jaeger <li...@opsec.eu> wrote: You probably have to clean it up. I would do this: - use the list of old-style packages in /var/db/pkg, together with the output of pkg info, to generate a list of packages that you need after clean up. My list looks like this, approx. 2000 entries: - [...] devel/automake devel/automake-wrapper devel/automoc4 devel/binutils devel/bison [...] - - Then build all the packages from your list via poudriere, and generate a repo of all those up2date packages. - Then (this is dangerous, if done via remote, keep a few ssh sessions running in parallel, if one fails): mkdir /usr/local/OLD cd /usr/local mv * OLD/ - Now no packages are installed - re-add all the packages, restore the config from OLD/... Ugh. I didn't setup this server to begin with. I recall, a while back, instructions for switching to pkgng. Is that what wasn't done? Yes, something like that. Should I run pkg2ng now? Would that help? Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Package database problems
--On November 16, 2017 at 8:49:24 PM +0100 Kurt Jaeger <li...@opsec.eu> wrote: Hi! > ???There's nothing to iterate over. There's nothing in /var/db/pkg > anymore except the SQLite databases. Then what is all this? (I'm only showing part of it. ls /var/db/pkg/ FreeBSD.metalibXfixes-5.0.3 p5-Net-Domain-TLD-1.74 py27-qt4-dbussupport-4.12_1 ImageMagick-6.9.2.10,1 libXfont-1.5.2,2 p5-Package-Stash-0.37_1 Looks like you have some old-style pkg_ leftovers. So, what should I do? I didn't setup this server to begin with. I recall, a while back, instructions for switching to pkgng. Is that what wasn't done? Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Package database problems
--On November 16, 2017 at 11:23:34 AM -0800 Freddie Cash <fjwc...@gmail.com> wrote: There's nothing to iterate over. There's nothing in /var/db/pkg anymore except the SQLite databases. Then what is all this? (I'm only showing part of it. ls /var/db/pkg/ FreeBSD.metalibXfixes-5.0.3p5-Net-Domain-TLD-1.74 py27-qt4-dbussupport-4.12_1 ImageMagick-6.9.2.10,1 libXfont-1.5.2,2 p5-Package-Stash-0.37_1 py27-qt4-gui-4.11.4,1 ORBit2-2.14.19_2 libXft-2.3.2_1p5-Package-Stash-XS-0.28_2 py27-setuptools-36.5.0 a2ps-4.13b_8libXi-1.7.9,1p5-Params-Util-1.07_2 py27-setuptools27-19.2 apache24-2.4.18libXpm-3.5.12p5-Params-Validate-1.29 py27-sip-4.19.2,1 apache24-2.4.29libXrandr-1.5.1p5-Params-ValidationCompiler-0.24 py27-six-1.11.0 apr-1.6.3.1.6.1libXrender-0.9.10 p5-Role-Tiny-2.06 py27-six-1.9.0 argp-standalone-1.3_3 libXt-1.1.5,1p5-Specio-0.42 py27-snowballstemmer-1.2.0_1 atk-2.24.0libXv-1.0.11,1p5-Sub-Exporter-0.987_1 py27-sphinx-1.3.1_2 autoconf-2.69_1libXvMC-1.0.10p5-Sub-Exporter-Progressive-0.001013 py27-sphinx-1.4.8_2,1 autoconf-wrapper-20131203 libXxf86vm-1.1.4_1 p5-Sub-Identify-0.14 py27-sphinx_rtd_theme-0.1.8 automake-1.15.1libarchive-3.3.2,1 p5-Sub-Install-0.928_1 py27-sphinx_rtd_theme-0.2.4 automake-wrapper-20131203 libatomic_ops-7.6.0_1 p5-Sub-Quote-2.004000 py27-sqlite3-2.7.11_7 avahi-app-0.6.31_5 libcheck-0.10.0p5-TimeDate-2.30_2,1 py27-tkinter-2.7.11_6 bacula-client-7.2.0_3 libclc-0.3.0.20170927 p5-Try-Tiny-0.28 py27-tkinter-2.7.14_6 bareos-client-static-16.2.6 libcroco-0.6.11p5-Variable-Magic-0.62 pydbus-common-1.2.0_1 bash-4.4.12_3 libdaemon-0.14_1 p5-XML-Parser-2.44 python27-2.7.14_1 bdftopcf-1.0.5libdevq-0.0.4p5-namespace-autoclean-0.28 python35-3.5.4 bigreqsproto-1.1.2 libdrm-2.4.88,1p5-namespace-clean-0.27 qpdf-6.0.0_1 binutils-2.28,1libedit-3.1.20170329_2,1 pango-1.36.8_2 qscintilla2-2.9.1,1 bison-3.0.4,1 libev-4.22,1 pango-1.40.6qt4-assistant-4.8.7 boehm-gc-7.6.0 libevent-2.1.8 pciids-20171021 qt4-clucene-4.8.7 boost-docs-1.65.1 libevent2-2.0.22_1 pcre-8.40_1 qt4-clucene-4.8.7_1 boost-jam-1.65.1libffi-3.2.1_1 pecl-APCu-5.1.8_1 qt4-corelib-4.8.7_9 The only way to "rebuild" local.sqlite is to reinstall everything. Well that sucks, because I CAN'T reinstall everything, since the supposed conflicts are preventing it. Are you saying to delete the database and then reinstall every port to build a new db? Good lord. I'm already into my second day of trying to fix this problem, and I've got tons of problems. Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Package database problems
--On November 16, 2017 at 11:23:34 AM -0800 Freddie Cash <fjwc...@gmail.com> wrote: The only way to "rebuild" local.sqlite is to reinstall everything. Is there a way to force a port install regardless of conflicts? Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Package database problems
That's the problem. The package that installed that file is not installed. Nor is the file in the location pkg complains about. Yet, it still complains of a conflict and refuses to install the package I'm trying to install. For example, I tried to upgrade devel/oniguruma. It complained about a conflict with oniguruma5, specifically /usr/local/bin/onig-config. That file does not exist, nor is onigurum5 installed. I wish there was a pkg command like rebuild-db that would iterate through /var/db/pkg and create a valid local.sqlite file that registers the packages currently existing on the server. --On November 16, 2017 at 12:39:47 PM -0600 Adam Vande More <amvandem...@gmail.com> wrote: On Thu, Nov 16, 2017 at 12:22 PM, Paul Schmehl <pschmehl_li...@tx.rr.com> wrote: I'm having problems with my package database. It complains about a conflict with a file that doesn't exist. Is there a way to create a new local.sqlite file using the pkg command? 'pkg which /path/to/file' IIRC should reveal the registered package? Perhaps best to address it that way. Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Package database problems
I'm having problems with my package database. It complains about a conflict with a file that doesn't exist. Is there a way to create a new local.sqlite file using the pkg command? Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Problem with perl5.24
--On September 26, 2017 at 10:05:32 PM +0200 Kurt Jaeger <li...@opsec.eu> wrote: Hi! I'm running into problems trying to update perl with portmaster. I get the following error message: make: don't know how to make post-clean-noflavor. Stop I get the same message if I try to uninstall. I tried pkg install, but that didn't fix the problem. I haven't found anything on the web about this error and didn't find anything in /usr/ports/UDPATING I'm dead in the water until I resolve this. See https://lists.freebsd.org/pipermail/freebsd-ports/2017-September/110296.h tml and https://lists.freebsd.org/pipermail/freebsd-ports/2017-September/110300.h tml It's a sideeffect of the new FLAVOURS feature. Will probably be fixed soon. Thanks. I finally resolved it by doing make reinstall in the port directory. Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Problem with perl5.24
I'm running into problems trying to update perl with portmaster. I get the following error message: make: don't know how to make post-clean-noflavor. Stop I get the same message if I try to uninstall. I tried pkg install, but that didn't fix the problem. I haven't found anything on the web about this error and didn't find anything in /usr/ports/UDPATING I'm dead in the water until I resolve this. Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Installing ports in other places
I need to install mediawiki, but I want to install it in a different location - in my home directory in a directory named wiki. I've read about DESTDIR, but I'm not certain that will work as I intend. If I run make install DESTDIR=/homedir/wiki, will the port install as /homedir/wiki/mediawiki? Or will it install in /homedir/wiki? Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
--On June 4, 2017 at 11:20:20 PM +0300 abi <a...@abinet.ru> wrote: On 04.06.2017 21:42, scratch65...@att.net wrote: As OP problem was solved, it's time to hijack the thread a little :) I'm considering to migrate as well, what is recommended path for upgrade ? Uninstall all php56 ports or replace them (I believe, -o key in portmaster). Here's what I did. portmaster -o lang/php71 lang/php56 That upgrades php. Then I removed all the php56-extensions: pkg-delete php56-\* mod_php56 php56-extensions And then installed the php71-extensions. cd /usr/ports/lang/php71-extensions make config make install clean Make sure you make a list of all the installed php56-extensions so you can select the same ones in php71-extensions. Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
--On June 4, 2017 at 12:40:43 PM -0700 "Jack L." <xxjack1...@gmail.com> wrote: mysql_connect is obsolete in php 7+, you need to change your code to use mysqli_connect. The site is up and running on php71 and both Joomla and Wordpress are working fine. I don't know if I did something wrong in php70 or not. I know I had mysqli configured in php70-extensions. Oh well, it's working fine now. Thanks for all the responses. Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
--On June 4, 2017 at 12:40:43 PM -0700 "Jack L." <xxjack1...@gmail.com> wrote: mysql_connect is obsolete in php 7+, you need to change your code to use mysqli_connect. Oh, that sucks. This server is running both Joomla and Wordpress. Joomla has been complaining about updating php to 70, so I thought I'd give it a shot. Don't know if Wordpress is compatible or not. I just installed php71 after reverting back to php56. We'll see if everything works or not. Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
--On June 4, 2017 at 9:28:29 PM +0200 Kurt Jaeger <li...@opsec.eu> wrote: Hi! PHP Fatal error: Uncaught Error: Call to undefined function mysql_connect() I noticed that there was no php70-mysql extension any more. Is there something that replaces that? databases/php70-mysqli Btw, you can migrate to php71, as well. Not much difference. That was installed. Is there a configuration option that needs to be set or changed? Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade PHP to 7.0
--On June 4, 2017 at 2:42:51 PM -0400 scratch65...@att.net wrote: [Default] On Sun, 04 Jun 2017 12:10:46 -0500, Paul Schmehl <pschmehl_li...@tx.rr.com> wrote: Are there any instructions explaining how to upgrade php from 5.6.30 to 7.0? Is it fairly straightforward? Or are there some gotchas one needs to know about? php.net has some info, but if you're not doing anything fancy you shouldn't have any trouble. I always mind Tony Hoare's advice and avoid the fancy stuff, so when I installed 7.0 instead of 5.6 everything ran fine. Unfortunately, I had a problem. PHP Fatal error: Uncaught Error: Call to undefined function mysql_connect() I noticed that there was no php70-mysql extension any more. Is there something that replaces that? Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Upgrade PHP to 7.0
Are there any instructions explaining how to upgrade php from 5.6.30 to 7.0? Is it fairly straightforward? Or are there some gotchas one needs to know about? Paul Schmehl, Retired 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Problems with mail/postfix-policyd-weight
Yesterday I upgraded my mail server from 8.4-RELEASE to 10.2-RELEASE. After a major release, you must reinstall all ports, so I did. Immediately afterwards I began getting errors from policyd-weight. postfix/policyd-weight[17305]: warning: child: err: Undefined subroutine Net::DNS::Packet::dn_expand called at /usr/local/bin/policyd-weight line 3589, GEN37 line 26. I uninstalled and reinstalled both mail/postfix-policyd-weight and dns/p5-Net-DNS to no avail. Googling shows that this was a problem that cropped up in June, 2014 but was resolved with 0.1.14 beta. The ports version is 0.1.15.2. The notes say not to use Net::DNS 0.54. The ports version is 1.01. So what's going on here? Has anyone else experienced this problem? Have a solution? Right now policyd-weight is uninstalled until I can resolve this issue. 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 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Would appreciate a committer's attention to these
--On January 8, 2015 at 3:24:55 PM -0500 Steven Kreuzer skreu...@freebsd.org wrote: On Thu, Jan 8, 2015 at 3:06 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I submitted change maintainer requests for all my remaining ports. 1/30 is my retirement date. I would appreciate it if someone could pick these up and process them by that date. https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=change%20main tainerlist_id=41295 Hi Paul- I grabbed most of those PRs and I will start working through them all. Thank you for your service to the FreeBSD community and congratulations on the retirement. Thanks. -- 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 ___ 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
Would appreciate a committer's attention to these
I submitted change maintainer requests for all my remaining ports. 1/30 is my retirement date. I would appreciate it if someone could pick these up and process them by that date. https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=change%20maintainerlist_id=41295 -- 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 ___ 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
sysutils/bsdststs
I got my monthly report and noticed that a number of ports were corrupt. pkg_info: the package info for package 'OpenSP-1.5.2_2' is corrupt pkg_info: the package info for package 'apache22-2.2.27_2' is corrupt pkg_info: the package info for package 'autoconf-2.69' is corrupt My ports are fine according to %pkg info. Why is bsdstats still using the old ports utilities? Is it going to be updated? 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 ___ 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: sysutils/bsdststs
--On January 1, 2015 at 3:32:19 PM -0500 A.J. Kehoe IV (Nanoman) nano...@nanoman.ca wrote: Paul Schmehl wrote: I got my monthly report and noticed that a number of ports were corrupt. pkg_info: the package info for package 'OpenSP-1.5.2_2' is corrupt pkg_info: the package info for package 'apache22-2.2.27_2' is corrupt pkg_info: the package info for package 'autoconf-2.69' is corrupt My ports are fine according to %pkg info. Why is bsdstats still using the old ports utilities? Is it going to be updated? pkg support was added to the FreeBSD BSDstats port in 2012: http://svnweb.freebsd.org/ports/head/sysutils/bsdstats/files/300.statisti cs.in?r1=300897r2=301654pathrev=301654 If the file /var/db/pkg/local.sqlite exists on your system, BSDstats should try to use pkg as expected. It does. # ls -lsa /var/db/pkg/local.sqlite 15696 -rw-r--r-- 1 root wheel 16044032 Jan 1 19:13 /var/db/pkg/local.sqlite Maybe there's a logic flaw? 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 ___ 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
Getting rid of my ports
I am retiring at the end of January. I will no longer be able to maintain ports (nor will I have much interest in doing so), so I need volunteers to take them over. They should all be up to date (although I haven't checked today.) Here's the list: # make search key=pa...@utdallas.edu | grep Port Port: byaccj-1.15 Port: liblognorm-1.0.0_1 Port: p5-Iodef-Pb-Simple-0.21 Port: p5-Net-DNS-Match-0.05 Port: p5-Parse-Range-0.96 Port: p5-IP-Anonymous-0.04 Port: p5-Net-Nessus-XMLRPC-0.30_1 Port: argus-sasl-3.0.8 Port: argus-clients-sasl-3.0.8 Port: p5-Net-Abuse-Utils-Spamhaus-0.04 Port: afterglow-1.6.2 Port: barnyard2-1.13 Port: barnyard2-sguil-1.13 Port: chaosreader-0.94_1 Port: p5-Snort-Rule-1.07 Port: sancp-1.6.1_5 Port: spybye-0.3_4 Port: p5-Linux-Cpuinfo-1.8 Port: p5-CIF-Client-0.21 Port: p5-REST-Client-249 Port: iwidgets-4.0.1_1 Port: p5-Gtk2-Ex-Dialogs-0.11_5 Port: p5-Gtk2-Ex-Utils-0.09_6 Port: p5-Gtk2-GladeXML-1.007_3 -- 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 ___ 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
PR 193566 and 193567
These were port updates submitted almost a month ago by me (I'm the maintainer.) Would someone mind looking at these and getting them approved? There should not be any issues with them, since very little was changed (just the version number in the Makefile and the distinfo file.) -- 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 ___ 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: PR 193566 and 193567
Thank you. --On October 6, 2014 at 8:14:34 PM +0200 Kurt Jaeger li...@opsec.eu wrote: Hi! I tested net-mgmt/argus3-clients using poudriere and found this issue: === Checking for items in STAGEDIR missing from pkg-plist Error: Orphaned: man/man1/rasql.1.gz Error: Orphaned: man/man1/rasqlinsert.1.gz Error: Orphaned: man/man1/rasqltimeindex.1.gz I think that is a pkg-plist issue. Can you check ? I found the solution by adding this to the pkg-plist: %%MYSQL%%man/man1/rasql.1.gz %%MYSQL%%man/man1/rasqlinsert.1.gz %%MYSQL%%man/man1/rasqltimeindex.1.gz -- 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 ___ 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
Abandoning the sguil ports
I am the maintainer for security/sguil-server, security/sguil-sensor and security/sguil-client. I am officially abandoning the ports. The security/sguil-server port is not staged. The other two are. The software has a new release out, so all three ports would need to be updated. Furthermore, the developer has changed to github, which drives me nuts. Finally, the ports are not even being used. They don't even have one download according to bsdstats.org. Since ports that aren't staged will go away on 9/1/2014, is there something additional that I would need to do? Or can these ports simply be removed from the tree now? -- 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 ___ 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: Abandoning the sguil ports
--On June 21, 2014 at 1:55:37 AM +0600 Muhammad Moinur Rahman 5u623...@gmail.com wrote: Hi Paul, I want to take those. OK. My suggestion would be to start from scratch with the -server port. I tried to create the port so it would handle all the details of installing and uninstalling, including setting up the certs. That's probably not the best way to go with staging. Since no one is using them, I'm not sure what the point is, but have at it. 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 ___ 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: SHEBANG_FILES
--On June 13, 2014 at 9:23:44 AM +0200 Matthias Andree matthias.and...@gmx.de wrote: Am 12.06.2014 23:52, schrieb Paul Schmehl: --On June 12, 2014 at 11:25:03 PM +0200 Kurt Jaeger li...@opsec.eu wrote: Hi! I'm working on switching one of my ports over to staging. During testing, I got this: Error: '/usr/bin/perl' is an invalid shebang you need USES=shebangfix for 'bin/argus-lsof' Error: '/bin/bash' is an invalid shebang you need USES=shebangfix for 'bin/argus-vmstat' I've never seen this before, so I had to do a little digging. Eventually I put this in the Makefile: USES=shebangfix SHEBANG_FILES=bin/argus-lsof bin/argus-vmstat Almost correct. Do I need a comma between the files? No, but instead of giving their install location, you need to list the files with the relative path into $WRKSRC after they've gotten unpacked. That *is* the relative path into WRKSRC. I just gave up trying to figure it out and used REINPLACE instead. 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 ___ 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: What is the preferred method for updating ports now?
--On June 11, 2014 at 3:10:07 PM -0700 Charles Swiger cswi...@mac.com wrote: On Jun 11, 2014, at 2:43 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: /usr/ports]# svn status svn: warning: W155007: '/usr/ports' is not a working copy Hmm.so I thought maybe I had to co the ports first: # svn co svn://svn.freebsd.org/ports/head/ That checks out the ports tree under a workarea named 'head' in your local directory. svn co svn://svn.freebsd.org/ports/head/ /usr/ports ...would checkout a workarea under /usr/ports. After that finished, I did this: /usr/ports]# svn up Skipped '.' Summary of conflicts: Skipped paths: 1 So then I did this: /usr/ports]# svn status svn: warning: W155007: '/usr/ports' is not a working copy OK, now I'm really confused. It seems that I've done nothing at all. So what am I doing wrong? Try: mv /usr/ports /usr/ports_20140611 mv head /usr/ports cd /usr/ports svn status svn up Regards, Thanks. That was exactly the problem. -- 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 ___ 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
SHEBANG_FILES
I'm working on switching one of my ports over to staging. During testing,
I got this:
Error: '/usr/bin/perl' is an invalid shebang you need USES=shebangfix for
'bin/argus-lsof'
Error: '/bin/bash' is an invalid shebang you need USES=shebangfix for
'bin/argus-vmstat'
I've never seen this before, so I had to do a little digging. Eventually I
put this in the Makefile:
USES=shebangfix
SHEBANG_FILES=bin/argus-lsof bin/argus-vmstat
But I'm getting errors:
=== Patching for argus-sasl-3.0.6.1
sed: bin/argus-lsof: No such file or directory
The argus-lsof and argus-vmstat files don't exist in the tarball. They are
created during the make process. So I moved the SHEBANG_FILES line into
the .do-install section.
do-install:
${INSTALL_PROGRAM} ${WRKSRC}/bin/argus
${STAGEDIR}/${PREFIX}/sbin/argus
SHEBANG_FILES= bin/argus-lsof bin/argus-vmstat
Same error.
I even moved it inside the for loop that deals with the files:
.for i in argus-lsof argus-snmp argus-vmstat argusbug
SHEBANG_FILES= bin/argus-lsof bin/argus-vmstat
${INSTALL_SCRIPT} ${WRKSRC}/bin/$i ${STAGEDIR}/${PREFIX}/bin/$i
No difference.
What's the proper way to do this?
--
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
___
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: SHEBANG_FILES
--On June 12, 2014 at 11:25:03 PM +0200 Kurt Jaeger li...@opsec.eu wrote: Hi! I'm working on switching one of my ports over to staging. During testing, I got this: Error: '/usr/bin/perl' is an invalid shebang you need USES=shebangfix for 'bin/argus-lsof' Error: '/bin/bash' is an invalid shebang you need USES=shebangfix for 'bin/argus-vmstat' I've never seen this before, so I had to do a little digging. Eventually I put this in the Makefile: USES=shebangfix SHEBANG_FILES=bin/argus-lsof bin/argus-vmstat Almost correct. Do I need a comma between the files? But I'm getting errors: === Patching for argus-sasl-3.0.6.1 sed: bin/argus-lsof: No such file or directory The argus-lsof and argus-vmstat files don't exist in the tarball. They are created during the make process. Can you fix the path from the source files they are created from ? Then you do not need shebangfix for them. Well, yeah, I could. Which port is that ? net-mgmt/argus3 -- 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 ___ 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
What is the preferred method for updating ports now?
I used to use cvsup. Then I switched to portsnap. Do I now need to switch to svn? If so, is there a way to use svn to only update those ports that have changed since the last update? I've been using svn for a while to work on port updates. I know how to fetch the entire port infrastructure but not how to only update those ports that have changed. Portsnap can be automated to keep ports up to date. Is there a similar utility that uses svn instead? Is portmaster going away any time soon? Or is that now the preferred method for updating ports? Is portupgrade going away? (I no longer use it - just wondering.) As a port maintainer, what tools do I use now that I've converted to pkgng? Do we still use portlint? Or is there a new way to do that? So many questions.. -- 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 ___ 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: What is the preferred method for updating ports now?
--On June 11, 2014 at 6:01:43 PM +0100 Matthew Seaman matt...@freebsd.org wrote: On 06/11/14 17:20, Paul Schmehl wrote: I used to use cvsup. Then I switched to portsnap. Do I now need to switch to svn? If so, is there a way to use svn to only update those ports that have changed since the last update? I've been using svn for a while to work on port updates. I know how to fetch the entire port infrastructure but not how to only update those ports that have changed. Portsnap can be automated to keep ports up to date. Is there a similar utility that uses svn instead? To maintain a copy of the ports tree, portsnap is probably least effort, unless you're maintaining ports or want to make local customizations, in which case use svn. Is portmaster going away any time soon? Or is that now the preferred method for updating ports? Is portupgrade going away? (I no longer use it - just wondering.) No. portmaster and portupgrade are here for the foreseeable future. There's no reason to stop using them if they are your tools of choice. Neither of those are specifically preferred for updating ports -- in fact, there isn't any one method that is preferred: ports supports installing from source, with or without using tools like portmaster or portupgrade, and it now also supports installing using binary packages either from the FreeBSD official repositories or other repositories; either your own, or run by (hopefully reputable) third parties like PC-BSD for instance. As a port maintainer, what tools do I use now that I've converted to pkgng? Do we still use portlint? Or is there a new way to do that? So many questions.. Yes, portlint is still important. However as a developer, you should add DEVELOPER=YES to your /etc/make.conf -- this will enable a number of sanity tests now built into the ports Makefiles. This, plus the adoption of staging means that you should be able to do unit tests on an updated port as simply as: % make stage % make check-orphans % make package PACKAGES=/tmp which you can run as an ordinary user, rather than needing root level access (assuming you've installed all the dependencies already.) If your port passes all those, then it's in good shape, although I'd recommend further testing via Redports or the like before committing to the tree. Thank you, Matthew. As always, you have been very helpful. -- 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 ___ 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: What is the preferred method for updating ports now?
--On June 11, 2014 at 7:41:42 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-11 18:20, Paul Schmehl wrote: I used to use cvsup. Then I switched to portsnap. Do I now need to switch to svn? If so, is there a way to use svn to only update those ports that have changed since the last update? I've been using svn for a while to work on port updates. I know how to fetch the entire port infrastructure but not how to only update those ports that have changed. Portsnap can be automated to keep ports up to date. Is there a similar utility that uses svn instead? simply go to the root of your portstree and fire the command `svn up', but watch the output for conflicts marked with a capital 'C'. Running from time to time `svn cleanup' will keep remove dead metadata from the .svn directory. I did this and got the following: /usr/ports# svn up Skipped '.' Summary of conflicts: Skipped paths: 1 So I did this: /usr/ports# svn up svn://svn.freebsd.org/ports/HEAD/ svn: E205000: Try 'svn help update' for more information svn: E205000: 'svn://svn.freebsd.org/ports/HEAD' is not a local path [root@mail /usr/ports]# svn up svn://svn.freebsd.org/ports/ svn: E205000: Try 'svn help update' for more information svn: E205000: 'svn://svn.freebsd.org/ports' is not a local path Then I did this: /usr/ports]# svn status svn: warning: W155007: '/usr/ports' is not a working copy Hmm.so I thought maybe I had to co the ports first: # svn co svn://svn.freebsd.org/ports/head/ After that finished, I did this: /usr/ports]# svn up Skipped '.' Summary of conflicts: Skipped paths: 1 So then I did this: /usr/ports]# svn status svn: warning: W155007: '/usr/ports' is not a working copy OK, now I'm really confused. It seems that I've done nothing at all. So what am I doing wrong? -- 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 ___ 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: How are ports built now
--On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-07 22:40, Paul Schmehl wrote: --On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docproj Install print/ghostscript9 Upgrade pkgconf-0.9.5 to pkgconf-0.9.6 Upgrade lcms2-2.6_1 to lcms2-2.6_2 Install textproc/docbook-xml Install textproc/docbook-sgml Install www/mod_authnz_external22 === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: Installing xf86vidmodeproto: 2.3.1 Installing damageproto: 1.2.1 Installing dri2proto: 2.8 Installing pciids: 20140526 Installing randrproto: 1.4.0 Installing perl5: 5.16.3_10 Installing db48: 4.8.30.0 Reinstalling autoconf-2.69 (direct dependency changed) Reinstalling automake-1.14 (direct dependency changed) Reinstalling bootstrap-openjdk-r351880 (needed shared library changed) Reinstalling curl-7.37.0 (options changed) Reinstalling dejavu-2.34_3 (options changed) Upgrading en-freebsd-doc: 43251,1 - 44807,1 Reinstalling gettext-0.18.3.1_1 (options changed) Reinstalling igor-1.431 (direct dependency changed) Reinstalling ja-font-ipa-00303_1 (direct dependency changed) Reinstalling libgcrypt-1.5.3_2 (direct dependency changed) Reinstalling libwmf-nox11-0.2.8.4_11 (direct dependency changed) Reinstalling libxcb-1.10_2 (direct dependency changed) Reinstalling libxslt-1.1.28_3 (direct dependency changed) Reinstalling mcrypt-2.6.8_1 (direct dependency changed) Reinstalling mkfontdir-1.0.7 (direct dependency changed) Reinstalling mysqltuner-1.3.0 (direct dependency changed) Reinstalling neon29-0.29.6_6 (direct dependency changed) Reinstalling p5-Carp-Clan-6.04 (direct dependency changed) Reinstalling p5-Locale-gettext-1.05_3 (direct dependency changed) Reinstalling p5-XML-Parser-2.41_1 (direct dependency changed) Reinstalling p5-type1inst-0.6.1_5 (options changed) Reinstalling perl5.14-5.14.4_7 (options changed) Reinstalling php5-5.4.29 (options changed) Reinstalling php5-bz2-5.4.29 (direct dependency changed) Reinstalling php5-ctype-5.4.29 (direct dependency changed) Reinstalling php5-curl-5.4.29 (direct dependency changed) Reinstalling php5-dom-5.4.29 (direct dependency changed) Reinstalling php5-filter-5.4.29 (direct dependency changed) Reinstalling php5-hash-5.4.29 (direct dependency changed) Reinstalling php5-iconv-5.4.29 (direct dependency changed) Reinstalling php5-json-5.4.29 (direct dependency changed) Reinstalling php5-mbstring-5.4.29 (direct dependency changed) Reinstalling php5-mssql-5.4.29 (direct dependency changed) Reinstalling php5-mysql-5.4.29 (direct dependency changed) Reinstalling php5-openssl-5.4.29 (direct dependency changed) Reinstalling php5-pdo-5.4.29 (direct dependency changed) Reinstalling php5-phar-5.4.29 (direct dependency changed) Reinstalling php5-posix-5.4.29 (direct dependency changed) Reinstalling php5-session-5.4.29 (direct dependency changed) Reinstalling php5-simplexml-5.4.29 (direct dependency changed) Reinstalling php5-tokenizer-5.4.29 (direct dependency changed) Reinstalling php5-xml-5.4.29 (direct dependency changed) Reinstalling php5
Re: How are ports built now
--On June 8, 2014 at 11:38:37 AM -0400 Kevin Phair phair.ke...@gmail.com wrote: On 6/8/14, 11:20 AM, Paul Schmehl wrote: --On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) [[stuff]] === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: [[different stuff]] The upgrade will require 426 MB more space 373 MB to be downloaded Clearly portmaster and pkg upgrade disagree on what work needs to be done. Do you have non-default port options configured? I believe the packages are all created with the default options, so that if you've installed everything from ports, and some of those ports with non-default options, your dependencies when upgrading with portmaster could end up looking different than when upgrading with pkg. Yes, I do have a few ports with none-default options. The problem is, they're critical ports (like apache22). 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 ___ 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: How are ports built now
--On June 8, 2014 at 10:32:33 AM -0600 Warren Block wbl...@wonkity.com wrote: On Sun, 8 Jun 2014, Paul Schmehl wrote: Yes, I do have a few ports with none-default options. The problem is, they're critical ports (like apache22). At present, these have to be built from ports. Long-term, there is a plan to have multiple packages for ports with options. It seems like a completely unworkable solution to me. For example, say you have a port with 10 options. Imagine how many different binaries you would have to have to cover every possible combination of selected options. It would take a huge amount of storage 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 ___ 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: How are ports built now
--On June 8, 2014 at 6:05:35 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-08 17:20, Paul Schmehl wrote: --On June 7, 2014 at 11:16:04 PM +0200 olli hauer oha...@gmx.de wrote: On 2014-06-07 22:40, Paul Schmehl wrote: --On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. Do you see which port is looping? Perhaps a port was moved / renamed / removed and portmaster therfore is looping around Sadly I cannot help more since I used all the years tinderbox / poudriere to build packages. I've been working on this for two days now, so the parameters have changed a bit. But here's an example of what prompted my question: This is the result of portmaster -ad === All (18) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docproj Install print/ghostscript9 Upgrade pkgconf-0.9.5 to pkgconf-0.9.6 Upgrade lcms2-2.6_1 to lcms2-2.6_2 Install textproc/docbook-xml Install textproc/docbook-sgml Install www/mod_authnz_external22 === Proceed? y/n [y] n This is the result of pkg upgrade -n # pkg upgrade -n Updating repository catalogue Upgrades have been requested for the following 150 packages: Installing xf86vidmodeproto: 2.3.1 Installing damageproto: 1.2.1 Installing dri2proto: 2.8 Installing pciids: 20140526 Installing randrproto: 1.4.0 Installing perl5: 5.16.3_10 Installing db48: 4.8.30.0 On possible issue between `pkg upgrade' and portmaster with an current ports tree is that some of the ports where updated between last wednesday and now. E.g pkgconf and the freebsd docs where updated after the last package build. [removed a bunch of lines] Is it possible that portmaster builds with NO_PORTDOCS or DOCS=off or similar? No. The port mail/pflogsumm has as only OPTIONS_DEFINE=DOCS, but `pkg upgrade' complains about changed options Reinstalling pflogsumm-1.1.5,1 (options changed) DOCS on/off could be a possible explanation for all the '(options changed)' updates. In general I accept the default options, which is to install docs and examples. There are very few cases where I do not do that. Here's what portmaster wants to build now: === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docbook-sgml Install textproc/docbook-xml Install www/mod_authnz_external22 Re-install docproj-2.0_2 Install print/ghostscript9 All of these ports fail to install individually. Unfortunately, I have to have ghostscript because I use ImageMagick for our forum. Otherwise I remove it. It's always been problematic during installs and upgrades. 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 ___ 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: How are ports built now
--On June 8, 2014 at 7:17:01 PM +0200 Torfinn Ingolfsen tin...@gmail.com wrote: On Sat, Jun 7, 2014 at 10:19 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. Ah, ok. Sorry for the confusion. I'm still using portupgrade, and haven't used portmaster, so I have nothing to add about that. One one of the servers I seem to be in some sort of loop. Every time I run portmaster -ad the same ports come up for install/upgrade. Yet when portmaster completes it says the ports were successfully installed. Run portmaster -ad again, the same list pops up. All I can say is follow this mailing list closely. There seems to be a lot of problems with the ports tree lately, it has made me lose some confidence in the ports tree. Now I only update when I absolutely have to. Me too. Between staging and the change to pkgng, everything is upside down. It seems FreeBSD is headed toward the dependency hell of Linux instead of the smooth running ports system we once had. 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 ___ 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
Struggling mightily with port updates
I upgraded two systems to 8.4 and ran portmaster -ad to update all ports. Most of it worked fine, but I'm in docbook hell now. I also don't understand this: === All (6) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Re-install ruby-1.9.3.484_2,1 Install textproc/docbook-xml Install www/mod_authnz_external22 Re-install docproj-2.0_2 Install print/ghostscript9 === Proceed? y/n [y] I just upgraded ruby: === The following actions were performed: Re-installation of ruby-1.9.3.484_2,1 Re-installation of ruby19-bdb-0.6.6_3 Re-installation of ruby19-date2-4.0.19 So why does portmaster want to reinstall it? Is there a way to dump all the docbook stuff? It's a royal PITA. 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 ___ 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: How are ports built now
--On June 8, 2014 at 2:50:53 PM -0400 Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org wrote: Paul Schmehl pschmehl_li...@tx.rr.com writes: Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. Presumably it's a typo that you left out the -f option? Without that, you wouldn't have been rebuilding everything, and surely you would have noticed by now. Yes, it's a typo. I've been typing -ad for so long now trying to fix the remaining problems that I left that off. I'm about to give up on the whole thing and switch to another OS. This is beyond frustrating. 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 ___ 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: Struggling mightily with port updates
--On June 8, 2014 at 6:38:48 PM -0600 Warren Block wbl...@wonkity.com wrote: On Sun, 8 Jun 2014, Paul Schmehl wrote: I upgraded two systems to 8.4 and ran portmaster -ad to update all ports. Most of it worked fine, but I'm in docbook hell now. I also don't understand this: === All (6) === The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Re-install ruby-1.9.3.484_2,1 Install textproc/docbook-xml Install www/mod_authnz_external22 Re-install docproj-2.0_2 Install print/ghostscript9 === Proceed? y/n [y] I just upgraded ruby: === The following actions were performed: Re-installation of ruby-1.9.3.484_2,1 Re-installation of ruby19-bdb-0.6.6_3 Re-installation of ruby19-date2-4.0.19 So why does portmaster want to reinstall it? /usr/ports/UPDATING shows manual steps that must be taken. The 20140219 entry talks about the DocBook ports. I read that, but the uninstalls failed. I ended up having to run down the dependency rabbit hole, uninstalling ports one at a time until the one depending upon them were all gone. It's working now. 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 ___ 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: Who was the mental genius
--On June 7, 2014 at 1:32:08 PM +0200 Michelle Sullivan miche...@sorbs.net wrote: Paul Schmehl wrote: I appreciate the advice. I've elected to setup an alternate form of backup (using rsync over ssh to backup each server to its sibling) so I can upgrade to 8.4 without worrying about a loss. Once that's complete, I'll get the new backup system in place (using Storgrid backing up to a SAN at the hosting provider). After that I can comfortably move to 9 or 10. I don't like running bleeding edge releases on production servers. This work I'm doing is entirely voluntary, for a hobby website with a small budget, so I have to be very careful about not breaking anything. When I installed one of these servers 9 wouldn't even install (missing RAID drivers), which is why I used 8. My issue is some of the production servers I am running if I perform an 'OS Reload' Softlayer (the hosting provider) will only allow me to reload with 7.x releases... totally unsupported. Others only 7.2 or 8.4, others 8.4, 9.0 or 10.0... So last production reload I did after freebsd-update screwed up (and it was probably user error (or distro error - Softlayer's setup) not a problem with freebsd-update - going from 7.2-8.4) I had to reload with 9.0 and freebsd-update to 9.2 (10.0 was not even an option on that server - just 2 months ago) FreeBSD maintainer problem? No User (me) problem? No and Yes (no because I didn't do anything, yes because a production server went down) Softlayer problem? Probably - but then they give you 20+ OS options mostly Windows and (paid support) $penguin OSs ... FreeBSD seems not a priority for them (and they don't have any other *BSDs) so can you blame them? (probably getting kickbacks for the support contracts) There isn't an easy answer, everyone is trying to do the right thing, but I feel your pain (mentioned elsewhere in this thread.) Thank you, Michelle. I think you've hit on one of the crucial elements of this problem. For example; after realizing that I had to upgrade, I had to scramble to setup a temporary backup solution before I could upgrade. (My original problem was that my backup system failed, and I needed to devise an alternate solution. After some discussion with the owners, it was decided to pay for a backup solution from the hosting provider, because that will give us the best long term stability.) So, I setup a temporary backup, then upgraded to 8.4. AFTER doing that, Baptiste responded and, among other things, revealed that 8.4 wouldn't be good enough. So now I have to upgrade yet again. Right now both systems are at 8.4, but the critical system (the website) is still not fixed. I ran portmaster -ad to update all the ports and, as usual, ran into problems. I'm currently working through those problems, but it will take a while. And that is the point, for me. I have been thrust into a situation where, when I had other plans for the weekend - involving my grandchildren - I now have to devote time to get this system back into working condition BEFORE I do it all over again (moving to 9. - I don't dare go to 10. yet on a production system.) If something breaks in a bad way, then I have to get in my car, drive over to the hosting site and stay there until it's fixed. Yes, if this was my job, that would be expected. But it's not. This is volunteer work that I do on my own time without compensation. So it might be understandable that I got a little pissed off and reacted with anger when things broke so unexpectedly and without notice. I've searched. There's no notice in UPDATING. There was no announcement on the ports list. I found NOTHING to warn me of this problem except other people complaining of the same problem. 8.4 went EOL in September 2012. This problem was introduced with a patch committed on May 5, 2014. So the smart asses who ridiculed me about using an out of date system don't even know what they're talking about. Yet some pompous jerks on this list want to accuse me of incompetence, laziness or dereliction without even knowing the circumstances of the problem. Most of them assumed this was my job and I had fallen down on it. Not one of them tried to address the actual issue. They were more interested in ridiculing me. Not that I care. But that kind of attitude and behavior will drive some people away from FreeBSD. (And yes, I'm deliberately poking them in the eye, and they know who they are.) I appreciate people like you and others who have read through the thread, overlooked the anger and zeroed in on the issue. I especially appreciate you making others aware of the many complex issues that some of us have to deal with that they don't seem to think about before making major changes that break things. I'm not pointing fingers. I'm just saying, hey, this blew up in a big way. How about some advance warning next time? Without that, FreeBSD won't survive. Arnold is correct. I love
How are ports built now
I'm an oldtimer, having used the port building system for years. Recently I upgraded two servers to 8.4 and implemented the pkgng system. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. Is portmaster not the appropriate method for updating ports with pkgng? Are we forced to now go to binary packages only? 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 ___ 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: How are ports built now
--On June 7, 2014 at 10:04:17 PM +0200 Torfinn Ingolfsen tin...@gmail.com wrote: Hi, On Sat, Jun 7, 2014 at 9:03 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I'm an oldtimer, having used the port building system for years. Recently I upgraded two servers to 8.4 and implemented the pkgng system. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. Is portmaster not the appropriate method for updating ports with pkgng? Are we forced to now go to binary packages only? I think you are a bit confused here. AFAIK, portmaster, portupgrade and so on are management tools for installing and upgrading ports. However, to update the ports tree on your machine (which is what you use when you are building from source) you need another tool. Supported versions of FreeBSD have the portsnap(8) command, which is used to update the ports tree. Thanks, but no, you misunderstand. I just upgraded to servers to 8.4 and decided to adopt the new pkgng system at the same time. Any time I upgrade the OS, I always rebuild all ports. I've been using portmaster -ad to do that for a while now. One one of the servers I seem to be in some sort of loop. Every time I run portmaster -ad the same ports come up for install/upgrade. Yet when portmaster completes it says the ports were successfully installed. Run portmaster -ad again, the same list pops up. I'm still trying to figure out what's wrong. I thought it might be some sort of conflict between the portmaster db and the pkgng db. 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 ___ 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: How are ports built now
--On June 7, 2014 at 10:22:41 PM +0200 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for building from ports, Portmaster doesn't care whether you're using the new PNGNG or the old pkg_* tools. Thanks. That's good to know. Now, when I run portmaster -ad, it seems to keep reinstalling the same ports over and over again. That's strange. Perhaps PKGNG hasn't been initialised properly on your system(s), that's all I can think of at the moment. Did you use pkg2ng? I'm pretty sure I did, but I ran it again. I noticed several errors which I will have to investigate. 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 ___ 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: Who was the mental genius
--On June 6, 2014 at 8:35:06 AM +0200 John Marino freebsd.cont...@marino.st wrote: On 6/6/2014 05:37, Paul Schmehl wrote: Something like that would have been more than adequate. As I pointed out, the warning you get about pkgng and the 9/1/2014 deadline is perfect. It's been there for a couple of months, and it pops up ever time you do a port. If you miss that and don't convert, you don't have anyone but yourself to blame. Which is exactly the same case with you and the 8.3 EOL. If your business relies involves server maintenance, it's entirely your responsibility to track EOL. How somebody with senior in their job title is looking to blame everyone else for failing something so basic is rich. You say semantics isn't important? You say 8.3 isn't old? It may not be old compared to a dog, but it reached its published end-of-life. Any expectation you have about support after EOL where probably forged by watching Microsoft support XP. That's not the model to expect. Install some mirrors in your house. I have no idea why you've decided to assume the role of preacher and tell me what to do, but I can assure you that you are completely ignorant of the circumstances behind my complaints. They have absolutely nothing to do with my professional position. Regarding your comment about EOL, one thing has been almost constant throughout my professional career. When a system goes EOL it isn't deliberately broken by the vendor. The system will happily hum along and function for years after EOL without problems. Breaking something as vital as the ports system without proper warning is not a way to win converts to your platform or to retain those who have used it for a long time. Again. I think FreeBSD is a great OS. It's the only Unix platform I use (and I've tried them all, trust me.) It saddens me to see it losing market share because of tone deaf development processes that ignore the end user. If I didn't give a shit, I wouldn't have complained. Your reference to Microsoft is laughable. I haven't done support or admin work on a Windows platform in more than sixteen years. As for your idiotic advice, not everyone in the world has the wherewithal to install some mirrors in your house, but my recommendation to you would be to look in the ones at your house before you ignorantly criticize others. -- 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 ___ 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: Who was the mental genius
--On June 6, 2014 at 5:27:58 PM +1000 Dewayne Geraghty
dewayne.gerag...@heuristicsystems.com.au wrote:
On 6/06/2014 11:05 AM, Erich Dollansky wrote:
Hi,
On Thu, 05 Jun 2014 15:09:53 -0500
Paul Schmehl pschmehl_li...@tx.rr.com wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system
instead of outright breaking ports? The idiots are apparently
running the asylum. {{sigh}}
this is the reason why I am asking for versions on the ports tree since
a decade. Ok, we have the revision now. Just go back in the revision
until it works. It is a good practice to make a note of the revision of
the running ports tree you have before updating it.
Erich
___
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
Paul,
I would echo Enrich's advise. Occassionally over the last 18 months my
ports tree build (of 487 ports) would fail. A workaround, for me, was
to update the ports tree and then revert /usr/ports/Mk - sometimes I'd
search through the svn logs for a clue, but more recently I'd revert a
week at a time. This being done to get something urgent out of the way
until a PR or fix was acted upon, and the folks supporting ports
meta-system are extremely responsive. Of course if a port needs
something that was changed under /usr/ports/Mk then you'll probably have
to revert the port as well and change the VERSION info as needed - this
is time-consuming and you really need to set aside some time for
testing. Its a real kludge but if you're stuck...
As I recall the change to ports to use a different make was tied to EOL
for 8.3, seems reasonable though something of a paradigm shift for ol'
timers (I'm a 2.2.5 person) that are used to building ports on a system
long after the base system has been EOL.
However it does lend itself to the argument that if changes to the ports
system is tied to the base operating system, then the meta-ports ie
/usr/ports/Mk should also. Unfortunately release management of the
ports meta-system, after a decade, remains elusive. Though it should be
noted that preparatory communication is improving - thanks to the team
and Eitan's contributions.
During some side-conversations I was surprised to learn that there is
some back-porting of fixes taking place in the ports branches ref:
http://svnweb.freebsd.org/ports/branches/2014Q2/ (thanks to Guido for
bringing that to our attention). So maybe this is your starting point and
svn update the particular ports you require is another option (as a
temporary workaround)?
I appreciate the advice. I've elected to setup an alternate form of backup
(using rsync over ssh to backup each server to its sibling) so I can
upgrade to 8.4 without worrying about a loss. Once that's complete, I'll
get the new backup system in place (using Storgrid backing up to a SAN at
the hosting provider).
After that I can comfortably move to 9 or 10. I don't like running
bleeding edge releases on production servers. This work I'm doing is
entirely voluntary, for a hobby website with a small budget, so I have to
be very careful about not breaking anything.
When I installed one of these servers 9 wouldn't even install (missing RAID
drivers), which is why I used 8.
--
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
___
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: Who was the mental genius
--On June 6, 2014 at 10:51:04 AM +0200 Michael Gmelin gre...@freebsd.org wrote: On 06 Jun 2014, at 10:22, John Marino freebsd.cont...@marino.st wrote: On 6/6/2014 10:18, Alfred Perlstein wrote: Sure, but really a couple of lines to warn people and wave them towards next steps is probably advisable next time. Maybe we can alter the uname -a string to show the EOL so that every time the machine boots you see it on top of the MOTD. :) Of course, that won't help for the turn-on-and-forget servers with uptime measured in years... As a serious questions, where should such a you have X months/days remaining before server is EOL, update before then messages pop up? weekly cron messages sent to root? periodic/security/450-check_eol ?(info if 90 days left, error if past eol) EOL notification is not the problem. The problem is breaking ports at EOL. That's a special circumstance and begs for notification. This isn't rocket science. For at least two months now this notification has been popping up every time I work on ports. /!\ WARNING /!\ pkg_install EOL is scheduled for 2014-09-01. Please consider migrating to pkgng http://blogs.freebsdish.org/portmgr/2014/02/03/time-to-bid-farewell-to-the-old-pkg_-tools/ If you do not want to see this message again set NO_WARNING_PKG_INSTALL_EOL=yes in your make.conf Do you think I would miss the 9/1 deadline? Not a chance. But the advance warning gives me time to plan the change when it's convenient for me. This change has me scrambling to adapt. Granted, it only took me a few minutes to figure out what to do, but not everyone has the background and experience to do that. Some will simply panic. Others will switch to Linux. That doesn't seem like a goal FreeBSD should support. -- 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 ___ 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: Who was the mental genius
--On June 6, 2014 at 5:17:40 PM +0200 Baptiste Daroussin b...@freebsd.org wrote: On Fri, Jun 06, 2014 at 09:34:26AM -0500, Paul Schmehl wrote: --On June 6, 2014 at 10:51:04 AM +0200 Michael Gmelin gre...@freebsd.org wrote: On 06 Jun 2014, at 10:22, John Marino freebsd.cont...@marino.st wrote: On 6/6/2014 10:18, Alfred Perlstein wrote: Sure, but really a couple of lines to warn people and wave them towards next steps is probably advisable next time. Maybe we can alter the uname -a string to show the EOL so that every time the machine boots you see it on top of the MOTD. :) Of course, that won't help for the turn-on-and-forget servers with uptime measured in years... As a serious questions, where should such a you have X months/days remaining before server is EOL, update before then messages pop up? weekly cron messages sent to root? periodic/security/450-check_eol ?(info if 90 days left, error if past eol) EOL notification is not the problem. The problem is breaking ports at EOL. That's a special circumstance and begs for notification. This isn't rocket science. For at least two months now this notification has been popping up every time I work on ports. /!\ WARNING /!\ pkg_install EOL is scheduled for 2014-09-01. Please consider migrating to pkgng http://blogs.freebsdish.org/portmgr/2014/02/03/time-to-bid-farewell-to-t he-old-pkg_-tools/ If you do not want to see this message again set NO_WARNING_PKG_INSTALL_EOL=yes in your make.conf Do you think I would miss the 9/1 deadline? Not a chance. But the advance warning gives me time to plan the change when it's convenient for me. This change has me scrambling to adapt. Granted, it only took me a few minutes to figure out what to do, but not everyone has the background and experience to do that. Some will simply panic. Others will switch to Linux. That doesn't seem like a goal FreeBSD should support. The mental genius is me apparently (thanks for the kind words, btw) I'm responsible for both the pkg_install EOL message and for breaking ports tree with older make (btw you can recover with installing manually bmake). No offense was meant. I deliberately chose the subject to stimulate discussion, which it has obviously done. Yes it would have been a good idea to give a warning to the user about the fact that the ports tree won't be support long on after EOL of 8.3, given the ports tree will break again quite soon after EOL of 8.4 I should think about adding such a message right now (btw this is not that easy in the case we are talking about because I have no way to differentiate a fmake with support for :tl from a fmake without support for :tu same goes for :tu) hence it is hard to print a message. I fully understand this. Sometimes figuring out how to warn a user is complex and difficult. However, the decision to inform should not hinge on the difficulty of the implementation but on the criticality of the change. However, you can detect the RELEASE version and you do know the EOL date, so you could base detection on that. Pseudo warning triggered with every port install or upgrade: WARNING!!! 8.4 goes EOL on m/d/yy and ports will break. Be sure to plan an upgrade before EOL or, alternatively, use svn -rev to retain your current version of ports until you can successfully upgrade. Concerning breaking after 8.4 EOL it might be easier. Well, I'm glad you tipped me off to that since I'm presently upgrading to 8.4. That *might* have influenced me to go to 9 instead, had I known it before deciding. The reason why I haven't added a warning like I did for pkg_install is that: 1. it is hard to detect when to print the warning (more complicated that one can imagine first) 2. freebsd-update is already issueing a warning about EOL coming soon so I would have expected user to already know when EOL is coming and/or getting the info from freebsd-update. Again, this isn't an EOL issue. EOL is a fact of life. RELEASES go EOL all the time. They have for decades. What's different about this is that it broke ports. THAT should not be taken lightly and should require thorough thought about how to notify end users in a significant way that's not likely to be missed. The pkg_install message is a *perfect* way of notifying the end user. It can't be missed. And it nags you every time you install or upgrade a port. Something similar should have been done for the change to fmake, and certainly needs to be done before 8.4 goes EOL. I appreciate your willingness to engage on this point, because I think it's a critical issue that impacts a lot of users. Very few of those users will complain effectively or in the right forums. Some of them will simply give up and change OSes. That would be a shame. The issue wasn't that difficult for me to recover from, and I am proceeding with my work. Others may not be so fortunate. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't
libiconv problems
According to UPDATING, I should be able to do this to resolve issues with libiconv: pkg query %ro libiconv ports_to_update On my system, running 8.4 RELEASE with the old packaging system, this command doesn't do anything. I ran pkg_info to get a list of dependent apps and then piped that into xargs portmaster, but I got errors. # cat dependencies.txt | xargs portmaster === /var/db/pkg/Information does not exist === Aborting update === Killing background jobs Terminated Terminated Terminated Terminated Terminated Terminated Terminated Terminated Terminated Terminated Terminated === Exiting So how can I fix this problem without updating to the new pkg system? -- Paul Schmehl (pa...@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/infosecurity/ ___ 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: libiconv problems
--On June 6, 2014 at 12:46:09 PM -0500 Bryan Drewery bdrew...@freebsd.org wrote: On 6/6/14, 12:25 PM, Paul Schmehl wrote: According to UPDATING, I should be able to do this to resolve issues with libiconv: pkg query %ro libiconv ports_to_update On my system, running 8.4 RELEASE with the old packaging system, this command doesn't do anything. I ran pkg_info to get a list of dependent apps and then piped that into xargs portmaster, but I got errors. # cat dependencies.txt | xargs portmaster === /var/db/pkg/Information does not exist === Aborting update === Killing background jobs Terminated Terminated Terminated Terminated Terminated Terminated Terminated Terminated Terminated Terminated Terminated === Exiting So how can I fix this problem without updating to the new pkg system? You don't. UPDATING says: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv 8.4 not affected, according to the entry. All well and good, except for one problem: ls /usr/ports/devel/libiconv* ls: /usr/ports/devel/libiconv*: No such file or directory And yes my ports are current. -- Paul Schmehl (pa...@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/infosecurity/ ___ 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
Who was the mental genius
That decided it was a good idea to completely break ports to force people
to upgrade? You couldn't come up with a warning system instead of outright
breaking ports? The idiots are apparently running the asylum. {{sigh}}
--
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
___
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: Who was the mental genius
--On June 5, 2014 at 11:18:31 PM +0200 A.J. 'Fonz' van Werven
free...@skysmurf.nl wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system instead
of outright breaking ports? The idiots are apparently running the
asylum. {{sigh}}
It might help to know exactly what you're talking about... What is it that
broke?
The change to make that causes this when you run pkg commands or try to
build ports:
Unknown modifier 't'
It was done deliberately to break ports so that people would be forced to
upgrade to a supported version.
https://forums.freebsd.org/viewtopic.php?f=5t=46291
--
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
___
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: Who was the mental genius
--On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi m...@madpilot.net wrote:
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 A.J. 'Fonz' van Werven
free...@skysmurf.nl wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system instead
of outright breaking ports? The idiots are apparently running the
asylum. {{sigh}}
It might help to know exactly what you're talking about... What is it
that
broke?
The change to make that causes this when you run pkg commands or try to
build ports:
Unknown modifier 't'
It was done deliberately to break ports so that people would be forced
to upgrade to a supported version.
https://forums.freebsd.org/viewtopic.php?f=5t=46291
No it was not done deliberately
Newer freebsd version moved to a newer make utility, and support for the
old one has been dropped after support for all old releases containing
it was ceased.
So they dropped the support accidentally? Is this really the time to argue
semantics?
Which releases are supported and for how long is well known, and
published in here when a new release is published:
http://www.freebsd.org/security/security.html#sup
The updates are free, as in no payment needed. What's keeping you from
performing a binary update of the base system every year or so?
I have two hosts on the internet for which the backup system failed. I
didn't catch it right away, so now I'm several days behind on backups. I
need to install a new system, but it requires ports I don't yet have
installed. So now I have two options; upgrade with my fingers crossed and
hope it works or scramble to find some way to backup before I upgrade just
in case the upgrade fails.
Running such an old system as any of the unsupported releases is also
most probably exposing you to security vulnerabilities.
First of all, 8.3 is not an old system. Secondly, you used to be able to
run old systems for a long time after support was dropped without
encountering issues like this. Finally, I'm a port maintainer of a fair
number of ports, so FreeBSD isn't free for me. I put a lot of time into it.
When such a drastic change is made, it should be well advertised in advance
(think the pkgng announcement you get every time you install a port) and
not implemented in such a disruptive manner. It's clear from the forum
announcement that I linked to that I was not the only one caught by
surprise and that it didn't even work on supported versions when the change
was first implemented.
Sometimes to change things you need to break compatibility, the project
did wait till it was coherent with what was promised before doing this.
What you call the project is made up of people. SOMEONE should be
thinking through the impact on end users and helping to plan such major
transitions in a way that's least disruptive IF you want the system to
remain viable.
Perhaps this is part of the reason adoption of FreeBSD has dropped so
dramatically over the years. I'm retiring in 18 months. When I leave, the
last FreeBSD system goes with me. No one is even interested in learning it
any more. FreeBSD used to rule the web. Now it's Linux. There's a lesson
in there for those that are listening, but apparently the project is not.
Which is sad, because FreeBSD, IMNSHO, is a very good OS.
There's no need to respond to this. I'm just venting. And clearly my
opinion doesn't matter anyway.
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
___
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: Who was the mental genius
--On June 5, 2014 at 8:08:35 PM -0700 Alfred Perlstein alf...@freebsd.org
wrote:
On 6/5/14, 7:32 PM, Paul Schmehl wrote:
--On June 5, 2014 at 11:50:38 PM +0200 Guido Falsi m...@madpilot.net
wrote:
On 06/05/14 23:43, Paul Schmehl wrote:
--On June 5, 2014 at 11:18:31 PM +0200 A.J. 'Fonz' van Werven
free...@skysmurf.nl wrote:
Paul Schmehl wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system
instead
of outright breaking ports? The idiots are apparently running the
asylum. {{sigh}}
It might help to know exactly what you're talking about... What is it
that
broke?
The change to make that causes this when you run pkg commands or try to
build ports:
Unknown modifier 't'
It was done deliberately to break ports so that people would be forced
to upgrade to a supported version.
https://forums.freebsd.org/viewtopic.php?f=5t=46291
No it was not done deliberately
Newer freebsd version moved to a newer make utility, and support for the
old one has been dropped after support for all old releases containing
it was ceased.
So they dropped the support accidentally? Is this really the time to
argue semantics?
Which releases are supported and for how long is well known, and
published in here when a new release is published:
http://www.freebsd.org/security/security.html#sup
The updates are free, as in no payment needed. What's keeping you from
performing a binary update of the base system every year or so?
I have two hosts on the internet for which the backup system failed.
I didn't catch it right away, so now I'm several days behind on
backups. I need to install a new system, but it requires ports I
don't yet have installed. So now I have two options; upgrade with my
fingers crossed and hope it works or scramble to find some way to
backup before I upgrade just in case the upgrade fails.
Running such an old system as any of the unsupported releases is also
most probably exposing you to security vulnerabilities.
First of all, 8.3 is not an old system. Secondly, you used to be able
to run old systems for a long time after support was dropped without
encountering issues like this. Finally, I'm a port maintainer of a
fair number of ports, so FreeBSD isn't free for me. I put a lot of
time into it.
When such a drastic change is made, it should be well advertised in
advance (think the pkgng announcement you get every time you install a
port) and not implemented in such a disruptive manner. It's clear from
the forum announcement that I linked to that I was not the only one
caught by surprise and that it didn't even work on supported versions
when the change was first implemented.
Sometimes to change things you need to break compatibility, the project
did wait till it was coherent with what was promised before doing this.
What you call the project is made up of people. SOMEONE should be
thinking through the impact on end users and helping to plan such
major transitions in a way that's least disruptive IF you want the
system to remain viable.
Perhaps this is part of the reason adoption of FreeBSD has dropped so
dramatically over the years. I'm retiring in 18 months. When I
leave, the last FreeBSD system goes with me. No one is even
interested in learning it any more. FreeBSD used to rule the web.
Now it's Linux. There's a lesson in there for those that are
listening, but apparently the project is not. Which is sad, because
FreeBSD, IMNSHO, is a very good OS.
There's no need to respond to this. I'm just venting. And clearly my
opinion doesn't matter anyway.
I think your opinion matters.
I agree I would be rudely surprised by such a breakage myself. That said
we need to find a way to desupport things eventually.
Any ideas on what should have been done that can be done in a short
amount of code as possible? Perhaps there's some way to determine
between the old and new makes and just add some kind of target like:
# psuedo make(1) code:
.ifndef THIS_IS_NEW_MAKE
.BEGIN:
echo your system is running an unsupported version of FreeBSD the
last version to support this is r232423
echo please run svn update -r232423 to get a working ports tree as
of that date or upgrade to a more recent
echo freebsd release using freebsd-update [[insert link to
freebsd-update]]
exit 1
.endif
Something like that would have been more than adequate. As I pointed out,
the warning you get about pkgng and the 9/1/2014 deadline is perfect. It's
been there for a couple of months, and it pops up ever time you do a port.
If you miss that and don't convert, you don't have anyone but yourself to
blame.
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
Done with this port
I'm giving up x11-toolkits/iwidgets. Someone else can wrestle this thing into compliance with STAGE. I've beaten my head against that damn wall long enough. If no one takes it, it dies in June. Staging may kill a lot of ports. I'm not longer the maintainer for that one. -- 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 ___ 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: Done with this port
--On May 20, 2014 at 8:53:36 PM +0200 Matthias Andree mand...@freebsd.org wrote: Am 20.05.2014 18:49, schrieb Paul Schmehl: I'm giving up x11-toolkits/iwidgets. Someone else can wrestle this thing into compliance with STAGE. I've beaten my head against that damn wall long enough. If no one takes it, it dies in June. Staging may kill a lot of ports. I'm not longer the maintainer for that one. Paul, Thank you for maintaining the port thus far. However, I have just committed a port upgrade to convert it to staging (SVN revision 354666). Would you be willing to continue maintaining this port with this particular obstacle out of your way? Please let us know ASAP, and please Cc: me on your reply. Thanks. With some of my ports I have been really struggling trying to get staging working. I'd be very interested to see what you did, since it was apparently easy for you to do. I guess I'll keep maintainership for now. I'm retiring in about 18 months, so I may have to give all my ports up then. 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 ___ 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
staging
Is there a way to find out if a port is being used? Some of my ports are pretty old. No point in upgrading them if no one is using them. 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 ___ 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
Can't figure out github syntax
I'm working on a new port that's fetched from github. This works: MASTER_SITES= https://github.com/collectiveintel/cif-v1/releases/download/v1.0.2-FINAL/ DISTNAME= libcif-v1.0.2-FINAL But I cannot for the life of me figure out how to convert that to the more normal USE_GITHUB syntax. Is there a doc on the GITHUB syntax that explains it for dummies? -- 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 ___ 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: Can't figure out github syntax
--On February 28, 2014 at 11:21:24 PM +0200 Kozlov Sergey
kozlov.sergey@gmail.com wrote:
On 28.02.2014 20:43, Paul Schmehl wrote:
I'm working on a new port that's fetched from github.
This works:
MASTER_SITES=
https://github.com/collectiveintel/cif-v1/releases/download/v1.0.2-FINAL/
DISTNAME= libcif-v1.0.2-FINAL
But I cannot for the life of me figure out how to convert that to the
more normal USE_GITHUB syntax.
Is there a doc on the GITHUB syntax that explains it for dummies?
Hi!
Check out the (/usr/ports)/Mk/bsd.sites.mk file, It's pretty well
documented.
i wish that were true. It might be for developers, but it's not for me.
I think the right combination of GH_ACCOUNT, GH_PROJECT, GH_TAGNAME and
GH_COMMIT would do the trick.
I would think so too, however...
Here's my Makefile:
# cat Makefile
# $FreeBSD$
PORTNAME= cif
PORTVERSION=1.0.2
MASTER_SITES= GH GHC
CATEGORIES= www perl5
MAINTAINER= pa...@utdallas.edu
COMMENT=Collective intelligence framework tool
LICENSE=LGPL3
BUILD_DEPENDS= p5-Net-SSLeay=1.43:${PORTSDIR}/security/p5-Net-SSLeay \
p5-Config-Simple=4.59:${PORTSDIR}/devel/p5-Config-Simple \
p5-DateTime-Format-DateParse=0.05:${PORTSDIR}/devel/p5-DateTime-Format-DateParse
\
p5-Google-ProtocolBuffers=0.08:${PORTSDIR}/devel/p5-Google-ProtocolBuffers
\
p5-Regexp-Common=2.122:${PORTSDIR}/textproc/p5-Regexp-Common \
p5-URI=1.56:${PORTSDIR}/net/p5-URI \
p5-LWP-Protocol-https=6.02:${PORTSDIR}/www/p5-LWP-Protocol-https \
p5-Digest-SHA1=2.10:${PORTSDIR}/security/p5-Digest-SHA1 \
p5-Net-Patricia=1.16:${PORTSDIR}/net/p5-Net-Patricia \
p5-Module-Pluggable=3.8:${PORTSDIR}/devel/p5-Module-Pluggable \
p5-Try-Tiny=0.04:${PORTSDIR}/lang/p5-Try-Tiny \
p5-MIME-Base64=3.06:${PORTSDIR}/converters/p5-MIME-Base64 \
p5-Iodef-Pb-Simple=0.21:${PORTSDIR}/devel/p5-Iodef-Pb-Simple \
p5-Regexp-Common-net-CIDR=0.02:${PORTSDIR}/textproc/p5-Regexp-Common-net-CIDR
\
p5-Compress-Snappy=0.18:${PORTSDIR}/archivers/p5-Compress-Snappy \
p5-Log-Dispatch=2.32:${PORTSDIR}/devel/p5-Log-Dispatch \
p5-JSON-XS=3.0.0:${PORTSDIR}/converters/p5-JSON-XS
USE_GITHUB= yes
GH_ACCOUNT= collectiveintel
GH_PROJECT= cif-v1
GH_TAGNAME= libcif-v${PORTVERSION}-FINAL
GH_COMMIT= d86ca6c
#https://github.com/collectiveintel/cif-v1/releases/download/v1.0.2-FINAL/libcif-v1.0.2-FINAL.tar.gz
HAS_CONFIGURE= yes
CONFIGURE_ARGS= --prefix=${STAGEDIR}/${PREFIX}
.include bsd.port.mk
The commented out url is what I want to pull down. The TAGNAME does not do
that. If I call the url MASTER_SITES it works fine, but that's obviously
not the right way to do it.
I don't understand how to get these macros to do what I need.
Attempting to fetch
https://codeload.github.com/collectiveintel/cif-v1/legacy.tar.gz/libcif-v1.0.2-FINAL?dummy=/cif-1.0.2.tar.gz
fetch:
https://codeload.github.com/collectiveintel/cif-v1/legacy.tar.gz/libcif-v1.0.2-FINAL?dummy=/cif-1.0.2.tar.gz:
Not Found
= Attempting to fetch
http://codeload.github.com/collectiveintel/cif-v1/legacy.tar.gz/libcif-v1.0.2-FINAL?dummy=/cif-1.0.2.tar.gz
Obviously it's not descending into the releases/download folder to find the
tarball. The question is, why isn't it, and how do I get it to do that?
--
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
___
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: Can't figure out github syntax
--On February 28, 2014 at 4:02:16 PM -0600 Paul Schmehl
pschmehl_li...@tx.rr.com wrote:
--On February 28, 2014 at 11:21:24 PM +0200 Kozlov Sergey
kozlov.sergey@gmail.com wrote:
On 28.02.2014 20:43, Paul Schmehl wrote:
I'm working on a new port that's fetched from github.
This works:
MASTER_SITES=
https://github.com/collectiveintel/cif-v1/releases/download/v1.0.2-FINA
L/ DISTNAME= libcif-v1.0.2-FINAL
But I cannot for the life of me figure out how to convert that to the
more normal USE_GITHUB syntax.
Is there a doc on the GITHUB syntax that explains it for dummies?
Hi!
Check out the (/usr/ports)/Mk/bsd.sites.mk file, It's pretty well
documented.
i wish that were true. It might be for developers, but it's not for me.
I think the right combination of GH_ACCOUNT, GH_PROJECT, GH_TAGNAME and
GH_COMMIT would do the trick.
I would think so too, however...
Here's my Makefile:
# cat Makefile
# $FreeBSD$
PORTNAME= cif
PORTVERSION=1.0.2
MASTER_SITES= GH GHC
CATEGORIES= www perl5
MAINTAINER= pa...@utdallas.edu
COMMENT=Collective intelligence framework tool
LICENSE=LGPL3
BUILD_DEPENDS= p5-Net-SSLeay=1.43:${PORTSDIR}/security/p5-Net-SSLeay \
p5-Config-Simple=4.59:${PORTSDIR}/devel/p5-Config-Simple \
p5-DateTime-Format-DateParse=0.05:${PORTSDIR}/devel/p5-DateTime-Format-
DateParse \
p5-Google-ProtocolBuffers=0.08:${PORTSDIR}/devel/p5-Google-ProtocolBuff
ers \
p5-Regexp-Common=2.122:${PORTSDIR}/textproc/p5-Regexp-Common \
p5-URI=1.56:${PORTSDIR}/net/p5-URI \
p5-LWP-Protocol-https=6.02:${PORTSDIR}/www/p5-LWP-Protocol-https \
p5-Digest-SHA1=2.10:${PORTSDIR}/security/p5-Digest-SHA1 \
p5-Net-Patricia=1.16:${PORTSDIR}/net/p5-Net-Patricia \
p5-Module-Pluggable=3.8:${PORTSDIR}/devel/p5-Module-Pluggable \
p5-Try-Tiny=0.04:${PORTSDIR}/lang/p5-Try-Tiny \
p5-MIME-Base64=3.06:${PORTSDIR}/converters/p5-MIME-Base64 \
p5-Iodef-Pb-Simple=0.21:${PORTSDIR}/devel/p5-Iodef-Pb-Simple \
p5-Regexp-Common-net-CIDR=0.02:${PORTSDIR}/textproc/p5-Regexp-Common-ne
t-CIDR \
p5-Compress-Snappy=0.18:${PORTSDIR}/archivers/p5-Compress-Snappy \
p5-Log-Dispatch=2.32:${PORTSDIR}/devel/p5-Log-Dispatch \
p5-JSON-XS=3.0.0:${PORTSDIR}/converters/p5-JSON-XS
USE_GITHUB= yes
GH_ACCOUNT= collectiveintel
GH_PROJECT= cif-v1
GH_TAGNAME= libcif-v${PORTVERSION}-FINAL
GH_COMMIT= d86ca6c
# https://github.com/collectiveintel/cif-v1/releases/download/v1.0.2-FINAL
# /libcif-v1.0.2-FINAL.tar.gz
HAS_CONFIGURE= yes
CONFIGURE_ARGS= --prefix=${STAGEDIR}/${PREFIX}
.include bsd.port.mk
The commented out url is what I want to pull down. The TAGNAME does not
do that. If I call the url MASTER_SITES it works fine, but that's
obviously not the right way to do it.
I don't understand how to get these macros to do what I need.
Attempting to fetch
https://codeload.github.com/collectiveintel/cif-v1/legacy.tar.gz/libcif-v
1.0.2-FINAL?dummy=/cif-1.0.2.tar.gz
fetch:
https://codeload.github.com/collectiveintel/cif-v1/legacy.tar.gz/libcif-v
1.0.2-FINAL?dummy=/cif-1.0.2.tar.gz: Not Found
= Attempting to fetch
http://codeload.github.com/collectiveintel/cif-v1/legacy.tar.gz/libcif-v1
.0.2-FINAL?dummy=/cif-1.0.2.tar.gz
Obviously it's not descending into the releases/download folder to find
the tarball. The question is, why isn't it, and how do I get it to do
that?
So, I go to github, click on releases and click on tags. I find the
tagname I want -
v1.0.2-FINAL, which has the commit has of d86ca6c. I put that in my
Makefile and run make makesum. The system pulls down the
cif-v1.0.2-FINAL.tar.gz file. Not really what I want (I only want
libcif-v1.0.2-FINAL.tar.gz), but OK, I can work around that.
So I run make install, and what happens? can't cd to
/usr/ports/www/cif/work/collectiveintel-cif-v1-d86ca6c: No such file or
directory
WTF???
So I ls work:
ls work/
.extract_done.cif._usr_local.license-catalog.mk
.license-report .license_done.cif._usr_local
collectiveintel-cif-v1-ebd850d/
WTF?? Why is the commit hash different than the one I specified?
Ive run into this time and time again trying to build ports that use
GITHUB. I HATE it. Drives me batty. It at least doubles the time it
takes me to figure out how to get a damn port working.
I've considered just saying fuck it, you put your software on github, I
will no longer maintain the damn port.
Why is this so frickin' hard to do?
--
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
Package build failure
-sensor-0.8.0 = SHA256 Checksum OK for sguil-sensor-0.8.0.tar.gz. === ===phase: patch-depends === ===phase: patch === Patching for sguil-sensor-0.8.0 === Applying FreeBSD patches for sguil-sensor-0.8.0 === ===phase: build-depends === ===phase: lib-depends === sguil-sensor-0.8.0 depends on shared library: tls - not found ===Verifying install for tls in /usr/ports/devel/tcltls === Installing existing package /packages/All/tcltls-1.6_1.txz Installing tcltls-1.6_1...Installing tcl86-8.6.1... done done === Returning to build of sguil-sensor-0.8.0 Error: shared library tls does not exist *** [lib-depends] Error code 1 Stop in /usr/ports/security/sguil-sensor. === Cleaning for sguil-sensor-0.8.0 -- 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 ___ 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: STAGE problem
--On December 11, 2013 5:59:36 PM +0100 Michael Gmelin free...@grem.de wrote: On Wed, 11 Dec 2013 10:47:34 -0600 Paul Schmehl pschmehl_li...@tx.rr.com wrote: I'm working on updating the devel/liblognorm port. I've run into a problem that I believe is related to STAGE. When I run make install I get the following error: === Building package for liblognorm-1.0.0 Creating package /usr/ports/devel/liblognorm-update/liblognorm/work/liblognorm-1.0.0.tbz Registering depends: json-c-0.11 libestr-0.1.5. Creating bzip'd tar ball in '/usr/ports/devel/liblognorm-update/liblognorm/work/liblognorm-1.0.0.tbz' tar: lib/liblognorm.so.0: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 *** [do-package] Error code 1 Stop in /usr/ports/devel/liblognorm-update/liblognorm. liblognorm.so exists in the stagedir: /usr/ports/devel/liblognorm-update/liblognorm]# find . -name liblognorm.so ./work/liblognorm-1.0.0/src/.libs/liblognorm.so ./work/stage/usr/local/lib/liblognorm.so If I add NO_STAGE= yes to the Makefile, the port builds and installs fine. Why is stage appending the .0? How do I resolve this problem? (Obviously adding NO_STAGE= yes is not the answer!) What's in plist? Thanks. That was the problem. Should have thought of it myself. -- 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 ___ 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: NO_STAGE: Bump PORTREVISION ? Pr class 'change' or 'update' ?
--On October 24, 2013 10:21:25 AM +0200 John Marino freebsd.cont...@marino.st wrote: On 10/24/2013 10:05, Marco Steinbach wrote: Hi, the 'FAQ on PORTREVISION' discussion found at [1] seems to suggest, that enabling staging does not require a PORTREVISION bump. On the other hand, enabling staging seems to be a change in packaging, although from a users perspective the packaged files don't change. And a change in packaging is said to require a bump in PORTREVISION, according to the referenced thread. Are you referring to man pages? I believe those were getting added to the plist internally before, so the final difference in plist before and after staging is zero (if man pages are the only item in question). When enabling staging, is a maintainer supposed to bump PORTREVISION ? I don't see many PORTREVISION bumps as result of stage conversion (only). So I think not. I am working on a perfect example of why PORTREVISION MUST be bumped. I maintain security/barnyard2, which requires an update for reasons other than STAGE. As with any port, if I have to update it, I'm also going to comply with the latest architecture (as I did when OPTIONS changed), so I'm including a change to use STAGE. There is a slave port, security/barnyard2-sguil, which has STAGE= no in its Makefile. If I don't bump the PORTREVISION, that port will not update and subsequently will not build, because it's expecting the parent port NOT to be using STAGE. So I need to use PORTREVISION to force clients to pickup the change to STAGE in_both_ports or they won't work at all. I suspect that what's happened is that, without guidance, port maintainers are choosing both options for various reasons, which leads to inconsistency in the ports tree. ISTM a change as major as STAGE should REQUIRE that PORTREVISION be bumped. -- 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 ___ 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: FreeBSD Port: barnyard2-1.12
I don't maintain the prelude port. It looks like nobody does, since the maintainer address is po...@freebsd.org. I think if you submit the PR somebody will pick it up and commit it. --On October 24, 2013 12:00:43 AM +0200 Nicolas Edel nicolas.e...@gmail.com wrote: On Wed, Oct 23, 2013 at 5:55 PM, Nicolas Edel nicolas.e...@gmail.com wrote: Hi, Just to let you be aware of the following pb when using barnyard2 with prelude output enabled but without being able to do any reverse lookup for hostname. [...] (gdb) core barnyard2.core Core was generated by `barnyard2'. Program terminated with signal 11, Segmentation fault. [...] # 0 0x2812a091 in get_fqdn (analyzer=0x28e62f80, nodename=0xbfbfe250 monitor) at prelude-client.c:381 381 in prelude-client.c [New Thread 28804f00 (LWP 101446/barnyard2)] [New Thread 28804300 (LWP 100080/barnyard2)] (gdb) where # 0 0x2812a091 in get_fqdn (analyzer=0x28e62f80, nodename=0xbfbfe250 monitor) at prelude-client.c:381 [...] So I fetched the sources and have a look at the code. The bug is clearly in libprelude port since prelude-client.c belongs to it. Please let me know if you want me to send this bug (and a trivial patch) to (lib)prelude staff. Regards, :Nicolas ___ 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 Paul Schmehl (pa...@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ 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: Compiling sguil-server on Release 9.2 i386
--On October 21, 2013 7:48:59 AM +0200 John Marino
freebsd.cont...@marino.st wrote:
On 10/21/2013 00:47, Paul Schmehl wrote:
--On October 20, 2013 9:34:36 AM +0200 John Marino
It is not a mystery what is wrong.
The RUN_DEPENDS is being executed as a shell command, not a make
definition.
You're wrong. The RUN_DEPENDS does not have a shell command embedded in
it anywhere.
When you indent, it executes the command in the shell. Notice that only
make targets are indented.
I discovered this on my own while working on the port this morning.
That was never correct, and the new bmake makes this much
more obvious. Secondly, I'm pretty sure you can specify
databases/mysqltcl without having to execute a make command on that
port.
You're pretty sure? Rather than hard code a version, which would break
the port the moment mysqltcl was updated, I chose to use the existing
port version, which would work no matter what version was current on any
particular box.
Yes, I am sure. You can tell it that the port is the dependency
regardless of version. If you absolutely wanted to specify a file, you
can specify a different one that the file name doesn't change. Yes, you
can a RUN_DEPENDS without that line in ways that are robust.
The dependency is mysqltcl. That port installs two files in
${LOCALBASE}/lib/mysqltcl-${PORTVERSION}/. How do you reference those
files without using the portversion?
Thirdly, you use ${MYSQLTCL_VER}, but it's never defined.
Yes, and that is a problem. I noticed that last night when I was
looking at the port. Line 46 should read MYSQLTCL_VER= @${ECHO_CMD}
$$(${MYSQLTCL_CMDS}).
Again, completely unnecessary. Specify the *NON-INDENTED* RUN_DEPENDS
in a better way.
It looks like that port has changed, however, because it no longer
appends the version number to the name of the port, so I can probably
drop that entirely. I won't know until I test it.
Apparently line 46 was intended to define it but does not. Lastly, if
you were to use a shell command (which I highly discourage), it should
be something like this (not indented, and definitely not hardcoded to
${PORTSDIR}):
MYSQLT_VER!= cd ${.CURDIR}/../../databases/mysqltcl ${MAKE} -V
PORTVERSION
What do you suggest it be hardcoded to? ${PORTSDIR} can be set to
anything on an individual system. Using your construction forces it to
be in /usr/ports. Although that's the default, it's by no means
guaranteed that the ports tree will exist there on any given system.
That's why we use macros in Makefiles - to avoid forcing users to stick
to the default structure.
I just showed you. Replace ${PORTSDIR} with ${.CURDIR}/../../
I know you haven't believed a thing I've said so far, but using
${PORTSDIR} can break the build in specific configurations. And yes,
we've been replacing it with .CURDIR in other ports.
When I work on my ports I create a new directory ${PORTNAME}-update. Then
I svn the port into that directory, which creates a subdirectory named
${PORTNAME}. With ${.CURDIR}../../../ the build will not descend to
/usr/ports but to /usr/ports/security and the build will break. I fail to
see how that can be correct. If I build ports anywhere other than the
default location, the build will break.
Is this information documented somewhere? And how do I overcome this
obvious problem?
So that's like 4 or 5 errors right off the bat, problems that were
always present. I suspect the legacy make simply didn't define
RUN_DEPENDS and continued building, so mysqltcl was never specified in
the package.
Because MYSQLTCL_VER is never defined, I think the RUN_DEPENDS should
fail. It didn't. I can't explain why. (I've slept since I last worked
on that port.) I can assure you I tested the port with the option
enabled and it built and ran fine.
So you state previously that it *HAD* to be defined for RUN_DEPENDS to
work, and now state that it wasn't defined but RUN_DEPENDS did work?
Doubtful and easily verifiable. Find an old platform where it worked
and type make -V RUN_DEPENDS and see if mysqltcl is in the list. I
believe it simply wasn't defined which didn't prevent this build from
building (it was indented, remember?). I think the error was masked
with the previous version of make.
But I doubt seriously that has anything to do with the error that the OP
reported. It's probably related to the change to bmake, which I will
have to investigate, if I have to continue to define the port version
for mysqltcl. It looks like I might not have to any more.
I'll also have to update the port to use the new STAGE syntax, so this
will take a little while.
In the future, I would appreciate it if you adopt a less smug attitude
about somebody else's work. Or take over the port if you think you're
so much better. There's three sguil ports. You're welcome to take over
maintainership if you think you're God's gift to port building.
Sigh
I guess you still feel this way after what I just
Re: Compiling sguil-server on Release 9.2 i386
--On October 21, 2013 7:09:06 PM +0200 John Marino
freebsd.cont...@marino.st wrote:
On 10/21/2013 18:15, Paul Schmehl wrote:
--On October 21, 2013 7:48:59 AM +0200 John Marino
The dependency is mysqltcl. That port installs two files in
${LOCALBASE}/lib/mysqltcl-${PORTVERSION}/. How do you reference those
files without using the portversion?
Look at section 5.8.9 of the Porters Handbook:
http://www.freebsd.org/doc/en/books/porters-handbook/makefile-depend.html
Something like this should work:
RUN_DEPENDS+= mysqltcl3:${PORTSDIR}/databases/mysqltcl
No, it won't. You can't use that construction on libraries, which is what
mysqltcl is.
What do you think I am?
I haven't the foggiest idea. What you come across as is a guy who thinks
he knows everything and everyone else is stupid.
3. Do you really think I should do this for you? Or spoon-feed you? I
believe I gave you more than enough information to both understand the
problem and figure out the solution. that's how people learn.
No, you didn't. You provided the information in drips and drabs. It took
several emails, during which time I had already figured out the problem
myself before you posted what you could have posted initially.
As for your snarky do I want you to spoon-feed me, no thanks. I'd starve
to death waiting for you to feed me. You could have simply posted, in your
first reply, You cannot index commands under options. Remove the tabs.
Also, the ECHO line will probably generate a shell error anyway, so you're
going to have to find a way to resolve that. My suggestion would be to
hardcode the version number, since you can't approximate libraries.
It's not an attitude that makes me want to get to work on fixing the
problems.
How about pride in a job well done?
Again, I think you should accept this in the spirit it was given. If
you found it unpleasant, I'm sorry but that wasn't the intention.
How about I've always had pride in a job well done, and I resent you
implicating that I did not? My responses have been written the way they
were in the hope that YOU would learn something, but it's apparent you
haven't.
It's a moot point now. I've fixed the problems and updated the port to use
STAGE, and it's fixing to be sent in as a response to the PR.
--
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
___
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: Compiling sguil-server on Release 9.2 i386
--On October 20, 2013 9:34:36 AM +0200 John Marino
freebsd.cont...@marino.st wrote:
On 10/20/2013 03:49, Paul Schmehl wrote:
You should create a PR on sguil-server and document all this there and
request the maintainer fix it properly. Personally I don't think any
shell commands are needed at all, certainly not to specify a
RUN_DEPENDS. it's all messed up.
I'm the maintainer, and I can assure you I tested it thoroughly. The
port has built without error on many machines before this came up. I've
personally built and tested it numerous times.
With the MYSQL option set on? The default is off, so building the
default configuration numerous times would not have hit this.
Yes, of course it was set. I wouldn't submit a port without testing all
its options, and committers wouldn't commit a port that doesn't build with
any options set.
Nevertheless, I will take a look at what you've discussed and attempt to
determine what the problem is. It appears that something may have
changed in 9.2 that is causing the problem. Unfortunately I don't have
a 9.2 install, so I'll have to set one up before I can test it.
It is not a mystery what is wrong.
The RUN_DEPENDS is being executed as a shell command, not a make
definition.
You're wrong. The RUN_DEPENDS does not have a shell command embedded in it
anywhere.
That was never correct, and the new bmake makes this much
more obvious. Secondly, I'm pretty sure you can specify
databases/mysqltcl without having to execute a make command on that
port.
You're pretty sure? Rather than hard code a version, which would break the
port the moment mysqltcl was updated, I chose to use the existing port
version, which would work no matter what version was current on any
particular box.
Thirdly, you use ${MYSQLTCL_VER}, but it's never defined.
Yes, and that is a problem. I noticed that last night when I was looking
at the port. Line 46 should read MYSQLTCL_VER= @${ECHO_CMD}
$$(${MYSQLTCL_CMDS}).
It looks like that port has changed, however, because it no longer appends
the version number to the name of the port, so I can probably drop that
entirely. I won't know until I test it.
Apparently line 46 was intended to define it but does not. Lastly, if
you were to use a shell command (which I highly discourage), it should
be something like this (not indented, and definitely not hardcoded to
${PORTSDIR}):
MYSQLT_VER!= cd ${.CURDIR}/../../databases/mysqltcl ${MAKE} -V
PORTVERSION
What do you suggest it be hardcoded to? ${PORTSDIR} can be set to anything
on an individual system. Using your construction forces it to be in
/usr/ports. Although that's the default, it's by no means guaranteed that
the ports tree will exist there on any given system. That's why we use
macros in Makefiles - to avoid forcing users to stick to the default
structure.
So that's like 4 or 5 errors right off the bat, problems that were
always present. I suspect the legacy make simply didn't define
RUN_DEPENDS and continued building, so mysqltcl was never specified in
the package.
Because MYSQLTCL_VER is never defined, I think the RUN_DEPENDS should fail.
It didn't. I can't explain why. (I've slept since I last worked on that
port.) I can assure you I tested the port with the option enabled and it
built and ran fine.
But I doubt seriously that has anything to do with the error that the OP
reported. It's probably related to the change to bmake, which I will have
to investigate, if I have to continue to define the port version for
mysqltcl. It looks like I might not have to any more.
I'll also have to update the port to use the new STAGE syntax, so this will
take a little while.
In the future, I would appreciate it if you adopt a less smug attitude
about somebody else's work. Or take over the port if you think you're so
much better. There's three sguil ports. You're welcome to take over
maintainership if you think you're God's gift to port building.
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
___
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: Compiling sguil-server on Release 9.2 i386
--On October 19, 2013 4:37:58 PM +0200 John Marino
freebsd.cont...@marino.st wrote:
On 10/19/2013 16:32, s_gamm...@charter.net wrote:
Looks like that fixed it. It's building now.
Should the tab be removed before @${ECHO_CMD} $$(${MYSQLTCL_CMDS}) ?
No, I think that line is broken too, in at least two different ways.
The MYSQL option is busted. It doesn't appear to me that it was ever
tested; I can't see how it ever worked.
You should create a PR on sguil-server and document all this there and
request the maintainer fix it properly. Personally I don't think any
shell commands are needed at all, certainly not to specify a
RUN_DEPENDS. it's all messed up.
I'm the maintainer, and I can assure you I tested it thoroughly. The port
has built without error on many machines before this came up. I've
personally built and tested it numerous times.
Nevertheless, I will take a look at what you've discussed and attempt to
determine what the problem is. It appears that something may have changed
in 9.2 that is causing the problem. Unfortunately I don't have a 9.2
install, so I'll have to set one up before I can test it.
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
___
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: STAGE: explain man pages
--On October 9, 2013 8:44:55 PM +0100 Anton Shterenlikht me...@bris.ac.uk wrote: I'm getting: # make stage === Staging for urlview-0.9_7 === Generating temporary packing list /bin/sh ./mkinstalldirs /usr/ports/textproc/urlview/work/stage/usr/local/bin install -s -o root -g wheel -m 555 urlview /usr/ports/textproc/urlview/work/stage/usr/local/bin/urlview install -o root -g wheel -m 444 urlview.man /usr/local/man/man1/urlview.1 install -o root -g wheel -m 444 /usr/ports/textproc/urlview/work/urlview-0.9/sample.urlview /usr/ports/textproc/urlview/work/stage/usr/local/etc/urlview.conf.sample Compressing man pages # Note that the man page is not installed on stage. The Makefile has: PLIST_FILES=bin/urlview \ etc/urlview.conf.sample \ urlview.1 The last file is the man page. What am I doing wrong? You don't need to install or uninstall man pages. They're done automatically. In the Makefile, use MANx= name of man pages e.g MAN1= urlview.1 Remove the manpage from the pkg-plist file. 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 ___ 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: Explain staging
--On October 7, 2013 10:37:34 AM +0100 Anton Shterenlikht me...@bris.ac.uk wrote: Set DISTDIR in make.conf to for example /home/memyself/distfiles and move the existing distfiles there. There's no reasonable default for DISTDIR I think if it's assumed that fetch operates as non-root. -Kimmo sure, I can do /tmp/distfiles too. But that doesn't help with all the other failing targets. Then I might as well chown -R user:group /usr/ports and update the ports tree as an unprivileged user too. HOwever, security would suffer, I think. And, anyway, this would be a major change. If this were the case, it should be much better documented, I think. Absolutely correct. A change of this magnitude needs to be much better documented than it has been so far. 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 ___ 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
Suddenly STAGE appeared
Or did I miss the announcement? Is there a doc that explains STAGE and how to convert a port to the new system? Why STAGE was created? What it's purpose is? This is all very new to me, and I have 23 ports to worry about. -- 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 ___ 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: Suddenly STAGE appeared
--On October 4, 2013 4:35:57 PM +0200 Michael Gmelin free...@grem.de
wrote:
On Fri, 04 Oct 2013 09:22:25 -0500
Paul Schmehl pschmehl_li...@tx.rr.com wrote:
Or did I miss the announcement?
Is there a doc that explains STAGE and how to convert a port to the
new system? Why STAGE was created? What it's purpose is?
This is all very new to me, and I have 23 ports to worry about.
See
http://lists.freebsd.org/pipermail/freebsd-ports-announce/2013-October/00
0067.html
and the discussion here
http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086346.html
Now it make sense. I have a port that is failing to build on 10.0 because
of CLANG. I don't have a 10.0 install, and it builds fine with GCC. So I
updated the port to use USE_GCC= yes, and I was asked to convert the port
to use STAGE. Left me scratching my head, because this was all before the
announcement.
And I'm having problems building the port now - and wondering if I should
just abandon my ports because the new system is confusing to me. All this
transitional stuff is a lot to grasp when you've been building ports
successfully for a while and suddenly nothing works.
For example, make makeplist doesn't actually make a pkg-plist file on my
system.
# make makeplist
bin/sancp
etc/rc.d/sancp
etc/sancp.conf.dist
But no pkg-plist file is created.
WTH???
DOCS no longer build properly, and I have no clue why?
# make install
=== Building package for sancp-1.6.1_5
Creating package
/usr/ports/security/sancp-update/sancp/work/sancp-1.6.1_5.tbz
Registering depends:.
Creating bzip'd tar ball in
'/usr/ports/security/sancp-update/sancp/work/sancp-1.6.1_5.tbz'
tar: share/doc/sancp/CHANGES: Cannot stat: No such file or directory
tar: share/doc/sancp/INSTALL: Cannot stat: No such file or directory
tar: share/doc/sancp/ISSUES: Cannot stat: No such file or directory
tar: share/doc/sancp/README: Cannot stat: No such file or directory
tar: share/doc/sancp/SETUP: Cannot stat: No such file or directory
tar: share/doc/sancp/fields.LIST: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** [do-package] Error code 1
Stop in /usr/ports/security/sancp-update/sancp.
The Makefile has this:
PORTDOCS= CHANGES INSTALL ISSUES \
README SETUP fields.LIST
The docs are actually in ${WRKSRC}/doc, so I tried adding doc/ and
${WRKSRC}/doc, but neither worked. I tried adding %%PORTDOCS%%/docname to
pkg-plist, but that failed as well. So now I'm at a complete loss to know
how to get the DOCS to work.
If you're going to make changes to the ports system and expect us
non-programmers to successfully grasp how all the changes get implemented,
it would be very helpful to have a HOWTO page the explains the changes
required in understandable detail. The current page -
https://wiki.freebsd.org/ports/StageDir - is rather cryptic and open to
interpretation.
How do I list PORTDOCS so the build nows where to find them? Previously we
used .if !${NOPORTDOCS} and told INSTALL to descend into the doc directory
to fetch the docs. Then we changed to .if ${OPTIONS:MDOCS} and did the
same. Now Im told I don't need that section at all, but obviously,
without out, the build can't figure out where the docs are so it fails.
All of this should be anticipated and documented BEFORE these changes are
rolled out and we're required to implement them or you can expect lots of
frustration and people dropping ports.
I get that you're trying to do things in a better, more robust way, but
communication is key, and that communication has to be detailed and
understandable so us dummies can implement it.
--
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
___
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
NEED_ROOT
From my reading it appears that one of the goals of STAGE is to allow users
to build and install ports under their UID. Are the perms in /usr/ports
changing?
In testing the port that I'm working on, I find that I do not have rights
to write to /usr/ports/distfiles and I do not have rights to write to
${WORKDIR}. That pretty much precludes building the port unless your root.
No surprise there since the files in /usr/ports are owned by root:wheel.
So are the perms going to change? Is port building going to run setuid?
Or is this a vaporware?
--
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
___
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: [REL - head-i386-default][security/sancp] Failed for sancp-1.6.1_4 in build (fwd)
Thank you.
--On September 27, 2013 11:31:53 AM -0300 William Grzybowski
willia...@gmail.com wrote:
10.0 does not have gcc.
You need it to fix it to either respect ${CC} (in this case ${CXX}) or
use USE_GCC= in your port.
On Fri, Sep 27, 2013 at 11:26 AM, Paul Schmehl pa...@utdallas.edu wrote:
Did something change in 10.0? This port builds fine on my 8.3 box. I'm
at a loss to know how to fix a problem I can't reproduce.
Forwarded Message
Date: September 26, 2013 12:15:25 PM -0500
From: pkg-fall...@freebsd.org
To: pa...@utdallas.edu
Cc: pkg-fall...@freebsd.org
Subject: [REL - head-i386-default][security/sancp] Failed for
sancp-1.6.1_4 in build
You are receiving this mail as a port that you maintain
is failing to build on the FreeBSD package build server.
Please investigate the failure and submit a PR to fix
build.
Maintainer: pa...@utdallas.edu
Last committer: b...@freebsd.org
Ident: $FreeBSD: head/security/sancp/Makefile 327769 2013-09-20
22:55:24Z bapt $ Log URL:
http://beefy1.isc.freebsd.org/bulk/head-i386-default/2013-09-26_06h12m52
s/l ogs/sancp-1.6.1_4.log Build URL:
http://beefy1.isc.freebsd.org/bulk/head-i386-default/2013-09-26_06h12m52s
Log:
Building security/sancp
build started at Thu Sep 26 17:15:22 UTC 2013
port directory: /usr/ports/security/sancp
building for: FreeBSD head-i386-default-job-05 10.0-CURRENT FreeBSD
10.0-CURRENT i386 maintained by: pa...@utdallas.edu
Makefile ident: $FreeBSD: head/security/sancp/Makefile 327769
2013-09-20 22:55:24Z bapt $ Poudriere version: 3.1-pre
---Begin Environment---
UNAME_m=i386
UNAME_p=i386
OSVERSION=155
UNAME_v=FreeBSD 10.0-CURRENT
UNAME_r=10.0-CURRENT
BLOCKSIZE=K
MAIL=/var/mail/root
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local
/bi n:/root/bin STATUS=1
MASTERMNT=/usr/local/poudriere/data/build/head-i386-default/ref
PKG_EXT=txz
tpid=26384
POUDRIERE_BUILD_TYPE=bulk
NBPARALLEL=24
PKGNG=1
PKGNAME=sancp-1.6.1_4
PKG_DELETE=/usr/local/sbin/pkg-static delete -y -f
PKG_ADD=/usr/local/sbin/pkg-static add
PWD=/root
MASTERNAME=head-i386-default
USER=root
HOME=/root
POUDRIERE_VERSION=3.1-pre
LOCALBASE=/usr/local
PACKAGE_BUILDING=yes
PKG_VERSION=/poudriere/pkg-static version
---End Environment---
---Begin OPTIONS List---
---End OPTIONS List---
--CONFIGURE_ARGS--
--End CONFIGURE_ARGS--
--CONFIGURE_ENV--
TMPDIR=/tmp SHELL=/bin/sh CONFIG_SHELL=/bin/sh
--End CONFIGURE_ENV--
--MAKE_ENV--
TMPDIR=/tmp SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local
LOCALBASE=/usr/local LIBDIR=/usr/lib CC=cc CFLAGS=-O2 -pipe
-fno-strict-aliasing CPP=cpp CPPFLAGS= LDFLAGS= CXX=c++
CXXFLAGS=-O2 -pipe -fno-strict-aliasing MANPREFIX=/usr/local
BSD_INSTALL_PROGRAM=install -s -o root -g wheel -m 555
BSD_INSTALL_LIB=install -s -o root -g wheel -m 444
BSD_INSTALL_SCRIPT=install -o root -g wheel -m 555
BSD_INSTALL_DATA=install -o root -g wheel -m 444
BSD_INSTALL_MAN=install -o root -g wheel -m 444 --End MAKE_ENV--
--SUB_LIST--
PREFIX=/usr/local
LOCALBASE=/usr/local
DATADIR=/usr/local/share/sancp
DOCSDIR=/usr/local/share/doc/sancp
EXAMPLESDIR=/usr/local/share/examples/sancp
WWWDIR=/usr/local/www/sancp
ETCDIR=/usr/local/etc/sancp
--End SUB_LIST--
---Begin make.conf---
ARCH=i386
MACHINE=i386
MACHINE_ARCH=i386
USE_PACKAGE_DEPENDS=yes
BATCH=yes
WRKDIRPREFIX=/wrkdirs
PACKAGES=/packages
DISTDIR=/distfiles
/usr/local/etc/poudriere.d/make.conf
WITH_PKGNG=yes
NO_RESTRICTED=yes
DISABLE_MAKE_JOBS=yes
---End make.conf---
=== Cleaning for sancp-1.6.1_4
===phase: check-config
=== ===phase: pkg-depends
=== sancp-1.6.1_4 depends on file:
/usr/local/sbin/pkg - not found ===Verifying install for
/usr/local/sbin/pkg in
/usr/ports/ports-mgmt/pkg === Installing existing package
/packages/All/pkg-1.1.4_5.txz
Installing pkg-1.1.4_5... done
If you are upgrading from the old package format, first run:
# pkg2ng
=== Returning to build of sancp-1.6.1_4
=== ===phase: fetch-depends
=== ===phase: fetch
=== Fetching all distfiles required by
sancp-1.6.1_4 for building
=== ===phase: checksum
=== Fetching all distfiles required by
sancp-1.6.1_4 for building = SHA256 Checksum OK for
sancp-1.6.1-stable.tar.gz.
=== ===phase:
extract-depends
=== ===phase: extract
Question regarding github and multiple distribution files
I'm working on a port upgrade for security/afterglow. Previously the port was at Sourceforge. Now it's been moved to Github. Previously the port bundled all the extra' scripts and example files in the source tarball. Now they are three different sites on github. How do you translate multiple MASTER_SITES to github pulls? Should I just not bother and point to the scripts and examples in the pkg-message file? The afterglow site is here: https://github.com/zrlram/afterglow I can pull that down fine with the usual GH_?? macros. But how do I deal with the other two? http://github.com/zrlram/parsers https://github.com/zrlram/loganalysis Or do I just not bother? Or do I create two new ports? -- 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 ___ 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: [HEADS UP] Tcl/Tk moves to the USES framework
--On September 19, 2013 2:00:04 PM +0200 Pietro Cerutti g...@freebsd.org wrote: All, as of r327607 [1], Tcl/Tk ports can use the new USES framework, as described in [2]. We (tcltk@) could use your help to transition from the deprecated USE_TCL and USE_TK variables to the new framework. For this, I have set up a wiki page at [3] to help coordinate the efforts. There are currently 235 ports that need an update. If you happen to be the maintainer of one of these ports, please consider updating it and move the corresponding row from the Ports to convert to the Ports already converted table in the Wiki, or just send in a patch and ask tcltk@ do the job :) Thank you very much for your help! Pietro for tcltk@ [1] http://lists.freebsd.org/pipermail/svn-ports-all/2013-September/029743.ht ml [2] http://lists.freebsd.org/pipermail/svn-ports-all/2013-September/029745.ht ml [3] https://wiki.freebsd.org/UseTclTk If you're going to ask us port maintainers to do this sort of thing, it would be nice if you first put the file in /usr/ports/Mk/Uses. /usr/ports]# portsnap update Ports tree is already up to date. /usr/ports]# find /usr/ports/Mk/Uses -name tcl.mk /usr/ports]# ls /usr/ports/Mk/Uses/ ada.mk cmake.mk fmake.mk gmake.mk motif.mk perl5.mk readline.mk zenoss.mk bison.mk desktop-file-utils.mk fuse.mk iconv.mk ncurses.mk pkgconfig.mk shared-mime-info.mk charsetfix.mk display.mk gettext.mk imake.mk pathfix.mk qmail.mk shebangfix.mk -- 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 ___ 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
Strange problem with portmaster
I recently upgraded all the ports on a server, so I decided to run portmaster -r perl to make sure all the perl ports were up to date. I used portmaster -rfd perl and got the following error: /var/db/pkg/fd does not exist I googled a bit and found nothing. Then I thought, that's strange, fd was the second and third commands. So I ran: portmaster -r -f -d perl and I got /var/db/pkg/f does not exist Then I tried portmaster -rf -d perl and got /var/db/pkg/d does not exist I finally just ran portmaster -r perl, which worked of course. Apparently the -r switch doesn't want to see anything after except the port that's being recursively built? I didn't try portmaster -fd -r perl. Maybe I should have? -- Paul Schmehl (pa...@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/infosecurity/ ___ 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
Portmaster hangs on 9.1 Release
I'm updating machines, and the updates all work fine except a machine running 9.1 Release. On that machine, portmaster hangs. This is what I see: === Building for xorg-macros-1.17 === Creating a backup package for old version xorg-macros-1.16.1 I tried using -B to eliminate the backups, but then it hangs on Builiding. Anyone else seen this? Know of a solution? Did I miss something in UPDATING? -- 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 ___ 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: Portmaster hangs on 9.1 Release
--On June 14, 2013 11:13:25 AM -0500 Paul Schmehl pschmehl_li...@tx.rr.com wrote: I'm updating machines, and the updates all work fine except a machine running 9.1 Release. On that machine, portmaster hangs. This is what I see: === Building for xorg-macros-1.17 === Creating a backup package for old version xorg-macros-1.16.1 I tried using -B to eliminate the backups, but then it hangs on Builiding. Anyone else seen this? Know of a solution? Did I miss something in UPDATING? Never mind. I did miss something in UPDATING. Running make -C /usr/ports/ports-mgmt/portmaster build deinstall install clean fixed the problem. -- 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 ___ 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
I need help with git
I'm the maintainer for security/barnyard2. The software recently changed
so that all distros are pulled from github. The developers made new
commits, and now the port is broken, and I cannot figure out how to fix it.
Here's the relevant code from the Makefile:
PORTNAME= barnyard2
PORTVERSION=1.11
CATEGORIES= security
MAINTAINER= pa...@utdallas.edu
COMMENT=Interpreter for Snort unified2 binary output files
LICENSE=GPLv2
USE_GITHUB= yes
GH_ACCOUNT= firnsy
GH_PROJECT= ${PORTNAME}
GH_TAGNAME= master
GH_COMMIT= 4dfdc80
The master tagname apparently gets moved to the new commit every time the
developers commit changes. This is NOT what I want. I want the port to
stay at the release version until a new version is released.
I've tried everything I can think of to get this port to pull the commit I
want. It does not work. I've tried changing the tagname to v2-1.11,
v2-${PORTVERSION}, stable, dev-next, etc., etc. Nothing works.
Here's the git site: https://github.com/firnsy/barnyard2/commits/master
If I pull master, I get commit f57e464. That's not what I want. Why
doesn't this thing pull the commit I'm telling it to pull?
I'm so frustrated by this I'm about to drop this port. I do NOT want to
have to update the port every time the developers commit more code. That
is NOT how software should work.
Is there anyone who can tell me how to fix this problem so the port will
remain at the release version until the next version is released no matter
how many commits the developers make?
--
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
___
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: I need help with git
--On February 4, 2013 8:33:06 AM -0800 Micheas Herman m...@micheas.net wrote:
On Monday, February 4, 2013, Paul Schmehl wrote:
I'm the maintainer for security/barnyard2. The software recently
changed so that all distros are pulled from github. The developers made
new commits, and now the port is broken, and I cannot figure out how to
fix it.
Here's the relevant code from the Makefile:
PORTNAME= barnyard2
PORTVERSION= 1.11
CATEGORIES= security
MAINTAINER= pa...@utdallas.edu
COMMENT= Interpreter for Snort unified2 binary output files
LICENSE= GPLv2
USE_GITHUB= yes
GH_ACCOUNT= firnsy
GH_PROJECT= ${PORTNAME}
GH_TAGNAME= master
You need to change th GH_TAGNAME to the release you want if you go to the
repository on github and you can find the tags that the maintainers have
added to the project.
If you want a snapshot in time that is not tagged you could either
request the authors tag it, or fork it on github tag it yourself and put
your own account as the GH_ACCOUNT.
So now I have to maintain a git repository just to maintain my port? No
thanks. I'll abandon it first. This is volunteer work. I'm not going to
double my workload just because the system changed and doesn't work as
expected.
GH_COMMIT= 4dfdc80
Probably not needed if you specify a tag other than master.
According to /usr/ports/Mk/bsd.sites.mk, GH_COMMIT is mandatory.
# In order to use GitHub your port must define USE_GITHUB and the following
# variables:
#
# GH_ACCOUNT- account name of the GitHub user hosting the project
# default: not set, mandatory
#
# GH_PROJECT- name of the project on GitHub
# default: ${PORTNAME}
#
# GH_TAGNAME- name of the tag to download (master, 2.0.1, ...)
# default: ${DISTVERSION}
#
# GH_COMMIT - first 7 digits of the commit that generated GH_TAGNAME
# (man git-describe(1))
# default: not set, mandatory
#
Never mind. I finally figured it out. I had to change GH_TAGNAME to
v2-${PORTVERSION}. Now it pulls the commit for the release version as
desired.
--
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
___
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: I need help with git
--On February 4, 2013 5:36:02 PM +0100 Michael Gmelin free...@grem.de
wrote:
Hi Paul,
Could you revisit what I write to you about this a couple of months ago?
I just tried changing GH_TAGNAME to v2-1.11 in Makefile and it just
worked fine (by the way, that's what I suggested back then, you should
never depend on master, since it is a moving target)
USE_GITHUB= yes
GH_ACCOUNT= firnsy
GH_PROJECT= ${PORTNAME}
GH_TAGNAME= v2-1.11
GH_COMMIT= 4dfdc80
Are you sure there's nothing left in your build environment that stops
you from building the port successfully?
Somehow I missed your response. I figured it out before seeing your email
though, but thanks for providing the correct answer.
Cheers,
--
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
___
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: I need help with git
--On February 4, 2013 11:41:45 AM -0500 Greg Larkin glar...@freebsd.org
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/4/13 11:21 AM, Paul Schmehl wrote:
I'm the maintainer for security/barnyard2. The software recently
changed so that all distros are pulled from github. The developers
made new commits, and now the port is broken, and I cannot figure
out how to fix it.
Here's the relevant code from the Makefile:
PORTNAME= barnyard2 PORTVERSION=1.11 CATEGORIES=
security
MAINTAINER= pa...@utdallas.edu COMMENT=Interpreter for
Snort unified2 binary output files
LICENSE=GPLv2
USE_GITHUB= yes GH_ACCOUNT= firnsy GH_PROJECT=
${PORTNAME} GH_TAGNAME= master GH_COMMIT= 4dfdc80
The master tagname apparently gets moved to the new commit every
time the developers commit changes. This is NOT what I want. I
want the port to stay at the release version until a new version is
released.
I've tried everything I can think of to get this port to pull the
commit I want. It does not work. I've tried changing the tagname
to v2-1.11, v2-${PORTVERSION}, stable, dev-next, etc., etc.
Nothing works.
Here's the git site:
https://github.com/firnsy/barnyard2/commits/master
If I pull master, I get commit f57e464. That's not what I want.
Why doesn't this thing pull the commit I'm telling it to pull?
I'm so frustrated by this I'm about to drop this port. I do NOT
want to have to update the port every time the developers commit
more code. That is NOT how software should work.
Is there anyone who can tell me how to fix this problem so the port
will remain at the release version until the next version is
released no matter how many commits the developers make?
Hi Paul,
I just changed this line:
GH_TAGNAME= master
to this:
GH_TAGNAME= v2-1.11
and it worked fine.
Thanks, Greg. That is the correct answer.
--
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
___
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
Problems with GITHUB pulls
I maintain the security/barnyard2 port. It pulls the software from git,
which is the only place where it's available.
Here's the relevant portion of the port's Makefile:
USE_GITHUB= yes
GH_ACCOUNT= firnsy
GH_PROJECT= ${PORTNAME}
GH_TAGNAME= master
GH_COMMIT= 4dfdc80
The problem is, master's commit tag and md5 sum and size have changed. I
*could* update the port by changing the commit tag and the distino file,
but that's seems rather kludgy to me. The version hasn't changed. The
developers simply fixed some problems in the software and then bumped
master to the newer commit.
Is that really the correct way to handle software at git? If so, am I
going to be forced to update the port every time the developers make minor
changes to a version?
Is there a way for me to work around this problem so that the port version
remains at the stable commit until the version actually gets bumped?
GH_COMMIT is mandatory, so I can't leave that out. Yet the git tagname has
changed. What's the best way to handle this?
--
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
___
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
How to apply an svn diff
Once you've created an svn diff and submitted it using send-pr, how is the diff applied to update the port? I can't seem to figure this out from reading the svn docs. -- Paul Schmehl (pa...@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/infosecurity/ ___ 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: How to apply an svn diff
--On January 8, 2013 9:49:06 PM + Matthew Seaman matt...@freebsd.org wrote: On 08/01/2013 21:47, Paul Schmehl wrote: Once you've created an svn diff and submitted it using send-pr, how is the diff applied to update the port? I can't seem to figure this out from reading the svn docs. use patch(1) That worked. Thanks. 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 ___ 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: What is policy about auto-editing config files on port install / deinstall?
--On January 3, 2013 1:12:43 PM +0100 Fabian Keil
freebsd-lis...@fabiankeil.de wrote:
Scot Hetzel swhet...@gmail.com wrote:
On Wed, Jan 2, 2013 at 2:37 PM, Miroslav Lachman 000.f...@quip.cz
wrote:
Is somewhere written policy or portmgr recommendation about ports
behavior on install / deinstall?
My impression is that every maintainer has her own undocumented
policy although the approaches taken could be grouped into a few
categories.
This is likely true, however the Porters Handbook describes the preferred
methods for doing things.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html
I am talking about some ports doing nasty things.
Some ports are stopping services on deinstall, some not.
I prefer that when a port is uninstalled, that the service is stopped.
According to the Porters Handbook, this is not the preferred method:
6.24.1 Stopping Services at Deinstall
It is possible to have a service stopped automatically as part of the
deinstall routine. We advise using this feature only when it is absolutely
necessary to stop a service before its files go away. Usually, it is up to
the administrator's discretion to decide, whether to stop the service on
deinstall or not. Also note this affects upgrades, too.
A line like this goes in the pkg-plist:
@stopdaemon doormand
The argument must match the content of USE_RC_SUBR variable.
Some ports are editing my config files on deinstall, so even on
upgrade procedure I must check if port did some changes before I can
restart target daemon.
Most ports don't edit the config files as they install the original
config file to a different name.
In my opinion ports shouldn't mess with user-modified files unless
they properly parse them and can be expected not to break them.
The Porters Handbooks explicitly states this:
7.3 Configuration Files
If your port installs configuration files to PREFIX/etc (or elsewhere) do
not simply list them in the pkg-plist. That will cause pkg_delete(1) to
remove the files carefully edited by the user, and a re-installation will
wipe them out.
Instead, install sample file(s) with a filename.sample suffix. Then copy
the sample file to the real configuration file name, if it does not already
exist. On deinstall delete the configuration file, but only if it is
identical to the .sample file. You need to handle this both in the port
Makefile, and in the pkg-plist (for installation from the package).
Example of the Makefile part:
post-install:
@if [ ! -f ${PREFIX}/etc/orbit.conf ]; then \
${CP} -p ${PREFIX}/etc/orbit.conf.sample
${PREFIX}/etc/orbit.conf ; \
fi
For each configuration file, create the following three lines in pkg-plist:
@unexec if cmp -s %D/etc/orbit.conf.sample %D/etc/orbit.conf; then rm -f
%D/etc/orbit.conf; fi
etc/orbit.conf.sample
@exec if [ ! -f %D/etc/orbit.conf ] ; then cp -p %D/%F %B/orbit.conf; fi
The order of these lines is important. On deinstallation, the sample file
is compared to the actual configuration file. If these files are identical,
no changes have been made by the user and the actual file can be safely
deleted. Because the sample file must still exist for the comparison, the
@unexec line comes before the sample configuration file name. On
installation, if an actual configuration file is not already present, the
sample file is copied to the actual file. The sample file must be present
before it can be copied, so the @exec line comes after the sample
configuration file name.
To debug any issues, temporarily remove the -s flag to cmp(1) for more
output.
See pkg_create(1) for more information on %D and related substitution
markers.
If there is a very good reason not to install a working configuration file
by default, leave the @exec line out of pkg-plist and add a message
pointing out that the user must copy and edit the file before the software
will work.
And even then I don't think it should be done automatically without
user interaction.
I believe that's currently up to the maintainer as well, though.
Not if they are properly following the Porters Handbook and the committers
are verifying that they are doing so.
As with any system where humans are involved, the process is flawed.
However, there is a right way to do things. Refer to the Porters Handbook
and follow its instructions as much as is humanly possible.
--
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
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
rc.subr questions
I'm trying to figure out how to get an rc.subr script to start and stop a script. This works from the commandline (to start it): tclsh /usr/local/bin/dir/script -D -c /usr/local/etc/conffile I've tried various combinations of: command_interpreter argument_precmd command_args but I keep getting this error: unknown directive '/usr/local/bin/sguil-sensor/pads_agent.tcl' Doesn't matter if I make that string the val for command and don't use command_interpreter or do use command_interpreter. I've read the man page over and over, but I'm clueless as to how to use run_rc_script, which I *think* is the right way to call this script. -- 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 ___ 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: rc.subr questions
--On December 6, 2012 8:45:50 PM + Chris Rees cr...@freebsd.org wrote:
[CC rc@]
On 6 December 2012 20:36, Paul Schmehl pschmehl_li...@tx.rr.com wrote:
I'm trying to figure out how to get an rc.subr script to start and stop a
script.
This works from the commandline (to start it):
tclsh /usr/local/bin/dir/script -D -c /usr/local/etc/conffile
I've tried various combinations of:
command_interpreter
argument_precmd
command_args
but I keep getting this error:
unknown directive '/usr/local/bin/sguil-sensor/pads_agent.tcl'
Doesn't matter if I make that string the val for command and don't use
command_interpreter or do use command_interpreter.
I've read the man page over and over, but I'm clueless as to how to use
run_rc_script, which I *think* is the right way to call this script.
Make the script executable
It is.
, put a shebang in; #!/usr/bin/env tclsh
Here's the current script's starting lines:
#!/bin/sh
# Run tcl from users PATH \
exec tclsh $0 $@
# !/bin/sh
. /etc/rc.subr
name=tclshexample
rcvar=tclshexample_enable
load_rc_config $name
: ${tclshexample_enable=YES}
command=/usr/local/bin/dir/script
command_interpreter=tclsh
command_args=-D -c /usr/local/etc/conffile
run_rc_command $@
http://www.bayofrum.net/~crees/scratch/tclshexample
Would be much easier if you were to provide specifics or the actual
script :)
Chris
Here's the rc script I'm working on.
. /etc/rc.subr
load_rc_config pads_agent
#set defaults
pads_agent_enable=${pads_agent_enable:-NO}
pads_agent_conf=${pads_agent_conf:-/usr/local/etc/sguil-sensor/pads_agent.conf}
pads_agent_flags=${pads_agent_flags}:--D -c ${pads_agent_conf}
name=pads_agent
rcvar=pads_agent_enable
command=/usr/local/bin/sguil-sensor/pads_agent.tcl
command_interpreter=tclsh
command_args=${pads_agent_flags}
run_rc_command $@
Here's the error I'm getting when I run start:
/usr/local/etc/rc.d/pads_agent: WARNING: $command_interpreter tclsh !=
/bin/sh
Starting pads_agent.
/usr/local/etc/rc.d/pads_agent: WARNING: $command_interpreter tclsh !=
/bin/sh
/usr/local/etc/rc.d/pads_agent: unknown directive
'/usr/local/bin/sguil-sensor/pads_agent.tcl'.
Usage: /usr/local/etc/rc.d/pads_agent
[fast|force|one|quiet](start|stop|restart|rcvar|status|poll)
/usr/local/etc/rc.d/pads_agent: WARNING: failed to start pads_agent
I tried changing the interpreter to /bin/sh but I got the same error.
Here's the perms on the script:
# ls -lsa /usr/local/bin/sguil-sensor/pads_agent.tcl
12 -r-xr-xr-x 1 root wheel 11662 Dec 6 18:31
/usr/local/bin/sguil-sensor/pads_agent.tcl
--
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
___
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: rc.subr questions
--On December 6, 2012 9:30:04 PM + Chris Rees cr...@freebsd.org wrote:
On 6 December 2012 21:10, Paul Schmehl pschmehl_li...@tx.rr.com wrote:
--On December 6, 2012 8:45:50 PM + Chris Rees cr...@freebsd.org
wrote:
[CC rc@]
On 6 December 2012 20:36, Paul Schmehl pschmehl_li...@tx.rr.com wrote:
I'm trying to figure out how to get an rc.subr script to start and
stop a script.
This works from the commandline (to start it):
tclsh /usr/local/bin/dir/script -D -c /usr/local/etc/conffile
I've tried various combinations of:
command_interpreter
argument_precmd
command_args
but I keep getting this error:
unknown directive '/usr/local/bin/sguil-sensor/pads_agent.tcl'
Doesn't matter if I make that string the val for command and don't use
command_interpreter or do use command_interpreter.
I've read the man page over and over, but I'm clueless as to how to use
run_rc_script, which I *think* is the right way to call this script.
Make the script executable
It is.
, put a shebang in; #!/usr/bin/env tclsh
Here's the current script's starting lines:
# !/bin/sh
# Run tcl from users PATH \
exec tclsh $0 $@
# !/bin/sh
. /etc/rc.subr
name=tclshexample
rcvar=tclshexample_enable
load_rc_config $name
: ${tclshexample_enable=YES}
command=/usr/local/bin/dir/script
command_interpreter=tclsh
command_args=-D -c /usr/local/etc/conffile
run_rc_command $@
http://www.bayofrum.net/~crees/scratch/tclshexample
Would be much easier if you were to provide specifics or the actual
script :)
Chris
Here's the rc script I'm working on.
. /etc/rc.subr
load_rc_config pads_agent
# set defaults
pads_agent_enable=${pads_agent_enable:-NO}
pads_agent_conf=${pads_agent_conf:-/usr/local/etc/sguil-sensor/pads_age
nt.conf} pads_agent_flags=${pads_agent_flags}:--D -c
${pads_agent_conf}
name=pads_agent
rcvar=pads_agent_enable
command=/usr/local/bin/sguil-sensor/pads_agent.tcl
command_interpreter=tclsh
command_args=${pads_agent_flags}
run_rc_command $@
Here's the error I'm getting when I run start:
/usr/local/etc/rc.d/pads_agent: WARNING: $command_interpreter tclsh !=
/bin/sh
Starting pads_agent.
/usr/local/etc/rc.d/pads_agent: WARNING: $command_interpreter tclsh !=
/bin/sh
/usr/local/etc/rc.d/pads_agent: unknown directive
'/usr/local/bin/sguil-sensor/pads_agent.tcl'.
Usage: /usr/local/etc/rc.d/pads_agent
[fast|force|one|quiet](start|stop|restart|rcvar|status|poll)
/usr/local/etc/rc.d/pads_agent: WARNING: failed to start pads_agent
I tried changing the interpreter to /bin/sh but I got the same error.
Here's the perms on the script:
# ls -lsa /usr/local/bin/sguil-sensor/pads_agent.tcl
12 -r-xr-xr-x 1 root wheel 11662 Dec 6 18:31
/usr/local/bin/sguil-sensor/pads_agent.tcl
The problem is I think that the idiomatic tclsh syntax is to use the
# !/bin/sh shebang followed by some compat stuff... which doesn't play
nicely with rc's idea of how scripts should look.
If instead we use procname, that should work better.
http://www.bayofrum.net/~crees/scratch/tclshexample2
Does your tclsh script daemonise?
It's supposed to, but it fails. Let's cease this discussion for now while
I do some troubleshooting. I think I have bigger problems than just the
rc.subr stuff, and I don't want to waste any more of your time.
--
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
___
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
Dealing with options in dependent ports
I'm working on a port that has an option for a build_depends on another port. If that option is selected, the dependent port MUST be built with an option that is not selected by default. Is there a way to either force that option to be selected in the dependent port? Or, failing that, is it possible to pop up a message warning the installer that they must select that option before building the dependent port or, if they've already installed it without the option, they must deinstall and reinstall after selecting that option? -- 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 ___ 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: Dealing with options in dependent ports
--On November 30, 2012 4:47:40 PM +0100 Thierry Thomas thie...@freebsd.org wrote: Hello, Le ven 30 nov 12 à 16:36:32 +0100, Paul Schmehl pschmehl_li...@tx.rr.com écrivait : I'm working on a port that has an option for a build_depends on another port. If that option is selected, the dependent port MUST be built with an option that is not selected by default. Is there a way to either force that option to be selected in the dependent port? Or, failing that, is it possible to pop up a message warning the installer that they must select that option before building the dependent port or, if they've already installed it without the option, they must deinstall and reinstall after selecting that option? I'd suggest to make a slave port where you force the required option. However, to enforce the right dependency, this option have to produce a different plist. Thanks. I think that's probably the right answer. -- 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 ___ 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: Dealing with options in dependent ports
--On November 30, 2012 7:07:20 PM +0100 Alberto Villa avi...@freebsd.org
wrote:
On Fri, Nov 30, 2012 at 4:47 PM, Thierry Thomas thie...@freebsd.org
wrote:
However, to enforce the right dependency, this option have to produce a
different plist.
Really? Isn't enough to depend on the package name instead of a file?
No. The dependency installs files that are not otherwise installed, so the
pkg-plist has to reflect that. Here's how I did it in the port I just
created a slave for.
Created this section in the main port's Makefile:
.if defined(SLAVE)
OPTIONS_DEFINE+=BROCCOLI
OPTIONS_DEFAULT+= BROCCOLI
BROCCOLI_DESC= Build support for libbroccoli communications
.endif
This adds the option and enforces it being selected if you install the
slave port.
Then created this section in the main port's Makefile:
.if ${PORT_OPTIONS:MBROCCOLI}
PLIST_SUB+= BROCCOLI=
pre-configure:
(cd ${WRKSRC}/aux/broccoli ./configure)
pre-build:
(cd ${WRKSRC}/aux/broccoli ${MAKE})
post-build:
patch ${BUILD_WRKSRC}/cmake_install.cmake ${FILESDIR}/broccoli.patch
.else
PLIST_SUB+= BROCCOLI=@comment
.endif
The PLIST_SUB section allows you to add files to the pkg-plist that are
provisional, based on the install of the slave port.
Then the pkg_plist sub has the files included with the macro:
%%BROCCOLI%%include/broccoli.h
%%BROCCOLI%%lib/libbinpac.a
%%BROCCOLI%%lib/libbroccoli.a
%%BROCCOLI%%lib/libbroccoli.so
%%BROCCOLI%%lib/libbroccoli.so.5
%%BROCCOLI%%lib/libbroccoli.so.5.1.0
Those only get removed if the option was selected, so deinstall won't throw
errors if you install the main port without that option.
--
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
___
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: FreeBSD ports you maintain which are out of date
--On November 28, 2012 11:36:26 AM +1030 Shane Ambler free...@shaneware.biz wrote: On 28/11/2012 09:45, Kevin Oberman wrote: On Tue, Nov 27, 2012 at 8:12 AM, Radim Kolar h...@filez.com wrote: can be this daily spam turned off? i emailed there portsc...@portscout.freebsd.org but message was not delivered It's not spam, but a very useful service. I you don't work on any ports, you should be able to filter it very easily with procmail or your mail reader. Probably more to the point is that it shouldn't get sent to the ports mailing list - just to port maintainers. Did you ever think that sending it to the list might motivate someone else to take over the port? There's a reason ports get out of date. One of the reasons is because the port maintainer has lost interest or no longer has the time. If people on the list see it, someone who is motivated might update the port and end up being its new maintainer. -- 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 ___ 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
