My two cents about such bug: " package xxxx is already installed and configured "
- it have been seen at least since Precise
- Apport blame dpkg
- but i'm using 'synaptic' instead of the now defaulted 'software-center' in ubuntu, and never met such a bug on my systems
- as i understand, when a package is installed & configured, its status is not updated as expected
So Software-center, or one of its dependencies, should be blamed instead of dpkg. Those are never fixed and upstream never know about them.
Apport wrongly blame dpkg, and does not understand the repeating " package xxxx is already installed and configured " and is disturbed by the package name, which can be randomly every package in the archive. So it never detect duplicates in such a case.
Looks like the now applied tests have missed such a possiblity.
@Brian
My two cents about such bug: " package xxxx is already installed and configured "
- it have been seen at least since Precise
- Apport blame dpkg
- but i'm using 'synaptic' instead of the now defaulted 'software-center' in ubuntu, and never met such a bug on my systems
- as i understand, when a package is installed & configured, its status is not updated as expected
So Software-center, or one of its dependencies, should be blamed instead of dpkg. Those are never fixed and upstream never know about them.
Apport wrongly blame dpkg, and does not understand the repeating " package xxxx is already installed and configured " and is disturbed by the package name, which can be randomly every package in the archive. So it never detect duplicates in such a case.
Looks like the now applied tests have missed such a possiblity.