I'm working on a Scientific Linux box and am trying to install Maven using the yum command. Scientific Linux for those of you who do not know is based off of Red Hat Linux Enterprise Edition 6.
I'd prefer to install Maven in a way that lent itself to easy updating, that is why I have shied away from simply going to the Apache Maven site and getting the files I need.
Simply running yum with root privileges was not enough. I used yum search maven which returned "JPackage Utilities", which I tried to install only to get:
Package jpackage-utils-1.7.5-3.12.el6.noarch already installed and latest version
I was assuming that something like creating a new repo file something like /etc/yum.repos.d/maven.repo would do the trick.
I found a site suggesting that I point my maven.repo file to the URL http://www.jpackage.org/jpackage50.repo, however this seems to be a fix for an older version of Linux as it did not solve my problem
As always thanks in advance for any help or suggestions!
The distro agnostic generic repo is what you want. As root, add a couple of the jpackage-generic repos to yum (two snippets below). Then perform a yum update and finally yum install maven2.
cat > /etc/yum.repos.d/jpackage-generic-free.repo << EOF
[jpackage-generic-free]
name=JPackage generic free
baseurl=http://mirrors.dotsrc.org/jpackage/6.0/generic/free/
enabled=1
gpgcheck=1
gpgkey=http://www.jpackage.org/jpackage.asc
EOF
cat > /etc/yum.repos.d/jpackage-generic-devel.repo << EOF
[jpackage-generic-devel]
name=JPackage Generic Developer
baseurl=http://mirrors.dotsrc.org/jpackage/6.0/generic/devel/
enabled=1
gpgcheck=1
gpgkey=http://www.jpackage.org/jpackage.asc
EOF
I had all kinds of conflicts trying to use the JPackage repo with Scientific Linux 6.2, but I had much better luck with dchen's repo from the "Fedora People" unofficial repositories. The repo config I used is:
# Note: Replaced $releasever with 6Server since SL's "6.2" doesn't work
[epel-apache-maven]
name=maven from apache foundation.
baseurl=http://repos.fedorapeople.org/repos/dchen/apache-maven/epel-6Server/$basearch/
enabled=1
skip_if_unavailable=1
gpgcheck=0
[epel-apache-maven-source]
name=maven from apache foundation. - Source
baseurl=http://repos.fedorapeople.org/repos/dchen/apache-maven/epel-6Server/SRPMS
enabled=0
skip_if_unavailable=1
gpgcheck=0
The package itself is called apache-maven and installs maven 3.0.3.
This is more updated way:
curl http://www.jpackage.org/jpackage50.repo > /etc/yum.repos.d/jpackage.repo
yum update
yum install maven2
Thanks Andy for his answer (on Jun 10, 2011). It gave me some hints. However, when I followed it, I got a lot of dependencies issues, including problems like these
ERROR with rpm_check_debug vs depsolve:
rpmlib(FileDigests) is needed by plexus-container-default-1.0-0.a9s1.2.jpp6.noarch
rpmlib(FileDigests) is needed by aspectj-1.5.4-1.jpp6.noarch
rpmlib(FileDigests) is needed by rhino-1.7-1.r2.8.jpp6.noarch
rpmlib(FileDigests) is needed by saxon9-dom-B.9.0.0.8-2.jpp6.noarch
rpmlib(FileDigests) is needed by easymock2-2.5.2-2.jpp6.noarch
rpmlib(FileDigests) is needed by saxon9-B.9.0.0.8-2.jpp6.noarch
rpmlib(FileDigests) is needed by saxon9-xpath-B.9.0.0.8-2.jpp6.noarch
rpmlib(FileDigests) is needed by xmlbeans-2.4.0-3.jpp6.noarch
rpmlib(FileDigests) is needed by jtidy-7.0-0.V04aug2000r7_dev.2.jpp6.noarch
rpmlib(FileDigests) is needed by lucene-2.4.1-5.jpp6.noarch
rpmlib(FileDigests) is needed by aqute-bndlib-0.0.363-1.jpp6.noarch
Finally I realized the JPackage website actually has good and updated instruction. So I following these two pages and could finally installed maven2 on my machine.
Jpackage.org: Installation
Jpackage.org: Using a Repository -- Yum
Related
Server OS is Fedora 24. 64bit.
I want to install Git 2.6.6.
So download source code and installed.
This server is offline. So i don't use 'yum'.
./configure --prefix=/usr/local/git-2.6.6
make prefix=/usr/local/git-2.6.6 all
this is error message.
Can't locate ExtUtils/MakeMaker.pm in #INC (you may need to install the ExtUtils::MakeMaker module) (#INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at Makefile.PL line 3.
So I install ExUtils::MakeMaker.
First I download rpm file(https://fedora.pkgs.org/24/fedora-x86_64/perl-ExtUtils-MakeMaker-7.10-4.fc24.noarch.rpm.html)
And install rpm file
[root#swcm 다운로드]# rpm -ivh perl-ExtUtils-MakeMaker-7.10-4.fc24.noarch.rpm
오류: Failed dependencies:
perl(ExtUtils::Install) >= 1.52 is needed by perl-ExtUtils-MakeMaker-7.10-4.fc24.noarch
perl(ExtUtils::Installed) is needed by perl-ExtUtils-MakeMaker-7.10-4.fc24.noarch
perl(ExtUtils::Packlist) is needed by perl-ExtUtils-MakeMaker-7.10-4.fc24.noarch
perl-ExtUtils-ParseXS is needed by perl-ExtUtils-MakeMaker-7.10-4.fc24.noarch
[root#swcm 다운로드]# rpm -ivh perl-ExtUtils-Install-1.54-3.noarch.rpm
경고: perl-ExtUtils-Install-1.54-3.noarch.rpm: Header V3 DSA/SHA1 Signature, key ID 4026433f: NOKEY
오류: Failed dependencies:
perl(ExtUtils::MakeMaker) is needed by perl-ExtUtils-Install-1:1.54-3.noarch
perl(VMS::Filespec) is needed by perl-ExtUtils-Install-1:1.54-3.noarch
perl-ExtUtils-MakeMaker need to perl-ExtUtils-Install.
perl-ExtUtils-Install need to perl-ExtUtils-MakeMaker.
I don't know. What should I do?
Firstly, do you realise that Fedora 24 support ended last week? You are now using an unsupported operating system. I recommend upgrading to Fedora 25 or 26 as soon as possible.
Secondly, the version of git that is available for Fedora 24 is 2.7.4. You can download the RPM for this version from here. If you specifically need an older version, then perhaps you could explain why you think that (it's rarely true in my experience).
Thirdly, I think you're running up against Fedora's deliberately broken Perl installation. What you really want to do is to install the perl-core RPM (but that has dozens of dependencies that you will need to download).
To solve your current circular dependency problem, try installing both RPMs at the same time.
$ sudp rpm -ivh perl-ExtUtils-MakeMaker-*.rpm perl-ExtUtils-Install-*.rpm
But your life is going to get a lot easier if you can connect this machine to the internet - even temporarily.
you can try carton.
write a cpanfile
carton install on one server with internet
carton bundle
then scp those .tar.gz or whatever to the server do not have internet
carton install --cached (or cpanm the .tar.gz directly)
once done, move those files under local to the system dir.
https://metacpan.org/pod/Carton
another way is that you can install all those modules with the server has internet (same OS), then scp or rsync the installed files)
Thanks
A few days ago I had a few problems while installing trying to install lapis on my new installation of linux mint. The main problem was that I wanted to have lua 5.3 as the main lua interpreter on my system, but lapis only works with lua 5.1.
This is how I ended up installing it
Note: Instructions for normal installation process, with aditional lua 5.3 being optional
Prerequisites
First of all install all the prerequisites with apt-get install libreadline-dev libncurses5-dev libpcre3-dev libssl-dev perl make build-essential*. This is all you should need to install lua, luarocks and openresty.
* copied from openresty website
Lua Interpreter(s)
Next, go to https://www.lua.org/versions.html and download the latest version of lua5.1 (wget https://www.lua.org/ftp/lua-5.1.5.tar.gz). Then extract the downloaded file tar -xf lua-5.1.5.tar.gz and optionally rename the directory mv lua-5.1.5 lua51.
Now you can simply build and install lua by moving to the directory cd lua51 and running make make linux and sudo make install
Aditionally, you might want to have lua5.3 installed on your system as the main lua interpreter. Luarocks doesn't seem to particularly like this kind of setup though, so I recommend the following:
First download and extract (and optionally rename) both lua5.1 and lua 5.3; go to the lua 5.1 directory and open Makefile in a text editor; Edit lines 12-15 to install lua in another directory. For me it worked to just add /lua51 to INSTALL_TOP (line 12). Next go to line 44 and change the names of the binaries (I chose lua51 and luac51), optionally do the same with the man pages (this requires also changing them in the doc subdirectory).
The next step is to go to the src/ directory and edit the makefile there as well: in lines 32 and 35 change the names as you did in the previous makefile (lua51 and luac51 in my case).
After this you can just make linux and sudo make install as described above.
Luarocks
Now you need to install luarocks on your system. Start by downloading the latest release of luarocks (http://keplerproject.github.io/luarocks/releases/) and extract it. Again, you can rename it to luarocks/ reduce typing. cd to the directory you just extracted and run ./condigure.
If you changed the lua installation path, you will have give some parameters to the configure script:
For lua 5.1 ./configure --lua-version=5.1 --with-lua=/usr/local/lua51 --lua-suffix=51 is how I had to do it (--lua-suffix is what I added to lua and luac and --with-lua tells it where the bin, lib, etc. subdirectories are; only relevant if you changed INSTALL_TOP in the makefile)
Optionally you can now proceed to (download, ) build and install lua 5.3 with its standard configuration. After that you can even go back to the luarocks directory and repeat ./configure, make build and make install and it should automatically install itself with lua 5.3 and leave the installation for lua5.1 intact**.
** the luarocks executable is actually just a symlink to luarocks-VERSION (where VERSION can be 5.1, 5.3, etc.) in the same directory. Each time you install luarocks this link is overwritten to point to the latest installation, but the other executables are still there.
OpenResty
The next step is to install OpenResty: open http://openresty.org/en/installation.html and check the prerequisite section. It should say the same as at the beginning of this answer. If not, install any missing package now. You can also just follow the installation instructions there, but I will be repeating it anyway; go to http://openresty.org/en/download.html and download the latest version. Extract the downloaded archives (and rename the new directory to simply openresty). cd to the new directory and run ./configure --with-pcre-jit --with-ipv6 (this might take a while), make (this might take an even longer while) and sudo make install.
At this point everything except lapis itself should be set up and working.
Lapis
To install lapis, type sudo lurocks install lapis (user luarocks-5.1** instead if you have installed more than one version of it).
Congratulations! If you got no errors, you should now have lapis installed and ready to use :)
** see section Luarocks.
I want to host an apt-get repository.
How do I package my application, and how do I host it in a repository for use?
The application relies on Java, MySQL, upstart and is configured to run on boot as an upstart service.
The answer should also include, how to host the package on a repository.
Ref:
How do I package a Java program for Ubuntu?
How do I package Mono applications for Debian/Ubuntu
Packaging for Ubuntu - Web Application
Good question, maybe a personal ppa is what you are looking for. After you finish you will have to do a $ sudo add-apt-repository ppa:myApp/ppa. Then you can apt-get install it.
To package your application you will need to do this in your apps directory
myappFolder$ dh_make -p myApp_1.0 --createorig
To create a original tar of your app. This will also create a Debian folder with a control file, a rules file, changelog... Change the values in these files to fit how your package should be. Specifically the control file. You will have a Depends: field where you can write in packages your application relies on such as Java and MySQL, make sure to have the same names as Ubuntu repository for these things.
goodLink https://www.debian.org/doc/manuals/maint-guide/dreq.en.html
Check out chapter 5 the install file and then building the package in chapter 6. I use dpkg-buildpackage usually. debuild -us -uc is good too look up too.
Then create an account on Ubuntu launchpad.
https://login.launchpad.net/+new_account
Sign the Ubuntu code of conduct:
https://launchpad.net/codeofconduct (take away the extra h, no reputation for more links)
Activate a PPA:
https://launchpad.net/people/+me/ (extra h)
Then follow this guide to upload the package to your ppa:
https://help.launchpad.net/Packaging/PPA/Uploading (extra h)
I got these links from a great answer on ask.ubuntu. It's also got a more lengthy answer on creating a deb package.
https://askubuntu.com/questions/71510/how-do-i-create-a-ppa
Based on the article https://www.novell.com/support/kb/doc.php?id=7016113 I am trying to apply the glibc patches. However, I cannot update the system online as it is not connected to internet. I have downloaded the relevant security patches
glibc-html-2.11.3-17.45.55.5
glibc-i18ndata-2.11.3-17.45.55.5
glibc-info-2.11.3-17.45.55.5
glibc-locale-2.11.3-17.45.55.5
glibc-profile-2.11.3-17.45.55.5
nscd-2.11.3-17.45.55.5
All these are .rpm files. However,I am not sure how to apply these to the system. What is the command that I need to use? As per SUSE documentation it refers to using zypper ,but not sure on the exact procedure. Please let me know how do I apply these and how do I check if there are any dependencies that I need to install before this?
Thanks!
you can just do:
zypper in <path-to-rpm> <path-to-other-rpm>
if there are any missing dependencies, zypper will tell you.
You can also do it the old way using rpm:
rpm -Uvh <path-to-rpm> <path-to-other-rpm>
which basically does the same...
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
My development server (CentOS 5) is running Subversion 1.4.2, and I wish to upgrade it to 1.5. I have read in various blogs and documents scattered around the web that this may be done by using RPMForge. I have followed the instructions found on CentOS Wiki, including installing yum-priorities and setting my priorities as indicated (1 and 2 for core repo sources, and 20 for RPMForge).
However, when I attempt to run:
$ yum info subversion
the version number given to me is still 1.4.2, with a status of Installed. My other option at this point is compiling from source, but I would like to find a package-managed solution for ease of future upgrades.
Any thoughts?
What you are trying to do is to replace a "core" package (one which is
contained in the CentOS repository) with a newer package from a "3rd
party" repository (RPMForge), which is what the priorities plugin is
designed to prevent.
The RPMForge repository contains both additional packages not found in
CentOS, as well as newer versions of core packages. Unfortunately, yum
is pretty stupid and will always update a package to the latest version
it can find in any repository. So running "yum update" with RPMforge
enabled will update half of your system with the latest (bleeding edge,
possibly unstable and less well supported) packages from RPMForge.
Therefore, the recommended way to use repos like RPMForge is to use them
only together with a yum plugin like "priorites", which prevents
packages from "high" priority repos to overwrite those from "low"
priority repos (the name of the "priority" parameter is very
misleading). This way you can savely install additional packages (that
are not in core) from RPMForge, which is what most people want.
Now to your original question ...
If you want to replace a core package, things get a little tricky.
Basically, you have two options:
Uninstall the priority plugin, and disable the RPMForge repository by
default (set enabled = 0 in /etc/yum.repos.d/rpmforge.repo). You can
then selectively enable it on the command line:
yum --enablerepo=rpmforge install subversion
will install the latest subversion and dependencies from RPMForge.
The problem with this approach is that if there is an update to the
subversion package in RPMForge, you will not see it when the repo is
disabled. To keep subversion up to date, you have to remember to run
yum --enablerepo=rpmforge update subversion
from time to time.
The second possibility is to use the priorites plugin, but manually
"mask" the core subversion package (add exclude=subversion to the
[base] and [update] sections in /etc/yum.repos.d/CentOS-Base.repo).
Now yum will behave as if there is no package named "subversion" in
the core repository and happily install the latest version from
RPMForge. Plus, you will always get the latest subversion updates
when running yum update.
1.- if you are using yum-priorities disable this in the file /etc/yum/pluginconf.d/priorities.conf
2.- check the version of subversion
$ rpm -qa|grep subversion
subversion-1.4.2-4.el5_3.1
subversion-1.4.2-4.el5_3.1
3.- search the last version of the subversion from rpmforge repository
$ yum --enablerepo=rpmforge check-update subversion
subversion.x86_64 1.6.6-0.1.el5.rf rpmforge
4.- now proced to upgrade subversion with rpmforge repository
$ yum shell
>erase mod_dav_svn-1.4.2-4.el5_3.1
>erase subversion-1.4.2-4.el5_3.1
>install mod_dav_svn-1.6.6-0.1.el5.rf
>install subversion-1.6.6-0.1.el5.rf.x86_64
>run
that's all it works for me im running centos 5.4
Thanks Matt - we also have the only distro of SVN 1.7 on SVN.
You may also want to try uberSVN.
If you install RPMForge's repos, you should then be able to get a newer package - this isn't working for you?
You should see rpmforge.list in /etc/apt/sources.list.d with a line like:
repomd http://apt.sw.be redhat/el$(VERSION)/en/$(ARCH)/dag
I just tested on a clean CentOS 5 install, and yum check-update shows
subversion.i386 1.5.2-0.1.el5.rf rpmforge
subversion-perl.i386 1.5.2-0.1.el5.rf rpmforge
So check your sources list and run check-update again.
Edit: Whoops, lost part of my answer. Added it back above.
I'm not overly concerned about the other outdated packages at the moment, but as you can see there is no Subversion update available.
Nor any packages from rpmforge. It's your priority settings. Try disabling yum-priorities (change enabled=1 to enabled=0 in /etc/yum/pluginconf.d/priorities.conf) - then it should work.
So I guess the next question is why the priority is screwing it up.... I'm not sure on this, though.
Edit: See 8jean's answer for more about priorities.
its up to v 1.4.6 in Dag's repository.
You can try the one from Fedora's repo or have a bit of patience for the main repositories to upgrade it.
Making it from source is easy, read the INSTALL file when you download the source package, bear in mind CentOS may have moved where the files get installed. (Use "rpm -ql subversion" to see where the old files were installed to).
When v1.5.0 gets released to the repository, you can delete your built version and install using yum as before.
RPMForge is already in /etc/yum.repos.d/ as rpmforge.repo, and the contents are:
# Name: RPMforge RPM Repository for Red Hat Enterprise 5 - dag
# URL: http://rpmforge.net/
[rpmforge]
name = Red Hat Enterprise $releasever - RPMforge.net - dag
#baseurl = http://apt.sw.be/redhat/el5/en/$basearch/dag
mirrorlist = http://apt.sw.be/redhat/el5/en/mirrors-rpmforge
#mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge
enabled = 1
protect = 0
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag
gpgcheck = 1
priority=20
I have that exact line in in /etc/apt/sources.list.d/rpmforge.list .
When I run check-update, I get:
Loading "priorities" plugin
Loading "fastestmirror" plugin
Loading mirror speeds from cached hostfile
* epel: mirror.unl.edu
* rpmforge: fr2.rpmfind.net
* base: mirrors.portafixe.com
* updates: mirrors.portafixe.com
* addons: mirrors.portafixe.com
* extras: mirrors.portafixe.com
2202 packages excluded due to repository priority protections
bzip2.i386 1.0.3-4.el5_2 updates
bzip2-devel.i386 1.0.3-4.el5_2 updates
bzip2-libs.i386 1.0.3-4.el5_2 updates
libxml2.i386 2.6.26-2.1.2.6 updates
libxml2-devel.i386 2.6.26-2.1.2.6 updates
libxml2-python.i386 2.6.26-2.1.2.6 updates
perl.i386 4:5.8.8-15.el5_2.1 updates
sos.noarch 1.7-9.2.el5_2.2 updates
tzdata.noarch 2008e-1.el5 updates
I'm not overly concerned about the other outdated packages at the moment, but as you can see there is no Subversion update available.
All you need to do is get this script. worked perfectly for me on CentOS 5.3
http://wandisco.com/subversion/os/downloads
No, i don't work there or have any affiliation what-so-ever ... just found it and figured I would let you guys knows.
Good luck.