September 2012 - macports-tickets - lists.macosforge.org

[MacPorts] #27726: libcudd should be updated to 2.4.2
by MacPorts 02 Oct '14

02 Oct '14

#27726: libcudd should be updated to 2.4.2 -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: mij@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: libcudd -------------------------------------+-------------------------------------- libcudd 2.4.2 is out so the port should probably be updated to that version. The livecheck should probably also be fixed. -- Ticket URL: <https://trac.macports.org/ticket/27726> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 27

[MacPorts] #18569: fop 0.94 - Update to 0.95; add variant "hyphenation"
by MacPorts 02 Oct '14

02 Oct '14

#18569: fop 0.94 - Update to 0.95; add variant "hyphenation" ------------------------------------+--------------------------------------- Reporter: campesr@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Port Requests Component: ports | Version: 1.7.0 Keywords: fop, offo, hyphenation | Port: fop ------------------------------------+--------------------------------------- Hi, would it be possible to update fop to 0.95? There were many enhancements since 0.94. Would it be furthermore possible to add a variant (or a separate port), which will install the hyphenation patterns from http://offo.sourceforge.net/hyphenation/ ? Many thanks, Cheers. -- Ticket URL: <http://trac.macports.org/ticket/18569> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #17472: Xmgrace and extended ascii characters
by MacPorts 02 Oct '14

02 Oct '14

#17472: Xmgrace and extended ascii characters --------------------------------+------------------------------------------- Reporter: emoro@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | Port: --------------------------------+------------------------------------------- I've succesfully installed grace port in my Mac OSX Leopard 10.5.5 laptop (with spanish localization) However, grace does not recognize extended ascii characters (like the "ñ" or accented letters) in the windows boxes or on the "font tool" menu. Other X11 applications are working fine, including the xterm, xedit, etc. The Grace maintainers at http://plasma-gate.weizmann.ac.il/Grace/ say that there is a problem with openmotif version 2.2 and they recommend to use lesstif or to downgrade to openmotif 2.1. Is there any way to modify the grace port to do that? Thanks in advance -- Ticket URL: <http://trac.macports.org/ticket/17472> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #16514: Minicom: bad path for lock file
by MacPorts 02 Oct '14

02 Oct '14

#16514: Minicom: bad path for lock file -------------------------------------+-------------------------------------- Reporter: julien-mac(a)touche.fr.st | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | Port: -------------------------------------+-------------------------------------- Minicom create a lock file when it is launched to prevent another instance to be called. For now, Portfile set this to ${prefix}/var which is 755 by default on leopard, so by default only root can call minicom. It would be better if --enable-lock-dir was set up on ${prefix}/lock which could be set 1777. Else if we accept path outside of prefix, we can use /var/tmp (or /tmp to be more portable) -- Ticket URL: <http://trac.macports.org/ticket/16514> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #36198: t4k_common 0.1.1_1 - build error
by MacPorts 01 Oct '14

01 Oct '14

#36198: t4k_common 0.1.1_1 - build error -----------------------+-------------------------------- Reporter: aztec86@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: t4k_common -----------------------+-------------------------------- Upgrading MacPorts fails when building this port. MacOSX 10.5.8 PPC; Xcode version: 3.1.4; gcc 4.0; error: {{{ ---> Building t4k_common Error: org.macports.build for port t4k_common returned: command execution failed Please see the log file for port t4k_common for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_t4k_common/t4k_common/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets }}} From /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_t4k_common/t4k_common/main.log file: {{{ :info:build /opt/local/include/librsvg-2.0/librsvg/rsvg-cairo.h:27:2: warning: #warning "Including <librsvg/rsvg-cairo.h> directly is deprecated." :info:build t4k_loaders.c: In function ‘load_svg’: :info:build t4k_loaders.c:176: warning: ‘rsvg_init’ is deprecated (declared at /opt/local/include/librsvg-2.0/librsvg/rsvg.h:178) :info:build t4k_loaders.c:182: warning: ‘rsvg_term’ is deprecated (declared at /opt/local/include/librsvg-2.0/librsvg/rsvg.h:180) :info:build t4k_loaders.c:189: warning: ‘rsvg_term’ is deprecated (declared at /opt/local/include/librsvg-2.0/librsvg/rsvg.h:180) :info:build t4k_loaders.c: In function ‘load_svg_sprite’: :info:build t4k_loaders.c:203: warning: ‘rsvg_init’ is deprecated (declared at /opt/local/include/librsvg-2.0/librsvg/rsvg.h:178) :info:build t4k_loaders.c:209: warning: ‘rsvg_term’ is deprecated (declared at /opt/local/include/librsvg-2.0/librsvg/rsvg.h:180) :info:build t4k_loaders.c:217: warning: ‘rsvg_handle_get_desc’ is deprecated (declared at /opt/local/include/librsvg-2.0/librsvg/rsvg.h:227) :info:build t4k_loaders.c:227: warning: ‘rsvg_term’ is deprecated (declared at /opt/local/include/librsvg-2.0/librsvg/rsvg.h:180) :info:build t4k_loaders.c: In function ‘get_svg_dimensions’: :info:build t4k_loaders.c:314: warning: ‘rsvg_init’ is deprecated (declared at /opt/local/include/librsvg-2.0/librsvg/rsvg.h:178) :info:build t4k_loaders.c:320: warning: ‘rsvg_term’ is deprecated (declared at /opt/local/include/librsvg-2.0/librsvg/rsvg.h:180) :info:build t4k_loaders.c:332: warning: ‘rsvg_term’ is deprecated (declared at /opt/local/include/librsvg-2.0/librsvg/rsvg.h:180) :info:build t4k_loaders.c: In function ‘do_png_save’: :info:build t4k_loaders.c:1031: error: dereferencing pointer to incomplete type :info:build t4k_loaders.c:1032: error: dereferencing pointer to incomplete type :info:build t4k_loaders.c:1033: error: dereferencing pointer to incomplete type :info:build t4k_loaders.c:1034: error: dereferencing pointer to incomplete type :info:build t4k_loaders.c:1035: error: dereferencing pointer to incomplete type :info:build t4k_loaders.c:1036: error: dereferencing pointer to incomplete type :info:build make[3]: *** [t4k_loaders.lo] Error 1 :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_t4k_common/t4k_common/work/t4k_common-0.1.1/src' :info:build make[2]: *** [all-recursive] Error 1 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_t4k_common/t4k_common/work/t4k_common-0.1.1/src' :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_devel_t4k_common/t4k_common/work/t4k_common-0.1.1' :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_devel_t4k_common/t4k_common/work/t4k_common-0.1.1' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_t4k_common/t4k_common/work/t4k_common-0.1.1" && /usr/bin/make -w all :info:build Exit code: 2 :error:build org.macports.build for port t4k_common returned: command execution failed :debug:build Error code: CHILDSTATUS 9064 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: targets not executed for t4k_common: org.macports.install org.macports.build org.macports.destroot :notice:build Please see the log file for port t4k_common for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_t4k_common/t4k_common/main.log }}} -- Ticket URL: <https://trac.macports.org/ticket/36198> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[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