Re: dselect dconfusion
On Tue, Jul 27, 1999 at 11:30:25PM -0400, Buddha Buck wrote:
> > Still have many conficts/dependancy problems. Is there anyway to start
> > dselect from scratch? What I mean to ask is can I reset the selections
> > to what they were before I started to tinker with them?
>
> Not easily... Not after you leave dselect that is.
>
> If you get to a dependency-resolution screen, you can use "R" to reset
> your selections to what they were before you got there -- usually
> including the selection that caused the problem. But once you get out
> of a dependency-resolution screen, it's set.
>
You can try to minimize the conflicts, by doing the following
(although it will some patience to work it all out):
What I'm going to tell you to do will put all of you current
packages on hold, letting you work from a known starting point.
Start dselect and go to [S]elect. Highlight the header that says
'Updated packages (newer version is available)' and hit the = key.
This will more than likely throw you into the resolution screen
with a list of packages. If so, take a look at the package status
indicators. There are 4 columns, the first of which (E) is normally
blank, the other three indicating (from left to right) installed
status (I), old selection (O), and current selection (M). You only
need to worry about column 2 (I) and column 4 (M). For all
packages listed on the conflict screen that have a blank (I)
status (indicating not currently installed) hit _ (underscore). For
all other packages (with * as the I status), hit the = key. When
you get all the packages marked this way, hit Enter to return to
the main package list. (You might have to work through several
resolution screens this way before you get all the conflicts worked
out).
Now (back at main list), move the cursor down to the 'Up to date
installed packages' header and hit *. If you get a conflict
resolution screen, follow the directions in the previous paragraph.
Finally, move down to the 'Available packages (not currently
installed)' header and hit _ (underscore). You shouldn't get the
conflict screen here, but if you do, follow the previous
instructions.
You should now have be to a point where you can go back to the
'Updated packages' section and start marking them (one at a time)
with *, working out the conflicts as you go.
A couple of quick pointers... if you mark a package for upgrade, or
install, and get a screen full of conflicts, you can always hit the
'R' key to put everything back to what it was before you created
the conflict. If you get everything messed up again, remember to
hit 'X' from the package screen (if I'm not totally mistaken, it'll
reset everything back to the way it was when you started dselect,
effectively giving you the chance to start over.)
HTH,
Mike
[Private mail welcome, but no need to CC: me on list replies.]
--
Michael Merten -- ironfoot@popaccount.com
---> NRA Life Member -- http://www.nra.org
---> Debian GNU/Linux Fan -- http://www.debian.org
---> CenLA-LUG Founder -- http://www.angelfire.com/la2/cenlalug
--
".. [Concerning the celebration of the 4th of July, 1811,]
scarcely a word was said of the solicitude and labors and fears and
sorrows and sleepless nights of the men who projected, proposed,
defended, and subscribed the Declaration of Independence. Do you
recollect your memorable speech upon the day on which the vote was
taken? Do you recollect the pensive and awful silence which pervaded
the house when we were called up, one after another, to the table of
the President of Congress to subscribe what was believed by many at
that time to be our own death warrants?..."
-- A letter from Benjamin Rush to John Adams
Reply to: