On 09/ 9/10 05:40 PM, Darren Reed wrote:
In my test environment, I ran a depot server as publisher "darrenr"
to provide a custom package during the initial install. I've since
disabled that but now "pkg install" (to install a package from
opensolaris.org) complains because it can't contact "darrenr".
This error occurred even if I did "pkg install pkg://opensolaris.org/...".
I don't understand why it would need to contact "darrenr" if I've
told it which publisher to use to install a specific package.
What seems to work is to use "pkg set-publisher -d darrenr" to
disable the publisher "darrenr".
Shouldn't pkg know if there are any dependencies on packages
from "darrenr" (there weren't) and be able to ignore it if I ask
for a package and specify which publisher to get it from?
No, because one of the first things install does at the beginning is
check each publisher's repositories for updated metadata.
If it can't connect to do that, it will fail.
And before you ask, this particular behaviour is one that no one seems
to be able to agree on, which is why it is that way now.
If you want to skip the metadata update check, you'll need to use
--no-refresh.
And yes, while you specified a specific pkg and publisher, at the point
the metadata refresh is done, we don't yet know that we won't need
packages from the other publisher.
Users have requested the current behaviour explicitly in the past as
they want an image-update, install, etc. to fail if it can't get
packages from one of their publishers since that might affect the result
of the operation.
Cheers,
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
