pkg/26762: pkg_add -u of same version requires -f

[jschauma%netmeister.org@localhost]

>Number:         26762
>Category:       pkg
>Synopsis:       pkg_add -u of same version requires -f
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 25 18:59:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     Jan Schaumann
>Release:        NetBSD 2.0_BETA
>Organization:
        
>Environment:
        
        
System: NetBSD dogfish-head.cs.stevens-tech.edu 2.0_BETA NetBSD 2.0_BETA (BOCK) 
#17: Mon Aug 16 13:34:05 EDT 2004 
jschauma%doppelbock.hpcf.cs.stevens-tech.edu@localhost:/share/src/sys/arch/i386/compile/obj/BOCK
 i386
Architecture: i386
Machine: i386
>Description:
        If you want to upgrade a binary package, you can use 'pkg_add -u
        <newpackage>'.  As the name suggests, this performs an _up_grade.
        Ie, it assumes that the new package has a higher version than the
        installed version.

        If you want to do the equivalent of 'make replace' for binary
        packages -- that is, replace an installed binary package with
        another binary package of the same version -- 'pkg_add -u' will
        not do this.  Instead, it will display a message that this
        version is already recorded as installed.

        One can get around this by forcing the upgrade: pkg_add -f -u

        This can be seen as either a sw-bug (fix pkg_add(1)) or a doc-bug,
        since the manual page claims:

        -u      If the package that's being installed is already installed,
                either in the same or a different version, an update is per-
                formed.
>How-To-Repeat:
        install package foo-1.0
        build a binary package foo-1.0.tgz
        $ pkg_add -u foo-1.0.tgz
        pkg_add: package `foo-1.0' already recorded as installed
        $

>Fix:
        Either allow pkg_add to replace a binary package of the same version,
        or change the documentation.  If the latter, add a sentence that
        '-f -u' will have the desired effect.
>Release-Note:
>Audit-Trail:
>Unformatted: