getcontext missing on some architectures, what to do with wvstreams and wvdial?

[Luca Falavigna-4]

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?

--
  .''`.
 :  :' :   Luca Falavigna <dktrkranz@...>
 `.  `'
   `-

[Luk Claes]

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 debian-release-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...