[MacPorts] #13343: grep 2.5.3_0 won't install;
2.5.1a_1 worked fine
MacPorts
trac at macosforge.org
Tue Nov 20 21:29:17 PST 2007
#13343: grep 2.5.3_0 won't install; 2.5.1a_1 worked fine
--------------------------------------+-------------------------------------
Reporter: ryandesign at macports.org | Owner: waqar at macports.org
Type: defect | Status: assigned
Priority: Normal | Milestone: Port Bugs
Component: ports | Version: 1.6.0
Resolution: | Keywords:
--------------------------------------+-------------------------------------
Comment (by jmpp at macports.org):
Replying to [comment:7 spovich at gmail.com]:
> Replying to [comment:6 ryandesign at macports.org]:
> You can't reply to a ticket without being logged in. It is probably
different permissions or regular users vs committers. For
> me, the whole top section of the ticket view is not editable, the only
option available for a ticket is to post comments like
> this ;-)
Yes, it's a different set of permission for project members, they are
naturally allowed to tweak more ticket details than those solely holding
trac accounts. We're working on a new setup to allow some aspects of a
ticket to be editable by just anyone with any type of account, like the Cc
field, working our way up from there in a more fine-grained fashion to
full ticket modification privileges depending on who you are and your
affiliation to your project... but we aint there just yet ;-) Such a
system is still in the cooking, sorry about that!
>
> It also looks like once you post a comment, you get cc'd on future
updates to the ticket even if you aren't on the cc list.
>
Please don't count on that behavior, it may likely change in the future to
only those on the Cc field (plus reported and assignee, of course) being
notified of ticket updates.
-jmpp
--
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13343#comment:10>
MacPorts </projects/macports>
Ports system for Mac OS
More information about the macports-tickets
mailing list