Guo Yixuan wrote:
>Hendrik Boom wrote:
>> I just did a routine
>>
>> aptitude safe-upgrade
>>
>> from the root command-line on an 1386 Debian testing system. Here are
>> the past few lines in its output. Is this anything to worry about? Or
>> just an unimportant problem that will fix itself in some future upgrade?
>>
>> setting up tassksel-data
^^^^^^^^^^^^^
if this is not a typo on your part then
this could be a problem elsewhere:
"tassksel-data" is not a package, but "tasksel-data" is...
>> setting up tasksel
>> Processing triggers for mane ...
>> Processing triggers for python-support ...
>> Error: Timeout was reached
>>
>> Current status: 328 updates [-159]
>> notlookedfor:~ #
>>
>> "notlookedfor" is the machine name, part of the root shell prompt.
>>
>> -- hendrik
>
> Hi,
>
> I also get warnings like this recently. It starts about two weeks ago,
> and a internet search doesn't turn up many useful results on this
> problem, only with some similar report for ubuntu.
>
> Searching "Timeout was reached" in aptitude's source code doesn't have
> any results either... maybe its a bug in something that aptitude depends
> on (such as apt or dpkg).
songbird
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/417a89-o6q....@id-306963.user.uni-berlin.de
