Date: Fri, 12 Jan 2024 14:00:04 +0000 From: Jamie Landeg-Jones <jamie@catflap.org> To: portmaster@bsdforge.com, jamie@catflap.org Cc: freebsd-ports@freebsd.org Subject: Re: FreeBSD ports disabled for bsdforge Message-ID: <202401121400.40CE04P1085845@donotpassgo.dyslexicfish.net> In-Reply-To: <4ae511b8cf4e21ecfa8b4283ea369f6f@bsdforge.com> References: <202401111126.40BBQgJ4028906@donotpassgo.dyslexicfish.net> <4ae511b8cf4e21ecfa8b4283ea369f6f@bsdforge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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".) But I didn't realise it was only 6 days! Jeeze, I have many PR's that haven't been looked at it months! > Thanks! I'll try to reverse this. Did I miss a pr(1) too? I haven't noticed a PR. I only noticed because I was reinstalling a machine, and a number of ports suddenly became unfetchable, so I checked, and that is what I found! 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 I did ping both Daniel and Muhammad the day before I emailed you, but neither have responded! Hope this helps, Cheers, Jamie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202401121400.40CE04P1085845>