Hello Should this bug really be marked as fixed? This renders it quite difficult to find through the standard Debian BTS. I had the issue, and my first reflex is to check the BTS - I did not find any info about it so I turned to google, which luckily gave me the #710920 reference.
It is marked as a duplicate of #710877, which is displayed by the BTS but with a less specific subject, so it is harder to pinpoint. Could there be a possibility of enhancing the visibility of #710920 at least as long as the faulty package is still in testing? Best regards, Olivier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
