Re: Unattended package install.
I tried it and it seemed to die in the middle of the generation of
it's script. It might have something to do with my script hanging at
the end though.
I think I'll just keep entering my data by hand....my script's easier
than installing one package at a time anyway, and move on to later stages
of the install.
I'll keep sending you my script as it grows Hubert and if you can
expectify it with database and all that would be GRAND.
Here's what it came up with:
Origonal script:
#! /bin/sh
dpkg -i `find . -name "libc5_*.deb"`
dpkg -i `find . -name "libc5-dev_*.deb"`
dpkg -i `find . -name "libbfd2.7.0.9_*.deb"`
dpkg -i `find . -name "libdb1-dev_*.deb"`
dpkg -i `find . -name "libg++27_*.deb"`
dpkg -i `find . -name "libg++27-dev_*.deb"`
dpkg -i `find . -name "libgdbm1-dev_*.deb"`
dpkg -i `find . -name "libreadline2-dev_*.deb"`
dpkg -i `find . -name "perl_*.deb"`
dpkg -i `find . -name "tcl74_*.deb"`
dpkg -i `find . -name "expect_*.deb"`
dpkg -i `find . -name "at_*.deb"`
dpkg -i `find . -name "bin86_*.deb"`
dpkg -i `find . -name "binutils_*.deb"`
dpkg -i `find . -name "bsdmainutils_*.deb"`
dpkg -i `find . -name "cpp_*.deb"`
dpkg -i `find . -name "cron_*.deb"`
dpkg -i `find . -name "dnsutils_*.deb"`
dpkg -i `find . -name "dpkg-dev_*.deb"`
dpkg -i `find . -name "ed_*.deb"`
dpkg -i `find . -name "electric-fence_*.deb"`
dpkg -i `find . -name "gcc_*.deb"`
dpkg -i `find . -name "gdb_*.deb"`
dpkg -i `find . -name "kernel-source-2.0.30_*.deb"`
dpkg -i `find . -name "kernel-package_*.deb"`
dpkg -i `find . -name "less_*.deb"`
dpkg -i `find . -name "m4_*.deb"`
dpkg -i `find . -name "make_*.deb"`
dpkg -i `find . -name "netstd_*.deb"`
dpkg -i `find . -name "nvi_*.deb"`
dpkg -i `find . -name "patch_*.deb"`
expect's result:
#!/usr/bin/expect -f
#
# This Expect script was generated by autoexpect on Fri Apr 3 13:25:50
1998
# Expect and autoexpect were both written by Don Libes, NIST.
#
# Note that autoexpect does not guarantee a working script. It
# necessarily has to guess about certain things. Two reasons a script
# might fail are:
#
# 1) timing - A surprising number of programs (rn, ksh, zsh, telnet,
# etc.) and devices discard or ignore keystrokes that arrive "too
# quickly" after prompts. If you find your new script hanging up at
# one spot, try adding a short sleep just before the previous send. The
# -c flag (for "conservative") makes Expect do this automatically -
# pausing briefly before sending each character. This pacifies every
# program I know of. The -C flag allows you to define a character to
# toggle this mode off and on.
#
# 2) differing output - Some programs produce different output each time
# they run. The "date" command is an obvious example. Another is
# ftp, if it produces throughput statistics at the end of a file
# transfer. If this causes a problem, delete these patterns or replace
# them with wildcards. An alternative is to use the -p flag (for
# "prompt") which makes Expect only look for the last line of output
# (i.e., the prompt). The -P flag allows you to define a character to
# toggle this mode off and on.
#
# Read the man page for more info.
#
# -Don
set timeout -1
spawn /floppy/build-filter-addtobase.script
match_max 100000
expect -exact "(Reading database ... 2822 files and directories currently
installed.)\r
Preparing to replace libc5 5.4.23-6 (using ./base/libc5_5.4.33-3.deb)
...\r
Unpacking replacement libc5 ...\r
Setting up libc5 (5.4.33-3) ...\r
\r
Selecting previously deselected package libc5-dev.\r
(Reading database ... 2822 files and directories currently installed.)\r
Unpacking libc5-dev (from ./devel/libc5-dev_5.4.33-3.deb) ...\r
Setting up libc5-dev (5.4.33-3) ...\r
Selecting previously deselected package libbfd2.7.0.9.\r
(Reading database ... 3380 files and directories currently installed.)\r
Unpacking libbfd2.7.0.9 (from .../libbfd2.7.0.9_2.7.0.9-3.deb) ...\r
Setting up libbfd2.7.0.9 (2.7.0.9-3) ...\r
\r
Selecting previously deselected package libdb1-dev.\r
(Reading database ... 3385 files and directories currently installed.)\r
Unpacking libdb1-dev (from .../devel/libdb1-dev_1.85.4-3.deb) ...\r
Setting up libdb1-dev (1.85.4-3) ...\r
Selecting previously deselected package libg++27.\r
(Reading database ... 3405 files and directories currently installed.)\r
Unpacking libg++27 (from ./libs/libg++27_2.7.2.1-8.deb) ...\r
Setting up libg++27 (2.7.2.1-8) ...\r
\r
Selecting previously deselected package libg++27-dev.\r
(Reading database ... 3419 files and directories currently installed.)\r
Unpacking libg++27-dev (from .../libg++27-dev_2.7.2.1-8.deb) ...\r
Setting up libg++27-dev (2.7.2.1-8) ...\r
\r
Selecting previously deselected package libgdbm1-dev.\r
(Reading database ... 3756 files and directories currently installed.)\r
Unpacking libgdbm1-dev (from .../libgdbm1-dev_1.7.3-19.deb) ...\r
Setting up libgdbm1-dev (1.7.3-19) ...\r
\r
Selecting previously deselected package libreadline2-dev.\r
(Reading database ... 3809 files and directories currently installed.)\r
Unpacking libreadline2-dev (from .../libreadline2-dev_2.1-2.deb) ...\r
Setting up libreadline2-dev (2.1-2) ...\r
\r
Selecting previously deselected package perl.\r
(Reading database ... 3832 files and directories currently installed.)\r
Unpacking perl (from .../perl_5.003.07-10.deb) ...\r
Setting up perl (5.003.07-10) ...\r
\r
Selecting previously deselected package at.\r
(Reading database ... 4520 files and directories currently installed.)\r
Unpacking at (from ./admin/at_3.1.7-3.deb) ...\r
dpkg: dependency problems prevent configuration of at:\r
at depends on mail-transport-agent | smail | mailx; however:\r
Package mail-transport-agent is not installed.\r
Package smail is not installed.\r
Package mailx is not installed.\r
dpkg: error processing at (--install):\r
dependency problems - leaving unconfigured\r
Errors were encountered while processing:\r
at\r
Selecting previously deselected package bin86.\r
(Reading database ... 4544 files and directories currently installed.)\r
Unpacking bin86 (from ./devel/bin86_0.4-3.deb) ...\r
Setting up bin86 (0.4-3) ...\r
Selecting previously deselected package binutils.\r
(Reading database ... 4550 files and directories currently installed.)\r
Unpacking binutils (from ./devel/binutils_2.7.0.9-3.deb) ...\r
Setting up binutils (2.7.0.9-3) ...\r
\r
Selecting previously deselected package bsdmainutils.\r
(Reading database ... 4611 files and directories currently installed.)\r
Unpacking bsdmainutils (from ./utils/bsdmainutils_3.2-0.deb) ...\r
Setting up bsdmainutils (3.2-0) ...\r
Selecting previously deselected package cpp.\r
(Reading database ... 4654 files and directories currently installed.)\r
Unpacking cpp (from .../interpreters/cpp_2.7.2.1-8.deb) ...\r
Setting up cpp (2.7.2.1-8) ...\r
\r
Selecting previously deselected package cron.\r
(Reading database ... 4664 files and directories currently installed.)\r
Unpacking cron (from ./admin/cron_3.0pl1-38.deb) ...\r
Setting up cron (3.0pl1-38) ...\r
\r
Selecting previously deselected package dnsutils.\r
(Reading database ... 4687 files and directories currently installed.)\r
Unpacking dnsutils (from ./net/dnsutils_970203-0.1.deb) ...\r
Setting up dnsutils (970203-0.1) ...\r
\r
Selecting previously deselected package dpkg-dev.\r
(Reading database ... 4700 files and directories currently installed.)\r
Unpacking dpkg-dev (from ./utils/dpkg-dev_1.4.0.8.deb) ...\r
Setting up dpkg-dev (1.4.0.8) ...\r
Selecting previously deselected package ed.\r
(Reading database ... 4763 files and directories currently installed.)\r
Unpacking ed (from ./editors/ed_0.2-12.deb) ...\r
Setting up ed (0.2-12) ...\r
\r
Selecting previously deselected package electric-fence.\r
(Reading database ... 4772 files and directories currently installed.)\r
Unpacking electric-fence (from .../electric-fence_2.0.5-3.deb) ...\r
Setting up electric-fence (2.0.5-3) ...\r
Selecting previously deselected package gcc.\r
(Reading database ... 4781 files and directories currently installed.)\r
Unpacking gcc (from ./devel/gcc_2.7.2.1-8.deb) ...\r
Setting up gcc (2.7.2.1-8) ...\r
\r
Selecting previously deselected package gdb.\r
(Reading database ... 4869 files and directories currently installed.)\r
Unpacking gdb (from ./devel/gdb_4.16-6.deb) ...\r
Setting up gdb (4.16-6) ...\r
\r
Selecting previously deselected package kernel-source-2.0.30.\r
(Reading database ... 4894 files and directories currently installed.)\r
Unpacking kernel-source-2.0.30 (from
./devel/kernel-source-2.0.30_2.0.30-7.deb) ...\r
Setting up kernel-source-2.0.30 (2.0.30-7) ...\r
\r
Selecting previously deselected package kernel-package.\r
(Reading database ... 7129 files and directories currently installed.)\r
Unpacking kernel-package (from ./misc/kernel-package_3.28.deb) ...\r
Setting up kernel-package (3.28) ...\r
\r
Configuring the Full name of the local person responsible for the\r
kernel packages.\r
\r
This information will be used to sign the new packages produced. If\r
you never intend to sign the kernel images, source, or header packages\r
created (You should only need to do so if you upload an official\r
package), you may safely leave it blank. However, we recommend that\r
you do supply a full name if only so that the dpkg -s kernel-*\r
information looks prettier <grin>.\r
\r
Please supply the full name of the local kernel maintainer\r
:"
send -- "Henry Hollenberg\r"
expect -exact "Henry Hollenberg\r
\r
Configuring the email address of the local person responsible for the\r
kernel packages.\r
\r
This information will be put into the dpkg database, you may safely\r
leave it blank. However, we recommend that you do supply a email\r
address, it make keeping track easier.\r
\r
Please supply the email address of the local kernel maintainer\r
:"
send -- "speed@barney.iamerica.net\r"
expect -exact "speed@barney.iamerica.net\r
\r
Selecting previously deselected package less.\r
(Reading database ... 7158 files and directories
Henry Hollenberg speed@barney.iamerica.net
On Sat, 4 Apr 1998, Hubert Weikert wrote:
> On Fri, 3 Apr 1998, Henry Hollenberg wrote:
> > Anybody got any quick tips on how to plug expect into your
> > scripts similar to how Alex did below? (That expect is one
> > long man page...i hope there are some examples...).
>
> See /usr/doc/expect.../examples
>
> With autoexpect you should be able to generate a expect script from the
> first (manuall) run:
> autoexpect -f new-expect-script your-shell-script
> (you must first install/decompress autoxepect, on hamm the reference for
> expect on the first line of autoexpect must be changed, similar for the
> resulting expect script).
>
> Bye,
> Hubert
>
> ------------------------------------------------------------------------------
> Hubert Weikert DB1MQ Member of DARC (www.darc.de) and FITUG (www.fitug.de)
> Email: weikert@cube.net weikert@compuserve.com http://www.cube.net/~weikert/
> Book: Kryptographie mit dem Computer (PGP Praxis) ISBN 3-7905-1503-5 DM 19,80
> Key = 21978C61 fingerprint = 99 38 A5 83 C8 76 F4 E1 A7 9C B9 70 9A A7 70 10
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: