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

[MacPorts] #22906: mlocate: a locate/updatedb implementation
by MacPorts 03 Oct '14

03 Oct '14

#22906: mlocate: a locate/updatedb implementation -----------------------------------+---------------------------------------- Reporter: ryan@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Keywords: | Port: -----------------------------------+---------------------------------------- From its website, https://fedorahosted.org/mlocate/ mlocate is a locate/updatedb implementation. The 'm' stands for "merging": updatedb reuses the existing database to avoid rereading most of the file system, which makes updatedb faster and does not trash the system caches as much. The locate(1) utility is intended to be completely compatible to slocate. It also attempts to be compatible to GNU locate, when it does not conflict with slocate compatibility. -- Ticket URL: <http://trac.macports.org/ticket/22906> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #31017: tuxtype: update to 1.8.0
by MacPorts 03 Oct '14

03 Oct '14

#31017: tuxtype: update to 1.8.0 -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: davidstuartbruce@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: tuxtype -------------------------------------+-------------------------------------- tuxtype should probably be updated to 1.8.0 -- Ticket URL: <https://trac.macports.org/ticket/31017> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #25391: Update Guide to document support for bzr as fetch.type
by MacPorts 03 Oct '14

03 Oct '14

#25391: Update Guide to document support for bzr as fetch.type -----------------------------------+---------------------------------------- Reporter: mike.mclean@… | Owner: markd@… Type: defect | Status: new Priority: Low | Milestone: Component: guide | Version: 1.9.1 Keywords: | Port: -----------------------------------+---------------------------------------- Closed ticket http://trac.macports.org/ticket/23436 add bzr as a supported fetch.type. Update Section 5.3.3.1, Advanced Fetch Options of the guide (http://guide.macports.org/#reference.phases.fetch.advanced) to list bzr as a fetch.type. Create a 5.3.3.x section that lists the specifics for the bzr fetch.type. -- Ticket URL: <http://trac.macports.org/ticket/25391> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #19031: flow-tools: reinplace didn't change anything in several files
by MacPorts 02 Oct '14

02 Oct '14

#19031: flow-tools: reinplace didn't change anything in several files -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: flow-tools -------------------------------------+-------------------------------------- Using the patch in #15514 I see that flow-tools does many reinplaces which end up having no effect. Perhaps some of these are bugs. {{{ $ port install flow-tools ---> Fetching flow-tools ---> Attempting to fetch flow-tools-0.68.tar.gz from http://leopard.local/distfiles/flow-tools ---> Verifying checksum(s) for flow-tools ---> Extracting flow-tools ---> Applying patches to flow-tools Warning: reinplace s|__PREFIX__|/mp|g didn't change anything in /Users/rschmidt/macports/dports/net/flow-tools/files/patch-ftpaths.h Warning: reinplace s|@localstatedir@/sym/|/mp/share/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-capture.1.in Warning: reinplace s|@localstatedir@/sym/|/mp/share/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-fanout.1.in Warning: reinplace s|@localstatedir@/sym/|/mp/share/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-log2rrd.1.in Warning: reinplace s|@localstatedir@/sym/|/mp/share/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-mask.1.in Warning: reinplace s|@localstatedir@/sym/|/mp/share/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-receive.1.in Warning: reinplace s|@localstatedir@/sym/|/mp/share/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-rpt2rrd.1.in Warning: reinplace s|@localstatedir@/sym/|/mp/share/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-rptfmt.1.in Warning: reinplace s|@localstatedir@/cfg/|/mp/etc/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-log2rrd.1.in Warning: reinplace s|@localstatedir@/cfg/|/mp/etc/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-print.1.in Warning: reinplace s|@localstatedir@/cfg/|/mp/etc/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-receive.1.in Warning: reinplace s|@localstatedir@/cfg/|/mp/etc/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-rpt2rrd.1.in Warning: reinplace s|@localstatedir@/cfg/|/mp/etc/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-rptfmt.1.in Warning: reinplace s|@localstatedir@/cfg/|/mp/etc/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-log2rrd.html.in Warning: reinplace s|@localstatedir@/cfg/|/mp/etc/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-print.html.in Warning: reinplace s|@localstatedir@/cfg/|/mp/etc/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-receive.html.in Warning: reinplace s|@localstatedir@/cfg/|/mp/etc/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-rpt2rrd.html.in Warning: reinplace s|@localstatedir@/cfg/|/mp/etc/flow-tools/|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_net_flow-tools/work/flow-tools-0.68/docs /flow-rptfmt.html.in ---> Configuring flow-tools ^C $ }}} -- Ticket URL: <http://trac.macports.org/ticket/19031> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[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] #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