It won't help with the question in my environment:
The update for an all-in-one appliance from Filr 24.x to 24.4 went without any major problems today. The update of the Conntend Editor appliance also went smoothly.

Questions? Is it an all-in-on appliance? And was the appliance ever patched via zypper on the cli? And what was the previous version from which the upgrade to 24.4 is to be carried out?

What you see in the screenshot means that there is a file conflict for the update which needs to be resolved.
What I can advise from experience, but without support, is to shut down the appliance, perform a backup (please do not take a snapshot with VMware or similar). Restart and search for the repo conflicts in the cli with zypper. Then resolve them. The safest thing to do is to open a call

George

Yes, it is an all-in-one appliance; I was about to say that no, it's never been patched via the CLI, but now thinking about it and paying a little more attention to exactly which modules it's complaining about I realize that those are the modules I installed with zypper so that I could run .acme.sh for SSL certificate renewal. 

So this is a problem of my own creation.  I'll remove those 3 modules, let the upgrade to 24.4 complete and then see about getting socat tools and the two libraries it needs back again (or find a better way to get ssl certificates).

Thanks for your reply, you got me thinking down the right path.

Do you have Filr Standard or Advanced?
i had done the Upgrade today without trouble or error Messages

After the update a Reboot from the appliance and all start correctly, Version 24.4 Build 1059

self-inflicted; two years ago I implemented .acme.sh to get SSL certs for Filr; that required socat tools, which in turn required the two libraries.  As I didn't want to risk adding a repository to the Filr server that might foul up upgrades, I manually downloaded the 3 rpm's from a SUSE repo and installed them individually.  That of course has now fouled up the upgrade.

easily fixed of course with zypper rm

filr:~ # zypper rm socat
Reading installed packages...
Resolving package dependencies...

The following package is going to be REMOVED:
  socat

1 package to remove.

Package install size change:
| 0 B required by to be installed packages
-588.1 KiB | - 588.1 KiB released by to be removed packages

Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
(1/1) Removing: socat-1.7.2.4-3.1.x86_64 .........................................................................[done]

filr:~ # zypper rm libncurses5
Reading installed packages...
Resolving package dependencies...

The following 2 packages are going to be REMOVED:
  libncurses5 libreadline6

2 packages to remove.

Package install size change:
| 0 B required by to be installed packages
-1.3 MiB | - 1.3 MiB released by to be removed packages

Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
(1/2) Removing: libreadline6-6.3-83.33.1.x86_64 ..................................................................[done]
(2/2) Removing: libncurses5-5.9-78.1.x86_64 ......................................................................[done]

I almost thought something like that when I saw the modules. I also have problems in the field and with my own installation because I have a backup agent from a backup manufacturer in the applaince to have a database-compliant snapshot. However, I always have the acme console separately in a docker and then push the certificates in via script.

Why won't a VMware snapshot be sufficient?

Unfortunately, the topic cannot be explained in one or two sentences. Perhaps the following can help: In this all-in-one config there is a Postgres, snapper snapshots take place in the system. Depending on the state of the VM, a VMware snapshot can represent a consistent backup that makes it possible to restore the system to the point in time at which the snapshot was created.

It becomes even more interesting if the VMware system is also backed up with a VMware-compliant backup tool such as OT Dataprotector via the VMware API. Here too, the backup takes place via snapshots. If there is an unconsolidated snapshot of the machine in the system that has been executed manually, the “normal” backup will see the snapshot and, depending on how the backup has been configured, the backup snapshot will fail or it will first be consolidated and then a new backup will be executed. The manual snapshot is then lost or the metadata of the backup is missing information for the CBT. If Postgres is active, the VMware snapshot can have an inconsistent backup of the database in the snap, regardless of whether it was performed manually or by backup. To get a database compliant backup, the database itself must be dumped or secured via the backup API of the database. These were just a few targets for Theme Backup. My job in IT forensics and IT emergency management is to know exactly such things, which is unfortunately a very complex topic when it comes to consistent backup and metadata. Actually, what is needed at this point is a lecture like the ones I have given on the subject at universities.
George

my initial solution for SSL renewal without adding any modules is to migrate my domain DNS hosting from Network Solutions to CloudFlare; this gives me API access for acme.sh domain verification, no longer any need for direct communication which eliminates several headaches including no need for socat-tools and will also make it easier to docker-ize the process and/or have one vm get certs for all the servers and push them out via scp. 

I've been meaning to do this for quite awhile, but I kept making it Tomorrow-Dave's task; at last this problem inspired Tommorow-Dave to show up a day early and get it done.