Re: dselect problem...

[David Puryear <dayear@codenet.net>]

On 27-Oct-97 Lukas Eppler wrote:
      On 26 Oct 1997, Ben Pfaff wrote:
     > If I recall properly, I had this problem at one point and solved by
     > upgrading to a newer dpkg-ftp.  Try downloading the newest version
     > from hamm with a regular ftp program and installing with `dpkg -i'.
     > Then re-run Update and Install and see if that fixes the problem.
      
Thanks Ben, getting dpkg-ftp from hamm worked for me.

      Ups, this seems a very brute-force fix. What happens if you "clear the
      list of available packages"? or run dpkg --forget-old-unavail and rerun
      update? or you can try to "[not] keep debian directory [y/n]" at the end
      of the Install dialog. Dselect is quite self-reparatory, so fiddling
      around for a while with it already solved such problems for me.

Before posting, I think I tried many combinations of things to make it work.
Tried new directory, delete debian directory and Packages files, updated
Packages files, and so on, but I didn't try dpkg --forget-old-unavil. Next time
I'll try that, thanks.
      
      I think forcing someone to use unstable packages when having such kind of
      problems is not the best way. a lot of people are using stable without
      these problems. Are you sure you don't need extra packages when using
      dpkg-ftp from hamm?

I should have mentioned that my base setup is mixture of 1.3.1 and hamm, so I
don't mind using hamm packages.:) 

Thanks all for help,
       David


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .