I don't know if reopening is the right thing to do, but I'm running an
up to date testing system where this bug still is around.

Since I'm merely a user, I don't have full understanding of how debian's
package upgrading paths are. However there has passed almost one week
since Mr. Langasek: wrote will be fixed tomorrow.

Are the fixed packages propagating through a pipe somewhere, or is the
bug still around?
--
/Martin

Attachment: pgpUKrGS4nEWd.pgp
Description: PGP signature

Reply via email to