Version: 2.2.13 Hi
I cannot figure out why this bug has not been closed; as far as I can tell Lintian checks main, contrib and non-free these days[1]. The bug was cloned as #516530 (and later as #516676). I strongly suspect that somewhere between all the patches and all the clones the original bug was fixed but not closed. I have marked this as fixed in 2.2.13, because the last of the two clones were closed in 2.2.13. Therefore I assumed 2.2.13 to fix this issue; if anyone knows or have reason to believe this version information is incorrect, feel free to correct it or ask me to do it. If there is still a reason for #487515 to be open, please re-open it or write back and I will do it. Thank you in advance, ~Niels [1] At least that is what it says on http://lintian.debian.org/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
