Fedora 32: Anyone have success building akmod-xtables-addons ?

[Bill Shirley]

For years I've installed akmod-xtables-addons with no problems. Not so with Fedora
32.
It has a build error (excerpt):
[..]
Processing files: kmod-xtables-addons-5.6.12-300.fc32.x86_64-3.9-1.fc32.x86_64
error: Directory not found: 
/tmp/akmodsbuild.KP8gyCwB/BUILDROOT/xtables-addons-kmod-3.9-1.fc32.x86_64/usr/lib/modules/5.6.12-300.fc32.x86_64/extra
error: Directory not found: 
/tmp/akmodsbuild.KP8gyCwB/BUILDROOT/xtables-addons-kmod-3.9-1.fc32.x86_64/usr/lib/modules/5.6.12-300.fc32.x86_64/extra/xtables-addons

$ rpm -qa | grep -e kmod -e mock -e xtable | sort
akmods-0.5.6-25.fc32.noarch
akmod-xtables-addons-3.9-1.fc32.x86_64
kmod-27-1.fc32.x86_64
kmod-libs-27-1.fc32.x86_64
kmodtool-1-38.fc32.noarch
kmod-xtables-addons-3.9-1.fc32.x86_64
mock-2.3-1.fc32.noarch
mock-core-configs-32.6-1.fc32.noarch
xtables-addons-3.9-1.fc32.x86_64

The trouble is I don't know if this is due to a akmods (Fedora) problem or a
akmod-xtables-addons (RPMfustion) problem

Bill

[Jerry James]

On Thu, May 28, 2020 at 6:33 AM Bill Shirley <bill(a)shirleyfamily.net&gt; wrote:
>  For years I've installed akmod-xtables-addons with no problems.
> Not so with Fedora 32.
>  It has a build error (excerpt): 
I am not familiar with this particular akmod.  However, there should
be a build log in /var/cache/akmods somewhere.  If you can attach that
build log, we can see if it sheds light on the problem.
-- 
Jerry James
http://www.jamezone.org/

[stan]

On Thu, 28 May 2020 08:32:23 -0400
Bill Shirley <bill(a)ShirleyFamily.net&gt; wrote:

>  For years I've installed akmod-xtables-addons with no problems.
> Not
>  so with Fedora 32. It has a build error (excerpt):
>  [..]
>  Processing files:
>  kmod-xtables-addons-5.6.12-300.fc32.x86_64-3.9-1.fc32.x86_64 error:
>  Directory not found:
>
> /tmp/akmodsbuild.KP8gyCwB/BUILDROOT/xtables-addons-kmod-3.9-1.fc32.x86_64/usr/lib/modules/5.6.12-300.fc32.x86_64/extra
>  error: Directory not found:
>
> /tmp/akmodsbuild.KP8gyCwB/BUILDROOT/xtables-addons-kmod-3.9-1.fc32.x86_64/usr/lib/modules/5.6.12-300.fc32.x86_64/extra/xtables-addons
If you look in the /tmp directory, are there any akmodsbuild files
there, perhaps under a different key?  That is, is there a
communication problem, it is built, just not where expected.

>  $ rpm -qa | grep -e kmod -e mock -e xtable | sort
>  akmods-0.5.6-25.fc32.noarch
>  akmod-xtables-addons-3.9-1.fc32.x86_64
>  kmod-27-1.fc32.x86_64
>  kmod-libs-27-1.fc32.x86_64
>  kmodtool-1-38.fc32.noarch
>  kmod-xtables-addons-3.9-1.fc32.x86_64
>  mock-2.3-1.fc32.noarch
>  mock-core-configs-32.6-1.fc32.noarch
>  xtables-addons-3.9-1.fc32.x86_64
>  
>  The trouble is I don't know if this is due to a akmods (Fedora)
>  problem or a akmod-xtables-addons (RPMfustion) problem 
Could this have anything to do with the change from iptables to
nftables as backend in F32?

[Bill Shirley]

Build log attached.

It cleans up the /tmp directory:
$ ls /tmp
crontab.wVcyKK~
systemd-private-d1e60303890a4d22a4daf097e979ca6f-bluetooth.service-Tw72Bg
systemd-private-d1e60303890a4d22a4daf097e979ca6f-chronyd.service-icD9Ah
systemd-private-d1e60303890a4d22a4daf097e979ca6f-clamav-milter.service-gRSPQg
systemd-private-d1e60303890a4d22a4daf097e979ca6f-dbus-broker.service-viOLrf
systemd-private-d1e60303890a4d22a4daf097e979ca6f-dovecot.service-rgKyuf
systemd-private-d1e60303890a4d22a4daf097e979ca6f-httpd.service-7w82Qh
systemd-private-d1e60303890a4d22a4daf097e979ca6f-mariadb.service-BHlFof
systemd-private-d1e60303890a4d22a4daf097e979ca6f-ModemManager.service-N20beh
systemd-private-d1e60303890a4d22a4daf097e979ca6f-named.service-vI718g
systemd-private-d1e60303890a4d22a4daf097e979ca6f-openvpn-server(a)server.service-XN2Nti
systemd-private-d1e60303890a4d22a4daf097e979ca6f-php-fpm.service-4odq5g
systemd-private-d1e60303890a4d22a4daf097e979ca6f-postfix.service-ZMiyOh
systemd-private-d1e60303890a4d22a4daf097e979ca6f-systemd-logind.service-8WMvzf

Thanks for the replies,
Bill

On 5/28/2020 10:15 AM, stan via users wrote:
>  On Thu, 28 May 2020 08:32:23 -0400
>  Bill Shirley <bill(a)ShirleyFamily.net&gt; wrote:
>
> > For years I've installed akmod-xtables-addons with no problems. Not
> > so with Fedora 32. It has a build error (excerpt):
> > [..]
> > Processing files:
> > kmod-xtables-addons-5.6.12-300.fc32.x86_64-3.9-1.fc32.x86_64 error:
> > Directory not found:
> >
> /tmp/akmodsbuild.KP8gyCwB/BUILDROOT/xtables-addons-kmod-3.9-1.fc32.x86_64/usr/lib/modules/5.6.12-300.fc32.x86_64/extra
> > error: Directory not found:
> >
> /tmp/akmodsbuild.KP8gyCwB/BUILDROOT/xtables-addons-kmod-3.9-1.fc32.x86_64/usr/lib/modules/5.6.12-300.fc32.x86_64/extra/xtables-addons
>  If you look in the /tmp directory, are there any akmodsbuild files
>  there, perhaps under a different key?  That is, is there a
>  communication problem, it is built, just not where expected.
>
> > $ rpm -qa | grep -e kmod -e mock -e xtable | sort
> > akmods-0.5.6-25.fc32.noarch
> > akmod-xtables-addons-3.9-1.fc32.x86_64
> > kmod-27-1.fc32.x86_64
> > kmod-libs-27-1.fc32.x86_64
> > kmodtool-1-38.fc32.noarch
> > kmod-xtables-addons-3.9-1.fc32.x86_64
> > mock-2.3-1.fc32.noarch
> > mock-core-configs-32.6-1.fc32.noarch
> > xtables-addons-3.9-1.fc32.x86_64
> >
> > The trouble is I don't know if this is due to a akmods (Fedora)
> > problem or a akmod-xtables-addons (RPMfustion) problem
>  Could this have anything to do with the change from iptables to
>  nftables as backend in F32?
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Jerry James]

On Thu, May 28, 2020 at 8:36 AM Bill Shirley <bill(a)shirleyfamily.net&gt; wrote:
>  Build log attached. 
It shows that nothing was built.  Take a look at the
"Executing(%build)" part.  There is a make invocation, followed by
nothing.  Stan is probably right; the change from iptables to nftables
may have broken this module.  Possibly relevant:

https://www.spinics.net/lists/netfilter/msg59160.html
-- 
Jerry James
http://www.jamezone.org/

[stan]

On Thu, 28 May 2020 08:54:41 -0600
Jerry James <loganjerry(a)gmail.com&gt; wrote:

>  On Thu, May 28, 2020 at 8:36 AM Bill Shirley
> <bill(a)shirleyfamily.net&gt;
>  wrote:
>  > Build log attached.  
>  
>  It shows that nothing was built.  Take a look at the
>  "Executing(%build)" part.  There is a make invocation, followed by
>  nothing.  Stan is probably right; the change from iptables to nftables
>  may have broken this module.  Possibly relevant:
>  
>  https://www.spinics.net/lists/netfilter/msg59160.html 
From discussions on the -devel list, I think there is a setting for
firewalld that reverts to using iptables.  Check man firewalld?  Look in
/etc/firewalld?

If you can, that would be a workaround until this gets fixed.  Opening
a ticket at rpmfusion's bugzilla, if there isn't already one, would put
the issue on their radar.

https://bugzilla.rpmfusion.org/

[Bill Shirley]

Stan, thanks for your reply and your time.  You too, Jerry.

I'm using Shorewall and iptables instead of firewalld.  I've used this for years.
nftables configuration seems overly verbose to me.

I created a rpmfusion bugzilla. https://bugzilla.rpmfusion.org/show_bug.cgi?id=5662

Bill

On 5/28/2020 11:39 AM, stan via users wrote:
> On Thu, 28 May 2020 08:54:41 -0600
> Jerry James <loganjerry(a)gmail.com&gt; wrote:
>
>> On Thu, May 28, 2020 at 8:36 AM Bill Shirley <bill(a)shirleyfamily.net&gt;
>> wrote:
>>> Build log attached.
>> It shows that nothing was built.  Take a look at the
>> "Executing(%build)" part.  There is a make invocation, followed by
>> nothing.  Stan is probably right; the change from iptables to nftables
>> may have broken this module.  Possibly relevant:
>>
>> https://www.spinics.net/lists/netfilter/msg59160.html
>  From discussions on the -devel list, I think there is a setting for
> firewalld that reverts to using iptables.  Check man firewalld?  Look in
> /etc/firewalld?
>
> If you can, that would be a workaround until this gets fixed.  Opening
> a ticket at rpmfusion's bugzilla, if there isn't already one, would put
> the issue on their radar.
>
> https://bugzilla.rpmfusion.org/
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]