As written in ports/UPDATING for the 20141126 entry (Perl), I ran: # pkg upgrade -f Everything went as expected, i.e. fetching many packages, and suddenly: ... Fetching OpenEXR-2.2.0_3.txz: 100% 3 MB 1.7M/s 00:02 Fetching MathJax-2.4.0.txz: 100% 16 MB 1.4M/s 00:12 Fetching Coin-3.1.3_8.txz: 100% 2 MB 2.4M/s 00:01 Checking integrity...Assertion failed: (strcmp(uid, p->uid) != 0), function pkg_conflicts_check_local_path, file pkg_jobs_conflicts.c, line 350. Child process pid=64940 terminated abnormally: Abort trap Notes: $ pkg -v 1.4.0 $ uname -K -p -r 10.1-STABLE amd64 1001502
Remark: the previous session was run inside a `su -m' session. Trying to run it again from a root login session gives this result: # pkg upgrade -f Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (1431 candidates): 58% libfreehand00 has no direct installation candidates, change it to libfreehand? [ Y/n]: Checking for upgrades (1431 candidates): 91% db42 has no direct installation candidates, change it to db? [Y/n]: Checking for upgrades (1431 candidates): 100% Processing candidates (1431 candidates): 100% pkg: sqlite error while executing UPDATE packages SET name=?1 WHERE name=?2; in file pkg_jobs.c:1601: UNIQUE constraint failed: packages.name pkg: sqlite error while executing UPDATE packages SET name=?1 WHERE name=?2; in file pkg_jobs.c:1601: UNIQUE constraint failed: packages.name Checking integrity...Assertion failed: (strcmp(uid, p->uid) != 0), function pkg_ conflicts_check_local_path, file pkg_jobs_conflicts.c, line 350. Child process pid=65455 terminated abnormally: Abort trap
Same failure one week later with the next packages set! Checking integrity...Assertion failed: (strcmp(uid, p->uid) != 0), function pkg_conflicts_check_local_path, file pkg_jobs_conflicts.c, line 350. Child process pid=53216 terminated abnormally: Abort trap
Any workaround? Thjis is critical. I am sitting here with a production system and a failed upgrade...
Ok, # pkg upgrade without -f did it.
pkg 1.4.2 fixes it in single repo 1.4.3 fixes it in multi repo
(In reply to Baptiste Daroussin from comment #5) still exists pkg -v 1.10.4 or again? These developers are so miraclest.