ports/180358: pkg upgrade is much too aggressive
Garrett Wollman
wollman at bimajority.org
Sun Jul 7 05:20:00 UTC 2013
>Number: 180358
>Category: ports
>Synopsis: pkg upgrade is much too aggressive
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Jul 07 05:20:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Garrett Wollman
>Release: FreeBSD 9.1-RELEASE-p3 amd64
>Organization:
none
>Environment:
System: FreeBSD hergotha.csail.mit.edu 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #6 r250951: Thu May 23 23:38:53 EDT 2013 wollman at hergotha.csail.mit.edu:/usr/obj/usr/src/sys/HERGOTHA amd64
pkg 1.1.4
>Description:
I rebuilt my package repository (just the repository database, not the
packages), and "pkg upgrade" insisted on reinstalling *every single
package* on the client system, giving as a reason "needed shared
library changed". This is clearly wrong, since I was already running
*the exact same code*.
Even before this, the upgrade command was far too aggressive,
reinstalling dozens of packages unnecessarily after a minor
(same-version) update to a library dependency. Upgrades should only
be forced automatically if the *version* of the shared library
changes, not for any old package change; that's why shared libraries
have versions in the first place.
>How-To-Repeat:
rm $REPO/*.txz
pkg repo $REPO $SIGNING_KEY
pkg upgrade
>Fix:
Make "pkg upgrade" less agreesive unless some new 'force flag is
specified.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list