Date: Sat, 6 May 2023 14:03:00 -0700 From: Gary Aitken <freebsd@dreamchaser.org> To: Arthur Chance <freebsd@qeng-ho.org>, Yuri <yuri@aetern.org>, freebsd-questions@freebsd.org Subject: Re: Error in vm manpage Message-ID: <b040e748-87c2-e18d-df53-986f13f51994@dreamchaser.org> In-Reply-To: <1a48dbcf-71ba-69a0-c010-f16b11d14628@qeng-ho.org> References: <2986dfd0-ac48-9793-f480-84c8e6f4d222@Gmail.com> <f1994bbd-0516-6cf5-13ff-74816bf1620d@qeng-ho.org> <4763e87b-86bb-8756-4d67-febc6c3d6b04@aetern.org> <1a48dbcf-71ba-69a0-c010-f16b11d14628@qeng-ho.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/6/23 09:21, Arthur Chance wrote: > Maybe it's time I regenerated my ports rather than just updating them. > It would appear portsnap doesn't necessarily delete old ports as I have > both ports on my system and my last portsnap update was just after > midnight today. > > Also ports.freebsd.org doesn't seem to be up to date on these ports. I'm not dead certain on this but I think this is about the time when the tree is being updated, so it may be in a state of flux. Although if the change is not recent that wouldn't be what you're seeing. I've had problems in the past where waiting a few hours and then things showed up. Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b040e748-87c2-e18d-df53-986f13f51994>