Re: Squid aufs crashes under 10.0

2014-05-13 Thread Pavel Timofeev
Hi! Any plans to import squid34 to ports tree?

2014-02-11 9:40 GMT+04:00 Dennis Glatting free...@pki2.com:
 On Mon, 2014-02-10 at 20:11 +0100, Florian Smeets wrote:
 On 10/02/14 16:21, Dennis Glatting wrote:
  On Mon, 2014-02-10 at 11:15 +0400, Pavel Timofeev wrote:
  So what should I do?
  Write a PR to squid's bugzilla with link to this thread?
  Fill FreeBSD ports' PR? (it seems like maintainer of squid doesn't
  look at PRs about squid).
  And it seems like this problem is retaled to all of squid ports, not
  only to www/squid33.
 
 
  Good question. I don't know. I ported 3.4 and sent email to the
  maintainer and to the list. Zip in response.
 

 I plan to take care of it this week. (squid34 + aufs patches)


 My stuff here:

 fetch http://www.pki2.com/squid34.tar


 Florian



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: FreeBSD Port: print/cups-base - Avahi backend

2014-05-13 Thread Scot Hetzel
On Mon, May 12, 2014 at 1:51 PM, Raivo Hool raivo.h...@gmail.com wrote:
 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.)


You might want to change these lines from:

PLIST_SUB+= WITH_MDNSRESPONDER= WITH_AVAHI=@comment 

to

PLIST_SUB+=  DNSSD= MDNSRESPONDER=

Then in pkg-plist use:

%%DNSSD%%libexec/cups/backend/dnssd
%%MDNSRESPONDER%%libexec/cups/backend/dnssd

This way you don't list 'libexec/cups/backend/dnssd' twice in the pkg-plist.

Send the patch as a PR and someone should eventually get to it.

-- 
DISCLAIMER:

No electrons were maimed while sending this message. Only slightly bruised.
___
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: Patch wanted: VmRSS, VmSize and VmStk in /proc/pid/status

2014-05-13 Thread Scot Hetzel
On Mon, May 12, 2014 at 4:35 PM, Thierry Thomas thie...@freebsd.org wrote:
 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?


You could try reading the source for linprocfs to see how it gets those values:

https://svnweb.freebsd.org/base/head/sys/compat/linprocfs/linprocfs.c?revision=263620view=markup#l748


-- 
DISCLAIMER:

No electrons were maimed while sending this message. Only slightly bruised.
___
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


ports/INDEX building broken on 11.0-CURRENT

2014-05-13 Thread Don Lewis
Please excuse the crosspost.  I'm not sure if this is a ports problem or
a CURRENT problem.

I just updated my 11.0-CURRENT machine to r265940 and can no longer
build ports/INDEX-11.  My ports tree is r353903.  I think this problem
is being caused by the recent changes to /usr/share/mk/*.

# make index
Generating INDEX-11 - please wait..--- describe.accessibility ---
--- describe.arabic ---
--- describe.archivers ---
--- describe.astro ---
--- describe.audio ---
--- describe.benchmarks ---
--- describe.biology ---
--- describe.cad ---
--- describe.chinese ---
--- describe.comms ---
--- describe.converters ---
--- describe.databases ---
--- describe.deskutils ---
--- describe.devel ---
clang33: not found
make[5]: /usr/share/mk/bsd.compiler.mk line 24: warning: clang33 --version 
returned non-zero status
make[5]: /usr/share/mk/bsd.compiler.mk line 37: Unable to determine compiler 
type for clang33.  Consider setting COMPILER_TYPE.
=== devel/ccons failed
*** [describe.devel] Error code 1

make[2]: stopped in /usr/ports
1 error

make[2]: stopped in /usr/ports


Before reporting this error, verify that you are running a supported
version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you
have a complete and up-to-date ports collection.  (INDEX builds are
not supported with partial or out-of-date ports collections.
If that is the case, then
report the failure to po...@freebsd.org together with relevant
details of your ports configuration (including FreeBSD version,
your architecture, your environment, and your /etc/make.conf
settings, especially compiler flags and OPTIONS_SET/UNSET settings).

Note: the latest pre-generated version of INDEX may be fetched
automatically with make fetchindex.


*** Error code 1

Stop.
make[1]: stopped in /usr/ports
*** Error code 1

Stop.
make: stopped in /usr/ports


If I go to the offending port:

# cd /usr/ports/devel/ccons/
# make describe
clang33: not found
make: /usr/share/mk/bsd.compiler.mk line 24: warning: clang33 --version 
returned non-zero status
make: /usr/share/mk/bsd.compiler.mk line 37: Unable to determine compiler 
type for clang33.  Consider setting COMPILER_TYPE.


I don't have any problems building the INDEX file on 9.3-PRERELEASE
r265940.


___
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

2014-05-13 Thread portscout
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
math/asir2000   | 20110810| 20140513
+-+


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: Unable to update to clamav 0.98.3

2014-05-13 Thread Jerry
On Mon, 12 May 2014 11:03:50 -0300, Renato Botelho stated:

 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 

[QAT] 353931: 105x success, 1x depend (??? in security/trousers), 4x leftovers, 3x depend (checksum in print/texinfo), 1x fetch, 2x depend (ignored: is only for i386, while you are running amd64 in mu

2014-05-13 Thread Ports-QAT
- Update multimedia/libdvdread to 4.9.9
- Bump dependent ports' PORTREVISIONS and update LIB_DEPENDS [1]
- multimedia/libdvdnav: remove dependency to (now removed) dvdread-config
- sysutils/vstrip: remove useless dependency to multimedia/libdvdread

Approved by:portmgr (implicit) [1]
-

  Build ID:  20140513101801-54418
  Job owner: marty...@freebsd.org
  Buildtime: 3 hours
  Enddate:   Tue, 13 May 2014 13:21:13 GMT

  Revision:  353931
  Repository:
https://svnweb.freebsd.org/ports?view=revisionrevision=353931

-

Port:multimedia/bombono 1.2.2_3

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331414/bombono-1.2.2_3.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331415/bombono-1.2.2_3.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331416/bombono-1.2.2_3.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331417/bombono-1.2.2_3.log

-

Port:multimedia/dvdauthor 0.7.1_4

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331418/dvdauthor-0.7.1_4.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331419/dvdauthor-0.7.1_4.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331420/dvdauthor-0.7.1_4.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331421/dvdauthor-0.7.1_4.log

-

Port:multimedia/gmerlin-avdecoder 1.2.0_6

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331422/gmerlin-avdecoder-1.2.0_6.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331423/gmerlin-avdecoder-1.2.0_6.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331424/gmerlin-avdecoder-1.2.0_6.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331425/gmerlin-avdecoder-1.2.0_6.log

-

Port:multimedia/gstreamer-plugins-dvd 0.10.19_3,3

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331426/gstreamer-plugins-dvd-0.10.19_3,3.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331427/gstreamer-plugins-dvd-0.10.19_3,3.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331428/gstreamer-plugins-dvd-0.10.19_3,3.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331429/gstreamer-plugins-dvd-0.10.19_3,3.log

-

Port:multimedia/gstreamer-plugins-resindvd 0.10.23_3,3

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331430/gstreamer-plugins-resindvd-0.10.23_3,3.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331431/gstreamer-plugins-resindvd-0.10.23_3,3.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331432/gstreamer-plugins-resindvd-0.10.23_3,3.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~marty...@freebsd.org/20140513101801-54418-331433/gstreamer-plugins-resindvd-0.10.23_3,3.log


iconv and ports

2014-05-13 Thread John
Hello ports,

When portupgrade runs its daily run, I get this:

** Port marked as IGNORE: mail/exim-sa-exim:
You have iconv support in base system, but
/usr/local/include/iconv.h is +present too.  It will hiccup the build.

What is the proper way to fix this?

Thanks!
-- 
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: iconv and ports

2014-05-13 Thread Tijl Coosemans
On Tue, 13 May 2014 15:03:14 +0100 John wrote:
 Hello ports,
 
 When portupgrade runs its daily run, I get this:
 
 ** Port marked as IGNORE: mail/exim-sa-exim:
 You have iconv support in base system, but
 /usr/local/include/iconv.h is +present too.  It will hiccup the build.
 
 What is the proper way to fix this?
 
 Thanks!

I submitted a patch for exim several months ago:
http://www.freebsd.org/cgi/query-pr.cgi?pr=186290#reply2
___
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


firefox does not build on 10-STABLE

2014-05-13 Thread John
Hello ports!

I cannot get firefox to build on my system. Can anyone please help? 

ports version:

Path: /usr/ports
Working Copy Root Path: /usr/ports
URL: https://svn0.eu.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn0.eu.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 353949
Node Kind: directory
Schedule: normal
Last Changed Author: jadawin
Last Changed Rev: 353949
Last Changed Date: 2014-05-13 14:12:50 +0100 (Tue, 13 May 2014)

freebsd version: FreeBSD 10.0-STABLE #0 r265914: Mon May 12 16:53:49 BST 2014

/etc/make.conf is empty. The build fails like this:

#  define MOZ_ALWAYS_INLINE_EVEN_DEBUG __attribute__((always_inline)) inline
  ^
In file included from 
/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0/content/svg/content/src/Unified_cpp_content_svg_content_src8.cpp:2:
In file included from 
/usr/ports/www/firefox/work/mozilla-release/content/svg/content/src/nsSVGElement.cpp:9:
In file included from 
/usr/ports/www/firefox/work/mozilla-release/content/svg/content/src/nsSVGElement.h:15:
In file included from ../../../../dist/include/mozilla/css/StyleRule.h:16:
In file included from ../../../../dist/include/mozilla/css/Rule.h:12:
In file included from 
/usr/ports/www/firefox/work/mozilla-release/layout/style/nsIStyleRule.h:16:
In file included from ../../../../dist/include/nsISupports.h:10:
In file included from ../../../../dist/include/nsrootidl.h:13:
In file included from ../../../../dist/include/nscore.h:19:
../../../../dist/include/mozilla/mozalloc.h:234:21: warning: replacement 
function 'operator delete[]'
  cannot be declared 'inline' [-Winline-new-delete]
MOZALLOC_EXPORT_NEW MOZALLOC_INLINE
^
../../../../dist/include/mozilla/mozalloc.h:44:27: note: expanded from macro 
'MOZALLOC_INLINE'
#  define MOZALLOC_INLINE MOZ_ALWAYS_INLINE_EVEN_DEBUG
  ^
../../../../dist/include/mozilla/Attributes.h:27:75: note: expanded from macro
  'MOZ_ALWAYS_INLINE_EVEN_DEBUG'
#  define MOZ_ALWAYS_INLINE_EVEN_DEBUG __attribute__((always_inline)) inline
  ^
In file included from 
/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0/content/svg/content/src/Unified_cpp_content_svg_content_src8.cpp:2:
In file included from 
/usr/ports/www/firefox/work/mozilla-release/content/svg/content/src/nsSVGElement.cpp:9:
In file included from 
/usr/ports/www/firefox/work/mozilla-release/content/svg/content/src/nsSVGElement.h:15:
In file included from ../../../../dist/include/mozilla/css/StyleRule.h:16:
In file included from ../../../../dist/include/mozilla/css/Rule.h:12:
In file included from 
/usr/ports/www/firefox/work/mozilla-release/layout/style/nsIStyleRule.h:16:
In file included from ../../../../dist/include/nsISupports.h:10:
In file included from ../../../../dist/include/nsrootidl.h:13:
In file included from ../../../../dist/include/nscore.h:19:
../../../../dist/include/mozilla/mozalloc.h:240:21: warning: replacement 
function 'operator delete[]'
  cannot be declared 'inline' [-Winline-new-delete]
MOZALLOC_EXPORT_NEW MOZALLOC_INLINE
^
../../../../dist/include/mozilla/mozalloc.h:44:27: note: expanded from macro 
'MOZALLOC_INLINE'
#  define MOZALLOC_INLINE MOZ_ALWAYS_INLINE_EVEN_DEBUG
  ^
../../../../dist/include/mozilla/Attributes.h:27:75: note: expanded from macro
  'MOZ_ALWAYS_INLINE_EVEN_DEBUG'
#  define MOZ_ALWAYS_INLINE_EVEN_DEBUG __attribute__((always_inline)) inline
  ^
8 warnings generated.
8 warnings generated.
gmake[5]: Leaving directory 
`/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0/content/svg/content/src'
gmake[4]: Leaving directory 
`/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0'
gmake[3]: *** [compile] Error 2
gmake[3]: Leaving directory 
`/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0'
gmake[2]: *** [default] Error 2
gmake[2]: Leaving directory 
`/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0'
=== Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/www/firefox
*** Error code 1

Stop.
make: stopped in /usr/ports/www/firefox

thanks!

-- 
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


svn errors updating ports tree

2014-05-13 Thread Anton Shterenlikht
In the last few days I'm having these svn error:

svn: E185002: Svndiff has backwards-sliding source views

or

svn: E185005: Decompression of svndiff data failed: no size

when updating the ports src tree on ia64 -current.

I then run svn cleanup, but the following svn up
again shows one of the above errors.

What's going on?

I use subversion-1.8.8_2 and
https://svn0.eu.freebsd.org/ports/head

Please advise

Thanks

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: svn errors updating ports tree

2014-05-13 Thread Jim Riggs
On 13 May 2014, at 09:59, Anton Shterenlikht me...@bris.ac.uk wrote:

 In the last few days I'm having these svn error:
 
 svn: E185002: Svndiff has backwards-sliding source views
 
 or
 
 svn: E185005: Decompression of svndiff data failed: no size
 
 when updating the ports src tree on ia64 -current.
 
 I then run svn cleanup, but the following svn up
 again shows one of the above errors.

I have been seeing the same thing on amd64 both 8.x and 10.

___
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


drop maintainership of databases/pg_reorg, databases/postgresql-repmgr

2014-05-13 Thread Alexander Pyhalov

Hello.
We don't use FreeBSD on our database server longer. Besides, I became 
tightly involved in OpenIndiana development and just don't have time 
enough to support FreeBSD ports I've created, so I'd like to drop 
manitainership for databases/pg_reorg, databases/postgresql-repmgr.
I think it would be honest, because I just can't support them on 
adequate level.

--
Best regards,
Alexander Pyhalov,
system administrator of Computer Center of Southern Federal University
___
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

2014-05-13 Thread Anton Shterenlikht
On 12/05/2014 18:36, Anton Shterenlikht wrote:
 I'm updating devel/robodoc to staging.
 As suggested on the wiki page,
 env DEVELOPER=3Dyes make stage  make check-plist  make package
 runs fine, no issues.
 However, portlint -A reports:
=20
 # portlint -A
 WARN: /usr/ports/devel/robodoc/pkg-plist: Both ``%%PORTDOCS%%@dirrm %%D=
OCSDIR%%'' and ``%%PORTDOCS%%@unexec %D/%%DOCSDIR%% 2/dev/null || true''=
 are missing.  At least one should be used.
=20
 I have in pkg-plist:
=20
 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%%
=20
 What's the problem?
=20
 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+=3D DOCS EXAMPLES

to the Makefile if you want them to show up in an options dialogue.

still the same:

# cat pkg-plist 
bin/robodoc
bin/robohdrs
man/man1/robodoc.1.gz
man/man1/robohdrs.1.gz
%%PORTDOCSDOCSDIR%%/AUTHORS
%%PORTDOCSDOCSDIR%%/ChangeLog
%%PORTDOCSDOCSDIR%%/NEWS
%%PORTDOCSDOCSDIR%%/README
%%PORTDOCSDOCSDIR%%/manual.css
%%PORTDOCSDOCSDIR%%/manual.html
%%PORTDOCSDOCSDIR%%/robodoc_example.rc
%%PORTEXAMPLESEXAMPLESDIR%%/PerlExample/Source/Box.pm
%%PORTEXAMPLESEXAMPLESDIR%%/PerlExample/Source/Box/RectangularBox.pm
%%PORTEXAMPLESEXAMPLESDIR%%/PerlExample/Source/Box/SquareBox.pm
%%PORTEXAMPLESEXAMPLESDIR%%/PerlExample/Source/Cargo.txt
%%PORTEXAMPLESEXAMPLESDIR%%/PerlExample/Source/Loader.txt
%%PORTEXAMPLESEXAMPLESDIR%%/PerlExample/Source/SmartLoader.pm
%%PORTEXAMPLESEXAMPLESDIR%%/PerlExample/Source/TruckPacker.pl
%%PORTEXAMPLESEXAMPLESDIR%%/PerlExample/robodoc.rc
%%PORTDOCS%%@dirrmtry %%DOCSDIR%%
%%PORTEXAMPLES%%@dirrmtry %%EXAMPLESDIR%%/PerlExample/Source/Box
%%PORTEXAMPLES%%@dirrmtry %%EXAMPLESDIR%%/PerlExample/Source
%%PORTEXAMPLES%%@dirrmtry %%EXAMPLESDIR%%/PerlExample
%%PORTEXAMPLES%%@dirrmtry %%EXAMPLESDIR%%
# 

# 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 guess the issue is about dirrm vs dirrmtry ?

Thanks

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: svn errors updating ports tree

2014-05-13 Thread Anton Shterenlikht
From freebsd-li...@christianserving.org Tue May 13 17:12:33 2014

On 13 May 2014, at 09:59, Anton Shterenlikht me...@bris.ac.uk wrote:

 In the last few days I'm having these svn error:
 
 svn: E185002: Svndiff has backwards-sliding source views
 
 or
 
 svn: E185005: Decompression of svndiff data failed: no size
 
 when updating the ports src tree on ia64 -current.
 
 I then run svn cleanup, but the following svn up
 again shows one of the above errors.

I have been seeing the same thing on amd64 both 8.x and 10.

also from svn0.eu mirror?

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


Port update 189120 needs committed

2014-05-13 Thread qjail
 

 Will some committer please commit this port update.
 It's just a script.

 http://www.freebsd.org/cgi/query-pr.cgi?pr=189120


 Thanks in advance.
 Joe 

___
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: drop maintainership of databases/pg_reorg, databases/postgresql-repmgr

2014-05-13 Thread Antoine Brodin
On Tue, May 13, 2014 at 6:08 PM, Alexander Pyhalov a...@rsu.ru wrote:
 Hello.
 We don't use FreeBSD on our database server longer. Besides, I became
 tightly involved in OpenIndiana development and just don't have time enough
 to support FreeBSD ports I've created, so I'd like to drop manitainership
 for databases/pg_reorg, databases/postgresql-repmgr.
 I think it would be honest, because I just can't support them on adequate
 level.


Hi,

Thanks for letting us know,  I have reset maintainer.

Cheers,

Antoine
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Port update 181945 needs committed

2014-05-13 Thread jail-primer
 

 Will some committer please commit this port update.
 It's just a script.


 http://www.freebsd.org/cgi/query-pr.cgi?pr=181945


 Thanks in advance.
 Joe 

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: Port update 181945 needs committed

2014-05-13 Thread Kurt Jaeger
Hi!

  Will some committer please commit this port update.
  It's just a script.
 
 
  http://www.freebsd.org/cgi/query-pr.cgi?pr=181945

It's already committed since Feb.2014 ?

-- 
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


staging without root privileges

2014-05-13 Thread Anton Shterenlikht
https://wiki.freebsd.org/ports/StageDir
says 

Make sure you tested make package as a normal user (not root).

Does this refer specifically to the package target?
Or to all targets up to and including package?

I'm asked for root passwd on make config,
and then I get an error on build:

mkdir: /usr/ports/devel/robodoc/work: Permission denied

which makes sense.

So do I understand correctly that only package
target is intended to be built without the
root UID?

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


[x11-fonts/sgifonts] Dynamic plist and double pkg-message

2014-05-13 Thread A.J. 'Fonz' van Werven
L.S.,

While seeing if I can prevent ports I'm using from being taken out and
executed by a firing squad for not having been stagified yet (and yes, I'm
willing to take maintainership of orphaned ones) I stumbled across the
following two issues involving x11-fonts/sgifonts:

-1-
This port uses a dynamically-generated plist because it uses bdftopcf and
mkfontdir. Can somebody please check whether it's okay to keep the
dynamic plist generation or I should eliminate that and add a static
pkg-plist?

-2-
When testing whether it works with portmaster -g I noticed that
pkg-message is being displayed twice. Is this normal behaviour, or did I
do something wrong? Come to think of it, it appears to be happening with
lots of ports nowadays.

Thanks in advance,

AvW

-- 
I'm not completely useless, I can be used as a bad example.


pgpZ6Uetfz25i.pgp
Description: PGP signature


Trouble with textproc/rubygem-nokogiri

2014-05-13 Thread Joseph Benden
Is anyone else having trouble with textproc/rubygem-nokogiri ? I can't
get it to build inside Poudriere or properly install outside of it. [The
previous version only installed with NO_STAGE=yes added to the Makefile.]

Comments, suggestions, and ideas are welcomed!

-Joe




 Creating the reference jail... done
 Mounting system devices for 10x86-default
 Mounting ports/packages/distfiles
 Using packages from previously failed build
 Mounting packages from:
/usr/local/poudriere/data/packages/10x86-default
 Mounting /var/db/ports from: /usr/local/etc/poudriere.d/options
 Logs:
/usr/local/poudriere/data/logs/bulk/10x86-default/2014-05-13_10h29m42s
 Appending to make.conf: /usr/local/etc/poudriere.d/10x86-make.conf
/etc/resolv.conf -
/usr/local/poudriere/data/build/10x86-default/ref/etc/resolv.conf
 Starting jail 10x86-default
 Loading MOVED
 Calculating ports order and dependencies
 Sanity checking the repository
 Deleting stale symlinks
 Deleting empty directories
 Cleaning the build queue
 Recording filesystem state for prepkg... done
 Committing packages to repository
 Removing old packages
 Building with flags: PREFIX=/prefix/rubygem-nokogiri-1.6.2
build started at Tue May 13 10:31:22 MST 2014
port directory: /usr/ports/textproc/rubygem-nokogiri
building for: FreeBSD 10x86-default 10.0-RELEASE FreeBSD 10.0-RELEASE amd64
maintained by: r...@freebsd.org
ident warning: no id keywords in
/usr/local/poudriere/data/build/10x86-default/ref//usr/ports/textproc/rubygem-nokogiri/Makefile
Makefile ident:
Poudriere version: 3.1-pre
Host OSVERSION: 1100019
Jail OSVERSION: 1000510

---Begin Environment---
PREFIX=/prefix/rubygem-nokogiri-1.6.2
PKGREPOSITORY=/tmp/pkgs
PACKAGES=/tmp/pkgs
OSVERSION=1000510
UNAME_v=FreeBSD 10.0-RELEASE
UNAME_r=10.0-RELEASE
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
SAVED_TERM=xterm-256color
NO_WARNING_PKG_INSTALL_EOL=yes
MASTERMNT=/usr/local/poudriere/data/build/10x86-default/ref
PKG_EXT=txz
FORCE_PACKAGE=yes
tpid=64692
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
POUDRIERE_BUILD_TYPE=bulk
PKGNG=1
PKG_DELETE=/usr/local/sbin/pkg-static delete -y -f
PKG_ADD=/usr/local/sbin/pkg-static add
OLDPWD=/usr/local/poudriere/ports/default
PWD=/usr/local/poudriere/data/build/10x86-default/ref/poudriere/rdeps
MASTERNAME=10x86-default
DEVELOPER_MODE=yes
USER=root
HOME=/root
POUDRIERE_VERSION=3.1-pre
TRYBROKEN=yes
LOCALBASE=/usr/local
PACKAGE_BUILDING=yes
PKG_VERSION=/poudriere/pkg-static version
PKG_BIN=/usr/local/sbin/pkg-static
---End Environment---

---Begin OPTIONS List---
---End OPTIONS List---

--CONFIGURE_ARGS--
--use-system-libraries
--End CONFIGURE_ARGS--

--CONFIGURE_ENV--
TMPDIR=/tmp SHELL=/bin/sh CONFIG_SHELL=/bin/sh
--End CONFIGURE_ENV--

--MAKE_ENV--
TMPDIR=/tmp SHELL=/bin/sh NO_LINT=YES
PREFIX=/prefix/rubygem-nokogiri-1.6.2  LOCALBASE=/usr/local 
LIBDIR=/usr/lib  CC=cc CFLAGS=-O2 -pipe -march=native
-fno-strict-aliasing  CPP=cpp CPPFLAGS=  LDFLAGS=  CXX=c++
CXXFLAGS=-O2 -pipe -march=native -fno-strict-aliasing 
MANPREFIX=/prefix/rubygem-nokogiri-1.6.2 BSD_INSTALL_PROGRAM=install 
-s -o root -g wheel -m 555  BSD_INSTALL_LIB=install  -s -o root -g
wheel -m 444  BSD_INSTALL_SCRIPT=install  -o root -g wheel -m 555 
BSD_INSTALL_DATA=install  -o root -g wheel -m 444 
BSD_INSTALL_MAN=install  -o root -g wheel -m 444
--End MAKE_ENV--

--PLIST_SUB--
RUBY_LIBDIR=lib/ruby/2.1
RUBY_ARCHLIBDIR=lib/ruby/2.1/amd64-freebsd10
RUBY_SITELIBDIR=lib/ruby/site_ruby/2.1
RUBY_SITEARCHLIBDIR=lib/ruby/site_ruby/2.1/amd64-freebsd10
RUBY_VENDORLIBDIR=lib/ruby/vendor_ruby/2.1
RUBY_VENDORARCHLIBDIR=lib/ruby/vendor_ruby/2.1/amd64-freebsd10
RUBY_MODDOCDIR=share/doc/ruby21/nokogiri
RUBY_MODEXAMPLESDIR=share/examples/ruby21/nokogiri
RUBY_DOCDIR=share/doc/ruby21
RUBY_EXAMPLESDIR=share/examples/ruby21
RUBY_RIDIR=share/ri/2.1/system
RUBY_SITERIDIR=share/ri/2.1/site
RUBY_ELISPDIR=lib/ruby/elisp
RUBY_VERSION=2.1.1
RUBY_VER=2.1
RUBY_SHLIBVER=21
RUBY_ARCH=amd64-freebsd10
RUBY_SUFFIX=21
RUBY_NAME=ruby21
RUBY_DEFAULT_SUFFIX=19
RUBY19=@comment

RUBY20=@comment

RUBY21=
PORTVERSION=1.6.2
REV=
GEMS_BASE_DIR=lib/ruby/gems/2.1
GEMS_DIR=lib/ruby/gems/2.1/gems
DOC_DIR=lib/ruby/gems/2.1/doc
CACHE_DIR=lib/ruby/gems/2.1/cache
SPEC_DIR=lib/ruby/gems/2.1/specifications
PORT=nokogiri-1.6.2
GEM_NAME=nokogiri-1.6.2
GEM_LIB_DIR=lib/ruby/gems/2.1/gems/nokogiri-1.6.2
GEM_DOC_DIR=lib/ruby/gems/2.1/doc/nokogiri-1.6.2
GEM_SPEC=lib/ruby/gems/2.1/specifications/nokogiri-1.6.2.gemspec
GEM_CACHE=lib/ruby/gems/2.1/cache/nokogiri-1.6.2.gem
EXTRACT_SUFX=.gem
RUBY_RD_HTML_FILES=@comment

OSREL=10.0
PREFIX=%D
LOCALBASE=/usr/local
PORTDOCS=@comment

PORTEXAMPLES=@comment

PORTDATA=
LIB32DIR=lib
GTK2_VERSION=2.10.0
GTK3_VERSION=3.0.0
DOCSDIR=share/doc/nokogiri
EXAMPLESDIR=share/examples/nokogiri
DATADIR=share/nokogiri
WWWDIR=www/nokogiri
ETCDIR=etc/nokogiri
--End PLIST_SUB--

--SUB_LIST--
PREFIX=/prefix/rubygem-nokogiri-1.6.2

Re: firefox does not build on 10-STABLE

2014-05-13 Thread Dimitry Andric
On 13 May 2014, at 16:52, John freebsd-li...@potato.growveg.org wrote:
 Hello ports!
 
 I cannot get firefox to build on my system. Can anyone please help? 
...
 /etc/make.conf is empty. The build fails like this:
 
 #  define MOZ_ALWAYS_INLINE_EVEN_DEBUG __attribute__((always_inline)) 
 inline
  ^
 In file included from 
 /usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0/content/svg/content/src/Unified_cpp_content_svg_content_src8.cpp:2:
 In file included from 
 /usr/ports/www/firefox/work/mozilla-release/content/svg/content/src/nsSVGElement.cpp:9:
 In file included from 
 /usr/ports/www/firefox/work/mozilla-release/content/svg/content/src/nsSVGElement.h:15:
 In file included from ../../../../dist/include/mozilla/css/StyleRule.h:16:
 In file included from ../../../../dist/include/mozilla/css/Rule.h:12:
 In file included from 
 /usr/ports/www/firefox/work/mozilla-release/layout/style/nsIStyleRule.h:16:
 In file included from ../../../../dist/include/nsISupports.h:10:
 In file included from ../../../../dist/include/nsrootidl.h:13:
 In file included from ../../../../dist/include/nscore.h:19:
 ../../../../dist/include/mozilla/mozalloc.h:234:21: warning: replacement 
 function 'operator delete[]'
  cannot be declared 'inline' [-Winline-new-delete]
 MOZALLOC_EXPORT_NEW MOZALLOC_INLINE
^
 ../../../../dist/include/mozilla/mozalloc.h:44:27: note: expanded from macro 
 'MOZALLOC_INLINE'
 #  define MOZALLOC_INLINE MOZ_ALWAYS_INLINE_EVEN_DEBUG
  ^
 ../../../../dist/include/mozilla/Attributes.h:27:75: note: expanded from macro
  'MOZ_ALWAYS_INLINE_EVEN_DEBUG'
 #  define MOZ_ALWAYS_INLINE_EVEN_DEBUG __attribute__((always_inline)) 
 inline
  ^
 In file included from 
 /usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0/content/svg/content/src/Unified_cpp_content_svg_content_src8.cpp:2:
 In file included from 
 /usr/ports/www/firefox/work/mozilla-release/content/svg/content/src/nsSVGElement.cpp:9:
 In file included from 
 /usr/ports/www/firefox/work/mozilla-release/content/svg/content/src/nsSVGElement.h:15:
 In file included from ../../../../dist/include/mozilla/css/StyleRule.h:16:
 In file included from ../../../../dist/include/mozilla/css/Rule.h:12:
 In file included from 
 /usr/ports/www/firefox/work/mozilla-release/layout/style/nsIStyleRule.h:16:
 In file included from ../../../../dist/include/nsISupports.h:10:
 In file included from ../../../../dist/include/nsrootidl.h:13:
 In file included from ../../../../dist/include/nscore.h:19:
 ../../../../dist/include/mozilla/mozalloc.h:240:21: warning: replacement 
 function 'operator delete[]'
  cannot be declared 'inline' [-Winline-new-delete]
 MOZALLOC_EXPORT_NEW MOZALLOC_INLINE
^
 ../../../../dist/include/mozilla/mozalloc.h:44:27: note: expanded from macro 
 'MOZALLOC_INLINE'
 #  define MOZALLOC_INLINE MOZ_ALWAYS_INLINE_EVEN_DEBUG
  ^
 ../../../../dist/include/mozilla/Attributes.h:27:75: note: expanded from macro
  'MOZ_ALWAYS_INLINE_EVEN_DEBUG'
 #  define MOZ_ALWAYS_INLINE_EVEN_DEBUG __attribute__((always_inline)) 
 inline
  ^
 8 warnings generated.
 8 warnings generated.
 gmake[5]: Leaving directory 
 `/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0/content/svg/content/src'
 gmake[4]: Leaving directory 
 `/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0'
 gmake[3]: *** [compile] Error 2
 gmake[3]: Leaving directory 
 `/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0'
 gmake[2]: *** [default] Error 2
 gmake[2]: Leaving directory 
 `/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-unknown-freebsd10.0'
 === Compilation failed unexpectedly.

Unfortunately, the error occurred before the part of the log you posted.
Can you post the full log somewhere, or search for a line containing
error: yourself, and paste that part instead?

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail


RE: Port update 189356 needs committed

2014-05-13 Thread jail-primer


-Original Message-
From: Kurt Jaeger [mailto:li...@opsec.eu]
Sent: Tuesday, May 13, 2014 1:01 PM
Cc: po...@freebsd.org
Subject: Re: Port update 181945 needs committed


Hi!

  Will some committer please commit this port update.
  It's just a script.


  http://www.freebsd.org/cgi/query-pr.cgi?pr=181945

It's already committed since Feb.2014 ?

--
p...@opsec.eu+49 171 3101372 6 years to go
!


Sorry my mistake, wrong pr number.

http://www.freebsd.org/cgi/query-pr.cgi?pr=189356




___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: Port update 189120 needs committed

2014-05-13 Thread Kurt Jaeger
Hi!

  Will some committer please commit this port update.
  It's just a script.
 
  http://www.freebsd.org/cgi/query-pr.cgi?pr=189120

It needs staging support, would you please try to add it ?

https://wiki.freebsd.org/ports/StageDir

-- 
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: Patch wanted: VmRSS, VmSize and VmStk in /proc/pid/status

2014-05-13 Thread Thierry Thomas
Le mar 13 mai 14 à 10:28:24 +0200, Scot Hetzel swhet...@gmail.com
 écrivait :

  It's why I'm looking for help here: does somebody knows how the
  corresponding values of these Vm... can be found in FreeBSD?
 
 You could try reading the source for linprocfs to see how it gets those 
 values:
 
 https://svnweb.freebsd.org/base/head/sys/compat/linprocfs/linprocfs.c?revision=263620view=markup#l748

Good idea, I'll check it!
-- 
Th. Thomas.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: staging without root privileges

2014-05-13 Thread Matthias Andree
Am 13.05.2014 19:18, schrieb Anton Shterenlikht:
 https://wiki.freebsd.org/ports/StageDir
 says 
 
 Make sure you tested make package as a normal user (not root).
 
 Does this refer specifically to the package target?

build targets (make all, make stage, make check-plist) and
packaging (make package).

 Or to all targets up to and including package?
 
 I'm asked for root passwd on make config,
 and then I get an error on build:
 
 mkdir: /usr/ports/devel/robodoc/work: Permission denied
 
 which makes sense.

Setting WRKDIRPREFIX to a directory you can write to can fix that, and
PACKAGES specifies where the package should end up. PORT_DBDIR can be
diverted to a directory so you can run even make config without root
privileges.

With that, and the distfiles already downloaded (make checksum), you
should be able to build most ports without privileges.  A few set
NEED_ROOT, those won't do without...
___
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: Java wildfly port

2014-05-13 Thread Kurt Jaeger
Hi!

 I hope we'll have it in the ports system soon.

Right now it's held up by the code slush for 9.3.

-- 
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: Are there plans for updating OpenOCD to version 0.8.0?

2014-05-13 Thread Steven Kreuzer
Hi Torfinn-

On Sun, May 4, 2014 at 4:38 PM, Torfinn Ingolfsen tin...@gmail.com wrote:
 Hello,
 Are there plans for updating devel/openocd to version 0.8.0?

I don't think I am going to get a chance to update this port in the
very near future. If you are interested in taking a shot at upgrading,
feel free to send me any patches for review.
I added it to my todo and hopefully will get a chance to update it.
___
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 compile error

2014-05-13 Thread Bruce

Error on amd freebsd-9.2

Error building Sage.

The following package(s) may have failed to build:

package: linbox-1.3.2.p0
log file: /usr/ports/math/sage/work/sage-6.1.1/logs/pkgs/linbox-1.3.2.p0.log
build directory: 
/usr/ports/math/sage/work/sage-6.1.1/local/var/tmp/sage/build/linbox-1.3.2.p0


The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

gmake: *** [build] Error 1
*** [do-build] Error code 1

Stop in /usr/ports/math/sage.
*** [stage] 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: ports/INDEX building broken on 11.0-CURRENT

2014-05-13 Thread Don Lewis
On 13 May, To: po...@freebsd.org wrote:
 Please excuse the crosspost.  I'm not sure if this is a ports problem or
 a CURRENT problem.
 
 I just updated my 11.0-CURRENT machine to r265940 and can no longer
 build ports/INDEX-11.  My ports tree is r353903.  I think this problem
 is being caused by the recent changes to /usr/share/mk/*.
 
 # make index
 Generating INDEX-11 - please wait..--- describe.accessibility ---
 --- describe.arabic ---
 --- describe.archivers ---
 --- describe.astro ---
 --- describe.audio ---
 --- describe.benchmarks ---
 --- describe.biology ---
 --- describe.cad ---
 --- describe.chinese ---
 --- describe.comms ---
 --- describe.converters ---
 --- describe.databases ---
 --- describe.deskutils ---
 --- describe.devel ---
 clang33: not found
 make[5]: /usr/share/mk/bsd.compiler.mk line 24: warning: clang33 
 --version returned non-zero status
 make[5]: /usr/share/mk/bsd.compiler.mk line 37: Unable to determine 
 compiler type for clang33.  Consider setting COMPILER_TYPE.
 === devel/ccons failed
 *** [describe.devel] Error code 1
 
 make[2]: stopped in /usr/ports
 1 error
 
 make[2]: stopped in /usr/ports
 
 
 Before reporting this error, verify that you are running a supported
 version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you
 have a complete and up-to-date ports collection.  (INDEX builds are
 not supported with partial or out-of-date ports collections.
 If that is the case, then
 report the failure to po...@freebsd.org together with relevant
 details of your ports configuration (including FreeBSD version,
 your architecture, your environment, and your /etc/make.conf
 settings, especially compiler flags and OPTIONS_SET/UNSET settings).
 
 Note: the latest pre-generated version of INDEX may be fetched
 automatically with make fetchindex.
 
 
 *** Error code 1
 
 Stop.
 make[1]: stopped in /usr/ports
 *** Error code 1
 
 Stop.
 make: stopped in /usr/ports
 
 
 If I go to the offending port:
 
 # cd /usr/ports/devel/ccons/
 # make describe
 clang33: not found
 make: /usr/share/mk/bsd.compiler.mk line 24: warning: clang33 --version 
 returned non-zero status
 make: /usr/share/mk/bsd.compiler.mk line 37: Unable to determine compiler 
 type for clang33.  Consider setting COMPILER_TYPE.
 
 
 I don't have any problems building the INDEX file on 9.3-PRERELEASE
 r265940.

Various ports were setting CC to the following, which was causing the
bsd.compiler.mk to barf:
clang32
clang33
/usr/bin/gcc
mingw32-gcc
gcc

The patch below allowed me to successfully run make index and reduced
the error spewage.  It also greatly reduces the need to run
${CC} --version
in order to set COMPILER_TYPE.

It still seems like a great waste to run
${CC} --version
for each port to set COMPILER_VERSION since only a handful of ports need
this information.

Then there is this sort of circular dependency in some ports, like this
one in textproc/ibus/Makefile:

.if ${COMPILER_TYPE} == gcc  ${COMPILER_VERSION}  46
USE_GCC=yes
.endif

This will cause CC to be redefined, but COMPILER_TYPE and
COMPILER_VERSION will still retain their old values.



Index: share/mk/bsd.compiler.mk
===
--- share/mk/bsd.compiler.mk(revision 265940)
+++ share/mk/bsd.compiler.mk(working copy)
@@ -21,23 +21,28 @@
 .if !target(__bsd.compiler.mk__)
 __bsd.compiler.mk__:
 
-_v!=   ${CC} --version
 .if !defined(COMPILER_TYPE)
-. if ${CC:T:Mgcc*}
+. if ${CC:T:M*gcc*}
 COMPILER_TYPE:=gcc  
-. elif ${CC:T:Mclang}
+. elif ${CC:T:Mclang*}
 COMPILER_TYPE:=clang
-. elif ${_v:Mgcc}
+. else
+_v!=   ${CC} --version
+.  if ${_v:Mgcc}
 COMPILER_TYPE:=gcc
-. elif ${_v:M\(GCC\)}
+.  elif ${_v:M\(GCC\)}
 COMPILER_TYPE:=gcc
-. elif ${_v:Mclang}
+.  elif ${_v:Mclang}
 COMPILER_TYPE:=clang
-. else
+.  else
 .error Unable to determine compiler type for ${CC}.  Consider setting 
COMPILER_TYPE.
+.  endif
 . endif
 .endif
 .if !defined(COMPILER_VERSION)
+. if !defined(_v)
+_v!=   ${CC} --version || echo 'unknown'
+. endif
 COMPILER_VERSION!=echo ${_v:M[1-9].[0-9]*} | awk -F. '{print $$1 * 1 + $$2 
* 100 + $$3;}'
 .endif
 .undef _v


___
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: math/sage compile error

2014-05-13 Thread Montgomery-Smith, Stephen
On 05/13/2014 05:55 PM, Bruce wrote:
 Error on amd freebsd-9.2
 
 Error building Sage.
 
 The following package(s) may have failed to build:
 
 package: linbox-1.3.2.p0
 log file:
 /usr/ports/math/sage/work/sage-6.1.1/logs/pkgs/linbox-1.3.2.p0.log
 build directory:
 /usr/ports/math/sage/work/sage-6.1.1/local/var/tmp/sage/build/linbox-1.3.2.p0
 
 
 The build directory may contain configuration files and other potentially
 helpful information. WARNING: if you now run 'make' again, the build
 directory will, by default, be deleted. Set the environment variable
 SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
 
 gmake: *** [build] Error 1
 *** [do-build] Error code 1
 
 Stop in /usr/ports/math/sage.
 *** [stage] Error code 1
 
 Stop in /usr/ports/math/sage.

Hi Bruce,

I am the maintainer of math/sage.  But I think I am missing all your
messages, because there are too many emails sent to freebsd-ports.  Can
you CC me as step...@freebsd.org on these emails?  Then we can start a
dialogue and figure out if I can solve your problem.

Thanks, Stephen
___
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 error log message

2014-05-13 Thread Bruce
/bin/sh ../../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../..  -I../.. -I. -I../../linbox -DDISABLE_COMMENTATOR -O2 -g 
-DNDEBUG -U_LB_DEBUG -DDISABLE_COMMENTATOR 
-I/usr/ports/math/sage/work/sage-6.1.1/local/include 
-I/usr/ports/math/sage/work/sage-6.1.1/local/include 
-I/usr/ports/math/sage/work/sage-6.1.1/local/include 
-I/usr/ports/math/sage/work/sage-6.1.1/local/include 
-I/usr/ports/math/sage/work/sage-6.1.1/local/include -pipe 
-Wl,-rpath=/usr/ports/math/sage/work/sage-6.1.1/local/lib 
-Wl,-rpath=/usr/local/lib/gcc47 
-Wl,-rpath=/usr/ports/math/sage/work/sage-6.1.1/local/lib 
-Wl,-rpath=/usr/local/lib/gcc47 -g -fPIC -c -o linbox-sage.lo linbox-sage.C
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I../.. -I. 
-I../../linbox -DDISABLE_COMMENTATOR -O2 -g -DNDEBUG -U_LB_DEBUG 
-DDISABLE_COMMENTATOR 
-I/usr/ports/math/sage/work/sage-6.1.1/local/include 
-I/usr/ports/math/sage/work/sage-6.1.1/local/include 
-I/usr/ports/math/sage/work/sage-6.1.1/local/include 
-I/usr/ports/math/sage/work/sage-6.1.1/local/include 
-I/usr/ports/math/sage/work/sage-6.1.1/local/include -pipe 
-Wl,-rpath=/usr/ports/math/sage/work/sage-6.1.1/local/lib 
-Wl,-rpath=/usr/local/lib/gcc47 
-Wl,-rpath=/usr/ports/math/sage/work/sage-6.1.1/local/lib 
-Wl,-rpath=/usr/local/lib/gcc47 -g -fPIC -c linbox-sage.C  -fPIC -DPIC 
-o .libs/linbox-sage.o

{standard input}: Assembler messages:
{standard input}:669830: Warning: end of file not at end of a line; 
newline inserted

{standard input}:670930: Error: unknown pseudo-op: `.lvl719'
{standard input}: Error: open CFI at the end of file; missing 
.cfi_endproc directive

g++47: internal compiler error: Killed: 9 (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html for instructions.
make[6]: *** [linbox-sage.lo] Error 1
make[6]: Leaving directory 
`/usr/ports/math/sage/work/sage-6.1.1/local/var/tmp/sage/build/linbox-1.3.2.p0/src/interfaces/sage'

make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory 
`/usr/ports/math/sage/work/sage-6.1.1/local/var/tmp/sage/build/linbox-1.3.2.p0/src/interfaces'

make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory 
`/usr/ports/math/sage/work/sage-6.1.1/local/var/tmp/sage/build/linbox-1.3.2.p0/src'

make[3]: *** [all] Error 2
make[3]: Leaving directory 
`/usr/ports/math/sage/work/sage-6.1.1/local/var/tmp/sage/build/linbox-1.3.2.p0/src'

Error building LinBox.

real3m21.911s
user2m59.280s
sys 0m12.563s

Error installing package linbox-1.3.2.p0

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the relevant part of the log file
  /usr/ports/math/sage/work/sage-6.1.1/logs/pkgs/linbox-1.3.2.p0.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/usr/ports/math/sage/work/sage-6.1.1/local/var/tmp/sage/build/linbox-1.3.2.p0 
and type 'make' or whatever is appropriate.

Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd 
'/usr/ports/math/sage/work/sage-6.1.1/local/var/tmp/sage/build/linbox-1.3.2.p0' 
 '/usr/ports/math/sage/work/sage-6.1.1/sage' --sh)

When you are done debugging, you can type exit to leave the subshell.

(END)

___
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: drupal7-7.26 - Release updates available; 7.27 7.28

2014-05-13 Thread Gio
Dear miwi,

I'd like to bring to your attention that the drupal7-7.26 port should be
updated to the latest drupal release: drupal7-7.28 dated 08 May 2014.

Prior to the current 7.28 release there was also a drupal7-7.27 release
dated 16 April 2014 which fixed some security vulnerabilities as
mentioned in a Drupal core security advisory SA-CORE-2014-002 linked
here: https://drupal.org/SA-CORE-2014-002

If there is anything I can do to help with updating the port please let
me know.

Regards

Gio
___
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: ejabberd-2.1.13 - Release updates available; 14.05, 13.12 13.10

2014-05-13 Thread Gio
Dear ashish,

I would like to bring to your attention that the ejabberd-2.1.13 port
should be
updated to the latest release: ejabberd Community 14.05 dated 13 May 2014.

Prior to the current ejabberd 14.05 release there was also a 13.12 release
dated 16 December 2013 and a 13.10 release dated 09 October 2013.

Support for ejabberd 2.1.x has been discontinued.
See: http://www.ejabberd.im/

If there is anything I can do to help with updating the port please let
me know.

Regards

Gio
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: FreeBSD Port: ejabberd-2.1.13 - Release updates available; 14.05, 13.12 13.10

2014-05-13 Thread Dewayne Geraghty

On 14/05/2014 11:09 AM, Gio wrote:
 Dear ashish,

 I would like to bring to your attention that the ejabberd-2.1.13 port
 should be
 updated to the latest release: ejabberd Community 14.05 dated 13 May 2014.

 Prior to the current ejabberd 14.05 release there was also a 13.12 release
 dated 16 December 2013 and a 13.10 release dated 09 October 2013.

 Support for ejabberd 2.1.x has been discontinued.
 See: http://www.ejabberd.im/

 If there is anything I can do to help with updating the port please let
 me know.

 Regards

 Gio
 ___
 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


Thank for the advise, though it is better to submit your requests via
the Problem Reporting mechanism at

http://freebsd.org/send-pr.html

This will be sent to the maintainer of the port, and provides a
consistent way for everyone to search for and track issues/requests. 

If you place, at the  beginning of your synopsis:
net-im/ejabberd
the PR is sent, directly to the maintainer.  And the category is ports

If there are security vulnerabilities that have been discovered but not
disclosed via portaudit, which isn't the case here, you should notify
ports-secur...@freebsd.org.  They're very responsive.
Dewayne.
___
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: math/sage error log message

2014-05-13 Thread Montgomery-Smith, Stephen
On 05/13/2014 07:17 PM, Bruce wrote:

 -Wl,-rpath=/usr/local/lib/gcc47 -g -fPIC -c linbox-sage.C  -fPIC -DPIC
 -o .libs/linbox-sage.o
 {standard input}: Assembler messages:
 {standard input}:669830: Warning: end of file not at end of a line;
 newline inserted
 {standard input}:670930: Error: unknown pseudo-op: `.lvl719'
 {standard input}: Error: open CFI at the end of file; missing
 .cfi_endproc directive
 g++47: internal compiler error: Killed: 9 (program cc1plus)
 Please submit a full bug report,
 with preprocessed source if appropriate.
 .

What a horrible error!  Do you get the error in the same place every
time you try to compile sage?

It might be a hardware error, or maybe the compiler is running out of
memory.  Did you try building it with MAKE_JOBS_UNSAFE set?  How many
cores do you have on your processor?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: FreeBSD Port: ejabberd-2.1.13 - Release updates available; 14.05, 13.12 13.10

2014-05-13 Thread Ashish SHUKLA
On Wed, 14 May 2014 02:09:57 +0100, Gio g...@spc.org said:
 Dear ashish,

Hi Gio,

 I would like to bring to your attention that the ejabberd-2.1.13 port
 should be
 updated to the latest release: ejabberd Community 14.05 dated 13 May 2014.

I know about these updates, and have tried updating port to 13.x release, but
not much success.

ejabberd project has switched to using git clones of dependencies, instead of
bundling them with the snapshot, which was not at all port friendly. As a
workaround, I packaged latest snapshot of all dependencies, but rebar stuff
needs to be workaround-ed, which I could not figure out last time I looked at
it. I'll look at it again in upcoming days.

I think other operating systems are also stuck at 2.1.13 for the same reason.

If you need to use the latest version, then I propose building/installing
yourself using their instructions.

 Prior to the current ejabberd 14.05 release there was also a 13.12 release
 dated 16 December 2013 and a 13.10 release dated 09 October 2013.

 Support for ejabberd 2.1.x has been discontinued.
 See: http://www.ejabberd.im/

 If there is anything I can do to help with updating the port please let
 me know.

Anyways, if you've already prepared an update for the port, then I'll be happy
to look at it.

HTH
-- 
Ashish SHUKLA  | GPG: F682 CDCC 39DC 0FEA E116  20B6 C746 CFA9 E74F A4B0
Sent from my Emacs


signature.asc
Description: PGP signature


RE: Port update 189120 needs committed

2014-05-13 Thread qjail


-Original Message-
From: Kurt Jaeger [mailto:li...@opsec.eu]
Sent: Tuesday, May 13, 2014 2:55 PM
To: qjail
Cc: po...@freebsd.org
Subject: Re: Port update 189120 needs committed


Hi!

  Will some committer please commit this port update.
  It's just a script.

  http://www.freebsd.org/cgi/query-pr.cgi?pr=189120

It needs staging support, would you please try to add it ?

https://wiki.freebsd.org/ports/StageDir

--
p...@opsec.eu+49 171 3101372 6 years to go
!


 http://svnweb.freebsd.org/ports/head/sysutils/qjail/?view=log

 revision 327772 says it's all ready added, or am I reading that wrong.


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: Port update 189120 needs committed

2014-05-13 Thread Kurt Jaeger
Hi!

It's just a script.
  
http://www.freebsd.org/cgi/query-pr.cgi?pr=189120
  
  It needs staging support, would you please try to add it ?
  
  https://wiki.freebsd.org/ports/StageDir

  http://svnweb.freebsd.org/ports/head/sysutils/qjail/?view=log
 
  revision 327772 says it's all ready added, or am I reading that wrong.

You are reading this wrong. The current port is configured
to not do the STAGE phase. That's why it has NO_STAGE=yes.

Have you looked at

 https://wiki.freebsd.org/ports/StageDir

? It says right at the start:

Convert a port to Stage

List of information to know to be able to convert a port.

Remove the NO_STAGE=yes line. 

and then goes on from there.

-- 
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