May 2013 - macports-tickets - lists.macosforge.org

[MacPorts] #34436: fetchmail config scripts on wiki out of date
by MacPorts 14 Jun '14

14 Jun '14

#34436: fetchmail config scripts on wiki out of date ----------------------------------+----------------------------------------- Reporter: bentley@… | Owner: macports-tickets@… Type: update | Status: new Priority: Low | Milestone: Component: wiki | Version: 2.0.4 Keywords: fetchmail doc | Port: ----------------------------------+----------------------------------------- The configuration scripts provided by the wiki to help configure the macports install for fetchmail do not appear to work. The primary reason appears to be that the BSD commands as used have changed since the instructions were written, so the scripts fail on execution. I was able to execute lines one at a time after checking to see how the command really needed to be written. (I eventually stopped following the wiki instructions altogether as I wasn't sure any of it would work.) I'm using 10.6.8 on a mini 1.66 GHz core duo with 2 GB. https://trac.macports.org/wiki/howto/SetupFetchmail -- Ticket URL: <https://trac.macports.org/ticket/34436> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #39220: p5-io-kqueue: update to 0.34
by MacPorts 13 Jun '14

13 Jun '14

#39220: p5-io-kqueue: update to 0.34 --------------------------+-------------------------- Reporter: ryandesign@… | Owner: pmq@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: p5-io-kqueue --------------------------+-------------------------- {{{ $ port livecheck p5-io-kqueue p5-io-kqueue seems to have been updated (port version: 0.32, new version: 0.34) }}} -- Ticket URL: <https://trac.macports.org/ticket/39220> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #39040: gnupod Portfile patch
by MacPorts 13 Jun '14

13 Jun '14

#39040: gnupod Portfile patch ---------------------+-------------------------------- Reporter: david@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: gnupod ---------------------+-------------------------------- Current portfile is broken, as it still uses the non-pure-perl version of vorbis perl. There are also many perl5.12 dependencies, rather than p5 (virtual) dependencies. The attached Portfile addresses the following: 1) gnupod will no build 2) changed all perl5.12 references to p5, to use whatever version of perl is selected One outstanding bug still exists. Using depends_lib-append port:p5-ogg-vorbis-header-pureperl somehow fires a p5.12 dependency. The brute force fix I uses was port:p5.16-ogg-vorbis-header-pureperl and is better fixed "the right way". So if the maintainer knows "the right way", please supply another patch to p5-ogg-vorbis-header-pureperl to fix this. Thanks. -- Ticket URL: <https://trac.macports.org/ticket/39040> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #38483: frozenbubble2: build for the right architectures
by MacPorts 13 Jun '14

13 Jun '14

#38483: frozenbubble2: build for the right architectures --------------------------+--------------------------- Reporter: ryandesign@… | Owner: pmq@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: frozenbubble2 --------------------------+--------------------------- frozenbubble2 does not build for the architecture requested in macports.conf. Here is an example of what happens if you try to install frozenbubble2 for i386 on an x86_64 Mac. -- Ticket URL: <https://trac.macports.org/ticket/38483> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #38346: gnupod: noarch
by MacPorts 13 Jun '14

13 Jun '14

#38346: gnupod: noarch --------------------------+-------------------- Reporter: ryandesign@… | Owner: pmq@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: gnupod --------------------------+-------------------- gnupod doesn't install any architecture-specific files that I can see. So it needs: {{{ supported_archs noarch }}} -- Ticket URL: <https://trac.macports.org/ticket/38346> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #38345: gnupod: fix variants
by MacPorts 13 Jun '14

13 Jun '14

#38345: gnupod: fix variants --------------------------+-------------------- Reporter: ryandesign@… | Owner: pmq@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: gnupod --------------------------+-------------------- The gnupod port has variants that only add dependencies: {{{ # should also use timidity variant flac description "Enable FLAC" { depends_lib-append port:flac port:p5.12-audio-flac-header } # should use Ogg::Vorbis::Header::PurePerl, won't work variant vorbis description "Enable Ogg/Vorbis" { depends_lib-append port:vorbis-tools port:p5.12-libvorbis-perl } variant aac description "Enable AAC" { depends_lib-append port:faac path:lib/libavcodec.dylib:ffmpeg } variant artwork description "Enable artwork support" { depends_lib-append port:ImageMagick } }}} The port needs to be updated to ensure that those dependencies will ''not'' be used if those variants are ''not'' selected, even if those ports are already installed. -- Ticket URL: <https://trac.macports.org/ticket/38345> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #38086: fragrouter@1.6 not installing
by MacPorts 13 Jun '14

13 Jun '14

#38086: fragrouter(a)1.6 not installing -------------------------------+-------------------------------- Reporter: turbominicooper@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: fragrouter -------------------------------+-------------------------------- cooper$ sudo port install fragrouter Password: ---> Computing dependencies for fragrouter ---> Building fragrouter Error: org.macports.build for port fragrouter returned: command execution failed Please see the log file for port fragrouter for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_fragrouter/fragrouter/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port fragrouter failed -- Ticket URL: <https://trac.macports.org/ticket/38086> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #38002: kedpm @0.4.1-cvs_1 segfaults on startup
by MacPorts 13 Jun '14

13 Jun '14

#38002: kedpm @0.4.1-cvs_1 segfaults on startup -------------------------+-------------------------------- Reporter: sewebster@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: kedpm -------------------------+-------------------------------- When I run kedpm, it segfaults. This is for the default gtk frontend. Starting it in CLI mode also fails, because it can't find readline, but I think that is unrelated, possibly a separate bug. I'm attaching the console output as well as the text from the Apple crash report. -- Ticket URL: <https://trac.macports.org/ticket/38002> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #37541: iperf @2.0.5 - configure failure: command execution failed
by MacPorts 13 Jun '14

13 Jun '14

#37541: iperf @2.0.5 - configure failure: command execution failed -------------------------+-------------------------------- Reporter: jimnieken@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: iperf | Port: iperf -------------------------+-------------------------------- iperf fails to build? I guess? Output from ports and from the log file bash-3.2$ sudo port install iperf ---> Configuring iperf Error: org.macports.configure for port iperf returned: configure failure: command execution failed Please see the log file for port iperf for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_iperf/iperf/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port iperf failed bash-3.2$ bash-3.2$ tail /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_iperf/iperf/main.log :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_iperf/iperf/work/iperf-2.0.5" && ./configure --prefix=/opt/local :info:configure Exit code: 1 :error:configure org.macports.configure for port iperf returned: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed while executing "$procedure $targetname" :info:configure Warning: targets not executed for iperf: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install :notice:configure Please see the log file for port iperf for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_iperf/iperf/main.log -- Ticket URL: <https://trac.macports.org/ticket/37541> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #36984: fetchmail - BUG in libdispatch client - ML 10.8.2
by MacPorts 13 Jun '14

13 Jun '14

#36984: fetchmail - BUG in libdispatch client - ML 10.8.2 -----------------------+-------------------------------- Reporter: srothe@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: fetchmail | Port: fetchmail -----------------------+-------------------------------- I installed fetchmail using mac ports. But everytime I start fetchmail (SSL included), I receive the following message in /var/log/mail.log [...] BUG in libdispatch client: Do not close random Unix descriptors [...] I have compiled the latest fetchmail version by myself, but I receive the same message. Fetchmail itself works, but what does it means? Thanks Soeren -- Ticket URL: <https://trac.macports.org/ticket/36984> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 12