Resetting dselect
hi all Does anyone know a quick way to unselect (hold I guess) all the packages in dselect (as opposed to going through the whole list and hitting =)??? thanks Andrew - Andrew McRobert LLB B.Sc(Comp. Sci) IT Liaison Officer, School of Law MURDOCH UNIVERSITY Perth, Western Australia Ph: [+61 8 9360 6479] Fax: [+61 8 9310 6671] e-mail: [EMAIL PROTECTED] Linux: The Choice of a GNU Generation
Re: Resetting dselect
Highlight the very top entry in dselect, - All packages -, and press the = key. Pressing an action key when highlighting any category heading applies that action to ALL packages in that category, and - All packages - is a heading that contains every package. Hope that helps. On Fri, Aug 18, 2000 at 04:10:34PM +0800, Andrew McRobert wrote: hi all Does anyone know a quick way to unselect (hold I guess) all the packages in dselect (as opposed to going through the whole list and hitting =)??? thanks Andrew -- Craig McPherson Network Admin Baptist Student Union Fayetteville, Arkansas
RE: Resetting dselect
thanks, but that doesn't seem to be working ... (I'm still getting about 2 ga-zillion packages to install) Andrew - Andrew McRobert LLB B.Sc(Comp. Sci) IT Liaison Officer, School of Law MURDOCH UNIVERSITY Perth, Western Australia Ph: [+61 8 9360 6479] Fax: [+61 8 9310 6671] e-mail: [EMAIL PROTECTED] Linux: The Choice of a GNU Generation -Original Message- From: David Vrabel [mailto:[EMAIL PROTECTED] Sent: Friday, August 18, 2000 4:41 PM To: Andrew McRobert Subject: Re: Resetting dselect On 18 Aug 2000, Andrew McRobert wrote: Does anyone know a quick way to unselect (hold I guess) all the packages in dselect (as opposed to going through the whole list and hitting =)??? If you press the key when the section header line is hightlighted it will affect all the packages in that sections. David Vrabel
Re: resetting dselect
what if i don't want to conf. them? - Original Message - From: David Z. Maze [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Wednesday, March 22, 2000 7:55 PM Subject: Re: resetting dselect Beavis [EMAIL PROTECTED] writes: Beavis ok, well lets just say this: what if the packages are in the Beavis upacked (not set up); install (was: install) state. Then you should probably configure them, either using 'dpkg --configure --pending' from the command line or using dselect's Configure option. -- David Maze [EMAIL PROTECTED] http://www.mit.edu/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: resetting dselect
[EMAIL PROTECTED] (Nick Barron) wrote: - Original Message - From: David Z. Maze [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Wednesday, March 22, 2000 7:55 PM Subject: Re: resetting dselect Beavis [EMAIL PROTECTED] writes: Beavis ok, well lets just say this: what if the packages are in the Beavis upacked (not set up); install (was: install) state. Then you should probably configure them, either using 'dpkg --configure --pending' from the command line or using dselect's Configure option. what if i don't want to conf. them? So then purge them. Why do you want unpacked but unconfigured packages on your system, anyway? Grab the source if you just want to look at the things. -- Colin Watson [EMAIL PROTECTED]
Re: resetting dselect
ok, well lets just say this: what if the packages are in the upacked (not set up); install (was: install) state. and i want the dselect to just ignore the face that they are not set up the reason why is that i can't install anything without gettting ride of this packages first. is there an easier way around this? [EMAIL PROTECTED] (Beavis) wrote: hello, i installed a few .deb manually meaning dpkg -i filename but dselect thinks that are are still unconfigured, which is not true They aren't just in obsolete/local? If they are, you can safely ignore them. If dselect thinks they're unconfigured then they probably are (dselect gets its information from the dpkg database, and installing via dselect is really not much different from 'dpkg -i'); does 'dpkg --configure -a' help? how do u reset the deselect so that it doesn't pick up the packages as existing in the system Er, if a package has been installed with dpkg than you can't tell dselect it doesn't exist without doing serious violence to your packaging system. I don't recommend that at all. -- Colin Watson [EMAIL PROTECTED] -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: resetting dselect
Beavis [EMAIL PROTECTED] writes: Beavis ok, well lets just say this: what if the packages are in the Beavis upacked (not set up); install (was: install) state. Then you should probably configure them, either using 'dpkg --configure --pending' from the command line or using dselect's Configure option. -- David Maze [EMAIL PROTECTED] http://www.mit.edu/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
resetting dselect
hello, i installed a few .deb manually meaning dpkg -i filename but dselect thinks that are are still unconfigured, which is not true how do u reset the deselect so that it doesn't pick up the packages as existing in the system the packages are kdebase, kbelibs2g tkankx beavis..
Re: resetting dselect
[EMAIL PROTECTED] (Beavis) wrote: hello, i installed a few .deb manually meaning dpkg -i filename but dselect thinks that are are still unconfigured, which is not true They aren't just in obsolete/local? If they are, you can safely ignore them. If dselect thinks they're unconfigured then they probably are (dselect gets its information from the dpkg database, and installing via dselect is really not much different from 'dpkg -i'); does 'dpkg --configure -a' help? how do u reset the deselect so that it doesn't pick up the packages as existing in the system Er, if a package has been installed with dpkg than you can't tell dselect it doesn't exist without doing serious violence to your packaging system. I don't recommend that at all. -- Colin Watson [EMAIL PROTECTED]
Resetting dselect
-BEGIN PGP SIGNED MESSAGE- Hello All: I had added bo to my pkgs list and set everything to hold (I thought). Two questions. 1. Why does dselect seem to override holds on some pkgs? I hilighted the All pkgs line and hit hold (=) so I could selectively make changes yet there were a few pkgs here and there that remained in suggested status. Evedent when I tried to d/l a couple of MB's of pkgs and saw a list of 20 or so pkgs scroll past adding up to 40 MB's. I had to ^C and set them to hold one by one. 2. Now that I'm finished with that and want to d/l in suggested mode I can't reset the pkgs to suggested mode (U). I'd really hate to have to reset them one by one. Is there a quick way to reset the status? I've tried to mv the status files out to be rebuilt but dselect just bombs out when I do that. Thanks, Have a good one. - -- Rick Jones E-Mail: Rick [EMAIL PROTECTED] Date: 09-Apr-97 Time: 10:06:58 - -- -BEGIN PGP SIGNATURE- Version: 2.6.2 iQCVAwUBM0uiggi+Ph+i3TgpAQF6ygP+NZUwGv4/MGGTeDx2L7t5QSn+P36JJrjc u/TQojINQKlGBnstdKsbNqcXtLgEilstshm7lA8WzgTGrDKUgrhfs5jnjjNQQRJn n3q3EEEaS2PQcxey1HRRLA1CPYgv4if+fMQn4ebxMot3oY2eJX8ZfjJYvXIdYJX6 RTVffQaqPtw= =KHQ/ -END PGP SIGNATURE-
