Your message dated Tue, 26 Jan 2021 22:07:06 +0100
with message-id <[email protected]>
and subject line Re: Bug#981007: systemd: default syscall-filter list is 
incomplete for i386 and breaks tar
has caused the Debian Bug report #981007,
regarding systemd: default syscall-filter list is incomplete for i386 and 
breaks tar
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
981007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981007
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 241-7~deb10u5
Severity: important
Tags: patch upstream
User: [email protected]
Usertags: origin-kali
Control: fixed -1 systemd/244.1-1

We are running dist-upgrade tests within systemd-nspawn containers
and since we upgraded to buster, our i386 tests, running on an amd64
host machine, are failing with messages like this one:

---
Fetched 7044 MB in 1617d 11h 20min 34s (50 B/s)
tar: ./control: Cannot utime: Operation not permitted
tar: ./md5sums: Cannot utime: Operation not permitted
tar: ./shlibs: Cannot utime: Operation not permitted
tar: ./symbols: Cannot utime: Operation not permitted
tar: ./triggers: Cannot utime: Operation not permitted
tar: .: Cannot utime: Operation not permitted
tar: Exiting with failure status due to previous errors
dpkg-deb: error: tar subprocess returned error exit status 2
---

Thanks to https://bugzilla.redhat.com/show_bug.cgi?id=1770154 I understood
that this is actually related to the lack of some system calls
in the default whitelist maintained by systemd.

This has been fixed with this upstream pull request:
https://github.com/systemd/systemd/pull/13975

So this issue is only affecting the stable version 241-7~deb10u5.
The version in buster-backports is fine, as is the version in
testing/unstable.

But it would still be nice if this could be fixed via a point release.

Thanks for maintaining systemd!

--- End Message ---
--- Begin Message ---
Am 26.01.21 um 19:03 schrieb Michael Biebl:
If systemd from bpo + libseccomp 2.3.3-4 is working for you, then there might have been follow-up changes to systemd. If you are willing to dig deeper, then we can keep this bug report open.
I'll leave it up to you, if you want to close it or not.

Rereading that part:

No big deal. Feel free to close the bug. I will not have the time
to figure out the correct fix.

Given that, I'll close the bug report.

Regards,
Michael

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---

Reply via email to