Luca Falavigna wrote: > Hello Release Team, > > I'd like to have some guidance on how to manage bug #521473, which > affects wvstreams and wvdial because they rely on getcontext and > setcontext, not available in armel and kfreebsd* implementations of > eglibc (and this feature won't probably be implemented soon). > > I was thinking about the possibility to limit architectures to the ones > getcontext/setcontext are available and functional, mangling Arch > field or by adjusting P-A-S, and asking removal for armel and kfreebsd* > binaries afterwards. > > Do you agree with this approach, or have better advices?
It's a sane approach if wvdial and wvstreams don't work without it. Otherwise it would be better to fall back to not using these on architectures that not support it. Cheers Luk -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
