Source: mptcpd
Version: 0.12-4
Severity: important
Tags: upstream

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Sorry, I messed up: libell dropped a few symbols with release 0.69, and
I sloppily assumed it was old obsolete ones unused anywhere - without
thoroughly checking that assumption.

Affected packages are iwd (maintained by me, and fixed upstream already
so required just a rebuild) and mptcpd, where I've reported the issue:
https://github.com/multipath-tcp/mptcpd/issues/302

Now, for the Debian use of libell, I see multiple ways forward now:

a) I revert libell to version 0.68 (i.e. with 0.69+really0.68)
   and halt progress on libell and iwd until mptcpd supports 0.69.
b) I revert libell to version 0.68 (i.e. with 0.69+really0.68)
   and reintroduce libell 0.69 under a new Debian-specific API,
   which can then enter unstable but can only migrate to testing
   when also supported by mptcpd.
c) Someone says "pfff, that's easy peasy to patch in mptcpd",
   releases mptcpd in Debian with that patch,
   and also forwards the fix upstream.

Anyone feel like the hero for doing c), saving me from rolling back the
mess I've caused here?

 - Jonas

- -----BEGIN PGP SIGNATURE-----

iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbf6AcMHGRyQGpvbmVz
LmRrAAoJECx8MUbBoAEhHNoQAJURF8aEBP15UgB756woFFdNf2dox9AYssZepuS8
ImUty55pdZ6IjsPwpcUDeNKsyjWufZA4zjMNRYlehwMI2xYx9eYMvFqt87XET7mY
Tcj4Q1EsFcTqbUxLXrIC8VYEf2Z8BzWSRBaInPmyS85jvTmEu5S1icsa9WEYGMVC
yvczm6uZVf9Eap3oPs9Xvzpbz5bQVhM4TW/TPlQDkc1FNQtbq/Fdom/5zC92xNI4
n4Mt7rNHEfxOMy1T8obkfygVu6zpW8u+AnUPRejEOQPg+JFxWa5ABBsB69cd8P8Z
ZzivOYS08HzYRo6OYitJIaC3Oz1Lc3inIeaE2RBiGbx7nifmuEAK4ToMmuF5Pjd5
9HTciFa96G9F6lynHoxUcyHmLhy/CZLQIY7I+99UJZTYkwTqfCWtyW2hDpUd2rj0
ngByXpnq27tK7FJSTaWQ7f5zHx6aRdP4O5pSXh2gnzrSyzVwydR6GFyyVjLnWdwk
H+a0mWR6kFavmKPPOF2EV/IkGMxR7wfOHNEwfjKpk/En2bGWb+uQST9Qbn4GL9wi
KYOS2Zfeb/orcOk6nTC3lzda2ixqy0qYg0c1edNWWCVEDFUW2qA3QlNIN+FeZ51Z
x2vlTiFFpJHvS9LFhDdRHHqYJU7i7eaetejJw0Wtr1PUuSvsOUkpeN5kWvMYuyiJ
3yH9
=00Ml
- -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNATURE-----

iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmbf6ccMHGRyQGpvbmVz
LmRrAAoJECx8MUbBoAEhDC0QAIgQFA31UeNU2Qv7+4iuZtny1kjmhibqGaOwUQxx
PHmrOrDsOMEopXQUq4MwmAup+H6hMkQUSFktV8WI0okzesmS37LuGERotxOmRQAN
LsjJzrRfHbp94Ki0cr3lE3QRVbQ+7VJIBBWyep5zT3LRBzOjcT86Lir4sH+gt6j5
o0ws+0b2WjgzHwGDx97oj00xTpICu/smaunzEI6CS6yw9WMsFFFzBSkxot+ZQMxI
BZeL5KhHFu1LOoXJZ27as5uxrw3Lp6BXRgOuSUMF3TeARc+A2FwCd16j1WIaEpwg
bpqfzvz6Phj3bX0zzOnSIZpYgRmICCflFhb99s44LsPjxjCFrxonohSKXNCIYSE0
kkHxYlJ/9RwxIfv5BMICLADwQAAyEYuxbr+TRUS6Pg/wpbMb7KsvRRUpgzQayMyi
F6Y2uTYO4Pi94fCDDyzizsfs2XD6xmbE6omvqBsRl92MWSkMzoQfI3zABUz1LohY
gKRZZUkl1k6ahENMuBGUia+p5xtpzyoHAdyr8qTrc/zFK7dGm0GOMfXlkHyk+lQe
RdJ38y5WiECF/RrZG9HO/tNWEXHJqq4MIwEzGlBGVsorr7YXrr97AJtin290vYfB
H6d7vhV3Fdc6LrkhIHIXKOpwNpbDSZRkp9zFnWs+CrICrXy1EIeExtCTmmr4RF/u
Y8QN
=1E2p
-----END PGP SIGNATURE-----

Reply via email to