*pypolicyd-spf-1.3.1 (05 Jun 2014) 05 Jun 2014; Michael Orlitzky <mjo@gentoo.org> +pypolicyd-spf-1.3.1.ebuild, -pypolicyd-spf-1.3.ebuild: Version bump; remove v1.3 due to upstream bug #1325579.
dev-python/pyspf-2.0.10 breaks current stable mail-filter/pypolicyd-spf-1.1, I think. Trace callback about addr2bin.
(In reply to floppe from comment #1) > dev-python/pyspf-2.0.10 breaks current stable mail-filter/pypolicyd-spf-1.1, > I think. > > Trace callback about addr2bin. Yeah, I know, sorry. This bug depends on bug #529494 where another problem with pyspf-2.0.10 is reported. I'd really like pyspf-2.0.11 to go stable so that I can stabilize the new pypolicyd-spf, but they're both stuck waiting on pydns (bug #532318). As soon as I can, I'll CC the arches to get this done.
Encountered this today. In my case it caused mails to be rejected. Very bad. https://answers.launchpad.net/pypolicyd-spf/+question/232582 According to the maintainer, pyspf 2.0.8 is what broke pypolicyd-spf prior to 1.2 This should be addressed ASAP since it can cause rejections
(In reply to Mark LaCroix from comment #3) > > According to the maintainer, pyspf 2.0.8 is what broke pypolicyd-spf prior > to 1.2 > > This should be addressed ASAP since it can cause rejections I'm not the maintainer for pyspf or pydns, nor am I on the arch teams, so I'm not allowed to stabilize those packages. I agree this should be fixed ASAP, but the best place to complain is on those two bugs I mentioned. The arch teams may have a priority list of packages to stabilize, and I'm sure they have no idea that those two are particularly important.
I also think that the version 1.3.1 should be stabilised. The actual stable version does not work very well when the upgrade in 1.3.1 solved the problem as said in https://forums.gentoo.org/viewtopic.php?p=7738960
arches are already CCed in blocking bug :)
The current stable tree is now broken in a way that can cause mail rejections on upgrade. This should have been stabilized alongside pyspf, but wasn't.
I tested 1.3.2-r1 for bug #559364 and everything looks good with only python3. Thanks for the fix, Michael.
It hasn't been 30 days yet, but: * By the time bug #529494 is resolved, it will have been. * There's a known conflict with v1.3.1. So I'm changing this stablereq to target the latest version.
amd64 stable
x86 stable
