One other suggestion that could work for this scenario of old software is containers. Basically install the software in a container (docker/apptainer) and then use that to run it. Kind regards Detlev 20 Nov 2024 08:24:16 Simon Becherer <simon@becherer.de>:

Am 20.11.24 um 00:05 schrieb Shawn W Dunn:

...

On 11/19/24 14:40, Michael Born wrote:

...

Hi all.

Some weeks ago I was using EAGLE 7 to design a circuit board. Today it does not start anymore because of missing libraries (see below). zypper does not find a libopenssl1_0_0

How can I run the old commercial software binary on my tumbleweed computer?

Cheers, Michael

miborn@localhost:~/eagle7/lin> ldd eagle          linux-vdso.so.1 (0x00007f3a22129000) ...          libssl.so.1.0.0 => not found          libcrypto.so.1.0.0 => not found Spin up a Leap or Debian Distrobox and run it there?

qemu-kvm with old system, i did the same with a proprietary commercial software from the year 2000 take care that this box will not have connections to the outer world, because of in the future missing security updates.

you could for the short fixing of the problem use tumblweed cli, try to switch to the oldest availible version and check if the missing librarys are still there (this will only work if you encounter the problem about 2-max3 weeks after updating. i checked at the moment, they are not there anymore) then from a backup of your system, copy the files. if you have it running again, make a dd of your system and fire it up in qemu, delete everything you do not need, shrink the image, change network-address and you have a running virtual system. but most times install a new (older system) is faster/cleaner.

copy it to your proprietary software directory and check that the software find/load them. (ld-preload ore something like that will help)  -> but you will (maybe) face the same problem again in the future with other library's.

and by the way, this is not a question for this list, use for such questions support@lists.opensuse.org or users@lists.opensuse.org

simoN

-- www.becherer.de

Am 20.11.24 um 09:36 schrieb Michael Born:

Thank you all for your suggestions. I think, I will start with Leap and then read into qemu...

You can simply copy the /usr/lib64/libssl.so.1.* and /usr/lib64/libcrypto.so.1.* files of an old system, e.g. Leap 15.6, into your box. The /usr/lib64/lib{ssl,crypto}.so symlinks, if existing, need to remain intact though, do not modify these links. So no need to use qemu, chroot or similar. Cheers, Manfred

Cheers, Michael

Am 20.11.24 um 11:00 schrieb Manfred Schwarb via openSUSE Factory:

Am 20.11.24 um 10:54 schrieb Manfred Schwarb via openSUSE Factory:

...

Am 20.11.24 um 09:36 schrieb Michael Born:

...

Thank you all for your suggestions. I think, I will start with Leap and then read into qemu...

You can simply copy the /usr/lib64/libssl.so.1.* and /usr/lib64/libcrypto.so.1.* files of an old system, e.g. Leap 15.6, into your box. The /usr/lib64/lib{ssl,crypto}.so symlinks, if existing, need to remain intact though, do not modify these links.

So no need to use qemu, chroot or similar.

Oh, and if you do not have an old system, you can fetch an appropriate rpm file and extract it with rpm2cpio rpmfile | cpio -diumv --no-absolute-filenames

or just install it properly, even on tumbleweed: zypper ar http://download.opensuse.org/update/leap/15.6/sle/ sle-upd156 zypper ref -r sle-upd156 zypper in libopenssl1_0_0 # here, check what's actually installed from where... ;-) zypper mr -d sle-upd156 # disable to not pull in old stuff accidentally You should check what's installed from where of course. Having a running Leap15.6 system for reference is also handy to find what to get from where. If something wants to uninstall the libopenssl1_0_0 on every update, then you can lock it with "zypper al". If there is a security update in Leap for libopenssl, then you can reenable the 15.6 update repo temporarily and update the package. -- Stefan Seyfried "Once the rockets are up, who cares where they come down? That's not my department!" says Wernher von Braun -- Tom Lehrer

On Wed, 2024-11-20 at 13:00 +0300, Andrei Borzenkov wrote:

On Wed, Nov 20, 2024 at 12:54 PM Manfred Schwarb via openSUSE Factory <factory@lists.opensuse.org> wrote:

...

You can simply copy the /usr/lib64/libssl.so.1.* and /usr/lib64/libcrypto.so.1.* files of an old system,

libssl.so.1.1 and libcrypto.so.1.1 are still available in Tumbleweed, so it is better to not overwrite them.

consisering OP explicitly asked for openSSL 1.0.0, the presence of openSSL 1.1 won't help much here openSSL 1.0.0 was removed from Tumbleweed with snapshot 1024 - extracting the needed files either from Leap - or self-building the package in OBS - will be the sanest course of action There are still some binaries around for openSSL 1.0.0 at https://download.opensuse.org/repositories/security:/tls/openSUSE_Tumbleweed... (security:tls was the devel project of openSSL 1.0.0, and it did not yet clean up the remainders of it - giving you some chance to use it) If the packages are being installed, make sure to 'lock' them for zypper, or it will try to remove them again (due to the distro weak- remover acting when no package in the system requires the orphaned packages) Cheers, Dominique

Dominique Leuenberger wrote:

If the packages are being installed, make sure to 'lock' them for zypper, or it will try to remove them again (due to the distro weak- remover acting when no package in the system requires the orphaned packages)

For such cases, I have set up a private (local) repository where I keep such old RPMs, and switch the package to that repo.