pkg upgrade problem
nick at wholesum.net
Mon May 25 10:43:48 UTC 2015
I'm seeing the same thing on this machine:
FreeBSD kolia.dunhurtin.net 8.4-STABLE FreeBSD 8.4-STABLE #0 r283273:
Fri May 22 07:43:52 EDT 2015
root at kolia.dunhurtin.net:/usr/obj/usr/src/sys/KOLIA i386
I did a pkg delete on libreoffice but it didn't help - it went on to
issue the same message regarding octave which I also deleted (had been
meaning to anyway). When I had begun the first round of updating I
noticed pkg update itself to the current version.
I also ran pkg updating that day to see if there were any upgrade
instructions I'd missed - didn't notice any though
root at kolia:~ # pkg upgrade
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100% 968 B 1.0kB/s 00:01
Fetching packagesite.txz: 100% 5 MiB 5.3MB/s 00:01
Processing entries: 100%
FreeBSD repository update completed. 23867 packages processed.
Checking for upgrades (713 candidates): 100%
Processing candidates (713 candidates): 100%
pkg: Cannot solve problem using SAT solver:
upgrade rule: upgrade local apache-openoffice-4.1.1_8 to remote
cannot install package apache-openoffice, remove it from request? [Y/n]: n
pkg: cannot solve job using SAT solver
root at kolia:~ # pkg -v
On 5/16/2015 7:35 PM, William A. Mahaffey III wrote:
> I just tried to do a 'pkg upgrade -y' from the console CLI as root. I
> redirected all output to a file, which I list below:
> [root at kabini1, /etc, 6:40:13pm] 333 % cat LIST.pkg-upgrade.May2015.txt
> Updating FreeBSD repository catalogue...
> Fetching meta.txz... done
> Fetching packagesite.txz... done
> Processing entries... done
> FreeBSD repository update completed. 23971 packages processed.
> Checking for upgrades (536 candidates)... done
> Processing candidates (536 candidates)... done
> pkg: Cannot solve problem using SAT solver:
> pkg: cannot find libreoffice in the request
> pkg: cannot solve job using SAT solver
> [root at kabini1, /etc, 6:40:16pm] 334 %
> I had cleaned out the /var/db/pkg/ directory of old repo data & meta
> data. How do I work around this ? Is this a problem w/ remote repos,
> or something at my end (possibly including pilot error :-/ ) ? TIA &
> have a nice weekend ....
More information about the freebsd-questions