[Bug 1186710] New: wrong/dead symlinks with kernel-default-devel-5.12.4-2.1.x86_64 (after usrmerge?)
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 Bug ID: 1186710 Summary: wrong/dead symlinks with kernel-default-devel-5.12.4-2.1.x86_64 (after usrmerge?) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: munix9@googlemail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- $ rpm -q kernel-default-devel kernel-default-devel-5.12.4-2.1.x86_64 $ ls -l /lib lrwxrwxrwx 1 root root 7 May 25 07:58 /lib -> usr/lib/ $ ls -l /lib/modules/5.12.4-2-default total 0 lrwxrwxrwx 1 root root 53 Jun 1 21:16 build -> ../../../usr/src/linux-5.12.4-2-obj/x86_64/default lrwxrwxrwx 1 root root 34 Jun 1 21:16 source -> ../../../usr/src/linux-5.12.4-2 but that is one level too few, this are dead symlinks. it should be lrwxrwxrwx 1 root root 53 Jun 1 21:16 build -> ../../../../usr/src/linux-5.12.4-2-obj/x86_64/default lrwxrwxrwx 1 root root 34 Jun 1 21:16 source -> ../../../../usr/src/linux-5.12.4-2 I manually changed this for testing in a chroot environment to compile a kernel module. Without changing the original symlinks I get errors when compiling the module. After creating the correct symlinks, the module compiled correctly. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ro@suse.com, tiwai@suse.com --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- Likely an ill effect of brp-25-symlink? kenrel-*.spec merely creates a normal symlink to /usr/src/linux-obj-*. It's converted to the relative path by that script, IIRC. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c2 --- Comment #2 from Paolo Panto <munix9@googlemail.com> --- Found this in https://build.opensuse.org/public/build/Kernel:stable/standard/x86_64/kernel... [10738s] NO_BRP_STRIP_DEBUG is set: skipping strip [10738s] calling /usr/lib/rpm/brp-suse.d/brp-25-symlink [10739s] INFO: relinking /lib/modules/5.12.8-1.g9404e18-default/build -> ../../../usr/src/linux-5.12.8-1.g9404e18-obj/x86_64/default (was /usr/src/linux-5.12.8-1.g9404e18-obj/x86_64/default) [10739s] ERROR: link target doesn't exist (neither in build root nor in installed system): [10739s] /lib/modules/5.12.8-1.g9404e18-default/source -> /usr/src/linux-5.12.8-1.g9404e18 [10739s] Add the package providing the target to BuildRequires and Requires [10739s] INFO: relinking /lib/modules/5.12.8-1.g9404e18-default/source -> ../../../usr/src/linux-5.12.8-1.g9404e18 (was /usr/src/linux-5.12.8-1.g9404e18) -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c3 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek@suse.com --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- Ah that's a ill effect of the recent UsrMerge... Possibly depending on the installation order, etc. The relative link is created at the time of package creation, and that's correct, per se. But, maybe we need to drop /usr in kernel-*.spec conditionally for TW. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c4 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com --- Comment #4 from Ludwig Nussel <lnussel@suse.com> --- looks like there is no way for a package to omit brp-25-symlink :-/ So choices are - buildignore brp-check-suse - make brp-check-suse detect usrmerge incompatible relative links - move the kernel modules to /usr Meanwhile quick workaround would be ln -s . /usr/usr -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- (In reply to Ludwig Nussel from comment #4)
looks like there is no way for a package to omit brp-25-symlink :-/ So choices are
- buildignore brp-check-suse - make brp-check-suse detect usrmerge incompatible relative links - move the kernel modules to /usr
Meanwhile quick workaround would be ln -s . /usr/usr
I'm afraid that the relative symlink is bad in this case. The kernel package from the latest build is often used on a Leap or SLE system, and this would break things. And a similar problem is about the definition of %_firmwaredir. On TW, it's /usr/lib/firmware, but this path isn't looked up by the kernel. The kernel lookup path is only /lib/fimrware (and subdirs). This will make the package built for TW containing a firmware wouldn't be usable on the old distros any longer. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c9 --- Comment #9 from Paolo Panto <munix9@googlemail.com> --- (In reply to Ludwig Nussel from comment #4)
looks like there is no way for a package to omit brp-25-symlink :-/ So choices are
- buildignore brp-check-suse - make brp-check-suse detect usrmerge incompatible relative links - move the kernel modules to /usr
Meanwhile quick workaround would be ln -s . /usr/usr
thx, this helps https://build.opensuse.org/package/show/home:munix9/tmp-usrmerge-fix https://build.opensuse.org/package/show/home:munix9/vmware-host -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c19 Christophe Giboudeaux <christophe@krop.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Larry.Finger@gmail.com --- Comment #19 from Christophe Giboudeaux <christophe@krop.fr> --- *** Bug 1186899 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c21 --- Comment #21 from Takashi Iwai <tiwai@suse.com> --- *** Bug 1186899 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c22 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markus.kossmann@gmx.de --- Comment #22 from Takashi Iwai <tiwai@suse.com> --- *** Bug 1186904 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c23 --- Comment #23 from Stephan Kulow <coolo@suse.com> --- Rudi's patch won't work, the glob is the link *target* not the link itself. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c24 --- Comment #24 from Stephan Kulow <coolo@suse.com> --- https://github.com/openSUSE/brp-check-suse/pull/44 - the problem with the firmware I don't see on my installation, so I can't verify. -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c25 Achim Herwig <achim.herwig@wodca.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |achim.herwig@wodca.de --- Comment #25 from Achim Herwig <achim.herwig@wodca.de> --- Still present in kernel-default-devel-5.12.9-1 -- You are receiving this mail because: You are the assignee for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1186710 http://bugzilla.opensuse.org/show_bug.cgi?id=1186710#c27 --- Comment #27 from Takashi Iwai <tiwai@suse.com> --- (In reply to Stephan Kulow from comment #24)
https://github.com/openSUSE/brp-check-suse/pull/44 - the problem with the firmware I don't see on my installation, so I can't verify.
There was a breakage in sof-firmware package (which was already fixed meanwhile), but it's not directly related with brp-check-suse, I guess. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com