Your message dated Sat, 29 Mar 2025 01:36:24 +0000
with message-id <e1tyl7y-0035le...@fasolo.debian.org>
and subject line Bug#1079329: fixed in systemd 257.4-6
has caused the Debian Bug report #1079329,
regarding systemd(?) still creates /lib64 on arm64
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 ow...@bugs.debian.org
immediately.)


-- 
1079329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Severity: serious
Justification: causes base-files.preinst to fail
User: helm...@debian.org
Usertags: dep17
Control: block 1077866 by -1
X-Debbugs-Cc: joche...@debian.org

Hi,

we're not 100% sure yet that this is systemd at cause, but it seems so
likely that I'm filing the bug here initially for further investigation.

Jochen observed that an arm64 machine with dracut would have a /lib64 ->
usr/lib symbolic link. The presence of such a link makes
base-files.preinst fail. debvm can be used to reproduce the problem:

$ debvm-create -- --architecture=arm64 --include=dracut
# creates a ./rootfs.ext4
$ debvm-run --append "rd.shell rd.break=pre-pivot"

That --append should drop you into a shell right before dracut does
pivot_root and hands off to systemd. At that time, now /sysroot/lib64
exists. Once the machine has booted /lib64 exists. At this time, the
most plausible hypothesis is that systemd still creates it despite
having been improved earlier.

Would you happen to know a good way to validate this hypothesis?

A possible approach could be enabling linux-level tracing and hooking on
the symlinkat syscall to see which processes issue it, but it could be
many. Any idea for narrowing down the component?

Thanks in advance

Helmut

--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 257.4-6
Done: Luca Boccassi <bl...@debian.org>

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1079...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luca Boccassi <bl...@debian.org> (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 28 Mar 2025 23:33:26 +0000
Source: systemd
Architecture: source
Version: 257.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 
<pkg-systemd-maintain...@lists.alioth.debian.org>
Changed-By: Luca Boccassi <bl...@debian.org>
Closes: 1079329
Changes:
 systemd (257.4-6) unstable; urgency=medium
 .
   * systemd: conflict with dracut on arm64. Same as the systemd-
     nspawn/arm64 changes of 257.4-4. As correctly pointed out on the
     reopened #1079329 this combination also creates incompatibilities, so
     add an explicit package conflict to fix this occurrence too as
     requested by the reporter. (Closes: #1079329)
   * d/control: fix systemd-boot and systemd-boot-tools descriptions
   * Add Lintian override for 'unknown-field Protected'
Checksums-Sha1:
 ac19e4de575fa0ebaa0b52fbb5bfb6439598273b 8673 systemd_257.4-6.dsc
 dd904b6ecebb69780a1662b360a502dcf2ed01f8 180720 systemd_257.4-6.debian.tar.xz
 6ee19fba0a81b3be1c4276907dfaa54fa5d287ea 14031 systemd_257.4-6_source.buildinfo
Checksums-Sha256:
 be9a40f513b7f5b58dd353496ee71f68e3419702c38da6ea7497f9e9b11c20cf 8673 
systemd_257.4-6.dsc
 85d538ed9b209c461c3555d1305b70eda3567e7bf744ea64d83f155c77891a3b 180720 
systemd_257.4-6.debian.tar.xz
 c119a0164a8e368fb0452be0e090d70a9fe88bb1a5fada9a46a0c784514c9078 14031 
systemd_257.4-6_source.buildinfo
Files:
 1d417c8b197bd51d05b5fbc29de2b0a3 8673 admin optional systemd_257.4-6.dsc
 ec924ba2df5e1e70f4243e28a807a394 180720 admin optional 
systemd_257.4-6.debian.tar.xz
 7c2d66b298f0025922db05e13830744c 14031 admin optional 
systemd_257.4-6_source.buildinfo


-----BEGIN PGP SIGNATURE-----

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmfnMgQRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB4SdQ/+JFT2QUf2ry7kPxBaYwFGIC4w0ywSm2+5
6VHO0zBB120lirNPX82LNOb/XNJZcRfMbMUL5Z5snAdbdpav630O4cJ2e1cKKL8M
Zux7RoU+Rp8hXzk7hqRY+buwrD4CslsIhqNf3KTLiQ9ndtRBNHv4YjcH4/ljP6jI
m2B+D+8yaBiGW1ZAJzTdN0eXebaJy8vhoDtq19JcYruRRpz0UGJU/Jqhg6I46xw4
75k15sxkOcxBwM3t0cY4/3md9wueC/02gzVxLfE8LrDCtCFWekPJYvkZZWolNbqJ
RX40qHUQ2no0bE6PCglBih2ILFR4O5bCUTbQNucoBuYVJr9JZFILeEUUOt7vPjYp
Qkq65QdNWD3O/raiOtSGIqZ0WzT4nFBBwhGFrqZ3rs3Qrk2Gfyv0g+CadxsgzVmH
tvhA+biQ2JA4c4clZNt/AgZLepIIUAWHEAs6279aE7cZ9v0wmYv5mcqGwqejivZh
uYGE4zr+3781iIIsGgKkVYVywjUHkoZdNg7sDlJsKB+s49+p2JwGath5FpKiCdFO
iXfm1YDRD4I+gD1QvcoHaRgOlnGYPuJmB6kJnKypeA4FYZzPrqtp3hKQq1xBmTnM
ptZoy9e/ui7VAEaw3Y+v/24ZN1gy4Du7o5fVbd0cz4ivVAESn0aP9zvS7GcGCh4L
7e2WEhIJS38=
=T7Ph
-----END PGP SIGNATURE-----

Attachment: pgpMWtzmzVFQJ.pgp
Description: PGP signature


--- End Message ---

Reply via email to