poudriere + soundkonverter build fails
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. Thanks Wolfgang___ 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
Is it or isn't it installed? (It is, but ports tries to again, doomed to fail.)
TLDR; check lines prefixed with ? in the transcript below. Ran into this over a couple weeks ago. Checked again with last night's portsnap, same problem, same ports. Figured I ought to pipe up about it. Seems like a good ol' classic mystery. I don't know if it's just one instance of a general problem in the way dependencies get detected and dispatched to be installed, maybe just in the python infrastructure, a bug in the net/py-kombu port (which my eyes couldn't find a problem with), or what. I looked into it for an hour before punting with a trivial workaround and moving on, didn't think much of it at the time, figuring it was just one of those temporary problems smarter minds are already hard at work fixing. Apparently they weren't or didn't. This time I'm using a squeaky clean new amd64 9.2-RELEASE-p1 system (empty /usr/local then installing all ports from the same snapshot of /usr/ports). ***How to reproduce: Just happen to already have the dependency devel/py-boto (py27-boto-2.14.0) or devel/py-pyzmq (py27-pyzmq-2.2.0) installed (and their port dirs since cleaned up) when you try to install net/py-kombu (py27-kombu-3.0.1) from ports with BOTO and/or ZMQ options. (In my case I have all its options on.) ***Transcripts: (attention to lines prefixed with ? and !) === Installing for py27-kombu-3.0.1 === py27-kombu-3.0.1 depends on package: py27-amqp=1.3.1 - found === py27-kombu-3.0.1 depends on package: py27-anyjson=0.3.3 - found === py27-kombu-3.0.1 depends on package: py27-beanstalkc0 - found ?=== py27-kombu-3.0.1 depends on package: py27-boto=2.6.0 - not found ===Verifying install for py27-boto=2.6.0 in /usr/ports/devel/py-boto === Installing for py27-boto-2.14.0 === py27-boto-2.14.0 depends on file: /usr/local/bin/easy_install-2.7 - found === py27-boto-2.14.0 depends on file: /usr/local/bin/python2.7 - found === py27-boto-2.14.0 depends on executable: python - found === py27-boto-2.14.0 depends on executable: python2 - found === Generating temporary packing list === Checking if devel/py-boto already installed ?=== py27-boto-2.14.0 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/py-boto without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/devel/py-boto. *** [run-depends] Error code 1 Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # === Installing for py27-kombu-3.0.1 === py27-kombu-3.0.1 depends on package: py27-amqp=1.3.1 - found === py27-kombu-3.0.1 depends on package: py27-anyjson=0.3.3 - found === py27-kombu-3.0.1 depends on package: py27-beanstalkc0 - found !=== py27-kombu-3.0.1 depends on package: py27-boto=2.6.0 - not found !===Verifying install for py27-boto=2.6.0 in /usr/ports/devel/py-boto !=== Returning to build of py27-kombu-3.0.1 === py27-kombu-3.0.1 depends on package: pymongo0 - found === py27-kombu-3.0.1 depends on package: py27-sqlalchemy0 - found ?=== py27-kombu-3.0.1 depends on package: py27-pyzmq=2.2.0 - not found ===Verifying install for py27-pyzmq=2.2.0 in /usr/ports/devel/py-pyzmq === Installing for py27-pyzmq-2.2.0 === py27-pyzmq-2.2.0 depends on file: /usr/local/bin/python2.7 - found === py27-pyzmq-2.2.0 depends on executable: python - found === py27-pyzmq-2.2.0 depends on shared library: zmq.1 - found === Generating temporary packing list === Checking if devel/py-pyzmq already installed ?=== py27-pyzmq-2.2.0 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/py-pyzmq without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/devel/py-pyzmq. *** [run-depends] Error code 1 Stop in /usr/ports/net/py-kombu. *** [install] Error code 1 Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # ___ 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
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. 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 Regards, 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: Is it or isn't it installed? (It is, but ports tries to again, doomed to fail.)
Try again. On Tue, Nov 5, 2013 at 11:55 AM, Chad J. Milios mil...@ccsys.com wrote: TLDR; check lines prefixed with ? in the transcript below. Ran into this over a couple weeks ago. Checked again with last night's portsnap, same problem, same ports. Figured I ought to pipe up about it. Seems like a good ol' classic mystery. I don't know if it's just one instance of a general problem in the way dependencies get detected and dispatched to be installed, maybe just in the python infrastructure, a bug in the net/py-kombu port (which my eyes couldn't find a problem with), or what. I looked into it for an hour before punting with a trivial workaround and moving on, didn't think much of it at the time, figuring it was just one of those temporary problems smarter minds are already hard at work fixing. Apparently they weren't or didn't. This time I'm using a squeaky clean new amd64 9.2-RELEASE-p1 system (empty /usr/local then installing all ports from the same snapshot of /usr/ports). ***How to reproduce: Just happen to already have the dependency devel/py-boto (py27-boto-2.14.0) or devel/py-pyzmq (py27-pyzmq-2.2.0) installed (and their port dirs since cleaned up) when you try to install net/py-kombu (py27-kombu-3.0.1) from ports with BOTO and/or ZMQ options. (In my case I have all its options on.) ***Transcripts: (attention to lines prefixed with ? and !) === Installing for py27-kombu-3.0.1 === py27-kombu-3.0.1 depends on package: py27-amqp=1.3.1 - found === py27-kombu-3.0.1 depends on package: py27-anyjson=0.3.3 - found === py27-kombu-3.0.1 depends on package: py27-beanstalkc0 - found ?=== py27-kombu-3.0.1 depends on package: py27-boto=2.6.0 - not found ===Verifying install for py27-boto=2.6.0 in /usr/ports/devel/py-boto === Installing for py27-boto-2.14.0 === py27-boto-2.14.0 depends on file: /usr/local/bin/easy_install-2.7 - found === py27-boto-2.14.0 depends on file: /usr/local/bin/python2.7 - found === py27-boto-2.14.0 depends on executable: python - found === py27-boto-2.14.0 depends on executable: python2 - found === Generating temporary packing list === Checking if devel/py-boto already installed ?=== py27-boto-2.14.0 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/py-boto without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/devel/py-boto. *** [run-depends] Error code 1 Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # === Installing for py27-kombu-3.0.1 === py27-kombu-3.0.1 depends on package: py27-amqp=1.3.1 - found === py27-kombu-3.0.1 depends on package: py27-anyjson=0.3.3 - found === py27-kombu-3.0.1 depends on package: py27-beanstalkc0 - found !=== py27-kombu-3.0.1 depends on package: py27-boto=2.6.0 - not found !===Verifying install for py27-boto=2.6.0 in /usr/ports/devel/py-boto !=== Returning to build of py27-kombu-3.0.1 === py27-kombu-3.0.1 depends on package: pymongo0 - found === py27-kombu-3.0.1 depends on package: py27-sqlalchemy0 - found ?=== py27-kombu-3.0.1 depends on package: py27-pyzmq=2.2.0 - not found ===Verifying install for py27-pyzmq=2.2.0 in /usr/ports/devel/py-pyzmq === Installing for py27-pyzmq-2.2.0 === py27-pyzmq-2.2.0 depends on file: /usr/local/bin/python2.7 - found === py27-pyzmq-2.2.0 depends on executable: python - found === py27-pyzmq-2.2.0 depends on shared library: zmq.1 - found === Generating temporary packing list === Checking if devel/py-pyzmq already installed ?=== py27-pyzmq-2.2.0 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/py-pyzmq without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/devel/py-pyzmq. *** [run-depends] Error code 1 Stop in /usr/ports/net/py-kombu. *** [install] Error code 1 Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # -- 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
Re: FreeBSD Port: petsc-2.3.3.p0_7,1
On 10/20/13, Guillaume DOLLÉ dolle.guilla...@gmail.com wrote: Would it possible to update Petsc to version 3.4.3 ? Create a new port for slepc-3.4.3 (extension for petsc) could be also nice. Thank in advance. Yes, both are on my todo list, as soon as I finish some other pending updates. b. ___ 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: Is it or isn't it installed? (It is, but ports tries to again, doomed to fail.)
On 05/11/2013 14:55, Chad J. Milios wrote: TLDR; check lines prefixed with ? in the transcript below. Ran into this over a couple weeks ago. Checked again with last night's portsnap, same problem, same ports. Figured I ought to pipe up about it. Seems like a good ol' classic mystery. I don't know if it's just one instance of a general problem in the way dependencies get detected and dispatched to be installed, maybe just in the python infrastructure, a bug in the net/py-kombu port (which my eyes couldn't find a problem with), or what. I looked into it for an hour before punting with a trivial workaround and moving on, didn't think much of it at the time, figuring it was just one of those temporary problems smarter minds are already hard at work fixing. Apparently they weren't or didn't. This time I'm using a squeaky clean new amd64 9.2-RELEASE-p1 system (empty /usr/local then installing all ports from the same snapshot of /usr/ports). ***How to reproduce: Just happen to already have the dependency devel/py-boto (py27-boto-2.14.0) or devel/py-pyzmq (py27-pyzmq-2.2.0) installed (and their port dirs since cleaned up) when you try to install net/py-kombu (py27-kombu-3.0.1) from ports with BOTO and/or ZMQ options. (In my case I have all its options on.) ... === Checking if devel/py-boto already installed ?=== py27-boto-2.14.0 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/py-boto without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/devel/py-boto. *** [run-depends] Error code 1 Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # ... Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # That looks like the dependencies in net/py-kombu are broken. I.e. they refer to files that are not/no longer installed by the dependencies. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Is it or isn't it installed? (It is, but ports tries to again, doomed to fail.)
On Tue, Nov 5, 2013 at 2:09 PM, Dominic Fandrey kamik...@bsdforen.de wrote: On 05/11/2013 14:55, Chad J. Milios wrote: TLDR; check lines prefixed with ? in the transcript below. Ran into this over a couple weeks ago. Checked again with last night's portsnap, same problem, same ports. Figured I ought to pipe up about it. Seems like a good ol' classic mystery. I don't know if it's just one instance of a general problem in the way dependencies get detected and dispatched to be installed, maybe just in the python infrastructure, a bug in the net/py-kombu port (which my eyes couldn't find a problem with), or what. I looked into it for an hour before punting with a trivial workaround and moving on, didn't think much of it at the time, figuring it was just one of those temporary problems smarter minds are already hard at work fixing. Apparently they weren't or didn't. This time I'm using a squeaky clean new amd64 9.2-RELEASE-p1 system (empty /usr/local then installing all ports from the same snapshot of /usr/ports). ***How to reproduce: Just happen to already have the dependency devel/py-boto (py27-boto-2.14.0) or devel/py-pyzmq (py27-pyzmq-2.2.0) installed (and their port dirs since cleaned up) when you try to install net/py-kombu (py27-kombu-3.0.1) from ports with BOTO and/or ZMQ options. (In my case I have all its options on.) ... === Checking if devel/py-boto already installed ?=== py27-boto-2.14.0 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/py-boto without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/devel/py-boto. *** [run-depends] Error code 1 Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # ... Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # That looks like the dependencies in net/py-kombu are broken. I.e. they refer to files that are not/no longer installed by the dependencies. Did you get my email asking to try again after the last port update fixing the dependencies? -- 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
Re: how to set SGID?
Larry Rosenman l...@lerctr.org wrote: I got a PR about sysutils/lsof not getting installed sgid kmem. I'm surprised. It doesn't even build right now. I'm not sure with all the new staging stuff (sunpoet did it for me) how to fix it. What's the incantation I need? The best way is to set special owner/group/permissions in pkg-plist, like this: ... @group kmem @mode 2755 sbin/lsof @mode @group ... Of course you have chosen not to have a pkg-plist. At the moment, the port requires NEED_ROOT=yes, so that (1) do-install succeeds and (2) the sgid information is picked up and put into the package archive. I've already committed the NEED_ROOT=yes addition. -- Christian naddy Weisgerber na...@mips.inka.de ___ 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: cinepaint
Hello! There is good news. After some investigations I found solve. I sent my report to FreeBSD-gnats ( http://www.freebsd.org/cgi/query-pr.cgi?pr=183691). In attachment you can see patches for source files. If you do not complicate, test them. 2013/11/2 Fernando Apesteguía fernando.apesteg...@gmail.com El 01/11/2013 18:53, Alexander Janus avjw...@gmail.com escribió: In my experiment I installed cinepaint and all other soft from packages repository under VirtualBox and FreeBSD 9.2 AMD64 Release. I've got the same results: Segmentation fault. I just recompile glib20 with debugging symbols, and get new backtrace: #0 0x000805b3a5ce in type_node_check_conformities_UorL (node=0x80b3c9280, iface_node=0xc3faf00, support_interfaces=1, support_prerequisites=0, have_lock=0) at gtype.c:3467 3467 if (/* support_inheritance */ [New Thread 80b007400 (LWP 100813/cinepaint)] (gdb) bt #0 0x000805b3a5ce in type_node_check_conformities_UorL (node=0x80b3c9280, iface_node=0xc3faf00, support_interfaces=1, support_prerequisites=0, have_lock=0) at gtype.c:3467 #1 0x000805b3a8bf in type_node_conforms_to_U (node=0x80b3c9280, iface_node=0xc3faf00, support_interfaces=1, support_prerequisites=0) at gtype.c:3513 #2 0x000805b3b460 in g_type_check_instance_is_a ( type_instance=0x80b39e350, iface_type=205500160) at gtype.c:3999 #3 0x004f26f1 in brush_select_new (title=0x0, init_name=0x0, init_opacity=0, init_spacing=0, init_noise_freq=0.25, init_noise_step_start=0.5, init_noise_step_width=0.5, init_mode=0) at brush_select.c:554 #4 0x00426611 in create_brush_dialog () at brushlist.c:520 #5 0x004a79e6 in layout_restore () at layout.c:180 #6 0x0041b823 in gimp_init (gimp_argc=0, gimp_argv=0x7fffdab0) at app_procs.c:212 #7 0x004ab667 in init () at main.c:537 #8 0x0048edd9 in install_verify (install_callback=0x4ab5c0 init) at install.c:83 #9 0x004ab5a0 in main (argc=1, argv=0x7fffdaa8) at main.c:482 Is this indicates about bug in glib on the only 64-bit systems? I saw a discussion of this problem in NetBSD forum. it looks like. 2013/11/1 Fernando Apesteguía fernando.apesteg...@gmail.com On Thu, Oct 31, 2013 at 7:02 PM, Alexander Janus avjw...@gmail.com wrote: Backtrace without debug information: #0 0x000805a50b5b in g_type_check_instance_is_a () from /usr/local/lib/libgobject-2.0.so.0 [New Thread 80b007400 (LWP 100668/cinepaint)] (gdb) bt #0 0x000805a50b5b in g_type_check_instance_is_a () from /usr/local/lib/libgobject-2.0.so.0 #1 0x004b6f99 in display_brush_get_row_float16 () #2 0x00422b0c in ?? () #3 0x0047fe67 in ?? () #4 0x0041c2f5 in ?? () #5 0x00483346 in ?? () #6 0x0046f767 in ?? () #7 0x00482f4d in ?? () #8 0x004199e1 in ?? () #9 0x0008007bf000 in ?? () #10 0x in ?? () Backtrace with debug information (make WITH_DEBUG=yes install): #0 0x000805adeb5b in g_type_check_instance_is_a () from /usr/local/lib/libgobject-2.0.so.0 [New Thread 80b007400 (LWP 100354/cinepaint)] (gdb) bt #0 0x000805adeb5b in g_type_check_instance_is_a () from /usr/local/lib/libgobject-2.0.so.0 #1 0x004f26f1 in brush_select_new (title=0x0, init_name=0x0, init_opacity=0, init_spacing=0, init_noise_freq=0.25, init_noise_step_start=0.5, init_noise_step_width=0.5, init_mode=0) at brush_select.c:554 #2 0x00426611 in create_brush_dialog () at brushlist.c:520 #3 0x004a79e6 in layout_restore () at layout.c:180 #4 0x0041b823 in gimp_init (gimp_argc=0, gimp_argv=0x7fffdab0) at app_procs.c:212 #5 0x004ab667 in init () at main.c:537 #6 0x0048edd9 in install_verify (install_callback=0x4ab5c0 init) at install.c:83 #7 0x004ab5a0 in main (argc=1, argv=0x7fffdaa8) at main.c:482 I don't see much there. g_type_check_instance_is_a should have two parameters but they are not shown in the backtrace. I googled a while and it seems there are other packages (gedit, gimp) that suffer from similar bugs. The offending line seems to be this one inside g_type_check_instance_is_a_ node = lookup_type_node_I (type_instance-g_class-g_type); Is your glib installed from binary or did you build it yourself? If the case is the latter, I would try to use the one in the repositories just in case. Cheers. 2013/10/31 Fernando Apesteguía fernando.apesteg...@gmail.com El 30/10/2013 19:36, Alexander Janus avjw...@gmail.com escribió: Good day, Dear Sirs! Help me, please. I build cinepaint port on my FreeBSD 9.2 release AMD64 desktop , build was successfull, but launch causes Segmentation fault. Ok, I pkg_add -r cinepaint, and I again get
I'm having conflicts with pkg pkg_ and portmaster .
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. 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. 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
Re: problems after installing ports-mgmt/portconf
On Sat, Oct 12, 2013 at 11:58 PM, Eitan Adler li...@eitanadler.com wrote: On Sat, Oct 12, 2013 at 11:43 AM, Matthias Apitz g...@unixarea.de wrote: El día Friday, October 11, 2013 a las 06:16:23PM -0500, Matthew D. Fuller escribió: On Fri, Oct 11, 2013 at 09:37:13AM +0200 I heard the voice of Matthias Apitz, and lo! it spake thus: I have had to uninstall portconf again to be able to build more ports. Near's I can tell, portconf and bmake just flat out don't get along. With some squirreling around in make.conf, you can make _that_ warning shut up, but you just wind up with a different one for ports that you have portconf stuff for. I stopped investigating at that point :| Maybe my English is poor, I do not understand your message. Please clarify. Thx Translation: bmake and portconf are not compatible. Once you fix the couldn't read shell's output error, there are others. I've submitted a dirty hack for ports-mgmt/portconf as ports/183104. It works fine on my box. HTH Regards, sunpoet -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
pkg install subversion broken on 9.2-R...
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. -- 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: pkg install subversion broken on 9.2-R...
On Wed, Nov 6, 2013 at 6:54 AM, John-Mark Gurney j...@funkthat.com 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. Pkg doesn't know that those conflicting packages are different versions of the same software, it only knows that there is a conflict between them. The solution to this requires a change at ports level. -Kimmo ___ 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
