On Thursday 28 February 2002 18:12, Troy Telford wrote: > I hope this will be simple... > > I recently re-installed Debian. After revising my apt.sources list, as > well as a good 'ol dist-upgrade to bring my system up to Debian > 3.0/unstable, I discovered an interesting problem: > > For some reason, while apt-get has no problem with the change, 'dselect' > still thinks it's running Potato. It shows the current versions of the > software I have installed, however it still diplays/uses the > package-list from Potato. > > This isn't much of a problem for the most part, because I just use > apt-get for package installation/maintenance. But, when I'm looking for > a package to install, I can't go to dselect and look up the proper > package name for apt-get. (This being because it has the old Potato > package list, and not the unstable package list). So, as an > alternative, I have to go to the Debian site, and use its query for the > package name(s). Which is a bit of a bandwidth & resource hog > considering the information should be on my computer already... > > So, for instance, if I want to install GNOME, I look up 'gnome' within > dselect. However, only GNOME 1.0 is shown -- which is definately not > the version that is shown when I look it up on the Debian site. > > So, how do I re-initialize dselect's package database so it shows the > 'unstable' branch packages, rather than the 'potato' branch ones. > > (I have already updated the apt sources list, as well as 'apt-get > dist-upgrade', so my distribution is the unstable one, and everything > but dselect seems to be fine.) > > -Troy
try running dselect update bob
