Re: FreeBSD ports disabled for bsdforge

From: Chris <portmaster_at_bsdforge.com>
Date: Fri, 12 Jan 2024 17:30:28 UTC
On 2024-01-12 06:44, Alexey Dokuchaev wrote:
> On Fri, Jan 12, 2024 at 02:00:04PM +0000, Jamie Landeg-Jones wrote:
>> Chris <portmaster@bsdforge.com> wrote:
>> ...
>> > NO! I missed the domain renewal by 5 days. So domain went unavailable.
>> > I fixed it on the 6th day.
>> 
>> I thought it was a bit rash of them to do all that so soon (it was obvious
>> that the domain hadn't expired completely, as I could see that you renewed
>> it before it was returned to being "unused".)
> 
> It was very rash, but for endangered ports, they'll use any possibility.
> 
>> I did find some other commits too, where ports have either had the
>> maintainer changed, or marked broken.
>> 
>> https://cgit.freebsd.org/ports/log/?qt=grep&q=bsdforge
> 
> Yeah, Chris should probably review all those undue commits and ask them
> to be reverted, at least the deprecation/maintainer resets.
> 
>> I did ping both Daniel and Muhammad the day before I emailed you, but
>> neither have responded!
> 
> Muhammad seldom responds to email these days; for both of them I believe
> this situation (Chris' domain renewal and him coming back online) is
> uncomfortable as they both want for his ports to die ASAP. :(
> 
> /danfe
Thanks for the reply Alexey!
IMHO this (excluding you && Jamie) seems a bit political. Or at least 
unprofessional. :(
Which leaves my only recourse to whip up some 50 pr(1)'s to correct this. 
Which ultimately
results in a great deal more work for /everyone/. :(

Thanks again.

--Chris