Re: How do we debug dselect/apt?
- To: Jason Gunthorpe <firstname.lastname@example.org>
- Cc: Debian-Devel <email@example.com>
- Subject: Re: How do we debug dselect/apt?
- From: Oscar Levi <firstname.lastname@example.org>
- Date: Tue, 2 Feb 1999 13:18:17 -0800
- Message-id: <[🔎] 19990202131816.A800@hazel.buici.com>
- In-reply-to: <Pine.LNX.3.96.990202121103.7187B-100000@wakko>; from Jason Gunthorpe on Tue, Feb 02, 1999 at 12:11:55PM -0700
- References: <19990202105450.A1703@hazel.buici.com> <Pine.LNX.3.96.990202121103.7187B-100000@wakko>
On Tue, Feb 02, 1999 at 12:11:55PM -0700, Jason Gunthorpe wrote:
> On Tue, 2 Feb 1999, Oscar Levi wrote:
> > > > I installed Debian-Alpha to test the current alpha offering. I see a
> > > > couple of hitches in the initial dselect/apt install that are tough to
> > > > track without a log file from apt. Is there some way to track why it
> > > > does what it does.
> > >
> > > apt-get <?????> -s &> order.log
> > > script session.log
> > > apt-get <?????>
> > Remember we are testing the automatic setup procedures. I'm not
> > playing dumb here. It appears we need to log the progress of
> > dselect/apt when it is running from the setup script.
> What automatic setup procedure?
Have you never installed a Debian system from scratch? When the
machine reboots after base is copied to / and configured, the system
asks for a root password and then lets the user perform an initial
install from their favorite medium, CDROM, ftp, whatever. In terms of
testing, it is very helpful to have log files available to audit
problems when we don't expect them. In order to use your method, I
need to reinstall the machine from base again.
> You can always run those command by hand and grab the output. In any
> event a log without '-s' output is pretty much pointless.
Why not always save this, albeit compressed, during the first
invocation if dpkg/apt/dselect?