[bug-notifications] [pkgutil 0004054]: Could cswclassutils always be upgraded/installed first?
Mantis Bug Tracker
noreply at opencsw.org
Mon Nov 23 13:46:07 CET 2009
A NOTE has been added to this issue.
======================================================================
http://www.opencsw.org/mantis/view.php?id=4054
======================================================================
Reported By: skayser
Assigned To: bonivart
======================================================================
Project: pkgutil
Issue ID: 4054
Category: regular use
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 2009-11-23 13:17 CET
Last Modified: 2009-11-23 13:46 CET
======================================================================
Summary: Could cswclassutils always be upgraded/installed
first?
Description:
I have just upgraded axel from testing and a cswclassutils upgrade came
along at the same time. As axel depends on cswclassutils I would have
expected that cswclassutils would be upgraded first, but axel was upgraded
first.
Is there a reasoning to NOT upgrade depends first? Could pkgutil either
upgrade/install depends first (general case) or at least upgrade/install
cswclassutils first? There might be CAS contained in an updated
cswclassutils on which an updated package relies on.
# pkgutil -t http://mirror.opencsw.org/opencsw/testing -u axel
Fetching new catalog and descriptions
(http://mirror.opencsw.org/opencsw/testing/i386/5.10) if available...
Fetching new catalog and descriptions
(ftp://ftpint.consol.de/pub/comp/os/solaris/opencsw//current/i386/5.10) if
available...
Fetching new catalog and descriptions
(file:///install/pkgs/consol/i386/5.10) if available...
Parsing catalog, may take a while...
Install UPDATED packages: CSWaxel-2.4,REV=2009.11.23
CSWcswclassutils-1.30,REV=2009.11.21
CURRENT packages: CSWcommon-1.4.7,REV=2009.09.20
Total size: 46.5 KB
2 packages to fetch. Do you want to continue? [Y,n]
Fetching CSWcswclassutils-1.30,REV=2009.11.21 (1/2)...
Fetching CSWaxel-2.4,REV=2009.11.23 (2/2)...
=> Removing old version of CSWaxel
The following package is currently installed:
CSWaxel axel - Lightweight command-line download accelerator
(i386) 2.3,REV=2009.03.31
Do you want to remove this package? [y,n,?,q]
...
======================================================================
----------------------------------------------------------------------
(0007024) bonivart (manager) - 2009-11-23 13:46
http://www.opencsw.org/mantis/view.php?id=4054#c7024
----------------------------------------------------------------------
Did you go through with the install or did you abort? In your posted output
I can't see that. A new feature in 1.9 is to remove all updates before
installing all packages to better handle package splits that cause file
collisions. Maybe you interpreted that the removal of axel meant it would
also be installed (before cswclassutils) like it would in previous
releases.
Look at my test run below. I installed axel from current first without
updating cswclassutil (-iN axel) so I should have the same state as in your
example when doing the update, the list of packages is the same.
# pkgutil -t http://mirror.opencsw.org/opencsw/testing -u axel
Install UPDATED packages:
CSWaxel-2.4,REV=2009.11.23
CSWcswclassutils-1.30,REV=2009.11.21
CURRENT packages:
CSWcommon-1.4.7,REV=2009.09.20
Total size: 46.5 KB
2 packages to fetch. Do you want to continue? [Y,n]
Fetching CSWcswclassutils-1.30,REV=2009.11.21 (1/2)...
Fetching CSWaxel-2.4,REV=2009.11.23 (2/2)...
=> Removing old version of CSWaxel
Removal of <CSWaxel> was successful.
=> Removing old version of CSWcswclassutils
Removal of <CSWcswclassutils> was successful.
=> Installing CSWcswclassutils-1.30,REV=2009.11.21
Installation of <CSWcswclassutils> was successful.
=> Installing CSWaxel-2.4,REV=2009.11.23
Installation of <CSWaxel> was successful.
As you can see it removes both axel and cswclassutils before installing
the new versions with cswclassutils before axel.
More information about the bug-notifications
mailing list