Date: Sat, 21 Jun 2025 15:29:24 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 287700] Cannot 'pkg upgrade' from pkg-2.1.4 to pkg-2.2.0 on 14.3R Message-ID: <bug-287700-32340-m61DOh0QHn@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-287700-32340@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287700 Eric <erichanskrs@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erichanskrs@gmail.com --- Comment #1 from Eric <erichanskrs@gmail.com> --- (In reply to Masachika ISHIZUKA from comment #0) I haven't experienced this, upgrading from pkg 2.1.4 to 2.2.0 (using Latest) on my 14.3-R. On my system I cannot reproduce this when again starting with pkg 2.1.4 (with a clean pkg cache); however, your environment will no doubt be different. Your command # pkg upgrade tries to consider upgrading every installed package. This might have resulted in comparing quite a number of installed packages with the packages available remotely; also a lot of dependencies may have been involved and might have caused the infinite loop, though I cannot corroborate that. AFAIK the running pkg (that is 2.1.4 in this case) is first trying to upgrade itself (to 2.2.0 here); I don't know how much 'other processing' is undertaken before pkg tries to upgrade itself. Your solution/workaround seems to have worked effectively. As alternatives to this 'pkg add' route, users facing the same problem in trying to get pkg upgraded to 2.2.0 might consider trying: # pkg upgrade pkg or even: # pkg upgrade -r FreeBSD pkg thereby limiting this to upgrading only the pkg package. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-287700-32340-m61DOh0QHn>