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

[MacPorts] #36522: commons-daemon java 1.7 mountain lion fails
by MacPorts 01 Oct '14

01 Oct '14

#36522: commons-daemon java 1.7 mountain lion fails -----------------------------+-------------------------------- Reporter: eamonn.kearns@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: -----------------------------+-------------------------------- The build process looks for jni_md.h in /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/include but it is located in /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/include/darwin I am not sure how to resolve this properly, but I hacked it by cping the files up one level. -- Ticket URL: <https://trac.macports.org/ticket/36522> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #39194: slimdata @2.6.5 fails to link
by MacPorts 01 Oct '14

01 Oct '14

#39194: slimdata @2.6.5 fails to link -----------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: slimdata -----------------------------+-------------------------------- slimdata fails to build. I guess the problem is here: {{{ [...] /usr/bin/g++-4.0 -pipe -O2 -arch i386 -O3 -Wall -fPIC -I/opt/local/include -I../include -I. -DPACKAGE_NAME=\"slim\" -DPACKAGE_TARNAME=\"slim\" -DPACKAGE_VERSION=\"v2_6_5\" -DPACKAGE_STRING=\"slim\ v2_6_5\" -DPACKAGE_BUGREPORT=\"jfowler(a)princeton.edu\" -DPACKAGE_URL=\"\" -DHAVE_LIBM=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UTIME_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_UTIME_H=1 -DHAVE_UTIME_NULL=1 -DHAVE_MEMSET=1 -DHAVE_SQRT=1 -DHAVE_STRCHR=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 -DHAVE_UTIME=1 -L/opt/local/lib -arch i386 -fPIC -L../lib -shared -Wl,-dylib_install_name -Wl,libslim.so.0 -o ../lib/libslim.so.0.0 bit_constants.o bitstream.o raw_section.o slim_channel.o slim_codec_constant.o slim_codec_default.o slim_codec_factory.o slim_codec_runlength.o slim_codec_reduced_binary.o slim_control.o slim_exceptions.o slim_file.o slimlib.o -lm Undefined symbols: "_main", referenced from: start in crt1.10.5.o ld: symbol(s) not found collect2: ld returned 1 exit status [...] }}} The complete main.log is attached. I build on a Mac OS X 10.5.8 machine. Xcode 3.1.4 Component versions: DevToolsCore-1204.0; DevToolsSupport-1186.0 BuildVersion: 9M2809 -- Ticket URL: <https://trac.macports.org/ticket/39194> MacPorts <http://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #36410: Qt applications are blurry on MBP Retina
by MacPorts 01 Oct '14

01 Oct '14

#36410: Qt applications are blurry on MBP Retina ----------------------------------+-------------------------------- Reporter: mail.pourri@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: qt kde retina blurry | Port: qt4 ----------------------------------+-------------------------------- The applications using Qt (all KDE apps) are not rendering correctly on a MacBookPro with Retina screen. The text is blurry like if it was upsized with a very bad filter. -- Ticket URL: <https://trac.macports.org/ticket/36410> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 15

[MacPorts] #36325: Add link to relevant bugs to the ports pages
by MacPorts 01 Oct '14

01 Oct '14

#36325: Add link to relevant bugs to the ports pages -------------------------+-------------------- Reporter: bgschaid@… | Owner: jmpp@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: website | Version: 2.1.2 Keywords: | Port: -------------------------+-------------------- Usually when I encounter a bug when upgrading a port (for instance qt4-mac) my first impules is to google "macport qt4-mac". One of the first pages I get is the overview page of the port (in this case http://www.macports.org/ports.php?by=library&substr=qt4-mac) It would be nice if in addition to the information there also a link "Tickets for this port" that leads to a trac page with a list of tickets (like this one http://trac.macports.org/query?port=qt4-mac&col=id&col=summary&col=port&col…) This would make it easier to find out whether there is already a fix for the problem (for that reason closed tickets should be in that list) or whether a new ticket should be opened -- Ticket URL: <https://trac.macports.org/ticket/36325> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #30945: bug report workflow could use some improvement
by MacPorts 01 Oct '14

01 Oct '14

#30945: bug report workflow could use some improvement ---------------------------------------+------------------------------------ Reporter: macosforge@… | Owner: jmpp@… Type: defect | Status: new Priority: Normal | Milestone: Component: website | Version: 2.0.1 Keywords: | Port: ---------------------------------------+------------------------------------ currently, I click "Report a bug" on the webpage and I'm being greeted with "login with email and password". [[BR]] First fail: it doesn't tell me what to do when I don't an account ("register" is at the top right and not that intuitive), but more seriously, [[BR]] 2) why require a login at all? millions of blogs can live without that. Let me enter an optional(!) email address to get notified if I want to, maybe make me confirm it via an optin link sent there (to catch spelling mistakes) - but the whole process needs to be much more accessible (see any study on how many users you lose if you require users to log in to your site). another small suggestion - it's good to refer to the bug submission guidelines, maybe a small executive summary would be nice: * tell the user to search for duplicates first[[BR]] * explain the format for summary: [port] [version] [concise description] - example: ...[[BR]] * use { { { ... } } } in description for terminal output) -- Ticket URL: <https://trac.macports.org/ticket/30945> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #30533: Remove mention of X11 from your reqs webpage: I installed xorg-server accidentally after misreading the page
by MacPorts 01 Oct '14

01 Oct '14

#30533: Remove mention of X11 from your reqs webpage: I installed xorg-server accidentally after misreading the page -----------------------------------+---------------------------------------- Reporter: jasonspiro4@… | Owner: jmpp@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: website | Version: Keywords: | Port: -----------------------------------+---------------------------------------- [http://www.macports.org/install.php#requirements www.macports.org/install.php#requirements] includes three sentences about X11. I skimmed them too fast. So I didn't realize all modern versions of OS X -- 10.5 "Leopard" and newer -- preinstall X11 by default. I didn't know where this MacBook's OS X DVD was. So I used MacPorts to build and install a second copy of X11, not knowing that I already had one copy installed. I wasted time, disk space, and electricity. Please remove X11 from the list of MacPorts requirements, so that nobody else will make the same mistake as me. :) -- Ticket URL: <https://trac.macports.org/ticket/30533> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #20946: add license display to ports.php
by MacPorts 01 Oct '14

01 Oct '14

#20946: add license display to ports.php ------------------------------+--------------------------------------------- Reporter: snc@… | Owner: jmpp@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: website | Version: Keywords: | Port: ------------------------------+--------------------------------------------- Would it be beneficial to provide the license information in the information displayed about our available ports? -- Ticket URL: <http://trac.macports.org/ticket/20946> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #19300: ports.php: web site should have page about each port, not link to portfile
by MacPorts 01 Oct '14

01 Oct '14

#19300: ports.php: web site should have page about each port, not link to portfile -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: jmpp@… Type: defect | Status: new Priority: Normal | Milestone: Website & Documentation Component: website | Version: Keywords: | Port: -------------------------------------+-------------------------------------- Currently ports.php lets you search for a port, but once you click on one for more info, it just takes you to the portfile in the repository. Users should never need to see the portfile text. Instead, we should show a nicely-formatted page which would include the information you can see in such commands as "`port info`" and "`port variants`" This issue was sent to me via email by Mojca Miklavec. -- Ticket URL: <http://trac.macports.org/ticket/19300> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #19298: ports.php: category pages hard to navigate; consider by-letter navigation
by MacPorts 01 Oct '14

01 Oct '14

#19298: ports.php: category pages hard to navigate; consider by-letter navigation -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: jmpp@… Type: defect | Status: new Priority: Normal | Milestone: Website & Documentation Component: website | Version: Keywords: | Port: -------------------------------------+-------------------------------------- If you're on a category page, the only available navigation links let you go to pages by number. This is not useful if you want to, say, browse a category for all ports whose names start with a particular letter. This deficiency was pointed out to me via email by Mojca Miklavec. -- Ticket URL: <http://trac.macports.org/ticket/19298> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #36782: yrus-sasl2 build failed (returned: command execution failed)
by MacPorts 01 Oct '14

01 Oct '14

#36782: yrus-sasl2 build failed (returned: command execution failed) -----------------------------+-------------------------------- Reporter: jeremy.booker@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: -----------------------------+-------------------------------- In trying to get JavaHL bindings for Subversion working... {{{ $ sudo port install subversion-javahlbindings +no_bdb +universal Password: ---> Computing dependencies for subversion-javahlbindings ---> Dependencies to be installed: cyrus-sasl2 gettext junit hamcrest- core apache-ant neon serf1 subversion curl-ca-bundle ---> Building cyrus-sasl2 Error: org.macports.build for port cyrus-sasl2 returned: command execution failed Error: Failed to install cyrus-sasl2 Please see the log file for port cyrus-sasl2 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_security_cyrus-sasl2/cyrus-sasl2/main.log Error: The following dependencies were not installed: cyrus-sasl2 gettext junit hamcrest-core apache-ant neon serf1 subversion curl-ca-bundle To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port subversion-javahlbindings failed }}} The main.log contains (after a bunch of successful commands): {{{ :info:build make[2]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_security_cyrus-sasl2/cyrus-sasl2/work/cyrus- sasl-2.1.25-x86_64/include' :info:build rm -f md5global.h :info:build ./makemd5 md5global.h:info:build make[2]: ./makemd5: Bad CPU type in executable :info:build make[2]: *** [md5global.h] Error 1 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_security_cyrus-sasl2/cyrus-sasl2/work/cyrus- sasl-2.1.25-x86_64/include' :info:build make[1]: *** [all-recursive] Error 1:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_security_cyrus-sasl2/cyr us-sasl2/work/cyrus-sasl-2.1.25-x86_64' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_security_cyrus-sasl2/cyrus- sasl2/work/cyrus-sasl-2.1.25-x86_64' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_security_cyrus-sasl2/cyrus-sasl 2/work/cyrus-sasl-2.1.25-x86_64" && /usr/bin/make -w all :info:build Exit code: 2 :error:build org.macports.build for port cyrus-sasl2 returned: command execution failed :debug:build Error code: NONE :debug:build Backtrace: command execution failed while executing "$procedure $targetname" :info:build Warning: targets not executed for cyrus-sasl2: org.macports.activate org.macports.build org.macports.destroot org.macports.install :error:build Failed to install cyrus-sasl2 :debug:build couldn't open "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex": no such file or directory while executing "open [file join $dir tclIndex]" }}} I'm running Snow Leopard (10.6.8), with MacPorts 2.1.2. -- Ticket URL: <https://trac.macports.org/ticket/36782> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7