Thanks. I cannot reproduce it but I think that the problem is something like:
- A package and its predependency set the same trigger. It is set once for the
predependency.
- The package and the predeps are unpacked
- The predeps are configured (but the trigger is not activated since is waiting
for the main package to configure)
- The package is configured but the installation is suddenly interrupted (and
here is the point that I cannot reproduce being unable to find how and exactly
when it must be interrupted) and the trigger is not executed.
- The installation reach a unstable state where dpkg (or apt) thinks that the
predep is correctly installed but the trigger was not executed.
- On the next installation dpkg (or apt) tries to configure a package (the
predep) already marked as configured.
** Changed in: dpkg (Ubuntu)
Status: Incomplete => Confirmed
--
package gcc 4:4.4.4-1ubuntu2 failed to install/upgrade: package gcc is already
installed and configured
https://bugs.launchpad.net/bugs/604305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
