Re: pkg_replace and detecting pkg(ng)
Hello,
I made a patch for your request.
Please see, http://www.freebsd.org/cgi/query-pr.cgi?pr=187723
Thank you.
Hi,
In the past I've been able to use pkg_replace on machine that didn't
have the ports collection installed.
With the current version of pkg_replace this doesn't seem to be
possible anymore, since pkg(ng) detection breaks in those cases:
: ${use_pkgng=`/usr/bin/make -f/usr/share/mk/bsd.port.mk -V
WITH_PKGNG`}
if [ x${use_pkgng} = xdevel ]; then
use_pkgng=yes
fi
bsd.port.mk requires /usr/ports/Mk/...
One of the main motivations to use pkg_replace for me is to not having
a ports tree on the machines I use it on.
I would suggest to replace this with a detection mechanism similar to
what ports does:
If sysctl -n kern.osreldate = 117
use_pkgng=yes, unless WITHOUT_PKGNG is defined
else if defined(WITH_PKGNG) (any value, not just ==yes)
use_pkgng=yes
else
use_pkgng=no
Determining WITH_PKGNG/WITHOUT_PKGNG should be done using make -V VAR
(without specifying a Makefile, so /etc/make.conf is read).
- Michael
--
Michael Gmelin
___
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: ushare-1.1a_9
Hello,
It appears that the ushare port requires GCC to build, but this
requirement is not present in the Makefile. Attempting to build without
GCC generates the following error:
[root@fileserver /usr/ports/net/ushare]# make clean
=== Cleaning for gmake-3.82_1
=== Cleaning for ushare-1.1a_9
[root@fileserver /usr/ports/net/ushare]#
[root@fileserver /usr/ports/net/ushare]# make
=== ushare-1.1a_9 depends on file: /usr/local/sbin/pkg - found
=== Fetching all distfiles required by ushare-1.1a_9 for building
=== Extracting for ushare-1.1a_9
= SHA256 Checksum OK for ushare-1.1a.tar.bz2.
=== Patching for ushare-1.1a_9
=== Applying FreeBSD patches for ushare-1.1a_9
=== ushare-1.1a_9 depends on executable: gmake - found
=== ushare-1.1a_9 depends on executable: pkgconf - found
=== ushare-1.1a_9 depends on shared library: libintl.so - found
=== ushare-1.1a_9 depends on shared library: upnp.9 - found
=== Configuring for ushare-1.1a_9
=== FreeBSD 10 autotools fix applied to
/usr/ports/net/ushare/work/ushare-1.1a/configure
Checking for compiler available...
Checking for locales ...
Checking for ifaddrs ...
Checking for langinfo ...
Checking for iconv ...
Checking for libixml ...
Checking for libthreadutil ...
Checking for libupnp = 1.4.2 ...
Checking for libdlna = 0.2.1 ...
uShare: configure is OK
version1.1a
using libupnp 1.6.19
using libdlna 0.2.3
configuration:
install prefix /usr/local
configuration dir ${PREFIX}/etc
locales dir${PREFIX}/share/locale
NLS supportyes
DLNA support yes
C compiler cc
STRIP strip
make gmake
CPUx86 ()
debug symbols no
strip symbols yes
optimize yes
CFLAGS -O -pipe -I/usr/local/include
-I/usr/ports/net/ushare/work/ushare-1.1a -W -Wall -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -O3 -DHAVE_LOCALE_H -DHAVE_SETLOCALE
-DHAVE_IFADDRS_H -DHAVE_LANGINFO_H -DHAVE_LANGINFO_CODESET -DHAVE_ICONV
-I/usr/local/include/upnp -DHAVE_DLNA
LDFLAGS -L/usr/local/lib -lintl
extralibs -lixml -lthreadutil -lpthread -lupnp -pthread
-L/usr/local/lib -ldlna -lavformat -lavcodec
Creating config.mak ...
Creating config.h ...
=== Building for ushare-1.1a_9
gmake[1]: Entering directory `/usr/ports/net/ushare/work/ushare-1.1a'
for subdir in po scripts src ; do \
gmake -C $subdir all; \
done
gmake[2]: Entering directory `/usr/ports/net/ushare/work/ushare-1.1a/po'
gmake fr.gmo de.gmo
gmake[3]: Entering directory `/usr/ports/net/ushare/work/ushare-1.1a/po'
gmake[3]: `fr.gmo' is up to date.
gmake[3]: `de.gmo' is up to date.
gmake[3]: Leaving directory `/usr/ports/net/ushare/work/ushare-1.1a/po'
touch stamp-po
gmake[2]: Leaving directory `/usr/ports/net/ushare/work/ushare-1.1a/po'
gmake[2]: Entering directory
`/usr/ports/net/ushare/work/ushare-1.1a/scripts'
gmake[2]: Nothing to be done for `all'.
gmake[2]: Leaving directory
`/usr/ports/net/ushare/work/ushare-1.1a/scripts'
gmake[2]: Entering directory `/usr/ports/net/ushare/work/ushare-1.1a/src'
cc -I.. -MM -O -pipe -I/usr/local/include
-I/usr/ports/net/ushare/work/ushare-1.1a cds.c cms.c msr.c http.c
presentation.c metadata.c mime.c services.c buffer.c util_iconv.c
content.c cfgparser.c trace.c redblack.c osdep.c ctrl_telnet.c ushare.c
1.depend
cc -c -O -pipe -I/usr/local/include
-I/usr/ports/net/ushare/work/ushare-1.1a -O -pipe -I/usr/local/include
-I/usr/ports/net/ushare/work/ushare-1.1a -W -Wall -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -O3 -DHAVE_LOCALE_H -DHAVE_SETLOCALE
-DHAVE_IFADDRS_H -DHAVE_LANGINFO_H -DHAVE_LANGINFO_CODESET -DHAVE_ICONV
-I/usr/local/include/upnp -DHAVE_DLNA -o cds.o cds.c
cc -c -O -pipe -I/usr/local/include
-I/usr/ports/net/ushare/work/ushare-1.1a -O -pipe -I/usr/local/include
-I/usr/ports/net/ushare/work/ushare-1.1a -W -Wall -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -O3 -DHAVE_LOCALE_H -DHAVE_SETLOCALE
-DHAVE_IFADDRS_H -DHAVE_LANGINFO_H -DHAVE_LANGINFO_CODESET -DHAVE_ICONV
-I/usr/local/include/upnp -DHAVE_DLNA -o cms.o cms.c
cc -c -O -pipe -I/usr/local/include
-I/usr/ports/net/ushare/work/ushare-1.1a -O -pipe -I/usr/local/include
-I/usr/ports/net/ushare/work/ushare-1.1a -W -Wall -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -O3 -DHAVE_LOCALE_H -DHAVE_SETLOCALE
-DHAVE_IFADDRS_H -DHAVE_LANGINFO_H -DHAVE_LANGINFO_CODESET -DHAVE_ICONV
-I/usr/local/include/upnp -DHAVE_DLNA -o msr.o msr.c
cc -c -O -pipe -I/usr/local/include
-I/usr/ports/net/ushare/work/ushare-1.1a -O -pipe -I/usr/local/include
-I/usr/ports/net/ushare/work/ushare-1.1a -W -Wall -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -O3 -DHAVE_LOCALE_H -DHAVE_SETLOCALE
-DHAVE_IFADDRS_H -DHAVE_LANGINFO_H -DHAVE_LANGINFO_CODESET -DHAVE_ICONV
-I/usr/local/include/upnp -DHAVE_DLNA -o http.o http.c
cc -c -O -pipe -I/usr/local/include
-I/usr/ports/net/ushare/work/ushare-1.1a -O -pipe -I/usr/local/include
graphics/mapserver Python mapscript fails
Hi,
I can't seem to build mapserver-6.4.0_1 with Python mapscript. I noticed
the following lines at the end of the mapscript build:
=== Registering installation for mapserver-6.4.0_1
pkg-static: lstat(/usr/local/lib/python2.7/site-packages/mapscript.py):
No such file or directory
pkg-static: lstat(/usr/local/lib/python2.7/site-packages/mapscript.pyc):
No such file or directory
pkg-static: lstat(/usr/local/lib/python2.7/site-packages/_mapscript.so):
No such file or directory
pkg-static:
lstat(/usr/local/lib/python2.7/site-packages/MapScript-6.4.0-py2.7.egg-info):
No such file or directory
Installing mapserver-6.4.0_1... done
And import mapscript in Python yields an error:
File
/usr/local/lib/python2.7/site-packages/MapScript-6.2.1-py2.7-freebsd-9.1-RELEASE-p7-amd64.egg/mapscript.py,
line 25, in module
_mapscript = swig_import_helper()
File
/usr/local/lib/python2.7/site-packages/MapScript-6.2.1-py2.7-freebsd-9.1-RELEASE-p7-amd64.egg/mapscript.py,
line 21, in swig_import_helper
_mod = imp.load_module('_mapscript', fp, pathname, description)
ImportError: Shared object libmapserver-6.2.1.so not found, required
by _mapscript.so
Apparently there's still an old lib link flying around. Rebuilding
Python didn't help though.
This is on
uname -a
FreeBSD frodo.metrico 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0: Sat Jan
11 03:25:02 UTC 2014
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
Any ideas?
Frank
--
Frank BRONIEWSKI
METRICO s.à r.l.
géomètres
technologies d'information géographique
rue des Romains 36
L-5433 NIEDERDONVEN
tél.: +352 26 74 94 - 28
fax.: +352 26 74 94 99
http://www.metrico.lu
___
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 +-+ math/asir2000 | 20110810| 20140224 +-+ www/apache22-peruser-mpm| 2.2.26 | 2.2.27 +-+ 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
pdksh put path to man page in /etc/shells
When portupgrade updated the shells/pdksh port on my system today it stored the path to its man page in the /etc/shells file rather than the path to the executable file, thus causing mail and login to fail for accounts that use /usr/local/bin/ksh as their login shell. Bob -- Bob Willcox| (1) If it's green or it wiggles, it's biology. b...@immure.com | (2) If it stinks, it's chemistry. Austin, TX | (3) If it doesn't work, it's physics. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
portmaster/portupgrade -P/PP + pkg, ports package sources
FYI,
I plan to enable this support soon in both tools.
I actually see 4 different modes here. Note I made up --local-only for
this discussion, I am not changing the flags in either tool.
-P: Use package if available, otherwise build from source.
-P --local-only: Use local package if available, otherwise build from
source.
-PP: Only use packages
-PP --local-only: Only use local packages.
I did not quite understand the use-case for it and was not convinced it
was needed until recently.
I will be adding a majority of the logic into the ports framework
though. A lot of this logic already exists, just needs to be refined and
hooked together.
Ports will have a flags to enable the use cases above (only for pkgng).
It will search local package dir and then remote for the package before
installing. These flags will all be off by default.
Portmaster/Portupgrade/Poudriere all will utilize them. Yes, poudriere
has a need here for installing dependencies from local packages for
interactive testing where it is more efficient to do it in the framework.
One of the reasons I plan to put this logic into ports is so the same
consistent (smart) logic can be used in both tools. In general I believe
that all logic like this should be in ports and not in tools such as
portmaster/portupgrade/poudriere/tinderbox. There is still some
unrelated lingering logic in poudriere that needs to be moved to the
framework in fact.
One of the blockers to making this work properly is having an official
repository installed out-of-the-box. I am working on getting an EN out
to publish the repository and fingerprints for pkg. As a last resort we
may publish this in ports as well in /Templates/repo, which pkg(8) can
utilize as a last resort for this ports feature. If it comes to that I
will give more details on it. This repo could be disabled in the same
way as the FreeBSD one is today, by creating a file in
/usr/local/etc/pkg/repos/FreeBSD.conf with contents FreeBSD: { enabled:
false }
--
Regards,
Bryan Drewery
signature.asc
Description: OpenPGP digital signature
[QAT] 348616: 2x leftovers, 4x success
Correct a typo. - Build ID: 20140319123401-24651 Job owner: mar...@freebsd.org Buildtime: 18 minutes Enddate: Wed, 19 Mar 2014 12:52:22 GMT Revision: 348616 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348616 - Port:net/netatalk3 3.1.1,1 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~mar...@freebsd.org/20140319123401-24651-304282/netatalk3-3.1.1,1.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~mar...@freebsd.org/20140319123401-24651-304283/netatalk3-3.1.1,1.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~mar...@freebsd.org/20140319123401-24651-304284/netatalk3-3.1.1,1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~mar...@freebsd.org/20140319123401-24651-304285/netatalk3-3.1.1,1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~mar...@freebsd.org/20140319123401-24651-304286/netatalk3-3.1.1,1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~mar...@freebsd.org/20140319123401-24651-304287/netatalk3-3.1.1,1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140319123401-24651 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
Update of quazip-0.5.1 to quazip-0.6.2 fails
I am running 10.0-RELEASE and when trying to upgrade quazip-0.5.1 to quazip-0.6.2 after latest update of the ports tree I obtain the following error: ... c++ -Wl,-O1 -pthread -Wl,-rpath,/usr/local/lib/qt4 -o qztest .obj/qztest.o .obj/testjlcompress.o .obj/testquachecksum32.o .obj/testquagzipfile.o .obj/testquaziodevice.o .obj/testquazip.o .obj/testquazipdir.o .obj/testquazipfile.o .obj/testquazipnewinfo.o .obj/testquazipfileinfo.o .obj/moc_testjlcompress.o .obj/moc_testquachecksum32.o .obj/moc_testquagzipfile.o .obj/moc_testquaziodevice.o .obj/moc_testquazipdir.o .obj/moc_testquazipfile.o .obj/moc_testquazip.o .obj/moc_testquazipnewinfo.o .obj/moc_testquazipfileinfo.o -L/usr/local/lib/qt4 -L/usr/local/lib -lz -L/usr/ports/archivers/quazip/work/quazip-0.6.2/qztest/../quazip/ -lquazip -lQtTest -L/usr/local/lib/qt4 -L/usr/local/lib -lQtCore .obj/testjlcompress.o: In function `TestJlCompress::extractFile()': testjlcompress.cpp:(.text+0x38a7): undefined reference to `QuaZip::setDefaultFileNameCodec(char const*)' .obj/testquazip.o: In function `TestQuaZip::getFileList()': testquazip.cpp:(.text+0x111c): undefined reference to `QuaZip::getFileInfoList64() const' .obj/testquazip.o: In function `TestQuaZip::setAutoClose()': testquazip.cpp:(.text+0x5328): undefined reference to `QuaZip::isAutoClose() const' testquazip.cpp:(.text+0x5456): undefined reference to `QuaZip::isAutoClose() const' testquazip.cpp:(.text+0x5486): undefined reference to `QuaZip::setAutoClose(bool) const' testquazip.cpp:(.text+0x548f): undefined reference to `QuaZip::isAutoClose() const' .obj/testquazipdir.o: In function `TestQuaZipDir::entryInfoList()': testquazipdir.cpp:(.text+0x9bd1): undefined reference to `QuaZipDir::entryInfoList64(QFlagsQDir::Filter, QFlagsQDir::SortFlag) const' .obj/testquazipfile.o: In function `TestQuaZipFile::zipUnzip()': testquazipfile.cpp:(.text+0xddb): undefined reference to `QuaZip::setZip64Enabled(bool)' .obj/testquazipfile.o: In function `TestQuaZipFile::getFileInfo()': testquazipfile.cpp:(.text+0x519e): undefined reference to `QuaZipFile::getFileInfo(QuaZipFileInfo64*)' .obj/testquazipfile.o: In function `TestQuaZipFile::setFileAttrs()': testquazipfile.cpp:(.text+0x6d4e): undefined reference to `QuaZipFile::getFileInfo(QuaZipFileInfo64*)' testquazipfile.cpp:(.text+0x6d86): undefined reference to `QuaZipFileInfo64::getPermissions() const' testquazipfile.cpp:(.text+0x6f0c): undefined reference to `QuaZipFile::getFileInfo(QuaZipFileInfo64*)' testquazipfile.cpp:(.text+0x6fa0): undefined reference to `QuaZipFileInfo64::getPermissions() const' .obj/testquazipnewinfo.o: In function `TestQuaZipNewInfo::setFileNTFSTimes()': testquazipnewinfo.cpp:(.text+0x37e): undefined reference to `QuaZipNewInfo::setFileNTFSTimes(QString const)' testquazipnewinfo.cpp:(.text+0x52b): undefined reference to `QuaZip::getCurrentFileInfo(QuaZipFileInfo64*) const' .obj/testquazipfileinfo.o: In function `TestQuaZipFileInfo::getNTFSTime()': testquazipfileinfo.cpp:(.text+0xd1b): undefined reference to `QuaZip::getCurrentFileInfo(QuaZipFileInfo64*) const' testquazipfileinfo.cpp:(.text+0xd67): undefined reference to `QuaZipFileInfo64::getNTFSmTime(int*) const' testquazipfileinfo.cpp:(.text+0xe2e): undefined reference to `QuaZipFileInfo64::getNTFSaTime(int*) const' testquazipfileinfo.cpp:(.text+0x10a1): undefined reference to `QuaZipFileInfo64::getNTFScTime(int*) const' c++: error: linker command failed with exit code 1 (use -v to see invocation) *** [qztest] Error code 1 make[2]: stopped in /usr/ports/archivers/quazip/work/quazip-0.6.2/qztest 1 error make[2]: stopped in /usr/ports/archivers/quazip/work/quazip-0.6.2/qztest *** [sub-qztest-all] Error code 2 make[1]: stopped in /usr/ports/archivers/quazip/work/quazip-0.6.2 1 error make[1]: stopped in /usr/ports/archivers/quazip/work/quazip-0.6.2 === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make: stopped in /usr/ports/archivers/quazip === make failed for archivers/quazip === Aborting update === Killing background jobs Terminated === You can restart from the point of failure with this command line: portmaster flags archivers/quazip Any hints are appreciated. Regards, 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: Update of quazip-0.5.1 to quazip-0.6.2 fails
Hi! I am running 10.0-RELEASE and when trying to upgrade quazip-0.5.1 to quazip-0.6.2 after latest update of the ports tree I obtain the following error: Please deinstall the old quazip before building the new port. MAINTAINER is notified. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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
port install hanging security/cyrus-sasl2
I'm seeing this step hanging around until the end of time.. any ideas? make install clean ... Compressing man pages (compress-man) === Installing for cyrus-sasl-2.1.26_4 === Checking if security/cyrus-sasl2 already installed === Registering installation for cyrus-sasl-2.1.26_4 *** Added group `cyrus' (id 60) *** Added user `cyrus' (id 60) (sitting there until the end of time) it seems to be waiting for this to finish: /usr/local/sbin/pkg-static register -i /usr/ports/security/cyrus-sasl2/work/stage -m /usr/ports/security FreeBSD ra 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r263322: Tue Mar 18 16:52:58 PDT 2014 /usr/obj/usr/src/sys/LFRH amd64 ports Revision: 348606 any troubleshooting ideas? Thank you, Waitman Gobble ___ 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] 348621: 2x leftovers, 4x success
Add php 5.5 in IGNORE. - Build ID: 20140319142800-6450 Job owner: a...@freebsd.org Buildtime: 13 minutes Enddate: Wed, 19 Mar 2014 14:40:36 GMT Revision: 348621 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348621 - Port:security/php-suhosin 0.9.33 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~a...@freebsd.org/20140319142800-6450-304312/php-suhosin-0.9.33.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~a...@freebsd.org/20140319142800-6450-304313/php-suhosin-0.9.33.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~a...@freebsd.org/20140319142800-6450-304314/php-suhosin-0.9.33.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~a...@freebsd.org/20140319142800-6450-304315/php-suhosin-0.9.33.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~a...@freebsd.org/20140319142800-6450-304316/php-suhosin-0.9.33.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~a...@freebsd.org/20140319142800-6450-304317/php-suhosin-0.9.33.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140319142800-6450 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
[QAT] 348627: 1x leftovers, 5x success
Update to 1.3.0.a2 Changes: - libpkg: Simplify code but turning annotations into a pkg_object - libpkg: Simplify dumping the configuration of plugins in pkg -vv - libpkg: Update libucl to latest version - libpkg: Fix options emission in the Manifest - libpkg: fix some multirepository bugs - pkg: fix pkg delete -f - pkg: fix pkg register - pkg: fix pkg upgrade - pkg: fix pkg shell - pkg: 'update' now warns user if no repos are enabled - Build ID: 20140319154600-1312 Job owner: b...@freebsd.org Buildtime: 8 minutes Enddate: Wed, 19 Mar 2014 15:54:03 GMT Revision: 348627 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348627 - Port:ports-mgmt/pkg-devel Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140319154600-1312-304348/pkg-devel-1.3.0.a2.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319154600-1312-304349/pkg-devel-1.3.0.a2.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319154600-1312-304350/pkg-devel-1.3.0.a2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319154600-1312-304351/pkg-devel-1.3.0.a2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319154600-1312-304352/pkg-devel-1.3.0.a2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319154600-1312-304353/pkg-devel-1.3.0.a2.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140319154600-1312 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: Plex Media Server Port issues
On 03/19/2014 12:08 AM, Waitman Gobble wrote: On 3/18/2014 4:36 PM, Kaya Saman wrote: Hi, I'm experiencing 3 issues with the Plex Media Server My configuration is running FreeBSD 10.0 x64 with the ports tree up to date. Issue 1: Upon first installing the port everything went fine however, PMS wouldn't start and kept complaining about a Python C Lang issue... Google'ing I managed to find a FreeBSD Forum posting stating to insert this line: #!/bin/sh export LD_LIBMAP=/lib/libc.so.7 /usr/local/share/plexmediaserver/libc.so.7 I don't recall using Plex Media Server however I think you are missing something in your LD_LIBMAP.. like an equal sign, instead of the space.. ie libc.so.7=the other libc.so.7 Thanks for the hint, I added it into the start.sh file and restarted the PMS service. I'm not sure if it actually did anything though as nothing seems to have changed. In the meantime however, shouldn't that have been added into the port in anycase? I can definitely say that the DLNA server isn't visible. I will check in the meantime to see if there is a setting somewhere maybe in the Preferences.xml file to turn on the visibility... unless anyone else has any ideas? Regards, Kaya ___ 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: port install hanging security/cyrus-sasl2
On 3/19/2014 7:28 AM, Waitman Gobble wrote: I'm seeing this step hanging around until the end of time.. any ideas? make install clean ... Compressing man pages (compress-man) === Installing for cyrus-sasl-2.1.26_4 === Checking if security/cyrus-sasl2 already installed === Registering installation for cyrus-sasl-2.1.26_4 *** Added group `cyrus' (id 60) *** Added user `cyrus' (id 60) (sitting there until the end of time) it seems to be waiting for this to finish: /usr/local/sbin/pkg-static register -i /usr/ports/security/cyrus-sasl2/work/stage -m /usr/ports/security FreeBSD ra 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r263322: Tue Mar 18 16:52:58 PDT 2014 /usr/obj/usr/src/sys/LFRH amd64 ports Revision: 348606 any troubleshooting ideas? Thank you, Waitman Gobble Problem solved. This machine was a 'fresh install' of FreeBSD 8 performed by a vendor. Apparently they installed a couple of ports for some reason (?). I think after upgrade to FreeBSD 10.0 there was some minor breakage of what they installed, ie (curl-7.24.0) /usr/local/bin/curl - shared library libcrypto.so.6 not found Anyway the solution was to wipe /usr/local/ and /var/db/pkg, seems to have solved my issue. Thanks, Waitman ___ 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: Update of quazip-0.5.1 to quazip-0.6.2 fails
Hi! I am running 10.0-RELEASE and when trying to upgrade quazip-0.5.1 to quazip-0.6.2 after latest update of the ports tree I obtain the following error: Please deinstall the old quazip before building the new port. thanks for your feedback. However, I am not sure, if I've got you right: Currently BUILDING of the new quazip version fails. How can deinstallation of the old version correct this behavior? The build imports some definitions from old .h files or so ? I saw the same problem, deinstalled the old version, build and it worked. There are cases where ports have this kind of quirk. Sometimes, it's documented in /usr/ports/UPDATING. And if I force uninstallion of the old version and if subsequently building of the new version should fail, I will be left with broken dependencies: You are right, that might be a problem. You can handle it this way: Create a package file: pkg create quazip-0.5.1 It will create a quazip-0.5.1.txz in the working directory. Then deinstall, and if the build fails, re-add the old pkg: pkg add quazip-0.5.1.txz Thanks for doing so. I am rather new to FreeBSD and do not yet know, when there is time to directly contact a port maintainer. Until now I have first reported an issue to the forum or the mailing list. And in a second step I have informed the corresponding port maintainer. Is this the recommended way to proceed? In general, informing the maintainer, probably generating a problem-report (using the command send-pr) is the correct way. In that special case http://www.freshports.org/archivers/quazip/ shows that the update was done after the maintainer failed to approve the update. So in this particular case informing him might be superfluous. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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: Plex Media Server Port issues
On 03/19/2014 05:14 PM, Waitman Gobble wrote:
On 3/19/2014 8:59 AM, Kaya Saman wrote:
On 03/19/2014 12:08 AM, Waitman Gobble wrote:
On 3/18/2014 4:36 PM, Kaya Saman wrote:
Hi,
I'm experiencing 3 issues with the Plex Media Server
My configuration is running FreeBSD 10.0 x64 with the ports tree up
to date.
Issue 1: Upon first installing the port everything went fine
however, PMS wouldn't start and kept complaining about a Python C
Lang issue... Google'ing I managed to find a FreeBSD Forum posting
stating to insert this line:
#!/bin/sh
export LD_LIBMAP=/lib/libc.so.7
/usr/local/share/plexmediaserver/libc.so.7
I don't recall using Plex Media Server however I think you are
missing something in your LD_LIBMAP.. like an equal sign, instead of
the space.. ie libc.so.7=the other libc.so.7
Thanks for the hint, I added it into the start.sh file and restarted
the PMS service.
I'm not sure if it actually did anything though as nothing seems to
have changed.
In the meantime however, shouldn't that have been added into the port
in anycase?
I can definitely say that the DLNA server isn't visible. I will check
in the meantime to see if there is a setting somewhere maybe in the
Preferences.xml file to turn on the visibility... unless anyone else
has any ideas?
Regards,
Kaya
___
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
Not sure, it looks like plex media server is a closed source
proprietary program. Are they using their own libc for some sort of
DRM scheme? Not sure how that works with GNU software, maybe they
wrote their own closed-source libc?
does /usr/local/share/plexmediaserver/libc.so.7 exist? maybe you need
to use the FreeBSD libc in the compatibility libraries...
Anyway the ports Makefile shows their binary files are compiled for
FreeBSD 9 , and uses the libstdc++ in
${LOCALBASE}/lib/compat/libstdc++.so.6 but no mention of libc.
Waitman
Hmm odd!
I found the FreeBSD portion on the Plex site so I think I'll take this
there as there is probably a larger user space...
Thanks in anycase.
Regards,
Kaya
___
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: Plex Media Server Port issues
On 3/19/2014 8:59 AM, Kaya Saman wrote:
On 03/19/2014 12:08 AM, Waitman Gobble wrote:
On 3/18/2014 4:36 PM, Kaya Saman wrote:
Hi,
I'm experiencing 3 issues with the Plex Media Server
My configuration is running FreeBSD 10.0 x64 with the ports tree up
to date.
Issue 1: Upon first installing the port everything went fine
however, PMS wouldn't start and kept complaining about a Python C
Lang issue... Google'ing I managed to find a FreeBSD Forum posting
stating to insert this line:
#!/bin/sh
export LD_LIBMAP=/lib/libc.so.7
/usr/local/share/plexmediaserver/libc.so.7
I don't recall using Plex Media Server however I think you are
missing something in your LD_LIBMAP.. like an equal sign, instead of
the space.. ie libc.so.7=the other libc.so.7
Thanks for the hint, I added it into the start.sh file and restarted
the PMS service.
I'm not sure if it actually did anything though as nothing seems to
have changed.
In the meantime however, shouldn't that have been added into the port
in anycase?
I can definitely say that the DLNA server isn't visible. I will check
in the meantime to see if there is a setting somewhere maybe in the
Preferences.xml file to turn on the visibility... unless anyone else
has any ideas?
Regards,
Kaya
___
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
Not sure, it looks like plex media server is a closed source proprietary
program. Are they using their own libc for some sort of DRM scheme? Not
sure how that works with GNU software, maybe they wrote their own
closed-source libc?
does /usr/local/share/plexmediaserver/libc.so.7 exist? maybe you need to
use the FreeBSD libc in the compatibility libraries...
Anyway the ports Makefile shows their binary files are compiled for
FreeBSD 9 , and uses the libstdc++ in
${LOCALBASE}/lib/compat/libstdc++.so.6 but no mention of libc.
Waitman
--
Waitman Gobble
San Jose California USA
___
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: Update of quazip-0.5.1 to quazip-0.6.2 fails
Am Wed, 19 Mar 2014 14:36:14 +0100 schrieb Kurt Jaeger li...@opsec.eu: Hi! Hi, Kurt, I am running 10.0-RELEASE and when trying to upgrade quazip-0.5.1 to quazip-0.6.2 after latest update of the ports tree I obtain the following error: Please deinstall the old quazip before building the new port. thanks for your feedback. However, I am not sure, if I've got you right: Currently BUILDING of the new quazip version fails. How can deinstallation of the old version correct this behavior? And if I force uninstallion of the old version and if subsequently building of the new version should fail, I will be left with broken dependencies: # pkg info -r quazip quazip-0.5.1: marble-4.12.3 MAINTAINER is notified. Thanks for doing so. I am rather new to FreeBSD and do not yet know, when there is time to directly contact a port maintainer. Until now I have first reported an issue to the forum or the mailing list. And in a second step I have informed the corresponding port maintainer. Is this the recommended way to proceed? Regards, 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
[QAT] 348642: 1x leftovers, 5x success
Update to 1.3.0.a3 - Fix a typo in pkg.conf(5) - pkg add is an alias on pkg install -l - Build ID: 20140319180600-4969 Job owner: b...@freebsd.org Buildtime: 8 minutes Enddate: Wed, 19 Mar 2014 18:13:58 GMT Revision: 348642 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348642 - Port:ports-mgmt/pkg-devel Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140319180600-4969-30/pkg-devel-1.3.0.a3.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319180600-4969-304445/pkg-devel-1.3.0.a3.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319180600-4969-304446/pkg-devel-1.3.0.a3.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319180600-4969-304447/pkg-devel-1.3.0.a3.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319180600-4969-304448/pkg-devel-1.3.0.a3.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319180600-4969-304449/pkg-devel-1.3.0.a3.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140319180600-4969 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
[QAT] 348643: 2x leftovers, 4x success
- Improve english in pkg-message - Build ID: 20140319183000-19486 Job owner: z...@freebsd.org Buildtime: 5 minutes Enddate: Wed, 19 Mar 2014 18:35:29 GMT Revision: 348643 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348643 - Port:net-mgmt/net-snmp 5.7.2_4 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~z...@freebsd.org/20140319183000-19486-304450/net-snmp-5.7.2_4.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~z...@freebsd.org/20140319183000-19486-304451/net-snmp-5.7.2_4.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~z...@freebsd.org/20140319183000-19486-304452/net-snmp-5.7.2_4.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~z...@freebsd.org/20140319183000-19486-304453/net-snmp-5.7.2_4.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~z...@freebsd.org/20140319183000-19486-304454/net-snmp-5.7.2_4.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~z...@freebsd.org/20140319183000-19486-304455/net-snmp-5.7.2_4.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140319183000-19486 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: Plex Media Server Port issues
On 2014-03-18 18:36, Kaya Saman wrote: Hi, I'm experiencing 3 issues with the Plex Media Server My configuration is running FreeBSD 10.0 x64 with the ports tree up to date. Issue 1: Upon first installing the port everything went fine however, PMS wouldn't start and kept complaining about a Python C Lang issue... Google'ing I managed to find a FreeBSD Forum posting stating to insert this line: #!/bin/sh export LD_LIBMAP=/lib/libc.so.7 /usr/local/share/plexmediaserver/libc.so.7 in the start.sh file located in: /usr/local/share/plexmediaserver In addition I had to comment out these two lines: #export LC_ALL=en_US.UTF-8 #export LANG=en_US.UTF-8 in the start.sh file. On FreeBSD we do not use the start.sh file supplied by Plex. We only use the /usr/local/etc/rc.d/plexmediaserver script. I did not strip it out of the port/package install as I did not feel that was necessary, but I will consider doing so to prevent this confusion in the future. Everything should work just fine using the FreeBSD rc script. I've tested on FreeBSD 9, 10, and CURRENT as well as in jails. Issue 2: As I'm running PMS in a Jail on a headless server, for some reason the rc script doesn't start properly?? This is quite weird... Using an SSH tunnel running: service plexmediaserver start or the /usr/local/etc/rc.d/plexmediaserver start method, not all services seem to come up properly. What exactly do you mean not all services seem to come up properly? You should see the following two processes at a minimum: /usr/local/share/plexmediaserver/Plex Media Server /usr/local/share/plexmediaserver/Plex DLNA Server Probably linked in with this is that not VNC'ing leaves me unable to login at the web interface. Putting my Plex ID/passwd combo in doesn't do a thing. This is a permissions issue caused by not running Plex from the rc script which automatically launches the process as the plex user. Issue 3: For some reason the DLNA server doesn't work properly Though it does show up as online using ps: plex 89291 0.0 0.2 139844 17808 - SJ 10:40PM 0:00.15 /usr/local/share/plexmediaserver/Plex DLNA Server It doesn't seem to broadcast itself. If you're running in a jail you're correct, this will not work. DLNA uses multicast and multicast does not work in FreeBSD jails. Let's start fresh here; remove the port, delete any contents in /usr/local/plexdata, and reinstall the port. Add plexmediaserver_enable=YES to /etc/rc.conf and start the service. It should start up flawlessly as I've handled all these quirks in the rc script (except the multicast in a jail issue; I cannot fix that). ___ 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: Update of quazip-0.5.1 to quazip-0.6.2 fails
Hi! In that special case http://www.freshports.org/archivers/quazip/ shows that the update was done after the maintainer failed to approve the update. So in this particular case informing him might be superfluous. Well, I am obviously not much trained in reading the commit history. I would conclude from the last entry 17 Mar 2014 15:54:23 and Approved by: maintainer timeout (nivit, 4 weeks) that the maintainer did not approve the commit and thus the commit remained untested. The committer probably did test it, but probably had no previous quazip installation to run into the problem. Can one conclude from this that the maintainer is aware of problems without reporting them? No -- this meant that someone told the maintainer to check the PR, but he failed to react. Why he failed to react (probably overload 8-} does not allow one to draw conclusions on his consent/dissent or anything else 8-} I cannot read that the maintainer failed to approve. Correct, the 'maintainer timeout' only says: He had time to react and failed to react. Or can I assume for sure every port maintainer has subscribed to this mailing list? You can't assume that. So, if you see problems, a mail directly to the maintainer is one way, submitting a PR is another way to handle it. This list is yet another way to get feedback on the issue. The best way it to submit a PR, because then the state of the problem can be tracked. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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: Update of quazip-0.5.1 to quazip-0.6.2 fails
Am Wed, 19 Mar 2014 18:09:43 +0100 schrieb Kurt Jaeger li...@opsec.eu: Hi! Hi kurt, I am running 10.0-RELEASE and when trying to upgrade quazip-0.5.1 to quazip-0.6.2 after latest update of the ports tree I obtain the following error: Please deinstall the old quazip before building the new port. thanks for your feedback. However, I am not sure, if I've got you right: Currently BUILDING of the new quazip version fails. How can deinstallation of the old version correct this behavior? The build imports some definitions from old .h files or so ? OK that helps. I saw the same problem, deinstalled the old version, build and it worked. There are cases where ports have this kind of quirk. Sometimes, it's documented in /usr/ports/UPDATING. And if I force uninstallion of the old version and if subsequently building of the new version should fail, I will be left with broken dependencies: You are right, that might be a problem. You can handle it this way: Create a package file: pkg create quazip-0.5.1 It will create a quazip-0.5.1.txz in the working directory. Then deinstall, and if the build fails, re-add the old pkg: pkg add quazip-0.5.1.txz Yeah, thanks. I have learned a lot about pkg(ng) and packages. I did create the backup package but did not need it, because installation of new quazip version went smoothly. Thanks for doing so. I am rather new to FreeBSD and do not yet know, when there is time to directly contact a port maintainer. Until now I have first reported an issue to the forum or the mailing list. And in a second step I have informed the corresponding port maintainer. Is this the recommended way to proceed? In general, informing the maintainer, probably generating a problem-report (using the command send-pr) is the correct way. Ah, I have not been aware of the existence of this command. I'v used in the past a more unformal way of sending an email containing the - in my opinion - relevant information. In that special case http://www.freshports.org/archivers/quazip/ shows that the update was done after the maintainer failed to approve the update. So in this particular case informing him might be superfluous. Well, I am obviously not much trained in reading the commit history. I would conclude from the last entry 17 Mar 2014 15:54:23 and Approved by: maintainer timeout (nivit, 4 weeks) that the maintainer did not approve the commit and thus the commit remained untested. Can one conclude from this that the maintainer is aware of problems without reporting them? I cannot read that the maintainer failed to approve. Or can I assume for sure every port maintainer has subscribed to this this mailing list? Please give me a hint, if I have got the wrong information. Regards, 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
py-setuptools fails to install on 10-stable
Hello, devel/py-setuptools27 is a dependency of textproc/py-MarkupSafe, however it fails to install on 10-stable due to some conflict. === Installing for py27-setuptools27-2.0.1 === Checking if devel/py-setuptools27 already installed === Registering installation for py27-setuptools27-2.0.1 as automatic Installing py27-setuptools27-2.0.1...pkg-static: py27-setuptools27-2.0.1 conflicts with py27-setuptools-2.0.1 (installs files into the same place). Problematic file: /usr/local/lib/python2.7/site-packages/easy-install.pth.dist *** Error code 70 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: Update of quazip-0.5.1 to quazip-0.6.2 fails
Am Wed, 19 Mar 2014 20:24:04 +0100 schrieb Kurt Jaeger li...@opsec.eu: Hi! Hi Kurt, Correct, the 'maintainer timeout' only says: He had time to react and failed to react. OK, thanks. You can't assume that. So, if you see problems, a mail directly to the maintainer is one way, submitting a PR is another way to handle it. This list is yet another way to get feedback on the issue. The best way it to submit a PR, because then the state of the problem can be tracked. Thanks for your advice. Regards, 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: py-setuptools fails to install on 10-stable
See UPDATING 20140307 On Wed, Mar 19, 2014 at 12:35 PM, Mike Jakubik mike.jaku...@intertainservices.com wrote: Hello, devel/py-setuptools27 is a dependency of textproc/py-MarkupSafe, however it fails to install on 10-stable due to some conflict. === Installing for py27-setuptools27-2.0.1 === Checking if devel/py-setuptools27 already installed === Registering installation for py27-setuptools27-2.0.1 as automatic Installing py27-setuptools27-2.0.1...pkg-static: py27-setuptools27-2.0.1 conflicts with py27-setuptools-2.0.1 (installs files into the same place). Problematic file: /usr/local/lib/python2.7/site- packages/easy-install.pth.dist *** Error code 70 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 -- 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] 348645: 2x leftovers, 2x depend (??? in x11-toolkits/swt-devel), 2x success
- Update to version 5.3.0.0 - Add LICENSE PR: ports/187714 Submitted by: Radim Kolar hsn@sanatana.dharma - Build ID: 20140319191600-14215 Job owner: pa...@freebsd.org Buildtime: 60 minutes Enddate: Wed, 19 Mar 2014 20:15:56 GMT Revision: 348645 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348645 - Port:net-p2p/vuze 5.3.0.0 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~pa...@freebsd.org/20140319191600-14215-304462/vuze-5.3.0.0.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~pa...@freebsd.org/20140319191600-14215-304463/vuze-5.3.0.0.log Buildgroup: 8.4-QAT/amd64 Buildstatus: DEPEND (??? IN X11-TOOLKITS/SWT-DEVEL) Log: https://qat.redports.org//~pa...@freebsd.org/20140319191600-14215-304464/swt-devel-3.7.1_1,1.log Buildgroup: 8.4-QAT/i386 Buildstatus: DEPEND (??? IN X11-TOOLKITS/SWT-DEVEL) Log: https://qat.redports.org//~pa...@freebsd.org/20140319191600-14215-304465/swt-devel-3.7.1_1,1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~pa...@freebsd.org/20140319191600-14215-304466/vuze-5.3.0.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~pa...@freebsd.org/20140319191600-14215-304467/vuze-5.3.0.0.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140319191600-14215 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: Plex Media Server Port issues
On 03/19/2014 06:59 PM, Mark Felder wrote: On 2014-03-18 18:36, Kaya Saman wrote: Hi, I'm experiencing 3 issues with the Plex Media Server My configuration is running FreeBSD 10.0 x64 with the ports tree up to date. Issue 1: Upon first installing the port everything went fine however, PMS wouldn't start and kept complaining about a Python C Lang issue... Google'ing I managed to find a FreeBSD Forum posting stating to insert this line: #!/bin/sh export LD_LIBMAP=/lib/libc.so.7 /usr/local/share/plexmediaserver/libc.so.7 in the start.sh file located in: /usr/local/share/plexmediaserver In addition I had to comment out these two lines: #export LC_ALL=en_US.UTF-8 #export LANG=en_US.UTF-8 in the start.sh file. On FreeBSD we do not use the start.sh file supplied by Plex. We only use the /usr/local/etc/rc.d/plexmediaserver script. I did not strip it out of the port/package install as I did not feel that was necessary, but I will consider doing so to prevent this confusion in the future. Everything should work just fine using the FreeBSD rc script. I've tested on FreeBSD 9, 10, and CURRENT as well as in jails. Thanks for the response! Ok this is strange, as I've just installed to root OS (non-jailed). # ps aux |grep plex plex 46502 0.0 0.2 208064 17204 - IsJ 4:06PM 0:07.88 /usr/local/sh plex 46503 0.0 0.1 223992 10188 - SNJ 4:06PM 0:21.70 Plex Plug-in plex 46508 0.0 0.1 139844 5260 - SJ4:06PM 0:01.15 /usr/local/sh root 76712 0.0 0.0 18724 1760 3 S+9:12PM 0:00.00 grep plex # /usr/local/etc/rc.d/plexmediaserver start Starting plexmediaserver. Again I get Sign in to Plex Account when going to URL: http://ip:32400/web the redirect goes here: 32400/web/index.html#!/login Issue 2: As I'm running PMS in a Jail on a headless server, for some reason the rc script doesn't start properly?? This is quite weird... Using an SSH tunnel running: service plexmediaserver start or the /usr/local/etc/rc.d/plexmediaserver start method, not all services seem to come up properly. What exactly do you mean not all services seem to come up properly? You should see the following two processes at a minimum: /usr/local/share/plexmediaserver/Plex Media Server /usr/local/share/plexmediaserver/Plex DLNA Server Sorry for not being more specific... the web service sometimes doesn't come up on port 32400 also I run into above login situation on other occasions. If I start the service from VNC: /usr/local/etc/rc.d/plexmediaserver start then all seems to be fine?? snip time lapse Ok, just copied my previous Preferences.xml content over to new instance and now Plex comes up fine! DLNA also is working! Thankfully I held off sending this email until now as it seems everything is fine and working :-) Seems to be the Jail was my issue and perhaps not enough memory ;-) as 8GB with 40TB over ZFS isn't much!! Probably linked in with this is that not VNC'ing leaves me unable to login at the web interface. Putting my Plex ID/passwd combo in doesn't do a thing. This is a permissions issue caused by not running Plex from the rc script which automatically launches the process as the plex user. Issue 3: For some reason the DLNA server doesn't work properly Though it does show up as online using ps: plex 89291 0.0 0.2 139844 17808 - SJ 10:40PM 0:00.15 /usr/local/share/plexmediaserver/Plex DLNA Server It doesn't seem to broadcast itself. If you're running in a jail you're correct, this will not work. DLNA uses multicast and multicast does not work in FreeBSD jails. Aha hence my switch to root OS per above! Let's start fresh here; remove the port, delete any contents in /usr/local/plexdata, and reinstall the port. Add plexmediaserver_enable=YES to /etc/rc.conf and start the service. It should start up flawlessly as I've handled all these quirks in the rc script (except the multicast in a jail issue; I cannot fix that). ...again see above ___ 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: ushare-1.1a_9
On 19 Mar 2014, at 09:59, Dean Hollister deanhollis...@bigpond.com wrote: It appears that the ushare port requires GCC to build, but this requirement is not present in the Makefile. Attempting to build without GCC generates the following error: ... In file included from cfgparser.c:30: In file included from ./cfgparser.h:24: ./ushare.h:135:13: warning: inline function 'display_headers' is not defined [-Wundefined-inline] inline void display_headers (void); ^ cfgparser.c:316:3: note: used here display_headers (); ^ 1 warning generated. This is because the ushare author apparently does not understand how inline works in C. It is very simple to fix: just drop the attached files into /usr/ports/net/ushare/files, overwriting any existing ones. -Dimitry patch-trace.c Description: Binary data patch-trace.h Description: Binary data patch-ushare.c Description: Binary data patch-ushare.h Description: Binary data signature.asc Description: Message signed with OpenPGP using GPGMail
[QAT] 348651: 5x leftovers, 1x fetch
Upgrade to Grsibi 1.0.0! - Build ID: 20140319205401-41061 Job owner: thie...@freebsd.org Buildtime: 90 minutes Enddate: Wed, 19 Mar 2014 22:23:53 GMT Revision: 348651 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348651 - Port:finance/grisbi Buildgroup: 10.0-QAT/amd64 Buildstatus: FETCH Log: https://qat.redports.org//~thie...@freebsd.org/20140319205401-41061-304588/grisbi-1.0.0.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~thie...@freebsd.org/20140319205401-41061-304589/grisbi-1.0.0.log Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~thie...@freebsd.org/20140319205401-41061-304590/grisbi-1.0.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~thie...@freebsd.org/20140319205401-41061-304591/grisbi-1.0.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~thie...@freebsd.org/20140319205401-41061-304592/grisbi-1.0.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~thie...@freebsd.org/20140319205401-41061-304593/grisbi-1.0.0.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140319205401-41061 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
[QAT] 348650: 18x leftovers, 6x depend (patch in mail/thunderbird), 42x success, 6x patch
- Update Firefox to 28.0 - Update Firefox ESR to 24.4.0 - Update Thunderbird to 24.4.0 - Update NSPR to 4.10.4 - Update NSS to 3.15.5 - Switch GSTREAMER option for non-esr ports to depend on multimedia/gstreamer1 [2] - Switch to Uses/compiler.mk, defaults to lang/gcc47 on 8.x and 9.x - Use port dependencies for libogg, libvorbis, libopus, harfbuzz, graphite2 - Enable readahead in url-classifier, asmjs, download resume like on Linux - Build www/firefox and www/seamonkey faster using unified compilation - Unbreak build on sparc64 [1] - Workaround OPTIMIZED_CFLAGS startup crash on 8.x and 9.x - OPTIMIZED_CFLAGS is enabled by default - A few DEBUG build fixes - Add clang 3.2/3.3/3.4 workarounds for i386 - Mention known GSTREAMER issue in pkg-message Submitted by: Jan Beich PR: ports/186580 [1] Requested by: kwm [2] Security: http://www.vuxml.org/freebsd/610de647-af8d-11e3-a25b-b4b52fce4ce8.html - Build ID: 20140319204801-9838 Job owner: b...@freebsd.org Buildtime: 110 minutes Enddate: Wed, 19 Mar 2014 22:37:56 GMT Revision: 348650 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348650 - Port:devel/nspr 4.10.4 Buildgroup: 10.0-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304516/nspr-4.10.4.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304517/nspr-4.10.4.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304518/nspr-4.10.4.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304519/nspr-4.10.4.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304520/nspr-4.10.4.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304521/nspr-4.10.4.log - Port:mail/linux-thunderbird 24.4.0 Buildgroup: 10.0-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304522/linux-thunderbird-24.4.0.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304523/linux-thunderbird-24.4.0.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304524/linux-thunderbird-24.4.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304525/linux-thunderbird-24.4.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304526/linux-thunderbird-24.4.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304527/linux-thunderbird-24.4.0.log - Port:mail/thunderbird 24.4.0 Buildgroup: 10.0-QAT/amd64 Buildstatus: PATCH Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304528/thunderbird-24.4.0.log Buildgroup: 10.0-QAT/i386 Buildstatus: PATCH Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304529/thunderbird-24.4.0.log Buildgroup: 8.4-QAT/amd64 Buildstatus: PATCH Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304530/thunderbird-24.4.0.log Buildgroup: 8.4-QAT/i386 Buildstatus: PATCH Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304531/thunderbird-24.4.0.log Buildgroup: 9.2-QAT/amd64 Buildstatus: PATCH Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304532/thunderbird-24.4.0.log Buildgroup: 9.2-QAT/i386 Buildstatus: PATCH Log: https://qat.redports.org//~b...@freebsd.org/20140319204801-9838-304533/thunderbird-24.4.0.log - Port:mail/thunderbird-i18n 24.4.0 Buildgroup: 10.0-QAT/amd64 Buildstatus: DEPEND (PATCH IN MAIL/THUNDERBIRD) Log:
[QAT] 348647: 4x leftovers, 20x success
- Update libopenraw to 0.0.9. - Fix build on FreeBSD 8.x by adding compiler:c++11-lang. (Use same compiler/linker as Boost.) [1] - Chase library version change. - Consistently use OPENRAW as option name. PR: ports/186779 [1] - Build ID: 20140319192800-23574 Job owner: t...@freebsd.org Buildtime: 4 hours Enddate: Wed, 19 Mar 2014 23:10:55 GMT Revision: 348647 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=348647 - Port:deskutils/xfce4-tumbler 0.1.30_1 Buildgroup: 10.0-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304474/xfce4-tumbler-0.1.30_1.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304475/xfce4-tumbler-0.1.30_1.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304476/xfce4-tumbler-0.1.30_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304477/xfce4-tumbler-0.1.30_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304478/xfce4-tumbler-0.1.30_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304479/xfce4-tumbler-0.1.30_1.log - Port:graphics/gegl 0.2.0_6 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304480/gegl-0.2.0_6.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304481/gegl-0.2.0_6.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304482/gegl-0.2.0_6.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304483/gegl-0.2.0_6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304484/gegl-0.2.0_6.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304485/gegl-0.2.0_6.log - Port:graphics/gthumb 2.14.1_6 Buildgroup: 10.0-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304486/gthumb-2.14.1_6.log Buildgroup: 10.0-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304487/gthumb-2.14.1_6.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304488/gthumb-2.14.1_6.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304489/gthumb-2.14.1_6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304490/gthumb-2.14.1_6.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304491/gthumb-2.14.1_6.log - Port:graphics/libopenraw Buildgroup: 10.0-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304492/libopenraw-0.0.9.log Buildgroup: 10.0-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304493/libopenraw-0.0.9.log Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304494/libopenraw-0.0.9.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~t...@freebsd.org/20140319192800-23574-304495/libopenraw-0.0.9.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log:
