|
Bugzilla – Full Text Bug Listing |
| Summary: | lib conflicts | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Jean-Daniel Dodin <jdd> |
| Component: | YaST2 | Assignee: | Adrian Schröter <adrian.schroeter> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | stefan.bruens |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | conflict.txt | ||
|
Description
Jean-Daniel Dodin
2005-08-25 20:59:55 UTC
Created attachment 47667 [details]
conflict.txt
the yast conflict windows as saved by yast (very good idea, this save option)
We are currently checking the zzz_all package conflicts about their validity. Of course, not ALL packages can be installed simultaneously due to directory or file conflicts (...). It was only an update, so only the files already in place had to be fetched. Gnome-Maintainers: Please check this. We figure that these dependencies are valid and were added in beta 3? Correct, but in the non OSS version, these conflicts didn't exist. As a temporary solution: $ rug install -d cairo (or whatever command you use to download packages, tell it to just download the RPM) $ rpm ivh cairo-0.9.xxx.rpm That way, it will install the new version without removing the old one, and will allow you to update. the update from cd iso's, dod not had any problem :-( thanks What do you mean by "dod"? sorry, typo :-( read "did". I had no problem at all making an update with the cd's (nothing related with this page) Sounds like the YOU source was out of date, Adrian? *** Bug 113506 has been marked as a duplicate of this bug. *** Which YOU source ? You speak about the yast sources, right ? The recommended way is not to click on all packages, but to use the YaST System Update functionality. Where did you red this wrong advice ? okay, yast sources ... it was a temporary build failure it seems. At least the dependencies are solvable on the final version. |