Re: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
On Mon, May 12, 2014 at 10:31:06AM +1000 I heard the voice of andrew clarke, and lo! it spake thus: A short script I threw together to show any ports installed that are marked as unstaged in the above list: Alternately, to check against the local ports tree: % pkg query -a '%o' | xargs -n1 -I% sh -c 'if make -C /usr/ports/% -V NO_STAGE | grep -v '^\$' /dev/null ; then echo % ; fi' -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ 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
R4 R4i SDHC Game Memory Flash card and save up to 69%
Dear client, We're pleased to inform you that, with months of research, we've introduced our new R4 products to market. We offer an over 50% discount on all our R4/R4i 3DS Cards. http://www.ggnds.com/nds-card-list.html You can get an additional discount of 15% with coupon code ggnds.com. Promo period is until May 31 only. So hurry before you miss your chance on this amazing offer. ___ 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: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
On 10/05/2014 17:33, Bryan Drewery wrote: You are receiving this mail as it affects FreeBSD ports that you maintain. In September 2013, the Ports framework learned how to Stage ports. On June 31st, all unstaged ports will be marked DEPRECATED and have their MAINTAINER reset. On August 31st, all unstaged ports will be removed from the ports tree. That's hardly fair with maintainer-updates not being committed for months. I usually stop updating my ports when that happens and resume my activity when my confidence that stuff has a chance of being committed is restored. I.e. when all my old updates have been committed. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
On 5/12/2014 10:01, Dominic Fandrey wrote: On 10/05/2014 17:33, Bryan Drewery wrote: You are receiving this mail as it affects FreeBSD ports that you maintain. In September 2013, the Ports framework learned how to Stage ports. On June 31st, all unstaged ports will be marked DEPRECATED and have their MAINTAINER reset. On August 31st, all unstaged ports will be removed from the ports tree. That's hardly fair with maintainer-updates not being committed for months. I would have thought it to be obvious, but ports with valid and applicable PRs are excluded. No unstaged port with a pending PR to stage it is going to be removed, the PR will get processed instead. I usually stop updating my ports when that happens and resume my activity when my confidence that stuff has a chance of being committed is restored. I.e. when all my old updates have been committed. I commit PR patches that are 6 to 18 months old fairly frequently. There is obviously a huge backlog but many PRs are processed daily. The PRs that aren't getting processed quickly are [NEW PORT] PRs (and apparently anything mentioning fuse-fs for some reason). A staging PR is going to jump the line; it has a higher priority. Why would you even entertain the idea that a staging PR will fall between the cracks? John ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Kalzium build fails (part of KDE4 port upgrade)
On Sunday 11 May 2014 17:11:28 Ajtim wrote: On Sunday 11 May 2014 22:56:52 Raphael Kubo da Costa wrote: Dave freebs...@dgmm.net writes: [ 48%] Generating parser.cmx [ 49%] Generating datastruct.cmx [ 50%] Generating chem.cmi [ 51%] Generating lexer.cmx [ 51%] Generating chem.cmx File /usr/ports/science/kalzium/work/kalzium-4.12.5/src/solver/chem.ml, line 1: Error: /usr/local/lib/ocaml/facile/facile.cmi is not a compiled interface for this version of OCaml. It seems to be for an older version of OCaml. Does it help if you rebuild math/facile? ___ 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 I did rebuild math/facile but I have problem to install science/avogadro (FreeBSD 10.0-RELEASE, amd64): Compressing man pages (compress-man) === Starting check for runtime dependencies === Gathering dependency list for science/avogadro from ports === Dependency check complete for science/avogadro === kalzium-4.12.4 science/avogadro (1/1) === Installing for avogadro-1.1.1_2 === Checking if science/avogadro already installed === Registering installation for avogadro-1.1.1_2 as automatic pkg-static: lstat(/usr/ports/science/avogadro/work/stage/usr/local/include/avogadro/pyth onerror.h): No such file or directory pkg-static: lstat(/usr/ports/science/avogadro/work/stage/usr/local/include/avogadro/pyth oninterpreter.h): No such file or directory pkg-static: lstat(/usr/ports/science/avogadro/work/stage/usr/local/include/avogadro/pyth onscript.h): No such file or directory pkg-static: lstat(/usr/ports/science/avogadro/work/stage/usr/local/lib/avogadro/1_1/exte nsions/pythonterminal.so): No such file or directory pkg-static: lstat(/usr/ports/science/avogadro/work/stage/usr/local/lib/python2.7/site- packages/Avogadro.so): No such file or directory pkg-static: lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/eng ineScripts/wireframe.py): No such file or directory pkg-static: lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/ext ensionScripts/example.py): No such file or directory pkg-static: lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/ext ensionScripts/): No such file or directory pkg-static: lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/eng ineScripts/): No such file or directory pkg-static: lstat(/usr/ports/science/avogadro/work/stage/usr/local/share/libavogadro/): No such file or directory *** Error code 74 Stop. make[1]: stopped in /usr/ports/science/avogadro *** Error code 1 Stop. make: stopped in /usr/ports/science/avogadro === Installation of avogadro-1.1.1_2 (science/avogadro) failed === Aborting update === Update for science/avogadro failed === Aborting update === Killing background jobs Terminated === You can restart from the point of failure with this command line: portmaster flags science/kalzium science/avogadro Avogradro install if I use NO_STAGE=yes option in Makefile. -- ajtiM http://www.redbubble.com/people/lumiwa ___ 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 +-+ devel/ocaml-lacaml | 7.0.7 | 7.0.14 +-+ 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
Re: To all port maintainers: libtool
On Mon, 12 May 2014 06:58:06 +0200 Matthias Andree wrote: Issue #1: .la files I just received PR 189491 (which proposes USES=libtool:keepla) and looked at it, and thought it good to kill the .la files, so I have tried USES=libtool, without keepla or stuff. The ports are depended on by a lot of other ports so I'd be careful with deleting the .la files. The port also has a patch to flip from -avoid-version to -version-info 0:0:0, and I tried to build with or without. (It should not matter much because libdb does not have non-system requisites, i. e. the port has no LIB_DEPENDS - it only uses libpthreads.) Now, with USES=libtool added, I either have both the foo.so.0 and foo.so.0.0.0 files, with the SONAME being the libdb-4.8.so.0, or if I leave the original upstream -avoid-version setting, I get libdb-4.8.so as SONAME and see libdb-4.8.so.0 files missing. With USES=libtool:keepla, this does not happen. It is utterly unclear to me how that fits together, so my first question is: can you reproduce this behaviour, or is my system goofing up? What concerns me about that is (1) that the file matching the SONAME of the library is merely a symlink, and (2) that the USES=libtool:keepla option apparently might have more effects than documented, namely, adding more library_names with the .0.0.0 and .0 suffix. During compilation and installation the behaviour with and without :keepla is exactly the same. So except for the .la files you should see exactly the same content in the staging area. For ports like this though, that meddle with version-info it's ok to add something like this to the Makefile: # TODO: remove :oldver together with patch-dist::configure USES= libtool:oldver Then it will be dealt with when we can start moving away from :oldver. I already did something like this in graphics/imlib, graphics/jpeg and graphics/tiff. Issue #2: libpthread. An .la file might look like this: [...] # Linker flags that can not go in dependency_libs. inherited_linker_flags=' -pthread' # Libraries that this one depends upon. dependency_libs=' -lpthread' [...] Now, if I remove the .la file, and a slave port that uses libtool to link will then have to list -pthread explicitly on the newer FreeBSD releases (because those fail linking if indirect .so requisites are missing). Yes, but this is no different from other libraries. If some other port needs libpthread it should link to it itself. It's not this port's responsibility. :keepla causes the inherited_linker_flags=-pthread to remain set, so I presume it is safe in this case. However, it does not appear to me that keepla is a temporary measure here, but it looks like it needs to stay forever. :keepla will stay yes, because it's possible for a port to use them, e.g. in combination with libltdl. ___ 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
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o ports/189698Add staging support to comms/java-commapi-freebsd o ports/189697Add staging support to comms/java-commapi f ports/189694[patch] ports/Mk/Uses/perl.mk: post-stage fails during f ports/189691[PATCH] devel/scons m4 tool, BSD specific problem. o ports/189690Update usr/ports/math/qrupdate as requested for port s o ports/189682[patch] add support for staging/options to print/cups- o ports/189679[MAINTAINER] math/units - 2.11 o ports/189678[maintainer update] textproc/ibus: stagify o ports/189676mcabber window resize broken by MFV r262639: ncurses 5 o ports/189674[MAINTAINER] net/fping - 3.10 o ports/189664Remove net/rsmb o ports/189660[maintainer-update] fix staging support for www/nanobl o ports/189659[maintainer-update] Add staging support to www/nanoblo o ports/189658[maintainer-update] Add staging support to audio/ogg2m f ports/189651[PATCH] lang/fasm update to 1.71.17 o ports/189648Resurrect devel/asl o ports/189647[maintainer update] emulators/visualboyadvance-m to r1 o ports/189645Update net/netpipes for staging o ports/189644Update graphics/pfstools for staging o ports/189641Delete the sysutils/3dm port o ports/189639Support staging for sysutils/djmount o ports/189638Support staging for sysutils/djmount o ports/189637Support staging for chinese/ibus-chewing o ports/189636net-mgmt/wifimgr: update to 1.11, add staging support o ports/189629[maintainer-update] update security/kpcli to 2.5 o ports/189628www/phpgedview: move to attic o ports/189627www/webtrees: update to 1.5.3, add staging support o ports/189625[MAINTAINER UPDATE] databases/spatialite_gui add stagg o ports/189622[MAINTAINER UPDATE] audio/lingot add stagging o ports/189621add 'staging' support to comms/uarduno o ports/189620[maintainer update] net/rtg: convert to staged port o ports/189617[MAINTAINER] science/h5utils add staging support f ports/189615[PATCH] Add Stage Support to irc/unreal o ports/189570[maintainer-update] replaced dependency o ports/189541[Maintainer] math/giacxcas update f ports/189540[UPDATE] databases/postgis21 o ports/189528Xcdroast cannot find cd-rom drive o ports/189497Deluge not downloading blocklist o ports/189494[PATCH] devel/magit-emacs24: add GIT_SUBVERSION option o ports/189493[MAINTAINER] japanese/ja-mecab: Convert to 'USES=libto o ports/189489update mail/mailagent to 3.1.78 to unbreak build with o ports/189488libxul does not compile in FreeBSD10 with last soundto f ports/189486[PATCH] sysutils/automount: disable EXFAT by default f ports/189484sysutils/modules segfaults when adding a new path f ports/189476[PATCH] net/fping: update to 3.10 f ports/189474[UPDATE] audio/asunder to 2.5 f ports/189458[PATCH] mail/postfix-policyd-spf-perl: update to 2.010 o ports/189455[MAINTAINER] graphics/leptonica: update to 1.70 o ports/189454[MAINTAINER] graphics/iulib: support staging o ports/189453hdf5-1.8.12 build error on FreeBSD-10.0-p2-amd64 o ports/189452[MAINTAINER] japanese/nhocr: update to 0.21 o ports/189447port upgrade: netdot-1.0.4 to netdot 1.0.6 o ports/189443New port: Split off amttool from comms/amtterm into sy o ports/189441dovecot-2.2-pigeonhole-0.4.2.tar.gz Not found o ports/189440lua-nginx-module-v0.9.4-0 size mismatch o ports/189439www/revive-adserver [new port], obsoletes www/openx o ports/189437Security update available for drupal7 o ports/189424converters/wkhtmltopng needs x11-fonts/xorg-fonts o ports/189414[new port] databases/php55-redis, PHP5-Extension for R f ports/189408[patch] deskutils/fet update to 5.21.3, allow build on o ports/189403[new port] net/wackamole - technically: resurrection+ o ports/189401New port: sysutils/amtc -- Threaded Intel AMT/vPro mas o ports/189397webinterface of print/cups not functional when install f ports/189390port lang/maude compilation failed f ports/189386
Maintainer timeout: security patch, ports/188945 (www/drupal6)
Would any committer be able to look at the captioned patch for www/drupal6? This is a security update that has been pending since 24 April. Many thanks Simon Wright. ___ 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: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
On Sat, May 10, 2014 at 11:33 AM, Bryan Drewery bdrew...@freebsd.org wrote: You are receiving this mail as it affects FreeBSD ports that you maintain. Clearly you have a list that identifies these ports. Would it be possible to share it so we can easily find which if our ports are still affected? 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: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
On Mon, May 12, 2014 at 1:58 PM, Vick Khera vi...@khera.org wrote: On Sat, May 10, 2014 at 11:33 AM, Bryan Drewery bdrew...@freebsd.org wrote: You are receiving this mail as it affects FreeBSD ports that you maintain. Clearly you have a list that identifies these ports. Would it be possible to share it so we can easily find which if our ports are still affected? Thanks! The list is available here: http://people.freebsd.org/~bapt/notstaged.txt ___ 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: Unable to update to clamav 0.98.3
On Thursday, May 08, 2014 04:35:11 PM Jerry wrote: FreeBSD 10.0-RELEASE I am unable to update to clamav-0.98.3. It terminates with the following error message: clamd.c:335:59: warning: format specifies type 'unsigned int' but the argument has type 'off_t' (aka 'long') [-Wformat] logg(#Log file size limited to %u bytes.\n, logg_size); ~~^ %ld 1 warning generated. CC tcpserver.o CC localserver.o CC session.o CC thrmgr.o CC server-th.o CC scanner.o scanner.c:105:25: warning: passing 'const unsigned char *' to parameter of type 'const char *' converts between pointers to integer types with different sign [-Wpointer-sign] strncpy(c-virhash, md5, 32); ^~~ /usr/include/string.h:101:57: note: passing argument to parameter here char*strncpy(char * __restrict, const char * __restrict, size_t); ^ 1 warning generated. CC others.o CC fan.o CCLD clamd gmake[3]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamd' Making all in clamdscan gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' CC output.o CC optparser.o CC misc.o CC getopt.o CC actions.o CC clamdcom.o ../shared/clamdcom.c:42:13: warning: implicit declaration of function 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent = send(sockd, line, len, 0); ^ ../shared/clamdcom.c:75:13: warning: implicit declaration of function 'recv' is invalid in C99 [-Wimplicit-function-declaration] s-r = recv(s-sockd, s-cur, sizeof(s-buf) - (s-cur - s-buf), 0); ^ 2 warnings generated. CC clamdscan.o CC proto.o CC client.o CCLD clamdscan gmake[3]: Leaving directory `/usr/ports/security/clamav/work/clamav-0.98.3/clamdscan' Making all in freshclam gmake[3]: Entering directory `/usr/ports/security/clamav/work/clamav-0.98.3/freshclam' CC output.o CC optparser.o CC getopt.o CC misc.o CC cdiff.o CC tar.o CC clamdcom.o ../shared/clamdcom.c:42:13: warning: implicit declaration of function 'send' is invalid in C99 [-Wimplicit-function-declaration] int sent = send(sockd, line, len, 0); ^ ../shared/clamdcom.c:75:13: warning: implicit declaration of function 'recv' is invalid in C99 [-Wimplicit-function-declaration] s-r = recv(s-sockd, s-cur, sizeof(s-buf) - (s-cur - s-buf), 0); ^ 2 warnings generated. CC freshclam.o In file included from freshclam.c:57: In file included from ../libclamav/others.h:21: In file included from ../libclamav/matcher.h:28: ../libclamav/others.h:154:5: error: unknown type name 'stats_section_t' stats_section_t *sections; ^ ../libclamav/others.h:323:5: error: unknown type name 'clcb_stats_add_sample' clcb_stats_add_sample cb_stats_add_sample; ^ ../libclamav/others.h:324:5: error: unknown type name 'clcb_stats_remove_sample' clcb_stats_remove_sample cb_stats_remove_sample; ^ ../libclamav/others.h:325:5: error: unknown type name 'clcb_stats_decrement_count' clcb_stats_decrement_count cb_stats_decrement_count; ^ ../libclamav/others.h:326:5: error: unknown type name 'clcb_stats_submit' clcb_stats_submit cb_stats_submit; ^ ../libclamav/others.h:327:5: error: unknown type name 'clcb_stats_flush' clcb_stats_flush cb_stats_flush; ^ ../libclamav/others.h:328:5: error: unknown type name 'clcb_stats_get_num' clcb_stats_get_num cb_stats_get_num; ^ ../libclamav/others.h:329:5: error: unknown type name 'clcb_stats_get_size' clcb_stats_get_size cb_stats_get_size; ^ ../libclamav/others.h:330:5: error: unknown type name 'clcb_stats_get_hostid' clcb_stats_get_hostid cb_stats_get_hostid; ^ ../libclamav/others.h:380:5: error: unknown type name 'clcb_stats_add_sample' clcb_stats_add_sample cb_stats_add_sample; ^ ../libclamav/others.h:381:5: error: unknown type name 'clcb_stats_remove_sample' clcb_stats_remove_sample cb_stats_remove_sample; ^ ../libclamav/others.h:382:5: error: unknown type name 'clcb_stats_decrement_count' clcb_stats_decrement_count cb_stats_decrement_count; ^ ../libclamav/others.h:383:5: error: unknown type name 'clcb_stats_submit' clcb_stats_submit cb_stats_submit; ^ ../libclamav/others.h:384:5: error: unknown type name 'clcb_stats_flush' clcb_stats_flush cb_stats_flush; ^ ../libclamav/others.h:385:5: error: unknown type name 'clcb_stats_get_num' clcb_stats_get_num cb_stats_get_num; ^ ../libclamav/others.h:386:5: error: unknown type name 'clcb_stats_get_size' clcb_stats_get_size cb_stats_get_size; ^ ../libclamav/others.h:387:5: error: unknown type name 'clcb_stats_get_hostid' clcb_stats_get_hostid cb_stats_get_hostid; ^ freshclam.c:762:5: warning: implicit declaration of
[QAT] 353800: 4x leftovers, 12x depend (ignored: please enable with_new_xorg, libglesv2 needs libdrm higher then 2.4.24 in graphics/libglesv2), 1x fetch, 179x success
Convert my ports to USES=tar - Build ID: 20140512105400-20788 Job owner: m...@freebsd.org Buildtime: 5 hours Enddate: Mon, 12 May 2014 16:15:00 GMT Revision: 353800 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=353800 - Port:databases/kbibtex 0.4.1_5 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330694/kbibtex-0.4.1_5.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330695/kbibtex-0.4.1_5.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330696/kbibtex-0.4.1_5.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330697/kbibtex-0.4.1_5.log - Port:deskutils/plasma-applet-qstardict 1.0.1_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330698/plasma-applet-qstardict-1.0.1_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330699/plasma-applet-qstardict-1.0.1_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330700/plasma-applet-qstardict-1.0.1_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330701/plasma-applet-qstardict-1.0.1_1.log - Port:editors/kile-kde4 2.1.3_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330702/kile-2.1.3_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330703/kile-2.1.3_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330704/kile-2.1.3_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330705/kile-2.1.3_2.log - Port:editors/texmaker 4.1.1,2 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330706/texmaker-4.1.1,2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330707/texmaker-4.1.1,2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330708/texmaker-4.1.1,2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330709/texmaker-4.1.1,2.log - Port:emulators/aqemu 0.8.2 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330710/aqemu-0.8.2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330711/aqemu-0.8.2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330712/aqemu-0.8.2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330713/aqemu-0.8.2.log - Port:emulators/dboxfe 0.1.3_5 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330714/dboxfe-0.1.3_5.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~m...@freebsd.org/20140512105400-20788-330715/dboxfe-0.1.3_5.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log:
[QAT] 353830: 4x leftovers
- Update to 1.226 PR: ports/189571 Submitted by: Bartek Rutkowski po...@robakdesign.com - Build ID: 20140512145800-21212 Job owner: swi...@freebsd.org Buildtime: 2 hours Enddate: Mon, 12 May 2014 17:11:24 GMT Revision: 353830 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=353830 - Port:x11-toolkits/p5-Pango 1.226 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~swi...@freebsd.org/20140512145800-21212-331002/p5-Pango-1.226.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~swi...@freebsd.org/20140512145800-21212-331003/p5-Pango-1.226.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~swi...@freebsd.org/20140512145800-21212-331004/p5-Pango-1.226.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~swi...@freebsd.org/20140512145800-21212-331005/p5-Pango-1.226.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140512145800-21212 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: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
On Sat, 10 May 2014 10:33:52 -0500 Bryan Drewery bdrew...@freebsd.org wrote: You are receiving this mail as it affects FreeBSD ports that you maintain. [...] If you already have PR needing to be committed please let us know and we will try to get on them ASAP. I've added ports/189682 to add staging support to print/cups-pdf (which have no maintainer ATM): http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/189682 -- Matthieu Volat ma...@alkumuna.eu signature.asc Description: PGP signature
make check-plist ok, but portlint complains: %%PORTDOCS%%@dirrm %%DOCSDIR%% missing
I'm updating devel/robodoc to staging. As suggested on the wiki page, env DEVELOPER=yes make stage make check-plist make package runs fine, no issues. However, portlint -A reports: # portlint -A WARN: /usr/ports/devel/robodoc/pkg-plist: Both ``%%PORTDOCS%%@dirrm %%DOCSDIR%%'' and ``%%PORTDOCS%%@unexec %D/%%DOCSDIR%% 2/dev/null || true'' are missing. At least one should be used. I have in pkg-plist: bin/robodoc bin/robohdrs man/man1/robodoc.1.gz man/man1/robohdrs.1.gz %%DOCSDIR%%/AUTHORS %%DOCSDIR%%/ChangeLog %%DOCSDIR%%/NEWS %%DOCSDIR%%/README %%DOCSDIR%%/manual.css %%DOCSDIR%%/manual.html %%DOCSDIR%%/robodoc_example.rc %%EXAMPLESDIR%%/PerlExample/Source/Box.pm %%EXAMPLESDIR%%/PerlExample/Source/Box/RectangularBox.pm %%EXAMPLESDIR%%/PerlExample/Source/Box/SquareBox.pm %%EXAMPLESDIR%%/PerlExample/Source/Cargo.txt %%EXAMPLESDIR%%/PerlExample/Source/Loader.txt %%EXAMPLESDIR%%/PerlExample/Source/SmartLoader.pm %%EXAMPLESDIR%%/PerlExample/Source/TruckPacker.pl %%EXAMPLESDIR%%/PerlExample/robodoc.rc @dirrmtry %%DOCSDIR%% @dirrmtry %%EXAMPLESDIR%%/PerlExample/Source/Box @dirrmtry %%EXAMPLESDIR%%/PerlExample/Source @dirrmtry %%EXAMPLESDIR%%/PerlExample @dirrmtry %%EXAMPLESDIR%% What's the problem? As recommended on the wiki page I made the docs and examples non-optional, because they are very small. Anton ___ 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: make check-plist ok, but portlint complains: %%PORTDOCS%%@dirrm %%DOCSDIR%% missing
On 12/05/2014 18:36, Anton Shterenlikht wrote: I'm updating devel/robodoc to staging. As suggested on the wiki page, env DEVELOPER=yes make stage make check-plist make package runs fine, no issues. However, portlint -A reports: # portlint -A WARN: /usr/ports/devel/robodoc/pkg-plist: Both ``%%PORTDOCS%%@dirrm %%DOCSDIR%%'' and ``%%PORTDOCS%%@unexec %D/%%DOCSDIR%% 2/dev/null || true'' are missing. At least one should be used. I have in pkg-plist: bin/robodoc bin/robohdrs man/man1/robodoc.1.gz man/man1/robohdrs.1.gz %%DOCSDIR%%/AUTHORS %%DOCSDIR%%/ChangeLog %%DOCSDIR%%/NEWS %%DOCSDIR%%/README %%DOCSDIR%%/manual.css %%DOCSDIR%%/manual.html %%DOCSDIR%%/robodoc_example.rc %%EXAMPLESDIR%%/PerlExample/Source/Box.pm %%EXAMPLESDIR%%/PerlExample/Source/Box/RectangularBox.pm %%EXAMPLESDIR%%/PerlExample/Source/Box/SquareBox.pm %%EXAMPLESDIR%%/PerlExample/Source/Cargo.txt %%EXAMPLESDIR%%/PerlExample/Source/Loader.txt %%EXAMPLESDIR%%/PerlExample/Source/SmartLoader.pm %%EXAMPLESDIR%%/PerlExample/Source/TruckPacker.pl %%EXAMPLESDIR%%/PerlExample/robodoc.rc @dirrmtry %%DOCSDIR%% @dirrmtry %%EXAMPLESDIR%%/PerlExample/Source/Box @dirrmtry %%EXAMPLESDIR%%/PerlExample/Source @dirrmtry %%EXAMPLESDIR%%/PerlExample @dirrmtry %%EXAMPLESDIR%% What's the problem? As recommended on the wiki page I made the docs and examples non-optional, because they are very small. portlint results are guidelines: if there's a good reason to do things in a way that portlint complains about, then go right ahead. However, you may have to justify your choices and persuade a committer to commit as is. Given you're installing some docs and examples, I'd add support for making them optional, even if they are pretty neglible in size. It's probably better for your port to behave in-line with other ports even if not doing that is a reasonable choice. Enabling DOCS and EXAMPLES in your port is pretty simple. You need to add %%PORTDOCS%% and %%PORTEXAMPLES%% to the appropriate lines in pkg-plist and add OPTIONS_DEFINE+= DOCS EXAMPLES to the Makefile if you want them to show up in an options dialogue. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
On Mon, 12 May 2014, John Marino wrote: I commit PR patches that are 6 to 18 months old fairly frequently. There is obviously a huge backlog but many PRs are processed daily. The PRs that aren't getting processed quickly are [NEW PORT] PRs (and apparently anything mentioning fuse-fs for some reason). A staging PR is going to jump the line; it has a higher priority. Why would you even entertain the idea that a staging PR will fall between the cracks? Perhaps the better question is: what are the factors that will make committers shy away from a PR, even if it's summary contains stage? [1] Maybe we (maintainers) can do better? [1] http://www.freebsd.org/cgi/query-pr-summary.cgi?category=portsseverity=priority=class=maintainer-updatestate=opensort=nonetext=responsible=multitext=stageoriginator=release= -- Melvyn ___ 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: print/cups-base - Avahi backend
The cups-base port has been marked as BROKEN if built against Avahi since version 1.4. (The Makefile even helpfully points the user to http://www.avahi.org/ticket/303 which states that the problem exists with CUPS version 1.4 and that a fix is in the making.) Since version 1.6, however, there exists native Avahi support in CUPS and there is really no point in marking the port broken and including all kinds of compatibility headers that are no longer of any use whatsoever. Building CUPS 1.7 directly against Avahi works well and without any need for the avahi-compat-libdns_sd headers. I tested the setup on my system and came up with the following patch that incidentally also checks whether one or the other mDNS backend was selected and activates the pkg-plist magic accordingly. (Note how the dependency on avahi-libdns has been replaced with a dependency on avahi-app, as the configure script checks for the presence of libavahi-client.so, installed by net/avahi-app.) Raivo patch-cups_172_avahi Description: Binary data ___ 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: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
On 5/12/2014 20:49, Melvyn Sopacua wrote: On Mon, 12 May 2014, John Marino wrote: I commit PR patches that are 6 to 18 months old fairly frequently. There is obviously a huge backlog but many PRs are processed daily. The PRs that aren't getting processed quickly are [NEW PORT] PRs (and apparently anything mentioning fuse-fs for some reason). A staging PR is going to jump the line; it has a higher priority. Why would you even entertain the idea that a staging PR will fall between the cracks? Perhaps the better question is: what are the factors that will make committers shy away from a PR, even if it's summary contains stage? [1] Maybe we (maintainers) can do better? [1] Heh, 54 out of 2000+ PRs isn't too bad. :) I doubt most cases are people intentionally passing over an ugly PR. I am sure it happens but staging is generally straightforward so the PR itself isn't going to scare someone off. John ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
Hi! Perhaps the better question is: what are the factors that will make committers shy away from a PR, even if it's summary contains stage? [1] Mostly lack of time. Maybe we (maintainers) can do better? By becoming committers yourself 8-) and sharing the burden 8-) -- 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: Kalzium build fails (part of KDE4 port upgrade)
On Sunday 11 May 2014 22:56:52 Raphael Kubo da Costa wrote: Does it help if you rebuild math/facile? Yes, it does, 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
math/sage build error
Trying build sage I get the following error on amd and freebsd-9.2: [reference] updating environment: 2 added, 0 changed, 0 removed [reference] reading sources... [ 50%] index [reference] reading sources... [100%] todolist [reference] Merging environment/index files... [reference] algebras: 2 todos, 16 index, 5 citations, 416 modules [reference] arithgroup: 0 todos, 12 index, 9 citations, 295 modules [reference] calculus: 2 todos, 23 index, 2 citations, 438 modules [reference] categories: 13 todos, 130 index, 6 citations, 567 modules [reference] cmd: 0 todos, 6 index, 0 citations, 277 modules [reference] coding: 0 todos, 10 index, 6 citations, 576 modules [reference] coercion: 0 todos, 4 index, 0 citations, 579 modules ./sage: line 134: 75966 Killed: 9 $SAGE_ROOT/src/bin/sage $@ gmake: *** [doc-html] Error 137 *** [do-build] Error code 1 Stop in /usr/ports/math/sage. *** [install] Error code 1 Stop in /usr/ports/math/sage. ___ 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: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
Hi, On Mon, 12 May 2014, John Marino wrote: On 5/12/2014 20:49, Melvyn Sopacua wrote: On Mon, 12 May 2014, John Marino wrote: I commit PR patches that are 6 to 18 months old fairly frequently. There is obviously a huge backlog but many PRs are processed daily. The PRs that aren't getting processed quickly are [NEW PORT] PRs (and apparently anything mentioning fuse-fs for some reason). A staging PR is going to jump the line; it has a higher priority. Why would you even entertain the idea that a staging PR will fall between the cracks? Perhaps the better question is: what are the factors that will make committers shy away from a PR, even if it's summary contains stage? [1] Maybe we (maintainers) can do better? [1] Heh, 54 out of 2000+ PRs isn't too bad. :) Ok..2000 ports PR's open at given time on how many committers? Starting to look like Kurt has the right idea here. I doubt most cases are people intentionally passing over an ugly PR. I am sure it happens but staging is generally straightforward so the PR itself isn't going to scare someone off. Well, mine (ports/188901) I can see why someone walks around it, cause the patch is 1MB and needs to be downloaded. The bulk is of course the giant plist introduced by staging (and we can blame Zend for a file-intensive boilerplate heavy framework, but that's another topic). However, I don't see a way to make it more attractive, which is why I asked. -- Melvyn ___ 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
Patch wanted: VmRSS, VmSize and VmStk in /proc/pid/status
Hello,
In the new versions of french/aster, there is this piece of Linux code:
---
static char filename[80];
static char sbuf[1024];
char* S;
int fd, num_read;
long lmem;
pid_t numpro;
pid_t getpid(void);
numpro = getpid();
sprintf(filename, /proc/%ld/status, (long)numpro);
fd = open(filename, O_RDONLY, 0);
if (fd==-1) return -1;
num_read=read(fd,sbuf,(sizeof sbuf)-1);
close(fd);
S=strstr(sbuf,VmData:)+8;
val[0] = (INTEGER)atoi(S);
S=strstr(sbuf,VmSize:)+8;
val[1] = (INTEGER)atoi(S);
if ( strstr(sbuf,VmPeak:) != NULL ) {
S=strstr(sbuf,VmPeak:)+8;
val[2] = atoi(S);
} else {
val[2] = -1 ;
}
S=strstr(sbuf,VmRSS:)+7;
val[3] = (INTEGER)atoi(S);
S=strstr(sbuf,VmStk:)+7;
lmem = atoi(S);
return lmem ;
---
Of course, it does'nt work on FreeBSD, because our status has a
different structure.
As a quick dirty work-around, I patched it to replace /proc by
/compat/linux/proc and it works. Unfortunately, this is not a good
solution, because this port is no more packageable (this piece of code
is run at the end of the build).
It's why I'm looking for help here: does somebody knows how the
corresponding values of these Vm... can be found in FreeBSD?
Thanks,
--
Th. Thomas.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
[QAT] 353903: 4x leftovers
- Fix build with libstatgrab 0.90 PR: ports/189740 Approved by:portmgr (antoine), maintainer - Build ID: 20140512220800-37809 Job owner: t...@freebsd.org Buildtime: 11 minutes Enddate: Mon, 12 May 2014 22:19:20 GMT Revision: 353903 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=353903 - Port:net-mgmt/collectd 4.10.9_6 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140512220800-37809-331302/collectd-4.10.9_6.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140512220800-37809-331303/collectd-4.10.9_6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140512220800-37809-331304/collectd-4.10.9_6.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~t...@freebsd.org/20140512220800-37809-331305/collectd-4.10.9_6.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140512220800-37809 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: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
On Sat, May 10, 2014 11:33 am, Bryan Drewery wrote: You are receiving this mail as it affects FreeBSD ports that you maintain. This decision was not easy, but if a port is not being staged after almost a year, we wonder if the ports are actually maintained and updated for releases and security issues. In my case, I missed the call to convert *all ports* to staging, as my pants have been bankrupt for about a year (working on restarting the upstream of the port I'm maintainer for). This may have been exacerbated by an interaction of greylisting and duplicate elimination that I just realized occurs - messages get past greylisting faster through the list than direct, so for messages that are sent both to the list and directly to me the copy that gets put in the list folder gets kept instead of the one that would go into my inbox. I will have a very hard time finishing converting to staging in three months - A. I have a day job. B. This port's current configuration (inherited from the previous maintainer) is sufficiently kludgy that I will probably have to rewrite it from scratch. (I've been trying over the weekend to hack it into shape but am realizing that I have to give up and rewrite the whole mess.) Jim Trigg Maintainer, mail/ecartis ___ 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] 353914: 4x leftovers
Fix build on current [1] PR: ports/188793 [1], ports/187919 [2] Submitted by: zeising [1], Thomas Schweikle t...@vr-web.de [2] Approved by:maintainer timeout - Build ID: 20140513050200-41397 Job owner: zeis...@freebsd.org Buildtime: 4 minutes Enddate: Tue, 13 May 2014 05:06:26 GMT Revision: 353914 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=353914 - Port:databases/rrdtool 1.4.8_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~zeis...@freebsd.org/20140513050200-41397-331346/rrdtool-1.4.8_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~zeis...@freebsd.org/20140513050200-41397-331347/rrdtool-1.4.8_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~zeis...@freebsd.org/20140513050200-41397-331348/rrdtool-1.4.8_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~zeis...@freebsd.org/20140513050200-41397-331349/rrdtool-1.4.8_1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140513050200-41397 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: [QAT] 353914: 4x leftovers
On May 13, 2014 7:06:28 AM CEST, Ports-QAT q...@redports.org wrote: Fix build on current [1] PR:ports/188793 [1], ports/187919 [2] Submitted by: zeising [1], Thomas Schweikle t...@vr-web.de [2] Approved by: maintainer timeout - Build ID: 20140513050200-41397 Job owner: zeis...@freebsd.org Buildtime: 4 minutes Enddate: Tue, 13 May 2014 05:06:26 GMT Revision: 353914 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=353914 - Port:databases/rrdtool 1.4.8_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~zeis...@freebsd.org/20140513050200-41397-331346/rrdtool-1.4.8_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~zeis...@freebsd.org/20140513050200-41397-331347/rrdtool-1.4.8_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~zeis...@freebsd.org/20140513050200-41397-331348/rrdtool-1.4.8_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~zeis...@freebsd.org/20140513050200-41397-331349/rrdtool-1.4.8_1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140513050200-41397 redports https://qat.redports.org/ Those are not related to rrdtool. -- Niclas Sent from my mobile device. Excuse my brevity. ___ 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
