On 05/11/2007, Bob Proulx <[EMAIL PROTECTED]> wrote: > Aptitude has so far not worked very well with wrapper programs such as > cron-apt.
> See also Bug#438537 for more discussion of this I see. (and indeed with APTCOMMAND=/usr/bin/apt-get OPTIONS="-o quiet=1 -o Apt::Get::List-CleanUp=false -o Dir::Etc::SourceList=/path/to/sources.list -o Dir::Etc::SourceParts='/dev/null'" everything seems to work correctly) The reason i wanted aptitude is simply that the config file is full of references to aptitude so i assumed it was safe to use it. Specifically the comments at the top of the file suggest it is useful. So i suggest clarifying the situation there a little, perhaps something like: # The command used to execute all actions. By default, apt-get is used. -# Change this to /usr/bin/aptitude to use aptitude instead, which will -# resolve changed Recommends (and Suggests as well, if aptitude is so -# configured). You can also set other utilities (especially useful in the -# config.d directory) so set some completely different tool. -# OBSERVE that this tool is indended for apt-get and tools like aptitude do not -# have full support for noninteractive upgrades. You may have to tune options -# to not create infinit logfiles for example. +# You can use any program you like here (or more usefully, you can set a different value in any +# file in config.d). +# Note that although aptitude is the recommended tool for interactive upgrades, +# for cron-apt's purposes apt-get is better, and (for most configurations) the extra +# features of aptitude are not relevant here: you can use aptitude, but it is not recommended. +# If you do insist on using aptitude, you will +# have to work around some of its bugs as described in later comments. +# The default is /usr/bin/apt-get (see also +# Debian bug #438537). +# APTCOMMAND=/usr/bin/apt-get +# APTCOMMAND=/usr/bin/aptitude +# APTCOMMAND=/usr/bin/apt-file -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
