>But my advice is use default repo (scientific linux) and epel or
>repoforge no more.
 
Agree... Indeed I don't have many repositories. The problem is that why Octave 
dependencies are not available in epel (at least for me).


Regards,
Mahmood



________________________________
 From: Edgar Vargas <cybernaut...@esdebian.org>
To: Mahmood Naderan <nt_mahm...@yahoo.com> 
Cc: sl-users <scientific-linux-users@fnal.gov> 
Sent: Wednesday, July 3, 2013 5:13 PM
Subject: Re: Problem installing Octave
 

2013/7/2, Mahmood Naderan <nt_mahm...@yahoo.com>:
> Dear all
> I want to install GNU Octave from repository on a SL6.3 machine. However,
> there is a dependency problem and I couldn't figure out the problem.
>
> ....
>
> --> Finished Dependency Resolution
> Error: Package: 6:octave-3.4.3-1.el6.x86_64 (epel)
>            Requires: libumfpack.so.5()(64bit)
> Error: Package: 6:octave-3.4.3-1.el6.x86_64 (epel)
>            Requires: libcxsparse.so.2()(64bit)
> Error: Package: 6:octave-3.4.3-1.el6.x86_64 (epel)
>            Requires: libcamd.so.2()(64bit)
> Error: Package: 6:octave-3.4.3-1.el6.x86_64 (epel)
>            Requires: libamd.so.2()(64bit)
> Error: Package: 6:octave-3.4.3-1.el6.x86_64 (epel)
>            Requires: libcholmod.so.1()(64bit)
> Error: Package: 6:octave-3.4.3-1.el6.x86_64 (epel)
>            Requires: libccolamd.so.2()(64bit)
> Error: Package: 6:octave-3.4.3-1.el6.x86_64 (epel)
>            Requires: libcolamd.so.2()(64bit)
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
>
>
> I don't want to use the '--skip-broken' since there was a similar option
> with apt (Ubuntu) and I found that this option will make future problems
> with packages.

My friend, is not a  good to use many respos, epel is sufficient to
octave, think what is the purpose? epel and default repo is suffcient,
maybe repoforge, but my advice is use the default repo, if you need
another, for example desktop then repoforge and epel.

when you are installing software you can use
--disablerepo=anotherrepo, the no problem.

But my advice is use default repo (scientific linux) and epel or
repoforge no more.

>
>
> Regards,
> Mahmood
>

Reply via email to