Your message dated Fri, 08 Feb 2019 14:21:22 -0500
with message-id <[email protected]>
and subject line Re: Bug#575835: ABI breakage with libev3 3.9
has caused the Debian Bug report #575835,
regarding ABI breakage with libev3 3.9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
575835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575835
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Package: libev3
Version: 1:3.9-1
Hi,
libev 3.8 had the following definition in ev.h:
#define EVFLAG_NOSIGFD 0x00200000U /* do not attempt to
use signalfd */
libev 3.9 now contains:
#define EVFLAG_NOSIGFD 0 /* compatibility to pre-3.9 */
#define EVFLAG_SIGNALFD 0x00200000U /* attempt to use signalfd */
This means that packages compiled against libev 3.8 that explicitly disable
signalfd() instead explicitly enable it when ran with libev 3.9. This obviously
can be solved by recompiling the app in question against libev 3.9.
I found this via the awesome window manager. When libev uses signalfd, it has to
add the signals in question to the signal mask. The signal mask is inherited by
child processes which makes everything started from awesome ignore e.g. SIGINT.
Cheers,
Uli
- --
- - Buck, when, exactly, did you lose your mind?
- - Three months ago. I woke up one morning married to a pineapple.
An ugly pineapple... But I loved her!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBCAAGBQJLsOk5AAoJECLkKOvLj8sG0WwH/RypdhMmLgChFjETtbexM3WL
GkcQYe9Fw0YdWdTYLULOB1sBlnl4UvwuJ+ldOaTrYQQSlXodkE5aJLVHCJsRNcQz
q8Ep7cZfLwa8wzNh54XkebgR9igZMtLWfqURoT/I1ZZ+cAWSF9UMpT3Rn3CV6jyb
1aQjzIJGu/iz/gArl3hw/Irans7Jn0Ao6vrZeCbe1+4i4knqqY/qU2t3uBl5W7Zq
54HTNALJHOeojDj3b/maC+OVXHR/FKBdrqjFi8NssgKY/7gzRqco+o+PTWCeYss7
FrOoPwXa8t2sl9OW3USgBz4jhcn17Sszsn+1y5EYyRsz2UivIySMKeiI2i2bSkM=
=T1tc
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Version: 1:4.15-3
Now that we are using libev4 instead of libev3, the ABI has already been
bumped and I consider this bug as done.
--
Regards,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
--- End Message ---
