December 2015 - macports-tickets - lists.macosforge.org

[MacPorts] #46224: qt4-mac 4.8.6 build failure on Leopard/PowerPC
by MacPorts 08 Oct '16

08 Oct '16

#46224: qt4-mac 4.8.6 build failure on Leopard/PowerPC ------------------------+-------------------------------- Reporter: dgonyier@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: qt4-mac ------------------------+-------------------------------- Build logs attached. -- Ticket URL: <https://trac.macports.org/ticket/46224> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #49203: bacula 7.0.4_1 +client_only +console_bat does not build because it can't find Qt4
by MacPorts 08 Oct '16

08 Oct '16

#49203: bacula 7.0.4_1 +client_only +console_bat does not build because it can't find Qt4 --------------------------------+-------------------------------- Reporter: gullevek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: bacula bat qt4-mac | Port: bacula --------------------------------+-------------------------------- It seems that in this new version the QMAKE and PKG_CONFIG_PATH vars are not carried over into the bacula configure run. It correctly finds + gets the qt4-mac settings, but in the configure from bacula it fails to find QMAKE and Qt4Gui. Qt4-mac was automatically installed into /opt/local/libexec/qt4/ If I add QMAKE='/opt/local/libexec/qt4/bin/qmake' before the QMAKE check and add export PKG_CONFIG_PATH='/opt/local/libexec/qt4/lib/pkgconfig' before the pkg-config check for Qt4 it builds correctly. -- Ticket URL: <https://trac.macports.org/ticket/49203> MacPorts <https://www.macports.org/> Ports system for OS X

1 16

[MacPorts] #46940: Error: org.macports.build for port libgcc returned: command execution failed
by MacPorts 08 Oct '16

08 Oct '16

#46940: Error: org.macports.build for port libgcc returned: command execution failed -------------------------+-------------------------------- Reporter: bri.cales@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: libgcc, gcc | Port: -------------------------+-------------------------------- Hello, I am trying to update my macports by using the commands: sudo port -v selfupdate sudo port upgrade outdated The self update works without errors but when I execute the second command I get this error: Error: org.macports.build for port libgcc returned: command execution failed Please see the log file for port libgcc for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc/main.log Error: Problem while installing libgcc Suggestions? -- Ticket URL: <https://trac.macports.org/ticket/46940> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #47043: Error while Building libgcc
by MacPorts 08 Oct '16

08 Oct '16

#47043: Error while Building libgcc -------------------------+-------------------------------- Reporter: paula.srs@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: -------------------------+-------------------------------- Error: Processing of port libgcc failed The main.log file is in attachment which includes this message: :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc/work/build" && /usr/bin/make -j4 -w bootstrap What can be the problem? Thank you, Paula -- Ticket URL: <https://trac.macports.org/ticket/47043> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #48460: REQ: sshuttle
by MacPorts 07 Oct '16

07 Oct '16

#48460: REQ: sshuttle ----------------------+-------------------------------- Reporter: becker@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ----------------------+-------------------------------- https://github.com/sshuttle/sshuttle Transparent proxy server that works as a poor man's VPN. Forwards over ssh. Doesn't require admin. Supports DNS tunneling. -- Ticket URL: <https://trac.macports.org/ticket/48460> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #49925: KF5 : PortGroup and initial ports (frameworks)
by MacPorts 07 Oct '16

07 Oct '16

#49925: KF5 : PortGroup and initial ports (frameworks) -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: -------------------------+-------------------------------- Here's an initial implementation of a PortGroup and the basic ports required to deploy KF5 through MacPorts, thanks in large part to lots of preliminary heavy lifting behind the scenes by Marko Känig. Without him this would have been much more work. This initial submission contains the PortGroup, the Frameworks, and a few tightly related ports. As always, further development can be followed via https://github.com/RJVB/macstrop/tree/master/kf5 . KDE5 is not a straightforward thing to deploy (package), in some ways even less so than KDE4, but in other ways "things" have improved sufficiently that a lot can be abstracted and automatised (more so than with KDE4). Most of that is done in the PortGroup, which contains the basic logic that makes declaring a port for a given KF5 application relatively easy. It also contains version definitions, because despite being individual packages, KF5 components are released in synchronised fashion, and won't build against older components. The PortGroup is also responsible for including the Qt5 PortGroup, and does so by indicating a preference for `port:qt5-kde`. The frameworks themselves, the building blocks on which KF5 applications are based (and "interesting/useful extensions to Qt5") are a bit different. I have chosen to bundle all frameworks as subports in a single (huge) portfile, in order to increase sharing of patches and reinplace statements (something the benefits of which I hope I won't have to explain). The meta-port is almost complete; it lacks only a number of "porting aid" frameworks which I plan to add when needed (or "in due time"). That meta-port, KF5-Frameworks, also contains the variant that I consider crucial for MacPorts, the one that activates the XDG-compliant mode of Qt's QStandardPaths. In a nutshell, this is the mode in which makes Qt5 (and KF5) code look for shared resources under ${prefix}/share, and use ~/.config, ~/.local and ~/.cache instead of the OS X-ish equivalents. Individual applications (pure Qt5 or KF5) may be adapted or even conceived to use the Apple-equivalents of these locations, but KF5 applications as a whole are designed primarily to function in a Freedesktop (XDG) universe, and cohabit/interact with other XDG-compliant applications that are *not* based on Qt5 (e.g. KDE4!). I consider this something MacPorts cannot ignore or not support. I'd even go so far as to remove the possibility to build KF5 otherwise, but as long as the QSP patch is only shipped with `port:qt5-kde` I see no other way than to provide a variant that becomes a default variant if the QSP/XDG activator is detected at build time. The KF5 PortGroup indicates a preference for `port:qt5-kde` and therefore it is that port which will be installed during a fresh install or on a build bot. I am aware this is a potential violation of the repeatable build principle, but only for/by users who go against a recommended dependency (and these users will be obliged to install all KF5 ports from source). NB: The XDG activator is an additional link module that I bundle with my `port:qt5-kde`; linking it with all KF5 frameworks means that any KF5 application will use QStandardPaths in XDG-compliant mode; this blunt approach is required since there is no single KF5 component with which all dependents are obliged to link. Making the compliancy mode optional (and inactive by default) means that "pure Qt5" applications function with native OS X QStandardPaths, and will thus behave exactly as their counterparts if installed from an official installer other external source. I consider that of equal importance as the repeatable build principle. Also note that there are a number of tweaks that allow me to use the same build and packaging logic on Linux, for testing and comparison; those tend to relax dependencies so they are obtained from the host. I'm not adamant on "getting these in" of course, but as long as I'm principle maintainer on these files I'm also not very keen on removing them . -- Ticket URL: <https://trac.macports.org/ticket/49925> MacPorts <https://www.macports.org/> Ports system for OS X

1 34

[MacPorts] #45690: eblook failed to build on Yosemite
by MacPorts 07 Oct '16

07 Oct '16

#45690: eblook failed to build on Yosemite ------------------------+-------------------------------- Reporter: aruminat@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Keywords: | Port: eblook ------------------------+-------------------------------- With the following error, eblook 1.6.1-media-20110801_0 failed to build with xcode 6.1 on Yosemite: {{{ eblook.c:482:39: error: use of undeclared identifier 'CPPFunction' rl_attempted_completion_function = (CPPFunction *)fileman_completion; ^ eblook.c:482:52: error: expected expression rl_attempted_completion_function = (CPPFunction *)fileman_completion; [snip] eblook.c:4366:8: error: use of undeclared identifier 'CPFunction' (CPFunction *) command_generator); ^ eblook.c:4366:20: error: expected expression (CPFunction *) command_generator); ^ 7 warnings and 4 errors generated. }}} -- Ticket URL: <https://trac.macports.org/ticket/45690> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[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