Looks like I am getting conflicting information from repoquery and yum.
I get the following from yum deplist:$ yum deplist python-sqlite-0:1.1.7-1.2.1.x86_64
Finding dependencies:
package: python-sqlite.x86_64 1.1.7-1.2.1
dependency: libc.so.6()(64bit)
provider: glibc.x86_64 2.5-58.el5_6.4
dependency: libc.so.6(GLIBC_2.2.5)(64bit)
provider: glibc.x86_64 2.5-58.el5_6.4
dependency: libc.so.6(GLIBC_2.3)(64bit)
provider: glibc.x86_64 2.5-58.el5_6.4
dependency: libc.so.6(GLIBC_2.4)(64bit)
provider: glibc.x86_64 2.5-58.el5_6.4
dependency: libpthread.so.0()(64bit)
provider: glibc.x86_64 2.5-58.el5_6.4
dependency: libsqlite3.so.0()(64bit)
provider: sqlite.x86_64 3.3.6-5
provider: dropbox.x86_64 0.7.110-1.el5.rf
dependency: python(abi) = 2.4
provider: python.x86_64 2.4.3-44.el5
provider: python.i386 2.4.3-44.el5
dependency: rtld(GNU_HASH)
provider: glibc.x86_64 2.5-58.el5_6.4
provider: glibc.i686 2.5-58.el5_6.4
provider: glibc.i386 2.5-58.el5_6.4
Finding dependencies:
package: python-sqlite.x86_64 1.1.7-1.2.1
dependency: libc.so.6()(64bit)
provider: glibc.x86_64 2.5-58.el5_6.4
dependency: libc.so.6(GLIBC_2.2.5)(64bit)
provider: glibc.x86_64 2.5-58.el5_6.4
dependency: libc.so.6(GLIBC_2.3)(64bit)
provider: glibc.x86_64 2.5-58.el5_6.4
dependency: libc.so.6(GLIBC_2.4)(64bit)
provider: glibc.x86_64 2.5-58.el5_6.4
dependency: libpthread.so.0()(64bit)
provider: glibc.x86_64 2.5-58.el5_6.4
dependency: libsqlite3.so.0()(64bit)
provider: sqlite.x86_64 3.3.6-5
provider: dropbox.x86_64 0.7.110-1.el5.rf
dependency: python(abi) = 2.4
provider: python.x86_64 2.4.3-44.el5
provider: python.i386 2.4.3-44.el5
dependency: rtld(GNU_HASH)
provider: glibc.x86_64 2.5-58.el5_6.4
provider: glibc.i686 2.5-58.el5_6.4
provider: glibc.i386 2.5-58.el5_6.4
glibc.x86_64 2.5-58.el5_6.4
sqlite.x86_64 3.3.6-5 OR dropbox.x86_64 0.7.110-1.el5.rf
python.x86_64 2.4.3-44.el5
sqlite.x86_64 3.3.6-5 OR dropbox.x86_64 0.7.110-1.el5.rf
python.x86_64 2.4.3-44.el5
Note that I can use either dropbox or sqlite to satisfy python-sqlite. I don't need both.
However, if I run a similar command with repoquery, I get conflicting results:
However, if I run a similar command with repoquery, I get conflicting results:
$ repoquery --requires --resolve --archlist=x86_64,noarch python-sqlite-0:1.1.7-1.2.1.x86_64
python-0:2.4.3-44.el5.x86_64
dropbox-0:0.7.110-1.el5.rf.x86_64
glibc-0:2.5-58.el5_6.2.x86_64
sqlite-0:3.3.6-5.x86_64
python-0:2.4.3-44.el5.x86_64
dropbox-0:0.7.110-1.el5.rf.x86_64
glibc-0:2.5-58.el5_6.2.x86_64
sqlite-0:3.3.6-5.x86_64
It seems to think I need BOTH dropbox and sqlite.
I would prefer to use the repoquery command because it should resolve my dependencies for me, but it does not appear to get me what I need.
Any thoughts? I'll start looking into what repositories are enabled.
Thanks!!
Thanks!!
On Mon, Jun 24, 2013 at 8:17 PM, Chris Kittlitz <ckittlitz@xxxxxxxxx> wrote:
CentOS 6.4. I'll take a look at my repositories tomorrow.Thanks for all the help.
On Monday, June 24, 2013, Frank Murphy wrote:On Mon, 24 Jun 2013 14:44:37 -0400
Chris Kittlitz <ckittlitz@xxxxxxxxx> wrote:
> I know how to resolve the last - repoquery --resolve
> pythone-elementtree. But how do I do the second? What does "(abi)"
> mean and how do I include that information when I am resolving the
> dependency?
>
> Thanks!
It means some of your pkgs maybe mixed,
some possible from different CentOS and or Epel releases.
What CentOS are you supposed to have?
--
Regards,
Frank "When in doubt PANIC!"
I check for new mail app. 20min
www.frankly3d.com
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
_______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum