Sorry, not sure what you mean exactly by "affecting a release".
This issue appeared at some point on wily (with some update, NOT at dist-upgrade) and I wonder how it could be ignored for so long, when it was first reported AND after it turned out that it had wrongly be marked as duplicate.
Sorry, not sure what you mean exactly by "affecting a release".
This issue appeared at some point on wily (with some update, NOT at dist-upgrade) and I wonder how it could be ignored for so long, when it was first reported AND after it turned out that it had wrongly be marked as duplicate.