On Thu, 25 Oct 2018 at 11:39, Chris Boot <[email protected]> wrote: > > So, in this case, perhaps the proper fix is for ferm to don't hardcode > > binary paths. > > Perhaps, but in that case a list of broken packages is going to need to > be compiled, bugs filed against them, and (versioned) Breaks added to > iptables to make sure that people's systems are not broken by this. > > It's also going to need a NEWS.Debian entry if there isn't one already > (I haven't checked) because people will have written scripts which > hard-code the old paths. >
Ok, I agree, fair enough. Are we sure that if we introduce some temporal/compatibility symlinks for buster, we won't have the same problem again in buster+1? i.e, at some point the symlinks in /sbin need to be dropped anyway, are we sure a stable release in between is enough time? Any volunteers to do this work? The available time I have to work in this package right now is very little.
