From owner-freebsd-stable@freebsd.org Wed Feb 24 07:41:23 2021 Return-Path: Delivered-To: freebsd-stable@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 1CD4E552FE8 for ; Wed, 24 Feb 2021 07:41:23 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Dlnst4lgZz4XQS for ; Wed, 24 Feb 2021 07:41:22 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 11O7fKMQ060631; Tue, 23 Feb 2021 23:41:26 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) MIME-Version: 1.0 Date: Tue, 23 Feb 2021 23:41:20 -0800 From: Chris To: Mark Millard Cc: freebsd-stable@freebsd.org Subject: Re: When did pkg(8) drop support for 12-stable? In-Reply-To: References: <1C347959-FDB2-42F7-97F5-F0A74078E7F2.ref@yahoo.com> <1C347959-FDB2-42F7-97F5-F0A74078E7F2@yahoo.com> User-Agent: UDNSMS/17.0 Message-ID: <4ea6cf79bc2fec2c348b98d437b48ec8@bsdforge.com> X-Sender: bsd-lists@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Dlnst4lgZz4XQS X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Feb 2021 07:41:23 -0000 On 2021-02-23 19:30, Mark Millard via freebsd-stable wrote: > On 2021-Feb-23, at 18:08, Chris wrote: > >> On 2021-02-23 17:42, Mark Millard wrote: >>> (Warner is only CC'd here.) >>> Warner Losh imp at bsdimp.com wrote on >>> Wed Feb 24 01:04:13 UTC 2021 : >>>> On Tue, Feb 23, 2021, 4:51 PM Chris wrote: >>>> > Given this is a pkg(8) error, I brought it up on ports@ >>>> > but it was suggested I (also?) bring it up here on stable@ >>>> > >>>> > OK awhile back I installed a copy of 12 stable from the >>>> > usb stick image. I tweaked it to my wishes then got called >>>> > away and haven't been able to get back to it until the other >>>> > day. This is still a fresh install which has a populated /usr/src. >>>> > So I >>>> > svnlite co svn://svn.freebsd.org/ports/head /usr/ports >>>> > followed by a >>>> > cd /usr/ports/ports-mgmt/pkg/ && make install clean >>>> > which returns >>>> > make >>>> > /!\ ERROR: /!\ >>>> > >>>> > Ports Collection support for your FreeBSD version has ended, and no ports >>>> > are >>>> > guaranteed to build on this syst >>>> em. Please upgrade to a supported release. >>>> > >>>> > No support will be provided if you silence this message by defining >>>> > ALLOW_UNSUPPORTED_SYSTEM. >>>> > >>>> > *** Error code 1 >>>> > >>>> > Stop. >>>> > Err what? Ok while I think this was from stable 12.1, it's still still 12, >>>> > and it's on stable. So what gives? >>>> > >>>> 12.1 has reached EOL now that 12.2 has been out a while. >>>> From release/12.1.0/ : >>> "Tag releng/12.1@r354233 as release/12.1.0 (12.1-RELEASE)" >>> I think that implicit in Warner's response is that >>> versions of stable/12/ that are not after r354233 are >>> also EOL. One needs to have stable/12/ material from >>> after -r354233 in order for it to be supported. >>> He might even mean that stable/12/ material from before: >>> "Tag releng/12.2@r366954 as release/12.2.0 (12.2-RELEASE)" >>> would also be considered as not supported. >>> To be safe you should be using stable/12/ material from >>> on or after -r366954 in order to have a supported >>> context. >>> (I'm not sure if anything is explicit about the status >>> of stable/12/ material between releng/12.1@r354233 >>> and releng/12.2@r366954 .) >> A HUGE thanks for all of this, Mark. This is EXACTLY what I needed. >> >> # uname -apKU >> FreeBSD fbsd12dev 12.1-STABLE FreeBSD 12.1-STABLE r363918 GENERIC amd64 >> amd64 1201522 1201522 >> which pretty well confirms what you deduced. >> I'm still a bit confused. It seems to me that it didn't _used_ >> to be that way. But my brain isn't using ECC. So a couple of >> bits may be flipped. > > The implication of all of stable/12/ being supported > would be support of stable/12/ from on or after its > creation: > > QUOTE > Revision 339434 - Directory Listing > Modified Fri Oct 19 00:09:24 2018 UTC (2 years, 4 months ago) by gjb > Copied from: head revision 339432 > Copy head@r339432 > to stable/12 as part of the 12.0-RELEASE cycle. > > Additional post-branch commits will follow. > END QUOTE > > Such does not seem likely to me. What would be the > point of dropping 12.0-RELEASE support and > 12.1-RELEASE support if such stable/12/ history was > covered, some of that history being minor variations > on the 12.0-RELEASE or 12.1-RELEASE ? > > Note: > Despite some claims in other messages, svn -r363918 > is not 12.1-RELEASE ( not -r354233 ) and -r363918 > is shown as (only) in stable/12/ by svn. Your > claim of 12-STABLE was correct, just not detailed > enough. Thanks. I really appreciate your taking the time to clear things up for me. It also seems clear that I've somehow mixed the purpose of RELEASE vs STABLE. :-/ Thanks again, Mark! --Chris > > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar)