ports/73888: Portupgrade doesn't force upgrades-by-package if package needs to be remotely fetched and installed package has the same version.
Michael Nottebrock
michaelnottebrock at gmx.net
Sat Nov 13 02:10:26 UTC 2004
>Number: 73888
>Category: ports
>Synopsis: Portupgrade doesn't force upgrades-by-package if package needs to be remotely fetched and installed package has the same version.
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Nov 13 02:10:25 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator: Michael Nottebrock
>Release: FreeBSD 4.10-STABLE i386
>Organization:
>Environment:
System: FreeBSD kiste 4.10-STABLE FreeBSD 4.10-STABLE #0: Thu Sep 23 21:58:42 CEST 2004 root at kiste:/usr/obj/usr/src/sys/KISTE-UP i386
>Description:
Portupgrade does not force upgrades by package if the packages needs to
be remotely (i.e. from the freebsd mirrors) fetched and the installed package
has the same version. Running portupgrade again after the package has been fetched succeeds.
>How-To-Repeat:
Find a package on a remote server which has the same version as the locally
installed port and is not available in /usr/ports/packages yet.
Try to portupgrade it with portupgrade -PPf. portupgrade will fail to force
the upgrade, but will fetch the package. Now run portupgrade -PPf again on the
same port, the upgrade will succeed.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list