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

[MacPorts] #26814: Add 'ruby19' variant to vim
by MacPorts 07 Jan '13

07 Jan '13

#26814: Add 'ruby19' variant to vim --------------------------------------+------------------------------------- Reporter: dmitry.gladkov@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: vim, ruby | Port: vim --------------------------------------+------------------------------------- I have ruby19 only installed and I don't want to install ruby 1.8.x back just to build vim with ruby support. I guess if vim is ruby19 compatible, it should be something like this in portfile: {{{ variant ruby description {Enable Ruby scripting} { configure.args-append --enable-rubyinterp depends_lib-append port:ruby19 } }}} -- Ticket URL: <https://trac.macports.org/ticket/26814> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #37023: php5-libev new port request
by MacPorts 07 Jan '13

07 Jan '13

#37023: php5-libev new port request ---------------------------------+-------------------------------- Reporter: watermark.nielsen@… | Owner: macports-tickets@… Type: request | Status: new Priority: Low | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: ---------------------------------+-------------------------------- Request for a PHP extension: https://github.com/m4rw3r/php-libev It's used by the http://reactphp.org project, if that's relevant. I'm not sure what level of maturity a project has to reach to be included into MacPorts or if it's more appropriate for the author to submit these. -- Ticket URL: <https://trac.macports.org/ticket/37023> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #37000: sshfs
by MacPorts 05 Jan '13

05 Jan '13

#37000: sshfs ---------------------------+-------------------------------- Reporter: jonlederman@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: ---------------------------+-------------------------------- HI, I am unable to run sshfs, which was installed via macports. When I type the command, I get: sudo echo password | sshfs jon@192.168.2.11:/opt ~/mnt -o dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid dyld: Library not loaded: /opt/local/lib/libfuse.2.dylib Referenced from: /opt/local/bin/sshfs Reason: Incompatible library version: sshfs requires version 11.0.0 or later, but libfuse.2.dylib provides version 10.0.0 Trace/BPT trap: 5 Any help appreciated. Thanks. Jon -- Ticket URL: <https://trac.macports.org/ticket/37000> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #34635: Skrooge will not run in MacPorts
by MacPorts 05 Jan '13

05 Jan '13

#34635: Skrooge will not run in MacPorts --------------------------------+------------------------------------------- Reporter: ron@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: Skrooge | Port: Skrooge --------------------------------+------------------------------------------- MacPorts 2.1.1, Mac OSx 10.7.4, Skrooge 1.3 I tried last year and I again tried a few days ago. Skrooge will NOT run in MacPorts, no matter what, it will not load. I am suspicious that it has never been successfully installed and loaded by anyone using MacPorts. I need help to get it running on my machine as the Skrooge development team do not seem to have access to a Mac machine. -- Ticket URL: <https://trac.macports.org/ticket/34635> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 26

[MacPorts] #35401: skrooge @1.3.0 runtime error
by MacPorts 05 Jan '13

05 Jan '13

#35401: skrooge @1.3.0 runtime error ------------------------------------+--------------------------------------- Reporter: fares.chucri@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: skrooge_monthly | Port: skrooge ------------------------------------+--------------------------------------- I have just updated skrooge from the 1.3.0 beta to the 1.3.0 and i get the following error: {{{ skrooge loading of skrooge monthly failed because the factory could not be found in skrooge_monthly }}} -- Ticket URL: <https://trac.macports.org/ticket/35401> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #32778: Request update wordpress @3.2.1 to wordpress @3.3.1
by MacPorts 04 Jan '13

04 Jan '13

#32778: Request update wordpress @3.2.1 to wordpress @3.3.1 --------------------------------+------------------------------------------- Reporter: raramayo@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: --------------------------------+------------------------------------------- Request update wordpress @3.2.1 to wordpress @3.3.1 Thanks -- Ticket URL: <https://trac.macports.org/ticket/32778> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #36721: cmph: universal variant fails
by MacPorts 04 Jan '13

04 Jan '13

#36721: cmph: universal variant fails --------------------------+-------------------- Reporter: ryandesign@… | Owner: miwi@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: cmph --------------------------+-------------------- See summary. -- Ticket URL: <https://trac.macports.org/ticket/36721> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #37127: Ports abandoned by miwi
by MacPorts 04 Jan '13

04 Jan '13

#37127: Ports abandoned by miwi -------------------------+------------------------------------------------- Reporter: | Owner: miwi@… ryandesign@… | Status: new Type: defect | Milestone: Priority: Normal | Version: Component: ports | Port: centerim, cmph, contao, cssh, Keywords: | mod_chroot, mybb, nut, php-lzf, php-rar, php- | stomp, php-timezonedb, php-vld, php5-lzf, | php5-rar, php5-stomp, php5-timezonedb, | php5-vld, phppgadmin, wordpress -------------------------+------------------------------------------------- Martin Wilke (MacPorts handle "miwi") has not committed to the MacPorts repository in some time, and has only ever responded to a single ticket that was assigned to him, out of 19: #26183 #30110 #30111 #30112 #30113 #30114 #30115 #30116 #30117 #32628 #32778 #33060 #34580 #34581 #34582 #35223 #36586 #36721 #36766 In order not to give users the false impression that a port is being maintained, when in fact it is not, if there is no response from miwi by January 1, 2013, he will be considered to have left the MacPorts project and his ports and tickets will be reassigned. See [http://guide.macports.org/chunked/project.update-policies.html#project .update-policies.abandonment port abandonment policy]. -- Ticket URL: <https://trac.macports.org/ticket/37127> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #37130: github portgroup: github.tarball_from downloads should set livecheck.url
by MacPorts 04 Jan '13

04 Jan '13

#37130: github portgroup: github.tarball_from downloads should set livecheck.url -------------------------+-------------------------------- Reporter: aronnax@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: -------------------------+-------------------------------- I maintain a pair of ports, gst-plugins-cairovis and gst-plugins-math, which are hosted on GitHub (and of which I am the author). I generate and upload stable source tarballs under the projects' respective downloads on GitHub. I just realized that the livecheck for these ports is busted. I had to override the defaults by adding the following: {{{ livecheck.url https://github.com/${github.author}/${name}/downloads livecheck.regex ${name}-(\\d+(\\.\\d+)*)[regsub -all \\. ${extract.suffix} \\.] }}} It is understandable that I would have to write my own regex, but it would be nice if {{{ github.tarball_from downloads }}} automatically set {{{livecheck.url}}} to something useful. -- Ticket URL: <https://trac.macports.org/ticket/37130> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #20448: doxygen +wizard fails to build on Tiger
by MacPorts 04 Jan '13

04 Jan '13

#20448: doxygen +wizard fails to build on Tiger -----------------------------------+---------------------------------------- Reporter: ccorn@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: QT | Port: doxygen -----------------------------------+---------------------------------------- Port: doxygen 1.5.9 +wizard (svn -r54420) Platform: Mac OS X 10.4.11 on a Powerbook G4 (Darwin 8.11.0/powerpc) Building DoxyWizard aborts with the attached linker errors. Two issues emerge from that: (1) Linking DoxyWizard does not find -lpng. The linker command line misses either an -L${worksrcdir}/libpng (yes, doxygen builds a static copy of libpng) or an -L${prefix}/lib. With respect to a given lib dependency port:libpng and a given post-patch action that inserts ${configure.cppflags} right after the compiler command, I have decided to insert ${configure.ldflags} right after the linker command as well. Thus, MacPort's libpng should be used. At least I hoped so. However, this still did not produce the desired linker command. (But I left the patch in for symmetry reasons.) Finally, I resorted to build.env-append LIBRARY_PATH=${prefix}/lib within the definition of variant wizard. This helped. (2) Universal binaries are built without demand. First, I supposed that this is because there is a second post-patch definition for variant wizard which might override the previous post-patch definition. I have moved the post-patch and post-destroot commands out of the variant definition, and I have guarded them with a test for variant wizard or platform darwin where necessary. Note that the present patches to doxywizard makefiles can mostly be applied without regard to whether variant wizard is in effect, but the patches are appropriate for macosx/darwin only. Therefore, most patches are guarded by the platform test alone. Again, this alone did not help. (I left the patch in because having several post-patch definitions looks confusing anyway.) Finally, I found that addon/doxywizard/doxywizard.pro.in itself specifies "CONFIG += x86 ppc". I have added a patchfile to remove that unless the universal variant is desired. This made the difference. Some quirks removed by the way: (3) ${tmake_conf} was used in post-patch actions, but defined for platform darwin only. I have moved the definition into the post-patch section. Both the definition and the affected patch action are conditioned on a test for platform darwin now. (4) The build dependency bin:ginstall:coreutils is not needed. Just add --install /usr/bin/install to configure.args, and doxygen will use that. Also relevant for ticket #18400. I have attached a Portfile patch, an additional patchfile and the (previous) error excerpts. The patches succeed in building doxygen +wizard and doxygen -wizard correctly on my platform. -- Ticket URL: <http://trac.macports.org/ticket/20448> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5