Re: starting dselect with predefined package list
Osamu Aoki, 2001-Nov-20 20:50 -0800: On Tue, Nov 20, 2001 at 07:59:54PM -0800, Sean 'Shaleh' Perry wrote: basically. You should only set selections on a fresh install. Otherwise you have packages from set A the other machine is set B and thus machine A gets the union of the set (i.e. more packages than B and a chance at conflicting packages). True if you do it as described without pattern match. What about using 'dpkg --get-selections \* packages' Then you get all packages listed (non-installed packages as purge) Thus you will get the exact same setting. (someone mentioned on this list) Bloating system can be avoided by this, I think. The package list lists packages that have been removed but not purged, on hold, set for purge but not purged, attempted to install and stuck, as well as simply installed. You should probably change all holds to installs, purge the packages marked deinstalled, fix any half installed packages and then save the output. I did not understand this. Fixing half installed sounds good to me :-) Thanks alot. I look forward to testing this out. And yes, this is for installing a new system that will be a s/w duplicate, and I figure this will shave a little time off the process. thanks, jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
starting dselect with predefined package list
Is there some way to do this? It would be cool to take a capture of 'dpkg -l' and start dselect with an option to load that package list so all I'd have to do is quickly verify the list loaded properly and then let it start installing. That way, I could pre-build the package list(s) for systems to help stream-line the installation. Just a thought...I have them once in awhile. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: starting dselect with predefined package list
Jeff [EMAIL PROTECTED] writes: Is there some way to do this? It would be cool to take a capture of 'dpkg -l' and start dselect with an option to load that package list so all I'd have to do is quickly verify the list loaded properly and then let it start installing. That way, I could pre-build the package list(s) for systems to help stream-line the installation. dpkg --set-selections -- Brian Nelson [EMAIL PROTECTED] [EMAIL PROTECTED] http://bignachos.com
RE: starting dselect with predefined package list
dumb shell tricks: Well, I frequently use lists of packages (just the names separated by spaces, no line breaks) and do: apt-get install `cat packagelist.txt` -Original Message- From: Jeff [SMTP:[EMAIL PROTECTED] Sent: Tuesday, November 20, 2001 12:06 PM To: debian user list Subject: starting dselect with predefined package list Is there some way to do this? It would be cool to take a capture of 'dpkg -l' and start dselect with an option to load that package list so all I'd have to do is quickly verify the list loaded properly and then let it start installing. That way, I could pre-build the package list(s) for systems to help stream-line the installation. Just a thought...I have them once in awhile. jc -- Jeff Coppock Systems Engineer Diggin' DebianAdmin and User -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting dselect with predefined package list
Brian Nelson, 2001-Nov-20 10:32 -0800: Jeff [EMAIL PROTECTED] writes: Is there some way to do this? It would be cool to take a capture of 'dpkg -l' and start dselect with an option to load that package list so all I'd have to do is quickly verify the list loaded properly and then let it start installing. That way, I could pre-build the package list(s) for systems to help stream-line the installation. dpkg --set-selections Okay, after looking this up in man, lemme ask: If I use 'dpkg --get-selections packages' and then 'dpkg --set-selections packages' on another system, and finally run dselect, my selects will be set to those listed in 'packages'? thanks, jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: starting dselect with predefined package list
On 21-Nov-2001 Jeff wrote: Brian Nelson, 2001-Nov-20 10:32 -0800: Jeff [EMAIL PROTECTED] writes: Is there some way to do this? It would be cool to take a capture of 'dpkg -l' and start dselect with an option to load that package list so all I'd have to do is quickly verify the list loaded properly and then let it start installing. That way, I could pre-build the package list(s) for systems to help stream-line the installation. dpkg --set-selections Okay, after looking this up in man, lemme ask: If I use 'dpkg --get-selections packages' and then 'dpkg --set-selections packages' on another system, and finally run dselect, my selects will be set to those listed in 'packages'? basically. You should only set selections on a fresh install. Otherwise you have packages from set A the other machine is set B and thus machine A gets the union of the set (i.e. more packages than B and a chance at conflicting packages). The package list lists packages that have been removed but not purged, on hold, set for purge but not purged, attempted to install and stuck, as well as simply installed. You should probably change all holds to installs, purge the packages marked deinstalled, fix any half installed packages and then save the output.
Re: starting dselect with predefined package list
Hi, On Tue, Nov 20, 2001 at 07:59:54PM -0800, Sean 'Shaleh' Perry wrote: If I use 'dpkg --get-selections packages' and then 'dpkg --set-selections packages' on another system, and finally run dselect, my selects will be set to those listed in 'packages'? basically. You should only set selections on a fresh install. Otherwise you have packages from set A the other machine is set B and thus machine A gets the union of the set (i.e. more packages than B and a chance at conflicting packages). True if you do it as described without pattern match. What about using 'dpkg --get-selections \* packages' Then you get all packages listed (non-installed packages as purge) Thus you will get the exact same setting. (someone mentioned on this list) Bloating system can be avoided by this, I think. The package list lists packages that have been removed but not purged, on hold, set for purge but not purged, attempted to install and stuck, as well as simply installed. You should probably change all holds to installs, purge the packages marked deinstalled, fix any half installed packages and then save the output. I did not understand this. Fixing half installed sounds good to me :-) -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki [EMAIL PROTECTED], GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://qref.sourceforge.net/quick/ +
