In fact I have detected plenty of similar problems with packages apparently coming from the same source, more specifically for the following pairs of packages:
libhdf5-lam-1.8.3 libhdf5-lam-1.8.4 libhdf5-lam-1.8.3 libhdf5-mpich-1.8.4 libhdf5-lam-1.8.3 libhdf5-openmpi-1.8.4 libhdf5-lam-1.8.3 libhdf5-serial-1.8.4 libhdf5-lam-1.8.4 libhdf5-mpich-1.8.3 libhdf5-lam-1.8.4 libhdf5-openmpi-1.8.3 libhdf5-lam-1.8.4 libhdf5-serial-1.8.3 libhdf5-mpich-1.8.3 libhdf5-mpich-1.8.4 libhdf5-mpich-1.8.3 libhdf5-openmpi-1.8.4 libhdf5-mpich-1.8.3 libhdf5-serial-1.8.4 libhdf5-mpich-1.8.4 libhdf5-openmpi-1.8.3 libhdf5-mpich-1.8.4 libhdf5-serial-1.8.3 libhdf5-openmpi-1.8.3 libhdf5-openmpi-1.8.4 libhdf5-openmpi-1.8.3 libhdf5-serial-1.8.4 libhdf5-openmpi-1.8.4 libhdf5-serial-1.8.3 libhdf5-serial-1.8.3 libhdf5-serial-1.8.4 If you need detailed installation logs and conflict file lists for these other pairs of packages please let me know. -Ralf. _______________________________________________ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
