Bug#669060: marked as done (Apt: E: Internal error: APT::pkgPackageManager::MaxLoopCount reached in SmartConfigure)
Your message dated Thu, 19 Apr 2012 00:55:56 +0200
with message-id <20120418225556.GR3626@xvii.vinc17.org>
and subject line Re: Bug#669093: Reassignment to libapt-pkg4.12 considered desirable
has caused the Debian Bug report #669093,
regarding Apt: E: Internal error: APT::pkgPackageManager::MaxLoopCount reached in SmartConfigure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
669093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669093
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 0.9.0
Severity: serious
Hi,
I'm seeing lots of errors like:
E: Internal error: APT::pkgPackageManager::MaxLoopCount reached in SmartConfigure for libapt-inst1.5:i386, aborting
E: Internal error: APT::pkgPackageManager::MaxLoopCount reached in SmartConfigure for libapt-inst1.5:amd64, aborting
E: Internal error: APT::pkgPackageManager::MaxLoopCount reached in SmartConfigure for adduser:amd64, aborting
Kurt
--- End Message ---
--- Begin Message ---
Version: 0.9.1
On 2012-04-18 23:51:19 +0200, Vincent Lefevre wrote:
> reassign 669093 libapt-pkg4.12
> found 669093 0.9.0
> thanks
Grrr... this reopened the bug. Closed it again.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
Reply to: