[PKG-Openstack-devel] Bug#858418: Bug#858418: Is it possible to release fixed packages now?

[Thomas Goirand]

On 01/09/2018 07:13 PM, Kepi wrote:
> Is it possible to release fixed packages soon?
> 
> This bug is making remote systems unaccessible after reboot, IMHO
> serverity should be critical. I don't think it is acceptable to have
> such bug for more than half year on stable distribution.
> 
> I can confirm that upstream patch mentioned by Nicolas is working.
> 
> Thanks

Hi,

While upstream patch may indeed fix the issue, it still relies on the
SYSTEMCTL_SKIP_REDIRECT systemd internal. Using any of these is in fact
*very wrong* and should never be used in the packaging of any package in
Debian. If you don't trust me, you can attempt asking the systemd
maintainers about this.

For this reason, unfortunately, it is very unlikely that the release
team will accept such a change in the stable release, and they will
likely ask for a better fix.

So, we should come up with a better way to fix the issue, a way that
will be accepted by the release team. According to my own experience, it
is also very unlikely that the release team will accept some new
.service files either, unfortunately.

I'd very happily accept any contribution if it's good enough. Though I
may very much dislike gratuitous comments on how much the work of
current package maintainers is unacceptable, even if I only very
recently started to take care of the OpenVSwitch package (ie: at least 6
months after this bug was opened, and many months after Stretch was
released). So please, Kepi, moderate yourself. FYI, I've been thinking
for a long time about ways to fix this problem, but so far haven't
figure out an acceptable way.

BTW, I don't agree severity should be set to critical. Definition for
critical is:

"makes unrelated software on the system (or the whole system) break, or
causes serious data loss, or introduces a security hole on systems where
you install the package."

Here, only the network as controlled by OpenVSwitch breaks (ie: only
OpenVSwitch breaks), and there's no data loss or security hole. Besides
this, it's not ideal, but it can be worked around by not using
/etc/network/interfaces for configuring OpenVSwitch. There's multiple
ways to achieve that. Yes, it's not ideal, but until we find a
satisfying way (in the eyes of the release team, that is) to fix the
issue, I don't think there's a choice, and that's still a workaround.

Last, is Philippe Latu's solution working? It doesn't feel right to me,
and didn't have time to test it out...

Cheers,

Thomas Goirand (zigo)