Date: Fri, 21 Aug 2020 19:32:43 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: portsnap belated complaint? Message-ID: <20200821193243.622b63e5@gumby.homeunix.com> In-Reply-To: <332bdd11-40f3-b5af-7683-aca6494abe6e@dreamchaser.org> References: <332bdd11-40f3-b5af-7683-aca6494abe6e@dreamchaser.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 21 Aug 2020 11:42:23 -0600 Gary Aitken wrote: > Can someone explain why the portsnap update below seems to have > succeeded (patches applied), but then afterwards I get the message > about needing to run portsnap extract? > > 11.3-RELEASE-p6 (upgraded from 10.something some time ago) > I believe the ports tree was generated when the OS was installed, but > not sure. I'm also not sure how /usr/ports was upgraded after the OS > upgrade. It wont be updated by when updating base. > # portsnap fetch This updates the compressed snapshot under /var, not the actual tree. > Extracting snapshot... done. ... > /usr/ports was not created by portsnap. > You must run 'portsnap extract' before running 'portsnap update'. portsnap has first to write the full tree with a "portsnap extract" This also writes a hidden data file that identifies file or port versions under that tree. Once that file is in place you use "update" instead. In general it's not a good idea to mix tools on the same tree or adopt a tree, so I'd delete everything under /usr/ports and run: portsnap fetch extract you then subsequently update with portsnap fetch update
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200821193243.622b63e5>