Your message dated Fri, 7 Sep 2018 06:11:36 +0200
with message-id <[email protected]>
and subject line Re: systemd: please make IPv6 user space code run time
configurable
has caused the Debian Bug report #831466,
regarding systemd: please make IPv6 user space code run time configurable
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.)
--
831466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831466
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 230-5pitti1
Severity: important
Dear Maintainer,
since a few months, systemd upstream tries to implement parts of IPv6
inside systemd/networkd while we have perfectly working code inside
the Linux kernel. Unfortunately, the systemd code is wrong in so many
places that it literally takes days to diagnose the new
misbehavior-of-the-day, making it necessary to build complex test labs
or to break existing productive systems just to find out what is wrong
in systemd's IPv6 code this week.
Nevertheless, upstream has decided to make this new code mandatory,
making it necessary for distributions to derive patches to disable the
misbehavior. This takes, again, valuable developer time.
Please convince upstream to implement a run-time switch to revert to
the kernel IPv6 code just in case a system actually needs working
IPv6. It would be so much easier to help upstream to develop reliable
code if switching back and forth between kernel and user space code
was not so damn hard.
Greetings
Marc
--- End Message ---
--- Begin Message ---
On Sat, 16 Jul 2016 14:21:34 +0200 Marc Haber
<[email protected]> wrote:
> Package: systemd
> Version: 230-5pitti1
> Severity: important
>
> Dear Maintainer,
>
> since a few months, systemd upstream tries to implement parts of IPv6
> inside systemd/networkd while we have perfectly working code inside
> the Linux kernel. Unfortunately, the systemd code is wrong in so many
> places that it literally takes days to diagnose the new
> misbehavior-of-the-day, making it necessary to build complex test labs
> or to break existing productive systems just to find out what is wrong
> in systemd's IPv6 code this week.
>
> Nevertheless, upstream has decided to make this new code mandatory,
> making it necessary for distributions to derive patches to disable the
> misbehavior. This takes, again, valuable developer time.
>
> Please convince upstream to implement a run-time switch to revert to
> the kernel IPv6 code just in case a system actually needs working
> IPv6. It would be so much easier to help upstream to develop reliable
> code if switching back and forth between kernel and user space code
> was not so damn hard.
I think this is out-of-scope for a downstream change and unlikely to be
implemented upstream. So closing the bug report as wontfix.
You are free of course to take this upstream yourself. If they actually
agree to this, then we can re-open the downstream bug report for easier
tracking.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
