Correct way to portupgrade php5 and php5-extensions-1.1 ?
Hi, Following the most recent update of PHP5 (5.2.6_2) and subsequent portaudit warnings for 5.2.6, I've been upgrading lang/php5 and lang/php5-extensions-1.1 on a number of machines. My question is, what is the best way to do this. Some options come to mind: 1) portupgrade -fpb php5-5.2.6 php5-extensions-1.1 or 2) portupgrade -fpb php5\* or 3) portupgrade -fpbR php5-5.2.6 I noticed that the first option didn't update the actual binaries in /usr/local/lib/php/20060613/, but it still works on the machine where I tried it. The second, I think, will always work (/usr/local/lib/php/20060613/ files are all updated/recompiled), but it takes a long time. I'm suspecting this way perhaps some ports will be updated/recompiled more than once? (once when php5-extensions is portupgraded, and once when for instance php5-session-5.2.6 is upgraded). The last option seems the best according to the manpage, but this would in my case also recompile phpmyadmin. Is that needed? Perhaps there are also different cases when for instance there is a minor version update like this one (from 5.2.6 to 5.2.6_2), and for instance a 5.2.6 to 5.2.7 or even 5.2.6 to 5.3 update). Who can shine some light on this dark matter? :-) -- Frederique ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Correct way to portupgrade php5 and php5-extensions-1.1 ?
Hi, Following the most recent update of PHP5 (5.2.6_2) and subsequent portaudit warnings for 5.2.6, I've been upgrading lang/php5 and lang/php5-extensions-1.1 on a number of machines. My question is, what is the best way to do this. Some options come to mind: 1) portupgrade -fpb php5-5.2.6 php5-extensions-1.1 or 2) portupgrade -fpb php5\* or 3) portupgrade -fpbR php5-5.2.6 I noticed that the first option didn't update the actual binaries in /usr/local/lib/php/20060613/, but it still works on the machine where I tried it. The second, I think, will always work (/usr/local/lib/php/20060613/ files are all updated/recompiled), but it takes a long time. I'm suspecting this way perhaps some ports will be updated/recompiled more than once? (once when php5-extensions is portupgraded, and once when for instance php5-session-5.2.6 is upgraded). The last option seems the best according to the manpage, but this would in my case also recompile phpmyadmin. Is that needed? Perhaps there are also different cases when for instance there is a minor version update like this one (from 5.2.6 to 5.2.6_2), and for instance a 5.2.6 to 5.2.7 or even 5.2.6 to 5.3 update). Who can shine some light on this dark matter? :-) -- FR ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Correct way to portupgrade php5 and php5-extensions-1.1 ?
Pine Digital Security Support wrote: Hi, Following the most recent update of PHP5 (5.2.6_2) and subsequent portaudit warnings for 5.2.6, I've been upgrading lang/php5 and lang/php5-extensions-1.1 on a number of machines. My question is, what is the best way to do this. Some options come to mind: 1) portupgrade -fpb php5-5.2.6 php5-extensions-1.1 or 2) portupgrade -fpb php5\* or 3) portupgrade -fpbR php5-5.2.6 I noticed that the first option didn't update the actual binaries in /usr/local/lib/php/20060613/, but it still works on the machine where I tried it. The second, I think, will always work (/usr/local/lib/php/20060613/ files are all updated/recompiled), but it takes a long time. I'm suspecting this way perhaps some ports will be updated/recompiled more than once? (once when php5-extensions is portupgraded, and once when for instance php5-session-5.2.6 is upgraded). The last option seems the best according to the manpage, but this would in my case also recompile phpmyadmin. Is that needed? Perhaps there are also different cases when for instance there is a minor version update like this one (from 5.2.6 to 5.2.6_2), and for instance a 5.2.6 to 5.2.7 or even 5.2.6 to 5.3 update). Who can shine some light on this dark matter? :-) I uprgraded PHP for same reason with just one simple command: portmaster php5-extensions-1.1 It did all required steps (it first upgrade libraries for core PHP, then php5-5.x.x, then libraries for extensions, then extensions and as last step php5-extensions-1.1) (optionally you can upgrade PECL extensions by portmaster pecl-\*) Then restart Apache and PHP 5.2.6_2 is on ;) Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Correct way to portupgrade php5 and php5-extensions-1.1 ?
Frederique Rijsdijk wrote: Hi, Following the most recent update of PHP5 (5.2.6_2) and subsequent portaudit warnings for 5.2.6, I've been upgrading lang/php5 and lang/php5-extensions-1.1 on a number of machines. My question is, what is the best way to do this. Some options come to mind: 1) portupgrade -fpb php5-5.2.6 php5-extensions-1.1 or 2) portupgrade -fpb php5\* The command is OK. It rebuilds all ports that starts with php5 in dependency order. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Correct way to portupgrade php5 and php5-extensions-1.1 ?
Pine Digital Security Support wrote: Hi, Following the most recent update of PHP5 (5.2.6_2) and subsequent portaudit warnings for 5.2.6, I've been upgrading lang/php5 and lang/php5-extensions-1.1 on a number of machines. My question is, what is the best way to do this. Some options come to mind: 1) portupgrade -fpb php5-5.2.6 php5-extensions-1.1 or 2) portupgrade -fpb php5\* or 3) portupgrade -fpbR php5-5.2.6 I noticed that the first option didn't update the actual binaries in /usr/local/lib/php/20060613/, but it still works on the machine where I tried it. The second, I think, will always work (/usr/local/lib/php/20060613/ files are all updated/recompiled), but it takes a long time. I'm suspecting this way perhaps some ports will be updated/recompiled more than once? (once when php5-extensions is portupgraded, and once when for instance php5-session-5.2.6 is upgraded). The last option seems the best according to the manpage, but this would in my case also recompile phpmyadmin. Is that needed? Perhaps there are also different cases when for instance there is a minor version update like this one (from 5.2.6 to 5.2.6_2), and for instance a 5.2.6 to 5.2.7 or even 5.2.6 to 5.3 update). Who can shine some light on this dark matter? :-) I uprgraded PHP for same reason with just one simple command: portmaster php5-extensions-1.1 It did all required steps (it first upgrade libraries for core PHP, then php5-5.x.x, then libraries for extensions, then extensions and as last step php5-extensions-1.1) (optionally you can upgrade PECL extensions by portmaster pecl-\*) Then restart Apache and PHP 5.2.6_2 is on ;) Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] I used this command: portmanager lang/php5-extensions -p -l -ui then restart apache as usual, portmanager just works :-) cheers, Tim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
net/icmpinfo - fails: install_error
Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags=-nullfs -plistcheck -onceonly and ccache support, with the official up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/icmpinfo-1.11.log : building icmpinfo-1.11 in directory /var/tinderbox/7-STABLE-FTP maintained by: [EMAIL PROTECTED] building for: 7.0-STABLE amd64 port directory: /usr/ports/net/icmpinfo Makefile ident: $FreeBSD: ports/net/icmpinfo/Makefile,v 1.17 2008/05/28 13:28:38 edwin Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Tue Sep 9 12:50:39 UTC 2008 .Last 40 lines of the log.. make: don't know how to make regression-test(continuing) phase 6: make install add_pkg === Installing for icmpinfo-1.11 === Generating temporary packing list === Checking if net/icmpinfo already installed install -s -o root -g wheel -m 555 /work/a/ports/net/icmpinfo/work/icmpinfo-1.11/icmpinfo /usr/local/bin /usr/sbin/chown root /usr/local/bin/icmpinfo /bin/chmod 4555 /usr/local/bin/icmpinfo install -o root -g wheel -m 444 /work/a/ports/net/icmpinfo/work/icmpinfo-1.11/icmpinfo.man /usr/local/man/man1/icmpinfo.1 === Compressing manual pages for icmpinfo-1.11 === Registering installation for icmpinfo-1.11 === SECURITY REPORT: This port has installed the following binaries which execute with increased privileges. /usr/local/bin/icmpinfo This port has installed the following files which may act as network servers and may therefore pose a remote security risk to the system. /usr/local/bin/icmpinfo If there are vulnerabilities in these programs there may be a security risk to the system. FreeBSD makes no guarantee about the security of ports included in the Ports Collection. Please type 'make deinstall' to deinstall the port if this is a concern. phase 7: make package === Building package for icmpinfo-1.11 tar: share/doc/icmpinfo/README: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 Creating package /tmp/packages/All/icmpinfo-1.11.tbz Registering depends:. Creating bzip'd tar ball in '/tmp/packages/All/icmpinfo-1.11.tbz' *** Error code 1 Stop in /a/ports/net/icmpinfo. build of /usr/ports/net/icmpinfo ended at Tue Sep 9 12:50:42 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/testing_process.txt Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - [EMAIL PROTECTED], PGP Key ID 057E9F8B493A297B ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devel/libtool15 unconditionally hardcodes autodetected textproc/gsed
* Alexey Shuvaev ([EMAIL PROTECTED]) wrote: While the ports are in freeze just want to point to the problem I have encountered. Not sure if this is a critical bug, just a bug or not a bug at all (so, no PR yet). This is definitely a bug, so better send-pr for this issue not to be lost while we're in freeze. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D [EMAIL PROTECTED] ..: jabber: [EMAIL PROTECTED]http://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devel/libtool15 unconditionally hardcodes autodetected textproc/gsed
On Tue, Sep 09, 2008 at 05:20:06PM +0400, Dmitry Marakasov wrote: * Alexey Shuvaev ([EMAIL PROTECTED]) wrote: While the ports are in freeze just want to point to the problem I have encountered. Not sure if this is a critical bug, just a bug or not a bug at all (so, no PR yet). This is definitely a bug, so better send-pr for this issue not to be lost while we're in freeze. I think Alexey's point might have been that this should be fixed during the freeze, before 6.4 and 7.1 ship with the ports tree - and I think it might be a good idea, if libtool uses sed (resp. gsed) in any files in the already-built target application / library. From a quick look, that does not seem to be the case, but if it is, it's important. What I mean is the following scenario: - libfoo uses libtool for its build - libfoo depends on libbar which depends on GNU sed - during libfoo's build, libbar is built, thus gsed is installed - during libfoo's build, libtool detects gsed installed and remembers it - in libfoo's binary package, there is a shell script that uses gsed, because libtool knows gsed is present on the system - an unsuspecting user installs the libfoo binary package without previously building libbar - the unsuspecting user gets a shell script that tries to run gsed and fails. Of course, this all hinges on the idea that libtool uses gsed in any files that are part of the binary package. From a quick look, the .la files do not contain any shell commands apart from variable assignments, but I'm not too familiar with libtool and I don't know if there are any other files that it might generate in the binary package. If libtool may put gsed into libfoo's binary package, this should be fixed before the freeze. If libtool only uses gsed during libfoo's build, then it is not a critical problem. Of course, if Dmitry is more familiar with libtool than I am, and he knows that libtool does not leave any such files, then I've just wasted everybody's time with unneeded idle speculation, for which I apologize :) G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 No language can express every thought unambiguously, least of all this one. pgprZ8yIal68Y.pgp Description: PGP signature
net/mpd - fails: install_error
Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags=-nullfs -plistcheck -onceonly and ccache support, with the official up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/mpd-3.18_5.log : building mpd-3.18_5 in directory /var/tinderbox/7-STABLE-FTP maintained by: [EMAIL PROTECTED] building for: 7.0-STABLE amd64 port directory: /usr/ports/net/mpd Makefile ident: $FreeBSD: ports/net/mpd/Makefile,v 1.51 2007/02/12 07:57:25 sem Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Tue Sep 9 15:14:07 UTC 2008 .Last 40 lines of the log.. === src (install) /usr/share/mk/bsd.compat.mk, line 35: warning: NOMAN is deprecated in favour of NO_MAN install -s -o root -g wheel -m 555 mpd /usr/local/sbin === conf (install) /usr/share/mk/bsd.compat.mk, line 35: warning: NOOBJ is deprecated in favour of NO_OBJ install -c -o root -g wheel -m 444 mpd.conf.sample mpd.links.sample mpd.secret.sample mpd.script.sample /usr/local/etc/mpd === Installing rc.d startup script(s) === Registering installation for mpd-3.18_5 === SECURITY REPORT: This port has installed the following files which may act as network servers and may therefore pose a remote security risk to the system. /usr/local/sbin/mpd This port has installed the following startup scripts which may cause these network services to be started at boot time. /usr/local/etc/rc.d/mpd If there are vulnerabilities in these programs there may be a security risk to the system. FreeBSD makes no guarantee about the security of ports included in the Ports Collection. Please type 'make deinstall' to deinstall the port if this is a concern. For more information, and contact details about the security status of this software, see the following webpage: http://sourceforge.net/projects/mpd/ phase 7: make package === Building package for mpd-3.18_5 tar: man/man8/mpd.8.gz: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 Creating package /tmp/packages/All/mpd-3.18_5.tbz Registering depends:. Registering conflicts: mpd-[^3]*. Creating bzip'd tar ball in '/tmp/packages/All/mpd-3.18_5.tbz' *** Error code 1 Stop in /a/ports/net/mpd. build of /usr/ports/net/mpd ended at Tue Sep 9 15:14:25 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/testing_process.txt Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - [EMAIL PROTECTED], PGP Key ID 057E9F8B493A297B ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
ftp/py-curl - fails: mtree
Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags=-nullfs -plistcheck -onceonly and ccache support, with the official up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. The build of this port was tried 4 times since last BotMail while trying to build ports that depend on it. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/py25-curl-7.16.4.log : building py25-curl-7.16.4 in directory /var/tinderbox/7-STABLE-FTP maintained by: [EMAIL PROTECTED] building for: 7.0-STABLE amd64 port directory: /usr/ports/ftp/py-curl Makefile ident: $FreeBSD: ports/ftp/py-curl/Makefile,v 1.30 2008/05/30 05:21:25 perky Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Tue Sep 9 15:48:11 UTC 2008 .Last 40 lines of the log.. Registering depends: curl-7.18.0 python25-2.5.2_3. Creating bzip'd tar ball in '/tmp/packages/All/py25-curl-7.16.4.tbz' Deleting py25-curl-7.16.4 === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 95166194 drwxr-xr-x3 root wheel 512 Sep 9 15:48 usr/local/share/doc/py-curl 9516620 56 -rw-r--r--1 root wheel 27397 Jul 11 2007 usr/local/share/doc/py-curl/ChangeLog 9516621 52 -rw-r--r--1 root wheel 26526 Jul 18 2002 usr/local/share/doc/py-curl/COPYING 95166224 -rw-r--r--1 root wheel1509 Sep 6 2005 usr/local/share/doc/py-curl/INSTALL 95166234 -rw-r--r--1 root wheel 471 Apr 22 2007 usr/local/share/doc/py-curl/README 95166244 -rw-r--r--1 root wheel1058 Apr 23 2007 usr/local/share/doc/py-curl/TODO 95166334 drwxr-xr-x2 root wheel1024 Sep 9 15:48 usr/local/share/doc/py-curl/tests 95166344 -rw-r--r--1 root wheel1953 Apr 10 2007 usr/local/share/doc/py-curl/tests/test.py 95166354 -rw-r--r--1 root wheel 693 Apr 21 2003 usr/local/share/doc/py-curl/tests/test_cb.py 95166364 -rw-r--r--1 root wheel 340 Apr 21 2003 usr/local/share/doc/py-curl/tests/test_debug.py 95166374 -rw-r--r--1 root wheel 289 Aug 24 2006 usr/local/share/doc/py-curl/tests/test_ftp.py 95166384 -rw-r--r--1 root wheel1419 May 1 2003 usr/local/share/doc/py-curl/tests/test_getinfo.py 95166398 -rw-r--r--1 root wheel2733 Mar 30 2005 usr/local/share/doc/py-curl/tests/test_gtk.py 9516640 12 -rw-r--r--1 root wheel5476 May 1 2003 usr/local/share/doc/py-curl/tests/test_internals.py 95166414 -rw-r--r--1 root wheel1126 May 1 2003 usr/local/share/doc/py-curl/tests/test_memleak.py 95166424 -rw-r--r--1 root wheel 676 Mar 11 2005 usr/local/share/doc/py-curl/tests/test_multi.py 95166434 -rw-r--r--1 root wheel1746 Apr 10 2007 usr/local/share/doc/py-curl/tests/test_multi2.py 95166448 -rw-r--r--1 root wheel2068 Mar 11 2005 usr/local/share/doc/py-curl/tests/test_multi3.py 95166454 -rw-r--r--1 root wheel1400 Mar 11 2005 usr/local/share/doc/py-curl/tests/test_multi4.py 95166464 -rw-r--r--1 root wheel1472 Mar 11 2005 usr/local/share/doc/py-curl/tests/test_multi5.py 95166474 -rw-r--r--1 root wheel1536 Mar 11 2005 usr/local/share/doc/py-curl/tests/test_multi6.py 95166484 -rw-r--r--1 root wheel1924 Nov 10 2006 usr/local/share/doc/py-curl/tests/test_multi_socket.py 95166494 -rw-r--r--1 root wheel1749 Nov 10 2006 usr/local/share/doc/py-curl/tests/test_multi_timer.py 9516650 12 -rw-r--r--1 root wheel5773 Apr 12 2005 usr/local/share/doc/py-curl/tests/test_multi_vs_thread.py 95166514 -rw-r--r--1 root wheel 589 Apr 21 2003 usr/local/share/doc/py-curl/tests/test_post.py 95166524 -rw-r--r--1 root wheel 535 Mar 3 2005 usr/local/share/doc/py-curl/tests/test_post2.py 95166534 -rw-r--r--1 root wheel 804 Jun 21 2004
Re: devel/libtool15 unconditionally hardcodes autodetected textproc/gsed
Here's the fix, btw.
Portrevision bump is to make users with gsed-tainted libtool to
rebuild it with correct sed.
--- libtool.patch begins here ---
Index: Makefile
===
RCS file: /home/pcvs/ports/devel/libtool15/Makefile,v
retrieving revision 1.62
diff -u -r1.62 Makefile
--- Makefile21 Aug 2008 06:16:44 - 1.62
+++ Makefile9 Sep 2008 16:02:47 -
@@ -7,6 +7,7 @@
PORTNAME?= libtool
PORTVERSION= 1.5.26
+PORTREVISION= 1
CATEGORIES=devel
MASTER_SITES= ${MASTER_SITE_GNU}
MASTER_SITE_SUBDIR=libtool
Index: files/patch-configure
===
RCS file: files/patch-configure
diff -N files/patch-configure
--- /dev/null 1 Jan 1970 00:00:00 -
+++ files/patch-configure 9 Sep 2008 16:02:47 -
@@ -0,0 +1,11 @@
+--- configure.orig 2008-02-01 19:38:42.0 +0300
configure 2008-09-09 20:01:57.0 +0400
+@@ -3615,7 +3615,7 @@
+ do
+ IFS=$as_save_IFS
+ test -z $as_dir as_dir=.
+- for lt_ac_prog in sed gsed; do
++ for lt_ac_prog in sed; do
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if { test -f $as_dir/$lt_ac_prog$ac_exec_ext $as_test_x
$as_dir/$lt_ac_prog$ac_exec_ext; }; then
+ lt_ac_sed_list=$lt_ac_sed_list $as_dir/$lt_ac_prog$ac_exec_ext
--- libtool.patch ends here ---
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
[EMAIL PROTECTED] ..: jabber: [EMAIL PROTECTED]http://www.amdmi3.ru
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Exploring the FreeBSD ports tree
Hello, while playing with fastcgi stuff, i have updated my tool to explore the FreeBSD ports tree. It is now a fastcgi responder which can answer questions behind a web server such as apache or lighttpd. It can be found here: http://www.lpthe.jussieu.fr/~talon/show_index.fcgi The needed configuration for lighttpd is explained in the comments at the beginning, this is basically the same as for Django. So one needs to run the python script show_index.fcgi as root, it creates a socket in /tmp, daemonizes, and changes its ownership to www. It then communicates with the web server through this socket. To browse the ports tree, just point the browser at /showindex/ on the given server. A reasonable number of queries per second is achievable through this setup. -- Michel TALON ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
net/xwhois - fails: install_error
Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags=-nullfs -plistcheck -onceonly and ccache support, with the official up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/xwhois-0.4.2_4.log : building xwhois-0.4.2_4 in directory /var/tinderbox/7-STABLE-FTP maintained by: [EMAIL PROTECTED] building for: 7.0-STABLE amd64 port directory: /usr/ports/net/xwhois Makefile ident: $FreeBSD: ports/net/xwhois/Makefile,v 1.26 2008/06/06 13:50:32 edwin Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Tue Sep 9 19:12:16 UTC 2008 .Last 40 lines of the log.. pkg_add libXau-1.0.3_2.tbz skipping libXau-1.0.3_2, already added pkg_add libXdmcp-1.0.2_1.tbz skipping libXdmcp-1.0.2_1, already added pkg_add xproto-7.0.10_1.tbz skipping xproto-7.0.10_1, already added pkg_add xextproto-7.0.2.tbz skipping xextproto-7.0.2, already added pkg_add inputproto-1.4.2.1.tbz skipping inputproto-1.4.2.1, already added pkg_add gtk-1.2.10_20.tbz skipping gtk-1.2.10_20, already added === Installing for xwhois-0.4.2_4 === xwhois-0.4.2_4 depends on executable: pkg-config - found === xwhois-0.4.2_4 depends on shared library: glib-12.3 - found === xwhois-0.4.2_4 depends on shared library: gtk-12.2 - found === Generating temporary packing list === Checking if net/xwhois already installed install -s -o root -g wheel -m 555 /work/a/ports/net/xwhois/work/xwhois-0.4.2/src/xwhois /usr/local/bin /bin/mkdir -p /usr/local/share/xwhois /bin/mkdir -p /usr/local/share/xwhois/pixmaps install -o root -g wheel -m 444 /work/a/ports/net/xwhois/work/xwhois-0.4.2/docs/xwhois.servers /usr/local/share/xwhois install -o root -g wheel -m 444 /work/a/ports/net/xwhois/work/xwhois-0.4.2/docs/xwhois.xpm /usr/local/share/xwhois/pixmaps === Registering installation for xwhois-0.4.2_4 phase 7: make package === Building package for xwhois-0.4.2_4 tar: share/doc/xwhois/README: Cannot stat: No such file or directory tar: share/doc/xwhois/TODO: Cannot stat: No such file or directory tar: share/doc/xwhois/ChangeLog: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 Creating package /tmp/packages/All/xwhois-0.4.2_4.tbz Registering depends: gtk-1.2.10_20 gettext-0.17_1 libiconv-1.11_1 glib-1.2.10_12 libXi-1.1.3,1 libXext-1.0.3,1 libX11-1.1.3_1,1 libXdmcp-1.0.2_1 libXau-1.0.3_2 libSM-1.0.3_1,1 libICE-1.0.4_1,1 xproto-7.0.10_1 pkg-config-0.23_1 perl-5.8.8_1 inputproto-1.4.2.1 kbproto-1.0.3 xextproto-7.0.2. Creating bzip'd tar ball in '/tmp/packages/All/xwhois-0.4.2_4.tbz' *** Error code 1 Stop in /a/ports/net/xwhois. build of /usr/ports/net/xwhois ended at Tue Sep 9 19:12:43 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/testing_process.txt Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - [EMAIL PROTECTED], PGP Key ID 057E9F8B493A297B ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Request for approval -- devel/p5-Data-Dump-Streamer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear portmgr team, I would like to ask you to approve the following fix: devel/p5-Data-Dump-Streamer [http://www.gahr.ch/FreeBSD/patches/p5-Data-Dump-Streamer.diff] Background: Update to 0.06 of devel/p5-B-Utils has changed the installation path of the file that p5-Data-Dump-Streamer checks for in the dependency list. Evidence: http://t64.tecnik93.com/errors/7-STABLE-FTP/p5-Data-Dump-Streamer-2.08.40.log Thanks. Best regards, - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkjG0tQACgkQwMJqmJVx944W9QCfVR20tGIRYmgx8cjySPtCoBTn 0EoAoMPLMh5onpyqR9LRjWG1Y8yK/Q1Z =05Zi -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
news/leafnode+ - fails: mtree
Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags=-nullfs -plistcheck -onceonly and ccache support, with the official up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/leafnode+-2.15_1.log : building leafnode+-2.15_1 in directory /var/tinderbox/7-STABLE-FTP maintained by: [EMAIL PROTECTED] building for: 7.0-STABLE amd64 port directory: /usr/ports/news/leafnode+ Makefile ident: $FreeBSD: ports/news/leafnode+/Makefile,v 1.31 2006/05/27 12:22:34 pav Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Tue Sep 9 20:25:05 UTC 2008 .Last 40 lines of the log.. : warning: warning: mktemp() possibly used unsafely; consider using mkstemp() cc -O2 -fno-strict-aliasing -pipe -DHAVE_POSIX_REGCOMP -DINET6 -c checkgroups.c cc -O2 -fno-strict-aliasing -pipe -DHAVE_POSIX_REGCOMP -DINET6 -o checkgroups checkgroups.o -L. -lutil ./libutil.a(xoverutil.o)(.text+0x796): In function `getxover': : warning: warning: mktemp() possibly used unsafely; consider using mkstemp() cc -O2 -fno-strict-aliasing -pipe -DHAVE_POSIX_REGCOMP -DINET6 -c leaftool.c cc -O2 -fno-strict-aliasing -pipe -DHAVE_POSIX_REGCOMP -DINET6 -o leaftool leaftool.o -L. -lutil ./libutil.a(xoverutil.o)(.text+0x796): In function `getxover': : warning: warning: mktemp() possibly used unsafely; consider using mkstemp() phase 5: make test make: don't know how to make regression-test(continuing) phase 6: make install add_pkg === Installing for leafnode+-2.15_1 === Generating temporary packing list === Checking if news/leafnode+ already installed === Copying documents to /usr/local/share/doc/leafnode+ === Compressing manual pages for leafnode+-2.15_1 === Registering installation for leafnode+-2.15_1 phase 7: make package === Building package for leafnode+-2.15_1 Creating package /tmp/packages/All/leafnode+-2.15_1.tbz Registering depends:. Creating bzip'd tar ball in '/tmp/packages/All/leafnode+-2.15_1.tbz' Deleting leafnode+-2.15_1 === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 28743394 drwxr-xr-x2 root wheel 512 Sep 9 20:25 usr/local/share/doc/leafnode+ 2874340 16 -r--r--r--1 root wheel7954 Sep 9 20:25 usr/local/share/doc/leafnode+/Changes 28743418 -r--r--r--1 root wheel3834 Sep 9 20:25 usr/local/share/doc/leafnode+/FAQ 28743424 -r--r--r--1 root wheel1681 Sep 9 20:25 usr/local/share/doc/leafnode+/INSTALL 2874343 12 -r--r--r--1 root wheel4930 Sep 9 20:25 usr/local/share/doc/leafnode+/README 28743448 -r--r--r--1 root wheel2156 Sep 9 20:25 usr/local/share/doc/leafnode+/config.example build of /usr/ports/news/leafnode+ ended at Tue Sep 9 20:25:13 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/testing_process.txt Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - [EMAIL PROTECTED], PGP Key ID 057E9F8B493A297B ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
palm/plucker - fails: manpage
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags=-nullfs -plistcheck -onceonly
and ccache support, with the official up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes.
Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/plucker-1.8_2.log :
building plucker-1.8_2 in directory /var/tinderbox/7-STABLE-FTP
maintained by: [EMAIL PROTECTED]
building for: 7.0-STABLE amd64
port directory: /usr/ports/palm/plucker
Makefile ident: $FreeBSD: ports/palm/plucker/Makefile,v 1.17 2007/05/19
20:20:26 flz Exp $
prefixes: LOCALBASE=usr/local X11BASE=usr/local
NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes
build started at Tue Sep 9 21:14:33 UTC 2008
.Last 40 lines of the log..
cd /work/a/ports/palm/plucker/work/plucker-1.8; find PyPlucker \( -name *.py
-or -name *.py? \) -exec install -o root -g wheel -m 444 {}
/usr/local/lib/python2.5/site-packages/{} \;
install -o root -g wheel -m 555
/work/a/ports/palm/plucker/work/plucker-1.8/PyPlucker/Spider.py
/usr/local/lib/python2.5/site-packages/PyPlucker
install -o root -g wheel -m 555
/work/a/ports/palm/plucker/work/plucker-1.8/PyPlucker/PluckerDocs.py
/usr/local/lib/python2.5/site-packages/PyPlucker
install -o root -g wheel -m 555
/work/a/ports/palm/plucker/work/plucker-1.8/PyPlucker/Decode.py
/usr/local/lib/python2.5/site-packages/PyPlucker
/bin/ln -sf /usr/local/lib/python2.5/site-packages/PyPlucker/Spider.py
/usr/local/bin/plucker-build
/bin/ln -sf /usr/local/lib/python2.5/site-packages/PyPlucker/PluckerDocs.py
/usr/local/bin/plucker-decode
/bin/ln -sf /usr/local/lib/python2.5/site-packages/PyPlucker/Decode.py
/usr/local/bin/plucker-dump
/bin/mkdir -p /usr/local/share/plucker
install -o root -g wheel -m 444
/work/a/ports/palm/plucker/work/plucker-1.8/PluckerUserGuide.pdb
/work/a/ports/palm/plucker/work/plucker-1.8/*.prc /usr/local/share/plucker
/bin/mkdir -p /usr/local/etc/plucker
install -o root -g wheel -m 444
/work/a/ports/palm/plucker/work/plucker-1.8/exclusionlist.txt
/usr/local/etc/plucker/exclusionlist.txt.sample
install -o root -g wheel -m 444
/work/a/ports/palm/plucker/work/plucker-1.8/home.html
/usr/local/etc/plucker/home.html.sample
install -o root -g wheel -m 444
/work/a/ports/palm/plucker/work/plucker-1.8/pluckerrc.sample
/usr/local/etc/plucker
/bin/mkdir -p /usr/local/share/plucker/fonts
install -o root -g wheel -m 444
/work/a/ports/palm/plucker/work/plucker-1.8/fonts/*
/usr/local/share/plucker/fonts
/bin/mkdir -p /usr/local/share/plucker/ppi
install -o root -g wheel -m 444
/work/a/ports/palm/plucker/work/plucker-1.8/ppi/* /usr/local/share/plucker/ppi
/bin/mkdir -p /usr/local/share/plucker/xlit
install -o root -g wheel -m 444
/work/a/ports/palm/plucker/work/plucker-1.8/xlit/* /usr/local/share/plucker/xlit
=== Compressing manual pages for plucker-1.8_2
gzip: can't stat: /usr/local/man/man1/plucker-build.1: No such file or directory
gzip: can't stat: /usr/local/man/man1/plucker-decode.1: No such file or
directory
gzip: can't stat: /usr/local/man/man1/plucker-dump.1: No such file or directory
=== Registering installation for plucker-1.8_2
phase 7: make package
=== Building package for plucker-1.8_2
tar: man/man1/plucker-build.1.gz: Cannot stat: No such file or directory
tar: man/man1/plucker-decode.1.gz: Cannot stat: No such file or directory
tar: man/man1/plucker-dump.1.gz: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
Creating package /tmp/packages/All/plucker-1.8_2.tbz
Registering depends: ImageMagick-6.4.3.6 libxml2-2.6.32 ghostscript8-8.62_5
pilot-link-0.12.2,1 libiconv-1.11_1 libltdl-1.5.26 fontconfig-2.5.0,1
freetype2-2.3.7 libXext-1.0.3,1 libXt-1.0.5_1 libX11-1.1.3_1,1 libXdmcp-1.0.2_1
libXau-1.0.3_2 libSM-1.0.3_1,1 libICE-1.0.4_1,1 xproto-7.0.10_1
pkg-config-0.23_1 jasper-1.900.1_6 ppmtoTbmp-1.1 netpbm-10.26.56 jbigkit-1.6
tiff-3.8.2_1 jpeg-6b_7 lcms-1.17,1 libfpx-1.2.0.12_1 png-1.2.31 perl-5.8.8_1
python25-2.5.2_3 gsfonts-8.11_4 expat-2.0.1 kbproto-1.0.3 xextproto-7.0.2.
Creating bzip'd tar ball in '/tmp/packages/All/plucker-1.8_2.tbz'
*** Error code 1
Stop in /a/ports/palm/plucker.
build of /usr/ports/palm/plucker ended at Tue Sep 9 21:15:18 UTC 2008
A description of the testing process can be found here:
http://T32.TecNik93.com/FreeBSD/QA-Tindy/testing_process.txt
Thanks for your work on making FreeBSD better,
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - [EMAIL PROTECTED], PGP Key ID 057E9F8B493A297B
Re: devel/libtool15 unconditionally hardcodes autodetected textproc/gsed
On Tue, Sep 09, 2008 at 06:11:44PM +0400, Dmitry Marakasov wrote: * Peter Pentchev ([EMAIL PROTECTED]) wrote: This is definitely a bug, so better send-pr for this issue not to be lost while we're in freeze. What I mean is the following scenario: - libfoo uses libtool for its build - libfoo depends on libbar which depends on GNU sed - during libfoo's build, libbar is built, thus gsed is installed - during libfoo's build, libtool detects gsed installed and remembers it No, as previously built libtool package will be used, which doesn't use gsed for sure. - in libfoo's binary package, there is a shell script that uses gsed, because libtool knows gsed is present on the system - an unsuspecting user installs the libfoo binary package without previously building libbar - the unsuspecting user gets a shell script that tries to run gsed and fails. ... If libtool may put gsed into libfoo's binary package, this should be fixed before the freeze. If libtool only uses gsed during libfoo's build, then it is not a critical problem. Neither seem to be the case for package building. Of course, if Dmitry is more familiar with libtool than I am, and he I am most likely not, knows that libtool does not leave any such files, then I've just wasted everybody's time with unneeded idle speculation, for which I apologize :) but my vision is that the problem will only show itself if you build libtool with gsed installed and then deinstall gsed. Thus, you'll end up with defunct libtool and all ports which have USE_AUTOTOOLS=libtool:15 will fail to build. I have encountered this with x11/libX11, FWIW. The error was 'gsed not found' or something similar. Since this doesn't affect package builds, I don't this this is serious enough to fix duing freeze. But still to be fixed :) Yes, but the releases will be bundled with a 'broken' devel/libtool15 port. Many [new] users could be using this port tree for a rather long time... I have filed PR with the proposed patch: http://www.freebsd.org/cgi/query-pr.cgi?pr=127256 Alexey. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade 'dovecot' failed
--- Backing up the old version --- Uninstalling the old version --- Deinstalling 'dovecot-1.1.2_1' Dovecot is still running. Shall I stop it? [y]? If you do not intend to reinstall Dovecot, you should manually remove the user 'dovecot' (uid='143') and the group 'dovecot' (gid='143'). Cleaning up /var/run/dovecot. [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 227 packages found (-1 +0) (...) done] --- Installing the new version via the port === Installing for dovecot-1.1.3 === dovecot-1.1.3 depends on shared library: iconv.3 - found === dovecot-1.1.3 depends on shared library: mysqlclient.15 - found Dovecot has reserved the groupname 'dovecot' and gid '143': Please resolve these issues and try again: Either remove the conflicting group or if you wish to continue using a legacy group override DOVECOT_GID. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.16784.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=dovecot-1.1.2_1 UPGRADE_PORT_VER=1.1.2_1 make reinstall --- Restoring the old version Dovecot has reserved the groupname 'dovecot' and gid '143': Please resolve these issues and try again: Either remove the conflicting group or if you wish to continue using a legacy group override DOVECOT_GID. pkg_add: install script returned error status ** Command failed [exit code 1]: /usr/sbin/pkg_add -f /var/tmp/portupgrade7wXzzsEk/dovecot-1.1.2_1.tbz --- Skipping 'mail/dovecot' ** Listing the failed packages (-:ignored / *:skipped / !:failed) - mail/dovecot (dovecot-1.1.2_1) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade 'dovecot' failed
On Wed, Sep 10, 2008 at 01:23:01AM +0400, Alex Keda wrote: --- Backing up the old version --- Uninstalling the old version --- Deinstalling 'dovecot-1.1.2_1' Dovecot is still running. Shall I stop it? [y]? ... --- Restoring the old version Dovecot has reserved the groupname 'dovecot' and gid '143': Please resolve these issues and try again: Either remove the conflicting group or if you wish to continue using a legacy group override DOVECOT_GID. pkg_add: install script returned error status ** Command failed [exit code 1]: /usr/sbin/pkg_add -f /var/tmp/portupgrade7wXzzsEk/dovecot-1.1.2_1.tbz --- Skipping 'mail/dovecot' ** Listing the failed packages (-:ignored / *:skipped / !:failed) - mail/dovecot (dovecot-1.1.2_1) Just a guess, are you running nscd? I've encountered problems with it caching stale information and ports running into trouble because of it. I haven't had time to report it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
