Bug 221711

Summary: ports-mgmt/pkg: core dump after switch to new repos caused by locked port
Product: Ports & Packages Reporter: Rick van der Zwet <info>
Component: Individual Port(s)Assignee: freebsd-pkg (Nobody) <pkg>
Status: Closed FIXED    
Severity: Affects Only Me Flags: bugzilla: maintainer-feedback? (pkg)
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   

Description Rick van der Zwet 2017-08-22 09:06:14 UTC
Sequence preceding the core-dump:

0) Dovecot2 was locked:
  $ pkg lock mail/dovecot2

1) Dovecot2 was merged into dovecot:
  $ pkg set -o mail/dovecot2:mail/dovecot
  $ pkg set -o mail/dovecot2-pigeonhole:mail/dovecot-pigeonhole

2) I required the latest repos instead of the quarly one (unrelated: since my custom ports running on latest tree where failing) thus created:
  cat <<EOF /usr/local/etc/pkg/repos/FreeBSD.conf 
FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest"

3) Did a fetch of new repos details:
  $ sudo pkg upgrade

4) Attempted upgrade fails. The traceback/logging is from the 2nd attempt, since first one was no longer present in my framebuffer. Error message is the same, yet missing some lines about the (already downloaded) new repository.

  $ sudo pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
dovecot2- is locked and may not be modified
Processing candidates (133 candidates): 100%
Checking integrity...
dovecot2- is locked and may not be modified
Assertion failed: (cun != NULL), function pkg_conflicts_check_chain_conflict, file pkg_jobs_conflicts.c, line 481.
Child process pid=2637 terminated abnormally: Abort trap

I know this is a rather odd sequence of events and I have not tried to reproduce it, yet it might be interesting to one may concerned. 

FYI: As a workaround I unlocked mail/dovecot and did the upgrade.
Comment 1 Baptiste Daroussin freebsd_committer 2021-08-18 08:22:11 UTC
I should have replied earlier to this one, but this has been fixed in the meantime.