From owner-freebsd-questions@freebsd.org Thu Nov 15 20:38:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6CD311108EC8 for ; Thu, 15 Nov 2018 20:38:59 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF76A7D370 for ; Thu, 15 Nov 2018 20:38:58 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm1-x32c.google.com with SMTP id r63-v6so20169204wma.4 for ; Thu, 15 Nov 2018 12:38:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=wCuruzBPW5H5K18/Sb6M3xUvK9e5IpO3x6oBbDeVSfg=; b=QNXAzdqcnOaWMGq2OVZzFkBHvM1kv3xZrd30SxpPP0CaD6+1DeGuIfp3Vrc70izen2 DBljsL/jcTSV2X8Ue55vjn+S3JG4j2cmh70wIwqW04/6gSqR7rf/9XBzVOR/KfOkafCJ DJLsD5cYxWkdoCyMLUYU2W9ZaT+S8CzFKgplXuyKtI1TVTRo4dXtvnNFBsZl0RBGhMYQ OD9pnAaIkLxZ6KgYQYuhgHJ9dFMZONOvBuI+0Na5AsGofmvBCM/d4L+t1QZPXO95BSWK amvsmpmRH03QLsFoqAhUnlzUgQi+3daBFJ45H4Dtw5NV0wvUjJFrMOjoV54Vnt/iDOhN ZI1w== X-Gm-Message-State: AGRZ1gIqATO+0c2d2fwHNj/vzDHMy4x97vOvqZLA+Jo4r8wpiQgTjoZW fB4tpMrRo57FqWVOUY2MI0n4ZJ9Dr8A= X-Google-Smtp-Source: AJdET5fh0v5Zm1sLmEA+qx1uJa8bH88sBKeabR1LqzEGqhZ6rlloGMZvOAhWeLdanpFpUTGwfT2+3Q== X-Received: by 2002:a1c:34d1:: with SMTP id b200-v6mr382800wma.115.1542314337220; Thu, 15 Nov 2018 12:38:57 -0800 (PST) Received: from gumby.homeunix.com ([90.211.70.103]) by smtp.gmail.com with ESMTPSA id j195-v6sm13430763wmf.13.2018.11.15.12.38.55 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 15 Nov 2018 12:38:56 -0800 (PST) Date: Thu, 15 Nov 2018 20:38:53 +0000 From: RW To: freebsd-questions@freebsd.org Subject: Re: ports: 11.2 install incompatible with portsnap? Message-ID: <20181115203853.74f6d6d5@gumby.homeunix.com> In-Reply-To: <0b12bf4c-8a2a-9642-7e72-600b6798543d@dreamchaser.org> References: <0b12bf4c-8a2a-9642-7e72-600b6798543d@dreamchaser.org> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: AF76A7D370 X-Spamd-Result: default: False [-3.67 / 200.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[googlemail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; NEURAL_HAM_SHORT(-0.90)[-0.898,0]; RECEIVED_SPAMHAUS_PBL(0.00)[103.70.211.90.zen.spamhaus.org : 127.0.0.10]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[googlemail.com]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.76)[ipnet: 2a00:1450::/32(-1.88), asn: 15169(-1.81), country: US(-0.10)]; RCVD_IN_DNSWL_NONE(0.00)[c.2.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2018 20:38:59 -0000 On Thu, 15 Nov 2018 10:18:14 -0700 Gary Aitken wrote: > root@breakaway:/usr/ports # portsnap update > /usr/ports was not created by portsnap. > You must run 'portsnap extract' before running 'portsnap update'. > > Note the next-to-last line: > /usr/ports was not created by portsnap. > > That may be true. It was created during a sysinstall, but > I don't know what the mechanism used to create it was. > As a general rule update tools should be allowed to start with a clean directory unless you know for a fact that adopting a exiting tree is harmless. portsnap keeps a hidden file in the ports directory that records what it installed in that instance of the port tree - it need to be there to perform an update. > Is this now normal? I think it always was.