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

[MacPorts] #36054: Feature request: reload action
by MacPorts 13 Aug '14

13 Aug '14

#36054: Feature request: reload action ----------------------------------+----------------------------------------- Reporter: mailtoarlo@… | Owner: macports-tickets@… Type: request | Status: new Priority: Low | Milestone: Component: base | Version: Keywords: | Port: ----------------------------------+----------------------------------------- When using ports that are started using launchd (e.g. apache2, mysql, php- fpm) the combination of {{{port unload}}} and {{{port load}}} is used to test configuration changes. Sadly typing this is long and cumbersome: {{{ sudo port unload apache2 && sudo port load apache2 }}} I suggest the {{{port reload}}} action that reduces the above to: {{{ sudo port reload apache2 }}} This is a common practice of "similar" commands like [http://manpages.ubuntu.com/manpages/hardy/en/man1/service.1.html service]. -- Ticket URL: <https://trac.macports.org/ticket/36054> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 13

[MacPorts] #37921: RFE: binutils's "notes" entry should specify which ports exactly it causes to fail to build
by MacPorts 13 Aug '14

13 Aug '14

#37921: RFE: binutils's "notes" entry should specify which ports exactly it causes to fail to build -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: binutils -------------------------+-------------------------------- Right now binutils comes with the following "notes" entry in its portfile: {{{ "Having ${name} installed will cause some other ports to\ fail to build. Consider uninstalling ${name}." }}} I'd like to know which ports exactly these are, or at least have a link to a Trac ticket or something, so I can be better informed about whether I should actually follow this advice to uninstall it or not. -- Ticket URL: <https://trac.macports.org/ticket/37921> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #39065: Unable to upgrade Atlas on Snow Leopard 10.6.8
by MacPorts 13 Aug '14

13 Aug '14

#39065: Unable to upgrade Atlas on Snow Leopard 10.6.8 -------------------------+-------------------------------- Reporter: atif.azad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: -------------------------+-------------------------------- Since I am behind a proxy, I ran the following commands (I am running OS X 10.6.8, and Xcode 3.2.6, macport 2.1.3: sudo port -d sync sudo port upgrade outdated ---> Computing dependencies for atlas ---> Building atlas Error: org.macports.build for port atlas returned: command execution failed Please see the log file for port atlas for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_math_atlas/atlas/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets -- Ticket URL: <https://trac.macports.org/ticket/39065> MacPorts <http://www.macports.org/> Ports system for OS X

1 39

[MacPorts] #41037: upgrade libetpan to 1.2
by MacPorts 13 Aug '14

13 Aug '14

#41037: upgrade libetpan to 1.2 ----------------------+-------------------------------- Reporter: perry@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: haspatch | Port: libetpan ----------------------+-------------------------------- libetpan appears to have moved from sourceforge to https://github.com/dinhviethoa/libetpan -- there has also been an update. This patch appears to do the right thing but I would recommend that the maintainer review it and test the result to make sure I didn't do anything wrong. Note also that the patch in files/ is now obsolete and can be removed. -- Ticket URL: <https://trac.macports.org/ticket/41037> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #32077: enforce-variants gtk2 +universal - @MacPorts version 2.03 - error
by MacPorts 13 Aug '14

13 Aug '14

#32077: enforce-variants gtk2 +universal - @MacPorts version 2.03 - error --------------------------------------------------------------------------------------------------------------------------------+ Reporter: adam.clay@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.0.3 Keywords: Scala, sudo port upgrade --enforce-variants gtk2 +universal , sudo port install fontconfig, sudo port install gtk2 | Port: fontconfig, gtk2, (enforce-variants gtk2 +universal) --------------------------------------------------------------------------------------------------------------------------------+ I am trying to install a free program called Scala that requires installation of MacPorts, and the ports "fontconfig" and "gtk2". These two seemed to install correctly from the terminal with the following commands: sudo port install fontconfig sudo port install gtk2 which tells me (if I understand the way MacPorts works) I installed both Macports, and these specific ports correctly. The instructions then ask me to modify my ".profile" file adding this line: export PATH=/opt/local/bin:/opt/local/sbin:$PATH which I did, and then install the libpng 1.4.5 or Combo Installer, which I did. Then, because I have a 64 bit Imac, I was asked to use the following terminal command: sudo port upgrade --enforce-variants gtk2 +universal, and when doing this I got the following error messsage: Error: Target org.macports.build returned: shell command failed (see log for details) Log for p5.12-xml-parser is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5 -xml-parser/p5.12-xml-parser/main.log Error: Unable to upgrade port: 1 Could anyone help me figure out why I cannot do this? -- Ticket URL: <https://trac.macports.org/ticket/32077> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 10

[MacPorts] #41194: vtk-devel: replace by vtk5
by MacPorts 12 Aug '14

12 Aug '14

#41194: vtk-devel: replace by vtk5 --------------------------+----------------------- Reporter: ryandesign@… | Owner: dweber@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: vtk-devel --------------------------+----------------------- Can the vtk-devel port be marked replaced_by vtk5? It appears to be much older than the vtk5 port; it hasn't been updated to a new version in over 4 years (since r58809) whereas vtk5 was updated to the latest available version of vtk5 one year ago (in r99218). -- Ticket URL: <https://trac.macports.org/ticket/41194> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #39300: libpqxx26 conflicts with libpqxx
by MacPorts 12 Aug '14

12 Aug '14

#39300: libpqxx26 conflicts with libpqxx --------------------------+-------------------------------- Reporter: ryandesign@… | Owner: dweber@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: libpqxx26, libpqxx --------------------------+-------------------------------- See summary: {{{ $ sudo port install compiler.blacklist=clang ---> Computing dependencies for libpqxx26 ---> Fetching distfiles for libpqxx26 ---> Verifying checksum(s) for libpqxx26 ---> Extracting libpqxx26 ---> Configuring libpqxx26 ---> Building libpqxx26 ---> Staging libpqxx26 into destroot ---> Installing libpqxx26 @2.6.9_0 ---> Activating libpqxx26 @2.6.9_0 Error: org.macports.activate for port libpqxx26 returned: Image error: /opt/local/bin/pqxx-config is being used by the active libpqxx port. Please deactivate this port first, or use 'port -f activate libpqxx26' to force the activation. Please see the log file for port libpqxx26 for details: /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_databases_libpqxx26/libpqxx26/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port libpqxx26 failed }}} The ports either should not conflict, or should indicate that they do. -- Ticket URL: <https://trac.macports.org/ticket/39300> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #39299: libpqxx26 build fails with clang due to -Werror
by MacPorts 12 Aug '14

12 Aug '14

#39299: libpqxx26 build fails with clang due to -Werror --------------------------+----------------------- Reporter: ryandesign@… | Owner: dweber@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: libpqxx26 --------------------------+----------------------- Building libpqxx26 fails with clang because the configure script uses `-Werror` and also something that clang doesn't recommend. {{{ checking ability to compile programs using the standard C library... configure: error: Could not build even a tiny test program using the standard C library. Something very basic has gone wrong; try reading config.log to find out what. You'll probably want to go straight to the end of that file and read backwards until you find an error message. Then identify the problem, try to fix it, and run this script again. The configure script's --help option may provide useful tips on how to influence what compiler and command line options are used, what additional libraries are linked in, and so on. }}} config.log says: {{{ configure:20712: checking ability to compile programs using the standard C library configure:20737: /usr/bin/clang++ -c -pipe -Os -arch x86_64 -Werror -I/opt/local/include conftest.cpp >&5 conftest.cpp:32:18: error: using directive refers to implicitly-defined namespace 'std' [-Werror] using namespace std; ^ 1 error generated. }}} I guess the best fix is to remove `-Werror` in those places. -- Ticket URL: <https://trac.macports.org/ticket/39299> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #39359: Cableswig @latest build failure
by MacPorts 12 Aug '14

12 Aug '14

#39359: Cableswig @latest build failure -----------------------+-------------------------------- Reporter: stephen@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: cableswig | Port: cableswig -----------------------+-------------------------------- Error msg + log link: {{{ ---> Building cableswig Error: org.macports.build for port cableswig returned: command execution failed Please see the log file for port cableswig for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_cableswig/cableswig/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port cableswig failed }}} [https://www.dropbox.com/s/1n8ckoh1utfx0gc/cableswig.log] -- Ticket URL: <https://trac.macports.org/ticket/39359> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #39361: cableswig @20090521_0: does not use the right compiler
by MacPorts 12 Aug '14

12 Aug '14

#39361: cableswig @20090521_0: does not use the right compiler ----------------------+----------------------- Reporter: larryv@… | Owner: dweber@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: cableswig ----------------------+----------------------- As can be seen in the [[attachment:main.log:ticket:39359|log file for #39359]], cableswig does not [[UsingTheRightCompiler|use the right compiler]], instead using `/usr/bin/cc` throughout. -- Ticket URL: <https://trac.macports.org/ticket/39361> MacPorts <http://www.macports.org/> Ports system for OS X

1 1