Hi,
If a package changes name the packager should tell rpm (and by extension zypper) about it by using a tag such as obsoletes:
In your case, the package was called -unstable which probably means it was intended to be installed in parallel with the normal one
If there is a bug here, it is that zypper installed the new package with --force, which IMHO is wrong, it shouldn't just overwrite files, it should refuse to install the new package until the collisions have been removed
zypper (and YaST2, even long before zypp existed) has always worked that way: It doesn't install packages in a single transaction, but one by one and therefore *must* use --force (or, more precisely, --replacefiles, which is implied by --force) because otherwise, it wouldn't be able to handle the case where a file is moved from one package to another. The only way to avoid --force (or --replacefiles) is to change zypp so that it installs packages in a single rpm transaction. I *suspect* that there must be a very good reason for not doing so because the solution is just so obvious. The conclusion is that packagers must take extra care to add "Conflicts" tags to their packages if there is indeed a conflict (note that the "Conflicts" does not, despite its ill fame, introduce any conflicts; if used correctly, it just makes the package manager aware of them). A "Conflicts" can later become an "Obsoletes" once there are no conflicts anymore (e.g. after all conflicting packages except one have been dropped). It seems that this was not done in this case. Andreas -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org