[update] graphics/py-soya3d
update to 0.15rc1
diff -ruN py-soya3d/Makefile py-soya3d.new/Makefile
--- py-soya3d/Makefile 2010-04-28 01:58:27.0 +0400
+++ py-soya3d.new/Makefile 2011-11-25 14:26:36.0 +0400
@@ -6,12 +6,12 @@
#
PORTNAME= soya3d
-PORTVERSION= 0.14
-PORTREVISION= 5
+DISTVERSION= 0.15rc1
+PORTREVISION= 1
CATEGORIES=graphics python
MASTER_SITES= http://download.gna.org/soya/
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
-DISTNAME= Soya-${PORTVERSION}
+DISTNAME= Soya-${DISTVERSION}
DISTFILES= ${DISTNAME}${EXTRACT_SUFX}
DIST_SUBDIR= python
@@ -55,6 +55,9 @@
@${REINPLACE_CMD} -e \
's|%%LOCALBASE%%|${LOCALBASE}|g' -e \
's|/usr/include|${LOCALBASE}/include|g'
${WRKSRC}/setup.py
+#Replace bad file (content binary simbols)
+ @${RM} ${WRKSRC}/editor/world.py && \
+ ${CP} ${FILESDIR}/world.py ${WRKSRC}/editor
post-install:
.if !defined(NOPORTEXAMPLES)
diff -ruN py-soya3d/distinfo py-soya3d.new/distinfo
--- py-soya3d/distinfo 2011-07-03 18:12:02.0 +0400
+++ py-soya3d.new/distinfo 2011-11-25 14:24:56.0 +0400
@@ -1,4 +1,4 @@
-SHA256 (python/Soya-0.14.tar.bz2) =
dcb93206d7154dc575ec6eeb7fa3ecfd6bfb78fa233db639e423857cd2a99590
-SIZE (python/Soya-0.14.tar.bz2) = 905659
+SHA256 (python/Soya-0.15rc1.tar.bz2) =
2567714bc312a171bb5b31cb854804a78cff878e8d5cd2352cf37f48c8eb6dd6
+SIZE (python/Soya-0.15rc1.tar.bz2) = 910576
SHA256 (python/SoyaTutorial-0.14.tar.bz2) =
86d5b8189e7f7b4269976a65f23a51291bb99c6272f2884cbd129a6e9cc6cbec
SIZE (python/SoyaTutorial-0.14.tar.bz2) = 5223674
diff -ruN py-soya3d/files/patch-setup.py py-soya3d.new/files/patch-setup.py
--- py-soya3d/files/patch-setup.py 2009-04-27 05:16:35.0 +0400
+++ py-soya3d.new/files/patch-setup.py 2011-11-25 14:24:56.0 +0400
@@ -1,14 +1,6 @@
setup.py 2009-04-22 10:00:23.0 -0500
-+++ setup.py 2009-04-22 10:03:23.0 -0500
-@@ -21,6 +21,7 @@
-
- # Modify the following if needed :
- USE_OPENAL = 1 # use OpenAL
-+HAVE_PYREX = 0
- #USE_OPENAL = 0
-
- # Modify the following if needed :
-@@ -32,7 +33,7 @@
+--- setup.py.bak 2010-01-19 00:39:57.0 +0300
setup.py 2011-11-25 05:43:09.0 +0400
+@@ -32,7 +32,7 @@
INCDIR = [
#"ode-0.5/include",
"/usr/include",
@@ -17,7 +9,7 @@
"/usr/X11R6/include",
"/usr/X11/include",
"/usr/include/freetype2",
-@@ -48,7 +49,7 @@
+@@ -48,7 +48,7 @@
LIBDIR = [
#"ode-0.5/lib",
"/usr/lib",
@@ -26,19 +18,26 @@
"/opt/local/lib", # For Mac OS X "darwin port"
"/usr/X11R6/lib",
"/usr/X11/lib",
-@@ -79,11 +80,6 @@
+@@ -81,12 +81,12 @@
SDISTING = ("sdist" in sys.argv[1:]) and not ("--help" in sys.argv[1:])
MACOSX_DEPLOYMENT_TARGET = os.getenv('MACOSX_DEPLOYMENT_TARGET')
-try:
- from Pyrex.Distutils import build_ext
-- HAVE_PYREX = 1
--except:
-- HAVE_PYREX = 0
-
- # Only enable Pyrex compilation for SVN sources
- if not os.path.exists(os.path.join(os.path.dirname(__file__), ".svn")):
-@@ -159,6 +155,7 @@
+- USE_PYREX = 1
+-except ImportError:
+- USE_PYREX = 0
+- print "No Pyrex found"
++#try:
++# from Pyrex.Distutils import build_ext
++# USE_PYREX = 1
++#except ImportError:
++USE_PYREX = 0
++# print "No Pyrex found"
+
+ if USE_PYREX: print "Pyrex compilation enabled!"
+ else: print "Pyrex compilation disabled."
+@@ -172,6 +172,7 @@
DEFINES.append(('SOYA_MACOSX',1))
else:
LIBS.append("openal")
diff -ruN py-soya3d/files/world.py py-soya3d.new/files/world.py
--- py-soya3d/files/world.py1970-01-01 03:00:00.0 +0300
+++ py-soya3d.new/files/world.py2011-11-25 14:24:56.0 +0400
@@ -0,0 +1,723 @@
+# -*- indent-tabs-mode: t -*-
+
+# Soya 3D
+# Copyright (C) 2001-2002 Jean-Baptiste LAMY
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+
+
+from editobj.observe import *
+import editobj.custom as custom
+import Tkinter, time, weakref
+import soya, soya.opengl, soya.sdlconst, soya.cube as cube, soya.cursor as
cursor
+
+STEP= 0.125
+EPSILON = 0.001
+
+# Additionnal key binding. (A dict mapping key ID to a lambda taking 2 args,
the root world and the edited object).
+KEY_BINDINGS = {}
+
+class WorldEdito
pr# for 9->10 problem?
There is a problem building various ports caused by the FreeBSD major version number going from 9 to 10 (specifically, from single to double digits). My morning brain has been unable to find this in the PR database; would some kind soul please help? Thanks, Robert Huff ___ 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"
-fstack-protector again (rpm4, BROKEN textproc/libextractor)
Hi!
I got a report that textproc/libextractor was marked BROKEN on
i386 which one of my ports uses, so with the help of swill's tb
(I don't really use i386 myself here anymore so thanx for that :)
I took a look. The failed libextractor log seem to be this one:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20110914141638/libextractor-0.6.2_4.log
The problem:
[...]
checking for rpmReadPackageFile in -lrpm... no
[...]
===> Building package for libextractor-0.6.2_4
tar: lib/libextractor/libextractor_rpm.la: Cannot stat: No such file or
directory
tar: lib/libextractor/libextractor_rpm.so: Cannot stat: No such file or
directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** Error code 1
[...]
The config.log from swill's tb reveals:
[...]
configure:19183: checking for rpmReadPackageFile in -lrpm
configure:19208: cc -o conftest -fno-strict-aliasing -O2 -pipe -fno-strict-alias
ing -I/usr/local/include -L/usr/local/lib -L/usr/local/lib -L/usr/local/lib/qt4
conftest.c -lrpm >&5
/usr/local/lib/librpm.so: undefined reference to `__stack_chk_fail_local'
configure:19208: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "libextractor"
| #define PACKAGE_TARNAME "libextractor"
| #define PACKAGE_VERSION "0.6.2"
| #define PACKAGE_STRING "libextractor 0.6.2"
| #define PACKAGE_BUGREPORT "bug-libextrac...@gnu.org"
| #define PACKAGE_URL ""
| #define PACKAGE "libextractor"
| #define VERSION "0.6.2"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define __EXTENSIONS__ 1
| #define _ALL_SOURCE 1
| #define _GNU_SOURCE 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR ".libs/"
| #define LT_MODULE_EXT ".so"
| #define LT_MODULE_PATH_VAR "LD_LIBRARY_PATH"
| #define LT_DLSEARCH_PATH "/lib:/usr/lib"
| #define HAVE_LIBDL 1
| #define HAVE_DLERROR 1
| #define HAVE_LIBDLLOADER 1
| #define error_t int
| #define __error_t_defined 1
| #define HAVE_PRELOADED_SYMBOLS 1
| #define HAVE_LTDL 1
| #define HAVE_UNISTD_H 1
| #define HAVE_DIRENT_H 1
| #define HAVE_CLOSEDIR 1
| #define HAVE_OPENDIR 1
| #define HAVE_READDIR 1
| #define HAVE_STRLCAT 1
| #define HAVE_STRLCPY 1
| #define LT_LIBEXT "a"
| #define SOMEBSD 1
| #define HAVE_LIBC_R 1
| #define HAVE_ICONV 1
| #define ICONV_CONST const
| #define LOCALEDIR "/usr/local/share/locale"
| #define ISOLOCALEDIR "/usr/share/locale"
| #define HAVE_FSEEKO 1
| #define HAVE_LIBSTDC__ 1
| #define HAVE_LANGINFO_H 1
| #define HAVE_VORBIS_VORBISFILE_H 1
| #define HAVE_VORBISFILE 1
| #define HAVE_FLAC_ALL_H 1
| #define HAVE_FLAC 1
| #define HAVE_FLAC 1
| #define HAVE_ZLIB_H 1
| #define HAVE_ZLIB 1
| #define HAVE_BZLIB_H 1
| #define HAVE_LIBBZ2 1
| /* end confdefs.h. */
|
| /* Override any GCC internal prototype to avoid an error.
|Use char because int might match the return type of a GCC
|builtin and then its argument prototype would still apply. */
| #ifdef __cplusplus
| extern "C"
| #endif
| char rpmReadPackageFile ();
| int
| main ()
| {
| return rpmReadPackageFile ();
| ;
| return 0;
| }
configure:19217: result: no
[...]
So the problem is this:
/usr/local/lib/librpm.so: undefined reference to `__stack_chk_fail_local'
which according to list archives happens/can happen [1] when one
links code built with -fstack-protector to code that wasn't, and
archivers/rpm4's configure script autodetects that the compiler
supports -fstack-protector and then proceeds to using it:
[...]
checking supported compiler flags...
-fno-strict-aliasing
-fstack-protector
checking for special C compiler options needed for large files... no
[...]
..while libextractor's doesn't. So I came up with this (untested)
patch for archivers/rpm4: (maintainers Cc'd, of course we'd want a
PORTREVISION bump there too.)
Index: Makefile
===
RCS file: /home/pcvs/ports/archivers/rpm4/Makefile,v
retrieving revision 1.38
diff -u -p -r1.38 Makefile
--- Makefile7 Oct 2011 14:33:17 - 1.38
+++ Makefile9 Dec 2011 17:24:09 -
@@ -101,6 +101,16 @@ LIB_DEPENDS+= lzma:${PORTSDIR}/archivers
.endif
post-patch:
+# disable -fstack-protector on i386 as that causes librpm clients
+# not using -fstack-protector faling to link there, like the autoconf
+# check in textproc/libextractor:
+#
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20110914141638/libextractor-0.6.2_4.log
+# [...] checking for rpmReadPackageFile in -lrpm... no [...]
+# (for some reason only 8/i386 is affected, 7/i386 and 8/amd64 are not.)
+.if ${ARCH} == "i386"
+ ${REINPLACE_CMD} -e '/cflags_to_try=/s/-fstack-protector//' \
+ ${WRKSRC}/configure
Update tutorial about Centreon and FreeBSD
Hi Friends, I just posted on my blog an update installation of Centreon in FreeBSD is now available a complete tutorial and revised on versions 2.3.3 (last) in an environment with Centreon and FreeBSD 9.0-RC3 Check in: http://www.luizgustavo.pro.br/blog/2011/12/09/english-centreon-2-3-3-freebsd-9/ Thanks -- Luiz Gustavo Costa (Powered by BSD) *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ mundoUnix - Consultoria em Software Livre http://www.mundounix.com.br ICQ: 2890831 / MSN: cont...@mundounix.com.br Tel: 55 (21) 4063-7110 / 8194-1905 / (11) 4063-0407 Blog: http://www.luizgustavo.pro.br ___ 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# for 9->10 problem?
On 12/09/2011 09:06, Robert Huff wrote: > > There is a problem building various ports caused by the FreeBSD > major version number going from 9 to 10 (specifically, from single > to double digits). > My morning brain has been unable to find this in the PR > database; would some kind soul please help? Read /usr/ports/UPDATING? -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/apache13 forbidden because: CVE-2011-3368, no patches against this issue build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=apache13 portname: www/apache13+ipv6 forbidden because: CVE-2011-3368, no patches against this issue build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=apache13%2Bipv6 portname: www/apache13-ssl forbidden because: CVE-2011-3368, no patches against this issue build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=apache13-ssl portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ 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"
FreeBSD unmaintained ports which are currently scheduled for deletion
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: archivers/bsdar description:BSD-licensed replacement of the ar utility maintainer: po...@freebsd.org status: IGNORE deprecated because: part of the base system expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=bsdar portname: audio/gnowavcut description:A GNOME/GTK+ based RIFF PCM Wave file splitter maintainer: po...@freebsd.org deprecated because: Abandonware expiration date:2011-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gnowavcut portname: cad/gtkwave description:Electronic Waveform Viewer maintainer: po...@freebsd.org deprecated because: No more public distfiles, no more upstream expiration date:2011-12-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=gtkwave portname: converters/py-iconvcodec description:Universal unicode codec using iconv(3) for Python maintainer: po...@freebsd.org deprecated because: Included into python itself since version 2.4 expiration date:2011-12-11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=converters&portname=py-iconvcodec portname: databases/clip description:Object oriented, xBase and Clipper language compatible compiler maintainer: po...@freebsd.org deprecated because: No develop anymore for long expiration date:2011-12-07 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20111206112917/clip-1.2.0.0_4.log (_Dec__7_04:40:51_UTC_2011) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=clip portname: databases/fireprofile description:Library to help profiling where programs are using MySQL maintainer: po...@freebsd.org status: BROKEN deprecated because: expiration date:2011-11-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=fireprofile portname: databases/keximdb description:MS Access import plugin for Kexi maintainer: po...@freebsd.org deprecated because: Depends on editors/koffice-kde3, which is scheduled for deletion expiration date:2011-11-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=keximdb portname: devel/kdevelop description:IDE for a wide variety of programming tasks maintainer: po...@freebsd.org status: BROKEN deprecated because: expiration date:2011-11-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=kdevelop portname: devel/libgetline description:A small, portable, and easy to use command line library maintainer: po...@freebsd.org deprecated because: Upstream disapear and distfile is no more available expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=libgetline portname: editors/koffice-kde3 description:Office Suite for KDE3 maintainer: po...@freebsd.org status: BROKEN deprecated because: expiration date:2011-11-30 build errors: http://pointyhat.FreeBSD.org/errorlogs/powerpc-errorlogs/e.8.20100815051156/koffice-1.6.3_13,2.log.bz2 (_Aug_27_21:21:39_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=koffice-kde3 portname: emulators/wahcade description:A frontend for almost any emulator (MameWAH clone) maintainer: po...@freebsd.org status: BROKEN deprecated because: expiration date:2011-11-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=wahcade portname: japanese/py-kanjilib description:Ja
FreeBSD unmaintained ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/csound broken because: does not package build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.2021102805/csound-5.13.log (_Nov__6_18:09:23_UTC_2011) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=csound portname: audio/tclmidi broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=tclmidi portname: audio/teamspeak_client broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=teamspeak_client portname: benchmarks/dbs broken because: does not compile on FreeBSD 9.X build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=dbs portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=big5con portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=hztty portname: chinese/kon2 broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=kon2 portname: databases/fireprofile broken because: Needs modification to work with newer MySQL build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=fireprofile portname: databases/msql broken because: Broken on FreeBSD 9+ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=msql portname: devel/dsss broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=dsss portname: devel/fastcrc broken because: Does not compile on recent FreeBSD-9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fastcrc portname: devel/gcvs broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gcvs portname: devel/kdevelop broken because: conflicting dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=kdevelop portname: devel/linux-js broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-js portname: devel/linuxthreads broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linuxthreads portname: devel/p5-Dialog broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-Dialog port
Re: pr# for 9->10 problem?
Doug Barton writes: > >There is a problem building various ports caused by the FreeBSD > > major version number going from 9 to 10 (specifically, from single > > to double digits). > >My morning brain has been unable to find this in the PR > > database; would some kind soul please help? > > Read /usr/ports/UPDATING? If you mean 20110928 - that identifies the problem, and provides workarounds, but does not name the pr. Robert Huff ___ 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# for 9->10 problem?
On 12/09/2011 12:20, Robert Huff wrote: > > Doug Barton writes: > >> > There is a problem building various ports caused by the FreeBSD >> > major version number going from 9 to 10 (specifically, from single >> > to double digits). >> > My morning brain has been unable to find this in the PR >> > database; would some kind soul please help? >> >> Read /usr/ports/UPDATING? > > If you mean 20110928 - that identifies the problem, and > provides workarounds, but does not name the pr. What are you trying to accomplish? -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: again, ports that stop daemons
On Sat, Dec 03, 2011 at 01:09:09AM +0200, Andriy Gapon wrote: > on 02/12/2011 21:55 Baptiste Daroussin said the following: > > On Fri, Dec 02, 2011 at 08:38:05PM +0100, Torfinn Ingolfsen wrote: > >> On Fri, Dec 2, 2011 at 1:13 PM, Andriy Gapon wrote: > >>> > >>> Or that they simply quit doing that and instead print a message like > >>> "Port X is > >>> deinstalled but it may have some processes running, please do Y and/or Z > >>> to find > >>> them and/or stop them". > >> > >> I prefer this suggestion. > > > > I also would prefer this. > > > BTW, this part of my suggestion was inspired by the following: > http://en.opensuse.org/SDB:Zypper_usage_11.3#Check_processes > > Not sure how that feature is implemented though. > FYI, since a few minutes, pkgng handle rc scripts, disabled by default because I still consider this feature dangerous. to activate it is: HANDLE_RC_SCRIPTS=yes in pkg.conf In the future I want to allow the users to add a list of globbing to be able to blacklist some of the packages where users don't want to see the scripts handled. BTW this is automatic, no need to have the ports tree handle it. regards, Bapt pgpwYwlwfihRQ.pgp Description: PGP signature
Re: again, ports that stop daemons
On 12/09/2011 13:18, Baptiste Daroussin wrote: > On Sat, Dec 03, 2011 at 01:09:09AM +0200, Andriy Gapon wrote: >> on 02/12/2011 21:55 Baptiste Daroussin said the following: >>> On Fri, Dec 02, 2011 at 08:38:05PM +0100, Torfinn Ingolfsen wrote: On Fri, Dec 2, 2011 at 1:13 PM, Andriy Gapon wrote: > > Or that they simply quit doing that and instead print a message like > "Port X is > deinstalled but it may have some processes running, please do Y and/or Z > to find > them and/or stop them". I prefer this suggestion. >>> >>> I also would prefer this. >> >> >> BTW, this part of my suggestion was inspired by the following: >> http://en.opensuse.org/SDB:Zypper_usage_11.3#Check_processes >> >> Not sure how that feature is implemented though. >> > FYI, since a few minutes, pkgng handle rc scripts, disabled by default > because I > still consider this feature dangerous. > to activate it is: > HANDLE_RC_SCRIPTS=yes in pkg.conf I previously described what I thought was a pretty good way to handle this question that addressed the needs expressed by all of the posters on the previous thread, but my suggestion didn't get any responses. Since this has come up again, it would be helpful (to me at least) if people would think about my idea, and if nothing else tell me why I'm wrong. :) Quoting: Speaking only for myself I hate the idea of stopping/starting services automatically. However this feature is often requested, and is something that is provided by many other package systems. If we have people who are willing to do the work I think it's worth discussing how to do it properly. The way that I envision it working would be a 3-knob system. One knob to always restart the services, one to never do it; and then asking on a per-port basis, which should be the default. I can imagine portmaster detecting this option in the pre-build phase similarly to how it detects and warns about IS_INTERACTIVE now, and giving the user a menu of options for how to handle it. I'm happy to add more details if people are interested. Where this actually becomes interesting is not in the ports build/install process, which is pretty easy to deal with, but with package installs/deinstalls. I definitely think it's doable, what we probably want to do is put a knob for this in the port's Makefile, and handle the stop/start for both the port and the package with a little script that can be included in the package, and run with @exec and @unexec. -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: kdelibs4 4.7.3 Build Fails FreeBSD 9-CURRENT
All installed and working. Needed to reinstall some packages first and then it went just fine. Thanks, ___ 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: kdelibs4 4.7.3 Build Fails FreeBSD 9-CURRENT
Had some similar issues with kdelibs4 4.7.3 on a fresh FreeBSD 9.0 RC2 amd64 system. I just did a 'make -j1' and it built fine. Ben Franklan > Trying to update from KDE 4.7.2 to 4.7.3 on FreeBSD 9.0-CURRENT #0: Tue > Jul 19 16:18:20 PDT 2011. I have run into the following error > repeatedly now and cannot find a similar error using google. I believe > that I have used the default options for KDE. [snip] > 1 error > *** Error code 2 > 1 error > *** Error code 1 ___ 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: again, ports that stop daemons
On Fri, Dec 09, 2011 at 01:25:25PM -0800, Doug Barton wrote: > On 12/09/2011 13:18, Baptiste Daroussin wrote: > > On Sat, Dec 03, 2011 at 01:09:09AM +0200, Andriy Gapon wrote: > >> on 02/12/2011 21:55 Baptiste Daroussin said the following: > >>> On Fri, Dec 02, 2011 at 08:38:05PM +0100, Torfinn Ingolfsen wrote: > On Fri, Dec 2, 2011 at 1:13 PM, Andriy Gapon wrote: > > > > Or that they simply quit doing that and instead print a message like > > "Port X is > > deinstalled but it may have some processes running, please do Y and/or > > Z to find > > them and/or stop them". > > I prefer this suggestion. > >>> > >>> I also would prefer this. > >> > >> > >> BTW, this part of my suggestion was inspired by the following: > >> http://en.opensuse.org/SDB:Zypper_usage_11.3#Check_processes > >> > >> Not sure how that feature is implemented though. > >> > > FYI, since a few minutes, pkgng handle rc scripts, disabled by default > > because I > > still consider this feature dangerous. > > to activate it is: > > HANDLE_RC_SCRIPTS=yes in pkg.conf > > I previously described what I thought was a pretty good way to handle > this question that addressed the needs expressed by all of the posters > on the previous thread, but my suggestion didn't get any responses. > Since this has come up again, it would be helpful (to me at least) if > people would think about my idea, and if nothing else tell me why I'm > wrong. :) And I previously read what you already said, but thanks, for providing your opinion again that help to see how our implementation matches user idea > > Quoting: > > Speaking only for myself I hate the idea of stopping/starting services > automatically. However this feature is often requested, and is something > that is provided by many other package systems. If we have people who > are willing to do the work I think it's worth discussing how to do it > properly. Completly agree that is why it is also deactivated by default. > > The way that I envision it working > would be a 3-knob system. One knob to always restart the services, one > to never do it; and then asking on a per-port basis, which should be the > default. I can imagine portmaster detecting this option in the pre-build > phase similarly to how it detects and warns about IS_INTERACTIVE now, > and giving the user a menu of options for how to handle it. I'm happy to > add more details if people are interested. > > Where this actually becomes interesting is not in the ports > build/install process, which is pretty easy to deal with, but with > package installs/deinstalls. I definitely think it's doable, what we > probably want to do is put a knob for this in the port's Makefile, and > handle the stop/start for both the port and the package with a little > script that can be included in the package, and run with @exec and @unexec. > I really do think this a package management feature, not a port feature, the way this is now done, in pkgng is mostly what you have says, except for the interactive one. the way it is handle in pkgng can work both for binary package and for source upgrade (here goes portmaster :)) transparently, it will handle all the rc scripts without forgetting one, not relying on what can be set or forgotten by the maintainer. I hate interactive packages, that is why I didn't add the interactive way, but patches are welcome to add interactive rc script management in pkgng :). regards, Bapt pgpgMkE4kg8VP.pgp Description: PGP signature
Clicking URLs with acroread8
I receive PDF documents with URLs that I need to click, and so I would like to get that working in acroread8. I symlink'ed firefox into /compat/linux/usr/local/bin, and set the preferences in acroread accordingly. That got me from a "firefox not found" error to this, printed out in the terminal: libfam.so.0: cannot open shared object file: No such file or directory Failed to load module: /usr/lib/gio/modules/libgiofam.so Since I have that lib installed as a result of the linux-base port, I assume that what is missing is something that it depends on. Any help resolving this is welcome. Alternatively, if I could extract the URL from the link, that'd be awesome too. :) Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
astro/xephem: make readme failure
>Submitter-Id: current-users >Originator:Conrad J. Sabatier >Organization: >Confidential: no >Synopsis: astro/xephem: make readme failure >Severity: non-critical >Priority: low >Category: ports >Class: sw-bug >Release: FreeBSD 9.0-PRERELEASE amd64 >Environment: System: FreeBSD serene.no-ip.org 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #0: Tue Dec 6 17:44:31 CST 2011 conr...@serene.no-ip.org:/usr/obj/usr/src/sys/CUSTOM amd64 >Description: "make readme" in $PORTSDIR/astro/xephem fails as follows: root:/usr/ports/astro/xephem# make readme ===> Creating README.html for xephem-3.7.4_3printf: illegal option -- n usage: printf format [arguments ...] printf: illegal option -- n usage: printf format [arguments ...] printf: illegal option -- n usage: printf format [arguments ...] sed: 1: "s|%%WEBSITE%%|*** Error ...": unescaped newline inside substitute pattern *** Error code 1 Stop in /usr/ports/astro/xephem. *** Error code 1 Stop in /usr/ports/astro/xephem. >How-To-Repeat: cd /usr/ports/astro/xephem make readme >Fix: (unknown) ___ 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"
