[users] Dependency issue with installing mod_dav_svn package on CentOS 5?

[Alfred von Campe]

On a CentOS 5 system, with the rpmforge as the only external
repository, and the Subversion 1.6.9 RPM from rpmforge installed, I
get the following error when trying to install mod_dav_svn:

# yum install mod_dav_svn
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Updates
Finished
639 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mod_dav_svn.i386 0:1.4.2-4.el5_3.1 set to be updated
--> Processing Dependency: subversion = 1.4.2-4.el5_3.1 for package:
mod_dav_svn
--> Finished Dependency Resolution
mod_dav_svn-1.4.2-4.el5_3.1.i386 from base has depsolving problems
--> Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by
package mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
Error: Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by
package mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest

If I install the RPM with rpm instead of yum, everything works find
in apache, but now yum complains about the missing dependency when
doing a "yum update". The workaround for me for now is to uninstall
the RPM, do a yum update, and then reinstall the RPM. Needless to
say, this is not ideal. Is there anything that can be done to fix
this or am I doing something wrong?

Alfred

[Paul Heinlein]

Post by Alfred von Campe
On a CentOS 5 system, with the rpmforge as the only external
repository, and the Subversion 1.6.9 RPM from rpmforge installed, I
# yum install mod_dav_svn
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Updates
Finished
639 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mod_dav_svn.i386 0:1.4.2-4.el5_3.1 set to be updated
--> mod_dav_svn
--> Finished Dependency Resolution
mod_dav_svn-1.4.2-4.el5_3.1.i386 from base has depsolving problems
--> Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by package
--> mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
Error: Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by package
mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
If I install the RPM with rpm instead of yum, everything works find in
apache, but now yum complains about the missing dependency when doing a "yum
update". The workaround for me for now is to uninstall the RPM, do a yum
update, and then reinstall the RPM. Needless to say, this is not ideal. Is
there anything that can be done to fix this or am I doing something wrong?

Are you running an x86_64 system? Does "rpm -q subversion" return two
(seemingly identical) entries? If so, the trouble is that you've got
i386 and an x86_64 subversion packages installed. Try

rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion

In that case, you can probably just delete the 32-bit version and then
try the update. (I should say, I've had no difficulties removing the
32-bit packages. There may be good reasons for both to be there, but I
don't know what they are.)

[Alfred von Campe]

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

No, I'm running i386 and only have one RPM installed:

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386

I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.

Alfred

[Christoph Maser]

Post by Alfred von Campe

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386
I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.
Alfred

And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)


Chris

[Nicolas Thierry-Mieg]

Post by Christoph Maser

Post by Alfred von Campe

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386
I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.
Alfred

And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)

well, if you want the newer subversion from rpmforge, I guess you should
also install mod_dav_svn 1.6.11 from rpmforge?

[Alfred von Campe]

Post by Nicolas Thierry-Mieg
well, if you want the newer subversion from rpmforge, I guess you
should also install mod_dav_svn 1.6.11 from rpmforge?

Yes, "yum install mod_dav_svn --disablerepo=base" does the trick!
I'll have to add a permanent rule to exclude mod_dav_svn from the
base repo so that I don't run into this again in the future.

Thanks,
Alfred

[Alfred von Campe]

Post by Nicolas Thierry-Mieg
well, if you want the newer subversion from rpmforge, I guess you
should also install mod_dav_svn 1.6.11 from rpmforge?

Yes, "yum install mod_dav_svn --disablerepo=base" does the trick!
I'll have to add a permanent rule to exclude mod_dav_svn from the
base repo so that I don't run into this again in the future.

Thanks,
Alfred

[Alfred von Campe]

Post by Nicolas Thierry-Mieg
well, if you want the newer subversion from rpmforge, I guess you
should also install mod_dav_svn 1.6.11 from rpmforge?

Yes, "yum install mod_dav_svn --disablerepo=base" does the trick!
I'll have to add a permanent rule to exclude mod_dav_svn from the
base repo so that I don't run into this again in the future.

Thanks,
Alfred

[Alfred von Campe]

Post by Nicolas Thierry-Mieg
well, if you want the newer subversion from rpmforge, I guess you
should also install mod_dav_svn 1.6.11 from rpmforge?

Yes, "yum install mod_dav_svn --disablerepo=base" does the trick!
I'll have to add a permanent rule to exclude mod_dav_svn from the
base repo so that I don't run into this again in the future.

Thanks,
Alfred

[Alfred von Campe]

Post by Nicolas Thierry-Mieg
well, if you want the newer subversion from rpmforge, I guess you
should also install mod_dav_svn 1.6.11 from rpmforge?

Yes, "yum install mod_dav_svn --disablerepo=base" does the trick!
I'll have to add a permanent rule to exclude mod_dav_svn from the
base repo so that I don't run into this again in the future.

Thanks,
Alfred

[Alfred von Campe]

Post by Christoph Maser
And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)

I guess that makes sense. I think you meant to say "should not
replace...". In any event, we needed subversion 1.6 (or at least
1.5) because of its enhanced merge capabilities.

Alfred

[Nicolas Thierry-Mieg]

Post by Christoph Maser

Post by Alfred von Campe

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386
I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.
Alfred

And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)

well, if you want the newer subversion from rpmforge, I guess you should
also install mod_dav_svn 1.6.11 from rpmforge?

[Alfred von Campe]

Post by Christoph Maser
And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)

I guess that makes sense. I think you meant to say "should not
replace...". In any event, we needed subversion 1.6 (or at least
1.5) because of its enhanced merge capabilities.

Alfred

[Nicolas Thierry-Mieg]

Post by Christoph Maser

Post by Alfred von Campe

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386
I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.
Alfred

And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)

well, if you want the newer subversion from rpmforge, I guess you should
also install mod_dav_svn 1.6.11 from rpmforge?

[Alfred von Campe]

Post by Christoph Maser
And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)

I guess that makes sense. I think you meant to say "should not
replace...". In any event, we needed subversion 1.6 (or at least
1.5) because of its enhanced merge capabilities.

Alfred

[Nicolas Thierry-Mieg]

Post by Christoph Maser

Post by Alfred von Campe

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386
I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.
Alfred

And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)

well, if you want the newer subversion from rpmforge, I guess you should
also install mod_dav_svn 1.6.11 from rpmforge?

[Alfred von Campe]

Post by Christoph Maser
And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)

I guess that makes sense. I think you meant to say "should not
replace...". In any event, we needed subversion 1.6 (or at least
1.5) because of its enhanced merge capabilities.

Alfred

[Nicolas Thierry-Mieg]

Post by Christoph Maser

Post by Alfred von Campe

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386
I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.
Alfred

And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)

well, if you want the newer subversion from rpmforge, I guess you should
also install mod_dav_svn 1.6.11 from rpmforge?

[Alfred von Campe]

Post by Christoph Maser
And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)

I guess that makes sense. I think you meant to say "should not
replace...". In any event, we needed subversion 1.6 (or at least
1.5) because of its enhanced merge capabilities.

Alfred

[Christoph Maser]

Post by Alfred von Campe

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386
I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.
Alfred

And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)


Chris

[Christoph Maser]

Post by Alfred von Campe

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386
I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.
Alfred

And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)


Chris

[Christoph Maser]

Post by Alfred von Campe

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386
I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.
Alfred

And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)


Chris

[Christoph Maser]

Post by Alfred von Campe

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386
I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.
Alfred

And that is right. If you want to use anything from base linked against
subversion you have to use the subversion package from base.
This is perfect example why one normally should to replace packages from
base. (protectbase or priorities yum plugin)


Chris

[Alfred von Campe]

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

No, I'm running i386 and only have one RPM installed:

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386

I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.

Alfred

[Alfred von Campe]

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

No, I'm running i386 and only have one RPM installed:

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386

I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.

Alfred

[Alfred von Campe]

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

No, I'm running i386 and only have one RPM installed:

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386

I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.

Alfred

[Alfred von Campe]

Post by Paul Heinlein
Are you running an x86_64 system? Does "rpm -q subversion" return
two (seemingly identical) entries?

No, I'm running i386 and only have one RPM installed:

$ rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion
subversion-1.6.11.0.1.el5.rf.i386

I think the issue is that CentOS itself comes with subversion V1.4.2
but I have superseded that with subversion V1.6.9 (actually just
updated to 1.6.11 today) from rpmforge. But the apache modules may
be expecting the version of SVN that came with the base OS. That's
my theory anyway.

Alfred

[Alfred von Campe]

On a CentOS 5 system, with the rpmforge as the only external
repository, and the Subversion 1.6.9 RPM from rpmforge installed, I
get the following error when trying to install mod_dav_svn:

# yum install mod_dav_svn
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Updates
Finished
639 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mod_dav_svn.i386 0:1.4.2-4.el5_3.1 set to be updated
--> Processing Dependency: subversion = 1.4.2-4.el5_3.1 for package:
mod_dav_svn
--> Finished Dependency Resolution
mod_dav_svn-1.4.2-4.el5_3.1.i386 from base has depsolving problems
--> Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by
package mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
Error: Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by
package mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest

If I install the RPM with rpm instead of yum, everything works find
in apache, but now yum complains about the missing dependency when
doing a "yum update". The workaround for me for now is to uninstall
the RPM, do a yum update, and then reinstall the RPM. Needless to
say, this is not ideal. Is there anything that can be done to fix
this or am I doing something wrong?

Alfred

[Paul Heinlein]

Post by Alfred von Campe
On a CentOS 5 system, with the rpmforge as the only external
repository, and the Subversion 1.6.9 RPM from rpmforge installed, I
# yum install mod_dav_svn
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Updates
Finished
639 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mod_dav_svn.i386 0:1.4.2-4.el5_3.1 set to be updated
--> mod_dav_svn
--> Finished Dependency Resolution
mod_dav_svn-1.4.2-4.el5_3.1.i386 from base has depsolving problems
--> Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by package
--> mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
Error: Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by package
mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
If I install the RPM with rpm instead of yum, everything works find in
apache, but now yum complains about the missing dependency when doing a "yum
update". The workaround for me for now is to uninstall the RPM, do a yum
update, and then reinstall the RPM. Needless to say, this is not ideal. Is
there anything that can be done to fix this or am I doing something wrong?

Are you running an x86_64 system? Does "rpm -q subversion" return two
(seemingly identical) entries? If so, the trouble is that you've got
i386 and an x86_64 subversion packages installed. Try

rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion

In that case, you can probably just delete the 32-bit version and then
try the update. (I should say, I've had no difficulties removing the
32-bit packages. There may be good reasons for both to be there, but I
don't know what they are.)

[Alfred von Campe]

On a CentOS 5 system, with the rpmforge as the only external
repository, and the Subversion 1.6.9 RPM from rpmforge installed, I
get the following error when trying to install mod_dav_svn:

# yum install mod_dav_svn
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Updates
Finished
639 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mod_dav_svn.i386 0:1.4.2-4.el5_3.1 set to be updated
--> Processing Dependency: subversion = 1.4.2-4.el5_3.1 for package:
mod_dav_svn
--> Finished Dependency Resolution
mod_dav_svn-1.4.2-4.el5_3.1.i386 from base has depsolving problems
--> Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by
package mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
Error: Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by
package mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest

If I install the RPM with rpm instead of yum, everything works find
in apache, but now yum complains about the missing dependency when
doing a "yum update". The workaround for me for now is to uninstall
the RPM, do a yum update, and then reinstall the RPM. Needless to
say, this is not ideal. Is there anything that can be done to fix
this or am I doing something wrong?

Alfred

[Paul Heinlein]

Post by Alfred von Campe
On a CentOS 5 system, with the rpmforge as the only external
repository, and the Subversion 1.6.9 RPM from rpmforge installed, I
# yum install mod_dav_svn
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Updates
Finished
639 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mod_dav_svn.i386 0:1.4.2-4.el5_3.1 set to be updated
--> mod_dav_svn
--> Finished Dependency Resolution
mod_dav_svn-1.4.2-4.el5_3.1.i386 from base has depsolving problems
--> Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by package
--> mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
Error: Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by package
mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
If I install the RPM with rpm instead of yum, everything works find in
apache, but now yum complains about the missing dependency when doing a "yum
update". The workaround for me for now is to uninstall the RPM, do a yum
update, and then reinstall the RPM. Needless to say, this is not ideal. Is
there anything that can be done to fix this or am I doing something wrong?

Are you running an x86_64 system? Does "rpm -q subversion" return two
(seemingly identical) entries? If so, the trouble is that you've got
i386 and an x86_64 subversion packages installed. Try

rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion

In that case, you can probably just delete the 32-bit version and then
try the update. (I should say, I've had no difficulties removing the
32-bit packages. There may be good reasons for both to be there, but I
don't know what they are.)

[Alfred von Campe]

On a CentOS 5 system, with the rpmforge as the only external
repository, and the Subversion 1.6.9 RPM from rpmforge installed, I
get the following error when trying to install mod_dav_svn:

# yum install mod_dav_svn
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Updates
Finished
639 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mod_dav_svn.i386 0:1.4.2-4.el5_3.1 set to be updated
--> Processing Dependency: subversion = 1.4.2-4.el5_3.1 for package:
mod_dav_svn
--> Finished Dependency Resolution
mod_dav_svn-1.4.2-4.el5_3.1.i386 from base has depsolving problems
--> Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by
package mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
Error: Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by
package mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest

If I install the RPM with rpm instead of yum, everything works find
in apache, but now yum complains about the missing dependency when
doing a "yum update". The workaround for me for now is to uninstall
the RPM, do a yum update, and then reinstall the RPM. Needless to
say, this is not ideal. Is there anything that can be done to fix
this or am I doing something wrong?

Alfred

[Paul Heinlein]

Post by Alfred von Campe
On a CentOS 5 system, with the rpmforge as the only external
repository, and the Subversion 1.6.9 RPM from rpmforge installed, I
# yum install mod_dav_svn
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Updates
Finished
639 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mod_dav_svn.i386 0:1.4.2-4.el5_3.1 set to be updated
--> mod_dav_svn
--> Finished Dependency Resolution
mod_dav_svn-1.4.2-4.el5_3.1.i386 from base has depsolving problems
--> Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by package
--> mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
Error: Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by package
mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
If I install the RPM with rpm instead of yum, everything works find in
apache, but now yum complains about the missing dependency when doing a "yum
update". The workaround for me for now is to uninstall the RPM, do a yum
update, and then reinstall the RPM. Needless to say, this is not ideal. Is
there anything that can be done to fix this or am I doing something wrong?

Are you running an x86_64 system? Does "rpm -q subversion" return two
(seemingly identical) entries? If so, the trouble is that you've got
i386 and an x86_64 subversion packages installed. Try

rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion

In that case, you can probably just delete the 32-bit version and then
try the update. (I should say, I've had no difficulties removing the
32-bit packages. There may be good reasons for both to be there, but I
don't know what they are.)

[Alfred von Campe]

On a CentOS 5 system, with the rpmforge as the only external
repository, and the Subversion 1.6.9 RPM from rpmforge installed, I
get the following error when trying to install mod_dav_svn:

# yum install mod_dav_svn
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Updates
Finished
639 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mod_dav_svn.i386 0:1.4.2-4.el5_3.1 set to be updated
--> Processing Dependency: subversion = 1.4.2-4.el5_3.1 for package:
mod_dav_svn
--> Finished Dependency Resolution
mod_dav_svn-1.4.2-4.el5_3.1.i386 from base has depsolving problems
--> Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by
package mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
Error: Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by
package mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest

If I install the RPM with rpm instead of yum, everything works find
in apache, but now yum complains about the missing dependency when
doing a "yum update". The workaround for me for now is to uninstall
the RPM, do a yum update, and then reinstall the RPM. Needless to
say, this is not ideal. Is there anything that can be done to fix
this or am I doing something wrong?

Alfred

[Paul Heinlein]

Post by Alfred von Campe
On a CentOS 5 system, with the rpmforge as the only external
repository, and the Subversion 1.6.9 RPM from rpmforge installed, I
# yum install mod_dav_svn
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
Excluding Packages from CentOS-5 - Base
Finished
Excluding Packages from CentOS-5 - Updates
Finished
639 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mod_dav_svn.i386 0:1.4.2-4.el5_3.1 set to be updated
--> mod_dav_svn
--> Finished Dependency Resolution
mod_dav_svn-1.4.2-4.el5_3.1.i386 from base has depsolving problems
--> Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by package
--> mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
Error: Missing Dependency: subversion = 1.4.2-4.el5_3.1 is needed by package
mod_dav_svn-1.4.2-4.el5_3.1.i386 (base)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
If I install the RPM with rpm instead of yum, everything works find in
apache, but now yum complains about the missing dependency when doing a "yum
update". The workaround for me for now is to uninstall the RPM, do a yum
update, and then reinstall the RPM. Needless to say, this is not ideal. Is
there anything that can be done to fix this or am I doing something wrong?

Are you running an x86_64 system? Does "rpm -q subversion" return two
(seemingly identical) entries? If so, the trouble is that you've got
i386 and an x86_64 subversion packages installed. Try

rpm -q --qf '%{name}-%{version}.%{release}.%{arch}\n' subversion

In that case, you can probably just delete the 32-bit version and then
try the update. (I should say, I've had no difficulties removing the
32-bit packages. There may be good reasons for both to be there, but I
don't know what they are.)