Trying to build package in mock with tar-1.35-8.fc44.x86_64.rpm, I observe errors such as:
~~~
... snip ...
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.DQQXG9
+ umask 022
+ cd /builddir/build/BUILD/rubygem-activesupport-8.1.2-build
+ cd /builddir/build/BUILD/rubygem-activesupport-8.1.2-build
+ rm -rf activesupport-8.1.2
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/activesupport-8.1.2.gem
Unpacked gem: '/builddir/build/BUILD/rubygem-activesupport-8.1.2-build/activesupport-8.1.2'
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd activesupport-8.1.2
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/activesupport-8.1.2-tests.tar.gz
/usr/bin/tar: test/abstract_unit.rb: Cannot open: Function not implemented
... snip ...
r/bin/tar: test/cache/behaviors: Cannot mkdir: Function not implemented
... snip ...
~~~
Downgrading to tar-1.35-7.fc44.x86_64.rpm inside mock resolves the issues. I have no idea why this happens on my system while it seems that there are not issues in e.g. Koji
....
(In reply to Pavel Cahyna from comment #3)
> I can reproduce it with your config but not without it, which explains why
> we don't have more complaints like this.
>
> Try commenting out the last line:
> config_opts['nspawn_args'] += ['--suppress-sync=yes']
I suppose it is related to this comment about the use of this option in mock : https://github.com/rpm-software-management/mock/pull/1613#issuecomment-3421908652
"This broke the tests (inside a build) of bootc because the implementation of this in nspawn uses seccomp which defaults to turning off some things, in our case use of openat2(RESOLVE_IN_ROOT)."
Indeed, tar now uses openat2.
Reassigning to systemd, as systemd-nspawn is from this component (the systemd-container subpackage).
From https://bugzilla.redhat.com/show_bug.cgi?id=2437037
....