February 2010 - macports-tickets - lists.macosforge.org

[MacPorts] #23293: Deprecation & Deletion of Zope ports
by MacPorts 17 Oct '14

17 Oct '14

#23293: Deprecation & Deletion of Zope ports -----------------------------------------------+---------------------------- Reporter: charlie.clark@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: zope | Port: -----------------------------------------------+---------------------------- With the release of Zope 2.12 the Zope now uses the buildout framework for package installation with py-setuptools or py-distribute being the only dependency. In the light of this and the extreme age of many of the Zope ports I suggest that all zope-ports be removed from the tree. I couldn't find any reference to port deletion or deprecation in the documentation. -- Ticket URL: <http://trac.macports.org/ticket/23293> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #22689: openvpn2-2.0.9 Compiling with gcc-4.2 leads to wrong behaviour
by MacPorts 15 Oct '14

15 Oct '14

#22689: openvpn2-2.0.9 Compiling with gcc-4.2 leads to wrong behaviour ------------------------------------------------+--------------------------- Reporter: wickedguitar6@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Keywords: openvpn2, default_gateway, gcc-4.0 | Port: openvpn2 ------------------------------------------------+--------------------------- There is a bug which leads to wrong detection of the default_gateway (0.0.0.0) when the three following conditions apply: 1) openvpn2-2.0.9 is compiled with gcc-4.2 (the default on Mac OS X 10.6) 2) It is used as a client 3) 'push "redirect-gateway def1"' is used on the server side (e.g. a linux-box) When the openvpn-2.0.9 is compiled with gcc-4.0 the bug does not occur. Default_gateway is detected correctly. However the gcc-4.0 compiler is not aware of the lzo2 library and openvpn must be configured with "--disable- lzo". -- Ticket URL: <http://trac.macports.org/ticket/22689> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #22407: Python interpreter build inconsistency across versions
by MacPorts 11 Oct '14

11 Oct '14

#22407: Python interpreter build inconsistency across versions ----------------------------------+----------------------------------------- Reporter: akitada@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Keywords: python | Port: python24, python25, python26, python31 ----------------------------------+----------------------------------------- For example, python26 is framework build but python25 is not. Can we change this inconsistency to get it simpler? -- Ticket URL: <http://trac.macports.org/ticket/22407> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

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