pkg 1.4.6 deleted itself - I thought this might happen!

Pierre Abbat phma at
Thu Feb 12 19:59:18 PST 2015

pkg 1.4.6 had a bug in which, if told to upgrade a package, it would leave the 
database thinking the package is installed, but its files are actually missing. 
I just tried to install a package, and pkg found it had to upgrade itself. 
Here's what happened:

# pkg ins minicom
Updating Avalon repository catalogue...
Avalon repository is up-to-date.
All repositories are up-to-date.
New version of pkg detected; it needs to be installed first.
The following 1 packages will be affected (of 0 checked):

Installed packages to be UPGRADED:
        pkg: 1.4.6 -> 1.4.11

The process will require 51 KB more space.
2 MB to be downloaded.

Proceed with this action? [y/N]: y
Fetching pkg-1.4.11.txz: 100%    2 MB  99.0k/s    00:22    
Checking integrity... done (0 conflicting)
[1/1] Upgrading pkg from 1.4.6 to 1.4.11...
[1/1] Extracting pkg-1.4.11:  20%
pkg: archive_read_extract(): truncated input
[1/1] Extracting pkg-1.4.11: 100%
[1/1] Deleting files for pkg-1.4.11: 100%
# pkg ins minicom
pkg: not found

So I have a downloaded pkg package in /var/cache/pkg/. What do I do with it?

ve ka'a ro klaji la .romas. se jmaji

More information about the Users mailing list