On Tue, Sep 02, 2008 at 04:35:06PM +0200, Michael Schroeder wrote:
On Tue, Sep 02, 2008 at 04:29:41PM +0200, Peter Poeml wrote:
On Mon, Sep 01, 2008 at 02:10:20PM +0200, Michael Schroeder wrote:
On Mon, Sep 01, 2008 at 02:06:07PM +0200, Peter Poeml wrote:
On Mon, Sep 01, 2008 at 02:03:39PM +0200, Michael Schroeder wrote:
On Mon, Sep 01, 2008 at 02:00:49PM +0200, Peter Poeml wrote:
This puzzles me, how does zypper deal with this?
Yum also doesn't do file conflicts, as the information needed for this is not present in the rpm-md metadata.
It does - it always runs a test transaction before changing the system, which reliably detects them.
Yeah, but this is after solving and downloading, which is way to late.
It's late, but not *too* late. It works. And I need to download the packages anyway, once the conflict is resolved.
How do you resolve the conflict?
There can be no single answer to this. That depends on the conflict. Possible resolutions range from - deciding for one of the conflicting packages, - deinstalling something that conflicts, - updating a package that should be updated but isn't, so far (maybe from elsewhere), - fixing my installation sources if they don't fit together somehow, - simply forcing the install when I know the conflict is harmless or I am willing to enforce it to fixing the broken package upstream, or reporting a bug. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development