[devinfo] SME 9.2 status

Discussion:

Jean-Philippe PIALASSE

2017-04-06 00:11:27 UTC

Hi all,

as CentOs had planned to release 6.9 packages sooner than they would
usually do ( their usual agenda is 8 weeks), we decided to postpone the
release of SME 9.2 to include the new upstream packages.

They have just synced to our mirror, and they are now in
smeupdates-testing for evaluation.

I have just rebuild initscript against the last available upstream
version with our patches. I will move it also to smeupdates-testing in a
few hours.

If you have some test machine you could do a yum update
--enablerepo=smeupdates-testing and give some feedback or open a bug if
you find anything suspicious. This will help us in releasing SME 9.2 soon.

When we are confident all packages are working fine together, last step
will be to build a last release candidate (SME 9.2.rc2) and test it for
upgrading and installing before releasing the final iso.

Jean-Philippe

_______________________________________________
Server Development Discussion
To unsubscribe, e-mail devinfo-***@lists.contribs.org
Searchable archive at https://lists.contribs.org/mailman/public/devinfo/

Terry Fage

2017-04-06 01:41:21 UTC

Permalink

Post by Jean-Philippe PIALASSE
When we are confident all packages are working fine together, last step
will be to build a last release candidate (SME 9.2.rc2) and test it for
upgrading and installing before releasing the final iso.

Don't you just love it when what you have said a week ago will happen
actually does :-)

Confident, will have some answers in a couple of hours, just watching a
couple of the devils spawn just at the minute :-)

TerryF

_______________________________________________
Server Development Discussion
To unsubscribe, e-mail devinfo-***@lists.contribs.org
Searchable archive at https://lists.contribs.org/mailman/public/devinfo/

Terry Fage

2017-04-06 07:52:12 UTC

Permalink

Post by Jean-Philippe PIALASSE
Hi all,
as CentOs had planned to release 6.9 packages sooner than they would
usually do ( their usual agenda is 8 weeks), we decided to postpone the
release of SME 9.2 to include the new upstream packages.
They have just synced to our mirror, and they are now in
smeupdates-testing for evaluation.

a yum update --enablerepo=smeupdates-testing is only pulling in our
stuff no upstream updates as yet, still syncing?
_______________________________________________
Server Development Discussion
To unsubscribe, e-mail devinfo-***@lists.contribs.org
Searchable archive at https://lists.contribs.org/mailman/public/devinfo/

Terry Fage

2017-04-06 07:54:57 UTC

Permalink

Post by Terry Fage

a yum update --enablerepo=smeupdates-testing is only pulling in our
stuff no upstream updates as yet, still syncing?

never mind, chagrin, I am a silly boy....
_______________________________________________
Server Development Discussion
To unsubscribe, e-mail devinfo-***@lists.contribs.org
Searchable archive at https://lists.contribs.org/mailman/public/devinfo/

Terry Fage

2017-04-06 09:03:22 UTC

Permalink

SME9.1 x64 clean install updated 6 Apr - 344mb of updates

SME9.2RC1 x64 clean install updated 6 Apr -192mb of updates

Updated initscripts

On initial looks, all seems to be good..
_______________________________________________
Server Development Discussion
To unsubscribe, e-mail devinfo-***@lists.contribs.org
Searchable archive at https://lists.contribs.org/mailman/public/devinfo/

Hsing-Foo Wang

2017-04-07 04:39:37 UTC

Permalink

I am testing updating a production server and use yumcheck
(https://wiki.contribs.org/Update_contribs#script_2)

I had to exclude the smeextras repo for the semextras repo contains some
very old versions of a great deal of packages (dating back to 2011)

Several repo's failed the yumcheck. I know we are looking at a clean SME
Serevr testing without any contribs, that works ok. But for updating a
production server yumcheck clearly shows that there are some issues with
several contribs when trying to update to 6.9 level.

Question is how to proceed?

a. Notify contrib maintainers to update ASAP?

b. Simply ignore, 'It is your problem that you have installed contribs' ?

c. Use yumcheck as an early warning system and report on devinfo?

d. Better protect and update (QC) repo's listed on the wiki (see Sogo
change, DAG etc.)

Contribs and howto's are an essential part of the user experience of SME
Server, so I think it is well worth the discussion.

The mic is open...

--------

Repo: centos-sclo-rh:

Resolving Dependencies
--> Running transaction check
---> Package rh-java-common-runtime.x86_64 0:1.1-46.el6 will be updated
---> Package rh-java-common-runtime.x86_64 0:1.1-47.el6 will be an update
---> Package rh-python34-python.x86_64 0:3.4.2-9.el6 will be updated
---> Package rh-python34-python.x86_64 0:3.4.2-14.el6 will be an update
---> Package rh-python34-python-libs.x86_64 0:3.4.2-9.el6 will be updated
---> Package rh-python34-python-libs.x86_64 0:3.4.2-14.el6 will be an update
---> Package v8314-runtime.x86_64 0:2.0-11.el6 will be updated
---> Package v8314-runtime.x86_64 0:2.1-1.el6 will be an update
---> Package v8314-v8.x86_64 1:3.14.5.10-8.el6 will be updated
--> Processing Dependency: v8314-v8 = 1:3.14.5.10-8.el6 for package:
1:v8314-v8-devel-3.14.5.10-8.el6.x86_64
---> Package v8314-v8.x86_64 1:3.14.5.10-9.el6 will be an update
--> Finished Dependency Resolution
Error: Package: 1:v8314-v8-devel-3.14.5.10-8.el6.x86_64 (@centos-sclo-rh)
Requires: v8314-v8 = 1:3.14.5.10-8.el6
Removing: 1:v8314-v8-3.14.5.10-8.el6.x86_64 (@centos-sclo-rh)
v8314-v8 = 1:3.14.5.10-8.el6
Updated By: 1:v8314-v8-3.14.5.10-9.el6.x86_64 (centos-sclo-rh)
v8314-v8 = 1:3.14.5.10-9.el6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Repo: epel:

Resolving Dependencies
--> Running transaction check
---> Package GraphicsMagick.x86_64 0:1.3.25-1.el6 will be updated
---> Package GraphicsMagick.x86_64 0:1.3.25-6.el6 will be an update
---> Package asterisk-sounds-core-en-ulaw.noarch 0:1.4.24-1_centos6 will
be updated
---> Package asterisk-sounds-core-en-ulaw.noarch 0:1.4.25-1.el6 will be
an update
--> Processing Dependency: asterisk-sounds-core-en = 1.4.25-1.el6 for
package: asterisk-sounds-core-en-ulaw-1.4.25-1.el6.noarch
--> Processing Dependency: asterisk >= 1.4.0 for package:
asterisk-sounds-core-en-ulaw-1.4.25-1.el6.noarch
---> Package fail2ban.noarch 0:0.9.3-1.el6.1 will be updated
---> Package fail2ban.noarch 0:0.9.6-1.el6.1 will be an update
---> Package gnustep-make.x86_64 0:2.6.2-1.el6 will be updated
---> Package gnustep-make.x86_64 0:2.6.8-1.el6 will be an update
--> Processing Dependency: gnustep-filesystem(x86-64) = 2.6.8-1.el6 for
package: gnustep-make-2.6.8-1.el6.x86_64
---> Package iftop.x86_64 0:1.0-0.7.pre4.el6 will be updated
---> Package iftop.x86_64 0:1.0-0.12.pre4.el6 will be an update
---> Package iksemel.x86_64 0:1.4-1_centos6 will be updated
---> Package iksemel.x86_64 0:1.4-2.el6 will be an update
---> Package jansson.x86_64 0:2.5-1_centos6 will be updated
---> Package jansson.x86_64 0:2.9-1.el6 will be an update
---> Package lcms2.x86_64 0:2.7-3.el6 will be updated
---> Package lcms2.x86_64 0:2.8-2.el6 will be an update
---> Package libsrtp.x86_64 0:1.4.4-4.20101004cvs.el6 will be updated
--> Processing Dependency: libsrtp.so.0()(64bit) for package:
asterisk-core-13.3.2-1_centos6.x86_64
---> Package libsrtp.x86_64 0:1.5.4-3.el6 will be an update
---> Package openvpn.x86_64 0:2.3.11-1.el6 will be updated
---> Package openvpn.x86_64 0:2.3.14-1.el6 will be an update
---> Package pjproject.x86_64 0:2.3-0.digium3.1_centos6 will be updated
--> Processing Dependency: libg7221codec.so.2()(64bit) for package:
asterisk-core-13.3.2-1_centos6.x86_64
--> Processing Dependency: libilbccodec.so.2()(64bit) for package:
asterisk-core-13.3.2-1_centos6.x86_64
---> Package pjproject.x86_64 0:2.3-7.el6 will be an update
--> Finished Dependency Resolution
Error: Package: asterisk-core-13.3.2-1_centos6.x86_64 (@asterisk-13)
Requires: libsrtp.so.0()(64bit)
Removing: libsrtp-1.4.4-4.20101004cvs.el6.x86_64
(@asterisk-current)
libsrtp.so.0()(64bit)
Updated By: libsrtp-1.5.4-3.el6.x86_64 (epel)
Not found
Error: Package: asterisk-core-13.3.2-1_centos6.x86_64 (@asterisk-13)
Requires: libg7221codec.so.2()(64bit)
Removing: pjproject-2.3-0.digium3.1_centos6.x86_64
(@asterisk-current)
libg7221codec.so.2()(64bit)
Updated By: pjproject-2.3-7.el6.x86_64 (epel)
Not found
Error: Package: asterisk-sounds-core-en-ulaw-1.4.25-1.el6.noarch (epel)
Requires: asterisk-sounds-core-en = 1.4.25-1.el6
Error: Package: gnustep-make-2.6.8-1.el6.x86_64 (epel)
Requires: gnustep-filesystem(x86-64) = 2.6.8-1.el6
Error: Package: asterisk-sounds-core-en-ulaw-1.4.25-1.el6.noarch (epel)
Requires: asterisk >= 1.4.0
Error: Package: asterisk-core-13.3.2-1_centos6.x86_64 (@asterisk-13)
Requires: libilbccodec.so.2()(64bit)
Removing: pjproject-2.3-0.digium3.1_centos6.x86_64
(@asterisk-current)
libilbccodec.so.2()(64bit)
Updated By: pjproject-2.3-7.el6.x86_64 (epel)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Repo: nodejs:

Resolving Dependencies
--> Running transaction check
---> Package nodejs.x86_64 1:4.7.0-1nodesource.el6 will be updated
--> Processing Dependency: nodejs(x86-64) = 1:4.7.0-1nodesource.el6 for
package: 1:nodejs-devel-4.7.0-1nodesource.el6.x86_64
---> Package nodejs.x86_64 1:4.8.2-1nodesource.el6 will be an update
--> Finished Dependency Resolution
Error: Package: 1:nodejs-devel-4.7.0-1nodesource.el6.x86_64 (@nodejs)
Requires: nodejs(x86-64) = 1:4.7.0-1nodesource.el6
Removing: 1:nodejs-4.7.0-1nodesource.el6.x86_64 (@nodejs)
nodejs(x86-64) = 1:4.7.0-1nodesource.el6
Updated By: 1:nodejs-4.8.2-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.8.2-1nodesource.el6
Available: nodejs-4.2.6-2nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.2.6-2nodesource.el6
Available: nodejs-4.3.0-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.3.0-1nodesource.el6
Available: nodejs-4.3.1-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.3.1-1nodesource.el6
Available: nodejs-4.3.2-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.3.2-1nodesource.el6
Available: nodejs-4.4.0-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.0-1nodesource.el6
Available: nodejs-4.4.1-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.1-1nodesource.el6
Available: nodejs-4.4.2-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.2-1nodesource.el6
Available: nodejs-4.4.3-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.3-1nodesource.el6
Available: nodejs-4.4.4-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.4-1nodesource.el6
Available: nodejs-4.4.5-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.5-1nodesource.el6
Available: nodejs-4.4.6-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.6-1nodesource.el6
Available: 1:nodejs-4.4.7-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.4.7-1nodesource.el6
Available: 1:nodejs-4.4.7-2nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.4.7-2nodesource.el6
Available: 1:nodejs-4.5.0-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.5.0-1nodesource.el6
Available: 1:nodejs-4.6.0-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.6.0-1nodesource.el6
Available: 1:nodejs-4.6.1-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.6.1-1nodesource.el6
Available: 1:nodejs-4.6.2-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.6.2-1nodesource.el6
Available: 1:nodejs-4.7.1-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.7.1-1nodesource.el6
Available: 1:nodejs-4.7.2-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.7.2-1nodesource.el6
Available: 1:nodejs-4.7.3-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.7.3-1nodesource.el6
Available: 1:nodejs-4.8.0-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.8.0-1nodesource.el6
Available: 1:nodejs-4.8.1-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.8.1-1nodesource.el6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Repo: smecontribs:

Resolving Dependencies
--> Running transaction check
---> Package iksemel.x86_64 0:1.4-1_centos6 will be updated
---> Package iksemel.x86_64 0:1.4-2.el6 will be an update
---> Package openvpn.x86_64 0:2.3.11-1.el6 will be updated
---> Package openvpn.x86_64 0:2.4.1-3.el6 will be an update
---> Package php-php-gettext.noarch 0:1.0.11-12.el6 will be updated
---> Package php-php-gettext.noarch 0:1.0.12-1.el6 will be an update
---> Package php-tcpdf.noarch 0:6.2.11-1.el6 will be updated
---> Package php-tcpdf.noarch 0:6.2.13-1.el6 will be an update
--> Processing Dependency: php-composer(fedora/autoloader) for package:
php-tcpdf-6.2.13-1.el6.noarch
---> Package php-tcpdf-dejavu-sans-fonts.noarch 0:6.2.11-1.el6 will be
updated
---> Package php-tcpdf-dejavu-sans-fonts.noarch 0:6.2.13-1.el6 will be
an update
---> Package phpMyAdmin.noarch 0:4.0.10.16-1.el6 will be updated
---> Package phpMyAdmin.noarch 0:4.0.10.19-1.el6 will be an update
---> Package smeserver-freepbx.x86_64 0:13-2.el6.sme will be updated
---> Package smeserver-freepbx.x86_64 0:13-13.el6.sme will be an update
--> Processing Dependency: mpg123 for package:
smeserver-freepbx-13-13.el6.sme.x86_64
--> Processing Dependency: ffmpeg for package:
smeserver-freepbx-13-13.el6.sme.x86_64
---> Package smeserver-openvpn-bridge.noarch 0:2.1-6.el6.sme will be updated
---> Package smeserver-openvpn-bridge.noarch 0:2.1-7.el6.sme will be an
update
--> Finished Dependency Resolution
Error: Package: smeserver-freepbx-13-13.el6.sme.x86_64 (smecontribs)
Requires: ffmpeg
Error: Package: php-tcpdf-6.2.13-1.el6.noarch (smecontribs)
Requires: php-composer(fedora/autoloader)
Error: Package: smeserver-freepbx-13-13.el6.sme.x86_64 (smecontribs)
Requires: mpg123
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Post by Terry Fage
SME9.1 x64 clean install updated 6 Apr - 344mb of updates
SME9.2RC1 x64 clean install updated 6 Apr -192mb of updates
Updated initscripts
On initial looks, all seems to be good..
_______________________________________________
Server Development Discussion
Searchable archive at https://lists.contribs.org/mailman/public/devinfo/

_______________________________________________
Server Development Discussion
To unsubscribe, e-mail devinfo-***@lists.contribs.org
Searchable archive at https://lists.contribs.org/mailman/public/devinfo/

michelandre

2017-04-07 05:24:55 UTC

Permalink

Hi HF,

Last week I tried the first script on a 9.1/64 to see what it will do.

End up with a lot of updates, lot of errors, and a Centos kernel!!!

Finally for the PHP SCL, I tried:
# yum update -y smeserver-php-scl php54* php55* php56*
--enablerepo=smecontribs,remi,epel

And it looks good with no errors.

I hesitate to try it on my real server...

SignatureThunderbird_2016-02-15_21h57 Michel-André

*************************************************************************

Post by Hsing-Foo Wang
I am testing updating a production server and use yumcheck
(https://wiki.contribs.org/Update_contribs#script_2)
I had to exclude the smeextras repo for the semextras repo contains
some very old versions of a great deal of packages (dating back to 2011)
Several repo's failed the yumcheck. I know we are looking at a clean
SME Serevr testing without any contribs, that works ok. But for
updating a production server yumcheck clearly shows that there are
some issues with several contribs when trying to update to 6.9 level.
Question is how to proceed?
a. Notify contrib maintainers to update ASAP?
b. Simply ignore, 'It is your problem that you have installed contribs' ?
c. Use yumcheck as an early warning system and report on devinfo?
d. Better protect and update (QC) repo's listed on the wiki (see Sogo
change, DAG etc.)
Contribs and howto's are an essential part of the user experience of
SME Server, so I think it is well worth the discussion.
The mic is open...
--------
Resolving Dependencies
--> Running transaction check
---> Package rh-java-common-runtime.x86_64 0:1.1-46.el6 will be updated
---> Package rh-java-common-runtime.x86_64 0:1.1-47.el6 will be an update
---> Package rh-python34-python.x86_64 0:3.4.2-9.el6 will be updated
---> Package rh-python34-python.x86_64 0:3.4.2-14.el6 will be an update
---> Package rh-python34-python-libs.x86_64 0:3.4.2-9.el6 will be updated
---> Package rh-python34-python-libs.x86_64 0:3.4.2-14.el6 will be an update
---> Package v8314-runtime.x86_64 0:2.0-11.el6 will be updated
---> Package v8314-runtime.x86_64 0:2.1-1.el6 will be an update
---> Package v8314-v8.x86_64 1:3.14.5.10-8.el6 will be updated
1:v8314-v8-devel-3.14.5.10-8.el6.x86_64
---> Package v8314-v8.x86_64 1:3.14.5.10-9.el6 will be an update
--> Finished Dependency Resolution
Requires: v8314-v8 = 1:3.14.5.10-8.el6
v8314-v8 = 1:3.14.5.10-8.el6
Updated By: 1:v8314-v8-3.14.5.10-9.el6.x86_64 (centos-sclo-rh)
v8314-v8 = 1:3.14.5.10-9.el6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Resolving Dependencies
--> Running transaction check
---> Package GraphicsMagick.x86_64 0:1.3.25-1.el6 will be updated
---> Package GraphicsMagick.x86_64 0:1.3.25-6.el6 will be an update
---> Package asterisk-sounds-core-en-ulaw.noarch 0:1.4.24-1_centos6
will be updated
---> Package asterisk-sounds-core-en-ulaw.noarch 0:1.4.25-1.el6 will
be an update
--> Processing Dependency: asterisk-sounds-core-en = 1.4.25-1.el6 for
package: asterisk-sounds-core-en-ulaw-1.4.25-1.el6.noarch
asterisk-sounds-core-en-ulaw-1.4.25-1.el6.noarch
---> Package fail2ban.noarch 0:0.9.3-1.el6.1 will be updated
---> Package fail2ban.noarch 0:0.9.6-1.el6.1 will be an update
---> Package gnustep-make.x86_64 0:2.6.2-1.el6 will be updated
---> Package gnustep-make.x86_64 0:2.6.8-1.el6 will be an update
--> Processing Dependency: gnustep-filesystem(x86-64) = 2.6.8-1.el6
for package: gnustep-make-2.6.8-1.el6.x86_64
---> Package iftop.x86_64 0:1.0-0.7.pre4.el6 will be updated
---> Package iftop.x86_64 0:1.0-0.12.pre4.el6 will be an update
---> Package iksemel.x86_64 0:1.4-1_centos6 will be updated
---> Package iksemel.x86_64 0:1.4-2.el6 will be an update
---> Package jansson.x86_64 0:2.5-1_centos6 will be updated
---> Package jansson.x86_64 0:2.9-1.el6 will be an update
---> Package lcms2.x86_64 0:2.7-3.el6 will be updated
---> Package lcms2.x86_64 0:2.8-2.el6 will be an update
---> Package libsrtp.x86_64 0:1.4.4-4.20101004cvs.el6 will be updated
asterisk-core-13.3.2-1_centos6.x86_64
---> Package libsrtp.x86_64 0:1.5.4-3.el6 will be an update
---> Package openvpn.x86_64 0:2.3.11-1.el6 will be updated
---> Package openvpn.x86_64 0:2.3.14-1.el6 will be an update
---> Package pjproject.x86_64 0:2.3-0.digium3.1_centos6 will be updated
asterisk-core-13.3.2-1_centos6.x86_64
asterisk-core-13.3.2-1_centos6.x86_64
---> Package pjproject.x86_64 0:2.3-7.el6 will be an update
--> Finished Dependency Resolution
Requires: libsrtp.so.0()(64bit)
Removing: libsrtp-1.4.4-4.20101004cvs.el6.x86_64
libsrtp.so.0()(64bit)
Updated By: libsrtp-1.5.4-3.el6.x86_64 (epel)
Not found
Requires: libg7221codec.so.2()(64bit)
Removing: pjproject-2.3-0.digium3.1_centos6.x86_64
libg7221codec.so.2()(64bit)
Updated By: pjproject-2.3-7.el6.x86_64 (epel)
Not found
Error: Package: asterisk-sounds-core-en-ulaw-1.4.25-1.el6.noarch (epel)
Requires: asterisk-sounds-core-en = 1.4.25-1.el6
Error: Package: gnustep-make-2.6.8-1.el6.x86_64 (epel)
Requires: gnustep-filesystem(x86-64) = 2.6.8-1.el6
Error: Package: asterisk-sounds-core-en-ulaw-1.4.25-1.el6.noarch (epel)
Requires: asterisk >= 1.4.0
Requires: libilbccodec.so.2()(64bit)
Removing: pjproject-2.3-0.digium3.1_centos6.x86_64
libilbccodec.so.2()(64bit)
Updated By: pjproject-2.3-7.el6.x86_64 (epel)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Resolving Dependencies
--> Running transaction check
---> Package nodejs.x86_64 1:4.7.0-1nodesource.el6 will be updated
--> Processing Dependency: nodejs(x86-64) = 1:4.7.0-1nodesource.el6
for package: 1:nodejs-devel-4.7.0-1nodesource.el6.x86_64
---> Package nodejs.x86_64 1:4.8.2-1nodesource.el6 will be an update
--> Finished Dependency Resolution
Requires: nodejs(x86-64) = 1:4.7.0-1nodesource.el6
nodejs(x86-64) = 1:4.7.0-1nodesource.el6
Updated By: 1:nodejs-4.8.2-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.8.2-1nodesource.el6
Available: nodejs-4.2.6-2nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.2.6-2nodesource.el6
Available: nodejs-4.3.0-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.3.0-1nodesource.el6
Available: nodejs-4.3.1-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.3.1-1nodesource.el6
Available: nodejs-4.3.2-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.3.2-1nodesource.el6
Available: nodejs-4.4.0-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.0-1nodesource.el6
Available: nodejs-4.4.1-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.1-1nodesource.el6
Available: nodejs-4.4.2-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.2-1nodesource.el6
Available: nodejs-4.4.3-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.3-1nodesource.el6
Available: nodejs-4.4.4-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.4-1nodesource.el6
Available: nodejs-4.4.5-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.5-1nodesource.el6
Available: nodejs-4.4.6-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 4.4.6-1nodesource.el6
Available: 1:nodejs-4.4.7-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.4.7-1nodesource.el6
Available: 1:nodejs-4.4.7-2nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.4.7-2nodesource.el6
Available: 1:nodejs-4.5.0-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.5.0-1nodesource.el6
Available: 1:nodejs-4.6.0-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.6.0-1nodesource.el6
Available: 1:nodejs-4.6.1-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.6.1-1nodesource.el6
Available: 1:nodejs-4.6.2-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.6.2-1nodesource.el6
Available: 1:nodejs-4.7.1-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.7.1-1nodesource.el6
Available: 1:nodejs-4.7.2-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.7.2-1nodesource.el6
Available: 1:nodejs-4.7.3-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.7.3-1nodesource.el6
Available: 1:nodejs-4.8.0-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.8.0-1nodesource.el6
Available: 1:nodejs-4.8.1-1nodesource.el6.x86_64 (nodejs)
nodejs(x86-64) = 1:4.8.1-1nodesource.el6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Resolving Dependencies
--> Running transaction check
---> Package iksemel.x86_64 0:1.4-1_centos6 will be updated
---> Package iksemel.x86_64 0:1.4-2.el6 will be an update
---> Package openvpn.x86_64 0:2.3.11-1.el6 will be updated
---> Package openvpn.x86_64 0:2.4.1-3.el6 will be an update
---> Package php-php-gettext.noarch 0:1.0.11-12.el6 will be updated
---> Package php-php-gettext.noarch 0:1.0.12-1.el6 will be an update
---> Package php-tcpdf.noarch 0:6.2.11-1.el6 will be updated
---> Package php-tcpdf.noarch 0:6.2.13-1.el6 will be an update
--> Processing Dependency: php-composer(fedora/autoloader) for
package: php-tcpdf-6.2.13-1.el6.noarch
---> Package php-tcpdf-dejavu-sans-fonts.noarch 0:6.2.11-1.el6 will be
updated
---> Package php-tcpdf-dejavu-sans-fonts.noarch 0:6.2.13-1.el6 will be
an update
---> Package phpMyAdmin.noarch 0:4.0.10.16-1.el6 will be updated
---> Package phpMyAdmin.noarch 0:4.0.10.19-1.el6 will be an update
---> Package smeserver-freepbx.x86_64 0:13-2.el6.sme will be updated
---> Package smeserver-freepbx.x86_64 0:13-13.el6.sme will be an update
smeserver-freepbx-13-13.el6.sme.x86_64
smeserver-freepbx-13-13.el6.sme.x86_64
---> Package smeserver-openvpn-bridge.noarch 0:2.1-6.el6.sme will be updated
---> Package smeserver-openvpn-bridge.noarch 0:2.1-7.el6.sme will be
an update
--> Finished Dependency Resolution
Error: Package: smeserver-freepbx-13-13.el6.sme.x86_64 (smecontribs)
Requires: ffmpeg
Error: Package: php-tcpdf-6.2.13-1.el6.noarch (smecontribs)
Requires: php-composer(fedora/autoloader)
Error: Package: smeserver-freepbx-13-13.el6.sme.x86_64 (smecontribs)
Requires: mpg123
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

_______________________________________________
Server Development Discussion
Searchable archive at https://lists.contribs.org/mailman/public/devinfo/

---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus