On Mon, 03 Nov 2014, Osamu Aoki wrote: > I think that the use of backported current testing package is the > reasonable option. The updates listed in the upstream changelog (see
Yeah, I am running a 4.46.0-1 backport in stable, it works perfectly in my usercase (which is rather simple, but still...) I could upload it to backports.org, but that leaves a security bug in stable unaddressed. > Quite frankly, I am not competent enough to extract a correct set of > patches out of these changes without breaking the program? It is too > risky since even upstream had few regressions. Yeah, I agree that trying to isolate the changes would be too risky. The stable release managers would have to aprove a full 4.46.0 update to address this in -stable. We'd have to ask them to know if this would be acceptable. If it isn't, it might make sense to downgrade the bug report to "important". > The changelog entry in 4.46.0 implied Python 2.6 or newer. The available > Python versions are: > oldstable 2.6.6-3+squeeze7 OK > stable 2.7.3-4+deb7u1 OK Well, I can attest that it works well in stable. And yes, the Version: 4.2.0-1 was a mistake. I will try to clean it up, but since it is missing the getmail4/* prefix, the BTS might not cooperate. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
