 |
 |
So I have to ask - did you guys do 'apt-get dist-upgrade'? I'm assuming you did. This will be tied up with the fact that all the rgma rpms were renamed, edg-rgma-* -> glite-rgma-*. The new rpms do have the right 'obsoletes' information though, which is why I would expect dist-upgrade to work. In the case of 'broken packages' messages, it's really helpful if you can do an 'apt-get install' on that particular package to give us more info on the conflict. Oliver Keeble Information Technology Department [log in to unmask] CERN +41 22 76 72360 CH-1211 Geneva 23 Fabien Wernli wrote: > On Fri, Aug 19, 2005 at 10:27:10AM +0200, Sergio Fantinel wrote: > >>to resolve the problem: >>rpm -e edg-rgma-api-java-4.0.2-1 edg-rgma-gin-4.0.6-1 >>edg-rgma-api-perl-4.0.2-1 edg-rgma-api-cpp-4.0.7-1 edg-rgma-api-c-4.0.3-1 >>edg-rgma-api-python-4.0.6-1 edg-rgma-command-line-4.0.6-1 >>edg-rgma-stubs-servlet-java-4.0.6-1 edg-rgma-log4j-4.0.3-1 >>edg-rgma-system-tests-4.0.5-1 edg-rgma-base edg-rgma-apel-3.4.45-1 >>edg-rgma-log4cpp-4.0.2-0 > > > We had the same issue when upgrading from 2_4_0 to 2_5_0