> > Fair enough. I think the previous release sat in my distro's repos for
> > around 18 months before we got 1.18.11, so I was hoping I wouldn't have
> > to wait that long again before 1.18.12 comes along and gets my
> > bandwidth monitoring scripts working again!
>
> Which distribution are you using?
Arch Linux. They're not particularly open to customising things,
preferring to stick to upstream releases as closely as possible.
> > I'll probably do a custom package with the git version, then I can get
> > things going once more without hassling you for more frequent
> > releases :)
>
> Can't you file a ticket in downstream bug tracker and request a
> backport? They probably also want commit 40406dbfaefbc ("nft: fix
> interface comparisons in `-C` commands").
I could but I've tried before and unless it's a serious problem you're
usually out of luck. They instead prefer to push the maintainers to do
another release so they can just bump the version number in their
package build scripts.
It's not too bad, Arch has a user repository for packages and I have
found that someone has already made a package build script for the git
version of iptables, so I tried installing that and it has fixed the
problem, so my immediate concern is sorted now.
I just have to remember to remove the git version and go back to the
official package when the next version of iptables comes out, as the git
packages don't update automatically.
Thanks again for getting a fix for this done so quickly.
Cheers,
Adam.
