Problem: pkg upgrade AND pkg install "almost" work but serious bugs [ too involved to discuss at the forums, too serious to test fixes on other machines [ another v9 also displays similar behavior ] ]. [ local.sqlite is too big to easily mail anywhere for upstream to diagnose, although I may/may not have done so. ] Version: pkg-devel 1.4.0.b2 [ only installed devel to fix this problem, which also existed in the regular port. The bug(s), if I recall, are very similar. ]. They a few weeks ago worked perfectly or almost so [on this machine at least, not on another which demostrates also the below Platform: 9.3-STABLE r273475 i386 AMD Athlon 64 X2 6000+ [similar to Bug 194146] Unexpected Results: ................... pkg install w3m-img Updating ... FreeBSD ... All ... The following 5 packages will be affected ( of 0 checked): New packages to be INSTALLED: w3m-img: 0.5.3_4 gnome-keyring: 3.14.0 w3m: 0.5.3_4 guile: 1.8.8_2 x264: 0.142.2455 [ proceeds to download the .txz not here already ] [ checks integrity, one conflicting ] pkg: Cannot solve problem using SAT solver: conflict rule: the following packages conflict with each other: w3m-img...(r), w3m...(r) [the line above repeats] cannot install package w3m-img, remove it from request? [Y/n]: n pkg: cannot solve job using SAT solver Checking integrity... done (0 conflicting) Conflicts with the existing packages have been found. One more solver iteration is needed to resolve them ......................................... What DOES work in case it helps the solution(s): This scenario, or a similar failure, occurs with each "pkg install" "pkg upgrade" I try. My workaround is to pkg upgrade -F (fetch only) and use portupgrade -P and pkg delete -f ... and pkg add ... txz ... but it is very problematic, undocumented, not recommended, etc.
Still not working correctly. Pardon the newbie for this Bugzilla procedure. New PR? pkg install sdl_net Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. The following 4 packages will be affected (of 0 checked): New packages to be INSTALLED: w3m: 0.5.3_4 Conflicts with w3m-img linux_base-f10: 10_9 deinstalled already porteasy: 2.8.5 deinstalled already Installed packages to be UPGRADED: sdl_net: 1.2.8_2 -> 1.2.8_3 The process will require 136 MB more space. 14 kB to be downloaded. Proceed with this action? [y/N]: y Fetching sdl_net-1.2.8_3.txz: Fetching sdl_net-1.2.8_3.txz: 100% 14 kB 14.4k/s 00:01 Checking integrity...Assertion failed: (pkgdb_ensure_loaded(j->db, p2, PKG_LOAD_FILES|PKG_LOAD_DIRS) == EPKG_OK), function pkg_conflicts_need_conflict, file pkg_jobs_conflicts.c, line 211. Child process pid=2990 terminated abnormally: Abort trap: 6 xxxxxxxxxxxxxxxxxxxxxxxxxxxxx Code below fixed here, temporarily? pkg add sdl_net-1.2.8_3-4c23cf30d4.txz Installing sdl_net-1.2.8_3... pkg: wrong architecture: FreeBSD:9:i386 instead of freebsd:9:x86:32 Failed to install the following 1 package(s): sdl_net-1.2.8_3-4c23cf30d4.txz xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx code above fixed here, temporarily? Script done on Sat Dec 13 19:47:26 2014
What repositories are you using? Which version of pkg ? I see pkg 1.4.0.b2 in your first report, which version on your second repo?
Just the upstream repository repo_type : binary repository : FreeBSD Architecture: freebsd:9:x86:32 ports-mgmt/pkg 1.4.0 (Fri dec 12) (downgraded from pkg-devel that had the architecture change) portupgrade -PP seems to still be working now though... despite not a direct pkg install... and is quicker than working around the error using three subsequent pkg commands, beginning with pkg install and can run more or less unattended.
v9 > v10 "pkg install" seems to work okay. ... despite installing gnomehier that has already been deprecated AND removed from the ports tree... probably as a dependency -PP portupgrade )) works fine, sometimes does not find the pkg, pkg fetch finds it... [maybe also see pair of emails dec 26-27 2014 to the ports@freebsd.org list] I would suggest if resources allow using a pre-pkg v9 system, pkg2ng it, and test for this PR to resolve where it may still happen. Then the bug there could maybe be solved in pkg (all versions) so that it does not appear again, say, in v 11 or v 12... Additionally, updating a v9 > v10 pkg files and usage and reinstall of pkg only eventually worked because I had a working v10 from which to synchronize "repos" "etc/pkg" "/usr/local/etc/pkg*" files until the errors dissipated. Maybe a wiki or pkg-message or pkg-check-lines-of-files could make that use case simpler for new installs, etc... [ not to mention the 'key' files ] and be also put into the wiki and man page(s) ... sort of like a 'sysinstall but just for pkg files and parameters...' Hopefully my last entry to this PR since I am mostly running V10...
Sorry I missed the Pr but yes all of this has been fixed (I hope :))