On 09/21/11 11:25, Brock Pytlik wrote:
On 09/21/11 07:22, Alan Coopersmith wrote:
I can reach 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.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
