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

[MacPorts] #46837: kerberos5 fails to build on 10.4ppc
by MacPorts 20 Aug '16

20 Aug '16

#46837: kerberos5 fails to build on 10.4ppc -------------------------+-------------------------------- Reporter: dsmithhfx@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: Tiger, ppc | Port: kerberos5 -------------------------+-------------------------------- Hi, I've tried this a couple of ways: "sudo port install kerberos5", and "sudo port install kerberos5 configure.compiler=apple-gcc-4.2", both failed during build. I scanned the log but can't figure out where the problem is. Port version 2.3.3. Tiger 10.4.11 G5ppc Attaching log (clang build) Thanks -- Ticket URL: <https://trac.macports.org/ticket/46837> MacPorts <https://www.macports.org/> Ports system for OS X

1 11

[MacPorts] #46701: kerberos5 does not build on PPC Tiger, Mac OS X 10.4.11, because void value cannot be ignored as it ought to be
by MacPorts 20 Aug '16

20 Aug '16

#46701: kerberos5 does not build on PPC Tiger, Mac OS X 10.4.11, because void value cannot be ignored as it ought to be -----------------------------+-------------------------------- Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: kerberos5 -----------------------------+-------------------------------- {{{ /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -DGET_TGT_VIA_PASSWD -DPRINC_LOOK_AHEAD -DCMD_PATH='"/bin /local/bin"' -I../../include -I../../include -DKRB5_DEPRECATED=1 -DKRB5_PRIVATE -I/opt/local/include -pipe -Os -arch ppc -fno-common -Wall -Wcast-align -Wshadow -Wmissing-prototypes -Wno- format-zero-length -Wmissing-format-attribute -Wmissing-prototypes -Wreturn-type -Wmissing-braces -Wparentheses -Wswitch -Wunused-function -Wunused-label -Wunused-variable -Wunused-value -Wunknown-pragmas -Wsign- compare -Wnewline-eof -Wdeclaration-after-statement -Werror-implicit- function-declaration -c main.c main.c: In function ‘get_configured_defccname’: main.c:818: error: void value not ignored as it ought to be make[2]: *** [main.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_net_kerberos5/kerberos5/work/krb5-1.13-final/src/clients/ksu' }}} -- Ticket URL: <https://trac.macports.org/ticket/46701> MacPorts <https://www.macports.org/> Ports system for OS X

1 16

[MacPorts] #51679: yum-createrepo @0.9.8_2 The createrepo command fails after installation
by MacPorts 19 Aug '16

19 Aug '16

#51679: yum-createrepo @0.9.8_2 The createrepo command fails after installation ------------------------+-------------------------------- Reporter: aszostak@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: yum-createrepo ------------------------+-------------------------------- The createrepo command fails to run after a fresh install of the yum- createrepo port. See the error message below: {{{ macosx-10-9:~ vagrant$ createrepo --help Traceback (most recent call last): File "/opt/local/share/createrepo/genpkgmetadata.py", line 28, in <module> import createrepo File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/createrepo/__init__.py", line 22, in <module> import yumbased File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/createrepo/yumbased.py", line 19, in <module> import rpm ImportError: No module named rpm }}} This is likely related to ticket #51678. -- Ticket URL: <https://trac.macports.org/ticket/51679> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #51678: yum @3.2.29_1 Cannot import yum module in python after install
by MacPorts 19 Aug '16

19 Aug '16

#51678: yum @3.2.29_1 Cannot import yum module in python after install ------------------------+-------------------------------- Reporter: aszostak@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: yum ------------------------+-------------------------------- I would expect that after installing the yum port that I should be able to import the module within python. However this fails. See below: {{{ macosx-10-9:~ vagrant$ sudo port install yum ---> Computing dependencies for yum ... ---> Cleaning yum ---> Scanning binaries for linking errors ---> No broken files found. macosx-10-9:~ vagrant$ which python /opt/local/bin/python macosx-10-9:~ vagrant$ python Python 2.7.11 (default, Mar 1 2016, 18:08:21) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import yum Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named yum >>> }}} It appears that the yum port installs the module under: {{{ /opt/local/lib/python/site-packages }}} rather than the following path where all other python 2.7 packages appear to be installed: {{{ /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages }}} -- Ticket URL: <https://trac.macports.org/ticket/51678> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #51528: openvpn2: passwordsave variant
by MacPorts 19 Aug '16

19 Aug '16

#51528: openvpn2: passwordsave variant -------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: openvpn2 -------------------------+-------------------------------- Some OpenVPN servers (particular Sophos UTM and Mikrotik) are configured to authenticate with a user/password combination either in addition to or instead of the TLS certificate. By default openvpn2 requires the user to enter this username/password on the console ''every time the VPN starts''. For [https://openvpn.net/archive/openvpn-users/2004-10/msg00418.html about 10 years] openvpn2 has had an option to load these details from a file instead of entering them on the console on each run ("auth-user-pass FILENAME"). However [https://openvpn.net/index.php/open- source/documentation/install.html?start=1 to use this feature openvpn2 must be built with "--enable-password-save"]. Without that configure time option (eg, default MacPorts), trying to use this feature results in: {{{ Tue May 31 15:41:05 2016 Sorry, 'Auth' password cannot be read from a file }}} The attached trivial patch adds a variant "+passwordsave" which enables compiling with "--enable-password-save": {{{ ewen@ashram:/usr/local/ports$ port variants openvpn2 openvpn2 has the variants: passwordsave: Build with --enable-password-save universal: Build for multiple architectures ewen@ashram:/usr/local/ports$ }}} After [https://guide.macports.org/chunked/development.local- repositories.html configuring for local ports], the patched version of the Portfile was tested with: {{{ portindex -f sudo port install -k openvpn2 +passwordsave }}} and then "auth-user-pass FILENAME" works. (To reduce the security risk the referenced file with the username/password should be "chmod +400" or similar, and ideally the password should ''only'' be used for the VPN credentials (as it is stored in plain text); I'm not sure how strictly OpenVPN checks the file permissions.) Obviously this is not ideal for a shared system, and so it should not be the default. But on a single-user workstation, interacting frequently with VPN servers that rely on the client storing the VPN credentials, it might be an acceptable tradeoff. Please consider merging this patch to add the optional variant, so MacPort users have the option of enabling this feature if it is appropriate for their environment. Ewen -- Ticket URL: <https://trac.macports.org/ticket/51528> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #49326: snort @2.9.7.6: Unknown pidfile style /opt/local/var/run/snort_en1.pid presented to startupitem.pidfile
by MacPorts 19 Aug '16

19 Aug '16

#49326: snort @2.9.7.6: Unknown pidfile style /opt/local/var/run/snort_en1.pid presented to startupitem.pidfile --------------------------+----------------------- Reporter: ryandesign@… | Owner: jul_bsd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: snort --------------------------+----------------------- snort uses the `startupitem.pidfile` variable incorrectly: {{{ ---> Computing dependencies for snort ---> Fetching distfiles for snort ---> Attempting to fetch snort-2.9.7.6.tar.gz from https://www.snort.org/downloads/snort/ ---> Verifying checksums for snort ---> Extracting snort ---> Configuring snort ---> Building snort ---> Staging snort into destroot ---> Creating launchd control script Error: ---> Unknown pidfile style /opt/local/var/run/snort_en1.pid presented to startupitem.pidfile ########################################################### # A startup item has been generated that will aid in # starting snort with launchd. It is disabled # by default. Execute the following command to start it, # and to cause it to launch at startup: # # sudo port load snort ########################################################### ---> Installing snort @2.9.7.6_0+mysql56+universal ---> Cleaning snort ---> Computing dependencies for snort ---> Deactivating snort @2.9.7.3_0+mysql56+universal ---> Activating snort @2.9.7.6_0+mysql56+universal ---> Cleaning snort ---> Uninstalling snort @2.9.7.3_0+mysql56+universal }}} You need to specify who creates the pidfile and who cleans it up. See https://guide.macports.org/#reference.startupitems.script Also, does `--create-pidfile` need to be added to `startupitem.executable`? -- Ticket URL: <https://trac.macports.org/ticket/49326> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #46320: net/snort: missing rules files from default snort.conf
by MacPorts 19 Aug '16

19 Aug '16

#46320: net/snort: missing rules files from default snort.conf -----------------------+----------------------- Reporter: pixilla@… | Owner: jul_bsd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: snort -----------------------+----------------------- {{{ $ snort -T -c /opt/local/etc/snort/snort.conf 2>&1 | tail -n3 ERROR: /opt/local/etc/snort//rules/local.rules(0) Unable to open rules file "/opt/local/etc/snort//rules/local.rules": No such file or directory. Fatal Error, Quitting.. }}} -- Ticket URL: <https://trac.macports.org/ticket/46320> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #51588: Macports port install keybase dependency gnupg fails
by MacPorts 19 Aug '16

19 Aug '16

#51588: Macports port install keybase dependency gnupg fails ------------------------------+-------------------------------- Reporter: gurlinthewurld@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: keybase, gnupg | Port: gnupg ------------------------------+-------------------------------- I have been trying to install keybase on my OSX external dev drive. It fails to install gnupg. I ran ```sudo port clean gnupg ``` and ```sudo port -v install gnupg ``` and then to get the details ```cat /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/main.log``` Is this an issue with my drive's paths? My other ports seem to be fine, and I selfupdate regularly. Thanks in advance. {{{ :info:configure config.status: executing po-directories commands :info:configure config.status: creating po/POTFILES :info:configure config.status: creating po/Makefile :info:configure :info:configure Version info: gnupg 1.4.20 :info:configure Configured for: Darwin (x86_64 -apple-darwin15.5.0) :info:configure :debug:configure Privilege de-escalation not attempted as not running as root. :debug:build build phase started at Thu Jun 9 13:11:22 EDT 2016 :notice:build ---> Building gnupg :debug:build Executing org.macports.build (gnupg) :debug:build Environment: CC_PRINT_OPTIONS='YES' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/.CC_PRINT_OPTIONS' CPATH='/opt/local/include' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.11' :debug:build Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/gnupg-1.4.20" && /usr/bin/make -j4 -w all' :debug:build Executing command line: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/gnupg-1.4.20" && /usr/bin/make -j4 -w all :info:build make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/gnupg-1.4.20' :info:build /Volumes/Macintosh HD/Applications/Xcode.app/Contents/Developer/usr/bin/make all-recursive :info:build make: /Volumes/Macintosh: No such file or directory :info:build make: *** [all] Error 1 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/gnupg-1.4.20' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/work/gnupg-1.4.20" && /usr/bin/make -j4 -w all :info:build Exit code: 2 :error:build org.macports.build for port gnupg returned: command execution failed :debug:build Error code: CHILDSTATUS 12774 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "portbuild::build_main org.macports.build" ("eval" body line 1) invoked from within "eval $procedure $targetname" :info:build Warning: targets not executed for gnupg: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port gnupg for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_gnupg/gnupg/main.log }}} -- Ticket URL: <https://trac.macports.org/ticket/51588> MacPorts <https://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #48579: libsodium: use release download
by MacPorts 18 Aug '16

18 Aug '16

#48579: libsodium: use release download --------------------------+------------------------ Reporter: ryandesign@… | Owner: stromnov@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: haspatch | Port: libsodium --------------------------+------------------------ The libsodium developers offer a release download, so the port should use it instead of the automatically generated download. This should eliminate the need to run autogen.sh. However, since this would result in yet another nearly identical tarball being downloaded for this version, it would be best to wait to commit this until it can be combined with the next version update of this port. -- Ticket URL: <https://trac.macports.org/ticket/48579> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #50312: `task` @2.5.0_0 build error
by MacPorts 18 Aug '16

18 Aug '16

#50312: `task` @2.5.0_0 build error -------------------------+-------------------------------- Reporter: starkhalo@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: task -------------------------+-------------------------------- -- Ticket URL: <https://trac.macports.org/ticket/50312> MacPorts <https://www.macports.org/> Ports system for OS X

1 5