Re: *-graveyard ports retired

2019-10-01 Thread Joshua Root
On 2019-10-1 21:27 , Renee Otten wrote: > If the conclusion is that replacements from, for example, > py34- to py35- are not useful (as it appears from > https://trac.macports.org/ticket/59051) then this change seems fine to > me. In that case we should recommend maintainers (likely in the guide or

Re: *-graveyard ports retired

2019-10-01 Thread Renee Otten
If the conclusion is that replacements from, for example, py34- to py35- are not useful (as it appears from https://trac.macports.org/ticket/59051 ) then this change seems fine to me. In that case we should recommend maintainers (likely in the guide or on

Re: *-graveyard ports retired

2019-09-30 Thread Joshua Root
On 2019-10-1 06:44 , Mojca Miklavec wrote: > On Mon, 30 Sep 2019 at 22:36, Joshua Root wrote: >> >> The p5-graveyard and py-graveyard ports have been removed as they no >> longer serve a useful purpose. The buildbot skips replaced ports >> automatically and thus doesn't generate the error reports t

Re: *-graveyard ports retired

2019-09-30 Thread Mojca Miklavec
On Mon, 30 Sep 2019 at 22:36, Joshua Root wrote: > > The p5-graveyard and py-graveyard ports have been removed as they no > longer serve a useful purpose. The buildbot skips replaced ports > automatically and thus doesn't generate the error reports that motivated > the creation of the graveyards.

*-graveyard ports retired

2019-09-30 Thread Joshua Root
The p5-graveyard and py-graveyard ports have been removed as they no longer serve a useful purpose. The buildbot skips replaced ports automatically and thus doesn't generate the error reports that motivated the creation of the graveyards. If you believe that setting replacements is useful for the