From owner-freebsd-current@freebsd.org Mon May 7 07:56:48 2018 Return-Path: Delivered-To: freebsd-current@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 DC93EFA9DA3 for ; Mon, 7 May 2018 07:56:47 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from smtp.freebsd.org (unknown [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FA0C831BD; Mon, 7 May 2018 07:56:47 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from ivaldir.etoilebsd.net (etoilebsd.net [178.32.217.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 5FFD515CF1; Mon, 7 May 2018 07:56:47 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by ivaldir.etoilebsd.net (Postfix, from userid 1001) id 392F649B71; Mon, 7 May 2018 09:56:16 +0200 (CEST) Date: Mon, 7 May 2018 09:56:16 +0200 From: Baptiste Daroussin To: Ian Lepore Cc: bsd-lists@BSDforge.com, FreeBSD Current Subject: Re: IGNORE_OSVERSION=yes -- can't install pkg Message-ID: <20180507075616.qtqplco6rasy4zbp@ivaldir.net> References: <7c58b8eb1bc3f83819c2aab6bfea322c@udns.ultimatedns.net> <1525538856.57768.293.camel@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="h5pmvhg5ne5od6pl" Content-Disposition: inline In-Reply-To: <1525538856.57768.293.camel@freebsd.org> User-Agent: NeoMutt/20180323 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2018 07:56:48 -0000 --h5pmvhg5ne5od6pl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 05, 2018 at 10:47:36AM -0600, Ian Lepore wrote: > On Sat, 2018-05-05 at 08:26 -0700, Chris H wrote: > > On Fri, 04 May 2018 22:57:52 -0700 said > >=20 > > >=20 > > > I just setup a jail from a 12-CURRENT I built awhile ago. It has no > > > ports > > > tree. So I'm attempting > > > to install svnlite. issuing pkg search svnlite returns > > > The package management tool is not yet installed on your system. > > > Do you want to fetch and install it now? [y/N]: y > > > Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/ > > > latest, > > > please wait... > > > Verifying signature with trusted certificate > > > pkg.freebsd.org.2013102301... > > > done > > > [12current.localhost] Installing pkg-1.10.5... > > > Newer FreeBSD version for package pkg: > > > To ignore this error set IGNORE_OSVERSION=3Dyes > > > - package: 1200062 > > > - running kernel: 1200054 > > > Allow missmatch now?[Y/n]: > > >=20 > > > Umm, what? Should I ignore this error? If so, why is there an error > > > at all? > > > I answered no. Guess I won't be able to use pkg(8) on this jail(8). > > > :-( > > >=20 > > > --Chris > > OK the only reference[1] I can find regarding this, indicates that > > answering "Y" > > to Allow missmatch now? resulted in an ABI mismatch that caused > > pkg(8) to be > > unusable. > > This is on an older version of 12, so I don't have anything that > > might have > > appeared in UPDATING. I really need this jail to resolve accumulating > > pr(1)'s > > on ports(7) I maintain. > >=20 > > Thank you. >=20 > The difference between 1200062 and 1200054 isn't going to affect > anything except modules which are intimate with kernel internals, such > as video drivers or virtualbox type stuff. >=20 > IMO, this new version checking done by pkg(8) is just bad Bad BAD. The > only control you get is a knob that tells you to ignore any version > mismatch. There appears to be no option to get the historical worked- > really-well behavior of ignoring mismatches of the minor version for > people who track -current. >=20 Except you devs are looking at it with a -CURRENT usage in mind. Most of our users are running releases. And you end up with en issue when let's say FreeBSD 10.0 is EOLed then the packages are now built on 10.1, if people continue running 10.0 because for instance they missed the notice about the 10.0 being EOL, they end up insta= lling packages that may be broken: new libc symbols for example, new syscalls etc. This check was one of the number 1 request over the last 3 years... For all people running -CURRENT they can add IGNORE_OSVERSION=3Dyes. More over, I received so many false bug report because actually developpers= were reporting "pkg is broken!!!" because they run pkg upgrade on a current syst= em that was 6+ month old or running pkg upgrade just after an ABI change that I consider this warning worth it. The only thing I would accept considering here is an advice on how to make = the tests more smooth for -CURRENT users. I consider an IGNORE_OSVERSION to be = good enough. I might change in next versions of pkg the runtime OSVERSION detection read= ing /bin/ls binary to be replaced by uname(1) to make it more friendly with incremental rebuild. Bapt --h5pmvhg5ne5od6pl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlrwBp0ACgkQY4mL3PG3 Plo1PhAA30fxmOTASuAEfNf7vXBbo/K00eU0hx+573nnXqxtZt72LKDuNyCHDqeb HnF6efab4bbMHXZtkS86a2Z3Q6z7xWFIhS0rctrxbAaRmjpdFcYxTLCUhSBz+p8l BZSK0lHI2oXqYc0PF0sztUzsQKvzoqy+7zzEgDbOa72l4aOGYCEkOunq6oJ2Gs/q MRbzszhSr14XtwetXLdN7Bugnoccxf6QL8RCka1INqzrRmu+hFujF+WKW13jDUQR YOCQllT8b2QK38MNXY7rpc9Jf5gD1ulkc/PW2sf783AsreaQVGE7o6ZeYcRRIXJ7 RF7eab9DJLFj9XUxa94kXf/TFGOf5tvugtgLrHN1vV4g6PpT+zCLfyhFCUpgLkN+ BAHQMkytaXNwj8JuM4HOs9uuhBLZ7sU4rgUm0JJXKRFY1IxQr8v/NTN5UnEt+npS i1wtuYbPxicDDCZxsQF+Tkcjumigzq3xnQT6JAJPLZmBaZ+3rpYIYWXykHDIzOKm TeAhETjl+sP5WXYMoPKQC1JmhUw/RUyAzARLI1jO0fZL8MVv/VFjhWB180cDzhns r7vnpTadwiqvfz5SyFc5dVxylYIugUKFANWMDYiVqgb8q2g7mt9b4IBjQ02tYLGF ssHYcbG5jcEnmogSEACvXwjVc9kWz5knlhGfavOsq+I5PFMOKUA= =3xuA -----END PGP SIGNATURE----- --h5pmvhg5ne5od6pl--