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

[MacPorts] #32967: cvsps needs to be UsingTheRightCompiler
by MacPorts 25 Aug '14

25 Aug '14

#32967: cvsps needs to be UsingTheRightCompiler ------------------------------+--------------------------------------------- Reporter: snc@… | Owner: erickt@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: cvsps ------------------------------+--------------------------------------------- {{{ cc -g -O2 -Wall -I. -DVERSION=\"2.1\" -c -o cbtcommon/debug.o cbtcommon/debug.c cc -g -O2 -Wall -I. -DVERSION="2.1" -c -o cbtcommon/debug.o cbtcommon/debug.c cc: Error: You should be using ${configure.cc} See http://trac.macports.org/wiki/UsingTheRightCompiler make: *** [cbtcommon/debug.o] Error 1 }}} -- Ticket URL: <https://trac.macports.org/ticket/32967> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #38905: irssi SSL bug
by MacPorts 25 Aug '14

25 Aug '14

#38905: irssi SSL bug -----------------------+-------------------------------- Reporter: jorgeja@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: -----------------------+-------------------------------- Hi! I have been having trouble (as in I can't) connecting to SSL irc servers. I think it is caused by OpenSSL 1.01e. I get -!- Irssi: warning SSL read error: decryption failed or bad record mac The bug is mentioned here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667014 And the irssi people have put out a bug fix for it here: http://bugs.irssi.org/index.php?getfile=278 -- Ticket URL: <https://trac.macports.org/ticket/38905> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #24708: p5-libxml-enno and p5-xml-dom conflict
by MacPorts 25 Aug '14

25 Aug '14

#24708: p5-libxml-enno and p5-xml-dom conflict -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: narf_tm@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: p5-libxml-enno, p5-xml-dom -------------------------------------+-------------------------------------- p5-libxml-enno and p5-xml-dom conflict; indeed the description of p5 -libxml-enno says it provides XML::DOM. We should have only a single port for this software, whichever is the latest. -- Ticket URL: <http://trac.macports.org/ticket/24708> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #35339: Update zorba to 2.5 release
by MacPorts 24 Aug '14

24 Aug '14

#35339: Update zorba to 2.5 release ------------------------------------+--------------------------------------- Reporter: cezar.andrei@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.1.1 Keywords: zorba | Port: zorba ------------------------------------+--------------------------------------- This is an update to zorba port to upgrade to release 2.5. Attached are the patch to the Portfile and updated patch files. -- Ticket URL: <https://trac.macports.org/ticket/35339> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 10

[MacPorts] #38952: Scrapy templates unreadable except by root
by MacPorts 22 Aug '14

22 Aug '14

#38952: Scrapy templates unreadable except by root -------------------------+-------------------------------- Reporter: moboyle79@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: -------------------------+-------------------------------- I installed py2.7-scrapy, and started following the basic scrapy tutorial [http://doc.scrapy.org/en/latest/intro/tutorial.html#intro-tutorial here], but got an error on the first step (creating a project). The command {{{scrapy startproject tutorial}}} gave a bunch of errors about permission denied in {{{/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/scrapy/templates/}}}. The files in there all seemed to be owned by root, with permissions and ownership {{{-rw------- 1 root wheel}}}. Since the scrapy startproject command copies some of these template files, it failed. I solved the problem by simply running {{{sudo chmod -R +r /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/scrapy/templates/}}} -- Ticket URL: <https://trac.macports.org/ticket/38952> MacPorts <http://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #37352: Fixes for #38606 and #36807
by MacPorts 22 Aug '14

22 Aug '14

#37352: Fixes for #38606 and #36807 --------------------------+-------------------------------- Reporter: sami.laine@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: torsocks --------------------------+-------------------------------- Updated Portfile for torsocks package, includes fixes for #38606 and #38607. -- Ticket URL: <https://trac.macports.org/ticket/37352> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #36807: torsocks should install a sample conf file, not a real conf file
by MacPorts 22 Aug '14

22 Aug '14

#36807: torsocks should install a sample conf file, not a real conf file --------------------------+-------------------------- Reporter: ryandesign@… | Owner: sami.laine@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: torsocks --------------------------+-------------------------- torsocks installs ${prefix}/etc/torsocks.conf, but ports should not install files users are expected to modify. Instead it [wiki:PortfileRecipes#configfiles should install a sample conf file]. -- Ticket URL: <https://trac.macports.org/ticket/36807> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #36806: torsocks installs documentation in the wrong directory
by MacPorts 22 Aug '14

22 Aug '14

#36806: torsocks installs documentation in the wrong directory --------------------------+-------------------------- Reporter: ryandesign@… | Owner: sami.laine@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: torsocks --------------------------+-------------------------- torsocks installs documentation files directly in ${prefix}/share but it [wiki:PortfileRecipes#doc should install them in] ${prefix}/share/doc/${name} -- Ticket URL: <https://trac.macports.org/ticket/36806> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #33719: keep machines from sleep during port building
by MacPorts 21 Aug '14

21 Aug '14

#33719: keep machines from sleep during port building ------------------------------------------+--------------------------------- Reporter: drechsel@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: | Port: all ------------------------------------------+--------------------------------- Frequently I noticed that my iMac G5 will go to sleep during a time extensive build (gcc45 at the moment). I googled and found some other people with that problem - and an easy solution: {{{ #!/bin/bash pmset noidle & <<<... do the work here ...>>> kill %pmset }}} Wouldnt it be smart to put the "noidle" command at the very beginning of any build script - and the "kill %pmset" at the very ending? I'd like the iMac to do the building - and then go to sleep after it's finished if nothing else is to do. -- Ticket URL: <https://trac.macports.org/ticket/33719> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #16373: svn fetch type should maintain a persistent working copy
by MacPorts 20 Aug '14

20 Aug '14

#16373: svn fetch type should maintain a persistent working copy -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts base enhancements Component: base | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- "`fetch.type svn`" is inefficient in that it checks out a new working copy every time, directly to the work area. That would be like a normal port downloading the distfile every time. Instead, we should check out a working copy to that port's distpath, and then in the extract phase we should `svn export` it to the work area. Some checks will be needed in the fetch phase to ensure that an existing working copy: * has no modifications: check `svn status`. Ideally we would try to clean up the working copy, for example by `svn revert`ing modified or added or deleted files, and then in a second `svn status` run, delete any unversioned files. But it's already an improvement if we just discard the working copy if `svn status --ignore-externals` produces any output. * is from the right URL: check `svn info`: check if the "URL" is the one we want. If not, check that the "Repository Root" is a substring of the repository we want. If yes, try to `svn switch` to the URL and revision we want; if not, discard the working copy. So the fetch phase would go something like... {{{ if {working copy exists} { if {working copy has modifications} { delete working copy } } if {working copy exists} { if {working copy url is the one we want} { svn update to the desired revision } else { if {working copy repository root matches beginning of desired url} { try to svn switch to the desired url and revision if {an error occurred} { delete working copy } } else { delete working copy } } } if {working copy doesn't exist} { check out working copy } }}} And the extract phase is simply to `svn export` the working copy from the distpath to the worksrcpath. (There is [http://subversion.tigris.org/issues/show_bug.cgi?id=2429 one problem] if the working copy has externals and the user is using Subversion earlier than 1.5, for example Subversion 1.4.whatever which is included with Leopard. But rather than spend time working around this in base, I think this is a case where the port should depend on MacPorts subversion.) -- Ticket URL: <http://trac.macports.org/ticket/16373> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 21