April 2016 - macports-tickets - lists.macosforge.org

[MacPorts] #50655: openvpn2 @2.3.8_0 Unable to launch
by MacPorts 06 Oct '16

06 Oct '16

#50655: openvpn2 @2.3.8_0 Unable to launch ----------------------+-------------------------------- Reporter: kolbcp@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ----------------------+-------------------------------- I initially do and see the following: {{{ $ cd /Library/LaunchDaemons $ sudo launchctl load -w org.macports.openvpn2.plist $ tail -f /var/log/system.log Feb 17 10:51:17 xxx com.apple.xpc.launchd[1] (org.macports.openvpn2): The Debug key is no longer respected. Please remove it. Feb 17 10:51:17 xxx com.apple.xpc.launchd[1] (org.macports.openvpn2): This service is defined to be constantly running and is inherently inefficient. Feb 17 10:51:17 xxx com.apple.xpc.launchd[1] (org.macports.openvpn2): Service only ran for 0 seconds. Pushing respawn out by 10 seconds. Feb 17 10:51:47 --- last message repeated 2 times --- Feb 17 10:51:47 xxx com.apple.xpc.launchd[1] (org.macports.openvpn2): Service only ran for 0 seconds. Pushing respawn out by 10 seconds. ... }}} This fails to launch openvpn2. Next I try the following: {{{ $ sudo launchctl unload -w org.macports.openvpn2.plist $ cat org.macports.openvpn2.plist <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd" > <plist version='1.0'> <dict> <key>Label</key><string>org.macports.openvpn2</string> <key>ProgramArguments</key> <array> <string>/opt/local/bin/daemondo</string> <string>--label=openvpn2</string> <string>--start-cmd</string> <string>/opt/local/sbin/openvpn2 --config /opt/local/etc/openvpn2/server.conf</string> <string>;</string> <string>--pid=exec</string> </array> <key>Debug</key><false/> <key>Disabled</key><true/> <key>KeepAlive</key><true/> </dict> </plist> $ sudo /opt/local/sbin/openvpn2 --config /opt/local/etc/openvpn2/server.conf }}} This launches openvpn2 and I am able to connect with an openvpn2 client. Next I try the following: {{{ $ sudo sh -c "cat > org.macports.openvpn2.test.plist" << END <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd" > <plist version='1.0'> <dict> <key>Label</key><string>org.macports.openvpn2</string> <key>ProgramArguments</key> <array> <string>/opt/local/sbin/openvpn2</string> <string>--config</string> <string>/opt/local/etc/openvpn2/server.conf</string> </array> <key>RunAtLoad</key> <true/> </dict> </plist> END $ sudo launchctl load -w org.macports.openvpn2.test.plist }}} This also launches openvpn2 and I am able to connect with an openvpn2 client. So... I can launch openvpn2 from the command line using the very same arguments that daemondo uses to start openvpn2. I can launch openvpn2 via daemondo from the command line using the very same arguments that the launchd.plist file uses to launch daemondo. I can create a launch.plist file that launches openvpn2 directly. But the launchd.plist file that comes with the openvpn2 port that uses daemondo to launch openvpn2 is not working. This is all on a freshly [within the last 24 hours] installed [not upgraded] OS X [not OS X Server] 10.11 El Capitan system. On of our two OS X [Server] 10.8 Mountain Lion systems the same launchd.plist file launches daemondo/openvpn2 without issue. I have no experience with Mavericks or Yosemite as we are moving from Mountain Lion directly to El Capitan. I did not find anything at macports.org or via Google that might help me with this. Any light a that can be shed on this would be appreciated. -- Ticket URL: <https://trac.macports.org/ticket/50655> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #49630: new (sub)port: dbusmenu-qt5
by MacPorts 06 Oct '16

06 Oct '16

#49630: new (sub)port: dbusmenu-qt5 -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: dbusmenu-qt -------------------------+-------------------------------- dbusmenu-qt exists in a version supporting Qt5, but for now only in bzr . The attached patch introduces a subport that builds dbusmenu-qt5. port:dbusmenu-qt includes the kde4 PortGroup, probably out of convenience. Since there is no dependency on KDE code, I have preferred to use only the Qt5 and cmake Portgroups. -- Ticket URL: <https://trac.macports.org/ticket/49630> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #49657: Incorrect behaviour of --append-verify (and --partial) options
by MacPorts 06 Oct '16

06 Oct '16

#49657: Incorrect behaviour of --append-verify (and --partial) options --------------------------+-------------------------------- Reporter: swordangel@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: rsync --------------------------+-------------------------------- OS X 10.11.1 El Capitan rsync version: 3.1.1 I seem to have discovered a nasty bug with the `--append-verify` (and `--partial`) options of rsync. As far as I can understand, the whole point of `--append-verify` is that in case of interruption, rsync will leave the destination file in its current state so that it can be resumed at a later point. Consider, for example: - source volume: "`/Volume/DyingHDD`" - destination volume: "`/Volume/NewHDD`" Suppose I have a 2 GB file "`/Volume/DyingHDD/00027.MTS`" and my DyingHDD is really dying: its read speed has degraded to around 5 MB/s and it's so unstable that it can't read 10 GB without suddenly going offline (OS X would think that it has not been ejected cleanly). So I try to salvage whatever is on DyingHDD by doing "`rsync -av --append- verify --timeout=60 /Volume/DyingHDD/ /Volume/NewHDD/`". Now, a few hundred MBs into 00027.MTS, DyingHDD suddenly disappears. I would expect rsync to leave "`/Volume/NewHDD/00027.MTS`" at the few hundred MB mark and quit. But that's not what happened. Instead, rsync proceeded to fill "`/Volume/NewHDD/00027.MTS`" '''all the way to 2 GB''' at the '''full speed''' of NewHDD (about 150 MB/s), and leave its timestamp at the current system time. Output of rsync: {{{ 00027.MTS 2,125,627,392 100% 29.94MB/s 0:01:07 (xfr#11, ir-chk=1083/66263) }}} So the next time I call "`rsync -av --append-verify --timeout=60 /Volume/DyingHDD/ /Volume/NewHDD/`", rsync just '''skips over''' 00027.MTS. `--partial` has a similar behaviour I somewhat doubt it's a general bug in rsync exists in all platforms. All of the Linux people that I have spoken to say that `--append-verify` does leave the file in its partial state on Linux. -- Ticket URL: <https://trac.macports.org/ticket/49657> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #48905: New port: syncthing
by MacPorts 06 Oct '16

06 Oct '16

#48905: New port: syncthing ---------------------------+-------------------------------- Reporter: link.dupont@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: syncthing ---------------------------+-------------------------------- Open source continuous file synchronization application Syncthing replaces proprietary sync and cloud services with something open, trustworthy and decentralized. Your data is your data alone and you deserve to choose where it is stored, if it is shared with some third party and how it's transmitted over the Internet. http://syncthing.net -- Ticket URL: <https://trac.macports.org/ticket/48905> MacPorts <https://www.macports.org/> Ports system for OS X

1 14

[MacPorts] #49575: py27-awscli @1.7.22_1 should depend on py27-docutils
by MacPorts 04 Oct '16

04 Oct '16

#49575: py27-awscli @1.7.22_1 should depend on py27-docutils --------------------+-------------------------------- Reporter: ben@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: py27-awscli --------------------+-------------------------------- Installing py27-awscli @1.7.22_1 and running `aws` yields this output: {{{ Traceback (most recent call last): File "/opt/local/bin/aws", line 19, in <module> import awscli.clidriver File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/awscli/clidriver.py", line 30, in <module> from awscli.help import ProviderHelpCommand File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/awscli/help.py", line 19, in <module> from docutils.core import publish_string ImportError: No module named docutils.core }}} After `port install py27-docutils`, the output is: {{{ usage: aws [options] <command> <subcommand> [parameters] aws: error: too few arguments }}} So it appears that py27-awscli ought to depend on py27-docutils. -- Ticket URL: <https://trac.macports.org/ticket/49575> MacPorts <https://www.macports.org/> Ports system for OS X

1 8

[MacPorts] #45832: defect: policykit 0.112_1 cannot be built on PPC Tiger and Leopard because it needs Clang 3.4 which cannot be built
by MacPorts 02 Oct '16

02 Oct '16

#45832: defect: policykit 0.112_1 cannot be built on PPC Tiger and Leopard because it needs Clang 3.4 which cannot be built -----------------------------+-------------------------------- Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: policykit -----------------------------+-------------------------------- See [44320]. This must be a defect inside the Portfile, because {{{ port info policykit }}} mentions {{{ Build Dependencies: pkgconfig, intltool, gtk-doc, autoconf, automake, libtool Library Dependencies: glib2, gobject-introspection, mozjs17 }}} and no Clang – although I have no idea what mozjs17 might me. Part of *some* Firefox? I have installed on PPC Mac OS X 10.5.8, Leopard: {{{ port installed | egrep 'pkgconfig|intltool|gtk- doc|autoconf|automake|libtool|glib2|gobject- introspection|mozjs17|gcc|clang|llvm' autoconf @2.69_2 (active) autoconf213 @2.13_1 (active) automake @1.14.1_2 (active) cctools @806_3+llvm33 (active) clang-3.3 @3.3_5+analyzer+python27 (active) clang_select @1.0_0 (active) gcc48 @4.8.3_0 gcc48 @4.8.3_1 (active) gcc49 @4.9.1_0 (active) gcc_select @0.1_8 (active) gccmakedep @1.0.3_0 (active) glib2 @2.42.0_1 (active) gobject-introspection @1.42.0_0 (active) gtk-doc @1.21_1 (active) intltool @0.50.2_3+perl5_16 (active) ld64 @97.17_3+llvm31 (active) libgcc @4.9.1_0 libgcc @4.9.1_1 (active) libtool @2.4.2_5 (active) llvm-3.1 @3.1_8 (active) llvm-3.3 @3.3_4 (active) llvm-3.4 @3.4.2_0 (active) llvm_select @1.0_0 (active) pkgconfig @0.28_0 (active) }}} -- Ticket URL: <https://trac.macports.org/ticket/45832> MacPorts <https://www.macports.org/> Ports system for OS X

1 24

[MacPorts] #47764: Ghostscript 9.16 does not build on PPC Tiger (Mac OS X 10.4.11) because of prototype
by MacPorts 02 Oct '16

02 Oct '16

#47764: Ghostscript 9.16 does not build on PPC Tiger (Mac OS X 10.4.11) because of prototype -----------------------------+-------------------------------- Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: ghostscript -----------------------------+-------------------------------- {{{ /opt/local/bin/gcc-apple-4.2 -DHAVE_MKSTEMP -DHAVE_FSEEKO -DHAVE_FONTCONFIG -DHAVE_LIBIDN -DHAVE_SETLOCALE -DHAVE_BSWAP32 -DHAVE_STRERROR -DHAVE_PREAD_PWRITE=1 -DGS_RECURSIVE_MUTEXATTR=PTHREAD_MUTEX_RECURSIVE -O2 -isystem/opt/local/include -Wall -Wstrict-prototypes -Wundef -Wmissing- declarations -Wmissing-prototypes -Wwrite-strings -Wno-strict-aliasing -Werror=declaration-after-statement -fno-builtin -fno-common -Werror =return-type -DHAVE_STDINT_H=1 -DHAVE_DIRENT_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMES_H=1 -DHAVE_INTTYPES_H=1 -DGX_COLOR_INDEX_TYPE="unsigned long long" -D__USE_UNIX98=1 -D"strnlen(a,b)=strlen(a)" -pipe -Os -arch ppc -DUSE_LIBICONV_GNU -DUSE_LIBPAPER -I/opt/local/include -I./soobj -I./base -I./devices -DWHICH_CMS="lcms2" -I./trio -o ./soobj/gssprintf_0.o -c ./base/gssprintf.c In file included from ./trio/trio.h:35, from ./base/gssprintf.c:19: ./trio/triop.h:407: error: type qualifiers ignored on function return type make[2]: *** [soobj/gssprintf_0.o] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.16' }}} The error happens with a patched version of Portfile which does not allow the use of Clang/llvm 3.3; Clang/llvm 3.4 are installed. -- Ticket URL: <https://trac.macports.org/ticket/47764> MacPorts <https://www.macports.org/> Ports system for OS X

1 8

[MacPorts] #50342: doxygen @1.8.10_2 does not build on PPC Tiger, Mac OS X 10.4.11, because of Python code error?
by MacPorts 02 Oct '16

02 Oct '16

#50342: doxygen @1.8.10_2 does not build on PPC Tiger, Mac OS X 10.4.11, because of Python code error? -----------------------------+-------------------------------- Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: doxygen -----------------------------+-------------------------------- {{{ :info:build [ 27%] Generating ../generated_src/ce_parse.h :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10/generated_src && /opt/local/bin/bison -l -d -p ce_parsexpYY /opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10/src/constexp.y -o ce_parse.c :info:build [ 28%] Generating /opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10/generated_src/resources.cpp :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10/src && /opt/local/bin/python /opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10/src/res2cc_cmd.py /opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10/templates /opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10/generated_src/resources.cpp :info:build File "/opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10/src/res2cc_cmd.py", line 40 :info:build print("static const unsigned char %s_data[] = " % self.bareName,file=outputFile) :info:build ^ :info:build SyntaxError: invalid syntax :info:build make[2]: *** [generated_src/resources.cpp] Error 1 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10' :info:build make[1]: *** [src/CMakeFiles/_doxygen.dir/all] Error 2 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_lil.fr.rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.10" && /usr/bin/make -w all VERBOSE=ON :info:build Exit code: 2 :error:build org.macports.build for port doxygen returned: command execution failed }}} -- Ticket URL: <https://trac.macports.org/ticket/50342> MacPorts <https://www.macports.org/> Ports system for OS X

1 13

[MacPorts] #48454: babl @0.1.12 build failure (codegen)
by MacPorts 01 Oct '16

01 Oct '16

#48454: babl @0.1.12 build failure (codegen) ----------------------+-------------------------------- Reporter: ghajek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: babl ----------------------+-------------------------------- OS X 10.5, PPC. Full log attached. This followed a 'port -fp uninstall installed' and reinstall, so everything else is current. {{{ :info:build ld warning: codegen with reference kind 17 in _babl_init prevents image from loading in dyld shared cache :info:build ld warning: codegen with reference kind 14 in _babl_init prevents image from loading in dyld shared cache :info:build ld warning: codegen with reference kind 14 in _babl_init prevents image from loading in dyld shared cache :info:build ld warning: codegen with reference kind 17 in _babl_exit prevents image from loading in dyld shared cache [rinse, lather, repeat] :info:build ld: absolute addressing (perhaps -mdynamic-no-pic) used in _babl_init from .libs/babl.o not allowed in slidable image. Use '-read_only_relocs suppress' to enable text relocs :info:build collect2: ld returned 1 exit status :info:build clang: error: linker (via gcc) command failed with exit code 1 (use -v to see invocation) :info:build make[3]: *** [libbabl-0.1.la] Error 1 [etc.] :error:build org.macports.build for port babl returned: command execution failed :debug:build Error code: CHILDSTATUS 97056 2 }}} -- Ticket URL: <https://trac.macports.org/ticket/48454> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #46132: openjade fails to build on OSX Lion
by MacPorts 30 Sep '16

30 Sep '16

#46132: openjade fails to build on OSX Lion -----------------------------+-------------------------------- Reporter: pilgrimaflame@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: openjade | Port: openjade -----------------------------+-------------------------------- openjade fails to build on OSX Lion, with Xcode 4.2.1 installed. I get the following error code output in Terminal. {{{ #!div style="font-size: 80%" Code highlighting: {{{#!python ---> Building openjade Error: org.macports.build for port openjade returned: command execution failed }}} }}} -- Ticket URL: <https://trac.macports.org/ticket/46132> MacPorts <https://www.macports.org/> Ports system for OS X

1 11