Clean server apache2 install problem


I installed a ‘few’ tumbleweed servers, all default out of the box. When I use

zypper in apache2

I get:

Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: apache2-2.4.27-1.3.x86_64 requires, but this requirement cannot be provided
  uninstallable providers: liblua5_3-5-5.3.4-1.1.x86_64[repo-oss]
 Solution 1: replacement of liblua5_3-5.3.3-2.2.x86_64 with liblua5_3-5-5.3.4-1.1.x86_64
 Solution 2: do not install apache2-2.4.27-1.3.x86_64
 Solution 3: break apache2-2.4.27-1.3.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c] (c): c

Notice there is no default answer so I can’t use the -n option with zypper.
I figured it was some repo/package error that would get fixed pretty fast. Now a couple of weeks later I found some time to pick this up again, and the problem still remains.
I could go for solution 1 and everything seems to work. But I have a large amount of servers which all need apache2. And without the use of -n I don’t think I can script this. Certainly not with Ansible, which is preferred.

Any idea if this needs fixing in the package or to I need to get really creative to automate this? It doesn’t seem OK on a clean box to be asked this question.

I would suggest updating your install iso image or make sure you zypper dup first, then install apache2, but lua does need to be updated…

Repository     : Main Repository (OSS)                           
Name           : lua53                                           
Version        : 5.3.4-1.1

zypper in -D apache2
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 5 NEW packages are going to be installed:
  apache2 apache2-mod_dnssd apache2-prefork apache2-utils system-user-wwwrun

Hi, thanks for your reply.
I’ll try this.

Yet, Tumbleweed is a rolling distro. I didn’t think zypper dup would be needer, ever?

For Tumbleweed, zypper dup always needs to be run, not ‘up’ even numerous times (snapshot updates) in a week for the latest packages… if your running btrfs, make sure you configure snapshots and ensure the btrfs maintenance service is running to keep the disk space healthy…

The release is currently at;

cat /etc/os-release |grep VERSION_ID

Ok thanks, I did not know this.

It can also break since it uses bleeding edge packages, you might want to reconsider it’s use in your environment and switch to openSUSE Leap 42.3?

Since I now found some documentation, if using

zypper dup

on Tumbleweed, make sure you use

zypper dup --no-allow-vendor-change 

for less possible problems.

I found that a distro update on a LAMP server gives more problems when going from an older version to the newer than a rolling distro like TW. So I have been using TW for ages now without any problems ever as long as there is no GUI. When I need a GUI it’s the latest OpenSUSE version I install.

This is the first time I ran in to a problem on TW when just using it for LAMP.

The latter is already the default, so no longer needed. A ‘zypper dup’ is all.

Re, apache I’d recommend to install yast2-http-server as well to configure the webserver through YaST, or install the LAMP-pattern.

Not trying to argue, I did zypper dup and got lots of vendor changes, hence looking in to documentation.
Could there be another reason for these vendor changes? It did ask permission before changing.

Use some verbosity eg -vvvv if your getting vendor changes then you have non-standard repositories present, what is the output from;

zypper lr -d

For Tumbleweed, there is not much need for additional repositories, since everything comes from development repositories. If your only running a LAMP setup then you should only need the oss repository. If something you need is not in Tumbleweed, then you should ask the maintainer to push to Tumbleweed.