First - As a maintainer - I get source code from Oracle and fix it to build within Open Build System. I don’t get to start with a patched.tar.bz2 file - I create that so obs can build the it and I can test it before we submit it to Factory.
Nowhere does he say how he installed it - it shows the a path to a file I was not familiar with.
As a maintainer I see this path on failures -
/home/user/home:larryr:branches:Virtualization/virtualbox/VirtualBox-7.0.10/src/VBox/VMM/VMMAll
If this is the path that the OBS factory builds and installed from yast or zypper - I was not aware of that.
/home/abuild/rpmbuild/BUILD/VirtualBox-7.0.10/src/VBox/VMM/VMMAll/PGMAll.cpp(3850)
/usr/lib/rpm/rpmuncompress -x /home/abuild/rpmbuild/SOURCES/VirtualBox-7.0.10-patched.tar.bz2
I would like to see this when VirtualBox has an issue:
# zypper se -si virtualbox
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+----------------------------------+---------+---------------------+--------+---------------------------------------
i+ | python3-virtualbox | package | 7.0.10-4.1 | x86_64 | openSUSE-Tumbleweed-Oss
i+ | python3-virtualbox-debuginfo | package | 7.0.10-4.1 | x86_64 | openSUSE-Tumbleweed-Repository (DEBUG)
i+ | virtualbox | package | 7.0.10-4.1 | x86_64 | openSUSE-Tumbleweed-Oss
i+ | virtualbox-guest-tools | package | 7.0.10-4.1 | x86_64 | openSUSE-Tumbleweed-Oss
i+ | virtualbox-kmp-default | package | 7.0.10_k6.5.3_1-3.4 | x86_64 | (System Packages)
i+ | virtualbox-kmp-default | package | 7.0.10_k6.5.2_1-3.3 | x86_64 | (System Packages)
i+ | virtualbox-kmp-default | package | 7.0.10_k6.5.4_1-4.1 | x86_64 | openSUSE-Tumbleweed-Oss
#