Hi All,
I am trying to install Anjuta from the KB Singh repos on CentOS 5 without success.
yum install --enablerepo=atrpms,centosplus,rpmforge,kbs-Extras-x86_64,kbs-Misc-x86_64 anjuta-1.2.2-6 Loading "installonlyn" plugin Setting up Install Process Setting up repositories Reading repository metadata in from local files Parsing package install arguments Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package anjuta.x86_64 1:1.2.2-6 set to be updated --> Running transaction check --> Processing Dependency: libvte.so.4()(64bit) for package: anjuta --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Package vte.i386 0:0.14.0-2.el5 set to be updated --> Running transaction check --> Processing Dependency: libvte.so.4()(64bit) for package: anjuta --> Finished Dependency Resolution Error: Missing Dependency: libvte.so.4()(64bit) is needed by package anjuta
It keeps failing on libvte.so.4 which I don't have
/usr/lib64/libvte.so.9 /usr/lib64/libvte.so.9.1.5
has anyone gotten this to work or should I build it from the SRPMS?
James A. Peltier wrote:
err ? I have not actually built anjuta for centos-5 as yet :)
I can do it now, and it should show up on the repo in a few hours.
Karanbir Singh wrote:
I'm attempting to build Anjuta 2.2.2 which is the latest stable using the supplied anjuta.spec file however it has later package requirements in it. Do you think it would be safe to replace the listed requirements with those that come with CentOS 5?
This is my first time packaging an RPM so I apologize if this is elementary.
James A. Peltier wrote:
The answer is ... it depends :D
Sometimes, if you are going to downgrade all the items, you can do that. Other times the software in question really does REQUIRE newer packages to build properly.
Most of the time, if a specific version is NOT required, then an non-versioned require is put in ... ie:
BuildRequires: glibc-devel
However, sometimes you need a specific version, so you would use:
BuildRequires: glibc-devel >= 2.5
(same is true for "Requires:")
SO ... if the person who did the research and wrote the SPEC did it correctly, then no, you can't change it. BUT ... if they did it in correctly and specified a version where one is not really required, then you might be able to change it.
Doesn't really answer you question ... but the only way to tell is to change the version and build it :D
-
James A. Peltier -
Johnny Hughes -
Karanbir Singh