On Fri, March 23, 2007 06:56, Colin Watson wrote:
> Could somebody get a log of this failure with DEBCONF_DEBUG=developer
> set in the environment? It would help to see what's actually happening.
I will try to run adept_updater in the following manner:
sudo script -c ~/tmp/DebugAdept.sh
where "~/tmp/DebugAdept.sh" contains:
#!/bin/sh
DEBCONF_DEBUG=developer
sudo adept_manager
I will then e-mail the contents of the script file to you.
Will this capture all the details you need?
Dan
P.S. I don't have any updates pending at the moment... :(
- - - -
"Wait for that wisest of all counselors, time." -- Pericles
"I do not fear computers, I fear the lack of them." -- Isaac Asimov
On Fri, March 23, 2007 06:56, Colin Watson wrote: DEBUG=developer
> Could somebody get a log of this failure with DEBCONF_
> set in the environment? It would help to see what's actually happening.
I will try to run adept_updater in the following manner:
sudo script -c ~/tmp/DebugAdept.sh
where "~/tmp/ DebugAdept. sh" contains: DEBUG=developer
#!/bin/sh
DEBCONF_
sudo adept_manager
I will then e-mail the contents of the script file to you.
Will this capture all the details you need?
Dan
P.S. I don't have any updates pending at the moment... :(
- - - -
"Wait for that wisest of all counselors, time." -- Pericles
"I do not fear computers, I fear the lack of them." -- Isaac Asimov