Date: Wed, 14 Feb 2018 20:34:39 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 225104] ports-mgmt/pkg: "pkg update" fails to update package database saying that kernel too old for some package Message-ID: <bug-225104-32340-fdObdXxHOQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-225104-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-225104-32340@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225104 Bryan Drewery <bdrewery@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bdrewery@FreeBSD.org --- Comment #24 from Bryan Drewery <bdrewery@FreeBSD.org> --- (In reply to Roger Pau Monn=C3=A9 from comment #13) > I certainly preferred previous pkg behaviour, which would let you install > anything (and it might fail to load because of missing/wrong shared > libraries). Is there any option to restore previous behaviour? If not, can > we please get one? >=20 > Thanks, Roger. The previous behavior was called "russian roulette". Every time you run "pkg upgrade" you risk nuking the usability of all packages depending on what forward-incompatible change they were built against. Some recent examples are linking against libdl and ino64. The workaround people are using should not be used - the proper thing with pkg on CURRENT has *always been* that you should upgrade the system before upgrading packages. It is a different process than building ports directly on your system. Building locally ensures ABI compatibility every time, but with pkg you are getting packages from a future CURRENT system. FreeBSD does not have forward-compatibility in general, only backwards. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-225104-32340-fdObdXxHOQ>