Bug 1540 - changes to authorities should include refresh
: changes to authorities should include refresh
Status: RESOLVED FIXINSOURCE
Product: pkg
cli
: unspecified
: ANY/Generic All
: P3 enhancement (vote)
: in99
Assigned To: Brock Pytlik
: pkg/cli watcher
:
:
:
: 2917
: pkg-blocker-2008-11
  Show dependency treegraph
 
Reported: 2008-04-24 15:21 UTC by Dan Price
Modified: 2008-09-17 18:53 UTC (History)
4 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Dan Price 2008-04-24 15:21:09 UTC
Seems to me that altering your client's authorities should implicitly include
an appropriate refresh.

We've seen several people be perplexed when they add a new authority but can't
get the packages the new authority offers.

Perhaps a flag could also be added for "don't refresh" if the user is e.g.
having a network connectivity issue or the authority they are adding isn't
presently online.

Or we could attempt the refresh, and print some sort of nice message if it
fails.
Comment 1 Dan Price 2008-07-30 20:46:51 UTC
Made blocker for November.  It's an annoying usability problem, and in general
we want to reduce the likelihood of most users to ever need refresh.
Comment 2 Brian Leonard 2008-08-15 09:32:00 UTC
Ideally this automatic refresh would only apply to the new authority. Refreshes
to the existing authorities, especially the default one, have been burning
people.
Comment 3 Danek Duvall 2008-08-15 11:17:15 UTC
Yes, the refresh should probably only apply to the new authority.

How have people been burned by refreshing from the default authority?
Comment 4 Gregg Sporar 2008-08-15 12:30:02 UTC
>How have people been burned by refreshing from the default authority?

1. Install OpenSolaris 2008.05 from the LiveCD
2. Add an IPS repository
3. pfexec pkg refresh
4. Install something from the new repository
---- weeks go by -----
5. Install something from pkg.opensolaris.org.  In my case, SUNWgcc.  It
completely slipped my mind that as a result of that pkg refresh I did in order
to use some other repo, the install of SUNWgcc from pkg.opensolaris.org was the
latest version of SUNWgcc *at the time that I had done the pkg refresh*.  So
what I *should* have done to do my install was specified the version of SUNWgcc
that is from build 86.  But since I forgot to do that, I got the SUNWgcc from
build 93 instead.  As a result, /usr/bin/ld no longer works.  :-(

For now, the work around is well known: *always* do a pkg refresh and a
*complete* image update before installing things from pkg.opensolaris.org.  But
that is pretty painful - most users do not want to do that just so they can get
something like the GNU tools.  And the expectation of users of Linux distros
such as Ubuntu is that they do not need to worry about the default repo. moving
forward on them - my install of Ubuntu 7.10 still pulls binaries that are
intended to work with the kernel that was included with 7.10.

The confusion/burn rate out in the community is apparent in threads such as
this one: http://opensolaris.org/jive/thread.jspa?threadID=69380&tstart=0
Comment 5 Danek Duvall 2008-08-15 12:53:03 UTC
Ah, I see.  Yes, that was a bug in incorporations in build 86 that's been fixed
since.  Although we (now) require you to update SUNWipkg before running an
image-update, it may be useful to do so before any install, to get past
inevitable bugs.  One of the hazards of using a product still in rapid
development.  :-/
Comment 6 Brock Pytlik 2008-08-27 14:10:31 UTC
Adding a dependency to 2917 as we really shouldn't have to refresh all
authorities because of a change to a specific one.

*** This bug has been marked as a duplicate of bug 2917 ***
Comment 7 Brock Pytlik 2008-08-27 14:14:54 UTC
Oops, that I meant to add a dependency, not mark a duplicate, sorry about that.
Comment 8 Brock Pytlik 2008-08-29 14:57:59 UTC
Assigning to me and starting work on it.
Comment 9 Brock Pytlik 2008-08-29 17:30:54 UTC
Assigning to me and working on it.
Comment 10 Dan Price 2008-09-11 00:36:13 UTC
(Made an accidental update to this bug... resetting)
Comment 11 Brock Pytlik 2008-09-17 17:28:39 UTC
targeting 99
Comment 12 Brock Pytlik 2008-09-17 18:53:27 UTC
Fixed in change set 3dc9fc9b5fee6dcf7b8b3461d8860588c7231d5f