Le 15 août 07 à 16:23, Lorin Rivers a écrit :
I've noticed some of the ports that are triggering this getting fixed right away. What does this disposition indicate?
---------- Forwarded message ---------- From: MacPorts <trac@macosforge.org> Date: Aug 14, 2007 6:40 PM Subject: Re: [MacPorts] #12476: cadaver install fails with mtree violation To: lrivers@gmail.com
#12476: cadaver install fails with mtree violation -------------------------------- +------------------------------------------- Reporter: lrivers@gmail.com | Owner: macports-dev@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.5.0 Resolution: | Keywords: cadaver mtree -------------------------------- +------------------------------------------- Changes (by ryandesign@macports.org):
* milestone: => Port Bugs * cc: => lrivers@gmail.com, landonf@macports.org
-- Ticket URL: <https://trac.macports.org/projects/macports/ticket/12476> MacPorts </projects/macports> Ports system for Mac OS
They tell us that the ticket describe a port bug, nothing more, nothing less. -- Anthony Ramine, the infamous MacPorts Trac slave. nox@macports.org