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

[MacPorts] #50544: dnscrypt-proxy @1.6.0_2: update to 1.6.1
by MacPorts 04 Feb '16

04 Feb '16

#50544: dnscrypt-proxy @1.6.0_2: update to 1.6.1 ---------------------------------+-------------------------------- Reporter: mschamschula@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: haspatch maintainer | Port: dnscrypt-proxy ---------------------------------+-------------------------------- dnscrypt-proxy has been updated to version 1.6.1. -- Ticket URL: <https://trac.macports.org/ticket/50544> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #50530: Malformed packets could cause the OpenDNS deviceid, OpenDNS set-client-ip, blocking and AAAA blocking plugins to use uninitialized pointers, leading to a denial of service or possibly code execution.
by MacPorts 04 Feb '16

04 Feb '16

#50530: Malformed packets could cause the OpenDNS deviceid, OpenDNS set-client-ip, blocking and AAAA blocking plugins to use uninitialized pointers, leading to a denial of service or possibly code execution. ------------------------------------+-------------------------------- Reporter: gavin@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.4 Keywords: Security Vulnerability | Port: dnscrypt-proxy ------------------------------------+-------------------------------- According to (https://github.com/jedisct1/dnscrypt- proxy/releases/tag/1.6.1) Malformed packets could cause the OpenDNS deviceid, OpenDNS set-client-ip, blocking and AAAA blocking plugins to use uninitialized pointers, leading to a denial of service or possibly code execution. The vulnerable code is present since dnscrypt-proxy 1.1.0. OpenDNS users and people using dnscrypt-proxy in order to block domain names and IP addresses should upgrade as soon as possible. Please update the port when possible. Thanks. -- Ticket URL: <https://trac.macports.org/ticket/50530> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #50538: bacula install fails with clang errors
by MacPorts 04 Feb '16

04 Feb '16

#50538: bacula install fails with clang errors ---------------------------+-------------------------------- Reporter: smccandlish@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: bacula ---------------------------+-------------------------------- I attempted to install bacula (7.0.4_1) with -client_only option (might also happen without that option), on Mac OS 10.10.5. Did not work. Log file has misc. errors relating to clan, ac_nonexistent.h and confdefs.h, all of which are basically gibberish to me. -- Ticket URL: <https://trac.macports.org/ticket/50538> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #50531: Error synchronizing MacPorts sources on MacOSX 10.11.3
by MacPorts 04 Feb '16

04 Feb '16

#50531: Error synchronizing MacPorts sources on MacOSX 10.11.3 -------------------------------------------------+------------------------- Reporter: hmaldonado1@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Keywords: Error synchronizing MacPorts | Version: 2.3.4 sources | Port: port -------------------------------------------------+------------------------- ====== Issue ====== hectors-Mac-mini:~ hector$ sudo port -v selfupdate ---> Updating MacPorts base sources using rsync rsync: read error: Operation timed out (60) rsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/io.c(604) [receiver=2.6.9] Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit code: 12 Error: Error synchronizing MacPorts sources: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed ====== Additional Information ====== Mac OS X 10.11.3 -Firewall Turned Off -TCPHandshake PSH,ACK only hectors-Mac-mini:~ hector$ sudo port -v MacPorts 2.3.4 hectors-Mac-mini:~ hector$ xcode-select --install xcode-select: error: command line tools are already installed, use "Software Update" to install updates hectors-Mac-mini:~ hector$ cat .profile # MacPorts Installer addition on 2016-02-03_at_11:14:28: adding an appropriate PATH variable for use with MacPorts. export PATH="/opt/local/bin:/opt/local/sbin:$PATH" # Finished adapting your PATH environment variable for use with MacPorts. hectors-Mac-mini:~ hector$ uname -a Darwin hectors-Mac-mini.local 15.3.0 Darwin Kernel Version 15.3.0: Thu Dec 10 18:40:58 PST 2015; root:xnu-3248.30.4~1/RELEASE_X86_64 x86_64 hectors-Mac-mini:~ hector$ gcc --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 7.0.2 (clang-700.1.81) Target: x86_64-apple-darwin15.3.0 Thread model: posix * * * Fresh install of Mac OS X 10.11.3, base installation plush Mac Ports * * * -- Ticket URL: <https://trac.macports.org/ticket/50531> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #50527: 'sudo port clean' fails
by MacPorts 04 Feb '16

04 Feb '16

#50527: 'sudo port clean' fails ----------------------+-------------------------------- Reporter: bmayer@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ----------------------+-------------------------------- I was performing a 'upgrade outdated' and ran into the issue: $ time sudo port upgrade outdated Password: ---> Computing dependencies for qwt61 Error: Unable to exec port: Can't install qwt61 because conflicting ports are active: qwt52 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets The next step is to do a 'sudo port clean' as near as I can tell, but that appears to have confused itself. $ sudo port clean Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/xok"). Please verify that the directory and portfile syntax are correct. To use the current port, you must be in a port's directory. -- Ticket URL: <https://trac.macports.org/ticket/50527> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

Re: [MacPorts] #28793: Qxt
by MacPorts 04 Feb '16

04 Feb '16

#28793: Qxt -------------------------+-------------------------------- Reporter: gabriele@… | Owner: macports-tickets@… Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: wontfix | Keywords: Port: | -------------------------+-------------------------------- Changes (by jmr@…): * status: new => closed * resolution: => wontfix Comment: No response to comment:1, and this appears to no longer be maintained upstream. -- Ticket URL: <https://trac.macports.org/ticket/28793#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #48114: cccc-3.1.4 fails to build
by MacPorts 04 Feb '16

04 Feb '16

#48114: cccc-3.1.4 fails to build ----------------------------------------+-------------------------------- Reporter: schmieder.matthias@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.3 Keywords: yosemite,erase,Xcode 6.3.2 | Port: cccc ----------------------------------------+-------------------------------- Hi, just tried to install cccc an my MacBook Pro with Yosemite installed but it failed. The log output brings up the following error message {{{ ./cccc_tbl.cc:99:7: error: use of undeclared identifier 'erase' erase(value_iterator); ^ this-> }}} tracing the error down I found a missing scope in said function. '''cccc_tbl.cpp:92''' {{{ template<class T> bool CCCC_Table<T>::remove(T* old_item_ptr) { bool retval=false; typename map_t::iterator value_iterator=map_t::find(old_item_ptr->key()); if(value_iterator!=map_t::end()) { erase(value_iterator); retval=true; } return retval; } }}} changing '''cccc_tbl.cpp:99''' to {{{ map_t::erase(value_iterator); }}} fixed to problem. I added to log file as well as a patch file to this ticket. BR Matthias -- Ticket URL: <https://trac.macports.org/ticket/48114> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #50528: logwatch: build fails on all buildbots during activation
by MacPorts 04 Feb '16

04 Feb '16

#50528: logwatch: build fails on all buildbots during activation ----------------------------+-------------------------- Reporter: devans@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: 2.3.4 Keywords: | Port: logwatch ----------------------------+-------------------------- Fails during activation as follows: {{{ Error: org.macports.activate for port logwatch returned: Image error: /opt/local/bin/logwatch already exists and does not belong to a registered port. Unable to activate port logwatch. Use 'port -f activate logwatch' to force the activation. DEBUG: Error code: registry::image-error DEBUG: Backtrace: Image error: /opt/local/bin/logwatch already exists and does not belong to a registered port. Unable to activate port logwatch. Use 'port -f activate logwatch' to force the activation. }}} I'm guessing this is a copy installed as part of the buildbot infrastructure? If so perhaps this should be installed in a different location such as /usr/local. -- Ticket URL: <https://trac.macports.org/ticket/50528> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #50529: chromaprint fails checksum test
by MacPorts 04 Feb '16

04 Feb '16

#50529: chromaprint fails checksum test -------------------------------+-------------------------------- Reporter: barry.j.mcinnes@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: chromaprint | Port: chromaprint -------------------------------+-------------------------------- {{ On 10.11.3 after macports self update and port clean chromaprint, gives checksum error on download. debug log attached. }} -- Ticket URL: <https://trac.macports.org/ticket/50529> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #50058: Executables installed by pip are not linked into macports path (and are not “select”able in any way).
by MacPorts 03 Feb '16

03 Feb '16

#50058: Executables installed by pip are not linked into macports path (and are not “select”able in any way). -----------------------+-------------------------------- Reporter: william@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: pip -----------------------+-------------------------------- There's some prior discussion of this problem at https://github.com/pypa/pip/issues/113 In short: when I install a python package using pip, its executables are installed into the appropriately versioned python tree, but those executables are not symlinked to somewhere which is on my PATH. In my example, I have installed macports' pip, and have `port select`ed `python35` and `pip35`. I then used pip to install the aws cli tools, `sudo pip install aws`. The `aws` binary is installed by `pip` at `/opt/local/Library/Frameworks/Python.framework/Versions/3.5/bin/aws`. So far so good. The problem is that that path is not on my `PATH` (of course … `port select` can't alter my path, only the individual symlinks in `/opt/local/bin` to the objects which are owned by that particular port for which `port select` was run). I would naively expect at first glance that issuing a `sudo port select pip pip35` would cause any binaries ''subsequently'' installed by that version of pip to be linked into my macports path `/opt/local/bin`. Of course that doean't happen with a standard `pip`. There follows the question of how to achieve this, since standard `pip` doesn't know it's supposed to do something about any binaries installed /after/ the `port select` operation, other than to install them in the appropriate place in the python heirarchy for the selected version of `pip`. This puts the question firmly in MacPorts' world, as per the latest comments on the github issue. Beporter's comment (third from last in that github issue at the time of writing) echos my feeling here … I would expect that something installed with the currently selected version of pip would end up on my path, though I completely understand why it doesn't at present. There's clearly some precedent for linking binaries to do with a specific python version directly in this way, since for example idle is linked thus on my installation, so the desired end result (I end up with a link `/opt/local/bin/aws -> /opt/local/Library/Frameworks/Python.framework/Versions/3.5/bin/aws`) would be consistent with this: {{{ idle -> /opt/local/bin/idle3.5 idle2.7 -> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/idle2.7 idle3 -> /opt/local/bin/idle3.5 idle3.4 -> /opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/idle3.4 idle3.5 -> /opt/local/Library/Frameworks/Python.framework/Versions/3.5/bin/idle3.5 }}} One way to achieve this (the “best” that I can think of so far) would be to modify MacPorts' `pip` so that when a given version of `pip` installs a binary it also links that into `/opt/local/bin`. This shouldn't be too hard to achieve but it's pretty invasive w.r.t. `pip`'s behaviour. It would, though, solve the oddness seen by me and others leading to `pip`-installed executables not appearing on my path. The `port select pip pipXX` command would also need on each invocation either to invoke `pip` or examine `pip`'s registry in order to unlink the executables which were installed by the version of `pip` being deselected, and link those owned by the version of `pip` being selected. Not rocket science, but a bit complicated. The alternative would seem to be to provide stub ports of some sort which use `pip` as the installation method under the hood but which handle the symlinking by providing `port select` machinery for each such port. That feels like a maintenance drag though (keeping up with `pip`'s repositories …) (Footnote: I can see that there's an existing port `py-awscli` which should provide what I need for now specifically in my example `aws` case, though it's pretty outdated, but that doesn't negate the general point about `pip` and paths in this bug …) -- Ticket URL: <https://trac.macports.org/ticket/50058> MacPorts <https://www.macports.org/> Ports system for OS X

1 6