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

[MacPorts] #28938: tomcat 7
by MacPorts 14 Mar '13

14 Mar '13

#28938: tomcat 7 ---------------------------------+------------------------------------------ Reporter: mikejbond@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: ---------------------------------+------------------------------------------ Would it be possible to add tomcat 7 (latest being 7.0.11) to macports? It's been GA for about six months now and appears to be stable. -- Ticket URL: <https://trac.macports.org/ticket/28938> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 11

[MacPorts] #38387: rust @0.5_3: Build fails on 10.6
by MacPorts 14 Mar '13

14 Mar '13

#38387: rust @0.5_3: Build fails on 10.6 -------------------------+---------------------- Reporter: larryv@… | Owner: larryv@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: snowleopard | Port: rust -------------------------+---------------------- Judging from [https://build.macports.org/builders/buildports-snowleopard- x86_64/builds/15749/steps/compile/logs/stdio the buildbot log], the bundled LLVM is not being configured properly. -- Ticket URL: <https://trac.macports.org/ticket/38387> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #38390: tomcat6 Can we get a tomcat 7
by MacPorts 14 Mar '13

14 Mar '13

#38390: tomcat6 Can we get a tomcat 7 ---------------------+-------------------------------- Reporter: jea@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: ---------------------+-------------------------------- More and more webapps are suggesting/requiring Tomcat 7. Can we get a port for it? We have tomcat6 port and it's great. -- Ticket URL: <https://trac.macports.org/ticket/38390> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

Re: [MacPorts] #14628: sdd fails to build
by MacPorts 14 Mar '13

14 Mar '13

#14628: sdd fails to build --------------------------+-------------------------------- Reporter: wsiegrist@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.0 Resolution: | Keywords: Port: sdd | --------------------------+-------------------------------- Changes (by ryandesign@…): * cc: anthony@…, ryandesign@… (added) Comment: Has duplicate #38384 which shows the same errors on 10.8 as there were on 10.5. I think the first thing we try should be to change the port from using gnumake to using smake, like the error message says. (Programs made by Jörg Schilling seem not to be buildable with a `make` other than the one made by Jörg Schilling: `smake`.) smake is an inconvenient build system that makes us jump through many hoops, and the hoops vary slightly depending on the age of the project. We have a half dozen or so ports in MacPorts already of various ages that use smake, so we should find one that's also from around 2004 and use that as a template for what to do with sdd. -- Ticket URL: <https://trac.macports.org/ticket/14628#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #38384: sdd-1.52 fails to build on osx 10.8.2
by MacPorts 14 Mar '13

14 Mar '13

#38384: sdd-1.52 fails to build on osx 10.8.2 -----------------------+-------------------------------- Reporter: anthony@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: sdd -----------------------+-------------------------------- Errors occur in "port install sdd" <attached log> and also in manual build using smake as per README in build directories. It appears that the platform is not supported in RULES directory and that there are various issues with the source. -- Ticket URL: <https://trac.macports.org/ticket/38384> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #38385: xsltproc: xsl:import : unable to load urn:docbkx:stylesheet
by MacPorts 14 Mar '13

14 Mar '13

#38385: xsltproc: xsl:import : unable to load urn:docbkx:stylesheet -------------------------+-------------------------------- Reporter: anyberry@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: docbook xsl | Port: libxslt -------------------------+-------------------------------- I have a simple custom xsl stylesheet which has this import: <xsl:import href="urn:docbkx:stylesheet"/> (in fact what I'm trying to do is built the maven reference book and the stylesheet is here: https://github.com/sonatype/maven-reference- en/blob/master/epub/epub-custom.xsl) when I run a2x, I get this error: warning: failed to load external entity "urn:docbkx:stylesheet" compilation error: file /Users/rasp/git/maven-reference-en/epub/epub- custom.xsl line 7 element import xsl:import : unable to load urn:docbkx:stylesheet the actual command is: xsltproc --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 --stringparam html.stylesheet "epub/epub-custom.css" --stringparam toc.section.depth 1 --stringparam chunk.section.depth 0 "/Users/rasp/git /maven-reference-en/epub/epub-custom.xsl" "/Users/rasp/git/maven- reference-en/target/book-mvnref.xml" if I run the command without this custom stylesheet, it works properly. I think this is something that should work out of the box - for some reason the standard stylesheet cannot be found during the import. I haven't figured out how to make this work. yes, I saw Ticket #35303 but that says that docbook-xsl should fix such a problem but it doesn't in my case -- Ticket URL: <https://trac.macports.org/ticket/38385> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #38360: subversion-perlbindings: Subports conflict on libsvn_swig_perl-1.0.dylib
by MacPorts 14 Mar '13

14 Mar '13

#38360: subversion-perlbindings: Subports conflict on libsvn_swig_perl-1.0.dylib -------------------------+------------------------------------------------- Reporter: raimue@… | Owner: dluke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: conflicts | Port: subversion-perlbindings subversion- | perlbindings-5.8 subversion-perlbindings-5.10 | subversion-perlbindings-5.12 subversion- | perlbindings-5.14 subversion-perlbindings-5.16 -------------------------+------------------------------------------------- I have subversion-perlbindings-5.16 installed and tried to install git- core +svn, which needs p5.12-svn-simple and that requires subversion- perlbindings-5.12. The installation resulted in the following error: {{{ ---> Activating subversion-perlbindings-5.12 @1.7.8_2 Error: org.macports.activate for port subversion-perlbindings-5.12 returned: Image error: /opt/local/lib/libsvn_swig_perl-1.0.dylib is being used by the active subversion-perlbindings-5.16 port. Please deactivate this port first, or use 'port -f activate subversion-perlbindings-5.12' to force the activation. Error: Failed to install subversion-perlbindings-5.12 }}} It should either be possible to install these ports side-by-side or they need to be marked conflicting. -- Ticket URL: <https://trac.macports.org/ticket/38360> MacPorts <http://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #38241: New port: quassel
by MacPorts 14 Mar '13

14 Mar '13

#38241: New port: quassel -------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: quassel -------------------------+-------------------------------- Port description: Quassel IRC is a modern, cross-platform, distributed IRC client, meaning that one (or multiple) client(s) can attach to and detach from a central core - much like the popular combination of screen and a text-based IRC client such as WeeChat, but graphical. The port has variants for two different flavours of Quassel: * ''monolithic'': Stand-alone version, can be used like any other IRC client. * ''client'': Connects to a remote Quassel core. Both flavours can co-exist alongside each other. By default, only the ''monolithic'' one is built. The ''core'' (server) component of Quassel is not included in this port. I chose not to add a ''kde'' variant because, well, I doubt it makes a lot of sense on OS X. Also, the transitive dependency closure of kdelibs4 is enormous. -- Ticket URL: <https://trac.macports.org/ticket/38241> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #38363: rust @0.5_2 Configure error - build failure
by MacPorts 14 Mar '13

14 Mar '13

#38363: rust @0.5_2 Configure error - build failure ---------------------------------+-------------------------------- Reporter: dougie.richardson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: ---------------------------------+-------------------------------- I tried to install rust 0.5_2 but got a build failure. I'm on OS X 10.8.2 with Xcode 4.6 with the latest command line tools installed (clang is clang-425.0.24). I tried cleaning the rust port and re-building to no avail. Here's what I tried to do: $ sudo port install rust ---> Fetching archive for rust ---> Attempting to fetch rust-0.5_2.darwin_12.x86_64.tbz2 from http://packages.macports.org/rust ---> Attempting to fetch rust-0.5_2.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/rust ---> Attempting to fetch rust-0.5_2.darwin_12.x86_64.tbz2 from http://lil.fr.packages.macports.org/rust ---> Fetching distfiles for rust ---> Verifying checksum(s) for rust ---> Extracting rust ---> Applying patches to rust ---> Configuring rust Error: org.macports.configure for port rust returned: configure failure: command execution failed Please see the log file for port rust for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_rust/rust/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port rust failed -- Ticket URL: <https://trac.macports.org/ticket/38363> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #38289: rust @0.5: upstream only supports newer compilers
by MacPorts 14 Mar '13

14 Mar '13

#38289: rust @0.5: upstream only supports newer compilers ----------------------+-------------------- Reporter: larryv@… | Owner: g5pw@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: rust ----------------------+-------------------- Originally reported in #38279. The [http://static.rust-lang.org/doc/0.5/tutorial.html#getting-started Rust Language Tutorial] claims that compilation requires GCC 4.4 or newer or Clang 3.0 or newer. I’m not sure whether it’s best to blacklist/whitelist compilers based on that documentation, or to just let it be until people start reporting failures. That’s up to you, I guess. One thorn is that Apple’s Clang doesn’t report version numbers like trunk Clang does. So we can’t just blacklist anything “older” than Clang 3.0; the compiler_blacklist_versions PortGroup filters on Clang build number (e.g., 425.0.24). -- Ticket URL: <https://trac.macports.org/ticket/38289> MacPorts <http://www.macports.org/> Ports system for OS X

1 2