Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict resolution does not work with pkg install in 1.4.0 #1098

Closed
bdrewery opened this issue Dec 16, 2014 · 7 comments
Closed

Conflict resolution does not work with pkg install in 1.4.0 #1098

bdrewery opened this issue Dec 16, 2014 · 7 comments
Labels

Comments

@bdrewery
Copy link
Member

# pkg install -A security/krb5
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:
        gettext-runtime: 0.19.3

Installed packages to be UPGRADED:
        krb5: 1.12.2 -> 1.13

The process will require 840 KB more space.
1 MB to be downloaded.

Proceed with this action? [y/N]: y
Fetching krb5-1.13.txz: 100%    1 MB   1.1M/s    00:01
Fetching gettext-runtime-0.19.3.txz: 100%  146 KB 149.3k/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=88012 terminated abnormally: Abort trap

This failed to handle the upgrade/replacement needed for gettext.

@bdrewery
Copy link
Member Author

Additionally my system is now in some corrupted state:

# pkg info|grep krb
krb5-1.12.2                    Authentication system developed at MIT, successor to Kerberos IV
# pkg install -A security/krb5
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
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=88105 terminated abnormally: Abort trap

@bdrewery
Copy link
Member Author

Note that the assert is wrong too, it should have the graceful error that a conflict was detected.

I see 3 distinct bugs here.

  1. Failure to handle replacement for gettext in pkg install
  2. Assert instead of "graceful" error that a conflict was found
  3. Running pkg install again after this immediately hits the conflicted state - unsure what is happening here. I don't see gettext-runtime in pkg info.

@kgadek
Copy link

kgadek commented Dec 17, 2014

I confirm that. Few mins ago updated pkg from 1.3.8_3 to 1.4.0 and now this happens:

MrPink# pkg install vim
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
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=1728 terminated abnormally: Abort trap
MrPink# pkg info | grep vim
MrPink# pkg --version
1.4.0
MrPink# uname -a
FreeBSD MrPink 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Fri Jan 17 01:46:25 UTC 2014     root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386
MrPink#

@rfdrake
Copy link

rfdrake commented Dec 17, 2014

I don't want to be the first to start a me-too thing, but I can also confirm here. Mine was also referencing the gettext-runtime replacement, so the underlying cause of the current problem might be a problem with the new package. Even if that were the case, I would expect "pkg install" to error more gracefully and let you do something with the broken pieces. :)

[rdrake@f10 ~]$ sudo pkg install p5-DBD-Sybase
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
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=63922 terminated abnormally: Abort trap

@erikarn
Copy link
Member

erikarn commented Dec 18, 2014

This happened to me; I just did a pkg upgrade -f to force upgrade everything and it resolved things!

@kgadek
Copy link

kgadek commented Dec 19, 2014

Yes, pkg upgrade -f fixed that for me as well. Strange.

@bapt
Copy link
Member

bapt commented Dec 22, 2014

fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants