On 09/15/11 08:57 AM, Danek Duvall wrote:
Tim Foster wrote:
https://cr.opensolaris.org/action/browse/pkg/timf/pkglint_fix_dep_obsolete/pkglint_fix_dep_obsolete-webrev/
This looks fine, though I don't understand why it's an error to rename a
package to an obsolete package.
A fair question - it looks like we do cope with this situation in the
packaging system itself: during an update, the renamed package that
depends on the now-obsolete package simply gets removed, along with the
obsolete package.
David, any ideas? Perhaps it's just that the build system doesn't drop
renamed packages from an incorporation, so during updates we get
something like:
timf@linn[262] pkg -R image install [email protected],5.11-0.141
Creating Plan -
pkg install: No solution was found to satisfy constraints
maintained incorporations: None
Plan Creation: dependency error(s) in proposed packages:
No suitable version of required package
pkg://opensolaris.org/[email protected],5.11-0.141:20110914T221950Z found:
Reject:
pkg://opensolaris.org/[email protected],5.11-0.141:20110914T221950Z
Reason: All versions matching 'require' dependency
pkg:/renamed-intermediate are rejected
Reject:
pkg://opensolaris.org/[email protected],5.11-0.141:20110914T221940Z
Reason: All acceptable versions of 'require' dependency on
pkg:/system/obsolete are obsolete
Plan Creation: Errors in installed packages due to proposed changes:
No suitable version of installed package
pkg://opensolaris.org/[email protected],5.11-0.140:20110914T221925Z found
Reject:
pkg://opensolaris.org/[email protected],5.11-0.140:20110914T221925Z
Reason: This version excluded by specified installation version
Reject:
pkg://opensolaris.org/[email protected],5.11-0.141:20110914T221950Z
Reason: All versions matching 'require' dependency
pkg:/renamed-intermediate are rejected
Reject:
pkg://opensolaris.org/[email protected],5.11-0.141:20110914T221940Z
Reason: All acceptable versions of 'require' dependency on
pkg:/system/obsolete are obsolete )
It looked from the description of the bug
that if we renamed a package to another package which erroneously had a
require dependency on an obsolete package, we'd ignore the error in that
last part of the chain.
But I don't care all that much; I don't see a reason *to* rename a package
to an obsolete one.
There's that too.
cheers,
tim
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
