PHP upgrade through port
Dear list, Currently I use php52-5.2.17_8 but want to upgrade to php52-5.3.xxx through the ports. Can somebody tell me how I can force portupgrade to do so? thanks, Jos Chrispijn -- Artificial intelligence is no match for natural stupidity... ___ 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: PHP upgrade through port
On 13/05/2012 09:18, Jos Chrispijn wrote: Currently I use php52-5.2.17_8 but want to upgrade to php52-5.3.xxx through the ports. Can somebody tell me how I can force portupgrade to do so? Basically you should delete any php52 or pecl ports, and anything that depends on them. Then install the php53 equivalents, reinstall the pecl modules and finally reinstall your php-based applications. As ever, make sure you have good backups before starting this procedure. So: # pkg_info -IX '^(php5|pecl)' /tmp/php-modules # pkg_delete -rX '^php5' 21 /tmp/php-deletion-log You might also want to save the output of 'pecl list' (if any) and 'pear list' if pecl and pear are installed on your system. Force the correct base version of php to be installed: # portmaster lang/php5 Reinstall any ported PHP applications, eg phpMyAdmin: # portmaster databases/phpmyadmin (etc., etc. for all the apps you had installed: check /tmp/php-deletion-log for details. This should install any necessary dependencies.) Finally, compare what you just installed with the record of what you previously installed to fix up any discrepancies, eg. if you have PHP applications installed from non-ports sources. There isn't an exact one-to-one correspondence between php52-* and php5-* ports (as I recall), since some functions have been moved into the PHP core, or shifted between different modules or moved to pear- or pecl- modules. However, those are generally the exceptions: if you can't find the exact equivalent php53 module, then (a) try the application without, (b) check the documentation on www.php.net for clues and finally (c) look for equivalent pear- or pecl- modules. Any PHP application installed from ports should automatically install everything it needs through the ports dependency mechanism. Also, if you use eAccelerator or similar, be sure to reinstall it after upgrading PHP. Note: the lang/php5 port is the correct port for php-5.3.x at the time of writing, but that port is very soon going to switch to providing php-5.4.x, and you would need to switch to lang/php53 if you don't want to go through yet another upgrade. Note 2: beware of the common problem with ordering of extension loadable modules in /usr/local/etc/php/extensions.ini -- some php modules depend on others; unfortunately there's no good way of controlling the order the modules are listed in extensions.ini to account for this. If php crashes on startup, swapping lines around in that file may well be the solution. It's been discussed many times on this list and freebsd-questions@..., so check the archives in case of difficulty. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: PHP upgrade through port
Hi Matthew, Thanks for your reply. For some reason that didn't work completely; must be because I am rather a newbie on this. Now I removed php5.2 all together from my FreeBSD server (including all related programs). If I now want to install php 5.3, how do I install the extensions as there is no php53-extensions? Or should I use the php52-extensions instead? regards, Jos Matthew Seaman: On 13/05/2012 09:18, Jos Chrispijn wrote: Currently I use php52-5.2.17_8 but want to upgrade to php52-5.3.xxx through the ports. Can somebody tell me how I can force portupgrade to do so? Basically you should delete any php52 or pecl ports, and anything that depends on them. Then install the php53 equivalents, reinstall the pecl modules and finally reinstall your php-based applications. As ever, make sure you have good backups before starting this procedure. So: # pkg_info -IX '^(php5|pecl)' /tmp/php-modules # pkg_delete -rX '^php5' 21 /tmp/php-deletion-log You might also want to save the output of 'pecl list' (if any) and 'pear list' if pecl and pear are installed on your system. Force the correct base version of php to be installed: # portmaster lang/php5 Reinstall any ported PHP applications, eg phpMyAdmin: # portmaster databases/phpmyadmin (etc., etc. for all the apps you had installed: check /tmp/php-deletion-log for details. This should install any necessary dependencies.) Finally, compare what you just installed with the record of what you previously installed to fix up any discrepancies, eg. if you have PHP applications installed from non-ports sources. There isn't an exact one-to-one correspondence between php52-* and php5-* ports (as I recall), since some functions have been moved into the PHP core, or shifted between different modules or moved to pear- or pecl- modules. However, those are generally the exceptions: if you can't find the exact equivalent php53 module, then (a) try the application without, (b) check the documentation on www.php.net for clues and finally (c) look for equivalent pear- or pecl- modules. Any PHP application installed from ports should automatically install everything it needs through the ports dependency mechanism. Also, if you use eAccelerator or similar, be sure to reinstall it after upgrading PHP. Note: the lang/php5 port is the correct port for php-5.3.x at the time of writing, but that port is very soon going to switch to providing php-5.4.x, and you would need to switch to lang/php53 if you don't want to go through yet another upgrade. Note 2: beware of the common problem with ordering of extension loadable modules in /usr/local/etc/php/extensions.ini -- some php modules depend on others; unfortunately there's no good way of controlling the order the modules are listed in extensions.ini to account for this. If php crashes on startup, swapping lines around in that file may well be the solution. It's been discussed many times on this list and freebsd-questions@..., so check the archives in case of difficulty. Cheers, Matthew ___ 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: problem running pkg_delete
On 12-5-2012 20:24, Robert Huff wrote: Suddenly I'm getting: pkg_delete: the package info for package Source is corrupt Any ideas? Can you provide the output of: grep -E '@(unexec|exec).*Source' /var/db/pkg/*/+CONTENTS -- Mel ___ 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: PHP upgrade through port
On 13/05/2012 12:47, Jos Chrispijn wrote: If I now want to install php 5.3, how do I install the extensions as there is no php53-extensions? Or should I use the php52-extensions instead? No -- use lang/php5-extensions. Like I said, anything with a php5- prefix is currently for php-5.3.x, however this will soon change so that php5- will mean php-5.4.x and to get php-5.3.x you'll need ports with a php53- prefix. But that hasn't happened yet, even though there are already some php53- ports in the tree (but not enabled yet). Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: PHP upgrade through port | SOLVED
Ok, solved; overlooked the /php5-extensions port. regards, Jos Chrispijn Jos Chrispijn: Hi Matthew, Thanks for your reply. For some reason that didn't work completely; must be because I am rather a newbie on this. Now I removed php5.2 all together from my FreeBSD server (including all related programs). If I now want to install php 5.3, how do I install the extensions as there is no php53-extensions? Or should I use the php52-extensions instead? regards, Jos Matthew Seaman: On 13/05/2012 09:18, Jos Chrispijn wrote: Currently I use php52-5.2.17_8 but want to upgrade to php52-5.3.xxx through the ports. Can somebody tell me how I can force portupgrade to do so? Basically you should delete any php52 or pecl ports, and anything that depends on them. Then install the php53 equivalents, reinstall the pecl modules and finally reinstall your php-based applications. As ever, make sure you have good backups before starting this procedure. So: # pkg_info -IX '^(php5|pecl)' /tmp/php-modules # pkg_delete -rX '^php5' 21 /tmp/php-deletion-log You might also want to save the output of 'pecl list' (if any) and 'pear list' if pecl and pear are installed on your system. Force the correct base version of php to be installed: # portmaster lang/php5 Reinstall any ported PHP applications, eg phpMyAdmin: # portmaster databases/phpmyadmin (etc., etc. for all the apps you had installed: check /tmp/php-deletion-log for details. This should install any necessary dependencies.) Finally, compare what you just installed with the record of what you previously installed to fix up any discrepancies, eg. if you have PHP applications installed from non-ports sources. There isn't an exact one-to-one correspondence between php52-* and php5-* ports (as I recall), since some functions have been moved into the PHP core, or shifted between different modules or moved to pear- or pecl- modules. However, those are generally the exceptions: if you can't find the exact equivalent php53 module, then (a) try the application without, (b) check the documentation on www.php.net for clues and finally (c) look for equivalent pear- or pecl- modules. Any PHP application installed from ports should automatically install everything it needs through the ports dependency mechanism. Also, if you use eAccelerator or similar, be sure to reinstall it after upgrading PHP. Note: the lang/php5 port is the correct port for php-5.3.x at the time of writing, but that port is very soon going to switch to providing php-5.4.x, and you would need to switch to lang/php53 if you don't want to go through yet another upgrade. Note 2: beware of the common problem with ordering of extension loadable modules in /usr/local/etc/php/extensions.ini -- some php modules depend on others; unfortunately there's no good way of controlling the order the modules are listed in extensions.ini to account for this. If php crashes on startup, swapping lines around in that file may well be the solution. It's been discussed many times on this list and freebsd-questions@..., so check the archives in case of difficulty. Cheers, Matthew ___ 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: PHP upgrade through port
On Sun, 13 May 2012 13:47:39 +0200 Jos Chrispijn articulated: Matthew Seaman: On 13/05/2012 09:18, Jos Chrispijn wrote: Currently I use php52-5.2.17_8 but want to upgrade to php52-5.3.xxx through the ports. Can somebody tell me how I can force portupgrade to do so? Basically you should delete any php52 or pecl ports, and anything that depends on them. Then install the php53 equivalents, reinstall the pecl modules and finally reinstall your php-based applications. As ever, make sure you have good backups before starting this procedure. So: # pkg_info -IX '^(php5|pecl)' /tmp/php-modules # pkg_delete -rX '^php5' 21 /tmp/php-deletion-log You might also want to save the output of 'pecl list' (if any) and 'pear list' if pecl and pear are installed on your system. Force the correct base version of php to be installed: # portmaster lang/php5 Reinstall any ported PHP applications, eg phpMyAdmin: # portmaster databases/phpmyadmin (etc., etc. for all the apps you had installed: check /tmp/php-deletion-log for details. This should install any necessary dependencies.) Finally, compare what you just installed with the record of what you previously installed to fix up any discrepancies, eg. if you have PHP applications installed from non-ports sources. There isn't an exact one-to-one correspondence between php52-* and php5-* ports (as I recall), since some functions have been moved into the PHP core, or shifted between different modules or moved to pear- or pecl- modules. However, those are generally the exceptions: if you can't find the exact equivalent php53 module, then (a) try the application without, (b) check the documentation on www.php.net for clues and finally (c) look for equivalent pear- or pecl- modules. Any PHP application installed from ports should automatically install everything it needs through the ports dependency mechanism. Also, if you use eAccelerator or similar, be sure to reinstall it after upgrading PHP. Note: the lang/php5 port is the correct port for php-5.3.x at the time of writing, but that port is very soon going to switch to providing php-5.4.x, and you would need to switch to lang/php53 if you don't want to go through yet another upgrade. Note 2: beware of the common problem with ordering of extension loadable modules in /usr/local/etc/php/extensions.ini -- some php modules depend on others; unfortunately there's no good way of controlling the order the modules are listed in extensions.ini to account for this. If php crashes on startup, swapping lines around in that file may well be the solution. It's been discussed many times on this list and freebsd-questions@..., so check the archives in case of difficulty. Please don't TOP POST (corrected here). If you don't know what that means, Google for it. Hi Matthew, Thanks for your reply. For some reason that didn't work completely; must be because I am rather a newbie on this. Now I removed php5.2 all together from my FreeBSD server (including all related programs). If I now want to install php 5.3, how do I install the extensions as there is no php53-extensions? Or should I use the php52-extensions instead? After installing the php5 you will need to install the php5-extensions-1.6 port: /usr/ports/lang/php5-extensions. Be sure to run make config in the port prior to installing it. That also applies to the php5-5.3.13 port: /usr/ports/lang/php5, especially if you need support for Apache. It is not built by default. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: problem running pkg_delete
Mel Flynn writes: pkg_delete: the package info for package Source is corrupt Any ideas? Can you provide the output of: grep -E '@(unexec|exec).*Source' /var/db/pkg/*/+CONTENTS Yes. huff@ grep -E '@(unexec|exec).*Source' /var/db/pkg/*/+CONTENTS /var/db/pkg/open-motif-2.3.3/+CONTENTS:@unexec rm -f %D/man/cat3/XmTextGetSource.3.gz %D/man/cat3/XmTextGetSource.3 %D/man/cat3/XmTextGetSource.3.gz %D/man/cat3/XmTextGetSource.3.gz.gz %D/man/cat3/XmTextGetSource.3.gz.bz2 /var/db/pkg/open-motif-2.3.3/+CONTENTS:@unexec rm -f %D/man/cat3/XmTextSetSource.3.gz %D/man/cat3/XmTextSetSource.3 %D/man/cat3/XmTextSetSource.3.gz %D/man/cat3/XmTextSetSource.3.gz.gz %D/man/cat3/XmTextSetSource.3.gz.bz2 /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rm -f %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::Source.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::Source.3 %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::Source.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::Source.3.gz.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::Source.3.gz.bz2 /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rm -f %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler.3 %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler.3.gz.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler.3.gz.bz2 /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rm -f %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Executable.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Executable.3 %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Executable.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Executable.3.gz.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Executable.3.gz.bz2 /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rm -f %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::File.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::File.3 %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::File.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::File.3.gz.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::File.3.gz.bz2 /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rm -f %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Handle.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Handle.3 %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Handle.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Handle.3.gz.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Handle.3.gz.bz2 /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rm -f %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Perl.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Perl.3 %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Perl.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Perl.3.gz.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::Perl.3.gz.bz2 /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rm -f %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::RawTAP.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::RawTAP.3 %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::RawTAP.3.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::RawTAP.3.gz.gz %D/lib/perl5/5.14.2/man/cat3/TAP::Parser::SourceHandler::RawTAP.3.gz.bz2 /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rmdir %D/lib/perl5/site_perl/5.14.2/TAP/Parser/Source 2/dev/null || true /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rmdir %D/lib/perl5/site_perl/5.14.2/TAP/Parser/SourceHandler 2/dev/null || true /var/db/pkg/perl-threaded-5.14.2_2/+CONTENTS:@unexec rm -f %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source.3.gz %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source.3 %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source.3.gz %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source.3.gz.gz %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source.3.gz.bz2 /var/db/pkg/perl-threaded-5.14.2_2/+CONTENTS:@unexec rm -f %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source::Memory.3.gz %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source::Memory.3 %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source::Memory.3.gz %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source::Memory.3.gz.gz %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source::Memory.3.gz.bz2 /var/db/pkg/perl-threaded-5.14.2_2/+CONTENTS:@unexec rm -f %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source::SQLite.3.gz %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source::SQLite.3 %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source::SQLite.3.gz %D/lib/perl5/5.14.2/perl/man/cat3/CPANPLUS::Internals::Source::SQLite.3.gz.gz
Re: portupgrade-devel / WITH_PKGNG
Not Hanging. portversion -Fv took 5 hours to run instead of the minute or so. This makes everything useless. Anton On 05/13/2012 04:47, freebsd-ports-requ...@freebsd.org wrote: portupgrade-devel / WITH_PKGNG ___ 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: portupgrade-devel / WITH_PKGNG
On 5/13/2012 1:05 PM, Jeff Anton wrote: Not Hanging. portversion -Fv took 5 hours to run instead of the minute or so. This makes everything useless. Anton On 05/13/2012 04:47, freebsd-ports-requ...@freebsd.org wrote: portupgrade-devel / WITH_PKGNG ___ 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 Hi, Sorry I meant to update the list yesterday. The latest portupgrade-devel port has this issue fixed. You may want to just manually make deinstall reinstall for it. Regards, Bryan Drewery ___ 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: problem running pkg_delete
On 13-5-2012 14:48, Robert Huff wrote: Mel Flynn writes: pkg_delete: the package info for package Source is corrupt Any ideas? Can you provide the output of: grep -E '@(unexec|exec).*Source' /var/db/pkg/*/+CONTENTS Yes. Well, I was hoping to see some exotic exec construct that would confuse pkg_delete, but no such luck. huff@ grep -E '@(unexec|exec).*Source' /var/db/pkg/*/+CONTENTS /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rmdir %D/lib/perl5/site_perl/5.14.2/TAP/Parser/Source 2/dev/null || true /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rmdir %D/lib/perl5/site_perl/5.14.2/TAP/Parser/SourceHandler 2/dev/null || true This looks a bit suspicious, the quotes shouldn't really be there and it actually installs something ending in Source. However, it's probably best to rule out the obvious: if you have dir /var/db/pkg/Source/ does the +CONTENTS file in it look sane? When in doubt, post it. If you don't, any hits on: grep '^@pkgdep Source' /var/db/pkg/*/+CONTENTS -- Mel ___ 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: problem running pkg_delete
On 13 May 2012 20:35, Mel Flynn rfl...@acsalaska.net wrote: On 13-5-2012 14:48, Robert Huff wrote: Mel Flynn writes: pkg_delete: the package info for package Source is corrupt Any ideas? Can you provide the output of: grep -E '@(unexec|exec).*Source' /var/db/pkg/*/+CONTENTS Yes. Well, I was hoping to see some exotic exec construct that would confuse pkg_delete, but no such luck. huff@ grep -E '@(unexec|exec).*Source' /var/db/pkg/*/+CONTENTS /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rmdir %D/lib/perl5/site_perl/5.14.2/TAP/Parser/Source 2/dev/null || true /var/db/pkg/p5-Test-Harness-3.23/+CONTENTS:@unexec rmdir %D/lib/perl5/site_perl/5.14.2/TAP/Parser/SourceHandler 2/dev/null || true This looks a bit suspicious, the quotes shouldn't really be there and it actually installs something ending in Source. However, it's probably best to rule out the obvious: if you have dir /var/db/pkg/Source/ does the +CONTENTS file in it look sane? When in doubt, post it. If you don't, any hits on: grep '^@pkgdep Source' /var/db/pkg/*/+CONTENTS The quotes are from @dirrmtry, so inserted by bsd.port.mk. Chris ___ 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: problem running pkg_delete
On 13-5-2012 21:51, Chris Rees wrote: The quotes are from @dirrmtry, so inserted by bsd.port.mk. Ah, shows how rusty I am. Also, why aren't they single quotes? Do we actually support shell expansion dirrmtry? -- Mel ___ 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: Heimdal 1.5.2 problem
On Fri, May 11, 2012 at 1:15 PM, Matthias Andree matthias.and...@gmx.de wrote: Am 11.05.2012 04:42, schrieb Robert Simmons: And, this is the version of BerkeleyDB that it compiles and installs to satisfy the BDB backend that I enabled during config: db41-4.1.25_4 Try with the newest BDB that builds. Chances are versions 4.4 and beyond are better-behaved, chances are that they aren't. db41 is very old. Heimdal fails to compile if any other version of BDB is installed already. Also, according to the docs in Heimdal itself, GDBM is an alternative, but when I install GDBM, configure for Heimdal does not find it and goes ahead and installs db41. Has anyone else successfully installed Heimdal 1.5.2 from ports on FreeBSD 9.0? What did you do differently than me? I'm using the base system Kerberos where needed (i. e. fetchmail as a GSSAPI client). Have you or anyone else been able to successfully install Heimdal 1.5.2 from the ports tree using BDB? If so, what steps did you take that are different from what I did? ___ 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 get hplip to work on HP LaserJet 1212nf MFP
I built hplip from the ports on both the old and new computer, FreeBSD 8.2 i386 and 9.0 amd64 respectively, and can't get either of them to work, either on USB or Ethernet. I commented out device ulpt in the kernel config file, but got No devices found in the USB setup, even though the printer was recognized by system messages and usbconfig. When I connected the printer on the new computer via USB, ulpt.ko automatically loaded (how to prevent that?), but I got the same No devices found even when ulpt.ko was renamed to ulpt2.ko so it would not be found and loaded (a kludge). The printer was found when connected by Ethernet, but the binary plugin installation failed consistently, some complaint of /etc/issue or hp-plugin-install not found. By way of comparison, I also built hplip3 from pkgsrc in NetBSD 5.1_STABLE amd64; this was actually pkgsrc-wip (http://pkgsrc-wip.sourceforge.net). That was version 3.11.1. I got No devices found both with USB and Ethernet; could still try again with Ethernet, getting the printer IP address from either dmesg.boot or logging in to wireless router, though this is a slender chance. hplip versions for FreeBSD are 3.11.1 on the old computer and 3.11.5 on the new computer. I do intend to update my 9.0-STABLE installation on the new computer and then portupgrade or portmaster this and other ports, but fear more of the same frustration. Would I need to exclude ulpt module as well as kernel config device ulpt line, or can ulpt.ko be prevented from automatically loading, or would that make no difference? Are HP printers especially recalcitrant to setting up, or especially USB-quirky, as opposed to other brands such as Lexmark, Samsung, Brother, Xerox and Canon? Other things I intend to try are with Wine; I also intend to try on Linux, possibly on NetBSD if I can get that to install and run on the new computer. Linux is home base for hplip and much or most other open-source (quasi-)Unix software. Tom ___ 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
Smokeping failure
It's apparently failing on the absence of FCGI or CGI::Fast. Any idea why this is happening all of a sudden? make failure: cthulhu# cd /usr/ports/net-mgmt/smokeping cthulhu# make clean === Cleaning for smokeping-2.6.7 cthulhu# make === License check disabled, port has not defined LICENSE === Found saved configuration for smokeping-2.4.2_6 === Extracting for smokeping-2.6.7 = SHA256 Checksum OK for smokeping-2.6.7.tar.gz. === smokeping-2.6.7 depends on file: /usr/local/bin/perl5.12.4 - found cd /usr/ports/net-mgmt/smokeping/work/smokeping-2.6.7/lib ; /bin/rm BER.pm SNMP_util.pm SNMP_Session.pm === Patching for smokeping-2.6.7 === smokeping-2.6.7 depends on file: /usr/local/bin/perl5.12.4 - found === Applying FreeBSD patches for smokeping-2.6.7 /usr/bin/sed -i.bak -e s!%%USERS%%!smokeping!g -e s!%%GROUPS%%!smokeping!g -e s!%%PREFIX%%!/usr/local!g -e s!%%LOCALBASE%%!/usr/local!g -e s!%%DATADIR%%!/usr/local/share/smokeping!g -e s!%%DOCSDIR%%!/usr/local/share/doc/smokeping!g -e s!%%EXAMPLESDIR%%!/usr/local/share/examples/smokeping!g -e s!%%WWWDIR%%!/usr/local/www/smokeping!g -e s!%%ETCDIR%%!/usr/local/etc/smokeping!g /usr/ports/net-mgmt/smokeping/work/smokeping-2.6.7/doc/Makefile.in === smokeping-2.6.7 depends on executable: gmake - found === smokeping-2.6.7 depends on file: /usr/local/bin/perl5.12.4 - found === Configuring for smokeping-2.6.7 checking build system type... i386-portbld-freebsd9.0 checking host system type... i386-portbld-freebsd9.0 checking target system type... i386-portbld-freebsd9.0 checking for gcc... cc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking how to run the C preprocessor... cpp checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... conftools/install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether gmake sets $(MAKE)... yes checking for style of include used by gmake... GNU checking dependency style of cc... none checking whether to enable maintainer-specific portions of Makefiles... no checking for perl... /usr/local/bin/perl checking for sed... /usr/bin/sed checking for grep... (cached) /usr/bin/grep checking for echo... /bin/echo checking for ln... /bin/ln checking for cp... /bin/cp checking for rm... /bin/rm checking for rmdir... /bin/rmdir checking for mkdir... /bin/mkdir checking for find... /usr/bin/find checking for sendmail... /usr/sbin/sendmail checking for gnroff... no checking for nroff... /usr/bin/nroff checking for gnumake... no checking for gmake... /usr/local/bin/gmake checking checking for gnu make availablility... /usr/local/bin/gmake is GNU make checking checking for perl module 'RRDs'... Ok checking checking for perl module 'FCGI'... Failed checking checking for perl module 'CGI'... Ok checking checking for perl module 'CGI::Fast'... Failed checking checking for perl module 'Config::Grammar'... Ok checking checking for perl module 'Digest::HMAC_MD5'... Ok checking checking for perl module 'LWP'... Ok ** Aborting Configure ** If you know where perl can find the missing modules, set the PERL5LIB environment variable accordingly. FIRST though, make sure that 'perl' starts the perl binary you want to use for SmokePing. Now you can install local copies of the missing modules by running ./setup/build-perl-modules.sh /usr/local/thirdparty The RRDs perl module is part of RRDtool. Either use the rrdtool package provided by your OS or install rrdtool from source. If you install from source, the RRDs module is located PREFIX/lib/perl === Script configure failed unexpectedly. Please report the problem to po...@freebsd.org [maintainer] and attach the /usr/ports/net-mgmt/smokeping/work/smokeping-2.6.7/config.log including the output of the failure of your make command. Also, it might be a good idea to
Re: More lame portmgr poetry
On Mon, Dec 26, 2011 at 11:40:56AM -0500, Thomas Abthorpe wrote: On Fri, Dec 23, 2011 at 08:46:06PM -0500, Glen Barber wrote: On Fri, Dec 23, 2011 at 07:42:19PM -0500, Eitan Adler wrote: On Fri, Dec 23, 2011 at 4:45 PM, Glen Barber g...@freebsd.org wrote: Hmm.. Why does portmgr get to have all the fun? :) Do we get to hear you both sing at this year's BSDCAN? I'm quite certain none of us want that. +1 I can't speak for Glen per se, but a chorus of chain saws sound better than my singing :) Well, in case there was interest, Thomas and I did sing a quick song together in the Hacker's Lounge during BSDCan. The YouTube link is here: https://www.youtube.com/watch?v=2Mb6w4q_Gb0 I hope it was as good as expected. Cheers, Glen ___ 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
