You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Tilsley, Jerry M." <jm...@st-claire.org> on 2012/08/08 17:02:55 UTC
Install SVN from YUM, change Sqlite3 library path
All,
I am running RHEL 6.2 and am trying to install subversion via YUM. When I do this, it picks up a version of sqlite3 that not all my users have access to. The version of sqlite3 that all users have access to is in a path that I'm afraid isn't being searched by the YUM installation. How can I fix this so that the libraries of the version I want is loaded with the subversion installation?
Thanks,
Jerry Tilsley
Sr Systems Analyst
St. Claire Regional Medical Center
________________________________
Disclaimer****
This email is confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of St. Claire Regional Medical Center. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of the email is strictly prohibited. If you received this email in error please notify the St. Claire Regional Helpdesk by telephone at 606-783-6565.
Re: Install SVN from YUM, change Sqlite3 library path
Posted by Les Mikesell <le...@gmail.com>.
On Wed, Aug 8, 2012 at 11:51 AM, Tilsley, Jerry M.
<jm...@st-claire.org> wrote:
>
> Sorry, I'm going by a Centos install which is usually the same but
> maybe there is some difference. On Centos, sqlite 3.6.20 is the
> current stock version and what other packages should expect. I'd
> look at the problem the other way and figure out why your other user has
> something out of date in his library path.
>
> The user has an out of date package because the user and package are part of
> a large data interfacing system for a hospital. I would like for that user
> to be able to check scripts in, but because of the vendor system relies on
> the older version of sqlite, the user has to use that version.
Linux itself is relatively flexible about library paths and multiple
versions of things, but the RPM packaging system generally just wants
to manage a single version at a time on a machine (with a few
exceptions). Some brute-force solutions would be to recompile from
source, either with a static linkage to the current library or on the
target machine against the outdated libs. Or copy the current .so
file over to some other path that you would add to LD_LIBRARY_PATH in
the environment when running svn. Or if you don't care about branch
tracking, you might compile a 1.5 version from source that would not
have the library requirement but still has wire-protocol
compatibility.
--
Les Mikesell
lesmikesell@gmail.com
Re: Install SVN from YUM, change Sqlite3 library path
Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Thu, Aug 9, 2012 at 10:15 AM, Tilsley, Jerry M.
<jm...@st-claire.org> wrote:
> All,
>
> I was able to compile and install the version of SQLite I needed out into the public area. Then I downloaded the source of an earlier version of subversion and when I configured, it pulled in the sqlite.h file for the correct version. Now all is working for ALL my users as expected!
>
> Thanks,
>
> Jerry
Unless you installed it as an RPM and block yum from updating
subversion, this will break the next time subversion is updated in
your basic OS updates or if it is pulled in from dependencies for
another component, such as "git2svn".
The sqlite.h you are using should not be considered the "correct
version", seriously. It is apparently a non-standard, distributed
out-of-band version of SQLite and not part of the basic CentOS or RHEL
operating system and, in my experienced opinion, should not be used
for anything but that propietary software, to avoid precisely such
problems.
Why is it being found? Is there LD_LIBRARY_PATH being set somewhere
with a non-standard path, is /etc/ld.so.conf being set oddly, or does
it actually include an out-of-date RPM for SQLite that is triggering
these version conflicts?
RE: Install SVN from YUM, change Sqlite3 library path
Posted by "Tilsley, Jerry M." <jm...@st-claire.org>.
All,
I was able to compile and install the version of SQLite I needed out into the public area. Then I downloaded the source of an earlier version of subversion and when I configured, it pulled in the sqlite.h file for the correct version. Now all is working for ALL my users as expected!
Thanks,
Jerry
> -----Original Message-----
> From: Nico Kadel-Garcia [mailto:nkadel@gmail.com]
> Sent: Wednesday, August 08, 2012 4:49 PM
> To: Tilsley, Jerry M.
> Cc: Les Mikesell; users@subversion.apache.org
> Subject: Re: Install SVN from YUM, change Sqlite3 library path
>
> On Wed, Aug 8, 2012 at 12:51 PM, Tilsley, Jerry M.
> <jm...@st-claire.org> wrote:
> >
> > -----Original Message-----
> > From: Les Mikesell [mailto:lesmikesell@gmail.com]
> > Sent: Wednesday, August 08, 2012 12:45 PM
> > To: Tilsley, Jerry M.
> > Cc: users@subversion.apache.org
> > Subject: Re: Install SVN from YUM, change Sqlite3 library path
> >
> > On Wed, Aug 8, 2012 at 11:27 AM, Tilsley, Jerry M.
> > <jm...@st-claire.org> wrote:
> >> The repository is the basic one for RHEL 6.2, I haven't added any others.
> >> The issue is that this is installed by root, so it finds one set of
> >> libraries and compiles for that. Then when my other user tries to
> >> commit I get the error that Sqlite was compiled for 3.6.20 but using
> >> 3.6.4. I need this to be installed and compiled with the 3.6.4, but
> >> I cannot figure out how to get yum to pull that one in.
> >
> > Sorry, I'm going by a Centos install which is usually the same but
> > maybe there is some difference. On Centos, sqlite 3.6.20 is the
> > current stock version and what other packages should expect. I'd
> > look at the problem the other way and figure out why your other user
> > has something out of date in his library path.
> >
> > The user has an out of date package because the user and package are
> > part of a large data interfacing system for a hospital. I would like
> > for that user to be able to check scripts in, but because of the
> > vendor system relies on the older version of sqlite, the user has to use that
> version.
>
> *Oh*. And their out of date package is not in an RPM, and is somewhere
> enforcing a LD_LIBRARY_PATH in the user's environment to get the SQLite
> libraries from that out of date package.
>
> There are a number of possible approaches. I'm assuming this happens only
> for this specific user, or only for users's who've enabled a LD_LIBRARY_PATH
> as part of the configuration for this out of date package. One approach is to
> use something like this in the user's .bashrc or .profile.
>
> alias svn='LD_LIBRARY_PATH="" /usr/bin/svn"
________________________________
Disclaimer****
This email is confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of St. Claire Regional Medical Center. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of the email is strictly prohibited. If you received this email in error please notify the St. Claire Regional Helpdesk by telephone at 606-783-6565.
Re: Install SVN from YUM, change Sqlite3 library path
Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Wed, Aug 8, 2012 at 12:51 PM, Tilsley, Jerry M.
<jm...@st-claire.org> wrote:
>
> -----Original Message-----
> From: Les Mikesell [mailto:lesmikesell@gmail.com]
> Sent: Wednesday, August 08, 2012 12:45 PM
> To: Tilsley, Jerry M.
> Cc: users@subversion.apache.org
> Subject: Re: Install SVN from YUM, change Sqlite3 library path
>
> On Wed, Aug 8, 2012 at 11:27 AM, Tilsley, Jerry M.
> <jm...@st-claire.org> wrote:
>> The repository is the basic one for RHEL 6.2, I haven't added any others.
>> The issue is that this is installed by root, so it finds one set of
>> libraries and compiles for that. Then when my other user tries to commit I
>> get the error that Sqlite was compiled for 3.6.20 but using 3.6.4. I need
>> this to be installed and compiled with the 3.6.4, but I cannot figure out
>> how to get yum to pull that one in.
>
> Sorry, I'm going by a Centos install which is usually the same but
> maybe there is some difference. On Centos, sqlite 3.6.20 is the
> current stock version and what other packages should expect. I'd
> look at the problem the other way and figure out why your other user has
> something out of date in his library path.
>
> The user has an out of date package because the user and package are part of
> a large data interfacing system for a hospital. I would like for that user
> to be able to check scripts in, but because of the vendor system relies on
> the older version of sqlite, the user has to use that version.
*Oh*. And their out of date package is not in an RPM, and is somewhere
enforcing a LD_LIBRARY_PATH in the user's environment to get the
SQLite libraries from that out of date package.
There are a number of possible approaches. I'm assuming this happens
only for this specific user, or only for users's who've enabled a
LD_LIBRARY_PATH as part of the configuration for this out of date
package. One approach is to use something like this in the user's
.bashrc or .profile.
alias svn='LD_LIBRARY_PATH="" /usr/bin/svn"
RE: Install SVN from YUM, change Sqlite3 library path
Posted by "Tilsley, Jerry M." <jm...@st-claire.org>.
-----Original Message-----
From: Les Mikesell [mailto:lesmikesell@gmail.com]
Sent: Wednesday, August 08, 2012 12:45 PM
To: Tilsley, Jerry M.
Cc: users@subversion.apache.org
Subject: Re: Install SVN from YUM, change Sqlite3 library path
On Wed, Aug 8, 2012 at 11:27 AM, Tilsley, Jerry M.
<jm...@st-claire.org>> wrote:
> The repository is the basic one for RHEL 6.2, I haven't added any others. The issue is that this is installed by root, so it finds one set of libraries and compiles for that. Then when my other user tries to commit I get the error that Sqlite was compiled for 3.6.20 but using 3.6.4. I need this to be installed and compiled with the 3.6.4, but I cannot figure out how to get yum to pull that one in.
Sorry, I'm going by a Centos install which is usually the same but
maybe there is some difference. On Centos, sqlite 3.6.20 is the
current stock version and what other packages should expect. I'd
look at the problem the other way and figure out why your other user has something out of date in his library path.
The user has an out of date package because the user and package are part of a large data interfacing system for a hospital. I would like for that user to be able to check scripts in, but because of the vendor system relies on the older version of sqlite, the user has to use that version.
--
Les Mikesell
lesmikesell@gmail.com<ma...@gmail.com>
________________________________
Disclaimer****
This email is confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of St. Claire Regional Medical Center. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of the email is strictly prohibited. If you received this email in error please notify the St. Claire Regional Helpdesk by telephone at 606-783-6565.
Re: Install SVN from YUM, change Sqlite3 library path
Posted by Les Mikesell <le...@gmail.com>.
On Wed, Aug 8, 2012 at 11:27 AM, Tilsley, Jerry M.
<jm...@st-claire.org> wrote:
> The repository is the basic one for RHEL 6.2, I haven't added any others. The issue is that this is installed by root, so it finds one set of libraries and compiles for that. Then when my other user tries to commit I get the error that Sqlite was compiled for 3.6.20 but using 3.6.4. I need this to be installed and compiled with the 3.6.4, but I cannot figure out how to get yum to pull that one in.
Sorry, I'm going by a Centos install which is usually the same but
maybe there is some difference. On Centos, sqlite 3.6.20 is the
current stock version and what other packages should expect. I'd
look at the problem the other way and figure out why your other user
has something out of date in his library path.
--
Les Mikesell
lesmikesell@gmail.com
RE: Install SVN from YUM, change Sqlite3 library path
Posted by "Tilsley, Jerry M." <jm...@st-claire.org>.
The repository is the basic one for RHEL 6.2, I haven't added any others. The issue is that this is installed by root, so it finds one set of libraries and compiles for that. Then when my other user tries to commit I get the error that Sqlite was compiled for 3.6.20 but using 3.6.4. I need this to be installed and compiled with the 3.6.4, but I cannot figure out how to get yum to pull that one in.
-----Original Message-----
From: Les Mikesell [mailto:lesmikesell@gmail.com]
Sent: Wednesday, August 08, 2012 12:25 PM
To: Tilsley, Jerry M.
Cc: users@subversion.apache.org
Subject: Re: Install SVN from YUM, change Sqlite3 library path
On Wed, Aug 8, 2012 at 10:02 AM, Tilsley, Jerry M.
<jm...@st-claire.org> wrote:
> All,
>
>
>
> I am running RHEL 6.2 and am trying to install subversion via YUM.
> When I do this, it picks up a version of sqlite3 that not all my users
> have access to. The version of sqlite3 that all users have access to
> is in a path that I'm afraid isn't being searched by the YUM
> installation. How can I fix this so that the libraries of the version
> I want is loaded with the subversion installation?
Yum doesn't have much to do with library paths. It uses rpm dependencies to decide what other packages need to be installed and
should bring in everything the application needs. If you are using
3rd party repositories (as you must to get a subversion that needs
sqlite...) the package should be set up to require any libraries from there that it needs to work and they should be installed together.
--
Les Mikesell
lesmikesell@gmail.com
________________________________
Disclaimer****
This email is confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of St. Claire Regional Medical Center. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of the email is strictly prohibited. If you received this email in error please notify the St. Claire Regional Helpdesk by telephone at 606-783-6565.
Re: Install SVN from YUM, change Sqlite3 library path
Posted by Les Mikesell <le...@gmail.com>.
On Wed, Aug 8, 2012 at 10:02 AM, Tilsley, Jerry M.
<jm...@st-claire.org> wrote:
> All,
>
>
>
> I am running RHEL 6.2 and am trying to install subversion via YUM. When I
> do this, it picks up a version of sqlite3 that not all my users have access
> to. The version of sqlite3 that all users have access to is in a path that
> I’m afraid isn’t being searched by the YUM installation. How can I fix this
> so that the libraries of the version I want is loaded with the subversion
> installation?
Yum doesn't have much to do with library paths. It uses rpm
dependencies to decide what other packages need to be installed and
should bring in everything the application needs. If you are using
3rd party repositories (as you must to get a subversion that needs
sqlite...) the package should be set up to require any libraries from
there that it needs to work and they should be installed together.
--
Les Mikesell
lesmikesell@gmail.com