April 2009 - macports-tickets - lists.macosforge.org

[MacPorts] #18474: gimp-app 2.6.0_1 openDoc failure
by MacPorts 05 May '10

05 May '10

#18474: gimp-app 2.6.0_1 openDoc failure --------------------------------+------------------------------------------- Reporter: edheil@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: --------------------------------+------------------------------------------- apologies if this is a duplicate ticket; I'm not sure if I submitted or just previewed it and then closed the tab a few minutes ago. 2 problems with opening files using Gimp.app 1) gimp2 no longer builds gimp-remote by default. already submitted a bug about that: https://trac.macports.org/ticket/18473 2) on Leopard, with xquartz 2.3.2 (and I suspect also Apple's X11), the DISPLAY variable trick in Gimp.app/Contents/Resources/openDoc no longer works; in fact, it prevents openDoc from working at all. Changing it to something like this: #!/bin/sh # # Author: Aaron Voisine <aaron(a)voisine.org> DISPFILE=/tmp/display.$UID if [ -e $DISPFILE ] then export "DISPLAY=`cat $DISPFILE`" fi exec "/opt/local/bin/gimp-remote" "$@" makes it work on Leopard (which doesn't set /tmp/display.nnnn), and I imagine it would still work on older versions of OS X which do use /tmp/display.nnn This could be seen as an upstream bug but honestly I could not figure out how to do submit a bug from the website at http://gimp- app.sourceforge.net/ . -- Ticket URL: <http://trac.macports.org/ticket/18474> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #16793: Request for port: yorick
by MacPorts 03 May '10

03 May '10

#16793: Request for port: yorick -------------------------------+-------------------------------------------- Reporter: ralph(a)cs.cf.ac.uk | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Requests Component: ports | Version: 1.6.0 Keywords: | Port: -------------------------------+-------------------------------------------- This is a request for a new port: yorick See http://yorick.sourceforge.net/ -- Ticket URL: <http://trac.macports.org/ticket/16793> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #19412: Update TightVNC 1.3.9 to 1.3.10
by MacPorts 30 Apr '10

30 Apr '10

#19412: Update TightVNC 1.3.9 to 1.3.10 ---------------------------------+------------------------------------------ Reporter: luis.beca@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.7.1 Keywords: | Port: ---------------------------------+------------------------------------------ Please update TightVNC 1.3.9 to 1.3.10. -- Ticket URL: <http://trac.macports.org/ticket/19412> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #17921: Name Resolution does not work properly with vpnc 0.5.3
by MacPorts 29 Apr '10

29 Apr '10

#17921: Name Resolution does not work properly with vpnc 0.5.3 ----------------------------------+----------------------------------------- Reporter: monty19@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: vpnc name resolution | Port: vpnc ----------------------------------+----------------------------------------- When I did an update of ports and vpnc 0.5.3 installed I started having the following behaviour: /etc/resolv.conf is updated properly to reflect DNS servres on corporate network I can use dig or nslookup to successfully query the addresses of servers by name. I can not resolve names of systems on the corporate network using a web browser, ping, email client or anything else. Name resolution continues to work for hosts on the internet; kind of like the dns servers for my internet connection are still being used, although the resolv.conf does not reflect that. I have observed this broken behaviour with 0.5.2 and 0.5.3; I downgraded to 0.5.1 and am working properly again -- Ticket URL: <http://trac.macports.org/ticket/17921> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #16435: libdvdcss 1.2.9: refman.dvi build failure: Unicode char \u8:éph not set up for use with LaTeX
by MacPorts 28 Apr '10

28 Apr '10

#16435: libdvdcss 1.2.9: refman.dvi build failure: Unicode char \u8:éph not set up for use with LaTeX -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | -------------------------------------+-------------------------------------- {{{ $ sudo port install libdvdcss ---> Fetching libdvdcss ---> Verifying checksum(s) for libdvdcss ---> Extracting libdvdcss ---> Configuring libdvdcss ---> Building libdvdcss with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_Users_rschmidt_macports_dports_devel_libdvdcss/work/libdvdcss-1.2.9" && nice -n 10 make all " returned error 2 Command output: [121] [122]) (/opt/local/share/texmf- dist/fonts/source/jknappen/ec/exidigit.mf Ok [48] [49] [50] [51] [52] [53] [54] [55] [56] [57]) (/opt/local/share/texmf-dist/fonts/source/jknappen/ec/exiligtb.mf Ok) ) ) ) Font metrics written on ecti0900.tfm. Output written on ecti0900.600gf (256 characters, 48832 bytes). Transcript written on ecti0900.log. mktextfm: /var/tmp/texfonts/tfm/jknappen/ec/ecti0900.tfm: successfully generated. [5] ! Package inputenc Error: Unicode char \u8:éph not set up for use with LaTeX. See the inputenc package documentation for explanation. Type H <return> for immediate help. ... l.49 \item[Author:]Stéph ane Borel $<${\tt stef(a)via.ecp.fr}$>$ ? ! Emergency stop. ... l.49 \item[Author:]Stéph ane Borel $<${\tt stef(a)via.ecp.fr}$>$ Output written on refman.dvi (9 pages, 8452 bytes). Transcript written on refman.log. make[3]: *** [refman.dvi] Error 1 make[2]: *** [stamp-latex] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Status 1 encountered during processing. $ }}} -- Ticket URL: <http://trac.macports.org/ticket/16435> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #17792: vxl fails to build
by MacPorts 28 Apr '10

28 Apr '10

#17792: vxl fails to build ----------------------------------+----------------------------------------- Reporter: jwhowse4@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: ----------------------------------+----------------------------------------- On an intel mac running Leopard 10.5.6 and Xcode 3.1.2 vxl fails to build with the following error. It looks to me as if this may be related to the fact that I can not update ffmpeg. Any suggestions? {{{ Error: Target org.macports.build returned: shell command " cd "/opt/macports/var/macports/build/_opt_macports_var_macports_sources_rsync.macports.org_release_ports_devel_vxl/work/vxl-1.11.0" && make all " returned error 2 Command output: /opt/macports/include/ffmpeg/avcodec.h:2349: warning: 'ImgReSampleContext' is deprecated (declared at /opt/macports/include/ffmpeg/avcodec.h:2343) /opt/macports/include/ffmpeg/avcodec.h:2359: warning: 'ImgReSampleContext' is deprecated (declared at /opt/macports/include/ffmpeg/avcodec.h:2343) [ 34%] Building CXX object core/vidl/CMakeFiles/vidl.dir/vidl_clip.o [ 34%] Building CXX object core/vidl/CMakeFiles/vidl.dir/vidl_movie.o [ 34%] Building CXX object core/vidl/CMakeFiles/vidl.dir/vidl_frame.o [ 34%] Building CXX object core/vidl/CMakeFiles/vidl.dir/vidl_frame_resource.o [ 34%] Building CXX object core/vidl/CMakeFiles/vidl.dir/vidl_image_list_codec.o [ 34%] Building CXX object core/vidl/CMakeFiles/vidl.dir/vidl_io.o [ 34%] Building CXX object core/vidl/CMakeFiles/vidl.dir/vidl_mpegcodec.o [ 34%] Building CXX object core/vidl/CMakeFiles/vidl.dir/vidl_mpegcodec_helper.o [ 35%] Building CXX object core/vidl/CMakeFiles/vidl.dir/vidl_ffmpeg_codec.o /opt/macports/include/ffmpeg/avcodec.h:2349: warning: 'ImgReSampleContext' is deprecated (declared at /opt/macports/include/ffmpeg/avcodec.h:2343) /opt/macports/include/ffmpeg/avcodec.h:2359: warning: 'ImgReSampleContext' is deprecated (declared at /opt/macports/include/ffmpeg/avcodec.h:2343) /opt/macports/var/macports/build/_opt_macports_var_macports_sources_rsync.macports.org_release_ports_devel_vxl/work/vxl-1.11.0/core/vidl/vidl_ffmpeg_codec.cxx: In member function 'vil_image_view<vxl_byte> vidl_ffmpeg_codec::cur_frame() const': /opt/macports/var/macports/build/_opt_macports_var_macports_sources_rsync.macports.org_release_ports_devel_vxl/work/vxl-1.11.0/core/vidl/vidl_ffmpeg_codec.cxx:259: warning: 'img_convert' is deprecated (declared at /opt/macports/include/ffmpeg/avcodec.h:2511) /opt/macports/var/macports/build/_opt_macports_var_macports_sources_rsync.macports.org_release_ports_devel_vxl/work/vxl-1.11.0/core/vidl/vidl_ffmpeg_codec.cxx:261: warning: 'img_convert' is deprecated (declared at /opt/macports/include/ffmpeg/avcodec.h:2511) [ 35%] Building CXX object core/vidl/CMakeFiles/vidl.dir/Templates/vbl_smart_ptr+vidl_clip-.o [ 35%] Building CXX object core/vidl/CMakeFiles/vidl.dir/Templates/vbl_smart_ptr+vidl_codec-.o [ 35%] Building CXX object core/vidl/CMakeFiles/vidl.dir/Templates/vbl_smart_ptr+vidl_frame-.o [ 35%] Building CXX object core/vidl/CMakeFiles/vidl.dir/Templates/vbl_smart_ptr+vidl_image_list_codec-.o [ 35%] Building CXX object core/vidl/CMakeFiles/vidl.dir/Templates/vbl_smart_ptr+vidl_movie-.o Linking CXX shared library ../../lib/libvidl.dylib Undefined symbols: "_img_convert", referenced from: vidl_ffmpeg_codec::cur_frame() const in vidl_ffmpeg_codec.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [lib/libvidl.dylib] Error 1 make[1]: *** [core/vidl/CMakeFiles/vidl.dir/all] Error 2 make: *** [all] Error 2 }}} -- Ticket URL: <http://trac.macports.org/ticket/17792> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 10

[MacPorts] #19004: Sticky versions?
by MacPorts 24 Apr '10

24 Apr '10

#19004: Sticky versions? --------------------------------------+------------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts 1.7.1 Component: ports | Version: 1.7.0 Keywords: | Port: --------------------------------------+------------------------------------- Is it possible to tag a port in a way that makes "port upgrade outdated" not upgrade the port in question? This is possible with other package managing tools, such as apt. I ask because Subversion was recently updated to version 1.6. This makes Subversion integration in Eclipse (and possibly other IDE's) fail, since it doesn't recognize Subversion 1.6's file format. I had to downgrade to 1.5 to make everything work again. It would have been great if I could just tag my current Subversion install (1.5.5_0) as being sticky. -- Ticket URL: <http://trac.macports.org/ticket/19004> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #16808: RFE: saving/restoring installed ports
by MacPorts 24 Apr '10

24 Apr '10

#16808: RFE: saving/restoring installed ports ------------------------------+--------------------------------------------- Reporter: romy2k(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts base enhancements Component: base | Version: 1.6.0 Keywords: | Port: ------------------------------+--------------------------------------------- Would be great to be able to save a list of installed ports, with variants, to then restore with a single command on another machine. This includes subsets of ports. Would greatly help with migration, fresh installs, etc. -- Ticket URL: <http://trac.macports.org/ticket/16808> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #16745: Allow macports to compile with apple's gcc 4.2
by MacPorts 24 Apr '10

24 Apr '10

#16745: Allow macports to compile with apple's gcc 4.2 -------------------------------------------------+-------------------------- Reporter: illogical1(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: fix compilation gcc 4.2 apple-gcc42 | Port: expat giflib ilmbase jasper lcms libgpg-error libvorbis lzmautils openexr subversion tiff flac pth -------------------------------------------------+-------------------------- The following Portfile patches allow compilation with apple's gcc 4.2. Tested on 10.4. -- Ticket URL: <http://trac.macports.org/ticket/16745> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 11

[MacPorts] #17157: Update PortIndex incrementally so it is always current
by MacPorts 23 Apr '10

23 Apr '10

#17157: Update PortIndex incrementally so it is always current ----------------------------------+----------------------------------------- Reporter: frstan(a)bellsouth.net | Owner: wsiegrist(a)apple.com Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts base enhancements Component: server/hosting | Version: 1.7.0 Keywords: portindex update | Port: ----------------------------------+----------------------------------------- On Nov 9, 2008, at 9:03 AM, William Davis wrote: Commit by ryandesign(a)macports.org :: r41701 /trunk/base/src/port/portindex.tcl: (link) http://trac.macports.org/changeset/41701 portindex.tcl: Generate the port index in a temporary file first, then replace the PortIndex file all at once; fixes #16234 If this is the case cant we easily update the index more than twice a day now? Perhaps even every half hour? portindex is an annoyingly expensive operation. I don't know if the added load on the macports servers would be worth it? If someone gets around to implementing an incremental portindex option (say we store the index in an sqlite database and we add a post-commit hook that just updates the index entries for the ports that were just committed) then we could probably have an always up-to-date index without the huge resource requirements. -- Daniel J. Luke ticket filed by W Davis -- Ticket URL: <http://trac.macports.org/ticket/17157> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7