date:20131106

On 11/6/2013 14:30, Mark Martinec wrote:
 On 11/5/2013 14:54, Wolfgang Riegler wrote:
 building soundkonverter fails on 9.1 AMD64 with:
 /usr/local/include/taglib/mp4coverart.h:49: error: comma at end of
 enumerator list *** [CMakeFiles/soundkonverter.dir/metadata/tagengine.o]
 Error code 1 [snip]
 Complete build log is attached.
  
 John Marino wrote:
 There is a Problem Report system which is appropriate for these kinds of
 reports.  It automatically notifies the maintainer, and it has a place
 for attachments (which didn't make it through the mailer.)
 http://www.freebsd.org/send-pr.html
 
 That was already reported on 2013-10-11, but remains untouched:
 
   http://www.freebsd.org/cgi/query-pr.cgi?pr=182906
 
 

Yeah, that's unfortunate.  However, everything still has to go through
listed maintainer until it's clear that he's non-responsive.  Now it
appropriate to ping this list in that case, assuming multiple attempts
to ping the maintainer fail.  I put jhale in copy, so this will count as
a ping. :)

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

CC, CPP etc vs CONFIGURE_ENV

2013-11-06 Thread Andriy Gapon

I wonder why do-configure target explicitly sets things like CC=${CC}
CPP=${CPP} etc in configure script environment as opposed to them just being
placed into CONFIGURE_ENV.
What is the technical reason?

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

INDEX now builds successfully on 8.x

2013-11-06 Thread Ports Index build


___
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: CC, CPP etc vs CONFIGURE_ENV

2013-11-06 Thread Charles Swiger

Hi--

On Nov 6, 2013, at 6:27 AM, Andriy Gapon a...@freebsd.org wrote:
 I wonder why do-configure target explicitly sets things like CC=${CC}
 CPP=${CPP} etc in configure script environment as opposed to them just being
 placed into CONFIGURE_ENV.
 What is the technical reason?

Setting $CC and such worked with older ./configure which didn't implement 
$CONFIGURE_ENV.
It also plays more nicely with things which roll their own ./configure as a shim
that isn't actually GNU autoconf.

Regards,
-- 
-Chuck

___
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: CC, CPP etc vs CONFIGURE_ENV

2013-11-06 Thread Andriy Gapon

on 06/11/2013 17:11 Charles Swiger said the following:
 Hi--
 
 On Nov 6, 2013, at 6:27 AM, Andriy Gapon a...@freebsd.org wrote:
 I wonder why do-configure target explicitly sets things like CC=${CC}
 CPP=${CPP} etc in configure script environment as opposed to them just 
 being
 placed into CONFIGURE_ENV.
 What is the technical reason?
 
 Setting $CC and such worked with older ./configure which didn't implement 
 $CONFIGURE_ENV.
 It also plays more nicely with things which roll their own ./configure as a 
 shim
 that isn't actually GNU autoconf.

Apologies, you seem to think that CONFIGURE_ENV is an environment variable of
its own.  But, as far as I can see, it is not.  It is a make variable with a
value that expands to FOO=BAR VAR=VAL ... and those FOO, VAR, etc are the
environment variables that are to be set in configure's environment:

${SETENV} ... ${CONFIGURE_ENV} ./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}

So, either I didn't understand what you said or what you said is not relevant.


-- 
Andriy Gapon
___
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] r332670: 1x depend (??? in math/r-cran-mvtnorm), 3x leftovers

Mark as NO_STAGE

Somehow this port managed to not be touched during the NO_STAGE sweep.

Reported by:marino
-

  Build ID:  20131104073200-41078
  Job owner: b...@freebsd.org
  Buildtime: 2 days
  Enddate:   Wed, 06 Nov 2013 16:11:44 GMT

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

-

Port:math/R-cran-sspir 0.2.10_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20131104073200-41078-220412/R-cran-sspir-0.2.10_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   DEPEND (??? IN MATH/R-CRAN-MVTNORM)
  Log: 
https://qat.redports.org//~b...@freebsd.org/20131104073200-41078-220413/R-cran-mvtnorm-0.9.96_12.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20131104073200-41078-220414/R-cran-sspir-0.2.10_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20131104073200-41078-220415/R-cran-sspir-0.2.10_1.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20131104073200-41078
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: CC, CPP etc vs CONFIGURE_ENV

2013-11-06 Thread Charles Swiger

On Nov 6, 2013, at 7:25 AM, Andriy Gapon a...@freebsd.org wrote:
 Setting $CC and such worked with older ./configure which didn't implement 
 $CONFIGURE_ENV.
 It also plays more nicely with things which roll their own ./configure as a 
 shim
 that isn't actually GNU autoconf.
 
 Apologies, you seem to think that CONFIGURE_ENV is an environment variable of
 its own.  But, as far as I can see, it is not.  It is a make variable with a
 value that expands to FOO=BAR VAR=VAL ... and those FOO, VAR, etc are the
 environment variables that are to be set in configure's environment:
 
 ${SETENV} ... ${CONFIGURE_ENV} ./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}

Yes, setup via ports/bsd.options.mk and such (aka configure.mk on some other 
platforms).

 So, either I didn't understand what you said or what you said is not relevant.

That's fair enough-- I don't always manage to be both comprehensible and 
relevant.  :-)

I seemed to recall that sufficiently modern configure's would look into
$CONFIGURE_ENV if you set it via:

   export ${CONFIGURE_ENV}; ./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}

...instead.  But I don't see signs of that in GNU autoconf, so that might be
a non-standard thing.

Regards,
-- 
-Chuck

___
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

mozc-tool 1.11.1502.102 fail

2013-11-06 Thread Kenichi Niioka

Dear porters.

I have following error with FreeBSD 11.0-CURRENT #0 r257452 amd64.

$ cd /usr/ports/japanese/mozc-tool
$ make

[snip]

  AR(target) out_linux/Release/obj.target/gui/libcharacter_pad_lib.a
  AR(target) out_linux/Release/obj.target/client/libclient.a
  AR(target) out_linux/Release/obj.target/gui/libconfig_dialog_lib.a
  AR(target) out_linux/Release/obj.target/session/libkey_parser.a
  AR(target) out_linux/Release/obj.target/session/libkeymap.a
  AR(target) out_linux/Release/obj.target/session/libkey_event_util.a
  AR(target) out_linux/Release/obj.target/gui/libdictionary_tool_lib.a
  AR(target) out_linux/Release/obj.target/gui/libgui_base.a
  AR(target) out_linux/Release/obj.target/gui/libpost_install_dialog_lib.a
  AR(target) out_linux/Release/obj.target/gui/libset_default_dialog_lib.a
  AR(target) out_linux/Release/obj.target/gui/libword_register_dialog_lib.a
  CXX(target) out_linux/Release/obj.target/mozc_tool/gui/tool/mozc_tool_main.o
  LINK(target) out_linux/Release/mozc_tool
/usr/bin/ld: cannot find -liconv
c++: error: linker command failed with exit code 1 (use -v to see invocation)


Thanks in advance.

--
Kenichi Niioka
___
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

[RFC] Stage support for PEAR classes and channels

2013-11-06 Thread Antoine Brodin

Hi there,

The patch below adds stage support to pear classes and pear channels
(not devel/pear itself)
http://people.freebsd.org/~antoine/ports/stage-pear.diff

I verified on ~170 ports from devel that the content of the generated
package differs only in the timestamp in channel .reg files between
staged and unstaged.

Please comment,

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

Re: ports/161947: multimedia/libdvdnav builds broken binaries on big endian machines

2013-11-06 Thread jhibbits

Synopsis: multimedia/libdvdnav builds broken binaries on big endian machines

Responsible-Changed-From-To: freebsd-ppc-freebsd-ports
Responsible-Changed-By: jhibbits
Responsible-Changed-When: Wed Nov 6 17:49:23 UTC 2013
Responsible-Changed-Why: 
This is a ports bug, handing it over.

http://www.freebsd.org/cgi/query-pr.cgi?pr=161947
___
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: pkg install subversion broken on 9.2-R...

2013-11-06 Thread John-Mark Gurney

Bryan Drewery wrote this message on Wed, Nov 06, 2013 at 06:06 -0600:
 On 11/5/2013 10:54 PM, John-Mark Gurney wrote:
  Ok, I know this is partly my fault for not being specific enough, but
  after a pkg install python installed 2.7 and not 2.6 and the full set
  of 3.x versions, I was ok, lets just do the same for subversion...
  
  Of course I also didn't read that it was going to install 1.6.23_2,
  1.7.13 AND 1.8.3 when you run pkg install subversion so I got a bunch
  of conflicts...
  
  Are we planning on fixing that so that it either installs on version,
  or asks which version you'd like to install?
  
  Thanks.
  
 
 Yes, this comes up a lot. This is part of the ongoing effort to make all
 PKGNAMEs unique. Once that is done, pkg will track by PKGNAME instead of
 origin and this problem goes away as it will find only
 1 version of subversion when you type 'pkg install subversion'.
 
 The plan is to get that in for pkg-1.3.

Ok, good to hear.  Just wanted to make sure it was being worked on...

Thanks.

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 All that I will do, has been done, All that I have, has not.
___
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: OCaml 4?

2013-11-06 Thread Michael Grünewald

Hi Rui!

Sorry that I did not take time to answer your previous EMail. It seems
you did not check outstanding PRs or overlooked this one:

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

In short, there is a candidate upgrade in the ports, since quite a
while.  While I did not hear anything from committer, I probably need to
fix that STAGE thing before the port gets checked in.

Rui Paulo wrote:
 Any plans to upgrade OCaml in FreeBSD ports?  If you don't have time, I might 
 take a stab at it.

Three side notes:

- https://bitbucket.org/michipili/ports-bsd is a bitbucket repo where I
push my (mostly OCaml) FreeBSD ports before they went in the repo tree.
If you already have a bitbucket account, consider following this repo to
get updates. You may check this out if you want to try the port, your
feedback would be welcome.

- https://bitbucket.org/michipili/bsdmakepscripts is a bitbucket repo
for BSD Makefiles useful to develop with OCaml. (Shameless promotion!)

- It is best to use open channel (like the freebsd-ports@ mailing list),
because it is archived and indexed, so people sharing your concern get a
chance to find your question and my answer.

Best regards,
Michael

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

Re: poudriere + soundkonverter build fails

2013-11-06 Thread David Naylor

On Tuesday, 5 November 2013 14:54:12 Wolfgang Riegler wrote:
 Hi,

Hi,

 building soundkonverter fails on 9.1 AMD64 with:
 /usr/local/include/taglib/mp4coverart.h:49: error: comma at end of
 enumerator list *** [CMakeFiles/soundkonverter.dir/metadata/tagengine.o]
 Error code 1
 
 
 My options are:
 ---Begin OPTIONS List---
 === The following configuration options are available for
 soundkonverter-2.0.4: NLS=on: Native Language Support
  Audio codec formats: you have to choose at least one of them
  AFTEN=on: ATSC A/52 audio encoder
  FAAC=on: FAAC AAC encoder support
  FFMPEG=on: FFmpeg support (WMA, AIFF, AC3, APE...)
  FLAC=on: FLAC lossless audio codec support
  FLAKE=on: FLAC audio codec
  FLUIDSYNTH=on: SoundFont 2 audio codec
  LAME=on: LAME MP3 audio encoder support
  MAC=on: Monkey's Audio lossless codec
  MPLAYER=on: MPlayer media player support
  MUSEPACK=on: MPC audio format support
  NEROAAC=on: Nero AAC MPEG-3 and 3GPP audio codec
  OPUSTOOLS=on: Opus audio codec
  SHORTEN=on: Shorten (lossless) audio codec
  SPEEX=on: Speex audio format support
  TIMIDITY=on: MIDI audio decoder
  TTA=on: True Audio lossless audio codec
  TWOLAME=on: TwoLAME MP2 audio encoder support
  VORBIS=on: Ogg Vorbis audio codec support
  WAVPACK=on: WavPack lossless audio format support
  Audio filter tools: you have to choose at least one of them
  NORMALIZE=on: MP3/Ogg Vorbis audio filter and replaygain
  SOX=on: Universal sound sample translator
  Replaygain tools for codecs: you have to choose at least one of them
  AACGAIN=on: AAC audio replaygain
  FLAC=on: FLAC lossless audio codec support
  MP3GAIN=on: MP3 audio replaygain
  MUSEPACK=on: MPC audio format support
  NORMALIZE=on: MP3/Ogg Vorbis audio filter and replaygain
  VORBISGAIN=on: Ogg Vorbis audio replaygain
  WAVPACK=on: WavPack lossless audio format support
 === Use 'make config' to modify these settings
 ---End OPTIONS List---
 
 
 Complete build log is attached.

This is a strange error.  Nothing has changed with soundkonverter to cause 
this break so the cause is likely some other package (I naively blame taglib).  
You can fix it by using either clang of a newer version of gcc to build the 
port (for example `make USE_GCC=yes`).  

My current approach is to wait and see if the error goes away.  (Or wait until 
I have more time to track down the root cause, other than using an old 
compiler to compile new code [or something about old dogs and new code ;-D]).  

Regards

signature.asc
Description: This is a digitally signed message part.

Re: OCaml 4?

On 11/6/2013 20:38, Michael Grünewald wrote:
 Hi Rui!
 
 Sorry that I did not take time to answer your previous EMail. It seems
 you did not check outstanding PRs or overlooked this one:
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/173364
 
 In short, there is a candidate upgrade in the ports, since quite a
 while.  While I did not hear anything from committer, I probably need to
 fix that STAGE thing before the port gets checked in.
 
 Rui Paulo wrote:
 Any plans to upgrade OCaml in FreeBSD ports?  If you don't have time, I 
 might take a stab at it.
 
 Three side notes:
 
 - https://bitbucket.org/michipili/ports-bsd is a bitbucket repo where I
 push my (mostly OCaml) FreeBSD ports before they went in the repo tree.
 If you already have a bitbucket account, consider following this repo to
 get updates. You may check this out if you want to try the port, your
 feedback would be welcome.
 
 - https://bitbucket.org/michipili/bsdmakepscripts is a bitbucket repo
 for BSD Makefiles useful to develop with OCaml. (Shameless promotion!)
 
 - It is best to use open channel (like the freebsd-ports@ mailing list),
 because it is archived and indexed, so people sharing your concern get a
 chance to find your question and my answer.
 




The other thing to note is that DragonFly Ports (dports) has had ocaml 4
and related ocaml upgrades for 9 months.  There's really no need to
reinvent this, just take the dports versions.  I am so glad we didn't
wait around for those PRs.

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: I'm having conflicts with pkg pkg_ and portmaster .

2013-11-06 Thread Edwin L. Culp W.

On Wed, Nov 6, 2013 at 6:09 AM, Bryan Drewery bdrew...@freebsd.org wrote:

On 11/5/2013 1:05 PM, Edwin L. Culp W. wrote:
I try to use only portmaster and/or directly with the port using make,
etc. It seems like the pkg stuff ends up biting me every so often. I
far
prefer compiling to packages.

Hopefully my question is simple. I would love to make the pkg stuff
disappear and only use the ports tree directly or with portmaster.

portmaster is a wrapper around ports. Ports always use a package
management tool behind the scenes. It used to be the
pkg_create/pkg_add/pkg_info tools. Going forward it is pkg (if you have
WITH_PKGNG=yes in make.conf).

I don't have WITH_PKGNG=yes in make.conf but I might have tried it at the
beginning.
Is that going to be catastrophic?

portmaster does support the old tools still and the new one.

Did you previously run pkg2ng?

Very probable but not sure.

Did you add WITH_PKGNG=yes to your
make.conf? If so you cannot go backwards and there is no reason to do so.

I don't think so but over time I could have.

Somehow I seem to manage to create these problems on most of my ports:

=== No ORIGIN in /var/db/pkg/gutenprint-base-5.2.8/+CONTENTS

=== No ORIGIN in /var/db/pkg/gutenprint-cups-5.2.8_1/+CONTENTS

I have a list of my installed ports so I am tempted to just eliminate ALL
the pkg stuff, if possible, and just use ports directly and portmaster.
I
tried that a few weeks ago and somehow it seems to have come back. This
seems similar to the forum at
http://forums.freebsd.org/showthread.php?t=42842 I agree with what
rtwingfield says but I don't see a solution.
Basically I would love to remove pkg pkg_ stuff COMPLETELY and just
compile the port or use portmaster. Is that even an viable option, today?

I am up to date on 9.1 and will upgrade to current 10 shortly after I
have
my ports back to manual control if it isn't worse.

--
Regards,
Bryan Drewery

Does anyone have a quick and dirty method to get everything to work with
portmaster and preferably compiling and not packages.

I would certainly appreciate a link to help clean up and be able to get
back to business as usual.

Thanks,

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

Bienes Raíces in Coatepec, Veracruz, Mexico http://www.ecomania.info

http://www.facebook.com/pages/Inmobiliaria-Bienes-Raices-httpEcoManiainfo/102249989850215?sk=photos_albums
___
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: CC, CPP etc vs CONFIGURE_ENV

2013-11-06 Thread Andrew W. Nosenko

On Wed, Nov 6, 2013 at 6:51 PM, Charles Swiger cswi...@mac.com wrote:
 On Nov 6, 2013, at 7:25 AM, Andriy Gapon a...@freebsd.org wrote:
 Setting $CC and such worked with older ./configure which didn't implement 
 $CONFIGURE_ENV.
 It also plays more nicely with things which roll their own ./configure as a 
 shim
 that isn't actually GNU autoconf.

 Apologies, you seem to think that CONFIGURE_ENV is an environment variable of
 its own.  But, as far as I can see, it is not.  It is a make variable with a
 value that expands to FOO=BAR VAR=VAL ... and those FOO, VAR, etc are the
 environment variables that are to be set in configure's environment:

 ${SETENV} ... ${CONFIGURE_ENV} ./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}

 Yes, setup via ports/bsd.options.mk and such (aka configure.mk on some other 
 platforms).

 So, either I didn't understand what you said or what you said is not 
 relevant.

 That's fair enough-- I don't always manage to be both comprehensible and 
 relevant.  :-)

 I seemed to recall that sufficiently modern configure's would look into
 $CONFIGURE_ENV if you set it via:

export ${CONFIGURE_ENV}; ./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}

 ...instead.  But I don't see signs of that in GNU autoconf, so that might be
 a non-standard thing.


After variable substitution by make, it will become something like
export VAR1=FOO VAR2=BAR; ./configure
and then executed by shell.  So, from configure script point of view,
it is the same environment variables.

-- 
Andrew W. Nosenko andrew.w.nose...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: OCaml 4?

2013-11-06 Thread Michael Grünewald

Hi John,

John Marino wrote:

 The other thing to note is that DragonFly Ports (dports) has had ocaml 4
 and related ocaml upgrades for 9 months.  There's really no need to
 reinvent this, just take the dports versions.  I am so glad we didn't
 wait around for those PRs.

It seems dports has ocaml 4.00.1 while I prepared a 4.01.0, if you test
it, your feddback would be welcome!

Thank you for pointing out that dports can be used as a basis for
FreeBSD ports, maybe I will get the habit to check that out before
starting to work on a new port.

Best regards,
Michael

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

Re: OCaml 4?

On 11/6/2013 21:02, Michael Grünewald wrote:
 
 It seems dports has ocaml 4.00.1 while I prepared a 4.01.0, if you test
 it, your feddback would be welcome!

Surely dports could be updated to ocaml 4.01.0 as easily as changing the
PORTVERSION and regenerating the distinfo file?

 Thank you for pointing out that dports can be used as a basis for
 FreeBSD ports, maybe I will get the habit to check that out before
 starting to work on a new port.

We try to avoid maintaining different versions because they are a
maintenance nightmare.  Ocaml is a rare port and we very much want
FreeBSD to base an update on the dport so we can sync with FreeBSD again
(it's not just ocaml, but others like ocamlimages, etc).

Another is Libreoffice.  Every time there is an extremely minor update
to it, I have to regenerate a makefile diff again.

As such, the vast majority of dports identical or nearly so to their
ports counterparts.  At most they contain extra patches or a couple of
extra switches often contained in Makefile.DragonFly.

Sometimes we have fixes that FreeBSD could use.  Now that I have a
commit bit, I try to push these directly into FreeBSD port but there's a
lot left over from before that was the case.

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

Update devel/zmq (once more, this time Cc ports@)

Hi,

any chance you'll update zmq to the latest version in the near future,
or at to least 3.2.4? sysutils/py-salt depends on it and has keep-alive
issues with the old/outdated version.

Thanks,
Michael

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

Re: Update devel/zmq (once more, this time Cc ports@)

2013-11-06 Thread William Grzybowski

On Wed, Nov 6, 2013 at 8:05 PM, Michael Gmelin free...@grem.de wrote:
 Hi,

 any chance you'll update zmq to the latest version in the near future,
 or at to least 3.2.4? sysutils/py-salt depends on it and has keep-alive
 issues with the old/outdated version.

You should open a PR, that way it will timeout and then someone can
take care of it regardless of the maintainer availability.

-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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

Confusion about devel/py-yaml options

IMHO the sole purpose of this port is providing YAML support to python,
yet it defines

OPTIONS_DEFINE= YAML

which is not enabled by default and shown to the user as

[ ] YAMLYAML format or parser support

As far as I can tell this option enables the libyaml plugin in PyYAML.
LibYAML is written in C and as a result PyYAML is supposed to run
paster/nicer etc. Unfortunately the current option name doesn't make
this clear and probably should be overridden to say something like Use
libYAML plugin for faster YAML parsing.

Cheers,
Michael

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

Re: Update devel/zmq (once more, this time Cc ports@)

On Wed, 6 Nov 2013 20:14:48 -0200
William Grzybowski willia...@gmail.com wrote:

 On Wed, Nov 6, 2013 at 8:05 PM, Michael Gmelin free...@grem.de
 wrote:
  Hi,
 
  any chance you'll update zmq to the latest version in the near
  future, or at to least 3.2.4? sysutils/py-salt depends on it and
  has keep-alive issues with the old/outdated version.
 
 You should open a PR, that way it will timeout and then someone can
 take care of it regardless of the maintainer availability.
 

You're right, I was trying to get away being lazy.

PR is http://www.freebsd.org/cgi/query-pr.cgi?pr=183730

and a separate one for the python port

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


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

Re: Update devel/zmq (once more, this time Cc ports@)

2013-11-06 Thread Mark Martinec

Michael Gmelin wrote:
 any chance you'll update zmq to the latest version in the near future,
 or at to least 3.2.4? sysutils/py-salt depends on it and has keep-alive
 issues with the old/outdated version.

Not just keep-alive, the Salt needs libzmq version 3 for IPv6 support.

The Salt authors state that libzmq version 2 is often unreliable,
the version 3 now solves most of their reliability/stability issues.

William Grzybowski wrote:
 You should open a PR, that way it will timeout and then someone can
 take care of it regardless of the maintainer availability.

It's not just py-salt, another port relying on version 3 of libzmq
is amavisd-new, as version 2 of libzmq does not support IPv6
and version 3 does.

IMO the devel/zmq should switch to zmq version 3.2.4
which is now in devel/zmq-devel, and the zmq-devel should
switch to version 4.

Also the perl module ZeroMQ (port net/p5-ZeroMQ) is no longer maintained
and should be supplemented by perl modules  by the same author:
ZMQ-Constants, ZMQ-LibZMQ3, ZMQ, (and ZMQ-LibZMQ2 for backward
compatibility with old libzmq).

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

Re: Update devel/zmq (once more, this time Cc ports@)

On Wed, 6 Nov 2013 23:45:29 +0100
Mark Martinec mark.martinec+free...@ijs.si wrote:

 Michael Gmelin wrote:
  any chance you'll update zmq to the latest version in the near
  future, or at to least 3.2.4? sysutils/py-salt depends on it and
  has keep-alive issues with the old/outdated version.
 
 Not just keep-alive, the Salt needs libzmq version 3 for IPv6 support.
 
 The Salt authors state that libzmq version 2 is often unreliable,
 the version 3 now solves most of their reliability/stability issues.
 

And the salt authors are right about this, as I experienced in the last
couple of days. Apparently there's a reason why salt logs a big
warning about using zmq 2 on every start :)

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

[QAT] r332991: 2x leftovers, 2x finished

games/py-mnemosyne: update to 2.2.1

- Update to 2.2.1
- use python auto plist
- Drop maintainership

PR: ports/183707
Submitted by:   Marek marekrud gmail.com (maintainer)
-

  Build ID:  20131106133600-52813
  Job owner: w...@freebsd.org
  Buildtime: 10 hours
  Enddate:   Wed, 06 Nov 2013 23:40:49 GMT

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

-

Port:games/py-mnemosyne 2.2.1,1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131106133600-52813-222416/py27-mnemosyne-2.2.1,1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   FINISHED

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   FINISHED

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131106133600-52813-222419/py27-mnemosyne-2.2.1,1.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20131106133600-52813
redports https://qat.redports.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

[QAT] r332990: 1x leftovers, 3x finished

dns/knot: update to 1.3.3

- Update to 1.3.3
- Fix pkg-plist

PR: ports/183682
Submitted by:   Leo Vandewoestijne freebsd dns-lab.com (maintainer)
-

  Build ID:  20131106132000-38296
  Job owner: w...@freebsd.org
  Buildtime: 12 hours
  Enddate:   Thu, 07 Nov 2013 01:03:21 GMT

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

-

Port:dns/knot 1.3.3

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   FINISHED

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   FINISHED

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   FINISHED

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131106132000-38296-222415/knot-1.3.3.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20131106132000-38296
redports https://qat.redports.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

[QAT] r333052: 4x leftovers

- Change Makefile header
- Change maintainer email to @FreeBSD.org
- Support STAGEDIR
- Simplify post-extract

Approved by:pawel / wg (mentors, implicit)
-

  Build ID:  20131107025200-2868
  Job owner: nemy...@freebsd.org
  Buildtime: 15 minutes
  Enddate:   Thu, 07 Nov 2013 03:07:20 GMT

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

-

Port:games/krank 07_4

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~nemy...@freebsd.org/20131107025200-2868-222780/krank-07_4.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~nemy...@freebsd.org/20131107025200-2868-222781/krank-07_4.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~nemy...@freebsd.org/20131107025200-2868-222782/krank-07_4.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~nemy...@freebsd.org/20131107025200-2868-222783/krank-07_4.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20131107025200-2868
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: OCaml 4?

2013-11-06 Thread Michael Grünewald

John Marino wrote:
 On 11/6/2013 21:02, Michael Grünewald wrote:
 It seems dports has ocaml 4.00.1 while I prepared a 4.01.0, if you test
 it, your feddback would be welcome!
 
 Surely dports could be updated to ocaml 4.01.0 as easily as changing the
 PORTVERSION and regenerating the distinfo file?

Besides this, there is a minor update of the configure script, you can
get it from

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

or

   https://bitbucket.org/michipili/ports-bsd (branch ocaml)

 As such, the vast majority of dports identical or nearly so to their
 ports counterparts.  At most they contain extra patches or a couple of
 extra switches often contained in Makefile.DragonFly.

That is nice to know, thank you!
-- 
Michael
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

[QAT] r333063: 4x leftovers

Pack your dependencies onto your script file.

WWW: http://search.cpan.org/dist/App-FatPacker/
-

  Build ID:  20131107053800-16048
  Job owner: kuriy...@freebsd.org
  Buildtime: 39 minutes
  Enddate:   Thu, 07 Nov 2013 06:16:55 GMT

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

-

Port:devel/p5-App-FatPacker 0.009018

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~kuriy...@freebsd.org/20131107053800-16048-222852/p5-App-FatPacker-0.009018.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~kuriy...@freebsd.org/20131107053800-16048-222853/p5-App-FatPacker-0.009018.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~kuriy...@freebsd.org/20131107053800-16048-222854/p5-App-FatPacker-0.009018.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~kuriy...@freebsd.org/20131107053800-16048-222855/p5-App-FatPacker-0.009018.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20131107053800-16048
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

hi

2013-11-06 Thread Lotty Vail

HEY JUST WANT TO meet SOME ONE AND TALK AND GET TO KNOW YOU. OKAY Maybe we can 
go riding on my motorcycle. or go out and have a dinner and dancing or what 
ever sound like fun. If you want to know more about me just ask okay. Later
xxryyskyf ttyquwpskb zyliv
edxhf qfflz iopbe
znmuf F O S B R N T U M U K
whnleqngt E Q D W P R D Q F N C I N
___
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] shells/fish compiler error fix, version update

2013-11-06 Thread William MacKay

The shells/fish port has failed to build on FreeBSD 10 for several 
weeks.  It fails with errors like:


./io.h:12:12: error: no member named 'tr1' in namespace 'std'
./io.h:183:39: error: no template named 'shared_ptr'; did you mean 
'std::shared_ptr'?


This patch fixes the error by telling the compiler to use C++11.  It 
also updates fish from version 2.0.0 to version 2.1.0.


The patch is pasted below, or you can find it at 
http://frammish.org/fish-patch.txt.


Will MacKay

diff -u fish-old/Makefile fish-new/Makefile
--- fish-old/Makefile   2013-11-06 23:03:53.690089207 -0800
+++ fish-new/Makefile   2013-11-06 23:28:30.750988987 -0800
@@ -2,7 +2,7 @@
 # $FreeBSD: shells/fish/Makefile 328855 2013-09-30 19:58:20Z bsam $

 PORTNAME=  fish
-PORTVERSION=   2.0.0
+PORTVERSION=   2.1.0
 CATEGORIES=shells
 MASTER_SITES=  http://fishshell.com/files/%SUBDIR%/
 MASTER_SITE_SUBDIR=${PORTVERSION}
@@ -19,7 +19,7 @@
 USE_AUTOTOOLS= autoconf
 CONFIGURE_ARGS=--docdir=${WRKDIR}/tmproot

-CPPFLAGS+= -I${LOCALBASE}/include
+CPPFLAGS+= -I${LOCALBASE}/include -std=c++11
 LDFLAGS+=  -L${LOCALBASE}/lib -pthread ${ICONV_LIB}

 MAN1=  fish.1 fish_indent.1 fish_pager.1 fishd.1 mimedb.1
diff -u fish-old/distinfo fish-new/distinfo
--- fish-old/distinfo   2013-11-06 23:03:53.691088871 -0800
+++ fish-new/distinfo   2013-11-06 23:26:33.274022156 -0800
@@ -1,2 +1,2 @@
-SHA256 (fish-2.0.0.tar.gz) = 
7e4c4a0b3c518769a3d31b235e743de7a8d52f851ad19d2df9d53534e6238303

-SIZE (fish-2.0.0.tar.gz) = 1540652
+SHA256 (fish-2.1.0.tar.gz) = 
af527af9d145df5675ca3031c1a87007d4f4753a1cde49da88f4eb883a1cf044

+SIZE (fish-2.1.0.tar.gz) = 1707921

___
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: OCaml 4?