Assertion failed & Abort trap from pkg subsystem

Scot Hetzel swhetzel at gmail.com
Tue Dec 23 06:09:43 UTC 2014


On Mon, Dec 22, 2014 at 3:53 PM,  <sthaug at nethelp.no> wrote:
> Got the following when trying to install bash on a 10.1-STABLE amd64
> system:
>
> root at xxx:/home/sthaug # pkg install bash-4.3.30_1
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up-to-date.
> All repositories are up-to-date.
> The following 2 packages will be affected (of 0 checked):
>
> New packages to be INSTALLED:
>         bash: 4.3.30_1
>         gettext-runtime: 0.19.3
>
> The process will require 7 MB more space.
> 1 MB to be downloaded.
>
> Proceed with this action? [y/N]: y
> Fetching bash-4.3.30_1.txz: 100%    1 MB   1.2M/s    00:01
> Fetching gettext-runtime-0.19.3.txz: 100%  144 KB 147.2k/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=4851 terminated abnormally: Abort trap
>
> Being rather new to the world of pkg, I have no idea of what I can do
> here. Anybody?
>
> (Already tried "pkg check -Bdsr -a" to see if I have inconsistencies,
> but no.)
>
> Packages already installed on the system:
>
> root at xxx:/home/sthaug # pkg info
> apr-1.5.1.1.5.3_4              Apache Portability Library
> bind910-9.10.1_1               BIND DNS suite with updated DNSSEC and DNS64
> db5-5.3.28_1                   The Oracle Berkeley DB, revision 5.3
> dialog4ports-0.1.5_2           Console Interface to configure ports
> dnstop-20121017                Captures and analyzes DNS traffic (or analyzes libpcap dump)
> expat-2.1.0_1                  XML 1.0 parser written in C
> gdbm-1.11_2                    GNU database manager
> gettext-0.18.3.1_1             GNU gettext package

According to the 20141130 entry in /usr/ports/UPDATING, the gettext
port was split into 2 ports.  One containing the libraries, and the
other the developer tools.

See /usr/ports/UPDATING on how to fix this issue.

-- 
DISCLAIMER:

No electrons were maimed while sending this message. Only slightly bruised.


More information about the freebsd-stable mailing list