From owner-freebsd-qa@FreeBSD.ORG Sat Mar 6 16:14:17 2010 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24D13106566C for ; Sat, 6 Mar 2010 16:14:17 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from fallback4.mail.ru (fallback4.mail.ru [94.100.176.42]) by mx1.freebsd.org (Postfix) with ESMTP id 876B58FC15 for ; Sat, 6 Mar 2010 16:14:16 +0000 (UTC) Received: from mx34.mail.ru (mx34.mail.ru [94.100.176.48]) by fallback4.mail.ru (mPOP.Fallback_MX) with ESMTP id C1853136141E for ; Sat, 6 Mar 2010 18:58:35 +0300 (MSK) Received: from [91.155.189.108] (port=61618 helo=vova-vaio) by mx34.mail.ru with asmtp id 1NnwOd-0004YO-00 for freebsd-qa@freebsd.org; Sat, 06 Mar 2010 18:58:32 +0300 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-qa@freebsd.org Date: Sat, 06 Mar 2010 17:58:25 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: chukharev@mail.ru Message-ID: User-Agent: Opera Mail/10.10 (FreeBSD) X-Spam: Not detected X-Mras: Ok Subject: net-mgmt/wifimgr port test failure X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2010 16:14:17 -0000 The 'port test' command (ports-mgmt/porttools) tests a port for a number of possible errors by running portlint, building, packaging, installing, and de-installing with a check for left files. This is done with defined PREFIX and PKG_DBDIR variables. 'port test' command is a recommended by PortersHandbook test tool. When running 'port test' command in net-mgmt/wifimgr, the following output is generated. ===> Validating port with portlint looks fine. ===> flags: PREFIX=/home/chu/tmp/wifimgr-1.5_1 NO_DEPENDS=yes PKG_DBDIR=/tmp/pkg_db.AcvSn0Pw -- ===> Cleaning workspace before port test ===> Cleaning for wifimgr-1.5_1 ===> Extracting for wifimgr-1.5_1 => MD5 Checksum OK for wifimgr-1.5.tar.bz2. => SHA256 Checksum OK for wifimgr-1.5.tar.bz2. ===> Patching for wifimgr-1.5_1 ===> Configuring for wifimgr-1.5_1 ===> Building for wifimgr-1.5_1 cd src; make cc -O2 -pipe -march=native -fno-strict-aliasing -march=native -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -c wifimgr.c cc -O2 -pipe -march=native -fno-strict-aliasing -march=native -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -c string.c cc -O2 -pipe -march=native -fno-strict-aliasing -march=native -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -c net_list.c cc -O2 -pipe -march=native -fno-strict-aliasing -march=native -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -c wifimgr-gtk.c cc -o wifimgr wifimgr.o string.o net_list.o wifimgr-gtk.o -L/home/chu/tmp/wifimgr-1.5_1/lib -lintl -pthread -L/usr/local/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lgio-2.0 -lXext -lXrender -lXinerama -lXi -lXrandr -lXcursor -lXcomposite -lXdamage -lpangoft2-1.0 -lXfixes -lcairo -lX11 -lpango-1.0 -lm -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 cc -I/home/chu/tmp/wifimgr-1.5_1/include -c wifimgrsu.c wifimgrsu.c:47:21: error: libintl.h: No such file or directory wifimgrsu.c: In function 'main': wifimgrsu.c:71: warning: incompatible implicit declaration of built-in function 'gettext' wifimgrsu.c:92: warning: incompatible implicit declaration of built-in function 'gettext' wifimgrsu.c:102: warning: incompatible implicit declaration of built-in function 'gettext' wifimgrsu.c:137: warning: incompatible implicit declaration of built-in function 'gettext' wifimgrsu.c:149: warning: incompatible implicit declaration of built-in function 'gettext' *** Error code 1 Stop in /usr/home/chu/tmp/port_test_wrk/usr/ports/net-mgmt/wifimgr/work/wifimgr-1.5/src. *** Error code 1 Stop in /usr/home/chu/tmp/port_test_wrk/usr/ports/net-mgmt/wifimgr/work/wifimgr-1.5. *** Error code 1 Stop in /usr/ports/net-mgmt/wifimgr. ===> Error running make build ===> Cleaning up From owner-freebsd-qa@FreeBSD.ORG Sat Mar 6 16:34:17 2010 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E52CF106564A for ; Sat, 6 Mar 2010 16:34:17 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx34.mail.ru (mx34.mail.ru [94.100.176.48]) by mx1.freebsd.org (Postfix) with ESMTP id 753998FC0A for ; Sat, 6 Mar 2010 16:34:17 +0000 (UTC) Received: from [91.155.189.108] (port=61848 helo=vova-vaio) by mx34.mail.ru with asmtp id 1NnwxD-000Gt9-00 for freebsd-qa@freebsd.org; Sat, 06 Mar 2010 19:34:15 +0300 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "freebsd-qa@freebsd.org" Date: Sat, 06 Mar 2010 18:34:12 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: chukharev@mail.ru Message-ID: User-Agent: Opera Mail/10.10 (FreeBSD) X-Spam: Not detected X-Mras: Ok Subject: audio/amarok port test failure X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2010 16:34:18 -0000 The 'port test' command (ports-mgmt/porttools) tests a port for a number of possible errors by running portlint, building, packaging, installing, and de-installing with a check for left files. This is done with defined PREFIX and PKG_DBDIR variables. 'port test' command is recommended by the Porter's Handbook. Note that the port installs the usual way. When running 'port test' command in net-mgmt/wifimgr, the following output is generated indicated warnings from portlint and problems of packaging. The output is shortened. ===> Validating port with portlint WARN: /usr/ports/audio/amarok/pkg-plist: [567]: If and only if your port is DOCSDIR-safe (that is, a user can override DOCSDIR when building this port and the port will still work correctly) consider using DOCSDIR macro; if you are unsure if this this port is DOCSDIR-safe, then ignore this warning WARN: /usr/ports/audio/amarok/pkg-plist: [568]: If and only if your port is DOCSDIR-safe (that is, a user can override DOCSDIR when building this port and the port will still work correctly) consider using DOCSDIR macro; if you are unsure if this this port is DOCSDIR-safe, then ignore this warning WARN: /usr/ports/audio/amarok/pkg-plist: [569]: If and only if your port is DOCSDIR-safe (that is, a user can override DOCSDIR when building this port and the port will still work correctly) consider using DOCSDIR macro; if you are unsure if this this port is DOCSDIR-safe, then ignore this warning WARN: /usr/ports/audio/amarok/pkg-plist: [570]: If and only if your port is DOCSDIR-safe (that is, a user can override DOCSDIR when building this port and the port will still work correctly) consider using DOCSDIR macro; if you are unsure if this this port is DOCSDIR-safe, then ignore this warning WARN: /usr/ports/audio/amarok/pkg-plist: [571]: If and only if your port is DOCSDIR-safe (that is, a user can override DOCSDIR when building this port and the port will still work correctly) consider using DOCSDIR macro; if you are unsure if this this port is DOCSDIR-safe, then ignore this warning ....many more.... WARN: /usr/ports/audio/amarok/pkg-plist: [945]: If and only if your port is DOCSDIR-safe (that is, a user can override DOCSDIR when building this port and the port will still work correctly) consider using DOCSDIR macro; if you are unsure if this this port is DOCSDIR-safe, then ignore this warning WARN: /usr/ports/audio/amarok/pkg-plist: [946]: If and only if your port is DOCSDIR-safe (that is, a user can override DOCSDIR when building this port and the port will still work correctly) consider using DOCSDIR macro; if you are unsure if this this port is DOCSDIR-safe, then ignore this warning WARN: /usr/ports/audio/amarok/pkg-plist: Both ``%%PORTDOCS%%@dirrm %%DOCSDIR%%'' and ``%%PORTDOCS%%@unexec %D/%%DOCSDIR%% 2>/dev/null || true'' are missing. At least one should be used. WARN: Makefile: use ".if !defined(NOPORTDOCS)" to wrap installation of files into /usr/local/share/doc. WARN: Makefile: Consider adding support for a WITHOUT_NLS knob to conditionally disable gettext support. 0 fatal errors and 383 warnings found. ===> flags: PREFIX=/home/chu/tmp/amarok-1.4.10_7 NO_DEPENDS=yes PKG_DBDIR=/tmp/pkg_db.kjmtIaM4 -- ===> Cleaning workspace before port test ===> Cleaning for amarok-1.4.10_7 ===> Found saved configuration for amarok-1.4.10_7 ===> Extracting for amarok-1.4.10_7 => MD5 Checksum OK for amarok-1.4.10.tar.bz2. => SHA256 Checksum OK for amarok-1.4.10.tar.bz2. ===> Patching for amarok-1.4.10_7 ===> Applying FreeBSD patches for amarok-1.4.10_7 ===> Configuring for amarok-1.4.10_7 checking build system type... i386-portbld-freebsd8 checking host system type... i386-portbld-freebsd8 checking target system type... i386-portbld-freebsd8 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/local/bin/gmkdir -p checking for gawk... gawk checking whether gmake sets $(MAKE)... yes .... gmake[2]: Entering directory `/usr/ports/audio/amarok/work/amarok-1.4.10/po/uz@cyrillic' Making install in . gmake[3]: Entering directory `/usr/ports/audio/amarok/work/amarok-1.4.10/po/uz@cyrillic' gmake[4]: Entering directory `/usr/ports/audio/amarok/work/amarok-1.4.10/po/uz@cyrillic' gmake[4]: Nothing to be done for `install-exec-am'. /bin/sh ../../admin/mkinstalldirs /home/chu/tmp/amarok-1.4.10_7/share/locale/uz@cyrillic/LC_MESSAGES mkdir /home/chu/tmp/amarok-1.4.10_7/share/locale/uz@cyrillic mkdir /home/chu/tmp/amarok-1.4.10_7/share/locale/uz@cyrillic/LC_MESSAGES install -o root -g wheel -m 444 amarok.gmo /home/chu/tmp/amarok-1.4.10_7/share/locale/uz@cyrillic/LC_MESSAGES/amarok.mo gmake[4]: Leaving directory `/usr/ports/audio/amarok/work/amarok-1.4.10/po/uz@cyrillic' gmake[3]: Leaving directory `/usr/ports/audio/amarok/work/amarok-1.4.10/po/uz@cyrillic' gmake[2]: Leaving directory `/usr/ports/audio/amarok/work/amarok-1.4.10/po/uz@cyrillic' gmake[1]: Leaving directory `/usr/ports/audio/amarok/work/amarok-1.4.10/po' gmake[1]: Entering directory `/usr/ports/audio/amarok/work/amarok-1.4.10' gmake[2]: Entering directory `/usr/ports/audio/amarok/work/amarok-1.4.10' gmake[2]: Nothing to be done for `install-exec-am'. gmake[2]: Leaving directory `/usr/ports/audio/amarok/work/amarok-1.4.10' gmake[1]: Leaving directory `/usr/ports/audio/amarok/work/amarok-1.4.10' ATTENTION: In order to use certain devices (MTP, iPod, ..) through Amarok you need to be able to mount USB devices as the user running Amarok. Read more on how to set this up on FreeBSD here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/usb-disks.html ===> Running ldconfig /sbin/ldconfig -m /home/chu/tmp/amarok-1.4.10_7/lib ===> Registering installation for amarok-1.4.10_7 ===> Building package for amarok-1.4.10_7 tar: bin/amarok: Cannot stat: No such file or directory tar: bin/amarok_daapserver.rb: Cannot stat: No such file or directory tar: bin/amarok_proxy.rb: Cannot stat: No such file or directory tar: bin/amarokapp: Cannot stat: No such file or directory .... tar: share/services/amaroklastfm.protocol: Cannot stat: No such file or directory tar: share/services/amarokpcast.protocol: Cannot stat: No such file or directory tar: share/servicetypes/amarok_codecinstall.desktop: Cannot stat: No such file or directory tar: share/servicetypes/amarok_plugin.desktop: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 Creating package /usr/ports/packages/All/amarok-1.4.10_7.tbz Registering depends:. Creating bzip'd tar ball in '/usr/ports/packages/All/amarok-1.4.10_7.tbz' *** Error code 1 Stop in /usr/ports/audio/amarok. ===> Error running make package ===> Files currently installed in PREFIX share/doc/HTML/da/amarok/config.docbook share/doc/HTML/da/amarok/requirements.docbook share/doc/HTML/da/amarok/faq.docbook share/doc/HTML/da/amarok/quick.docbook share/doc/HTML/da/amarok/advanced.docbook share/doc/HTML/da/amarok/index.docbook .... share/locale/ku/LC_MESSAGES/amarok.mo share/locale/lo/LC_MESSAGES/amarok.mo share/locale/se/LC_MESSAGES/amarok.mo share/locale/rw/LC_MESSAGES/amarok.mo share/locale/ss/LC_MESSAGES/amarok.mo share/locale/nds/LC_MESSAGES/amarok.mo share/locale/uz@cyrillic/LC_MESSAGES/amarok.mo ===> Cleaning up From owner-freebsd-qa@FreeBSD.ORG Sat Mar 6 16:41:51 2010 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D895F106568B for ; Sat, 6 Mar 2010 16:41:51 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx76.mail.ru (mx76.mail.ru [94.100.176.91]) by mx1.freebsd.org (Postfix) with ESMTP id 96F3C8FC19 for ; Sat, 6 Mar 2010 16:41:51 +0000 (UTC) Received: from [91.155.189.108] (port=61886 helo=vova-vaio) by mx76.mail.ru with asmtp id 1Nnx4X-000A61-00 for freebsd-qa@freebsd.org; Sat, 06 Mar 2010 19:41:49 +0300 Content-Type: text/plain; charset=koi8-r; format=flowed; delsp=yes To: "freebsd-qa@freebsd.org" Date: Sat, 06 Mar 2010 18:41:47 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: chukharev@mail.ru Message-ID: User-Agent: Opera Mail/10.10 (FreeBSD) X-Spam: Not detected X-Mras: Ok Subject: sysutils/gnome-system-tools port test failure X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2010 16:41:52 -0000 The 'port test' command (ports-mgmt/porttools) tests a port for a number of possible errors by running portlint, building, packaging, installing, and de-installing with a check for left files. This is done with defined PREFIX and PKG_DBDIR variables. 'port test' command is recommended by the Porter's Handbook. Note that the port installs the usual way. When running 'port test' command in sysutils/gnome-system-tools, the following output is generated indicating warnings from portlint and problems of packaging. The output is shortened. ===> Validating port with portlint WARN: Makefile: Consider adding support for a WITHOUT_NLS knob to conditionally disable gettext support. 0 fatal errors and 1 warning found. ===> flags: PREFIX=/home/chu/tmp/gnome-system-tools-2.28.2_1 NO_DEPENDS=yes PKG_DBDIR=/tmp/pkg_db.BpBdvIMN -- ===> Cleaning workspace before port test ===> Cleaning for gnome-system-tools-2.28.2_1 ===> Extracting for gnome-system-tools-2.28.2_1 => MD5 Checksum OK for gnome2/gnome-system-tools-2.28.2.tar.bz2. => SHA256 Checksum OK for gnome2/gnome-system-tools-2.28.2.tar.bz2. ===> Patching for gnome-system-tools-2.28.2_1 ===> Applying FreeBSD patches for gnome-system-tools-2.28.2_1 ===> Configuring for gnome-system-tools-2.28.2_1 configure: WARNING: unrecognized options: --with-html-dir, --disable-gtk-doc checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/local/bin/gmkdir -p checking for gawk... gawk checking whether gmake sets $(MAKE)... yes checking whether NLS is requested... yes checking for style of include used by gmake... GNU checking for gcc... cc .... Installed schema `/schemas/apps/gnome-system-tools/users/showall' for locale `kn' Installed schema `/schemas/apps/gnome-system-tools/users/showall' for locale `gl' Installed schema `/schemas/apps/gnome-system-tools/users/showall' for locale `ko' test -z "/home/chu/tmp/gnome-system-tools-2.28.2_1/libdata/pkgconfig" || /usr/local/bin/gmkdir -p "/home/chu/tmp/gnome-system-tools-2.28.2_1/libdata/pkgconfig" install -o root -g wheel -m 444 gnome-system-tools.pc '/home/chu/tmp/gnome-system-tools-2.28.2_1/libdata/pkgconfig' test -z "/home/chu/tmp/gnome-system-tools-2.28.2_1/etc/gconf/schemas" || /usr/local/bin/gmkdir -p "/home/chu/tmp/gnome-system-tools-2.28.2_1/etc/gconf/schemas" install -o root -g wheel -m 444 gnome-system-tools.schemas '/home/chu/tmp/gnome-system-tools-2.28.2_1/etc/gconf/schemas' gmake[2]: Leaving directory `/usr/ports/sysutils/gnome-system-tools/work/gnome-system-tools-2.28.2' gmake[1]: Leaving directory `/usr/ports/sysutils/gnome-system-tools/work/gnome-system-tools-2.28.2' ===> Running ldconfig /sbin/ldconfig -m /home/chu/tmp/gnome-system-tools-2.28.2_1/lib ===> Registering installation for gnome-system-tools-2.28.2_1 ===> Building package for gnome-system-tools-2.28.2_1 tar: lib/nautilus/extensions-2.0/libnautilus-gst-shares.a: Cannot stat: No such file or directory tar: lib/nautilus/extensions-2.0/libnautilus-gst-shares.la: Cannot stat: No such file or directory tar: lib/nautilus/extensions-2.0/libnautilus-gst-shares.so: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 Creating package /usr/ports/packages/All/gnome-system-tools-2.28.2_1.tbz Registering depends:. Creating bzip'd tar ball in '/usr/ports/packages/All/gnome-system-tools-2.28.2_1.tbz' *** Error code 1 Stop in /usr/ports/sysutils/gnome-system-tools. ===> Error running make package ===> Files currently installed in PREFIX bin/network-admin bin/services-admin bin/shares-admin bin/time-admin bin/users-admin etc/gconf/gconf.xml.defaults/%gconf-tree.xml etc/gconf/schemas/gnome-system-tools.schemas libdata/pkgconfig/gnome-system-tools.pc share/locale/am/LC_MESSAGES/gnome-system-tools.mo share/locale/ar/LC_MESSAGES/gnome-system-tools.mo .... share/gnome-system-tools/ui/time.ui share/gnome-system-tools/ui/users.ui share/gnome-system-tools/pixmaps/world_map-960.png share/applications/network.desktop share/applications/services.desktop share/applications/shares.desktop share/applications/time.desktop share/applications/users.desktop ===> Cleaning up From owner-freebsd-qa@FreeBSD.ORG Sat Mar 6 16:44:14 2010 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01729106564A for ; Sat, 6 Mar 2010 16:44:14 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx71.mail.ru (mx71.mail.ru [94.100.176.85]) by mx1.freebsd.org (Postfix) with ESMTP id AF6088FC08 for ; Sat, 6 Mar 2010 16:44:13 +0000 (UTC) Received: from [91.155.189.108] (port=61901 helo=vova-vaio) by mx71.mail.ru with asmtp id 1Nnx6p-000Ga3-00 for freebsd-qa@freebsd.org; Sat, 06 Mar 2010 19:44:11 +0300 Content-Type: text/plain; charset=koi8-r; format=flowed; delsp=yes To: "freebsd-qa@freebsd.org" References: Date: Sat, 06 Mar 2010 18:44:10 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: chukharev@mail.ru Message-ID: In-Reply-To: User-Agent: Opera Mail/10.10 (FreeBSD) X-Spam: Not detected X-Mras: Ok Subject: Re: audio/amarok port test failure X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2010 16:44:14 -0000 > When running 'port test' command in net-mgmt/wifimgr, the following output is generated ... in audio/amarok ... From owner-freebsd-qa@FreeBSD.ORG Sat Mar 6 16:55:38 2010 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FCB2106564A for ; Sat, 6 Mar 2010 16:55:38 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx30.mail.ru (mx30.mail.ru [94.100.176.44]) by mx1.freebsd.org (Postfix) with ESMTP id E1F1F8FC18 for ; Sat, 6 Mar 2010 16:55:37 +0000 (UTC) Received: from [91.155.189.108] (port=61952 helo=vova-vaio) by mx30.mail.ru with asmtp id 1NnxHr-000B4z-00 for freebsd-qa@freebsd.org; Sat, 06 Mar 2010 19:55:35 +0300 Content-Type: text/plain; charset=koi8-r; format=flowed; delsp=yes Date: Sat, 06 Mar 2010 18:55:33 +0200 To: "freebsd-qa@freebsd.org" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: chukharev@mail.ru Message-ID: User-Agent: Opera Mail/10.10 (FreeBSD) X-Spam: Not detected X-Mras: Ok Subject: print/enscript-a4 port test failure X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2010 16:55:38 -0000 The 'port test' command (ports-mgmt/porttools) tests a port for a number of possible errors by running portlint, building, packaging, installing, and de-installing with a check for left files. This is done with defined PREFIX and PKG_DBDIR variables. 'port test' command is recommended by the Porter's Handbook. Note that the port installs the usual way. When running 'port test' command in print/enscript-a4, the following output is generated indicating fatal errors from portlint. ===> Validating port with portlint FATAL: Makefile: extra item "PAPERSIZE" placed in the PORTNAME section. FATAL: Makefile: extra item "MASTERDIR" placed in the PORTNAME section. WARN: Makefile: only one MASTER_SITE configured. Consider adding additional mirrors. Use of uninitialized value $tmp in pattern match (m//) at /usr/local/bin/portlint line 2670. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. Use of uninitialized value $str in pattern match (m//) at /usr/local/bin/portlint line 3052. 2 fatal errors and 1 warning found. Error validating port From owner-freebsd-qa@FreeBSD.ORG Sat Mar 6 17:00:04 2010 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4BD61065670 for ; Sat, 6 Mar 2010 17:00:04 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx33.mail.ru (mx33.mail.ru [94.100.176.47]) by mx1.freebsd.org (Postfix) with ESMTP id 676B08FC12 for ; Sat, 6 Mar 2010 17:00:03 +0000 (UTC) Received: from [91.155.189.108] (port=62498 helo=vova-vaio) by mx33.mail.ru with asmtp id 1NnxM9-000Pdj-00 for freebsd-qa@freebsd.org; Sat, 06 Mar 2010 20:00:01 +0300 Content-Type: text/plain; charset=koi8-r; format=flowed; delsp=yes Date: Sat, 06 Mar 2010 18:59:59 +0200 To: "freebsd-qa@freebsd.org" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: chukharev@mail.ru Message-ID: User-Agent: Opera Mail/10.10 (FreeBSD) X-Spam: Not detected X-Mras: Ok Subject: graphics/graphviz port test failure X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2010 17:00:04 -0000 The 'port test' command (ports-mgmt/porttools) tests a port for a number of possible errors by running portlint, building, packaging, installing, and de-installing with a check for left files. This is done with defined PREFIX and PKG_DBDIR variables. 'port test' command is recommended by the Porter's Handbook. Note that the port installs the usual way. When running 'port test' command in graphics/graphviz, the following output is generated indicating fatal errors from portlint. graphics/graphviz +++++++++++++++ ===> Validating port with portlint WARN: Makefile: [391]: use ${VARIABLE}, instead of $(VARIABLE). FATAL: Makefile: [331]: USE_RUBY is set after including bsd.port.pre.mk. WARN: Makefile: [213]: is USE_GNOME a user-settable option? Consider using WITH_GNOME instead. WARN: Makefile: [217]: is USE_XORG a user-settable option? Consider using WITH_XORG instead. WARN: Makefile: possible use of absolute pathname "/nonexistent". WARN: Makefile: CFLAGS/CXXFLAGS are not needed in CONFIGURE_ENV as they are already added there in bsd.port.mk. WARN: Makefile: only one MASTER_SITE configured. Consider adding additional mirrors. 1 fatal error and 6 warnings found. Error validating port From owner-freebsd-qa@FreeBSD.ORG Sat Mar 6 17:07:24 2010 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD7F2106566B for ; Sat, 6 Mar 2010 17:07:24 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx48.mail.ru (mx48.mail.ru [94.100.176.62]) by mx1.freebsd.org (Postfix) with ESMTP id 8C3B48FC0A for ; Sat, 6 Mar 2010 17:07:24 +0000 (UTC) Received: from [91.155.189.108] (port=62914 helo=vova-vaio) by mx48.mail.ru with asmtp id 1NnxTG-000NL5-00 for freebsd-qa@freebsd.org; Sat, 06 Mar 2010 20:07:22 +0300 Content-Type: text/plain; charset=koi8-r; format=flowed; delsp=yes Date: Sat, 06 Mar 2010 19:07:20 +0200 To: "freebsd-qa@freebsd.org" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: chukharev@mail.ru Message-ID: User-Agent: Opera Mail/10.10 (FreeBSD) X-Spam: Not detected X-Mras: Ok Subject: multimedia/ffmpeg port test failure X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2010 17:07:24 -0000 The 'port test' command (ports-mgmt/porttools) tests a port for a number of possible errors by running portlint, building, packaging, installing, and de-installing with a check for left files. This is done with defined PREFIX and PKG_DBDIR variables. 'port test' command is recommended by the Porter's Handbook. Note that the port installs the usual way. When running 'port test' command in multimedia/ffmpeg, the following output is generated indicating fatal errors from portlint. multimedia/ffmpeg +++++++++++++++ ===> Validating port with portlint FATAL: Makefile: [287]: contiguous blank lines (> 1 lines) found. WARN: Makefile: [315]: use ${VARIABLE}, instead of $(VARIABLE). WARN: Makefile: [247]: You may remove pkg-plist if you use PLIST_FILES and/or PLIST_DIRS. WARN: Makefile: [34]: possible direct use of command "install" found. use ${INSTALL_foobaa} instead. WARN: Makefile: only one MASTER_SITE configured. Consider adding additional mirrors. 1 fatal error and 4 warnings found. Error validating port From owner-freebsd-qa@FreeBSD.ORG Sat Mar 6 17:13:10 2010 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B35F106564A for ; Sat, 6 Mar 2010 17:13:10 +0000 (UTC) (envelope-from chukharev@mail.ru) Received: from mx71.mail.ru (mx71.mail.ru [94.100.176.85]) by mx1.freebsd.org (Postfix) with ESMTP id 2ADD38FC0A for ; Sat, 6 Mar 2010 17:13:09 +0000 (UTC) Received: from [91.155.189.108] (port=62936 helo=vova-vaio) by mx71.mail.ru with asmtp id 1NnxYo-0001yV-00 for freebsd-qa@freebsd.org; Sat, 06 Mar 2010 20:13:07 +0300 Content-Type: text/plain; charset=koi8-r; format=flowed; delsp=yes Date: Sat, 06 Mar 2010 19:13:05 +0200 To: "freebsd-qa@freebsd.org" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: chukharev@mail.ru Message-ID: User-Agent: Opera Mail/10.10 (FreeBSD) X-Spam: Not detected X-Mras: Ok Subject: audio/rhythmbox X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2010 17:13:10 -0000 The 'port test' command (ports-mgmt/porttools) tests a port for a number of possible errors by running portlint, building, packaging, installing, and de-installing with a check for left files. This is done with defined PREFIX and PKG_DBDIR variables. 'port test' command is recommended by the Porter's Handbook. Note that the port installs the usual way. When running 'port test' command in audio/rhythmbox, the following output is generated indicating fatal errors from portlint. audio/rhythmbox +++++++++++++++ ===> Validating port with portlint WARN: /usr/ports/audio/rhythmbox/pkg-plist: [592]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [593]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [594]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [595]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [596]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [597]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [598]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [599]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [600]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [601]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [602]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [603]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [604]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [605]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [606]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [607]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [608]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [609]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [610]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [611]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [612]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [613]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [614]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [615]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [616]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [617]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [618]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [619]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [620]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [621]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [622]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [623]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [626]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [627]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [628]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [629]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [630]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [631]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [632]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [633]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [634]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [635]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [636]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [637]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [638]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [639]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [640]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [641]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [642]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [643]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [644]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [645]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [646]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [647]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [648]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [649]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [650]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [651]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [652]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [653]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [654]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [655]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [656]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [657]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [658]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning WARN: /usr/ports/audio/rhythmbox/pkg-plist: [659]: If and only if your port is DATADIR-safe (that is, a user can override DATADIR when building this port and the port will still work correctly) consider using DATADIR macro; if you are unsure if this port is DATADIR-safe, then ignore this warning FATAL: Makefile: [109]: USE_PYTHON is set after including bsd.port.pre.mk. WARN: Makefile: use ".if !defined(NOPORTDOCS)" to wrap installation of files into /usr/local/share/doc. WARN: Makefile: Consider adding support for a WITHOUT_NLS knob to conditionally disable gettext support. WARN: Makefile: [111]: possible direct use of command "python" found. use ${PYTHON_CMD} instead. 1 fatal error and 69 warnings found. Error validating port