Date: Thu, 11 Jan 2018 17:49:35 +0100 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Ian Lepore <ian@freebsd.org> Cc: Boris Samorodov <bsam@passap.ru>, freebsd-current@FreeBSD.org Subject: Re: [self base packages] pkg: packages for wrong OS version: FreeBSD:12:amd64 Message-ID: <20180111164934.eqopinjs6tu3i3jn@ivaldir.net> In-Reply-To: <1515686254.44630.74.camel@freebsd.org> References: <da61ca31-3e85-99b6-5894-03796779c7ca@passap.ru> <20180110185336.nlwkwhxu574kybvi@ivaldir.net> <1515686254.44630.74.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, Jan 11, 2018 at 08:57:34AM -0700, Ian Lepore wrote: > On Wed, 2018-01-10 at 19:53 +0100, Baptiste Daroussin wrote: > > On Wed, Jan 10, 2018 at 09:29:04PM +0300, Boris Samorodov wrote: > > > > > > Hi All, > > > > > > I use self built base packages. Seems that I have a problem with pkg. > > > Today I've got this: > > > === > > > % sudo pkg update -f > > > Updating FreeBSD-base repository catalogue... > > > Fetching meta.txz: 100% 268 B 0.3kB/s 00:01 > > > Fetching packagesite.txz: 100% 29 KiB 29.4kB/s 00:01 > > > Processing entries: 0% > > > pkg: Newer FreeBSD version for package FreeBSD-libulog: > > > - package: 1200055 > > > - running kernel: 1200054 > > > pkg: repository FreeBSD-base contains packages for wrong OS version: > > > FreeBSD:12:amd64 > > > Processing entries: 100% > > > Unable to update repository FreeBSD-base > > > [...] > > > > > > % uname -aKU > > > FreeBSD latt.bsnet 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r327719: Tue Jan > > > 9 14:32:13 MSK 2018 > > > bsam@builder.bsnet:/usr/obj/usr/src/amd64.amd64/sys/PKG64X amd64 > > > 1200054 1200054 > > > > > > % pkg -v > > > 1.10.4 > > > > > hum > > > > pkg now has a mechanism to protect from installing too new package (aka packages > > built on a more recent system than the system you are running on. > > > > While this is great for ports this is a bit painful for upgrading base packages > > when building on current > > > > One has to specify pkg -o OSVERSION=1200055 to allow packages built on 1200055 > > to install on 1200054. > > > > I need to figure out a mechanism to make this simpler to handle to upgrade of > > base system while keeping this safety belt for users. > > > > Any idea is welcome > > > > Best regards, > > Bapt > > Is this new mechanism disabled if installing into something other than > the live system, such as when using -c or -r (and maybe -j)? > The new mechanism grab the information from the files in the userland, meaning, -c, -r and -j will discover the OSVERSION of the target binaries Bapt [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlpXlZwACgkQY4mL3PG3 Plr6TA//f0FrObHDOUTB87pM74sKhlpxj3/HO0a/PCVPRQ3h2qouoFOYK6evcAf5 mHu2LxvNzYmVxV2yRJUr4ottl2QfvazuOdNoSyG2lxE5CAxF9+eVOEuKgQZQuzFG uMMB+rtfxE2FxbREwGgamWbrQUnnhJwaygOmQNRv4G479xwBQ/JGdgaSheARwI1h G9XC2DbImbJ16kFkkejnrCqFR2JNfGh1rE0tTA7XfY+B8S6hnHCNhZ6n+BA9JOvb TglpuFSK70dWvhrQGmRb9FUqCoLvNIvVw0pxDrBD2WxRv7Qt4TKmp5Um0+A7ezVh f35GRWpaktpE23MSXPBvz1tJSqF8VWsUR7ZGuc7qgqKlYD9ngLv/9GP7vWmeoGIH pKrCRfM/SvMFiaBQ6vPktSTa+vflA9zRKgj9aG84hqJC9ld3kf4Ry9ir1cWSKYC6 izP9qg5xoG5XhZ7stQATarQZK+IlqMr3731kfMac5/E/pvIAu4hLbLYD960MVtbA t7+L2Ap72PStC1jmia8YMkVmY8rsjVovWvRlAiFt/9xojzIE3RYq4S6j4UoGu8mO uaJ5tlT+sA9l4ixF6JEwoy1+SL/NhyrVm///4iyF0u/YeKgBlR2Wi6uzhCiOpNBI SqYj/t6pzaefWkj/3E8PAzH9wlduGHnSGehQVBlV6Rkk3FGrpgk= =I/Qj -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180111164934.eqopinjs6tu3i3jn>