On Tue, May 27, 2008 at 06:32:48PM -0700, Ray Van Dolson wrote:
> Anyone else getting the following when trying to upgrade libxslt and
> libxslt-devel?
> 
> --> Running transaction check
> ---> Package libxslt-devel.i386 0:1.1.17-2.el5_1.1 set to be updated
> --> Processing Dependency: libxslt = 1.1.17-0 for package: libxslt-devel
> --> Finished Dependency Resolution
> Error: Missing Dependency: libxslt = 1.1.17-0 is needed by package 
> libxslt-devel
> 
> I actually also get the same error for libvorbis and libvorbis-devel:
<snip>
> 
> Epoch flags biting me here?  If I build libxslt from SRPM I can update
> it fine.  I have done a yum clean all.
> 
> This is on a fresh install of RHEL 5.2 i386.
> 
> Wanted to throw this out before filing a bug/sr.

I think you are running into the same yum RHN issue I hit a few days
ago. Basically yum + yum-metadata-parser from 5.2 appear to have
a bug when pulling dependency information via RHN repos.

The following is a snippet of yum debug output when talking to
identical repositories, the first via RHN the second straight http.
< looking for ('tcl-devel', 'EQ', ('0', '8.4.13', '0')) as a requirement of 
tk-devel.x86_64 0-8.4.13-5.el5_1.1 - u
> looking for ('tcl-devel', 'EQ', ('0', '8.4.13', None)) as a requirement of 
> tk-devel.x86_64 0-8.4.13-5.el5_1.1 - u

When talking to RHN, the release version in a Requires is forced
to 0 if it does not exist. What seems to be the proper operation
is seen when not talking through yum-rhn-plugin.

Reverting to the 5.1 version of yum and yum-metadata-parser (3.0.1
and 1.0-8) is functional as a temporarily workaround.

I had not filed a bug report yet since I have not had time to
validate the issue by digging into the code and/or replicating with
clean installs against a second RHN server. If you beat me to it,
please forward along the BZ/IssueTracker number.

Justin

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to