On 2014/11/10 08:03, Ryan Schmidt wrote:
>
> Are you sure just increasing the epoch is sufficient? Usually the version or
> revision should be increased when replacing a port.
>
>
I was [following the advice of step 4 in the PortfileRecipes][1],
without really understanding what sort of beh
> On Nov 9, 2014, at 9:50 AM, easie...@macports.org wrote:
>
> Revision
> 127967
> Author
> easie...@macports.org
> Date
> 2014-11-09 07:50:16 -0800 (Sun, 09 Nov 2014)
> Log Message
>
> bitcoind: obsolete in favor of bitcoin
> Modified Paths
>
> • trunk/dports/finance/bitcoind/Portfile
>
On 2014-11-10 09:33 , Clemens Lang wrote:
> Hi Shree,
>
> it seems there's something wrong with PortIndex generation on the MacOSForge
> servers. There are ports missing from the PortIndex we ship to our users, see
> https://trac.macports.org/ticket/45742.
>
> Can you take a look? Did you see any
Hi Shree,
it seems there's something wrong with PortIndex generation on the MacOSForge
servers. There are ports missing from the PortIndex we ship to our users, see
https://trac.macports.org/ticket/45742.
Can you take a look? Did you see any error messages come up recently? Can you
trigger re-cre
