June 2008 - macports-tickets - lists.macosforge.org

[MacPorts] #15397: libuninum distfile changed
by MacPorts 08 Jun '08

08 Jun '08

#15397: libuninum distfile changed --------------------------------+------------------------------------------- Reporter: simon(a)macports.org | Owner: mww(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | --------------------------------+------------------------------------------- Hi, the checksums for the libuninum distfile have changed: {{{ Portfile: sha1 3886b511b9f7e8a84efc16bc8e03bb676ce7104e Now: sha1 03e0390da91a0c3242da7d36cb21285906663066 }}} The new distfile compiles fine for me, but please look into it. Thanks, Simon -- Ticket URL: <http://trac.macports.org/ticket/15397> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

Re: [MacPorts] #14761: Cannot build proctools on Leopard
by MacPorts 07 Jun '08

07 Jun '08

#14761: Cannot build proctools on Leopard ---------------------------------+------------------------------------------ Reporter: akira(a)macports.org | Owner: akira(a)macports.org Type: defect | Status: assigned Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: leopard proctools kvm ---------------------------------+------------------------------------------ Comment (by akira(a)macports.org) Thanks guys! I'll look into this. -- Ticket URL: <http://trac.macports.org/ticket/14761#comment:11> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #15205: tokyocabinet update request
by MacPorts 07 Jun '08

07 Jun '08

#15205: tokyocabinet update request ---------------------------------+------------------------------------------ Reporter: akira(a)macports.org | Owner: akira(a)macports.org Type: enhancement | Status: closed Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Resolution: fixed | Keywords: ---------------------------------+------------------------------------------ Changes (by akira(a)macports.org) * status: new => closed * resolution: => fixed Comment: maintainer timeout. Committed in r37441 See also: ticket:15548 -- Ticket URL: <http://trac.macports.org/ticket/15205#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #13244: clisp does not build on 10.5 MacBook Pro; fails with "CPPFLAGS has changed"
by MacPorts 07 Jun '08

07 Jun '08

#13244: clisp does not build on 10.5 MacBook Pro; fails with "CPPFLAGS has changed" ------------------------------------+--------------------------------------- Reporter: jaroom(a)mindspring.com | Owner: eridius(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.5.0 Resolution: | Keywords: clisp ------------------------------------+--------------------------------------- Comment (by anthony.hw.kong(a)gmail.com) Same happened to mine (10.5.3). Here is the uname output. Darwin mymac 9.3.0 Darwin Kernel Version 9.3.0: Fri May 23 00:49:16 PDT 2008; root:xnu-1228.5.18~1/RELEASE_I386 i386 -- Ticket URL: <http://trac.macports.org/ticket/13244#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #11759: BUG: case-sensitive port uninstall
by MacPorts 07 Jun '08

07 Jun '08

#11759: BUG: case-sensitive port uninstall ------------------------------------+--------------------------------------- Reporter: yunzheng.hu(a)gmail.com | Owner: eridius(a)macports.org Type: defect | Status: assigned Priority: High | Milestone: MacPorts 1.6.1 Component: base | Version: Resolution: | Keywords: port uninstall case-sensitive ------------------------------------+--------------------------------------- Changes (by jmr(a)macports.org) * cc: pguyot(a)kallisys.net (added) Comment: I think that raimue's patch should actually be applied as well. The flat- file registry prevents us from having ports with names that differ only in case when running on a case-insensitive filesystem (even if we considered allowing them a good idea). My patch extends that restriction to case- sensitive filesystems. I made sure to use the canonical name whenever possible, but it's pretty easy to end up using the name as entered by the user, so it could easily happen in future code, breaking things again. We should therefore make the filemap treat port names case-insensitively as well. Of course, my reasoning falls down if the filemap code is used for anything other than associating file paths with port names. Is it? -- Ticket URL: <http://trac.macports.org/ticket/11759#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #14123: base-1.6.0 "port uninstall" left installed files at case-sensitive FS
by MacPorts 07 Jun '08

07 Jun '08

#14123: base-1.6.0 "port uninstall" left installed files at case-sensitive FS ----------------------------+----------------------------------------------- Reporter: ononon(a)csc.jp | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Low | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: ----------------------------+----------------------------------------------- Changes (by jmr(a)macports.org) * cc: jmr(a)macports.org, pguyot(a)kallisys.net (added) Comment: The attached patch should do what you're asking for. Paul, you wrote this code—will this break anything? -- Ticket URL: <http://trac.macports.org/ticket/14123#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

[MacPorts] #15545: ImageMagick-6.4.1-5 - checksum mismatch
by MacPorts 07 Jun '08

07 Jun '08

#15545: ImageMagick-6.4.1-5 - checksum mismatch ----------------------------------+----------------------------------------- Reporter: face(a)centosprime.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | ----------------------------------+----------------------------------------- {{{ ---> Fetching ImageMagick ---> Attempting to fetch ImageMagick-6.4.1-5.tar.bz2 from http://internap.dl.sourceforge.net/imagemagick ---> Verifying checksum(s) for ImageMagick Error: Checksum (md5) mismatch for ImageMagick-6.4.1-5.tar.bz2 Error: Checksum (sha1) mismatch for ImageMagick-6.4.1-5.tar.bz2 Error: Checksum (rmd160) mismatch for ImageMagick-6.4.1-5.tar.bz2 Error: Target org.macports.checksum returned: Unable to verify file checksums Error: Status 1 encountered during processing. }}} -- Ticket URL: <http://trac.macports.org/ticket/15545> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

Re: [MacPorts] #15052: pango: Font display problems when compiled against cairo 1.6.4
by MacPorts 07 Jun '08

07 Jun '08

#15052: pango: Font display problems when compiled against cairo 1.6.4 --------------------------------+------------------------------------------- Reporter: mike(a)it-loops.com | Owner: ryandesign(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: Resolution: | Keywords: --------------------------------+------------------------------------------- Comment (by ryandesign(a)macports.org) Replying to [comment:16 macports(a)flyn.org] > I would like to see a cairo variant build the Quartz font backend without the freetype backend. Once the Quartz GTK2 stack is stable, freetype should be unnecessary (two font engines is quite redundant) unless one wants to use X11 applications for their network-centricity. I think using "quartz" (build quartz & avoid freetype) and "no_x11" (avoid X11) like the GTK2 port will avoid confusion. A variant called "quartz" will make people think they need to use that variant to get Quartz functionality, which isn't true; Quartz functionality is always enabled on Mac OS X, since cairo 1.6.x. In MacPorts we usually like to build ports with maximal functionality. In this case, that would be a cairo port that supports as many backends as possible. That's what I do now. I could probably add a variant to disable fontconfig support, if there's a strong desire for that. Such a request should be made in a separate ticket. Note that all software that uses cairo must be written to support all backends. You can't just compile cairo with Quartz support and expect all cairo-using applications to know how to use Quartz. Each app must be written for this. Not all apps are. So there will likely be some cairo-using apps that need fontconfig. Even if today you only need GTK2 with only Quartz support, tomorrow you may want to install an unrelated app which happens to require cairo with fontconfig. So why not install a cairo with all possible backends in the first place? Which is what we offer now. (Except for glitz support. Which is in a variant. I don't know anything about glitz.) > GTK2's Portfile even says "cairo must be installed with the quartz variant enabled." That must be from the cairo 1.4.x days, when quartz support was still experimental, disabled by default, and therefore in a variant. In cairo 1.6.x, the Quartz backend was marked stable, and enabled by default, therefore I removed the variant and integrated it into the core port. -- Ticket URL: <http://trac.macports.org/ticket/15052#comment:17> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #15052: pango: Font display problems when compiled against cairo 1.6.4
by MacPorts 07 Jun '08

07 Jun '08

#15052: pango: Font display problems when compiled against cairo 1.6.4 --------------------------------+------------------------------------------- Reporter: mike(a)it-loops.com | Owner: ryandesign(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: Resolution: | Keywords: --------------------------------+------------------------------------------- Comment (by macports(a)flyn.org) Okay, good. I think we've got this bug figured out then.[[BR]] [[BR]] I would like to see a cairo variant build the Quartz font backend without the freetype backend. Once the Quartz GTK2 stack is stable, freetype should be unnecessary (two font engines is quite redundant) unless one wants to use X11 applications for their network-centricity. I think using "quartz" (build quartz & avoid freetype) and "no_x11" (avoid X11) like the GTK2 port will avoid confusion. GTK2's Portfile even says "cairo must be installed with the quartz variant enabled." -- Ticket URL: <http://trac.macports.org/ticket/15052#comment:16> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #15146: Upgrade scons to 0.98.2 and change to use python25
by MacPorts 06 Jun '08

06 Jun '08

#15146: Upgrade scons to 0.98.2 and change to use python25 ------------------------------+--------------------------------------------- Reporter: aronnax(a)umd.edu | Owner: landonf(a)macports.org Type: enhancement | Status: closed Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Resolution: fixed | Keywords: scons, python25, python_select ------------------------------+--------------------------------------------- Changes (by jmr(a)macports.org) * status: new => closed * resolution: => fixed Comment: Updated to 0.98.4 in r37414. -- Ticket URL: <http://trac.macports.org/ticket/15146#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0