Topic: [SOLVED] libwebp dependency prevents CentOS 6 update

[Mophilly]

I am trying to apply the latest CentOS 6 updates to an SME 9 installation.

yum update --enablerepo=smecontribs,remi,epel
...
Error: Package: gd-last-2.2.1-2.el6.remi.x86_64 (remi)
           Requires: libwebp.so.5()(64bit)

I do not know what to add or exclude to resolve the libwebp dependency.

Also, I opened a bug report for the contrib, https://bugs.contribs.org/show_bug.cgi?id=9579, just in case this needs to be handled as a bug.

[Stefano]

Never update your server with epel and remi repos enabled

[Mophilly]

OK. Thank you, Stefano.

I tried from the web panel, which did not seem to work, and from the cli using "yum update" without the --enablerepo switch, all before running the command with the three repos.

It this correct?
  yum update --enablerepo=smecontribs

[Stefano]

Yes

[Mophilly]

Thanks, Stephano. I appreciate your help with this.

Sadly, "yum update --enablerepo=smecontribs" did not work. Same error. Do I need to disable the remi and epel repo's before running the update? If yes, then I simply reenable them after?

[Stefano]

If you previously updated your server with those repos enabled, maybe you broke something.
Now I'm not in front of a pc

[Mophilly]

Understood.

Update: I found a note at centos.org that refers to the package the update appears to trip over, e.g. gd-last-2.1.1-2.el6.remi.x86_64.
  https://www.centos.org/forums/viewtopic.php?t=54626
The article suggests that running "yum --disablerepo=\* --enablerepo=base,updates update" to allow centos repos to install properly.

I wonder whether this might succeed:
1. yum disablerepo / enablerepo as above
2. then "yum update"
3. If success, then "yum update --enablerepo=smecontribs"
4. If success, then update or reinstall the php scl package(s) from remi

[guest22]

A normal Koozali SME Server update is performed ONLY with:

yum update

Do NOT enable/disable any repo manually. Check if you have any non stock repo's enabled by default.

[Mophilly]

Thank you, RequestedDeletion.

What happened, which may not be clear from my original post, is this...

0. Several months ago I installed the software collection so I could support ownCloud on this server.
1. Today I ran the update from the server-manager panel. Update did not complete and I was returned to the server-manager top page. I didn't expect that, so...
2. I ran the update from the server-manager in case I did not click the final button. Again returned to top page.
3. using the cli, i ran "yum clean all" followed by "yum update". error reported.
4. I then tried 'yum update --enablerepo=smecontribs,remi,epel". same error reported.

So that is the path I followed and here I am, for better or worse.

[guest22]

What is the output of 'yum update'

What is the output of 'db yum_repositories show'

[guest22]

3. using the cli, i ran "yum clean all" followed by "yum update". error reported.

That should be 'yum clean all --enablerepo=*', to also clear all the non stock repo's.

[Mophilly]

Thank you, RequestedDeletion, for your assistance.

What is the output of 'yum update'

What is the output of 'db yum_repositories show'

The output of yum update is quite lengthy, as is the list of repo's.
yum repo list: http://pastebin.com/pXePB5sf
yup update output: http://pastebin.com/aMSCPGaL

The pastebin links will be deleted in seven days (18 June 2016) but I can provide them elsewhere if asked.

[Mophilly]

Does this plan look like it will succeed?

0. yum --disablerepo=* --enablerepo=base,updates update
1. yum clean all --enablerepo=*
2. then "yum update"
3. If success, then "yum update --enablerepo=smecontribs"
4. If success, then update or reinstall the php scl package(s) from remi

Critique encouraged.

[guest22]

remi=repository

•    BaseURL=http://rpms.famillecollet.com/enterprise/6/remi/$basearch/
•     EnableGroups=no
•     Exclude=mysql*,php-*
•     GPGCheck=yes
•     GPGKey=http://rpms.famillecollet.com/RPM-GPG-KEY-remi
•     Name=Remi - EL6
•     Visible=yes
•     status=enabled

The remi repository should be disabled.

Code: [Select]

db yum_repositories setprop remi status disabled
signal-event yum-modify
yum update



Why it is enabled by default is another question.

[janet]

Mophilly

Good (& I believe recommended) practice is to always specify a packagename when using the --enablerepo=reponame  switch
The package name would be that which is found in the specified repo.
That way you do not inadvertantly update other packages that SHOULD NOT be updated.
This particularly applies to other external repos
ie any repo OTHER THAN those recommended repos to be enabled by default for sme server & the sme contribs repo
eg
yum update packagename --enablerepo=remi

In some cases you can do a general yum update when specifying the --enablerepo=smecontribs switch, but keep in mind that that will update any & all contribs that you have installed for which there is an update package.
Opinions vary on this, some people here prefer to have all packages including contribs updated in the one go, others (including me) prefer to only update one contrib package at a time.
The reason being that if a single package causes a problem, then it is much easier to identify which package caused the issue (after an update), whereas if you update many contribs at once & then experience problems, it can be difficult (or more difficult) to find the culprit.

eg
yum update smeserver-dansguardian --enablerepo=smecontribs

will only update the smeserver-dansguardian package & any dependencies, if it is already installed.