Mantis - pkg_get
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4054 regular use major always 2009-11-23 13:17 2009-11-23 14:10
Reporter: skayser Platform:  
Assigned To: bonivart OS:  
Priority: normal OS Version:  
Status: closed Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
Summary: 0004054: 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]
...
Steps To Reproduce:
Additional Information: # pkgutil -v
1.9b2
Relationships
Attached Files:
Issue History
Date Modified Username Field Change
2009-11-23 13:17 skayser New Issue
2009-11-23 13:39 bonivart Status new => assigned
2009-11-23 13:39 bonivart Assigned To => bonivart
2009-11-23 13:46 bonivart Note Added: 0007024
2009-11-23 14:01 skayser Note Added: 0007027
2009-11-23 14:10 bonivart Status assigned => closed
2009-11-23 14:10 bonivart Resolution open => fixed

Notes
(0007024)
bonivart   
2009-11-23 13:46   
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.
(0007027)
skayser   
2009-11-23 14:01   
You are right, going through with the update i can see exactly the same as in your example output. Thanks for the clarification, didn't know about the changed behavior in 1.9 (should have read the readme).