On Sep 21, 2011, at 12:22 PM, Shawn Walker wrote: > On 09/21/11 12:15, David Sechrest wrote: >> >> On Sep 21, 2011, at 12:11 PM, Shawn Walker wrote: >> >>> On 09/21/11 11:25, Brock Pytlik wrote: >>>> On 09/21/11 07:22, Alan Coopersmith wrote: >>>>> I can reach ipkg.us <http://ipkg.us> just fine, and can confirm that >>>>> file is not >>>>> available from it. That leaves me wondering: >>>>> >>>>> 1) Why is pkg trying to retrieve that file? >>>>> 2) What is pkg trying to update if that system is really on snv_173, >>>>> since there >>>>> is nothing newer in the main ipkg repo yet? >>>>> >>>> >>>> So, as Alan said, there is no such file on the server, and further, >>>> there's no file or license action that delivers a file with that hash >>>> (at least according to the search index). That leaves signature actions >>>> as the obvious candidate since the chain cert hashes aren't currently >>>> indexed and that's the only other payload action I can think of. >>>> >>>> If shawn's suggestion of pkg refresh --full doesn't work then I'll try >>>> to find what package has this hash in its manifest. >>> >>> I'd also note the other case I've seen this failure -- when a user has >>> planned an update using the signed version of the package, but then >>> switches to a repository that has an unsigned version or one with >>> different signatures. The client doesn't currently remove manifests >>> that are already downloaded and have an identical version, but >>> different digest. >> >> In that case consolidation/cacao/cacao-incorporation and/or >> library/cacao may be the culprits here. We still >> require bundling our own versions of these until we are able to use b174 >> which should be bundling the versions >> we require. > > Assuming the packages aren't already installed, the way to workaround that > then is to remove the relevant manifests from > /var/pkg/publisher/<publisher>/pkg/*. > > If you're feeling brave, the easiest way to do this is to: > > 1) create a backup be 'beadm create my-backup-be' > 2) rm -rf /var/pkg/publisher/<publisher_name>/pkg > 3) pkg info '*' > > That will force all of the manifests for your installed packages to be > retrieved again. If it all goes horribly wrong, you can just copy the good > files back from the backup BE. > > We have a bug open already to have the client check manifest digests so that > when repository administrators or others play tracks on the package system > (like changing a manifest, but not the version of the package) it will work > better.
Just to be clear, in the cacao case, the versions of the pkgs we bundle are distinct from the OS bundle versions. Also, in order to be able to install the versions we require we have to first do pkg uninstall entire '*cacao*'. We do remove our bits and reinstall entire before attempting to do something like 'pkg update' though. thanks Dave > > -Shawn > --- David Sechrest Phone: (408)276-5800 x15800 Systems Management Email: [email protected] Oracle Corporation _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
