www-client/seamonkey-2.53.17.1 - slot(0) no change in 37 days for unstable keywords: [ ~amd64, ~x86 ]. If you agree to stabilization, please add CC-ARCHES to Keywords-field.
@amd64 please stabilize. x86 build is broken for this version due to newer compiler version, so skip this version on x86.
amd64 done all arches done
I wonder if we should just drop x86 stable keywords? 2.53.17 is still vulnerable to the libwepb thing so no one should be running it anymore.
(In reply to Joonas Niilola from comment #3) > I wonder if we should just drop x86 stable keywords? 2.53.17 is still > vulnerable to the libwepb thing so no one should be running it anymore. It seems like seamonkey upstream didn't want to include the patch of Bug 915336, because firefox never had this patch included. It seems firefox has still the x86 keyword, I guess they updated the offending 3rg party library. I see last weekend 2.53.17.1 got a hot fix included. 2.53.18 has it's first beta released and I encountered some new issues with that. I don't know when upstream intends to do a final release for 2.53.18, so I suggest to do a 2.53.17-r1 with a few extra patches added, so that x86 can also get this. I'm not in favour of dropping keywords for things that can't be solved.
