Error in a package?

[Ultima]

Yeah, this is a bit annoying and needs to get fixed. The -f option IMO
should as the option suggests, forcefully upgrade the package even on an
error like this. I haven't really looked into why this package is
constantly causing this error, but manually deleting the pkg and installing
it works. Careful tho, all the pkg's depending on it will be removed and
will need to be reinstalled as well.

On Sun, Sep 11, 2016 at 4:55 PM, Grzegorz Junka <list1 at gjunka.com> wrote:

> Why I can not upgrade this package, even forcefully?
>
> root at ultrabook:~ # pkg upgrade -f javavmwrapper
> Updating ultrabook repository catalogue...
> ultrabook repository is up-to-date.
> All repositories are up-to-date.
> The following 1 package(s) will be affected (of 0 checked):
>
> Installed packages to be UPGRADED:
>         javavmwrapper: 2.5_1 -> 2.5_2
>
> Number of packages to be upgraded: 1
>
> 16 KiB to be downloaded.
>
> Proceed with this action? [y/N]: y
> Fetching javavmwrapper-2.5_2.txz: 100%   16 KiB  16.4kB/s 00:01
> Checking integrity... done (0 conflicting)
> [1/1] Upgrading javavmwrapper from 2.5_1 to 2.5_2...
> [1/1] Extracting javavmwrapper-2.5_2: 100%
> You may need to manually remove /usr/local/etc/javavm_opts.conf if it is
> no longer needed.
> pkg: Fail to rename /usr/local/bin/.checkvms.cSKXJhAdFAsw ->
> /usr/local/bin/checkvms: No such file or directory
>
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>