Hi Henry
Yes the error messages may be the cause of this blocking. Interesting
note. I'll look into this later today.
Best regards,
// Ola
Quoting henryb...@fsfe.org:
Ola
Many thanks for your help
I attach
- Logfile.txt.
This should be the clean system with the failing lines in
sources.list removed
- Logfile_2.txt
This is with a bad entry in sources.list
One minor comment: aptitude (apt-get) did not fail because of the
problem in the sources.list. If with the bad sources.list, I ran
aptitude update
aptitude full-upgrade
Then all worked, albeit with error messages :)
The problem seemed to be when called from cron-apt the notification of
error messages blocked the program from running further
--
Henry
On Mon, May 04, 2009 at 04:08:46PM +0200, Ola Lundqvist wrote:
Hi Henry
You have found the problem, so it is not so much for me to do. :-)
Basically cron-apt can only do that apt (or aptitude) can do and in this
case it fails because of a problem with the sources.list file.
A bit interesting that it was not logged though. I think that can be
improved for later releases. I think it is because errors were not sent
to the logging process.
If you run
apt-get > logfile.txt 2>&1
with the -x option enabled as I described in an earlier mail I think I
can tell that for sure.
Best regards,
// Ola
--
--- Inguza Technology AB --- MSc in Information Technology ----
/ o...@inguza.com Annebergsslingan 37 \
| o...@debian.org 654 65 KARLSTAD |
| http://inguza.com/ Mobile: +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
