Hi all,

As advised I reviewed the patch status of the Debian patche series
with the upstream source maintained by aparld.

0001-use-var-spool.patch upstreamed with
https://github.com/apalrd/tayga/commit/02cc95352dad0c9f351cfb9fb7334c38386f332b
but no longer used as commented out in upstream example, so patch
needs to be refreshed

0002-manpage.patch upstreamed with
https://github.com/apalrd/tayga/commit/33359ced1d803b5d4b328f16c8f2d5a12ffc012b
0003-configure-no-CFLAGS.patch upstreamed with
https://github.com/apalrd/tayga/commit/e504c35b7ede16642902da12062407e3a12e4d32
0004-quote-make-var.patch upstreamed with
https://github.com/apalrd/tayga/commit/230b7bc32182d65798a30193d8b5f54bf9f0b0d8
0005-guard-chdir.patch upstreamed with
https://github.com/apalrd/tayga/commit/4380c63991b04dd8edc239424a8b72be6fcf5fd7
0006-guard-write.patch upstreamed with
https://github.com/apalrd/tayga/commit/d0770307cfd5d2b3bff2264ccccf0593e1be0612
0007-static-EAM.patch upstreamed with
https://github.com/apalrd/tayga/commit/2274e5859e5b5815bcd5b253fd51fbfb40169743
0008-manpage-RFC.patch upstreamed with
https://github.com/apalrd/tayga/commit/5d9c945d6cdcb24fd39076d866688a00d27fc5fd
0009-systemd-service-file-for-tayga.patch upstreamed with
https://github.com/apalrd/tayga/commit/fa9ca99e3b83a63828c8d42ebeb544f5a6c1ddc7
0010-include-for-writev.patch upstreamed with
https://github.com/apalrd/tayga/commit/d1ca8391c788d7a0b8d9772d32ff99e17b2a43fe
0011-null-char.patch upstreamed with
https://github.com/apalrd/tayga/commit/16ea9a909e1f134a914b028362963f0f0306b6b5
0012-rfc8125-local-prefix.patch upstreamed with
https://github.com/apalrd/tayga/commit/3dde6b75b67e47f7ad929ec0a3463ce5aa35054b
0013-Fix-EAM-mapping-host-addressess.patch upstreamed with
https://github.com/apalrd/tayga/commit/68cc06f97dcbdaa8de8ed0eb61783500b822e408

0014-Use-RFC8215-WKP-by-default.patch not applied upstream, proposed
in https://github.com/apalrd/tayga/issues/151

>From my analysis:
0001 patch is to be refreshed
0002-0013 can be dropped
0014 is still needed
maintained upstream should be used to make use of the new features and
logging options as well as all the fixes.

I'rm running an instance in production and it also solves WiFi calling
when using the NAT64 when the `udp-cksum-mode§ configuration knob is
used.

Goetz

Reply via email to