[bug-notifications] [pkgutil 0004301]: pkgutil -u stops exits with unresolvable dependencies in the catalog

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://www.opencsw.org/mantis/view.php?id=4301 
====================================================================== 
Reported By:                flod
Assigned To:                bonivart
====================================================================== 
Project:                    pkgutil
Issue ID:                   4301
Category:                   regular use
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
====================================================================== 
Date Submitted:             2010-02-23 04:49 CET
Last Modified:              2010-02-23 15:52 CET
====================================================================== 
Summary:                    pkgutil -u stops exits with unresolvable
dependencies in the catalog
Description: 
If any of the installed packages has an unresolvable in the catalog,
pkgutil -u will exit with:
Package <name> not in catalog...exiting.

Systems can now only be updated manually with
pkgutil -u <package>
====================================================================== 

---------------------------------------------------------------------- 
 (0007503) flod (reporter) - 2010-02-23 15:52
 http://www.opencsw.org/mantis/view.php?id=4301#c7503 
---------------------------------------------------------------------- 
(1) It's clear that the dependencies for the problematic package can not be
resolved. The update for this package should be aborted.

(2) For me it would make more sense to skip packages with unresolvable
dependencies (instead of exiting before updating the sane packages). But
this might depend on any policies for the opencsw catalog as a whole. If
the whole catalog is considered problematic/buggy with an unresolvable
dependency than it makes sense to me, to stop updating at all.

(3) I have no idea how the dependencies are resolved any way. If it is not
possible to nicely skip a package, I would leave it as it is.

(4) Maybe it makes more sense to check the integrity of the catalog on the
server side. Is it possible to check for unresolvable dependencies before
updating packages in the repository or when rebuilding the catalog?