On 05/13/10 03:26 PM, Jim Hall wrote:
On May 13, 2010, at 1:30 PM, Shawn Walker wrote:
On 05/10/10 09:57 PM, Jim Hall wrote:
On May 10, 2010, at 10:31 PM, Shawn Walker wrote:
...
Errors from other publishers may be preventing you from using contrib.
Try:
pfexec pkg install --no-refresh alpine
That did it!
su...@killer:~$ pfexec pkg install --no-refresh alpine
DOWNLOAD PKGS FILES XFER (MB)
Completed 3/3 5191/5191 226.3/226.3
PHASE ACTIONS
Removal Phase 5204/5204
Install Phase 8162/8162
PHASE ITEMS
Reading Existing Index 8/8
Indexing Packages 3/3
su...@killer:~$ which alpine
/usr/bin/alpine
boy this does not "leap out" as the next step from the man page:
That's because it isn't the next step normally.
With --no-refresh, do not attempt to contact the repositories for
the image's publishers to retrieve publisher metadata (e.g.
catalogs).
Thanks for your help! I guess an alternative is to delete repositories?
Disable publishers you're not using, certainly.
I think an option similar to the "search" of pointing to a repository on
the command line would be nice. RFE?
Something similar is already planned, but that's not really the issue here.
In the past, the pkg(1)'s command was to simply continue on if a refresh
wasn't successful, but then some users indicated that was not good
default behaviour as it meant that if they did an image-update, and the
refresh failed, they may update to something other than the newest bits
they were expecting.
Likewise, an operation might fail much later on because a source that
was needed for the operation was unavailable, and the refresh check at
the beginning would have spotted that.
Long term, we'll have to work out some compromise that keeps both sets
of users happy. (The goal is to avoid a
property/policy/setting/whatever to control this if at all possible.)
Cheers,
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
