Op maandag 28 april 2003 11:41, schreef Lennart Börjeson:
I made exactly that transition last week. After reading several threads here on the same subject I decided to give apt4rpm a try. (Cf. http://linux01.gwdg.de/apt4rpm/). It didn't work as advertised...
First of all, the limited number of sites offering apt repositories for suse don't have the bandwidth to serve an international audience. E.g. I get 200-300 kbytes/s from my nearest suse mirror but only a tenth of that from gwdg, the only apt mirror I could get an answer from.
Lennart, good job. You may have saved yourself a lot of time by using "dist-upgrade" instead of just "upgrade". dist-upgrade decides whether to remove or install new pkgs, while upgrade just won't do that. With "-o rpm::options::=RPM_ARG" you can transfer rpm arguments to rpm. In case of your kde upgrade you could have tested it with: apt-get -o rpm::options::=--test dist-upgrade This command sequence would have told you that some pkgs need to be installed with force (I think this is koffice isn't it?). Which can be tackled by: apt-get -o rpm::options::=--force dist-upgrade The remaining issue is of course the server availability. Hope this helps. -- Richard Bos Without a home the journey is endless