[Bug 226143] Problem with portmaster/pkg autoremove

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Feb 23 17:03:07 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226143

            Bug ID: 226143
           Summary: Problem with portmaster/pkg autoremove
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: kpect at protonmail.com

Hello.
I have following portmaster config file which I use to install packages:

$ cat /usr/local/etc/portmaster.rc
NO_BACKUP=Bopt
MAKE_PACKAGE=gopt
ALWAYS_SCRUB_DISTFILES=dopt
PM_VERBOSE=vopt
PM_PACKAGES=first
PM_PACKAGES_LOCAL=pmp_local
PM_DEL_BUILD_ONLY=pm_dbo
PM_NO_CONFIRM=pm_no_confirm
PM_NO_TERM_TITLE=pm_no_term_title
LOCAL_PACKAGEDIR=/var/cache/pkg

Package files are being built and installed normally, but when I want to remove
all dependencies not all of them are removed with 'pkg autoremove':

$ doas pkg delete libuv
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages
in the universe):

Installed packages to be REMOVED:
        libuv-1.19.1

Number of packages to be removed: 1

Proceed with deinstalling packages? [y/N]: n

$ doas pkg autoremove -y
Checking integrity... done (0 conflicting)
Nothing to do.

If I set automatic flag for a package manually then it's get removed:

$ doas pkg set -A 1 libuv
Mark libuv-1.19.1 as automatically installed? [y/N]: y

$ doas pkg autoremove -y
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages:

Installed packages to be REMOVED:
        libuv-1.19.1

Number of packages to be removed: 1
[1/1] Deinstalling libuv-1.19.1...
[1/1] Deleting files for libuv-1.19.1: 100%

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list