Bug#887736: stretch-pu: package openvswitch/2.6.2~pre+git20161223-3

[Felipe Sateler]

On Tue, Aug 20, 2019 at 6:23 PM Adam D. Barratt <adam at adam-barratt.org.uk>
wrote:

> Control: tags -1 + moreinfo
>
> On Fri, 2018-01-19 at 15:21 +0100, Thomas Goirand wrote:
> > I started maintaining OpenVSwitch long after the Stretch release, and
> > discovered #858418, which is very annoying for OpenVSwitch users.
> >
> > tl;dr: #858418 prevent anyone that has a valid
> > /etc/network/interfaces
> > with OpenVSwitch directive from having a working network at boot. The
> > init script uses a non-documented, not-to-be-used systemd internal,
> > which is miserably failing.
> >
> > After a long discussion with the bug reporter (which can be read on
> > the BTS), I came to the conclusion that he's right, and that the most
> > reasonable and safe way to fix the current situation is to apply the
> > patch he suggested (and which resulting debdiff I attached to this
> > bug).
>
> As I understand things, that fix swaps use of one systemd internal for
> another, which doesn't seem like a great plan.
>
> When this was discussed (some time ago) on IRC, one of the systemd
> maintainers essentially said "don't do that". With apologies for the
> delay in doing so, I've CCed the maintainer list to see if we can find
> a mutually acceptable solution.
>

Both `service` and `invoke-rc.d` wrappers have a few safeguards against
running in unwanted contexts. Have you tried using one of them?

-- 

Saludos,
Felipe Sateler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190821/ecc47149/attachment.html>