From owner-freebsd-questions@freebsd.org Sat Aug 22 06:22:27 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 B090F3AF30B for ; Sat, 22 Aug 2020 06:22:27 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (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 4BYSwf4Vxvz4D0d for ; Sat, 22 Aug 2020 06:22:26 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([178.12.118.210]) by mrelayeu.kundenserver.de (mreue009 [212.227.15.167]) with ESMTPA (Nemesis) id 1MaIvV-1k6MfN2aCD-00WF82; Sat, 22 Aug 2020 08:22:16 +0200 Date: Sat, 22 Aug 2020 08:22:15 +0200 From: Polytropon To: Gary Aitken Cc: RW , freebsd-questions@freebsd.org, freebsd@edvax.de Subject: Re: portsnap belated complaint? Message-Id: <20200822082215.ed661720.freebsd@edvax.de> In-Reply-To: <1910cebb-026d-ee47-e793-23dc89ed4fe6@dreamchaser.org> References: <332bdd11-40f3-b5af-7683-aca6494abe6e@dreamchaser.org> <20200821193243.622b63e5@gumby.homeunix.com> <1910cebb-026d-ee47-e793-23dc89ed4fe6@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:tG+Nw3WhdTIpIsF3hpknaoDZpimb/mQBEzRK20MP90X0ot1o7/y rVk4nmxwk31PvQSw0Jwgh+ltk2cIkKIHt4bDA+ePPV+lzQGR5e1oN4AAn9dhcyaI7AMuzbT Cme+MVR09cHZGKTrKRuP/sGAHY913lhEzfgUIOr+s46H3nvgx3TFZOxbuF50pgbot8JE1pH Xxd+Qi0rWvNOa0EY+JTrg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:pMDTEgBOMC8=:+C27OEU08xOpljGtlZHiie as0grzkpqwkyhF7nCUtXnKXJILwyOKA6QelRFvJCZ4xUhO9KZfHosJYoz9i6v455s71Y6h+BM 9Mnbngnkv7qrYLnlg0CKNCkiO9XRapFp1Q7NEQHt7DERRP06n3y4HPrpvZWqxtFSq3GUQnutx IUMAw4kyU3RTrJGaMIS1ZI7T0wTh01Enh9iJsa2td3LEZzo/31wqdOz0UuHsi8KG+XvHVm7M6 co2Iw1Z7eYtKMCNNfLejq3hodx4+zq/LvRTi862SXRXkz+tguyA4NtJRIMt3wC0u1D4ZkJiEP BEXK776AUiVPX7j+W1lwTjMXREX9lpLjB1zDbIXOxNWyJC9aJgOTgLj7PC+fCdnsJ/E3tPPSx R8BOl2ki1zbKCWbc71nwGY67lGsK5MF/QoY8syqxHhO8NZjsbDkmHvi52ogjFkcOhpojd/T9m SnWCdExw9NtBVsjaFpId9ittSsWvsM8hKhtUrKzPXQlh3PGYH+TK9NKkWpzCT4d+QeLQkAEvg d53E3CqltIyTNvIjBSxUdCPs5W7LefVXKUCJjSx/reFcQo83c4PrMB76Ggsar+3KOgcubBnTw jdyejUyRUHqcVtvlyci6HxOtrsJUqitT8CEWhLWpnCxWa3UAwNO/d9da6uqa14Zz26J767WoT sgcyn2r4r2PR7rUtU09ZdyS/SFQ7yCBsCo/JfEOyxa8TM32A84LfuBi3TZ1R3A1lEGAYcH5DA UoO+fv8tSEWchxoY9ggBWIHjgV+mb6+OsBhauFKluDuLEm3sMuNb5kgUEtBwuzMeZRYuFsI/e VMh94YeOMysjmNG8iyYoix+mjvq45IlELI8w4FFpn4/6+Kp33QKM5O6tlPe5VjBBNHzc/Ci X-Rspamd-Queue-Id: 4BYSwf4Vxvz4D0d 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.126.187) smtp.mailfrom=freebsd@edvax.de X-Spamd-Result: default: False [3.38 / 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)[]; NEURAL_HAM_SHORT(-0.02)[-0.018]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; RECEIVED_SPAMHAUS_PBL(0.00)[178.12.118.210:received]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[212.227.126.187:from]; RCVD_TLS_LAST(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_POSSIBLE(0.00)[212.227.126.187:from]; FREEMAIL_CC(0.00)[googlemail.com,freebsd.org,edvax.de]; 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: Sat, 22 Aug 2020 06:22:27 -0000 On Fri, 21 Aug 2020 22:17:51 -0600, Gary Aitken wrote: > On 8/21/20 12:11 PM, Polytropon wrote: > >> ... > >> 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'. > > How can it apply patches if an extract hasn't been done and is needed? > Does it knowingly, by default, apply patches to a tree it knows is "bad"? > In this case, bad may simply mean installed at sysinstall time? > Is that a known/documented behavior people rely on? The core "problem" is that portsnap can only operate on trees that originate from a portsnap run. It cannot use ports trees installed from scratch (i. e., from the installation medium), or on such obtained via SVN. As explained in "man 8 portsnap", the operations "fetch", "extract" and "update" require a certain order and have "limited" results: "fetch" only fetches the snapshot, "extract" puts it into place, and "update" alters a ports tree according to a previously "fetch"ed snapshot. The initial observation leads me to believe that the ports tree that has been tried to update was not written by portsnap, which is also suggested by its error message. > > 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 > ... > > I'll assume it's all the result of installing ports with a new sysinstall > months ago; I thought I had extracted and updated and used it already. Exactly my impression. A ports tree that comes from bsdinstall is not something that portsnap can operate on. > Why doesn't the ports install done at sysinstall time not do the equivalent > of a fetch & extract? Would doing so be incompatible with anything else? Because at installation time, the ports tree that was current at the point of RELEASE is shipped on the installation medium. This is different from what portsnap expects, that's why the suggestion to _if_ you want to use portsnap, always start with a fresh snapshot, removing any /usr/ports that might already be there ("might", because the ports tree is optional and can be omitted during installation). > (I think this is the third time I've gotten caught by this stupid > behavior. I guess it's a moot point since portsnap is going away.) THe same applies when you use SVN to get "more fine grained" updates - you also need to start with a fresh copy created by SVN. Those methods are not interoperable. :-) > Does installing the ports tree when the system is installed and then > using portsnap count as mixing tools? Yes. The tree installed by bsdinstall is not usable for any further use with portsnap. > If so, it should be noted when the > option is presented at install time that if you are planning on updating the > ports tree, there's no point in installing it. That is absolutely understandable. As I've mentioned, any updating method, be it portsnap or svn, requires that you start with a clean new snapshot or checkout of /usr/ports. Installing the ports tree with bsdinstall only makes sense if you want to keep using _that_ version of the ports tree (i. e., the version of the tree that was current when the FreeBSD version was released). > Will this same behavior exist with the switch to git? I almost would think so. The suggestion will probably be: Remove /usr/ports, and then initialize the ports tree from scratch using git... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...