Re: Resetting dpkg/dselect?
Buddha Buck writes ("Resetting dpkg/dselect?"):
> Is there a way to reset what dpkg/dselect things are available?
This is a known problem; I haven't quite decided what the criteria
should be for forgetting about something, and when I do it will
probably be nontrivial to implement. Don't expect progress soon, I'm
afraid.
Ian.
> I am running into the confusion of having several a.out/0.93R6 packages
> appear in dselect, even though the packages have been replaced, aren't
> installed, aren't available on my machine in any form, and don't exist
> in any Package file.
>
> A perfect example of this is libc. As far as I can tell, the only
> mention in the Package files for libc is that libc4 conflicts with and
> provides it. Yet it continues to be displayed in dselect.
>
> More confusing is the ncurses packages. I have ncurses-base,
> ncurses-bin, ncurses-developer, ncurses-runtime, ncurses-term,ncurses3.0
> , ncurses3.0-dev and ncurses3.0-pic. Two are old a.out files, and it
> isn't obvious which ones I need. To make it worse, ncurses-runtime is
> one I DON'T wnat, but many of the others depend on ncurses-runtime
> (which is provided by the new ncurses-base).
>
> Since I don't have many of these old packages on my system in anyform
> anymore, except in the eyes of dselect, is there a way to make dselect
> purge what it "knows", and relearn what I have available?
>
> --
> Buddha Buck phaedrus@dreamscape.com
> "She was infatuated with their male prostitutes, whose members were
> like those of donkeys and whose seed came in floods like that of
> stallions." -- Ezekiel 23:20
>
Reply to: