From owner-freebsd-questions@freebsd.org Fri Aug 21 18:11:57 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C94DB3C477C for ; Fri, 21 Aug 2020 18:11:57 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BY8jm52fTz4JLF for ; Fri, 21 Aug 2020 18:11:56 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([178.12.112.48]) by mrelayeu.kundenserver.de (mreue106 [212.227.15.183]) with ESMTPA (Nemesis) id 1MKbwg-1juwQ92qMu-00KttD; Fri, 21 Aug 2020 20:11:45 +0200 Date: Fri, 21 Aug 2020 20:11:45 +0200 From: Polytropon To: freebsd@dreamchaser.org Cc: FreeBSD Mailing List Subject: Re: portsnap belated complaint? Message-Id: <20200821201145.79990198.freebsd@edvax.de> In-Reply-To: <332bdd11-40f3-b5af-7683-aca6494abe6e@dreamchaser.org> References: <332bdd11-40f3-b5af-7683-aca6494abe6e@dreamchaser.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:WBAbY4d5oUWqsU1XVq50SUdRrmFl6557gQVn9L5wIUMfP8X64QE N89D0eve3vTjzdLwCuYNUEQUDSsdRv014HA53o4bBCSgTYK4qMfOYZ0tecmXcmJj0yGV1In HdPW1SSKy3cwMwzhpRlmuV84evcsFflho8yRSEW5Rbh6hHaJxRmypcORAFLqNjzHMuhClRx WQVc2QXYnaNL0NPOOWgDw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:5ud/tNdp194=:ziYypiGhIc+3KoY3BLPECz WKaopYSIjVPF/FeJPChd39vAgs24lmL+bCaZYfbJQw7MZuHNUxxQFiNTKeS6s3AuGIuDKcYTQ X51mLVXfblEpLKqUyZv7MW7IxO6d8Q8YvUIDAJx+d+w7K4Nb7asrtu4dCaAQ5Rr1pcZtRVbNL 2usbm4lsOoCDBgWamHodm8vuDOSgMIYrHCjfTcLKfI157JHGX4ID2RlAOfkYrPpgXxymLTx8Q bcmROb3t61jN3wrgSngMzsqPbBpLbKEAMWCwetd4FFBhnpXM6xxucN2rLBb9TsSwUrF9BVdVS pCqyQRlSvLYXKQIaVTnmIc0dp8LsQ366/EhIAcftCxzKfxUNSP/2nY4b0iz2Ic7p550LFtbI8 5GkZzB+6goLNW02aWVDkkYPqtQlHWPhQodqL7ep7/sGzC5iu0qgf6ssrxtLMmeQe6sAx2Brl8 v02iH2x/exCq7aGOL/WMnhSWgqAxMyKaUoCbZS/qHKYQ/MEySEmVNNJj2u9JlfUp1allqdxlb ocyyZfQkCJmZby5nMl7ckMBBpg37k/OruJyjbnzh2mVviDoaS3jEoaXNnvAqUGh7czI1+RAYJ YZvGaulvC27DDmQAHGAMIEbrTonQ5kYaorbSwpB8iWVhRektS+BGcc7MHBfmWw19YPO7eIcP7 toOK/67GvWVr1QhwraHMIXzsoTJlxzxgYj0RBZtT4pCNmluS5gyMKGyxC4W5yZd/o/C2FErDb KwdiBH6zGIQrUZWck+Djn9dR4mjj8s28xrA1JeBiV/GlRzgit5mLmJZyp+3mXPieiNH2Wr1Hp Er1GouhswanrJiUUUthmnBQIeMXJIIpD3ChB/UWpAFFmOTK7DMeUORvB4E1FA8cVjBSeZS4lH r/pv1Db5yR0cMNW0SeTFfyQYZtIEeJcuM0ck1VD7gWUTCC2NSqGGeEyT04savww6oIfZb1g4f PEnnZOKK65uCj9aCTdNBZ/vmCzHHwNqCqrEf4kjI74xO5EBZVIcTdbrPwccMXWrG188nsZHuQ uWO81Hxg2val1dqV8Tt+rYxtBHKLFz24nXjI/Zm05dcC9DVxHLuerVxewCYSL7SgUWfXrr05R V9adk3+yWnbAcSBua4dKJmCbQDc3uiME9SaomBxK06znRlFdPFobDM+mhj56xNVpzhhJsmYUp cariAr7CShRt+2Gu7yGQ/S+O15IryLg3Gl09TizjvCxQ57zP80LlWdqQTfXIW45Phz+SsXK1w 5kEPHrkbOHtzcQKm2 X-Rspamd-Queue-Id: 4BY8jm52fTz4JLF X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@edvax.de has no SPF policy when checking 212.227.17.10) smtp.mailfrom=freebsd@edvax.de X-Spamd-Result: default: False [4.85 / 15.00]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RECEIVED_SPAMHAUS_PBL(0.00)[178.12.112.48:received]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.06)[0.062]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.56)[0.563]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.82)[0.825]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[212.227.17.10:from]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_POSSIBLE(0.00)[212.227.17.10:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Aug 2020 18:11:57 -0000 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. > > # portsnap fetch > ... > Extracting snapshot... done. > ... > Ports tree hasn't changed since last snapshot. > No updates needed. > You did not extract it. > # portsnap fetch update No, that invocation is correct. > ... > Fetching 4 metadata patches... done. > Applying metadata patches... done. > Fetching 0 metadata files... done. > Fetching 22 patches. > (22/22) 100.00% done. > done. > Applying patches... > done. > Fetching 2 new ports or files... done. > /usr/ports was not created by portsnap. > You must run 'portsnap extract' before running 'portsnap update'. According to the manual "man 8 portsnap": fetch Fetch a compressed snapshot of the ports tree, or update the existing snapshot. This command should only be used inter- actively; for non-interactive use, you should use the cron command. extract Extract a ports tree, replacing existing files and directo- ries. NOTE: This will remove anything occupying the loca- tion where files or directories are being extracted; in par- ticular, any changes made locally to the ports tree (for ex- ample, adding new patches) will be silently obliterated. Only run this command to initialize your portsnap-maintained ports tree for the first time, if you wish to start over with a clean, completely unmodified tree, or if you wish to extract a specific part of the tree (using the path option). update Update a ports tree extracted using the extract command. You must run this command to apply changes to your ports tree after downloading updates via the fetch or cron com- mands. Again, note that in the parts of the ports tree which are being updated, any local changes or additions will be removed. Something went wrong in your case. You probably should remove /usr/ports and obtain a fresh copy using the "fetch" and "extract" operations to make sure the snapshot is okay. Further updates to that snapshot can then be obtained using the "fetch" and "update" operation. You can find examples in the EXAMPLES section. :-) Also see chapter 4.5 of The FreeBSD Handbook, procedure 4.1: https://www.freebsd.org/doc/handbook/ports-using.html Everything you see matches the expected behaviour according to your problem description: > I believe the ports tree was generated when the OS was installed, > [...] > # portsnap fetch > [...] > # portsnap fetch update > [...] > /usr/ports was not created by portsnap. Whatever you have fetched, it was never extracted; what is still present in /usr/ports is not "compatible" with portsnap, that's why my suggestion to start with a fresh snapshot as explained above. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...