INDEX build failed for 8.x
INDEX build failed with errors: Generating INDEX-8 - please wait../home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 199: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 200: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 201: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 203: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 204: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 206: warning: duplicate script for target pre-install ignored Done. make_index: Circular dependency loop found: remmina-plugin-i18n-1.0.0_1 depends upon itself. Committers on the hook: cy danfe erwin fluffy miwi ohauer tabthorpe vanilla Most recent SVN update was: Updating '.': Usecurity/vuxml/vuln.xml Dnet/osrtspproxy/pkg-plist Unet/osrtspproxy/Makefile Unet/poptop/pkg-plist Unet/poptop/Makefile Unet/poptop/distinfo Unet/poptop/pkg-descr Unet/poptop/files/patch-defaults.h Unet/poptop/files/patch-plugins_Makefile Unet/poptop/files/patch-plugins_pptpd-logwtmp.c Unet/poptop/files/patch-Makefile.in Unet/poptop/files/patch-pptpd.c Unet/poptop/files/patch-pptpctrl.c Unet-mgmt/bpft/pkg-plist Unet-mgmt/bpft/Makefile UU www/privoxy/pkg-plist Uwww/privoxy/Makefile UU www/privoxy/files/privoxy.in UU www/privoxy/files/pkg-message.in Uwww/piwik/pkg-plist Uwww/piwik/Makefile Uwww/piwik/distinfo Udevel/cvstrac/Makefile Ddevel/cvstrac/files/patch-main.mk Ddevel/cvstrac/files/patch-Makefile Utextproc/rubygem-markaby/Makefile Utextproc/rubygem-markaby/distinfo Ujapanese/eb/Makefile Umisc/sword17/pkg-plist Umisc/sword17/Makefile Umisc/sword17/distinfo Umisc/bibletime/Makefile Updated to revision 339767. ___ 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 you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ games/xlife | 6.7.5 | 6.7.6 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt 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
FreeBSD 10.0-RC4 pkg upgrade QT conflict
# uname -a FreeBSD mercury.rd.tp.pl 10.0-RC4 FreeBSD 10.0-RC4 #0 r260130: Tue Dec 31 17:10:01 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 # pkg upgrade Updating repository catalogue Upgrades have been requested for the following 27 packages: Upgrading ImageMagick: 6.8.0.7_3 - 6.8.0.7_3,1 Reinstalling docbook-1.4_1 (direct dependency changed) Reinstalling docbook-xsl-1.76.1_1 (direct dependency changed) Upgrading e2fsprogs-libuuid: 1.42.8 - 1.42.9 Reinstalling gnome-doc-utils-0.20.10 (direct dependency changed) Upgrading libewf: 20131210 - 20131230 Upgrading musicpd: 0.17.3_4 - 0.18.5 Upgrading openjdk: 7.45.18 - 7.25.15_2,1 Upgrading qt4-corelib: 4.8.5 - 4.8.5_1 Upgrading qt4-qmake: 4.8.5 - 4.8.5_1 Upgrading redland: 1.0.16 - 1.0.17 Reinstalling xfce4-mpc-plugin-0.4.4_4 (direct dependency changed) Upgrading xfce4-whiskermenu-plugin: 1.3.0 - 1.3.1 Installing qt4-opengl: 4.8.5 Installing qt4-testlib: 4.8.5 Installing qt4-clucene: 4.8.5 Reinstalling mlt-0.9.0_2 (direct dependency changed) Upgrading qt4-qdbusviewer: 4.8.5 - 4.8.5_1 Installing qt4-declarative: 4.8.5 Installing qt4-webkit: 4.8.5_1 Upgrading qt4-assistant: 4.8.5 - 4.8.5_1 Upgrading qt4-linguist: 4.8.5 - 4.8.5_1 Reinstalling qzeitgeist-0.8.0 (direct dependency changed) Reinstalling virtualbox-ose-4.2.20_2 (direct dependency changed) Reinstalling kdelibs-4.10.5_2 (direct dependency changed) Reinstalling kdenlive-0.9.6_2 (direct dependency changed) Reinstalling libkcddb-4.10.5 (direct dependency changed) The upgrade will require 32 MB more space 0 B to be downloaded Proceed with upgrading packages [y/N]: y Checking integrity...pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/QtDeclarative with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-opengl-4.8.5 conflicts on /usr/local/include/qt4/Qt/QtOpenGL with: - qt4-opengl-4.8.5 pkg: WARNING: locally installed qt4-qtestlib-4.8.5 conflicts on /usr/local/include/qt4/Qt/QtTest with: - qt4-testlib-4.8.5 pkg: WARNING: locally installed qt4-webkit-4.8.5 conflicts on /usr/local/include/qt4/Qt/QtWebKit with: - qt4-webkit-4.8.5_1 pkg: WARNING: locally installed qt4-qtestlib-4.8.5 conflicts on /usr/local/include/qt4/Qt/qbenchmark.h with: - qt4-testlib-4.8.5 pkg: WARNING: locally installed qt4-qtestlib-4.8.5 conflicts on /usr/local/include/qt4/Qt/qbenchmarkmetric.h with: - qt4-testlib-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarative.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativecomponent.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativecontext.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativedebug.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativeengine.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativeerror.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativeexpression.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativeextensioninterface.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativeextensionplugin.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativeimageprovider.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativeinfo.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativeitem.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativelist.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativenetworkaccessmanagerfactory.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativeparserstatus.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativeprivate.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/qdeclarativeproperty.h with: - qt4-declarative-4.8.5 pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on
INDEX build failed for 8.x
INDEX build failed with errors: Generating INDEX-8 - please wait../home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 199: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 200: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 201: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 203: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 204: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 206: warning: duplicate script for target pre-install ignored Done. make_index: Circular dependency loop found: remmina-plugin-i18n-1.0.0_1 depends upon itself. Committers on the hook: cy danfe erwin fluffy gahr marino miwi nemysis ohauer tabthorpe vanilla Most recent SVN update was: Updating '.': Utextproc/hevea/Makefile Utextproc/hevea/distinfo Ugames/battletanks/pkg-descr Dgames/battletanks/files/patch-gcc-4.6 Agames/battletanks/files/patch-engine-sl08-sl08.py Agames/battletanks/files/patch-math-range_list.h Ugames/battletanks/files/patch-SConstruct Ugames/battletanks/pkg-plist Ugames/battletanks/Makefile Ugames/bugsquish/pkg-plist Ugames/bugsquish/Makefile UU games/bugsquish/distinfo Unet/yptransitd/pkg-plist Unet/yptransitd/Makefile Ddevel/dcmtk/Makefile.man Udevel/dcmtk/Makefile Udevel/dcmtk/pkg-plist Udevel/distcc/Makefile Updated to revision 339774. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC4 pkg upgrade QT conflict
Le mer 15 jan 14 à 12:47:59 +0100, CeDeROM cede...@tlen.pl écrivait : Checking integrity...pkg: WARNING: locally installed qt4-declarative-4.8.5 conflicts on /usr/local/include/qt4/Qt/QtDeclarative with: - qt4-declarative-4.8.5 Please read UPGRADING (ore pkg upgrading). -- Th. Thomas. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD 10.0-RC4 pkg upgrade QT conflict
Le mer 15 jan 14 à 13:35:36 +0100, Thierry Thomas thie...@freebsd.org écrivait : Please read UPGRADING (ore pkg upgrading). Ooops! UPDATING / pkg updating ! -- Th. Thomas. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Staging net/Sockets
Hello. I'm maintaining net/Sockets, which currently has NO_STAGE=yes added. I believe this is unneeded and no other change is necessary, but I'm quite noob. I've already followed https://wiki.freebsd.org/ports/StageDir and tested with port test, but before I submit an update, can anyone please help me double-checking? bye Thanks av. ___ 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: Staging net/Sockets
On 1/15/2014 14:36, Andrea Venturoli wrote: Hello. I'm maintaining net/Sockets, which currently has NO_STAGE=yes added. I believe this is unneeded and no other change is necessary, but I'm quite noob. I've already followed https://wiki.freebsd.org/ports/StageDir and tested with port test, but before I submit an update, can anyone please help me double-checking? bye Thanks av. I'd be happy to run it through Redports for you sans NO_STAGE line. I'll privately send you the link so you can watch it. John ___ 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
INDEX build failed for 8.x
INDEX build failed with errors: Generating INDEX-8 - please wait../home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 199: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 200: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 201: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 203: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 204: warning: duplicate script for target pre-install ignored /home/indexbuild/tindex/ports/japanese/p5-Mail-SpamAssassin/../../mail/p5-Mail-SpamAssassin/Makefile, line 206: warning: duplicate script for target pre-install ignored Done. make_index: Circular dependency loop found: remmina-plugin-i18n-1.0.0_1 depends upon itself. Committers on the hook: cy danfe erwin fluffy gahr gblach marino miwi nemysis ohauer tabthorpe theraven vanilla Most recent SVN update was: Updating '.': Unet/Sockets/Makefile Ugames/battletanks/Makefile Dgames/battletanks/files/patch-Install UMk/bsd.gnustep.mk Ulang/modula3/Makefile Umultimedia/mpv/pkg-plist Umultimedia/mpv/Makefile Umultimedia/mpv/distinfo Dmultimedia/mpv/files/patch-configure Dmultimedia/mpv/files/patch-stream-tvi_v4l2.c Amultimedia/mpv/files/patch-waftools-checks-custom.py Updated to revision 339779. ___ 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
INDEX now builds successfully on 8.x
___ 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 Port: emulators/virtualbox-ose
Hello, Having trouble compiling on a freshly installed 10.0-PRE, below is the error. The only port options selected are GUESTADDITIONS, VNC, WEBSERVICE. Thanks. kBuild: Compiling tstVMStructRC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/VMM/testcase/tstVMStructRC.cpp kBuild: Linking tstVMStructRC Using built-in specs. COLLECT_GCC=g++46 COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/lto-wrapper Target: x86_64-portbld-freebsd10.0 Configured with: ./../gcc-4.6.4/configure --disable-bootstrap --disable-nls --libdir=/usr/local/lib/gcc46 --libexecdir=/usr/local/libexec/gcc46 --program-suffix=46 --with-as=/usr/local/bin/as --with-gmp=/usr/local --with-gxx-include-dir=/usr/local/lib/gcc46/include/c++/ --with-ld=/usr/local/bin/ld --with-pkgversion='FreeBSD Ports Collection' --with-system-zlib --disable-libgcj --enable-languages=c,c++,objc,fortran --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/gcc46 --build=x86_64-portbld-freebsd10.0 Thread model: posix gcc version 4.6.4 (FreeBSD Ports Collection) COMPILER_PATH=/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../../../x86_64-portbld-freebsd10.0/bin/ LIBRARY_PATH=/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../../../x86_64-portbld-freebsd10.0/lib/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../:/lib/:/usr/lib/ COLLECT_GCC_OPTIONS='-m32' '-g' '-g' '-nostdlib' '-v' '-o' '/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC' '-L/usr/lib32' '-shared-libgcc' '-mtune=generic' '-march=x86-64' /usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/collect2 --eh-frame-hdr -m elf_i386_fbsd -V -dynamic-linker /libexec/ld-elf.so.1 -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC -L/usr/lib32 -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4 -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../../../x86_64-portbld-freebsd10.0/lib -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../.. /usr/lib32/crt1.o /usr/lib32/crti.o /usr/lib32/crtbegin.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC.o /usr/lib32/crtend.o /usr/lib32/crtn.o /usr/lib32/libc.so GNU ld (GNU Binutils) 2.24 Supported emulations: elf_x86_64_fbsd elf_i386_fbsd elf_x86_64 elf_i386 elf_l1om elf_l1om_fbsd elf_k1om elf_k1om_fbsd kBuild: Installing tstVMStructRC = /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/tstVMStructRC kBuild: Generating tstVMStructSize - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/tstVMStructRC: 1: Syntax error: ( unexpected /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/tstVMStructRC: 1: Syntax error: Error in command substitution kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h] Error 2 kmk: *** Deleting file `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h' *** Error code 2 Stop. make[1]: stopped in /usr/ports/emulators/virtualbox-ose *** Error code 1 Stop. make: stopped in /usr/ports/emulators/virtualbox-ose I then tried again but with gcc47 but I got a different errror. Build: Compiling RuntimeBldProg - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/dvm/dvmvfs.cpp In file included from /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/dvm/dvmvfs.cpp:40:0: /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/include/iprt/vfslowlevel.h:217:120: warning: trigraph ??) ignored, use -trigraphs to enable [-Wtrigraphs] kBuild: Compiling RuntimeBldProg - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/err/errinfo.cpp kBuild: Generating /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/Runtime/errmsgdata.h /usr/local/bin/kmk_sed: file /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/err/errmsg.sed line 31: Unmatched [ or [^ kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/Runtime/errmsgdata.h] Error 1
Re: Blanket approval to modernize the Ports Tree
On Tue, 7 Jan 2014, FreeBSD Ports Management Team Secretary wrote: This can be done with implicit portmgr@ blanket approval, and without maintainer approval. Please, however, respect some boundaries, do not change ports belonging to kde@, gnome@ or x11@. These teams work in private repos that may have changes pending. I've had an update for www/magento sent a few months back, which landed in spam. Replied to the bugbuster address and never saw any follow up. Work then took a lot of a time, so I didn't chase this down. Please note however, that I'm working on the 1.8.1.0 upgrade, which will convert to stage in the process. As a precaution, I'll put a link up to the patch, rather then add it to the mail as an attachment. It will be rather big, cause of the conversion to a pkg-plist. In short, hands off please, it's being worked on. ___ 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
USE_PYTHON version range no longer valid?
A port I maintain (sorta) can only be built under Python 2.2.1 through 2.4.x. The app isn't being developed any longer, so patches to get it to build under 2.5+ aren't likely to be forthcoming. The port Makefile previously had USE_PYTHON= 2.2-2.4, but it was changed this week to simply USE_PYTHON=2, with this comment: Python cleanup: - USE_PYTHON* = 2.X - USE_PYTHON* = 2 - USE_PYTHON* = 2.X+ - USE_PYTHON* = yes Reviewed by: python (mva, rm) Approved by: portmgr-lurkers (mat) By removing 2.4 as the maximum version, there are inevitable build errors for this app. Reverting to USE_PYTHON= 2.2-2.4 results in 'make' failing with this: === py27-4suite-1.0.b1_1 needs an unsupported version of Python. I'm fine with that, although I'm unsure what the ramifications are of Python 2.4 being unsupported. Do people have the option of installing Python 2.4.6 and using it with this port, or do we need to decommission the port? ___ 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: USE_PYTHON version range no longer valid?
On Wed, Jan 15, 2014 at 12:47:24PM -0700, Mike Brown wrote: A port I maintain (sorta) can only be built under Python 2.2.1 through 2.4.x. The app isn't being developed any longer, so patches to get it to build under 2.5+ aren't likely to be forthcoming. The port Makefile previously had USE_PYTHON= 2.2-2.4, but it was changed this week to simply USE_PYTHON=2, with this comment: Python cleanup: - USE_PYTHON* = 2.X - USE_PYTHON* = 2 - USE_PYTHON* = 2.X+ - USE_PYTHON* = yes Reviewed by:python (mva, rm) Approved by:portmgr-lurkers (mat) That means that port should either be removed from the ports tree, or one should fork it and port it to newer version of python. Python 2.4- are EOLed upstream for long, we are respecting upstream, so there nothing more we can do about it. regards, Bapt pgp3sGPr1Frr7.pgp Description: PGP signature
Re: USE_PYTHON version range no longer valid?
On, Wed Jan 15, 2014, Mike Brown wrote: A port I maintain (sorta) can only be built under Python 2.2.1 through 2.4.x. The app isn't being developed any longer, so patches to get it to build under 2.5+ aren't likely to be forthcoming. The port Makefile previously had USE_PYTHON= 2.2-2.4, but it was changed this week to simply USE_PYTHON=2, with this comment: Python cleanup: - USE_PYTHON* = 2.X - USE_PYTHON* = 2 - USE_PYTHON* = 2.X+ - USE_PYTHON* = yes Reviewed by:python (mva, rm) Approved by:portmgr-lurkers (mat) By removing 2.4 as the maximum version, there are inevitable build errors for this app. Reverting to USE_PYTHON= 2.2-2.4 results in 'make' failing with this: === py27-4suite-1.0.b1_1 needs an unsupported version of Python. I'm fine with that, although I'm unsure what the ramifications are of Python 2.4 being unsupported. Do people have the option of installing Python 2.4.6 and using it with this port, or do we need to decommission the port? Python 2.4 was removed from the tree ages ago and none of us noticed that this port would be affected by that. Sorry - it should have vanished with the removal of Python 2.4. I'll set a deprecation message along with the expiration date to the 1st of February. It will be removed from the tree after that date. Cheers Marcus pgprsiLUiDJpH.pgp Description: PGP signature
FreeBSD Port: abills-0.54
Why this port version is 0.54 while there is 0.55 version on the http://abills.net.ua/ ? ___ 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: security/libssh does not install ssh_threads
Dima Panov flu...@freebsd.org writes: 14.01.14, 9:29, Peter Klett ?: Hi, I'm currently trying to compile the nogui version of net-p2p/retroshare which has a dependency to libssh-0.5.4. In its Makefile it includes -lssh and -lssh_threads but the later is not build / installed by libssh. [skip] Please update. libssh-0.5.5_1 installs both standard and threaded libs. This is interesting. I ended up trying to find why this was the case and it seems to be us passing -DTHREADS_HAVE_PTHREAD_ARG and libssh checking for the wrong variable to decide whether to build libssh_threads.so. I've sent some patches upstream in http://thread.gmane.org/gmane.network.ssh.libssh.general/1389 ___ 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: security/libssh does not install ssh_threads
Am 2014-01-14 13:41, schrieb Dima Panov: Please update. libssh-0.5.5_1 installs both standard and threaded libs. Thank you! unfortunately I'm getting an error while linking: net-p2p/retroshare/work/retroshare-0.5.5/src/retroshare-nogui/src/ssh/rssshd.cc:38: undefined reference to `ssh_threads_get_pthread' I installed libssh from port, installed version is libssh-0.5.5_1 # ls -l /usr/local/lib/libssh* -rw-r--r-- 1 root wheel 542052 15 Jan 20:17 /usr/local/lib/libssh.a lrwxr-xr-x 1 root wheel 11 15 Jan 21:27 /usr/local/lib/libssh.so - libssh.so.4 lrwxr-xr-x 1 root wheel 15 15 Jan 21:27 /usr/local/lib/libssh.so.4 - libssh.so.4.2.5 -rwxr-xr-x 1 root wheel 254984 15 Jan 21:27 /usr/local/lib/libssh.so.4.2.5 -rw-r--r-- 1 root wheel1072 15 Jan 20:17 /usr/local/lib/libssh_threads.a lrwxr-xr-x 1 root wheel 19 15 Jan 21:27 /usr/local/lib/libssh_threads.so - libssh_threads.so.4 lrwxr-xr-x 1 root wheel 23 15 Jan 21:27 /usr/local/lib/libssh_threads.so.4 - libssh_threads.so.4.2.5 -rwxr-xr-x 1 root wheel3976 15 Jan 21:27 /usr/local/lib/libssh_threads.so.4.2.5 # objdump -T /usr/local/lib/libssh_threads.so.4.2.5 /usr/local/lib/libssh_threads.so.4.2.5: file format elf64-x86-64-freebsd DYNAMIC SYMBOL TABLE: 0420 ld .init .init w DF *UND* 01f1 FBSD_1.0 __cxa_finalize w D *UND* _Jv_RegisterClasses 002007c0 gD *ABS* Base_end 002007b8 gD *ABS* Base_edata 002007b8 gD *ABS* Base __bss_start 0420 gDF .init Base_init 0518 gDF .fini Base_fini I think I'm still missing something. Any hints? Thanks Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: abills-0.54
2014/1/16 Maxim Sirenko ma...@rivne.uar.net: Why this port version is 0.54 while there is 0.55 version on the http://abills.net.ua/ ? May be because you did not submit patches for update the port to the most recent version? ___ 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 -- Mikhail ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: emulators/virtualbox-ose
On Wed, Jan 15, 2014 at 7:58 PM, Mike Jakubik mike.jaku...@intertainservices.com wrote: Hello, Having trouble compiling on a freshly installed 10.0-PRE, below is the error. The only port options selected are GUESTADDITIONS, VNC, WEBSERVICE. Thanks. kBuild: Compiling tstVMStructRC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/VMM/testcase/tstVMStructRC.cpp kBuild: Linking tstVMStructRC Using built-in specs. COLLECT_GCC=g++46 COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/lto-wrapper Target: x86_64-portbld-freebsd10.0 Configured with: ./../gcc-4.6.4/configure --disable-bootstrap --disable-nls --libdir=/usr/local/lib/gcc46 --libexecdir=/usr/local/libexec/gcc46 --program-suffix=46 --with-as=/usr/local/bin/as --with-gmp=/usr/local --with-gxx-include-dir=/usr/local/lib/gcc46/include/c++/ --with-ld=/usr/local/bin/ld --with-pkgversion='FreeBSD Ports Collection' --with-system-zlib --disable-libgcj --enable-languages=c,c++,objc,fortran --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/gcc46 --build=x86_64-portbld-freebsd10.0 Thread model: posix gcc version 4.6.4 (FreeBSD Ports Collection) COMPILER_PATH=/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../../../x86_64-portbld-freebsd10.0/bin/ LIBRARY_PATH=/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../../../x86_64-portbld-freebsd10.0/lib/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../:/lib/:/usr/lib/ COLLECT_GCC_OPTIONS='-m32' '-g' '-g' '-nostdlib' '-v' '-o' '/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC' '-L/usr/lib32' '-shared-libgcc' '-mtune=generic' '-march=x86-64' /usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/collect2 --eh-frame-hdr -m elf_i386_fbsd -V -dynamic-linker /libexec/ld-elf.so.1 -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC -L/usr/lib32 -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4 -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../../../../x86_64-portbld-freebsd10.0/lib -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd10.0/4.6.4/../../.. /usr/lib32/crt1.o /usr/lib32/crti.o /usr/lib32/crtbegin.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC.o /usr/lib32/crtend.o /usr/lib32/crtn.o /usr/lib32/libc.so GNU ld (GNU Binutils) 2.24 Supported emulations: elf_x86_64_fbsd elf_i386_fbsd elf_x86_64 elf_i386 elf_l1om elf_l1om_fbsd elf_k1om elf_k1om_fbsd kBuild: Installing tstVMStructRC = /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/tstVMStructRC kBuild: Generating tstVMStructSize - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/tstVMStructRC: 1: Syntax error: ( unexpected /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/tstVMStructRC: 1: Syntax error: Error in command substitution kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h] Error 2 kmk: *** Deleting file `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h' *** Error code 2 Stop. make[1]: stopped in /usr/ports/emulators/virtualbox-ose *** Error code 1 Stop. make: stopped in /usr/ports/emulators/virtualbox-ose I then tried again but with gcc47 but I got a different errror. Build: Compiling RuntimeBldProg - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/dvm/dvmvfs.cpp In file included from /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/dvm/dvmvfs.cpp:40:0: /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/include/iprt/vfslowlevel.h:217:120: warning: trigraph ??) ignored, use -trigraphs to enable [-Wtrigraphs] kBuild: Compiling RuntimeBldProg - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/err/errinfo.cpp kBuild: Generating /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/Runtime/errmsgdata.h /usr/local/bin/kmk_sed: file /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Runtime/common/err/errmsg.sed line 31: Unmatched [ or [^ kmk:
Re: FreeBSD Port: emulators/virtualbox-ose
On 01/15/14 16:37, Bernhard Fröhlich wrote: On Wed, Jan 15, 2014 at 7:58 PM, Mike Jakubik mike.jaku...@intertainservices.com wrote: Hello, Having trouble compiling on a freshly installed 10.0-PRE, below is the error. The only port options selected are GUESTADDITIONS, VNC, WEBSERVICE. Thanks. kBuild: Compiling tstVMStructRC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/VMM/testcase/tstVMStructRC.cpp kBuild: Linking tstVMStructRC Using built-in specs. kmk: *** Deleting file `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/Runtime/errmsgdata.h' *** Error code 2 Stop. make[1]: stopped in /usr/ports/emulators/virtualbox-ose *** Error code 1 Stop. Could it be that you have a custom kernel and removed COMPAT_FREEBSD32 option from it? Doh, so sorry! ___ 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: security/libssh does not install ssh_threads
Am 2014-01-15 22:04, schrieb Raphael Kubo da Costa: Dima Panov flu...@freebsd.org writes: 14.01.14, 9:29, Peter Klett ?: Hi, I'm currently trying to compile the nogui version of net-p2p/retroshare which has a dependency to libssh-0.5.4. In its Makefile it includes -lssh and -lssh_threads but the later is not build / installed by libssh. [skip] Please update. libssh-0.5.5_1 installs both standard and threaded libs. This is interesting. I ended up trying to find why this was the case and it seems to be us passing -DTHREADS_HAVE_PTHREAD_ARG and libssh checking for the wrong variable to decide whether to build libssh_threads.so. I've sent some patches upstream in http://thread.gmane.org/gmane.network.ssh.libssh.general/1389 If I build the libssh library with your patches I can successfully link and the error does not occure anymore. Thank you for your work, are there any estimates when we could expect them to occur in the port? ___ 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
[QAT] r339795: 16x leftovers, 4x ???, 4x success
- Add missed dependency on libvncserver [1] - Use new style for LIB_DEPENDS - Pass maintainership from Koichiro IWAO to myself for -gnome and -nx ports by his request - Bump PORTREVISION due to changed dependencies list [2] Noticed by: QAT [1], mat@ [2] - Build ID: 20140115173000-44348 Job owner: flu...@freebsd.org Buildtime: 5 hours Enddate: Wed, 15 Jan 2014 22:14:01 GMT Revision: r339795 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=339795 - Port:net/remmina-plugin-gnome 1.0.0_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255764/remmina-plugin-gnome-1.0.0_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255765/remmina-plugin-gnome-1.0.0_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255766/remmina-plugin-gnome-1.0.0_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255767/remmina-plugin-gnome-1.0.0_2.log - Port:net/remmina-plugin-nx 1.0.0_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: ??? Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255768/remmina-plugin-nx-1.0.0_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: ??? Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255769/remmina-plugin-nx-1.0.0_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: ??? Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255770/remmina-plugin-nx-1.0.0_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: ??? Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255771/remmina-plugin-nx-1.0.0_2.log - Port:net/remmina-plugin-rdp 1.0.0_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255772/remmina-plugin-rdp-1.0.0_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255773/remmina-plugin-rdp-1.0.0_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255774/remmina-plugin-rdp-1.0.0_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255775/remmina-plugin-rdp-1.0.0_2.log - Port:net/remmina-plugin-telepathy 1.0.0_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255776/remmina-plugin-telepathy-1.0.0_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255777/remmina-plugin-telepathy-1.0.0_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255778/remmina-plugin-telepathy-1.0.0_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255779/remmina-plugin-telepathy-1.0.0_2.log - Port:net/remmina-plugin-vnc 1.0.0_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255780/remmina-plugin-vnc-1.0.0_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255781/remmina-plugin-vnc-1.0.0_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255782/remmina-plugin-vnc-1.0.0_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140115173000-44348-255783/remmina-plugin-vnc-1.0.0_2.log -
Re: FreeBSD Port: abills-0.54
))) OK I can't do that -- not enough knowledge experience. I thought the author maintains the port. Good Luck! 15.01.2014 23:14, Mikhail Tsatsenko пишет: 2014/1/16 Maxim Sirenko ma...@rivne.uar.net: Why this port version is 0.54 while there is 0.55 version on the http://abills.net.ua/ ? May be because you did not submit patches for update the port to the most recent version? ___ 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: abills-0.54
On 1/15/2014 23:23, Maxim Sirenko wrote: ))) OK I can't do that -- not enough knowledge experience. I thought the author maintains the port. Good Luck! The port is unmaintained, as seen in the second line of its description: http://www.freshports.org/net/abills/ The means the most probable way it will get an update is if a user submits an update via a PR. Even then, chances are the PR wouldn't get picked up right away due to very large backlog. You'd have to sell why that port should get attention before the rest (and being only 0.01 versions away from the most recent version doesn't sound bad). John ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: abills-0.54
Maxim Sirenko ma...@rivne.uar.net writes: I can't do that -- not enough knowledge experience. This one's pretty easy; nothing seems to need to be changed except for the version number. Go into the Makefile, change 0.54 to 0.55 and then do make makesum before doing make install. I can't be positive it works, because I didn't test it heavily, but it definitely builds. I thought the author maintains the port. Well, no; most ports are programs that run on many different operating systems. In some cases, the author hasn't even *heard* of FreeBSD. Ports may have a maintainer, who takes care of keeping it up to date and building, but abills doesn't have one. On the other hand, it doesn't seem to need a lot of maintenance. I would put in a PR to update it, but if it's going to be modified, it ought to be changed to handle the new staging infrastructure, and I don't have time to learn how to do that at the moment. ___ 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
Qpopper Port
I am going to have to give up maintaining qpopper. Not because I don't have the interest or time, but because I simply cannot update any port. The old port system may have had issues, but it worked!!! The new one does not. I am completely unable to upgrade or install any ports on a 9.1 or higher system. I have a number of those in production and will have to now resort to obtaining ports from the original sources and making them work on my systems. Its a colossal pain in the *^*^. I tried portmaster qpopper to get the latest source. That failed with lots of errors in other ports. Too many to try to do individually. I then used pkg_delete to delete all ports. Repeated portmaster qpopper. Portmaster no longer exists. Tried pkg_add -r portmaster. Message to setsomething in /etc/make.conf. Did that and then tried to run pkg2ng as it requested. pkg2ng does not exist. Its not a port either. Dead end. Went to /usr/ports/port-mgmt/portmaster and did a make. Get errors that file names are misspelled. Perhaps the new port system can be used by those who spend their day using it, but for those of us who have real work to do and only use it when needed, its just not viable. ___ 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: Qpopper Port
On 01/15/2014 06:08 PM, Doug Hardie wrote: I am going to have to give up maintaining qpopper. Not because I don't have the interest or time, but because I simply cannot update any port. The old port system may have had issues, but it worked!!! The new one does not. I am completely unable to upgrade or install any ports on a 9.1 or higher system. I have a number of those in production and will have to now resort to obtaining ports from the original sources and making them work on my systems. Its a colossal pain in the *^*^. Call me old fashioned. But I am still using FreeBSD-8 with the old ports system. I also never got into the idea of using portmaster or any of those fancy tools, and still use pkg_version and pkg_delete and cd /usr/ports/xxx/yyy make install clean to maintain my ports. I did install FreeBSD-10 on one computer recently, but I am experiencing the same problems with the ports I am maintaining - I cannot build many of them because dependent ports are breaking. Also, I get periodic emails from pkg-fall...@freebsd.org explaining how one or other of my ports don't build properly. Some of the error messages are clearly problems with switching from gcc to clang, and are easily fixed. But some of the other problems seem to be problems with FreeBSD-10 itself (especially /usr/bin/ld), or problems with pkgng. I do hope EOL for FreeBSD-8 is still some length of time away. If I had to upgrade today, it would create difficulties for me. ___ 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 Port: nut-2.6.5_1
Hi, can you please update nut to latest release 2.7.1? It supports many ups systems and contain a few bugfixes. See: https://github.com/networkupstools/nut/releases thanks, Michael ___ 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
[QAT] r339888: 4x leftovers
- Update libssh to 0.6.0 security release - Fix threaded library [1] Submitted by: rakuco@ via libssh mailing list [1] - Build ID: 20140116032801-45444 Job owner: flu...@freebsd.org Buildtime: 6 minutes Enddate: Thu, 16 Jan 2014 03:33:59 GMT Revision: r339888 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=339888 - Port:security/libssh 0.6.0 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140116032801-45444-256148/libssh-0.6.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140116032801-45444-256149/libssh-0.6.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140116032801-45444-256150/libssh-0.6.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140116032801-45444-256151/libssh-0.6.0.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140116032801-45444 redports https://qat.redports.org/ ___ 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: Qpopper Port
On Wed, Jan 15, 2014 at 4:52 PM, Montgomery-Smith, Stephen step...@missouri.edu wrote: On 01/15/2014 06:08 PM, Doug Hardie wrote: I am going to have to give up maintaining qpopper. Not because I don't have the interest or time, but because I simply cannot update any port. The old port system may have had issues, but it worked!!! The new one does not. I am completely unable to upgrade or install any ports on a 9.1 or higher system. I have a number of those in production and will have to now resort to obtaining ports from the original sources and making them work on my systems. Its a colossal pain in the *^*^. Call me old fashioned. But I am still using FreeBSD-8 with the old ports system. I also never got into the idea of using portmaster or any of those fancy tools, and still use pkg_version and pkg_delete and cd /usr/ports/xxx/yyy make install clean to maintain my ports. I did install FreeBSD-10 on one computer recently, but I am experiencing the same problems with the ports I am maintaining - I cannot build many of them because dependent ports are breaking. Also, I get periodic emails from pkg-fall...@freebsd.org explaining how one or other of my ports don't build properly. Some of the error messages are clearly problems with switching from gcc to clang, and are easily fixed. But some of the other problems seem to be problems with FreeBSD-10 itself (especially /usr/bin/ld), or problems with pkgng. I do hope EOL for FreeBSD-8 is still some length of time away. If I had to upgrade today, it would create difficulties for me. I should point out that 9 still defaults to the old package system. 10.0 defaults to pkgng AND defaults to building ports with clang. While I have not had any big issues for a while, you can go to 9 which will have neither pkgng nor clang by default. That said, but I am now running 10.0-RC5 and using both clang and pkgng and have hit no significant issues. The ports I maintain are fairly simple and converting to use the new systems was not a significant issue. I did have to retire some tools had written that worked with the old pkg database. I may re-do some to use the new database, but I have not bother, yet, and pkg info does a pretty good job of meeting my needs. I would have really liked to see both pkgng and staging have more time to settle in before they became standard, but it seems like they are working pretty well by now and I see them becoming much better. With the added capabilities in the basic structure of pkgng,ther is hte potential to do some really cool things that will make port maintenance much easier and would simply not have been possible with the old system. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.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
[QAT] r339889: 5x leftovers, 4x depend (linker_error in net/freerdp), 3x success
- Make QAT happy: plugins doesn't touch include/remmina, remove extra @dirrmtry Noticed by: QAT - Build ID: 20140116033800-40763 Job owner: flu...@freebsd.org Buildtime: 37 minutes Enddate: Thu, 16 Jan 2014 04:14:56 GMT Revision: r339889 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=339889 - Port:net/remmina-plugin-gnome 1.0.0_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256152/remmina-plugin-gnome-1.0.0_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256153/remmina-plugin-gnome-1.0.0_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256154/remmina-plugin-gnome-1.0.0_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256155/remmina-plugin-gnome-1.0.0_2.log - Port:net/remmina-plugin-i18n 1.0.0_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256156/remmina-plugin-i18n-1.0.0_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256157/remmina-plugin-i18n-1.0.0_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256158/remmina-plugin-i18n-1.0.0_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256159/remmina-plugin-i18n-1.0.0_2.log - Port:net/remmina-plugins 1.0.0_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (LINKER_ERROR IN NET/FREERDP) Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256160/freerdp-1.1.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: DEPEND (LINKER_ERROR IN NET/FREERDP) Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256161/freerdp-1.1.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: DEPEND (LINKER_ERROR IN NET/FREERDP) Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256162/freerdp-1.1.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: DEPEND (LINKER_ERROR IN NET/FREERDP) Log: https://qat.redports.org//~flu...@freebsd.org/20140116033800-40763-256163/freerdp-1.1.0.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140116033800-40763 redports https://qat.redports.org/ ___ 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: Qpopper Port
I am going to have to give up maintaining qpopper. Not because I don't have the interest or time, but because I simply cannot update any port. The old port system may have had issues, but it worked!!! The new one does not. I am completely unable to upgrade or install any ports on a 9.1 or higher system. I have a number of those in production and will have to now resort to obtaining ports from the original sources and making them work on my systems. Its a colossal pain in the *^*^. I tried portmaster qpopper to get the latest source. That failed with lots of errors in other ports. Too many to try to do individually. I then used pkg_delete to delete all ports. Repeated portmaster qpopper. Portmaster no longer exists. Tried pkg_add -r portmaster. Message to setsomething in /etc/make.conf. Did that and then tried to run pkg2ng as it requested. pkg2ng does not exist. Its not a port either. Dead end. Went to /usr/ports/port-mgmt/portmaster and did a make. Get errors that file names are misspelled. Perhaps the new port system can be used by those who spend their day using it, but for those of us who have real work to do and only use it when needed, its just not viable. I was able to build ports and upgrade with portmaster on FreeBSD 9.1 and 9.2-STABLE, and more recently, 10.0 prerelease and 11-HEAD. With 10.0 prerelease and 11-HEAD, I haven't got very far yet, not because of failures, but newness and maintaining four installations: 10.0 prerelease and 11-HEAD for both amd64 and i386. But I was able to use portmaster successfully. 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
Re: since 10.0rc5 - pkg: Unable to find catalogs
Hi I have the same problem but only with RC5-amd64.. I cant even access my local repo (same error).. RC5-i386 works fine. 11-CURRENT, no problem.. -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Sun, Jan 12, 2014 at 9:02 PM, Sebastian Jäschke jtkoert...@mac.comwrote: Hello, I'm working with the RCs from 10.0 since rc2 and had no problems until now. The rc5 is the first showing this problems: root@freebsd100:/ # pkg install nano Updating repository catalogue digests.txz 100% 1043KB 1.0MB/s 1.0MB/s 00:00 packagesite.txz 100% 4801KB 4.7MB/s 4.4MB/s 00:01 Incremental update completed, 22311 packages processed: 0 packages updated, 0 removed and 22311 added. pkg: Unable to find catalogs root@freebsd100:/ # uname -a FreeBSD freebsd100.xx 10.0-RC5 FreeBSD 10.0-RC5 #0 r260430: Wed Jan 8 05:10:04 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 root@freebsd100:/ # pkg -v 1.2.4_1 root@freebsd100:/ # pkg audit -F Vulnxml file up-to-date. 0 problem(s) in the installed packages found. root@freebsd100:/ # The only difference in my env since rc4 is, that I'm using a gmirror vm on this host instead of a single drive vm before. Sebastian ___ 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 -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。 もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. ___ 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: SCHED_ULE bug (was Re: cpuminer mines only on one core regardless of --threads option)
14.01.2014, 22:32, Alexander ag...@yandex.ru: 14.01.2014, 20:14, Subbsd sub...@gmail.com: On Tue, Jan 14, 2014 at 7:43 PM, Andrey Chernov a...@freebsd.org wrote: On 14.01.2014 17:01, Alexander wrote: on Freebsd 9.2 x64 on 5 different PCs I installed net-p2p/cpuminer from ports and by pkg install - result is the same - minerd mines only on one core regardless of --threads option. ... # top -P CPU 0: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 1: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 2: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU 3: 0.0% user, 100% nice, 0.0% system, 0.0% interrupt, 0.0% idle This is SCHED_ULE bug, I see _all_ processes (not minerd only in particular) stuck to the last CPU too (top's 'C' column is equal to the last CPU and never changes), latest -stable i386. It disappears for me switching to SCHED_4BSD. reboot didn't help (try on 3 different PCs) I'll try switching to SCHED_4BSD tomorrow (thanks Andrey Chernov) I sad wrong. minerd was started from cron after reboot immediately and broke SMP, so when I disable minerd from cron and reboot - SMP works fine. I think Andrey Chernov said here the reason http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/163585#reply3 So this bug is alive - on 9.1 and 9.2 x64 releases. I didn't try SCHED_4BSD yet, cause don't wont to use not-generic kernel because of mining only, but for interest I'll try it on one machine on this weekends. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: abills-0.54
Hi all! I highly appreciate the feedback I received on this topic! I couldn't even expect it! As regards abills -- there are no such changes between 0.54 0.55 that could break the port. Abills -- is a perl_rlm freeradius module and several perl scripts, so for persons who know ports it should be easy to update it. And it would be nice to build pkg so in 10.0 one could install it with pkg utility. Maxim. 16.01.2014 2:24, Lowell Gilbert пишет: Maxim Sirenko ma...@rivne.uar.net writes: I can't do that -- not enough knowledge experience. This one's pretty easy; nothing seems to need to be changed except for the version number. Go into the Makefile, change 0.54 to 0.55 and then do make makesum before doing make install. I can't be positive it works, because I didn't test it heavily, but it definitely builds. I thought the author maintains the port. Well, no; most ports are programs that run on many different operating systems. In some cases, the author hasn't even *heard* of FreeBSD. Ports may have a maintainer, who takes care of keeping it up to date and building, but abills doesn't have one. On the other hand, it doesn't seem to need a lot of maintenance. I would put in a PR to update it, but if it's going to be modified, it ought to be changed to handle the new staging infrastructure, and I don't have time to learn how to do that at the moment. ___ 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
