bug in backports that affects wheezy

2013-01-31 Thread Javi Merino
Hi debian-python, I'm not sure how to deal with #699405 [0]. It's a bug in squeeze-backports but presumably it also affects wheezy (I have to check that). Assuming that it does affect wheezy, should I upgrade it to "important", fix it in wheezy and then backport it to squeeze-backports? [0] htt

Re: bug in backports that affects wheezy

2013-01-31 Thread Simon McVittie
On 31/01/13 09:00, Javi Merino wrote: > Assuming that it does affect wheezy, should I upgrade it to > "important" If you think it "has a major effect on the usability of the package, without rendering it completely unusable to everyone"[1] then yes. > fix it in wheezy and then backport it to sque