Hello, I'm having some issues with urpmi lately. Take a look here:
http://eijk.homelinux.org/build/cooker/urpmi/i586/k3b-0.9-2mdk As you can see 2 packages are basically being installaed by urpmi: kdelibs-devel (fails) and libcdda0-devel (is installed) I can't judge the interals of urpmi (I'm a no-no in perl) but the difference I see with urpmi shipped with 9.1 is that urpmi now splits up the job into smaller bits and tries to install those, seperately. The nice things of the version shipped with 9.1 are: - it does the calculation first; - if something isn't right then it gives the reason why something has failed; - when something is wrong in the calculation it doesn't install any packages. With the current version it goes ahead and tries to install packages anyway, leaving the user with without the package he wanted to install. There is also no clear error message that the package he was trying to install didn't make it, or why it didn't make it. There are some messages (for the individual packages) why they didn't make it, but these often overlap --> because package A failed to install, package B also failed to install. Instead of giving the combined error, which in most cases will be LESS, now the user can go ahead and puzzle what is going on. May I ask what the long term strategy is for urpmi? Are these issues known and being worked on? Is there a possibility to get the 9.1 version back? Why I'm saying this: urpmi isn't helping me (with slbd) at this momment. I'm capable to install kdelibs-devel by hand on a system and the system ends up without any dependency issues, and only with cooker packages. Why can't urpmi do the same? It _used_ to be possible... regards, Stefan PS: this issue isn't limited to kdelibs-devel. The number of packages that can't be installed due to urpmi not being able to install the BuildRequires is increasing, on a daily basis. See: Packages with "missing BuildRequires": http://eijk.homelinux.org/build/cooker/i586/ Urpmi install logs: http://eijk.homelinux.org/build/cooker/urpmi/i586/
