Task #3066

dependency issues with nethserver-wordpress

Added by stephane de Labrusse almost 5 years ago. Updated almost 5 years ago.

Status:CLOSEDStart date:
Priority:NormalDue date:
Assignee:Davide Principi% Done:

100%

Category:-
Target version:nf-closed

Description

Hi All

With the release of nethserver-wordpress in nethforge, I have seen that dependencies are not imported in nethforge and we need to manually enable epel if we want to install that contribs.

It is not really important for me if we document that epel is a mandatory (less works if we want to follow updates) but that need to be decided. and written in the documentation ----> http://dev.nethserver.org/projects/nethforge/wiki/Nethserver-wordpress

for now

yum install nethserver-wordpress --enablerepo=nethforge --disablerepo=epel ----> Error: Package: nethserver-wordpress-1.0.0-2.ns6.noarch (nethforge) Requires: wordpress

but if I enable epel

yum install nethserver-wordpress --enablerepo=nethforge,epel

Installing:
nethserver-wordpress noarch 1.0.0-2.ns6 nethforge 17 k
Installing for dependencies:
enchant x86_64 1:1.5.0-4.el6 centos-base 49 k
hunspell x86_64 1.2.8-16.el6 centos-base 177 k
php-IDNA_Convert noarch 0.8.0-1.el6 epel 35 k
php-PHPMailer noarch 5.2.2-1.el6 epel 474 k
php-enchant x86_64 5.3.3-27.el6_5.2 centos-updates 30 k
php-getid3 noarch 1:1.9.7-1.el6 epel 420 k
php-simplepie noarch 1.3.1-3.el6 epel 465 k
wordpress noarch 4.1-1.el6 epel 4

Else I wonder if you need to manually add a contrib to the package manager because I can't find nethserver-wordpress when I use it ??

History

#1 Updated by Filippo Carletti almost 5 years ago

stephane de Labrusse wrote:

Else I wonder if you need to manually add a contrib to the package manager because I can't find nethserver-wordpress when I use it ??

I think that we need to streamline the whole NethForge process.
Here we have two problems:
1. pull external dependencies or ask the user to enable external repos?
2. how to modify nethforge group when new packages are released

I'd pull deps to be sure we have a stable contrib. Having a controlled env is easier to maintain.

Note: is the forum a better place to discuss these kind of problems?

#2 Updated by Davide Principi almost 5 years ago

  • Tracker changed from Feature to Task
  • Assignee set to Davide Principi

I'm sorry, my mistake: I'll fix the repo ASAP, and add the proper YUM group settings.

By now we've to import any external dependency into nethserver-nethforge repository. I'd prefer going on this way: I don't know what will happen if one package is upgraded from upstream, if it breaks something etc... If you see other viable solutions, let's discuss them on community.nethserver.org.

#3 Updated by stephane de Labrusse almost 5 years ago

No problem Davide, we are just human :)

Anyways if someone wants to be bleeding age, he can enable epel, and play his dangerous life, it depends of his temperament, but in fact it could be interesting to have a script which is here to look after other repositories used as dependencies and import automatically updated rpms in a third repository (eg nethforge-dev).

Of course for two Modules, that can be done manually (eg every month looks after updates).

That makes me remember that we should look after nethserver-PhpMyAdmin, sure that updates might be available. I will have a go.

#4 Updated by Davide Principi almost 5 years ago

  • Status changed from NEW to CLOSED
  • % Done changed from 0 to 100

Thank you Stephane! We'd like to set up more automation tools for repository maintenance: let's discuss them in the forum!

For what concerns nethserver-wordpress I just pushed the deps:

In nethserver-nethforge 6.5 and 6.6:
perl-Expect-1.21-3.el6.noarch.rpm
php-getid3-1.9.7-1.el6.noarch.rpm
php-PHPMailer-5.2.2-1.el6.noarch.rpm
php-simplepie-1.3.1-3.el6.noarch.rpm
php-IDNA_Convert-0.8.0-1.el6.noarch.rpm
wordpress-4.1-1.el6.noarch.rpm

Added also nethserver-wordpress to https://github.com/nethesis/comps-nethforge

Ring me if there is still any issue!

#5 Updated by stephane de Labrusse almost 5 years ago

No more issues, just a pop up to say that I can install from the CLI and from the GUI

Also available in: Atom PDF