Bug 113159 - lib conflicts
Summary: lib conflicts
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 3
Hardware: i686 All
: P5 - None : Normal
Target Milestone: ---
Assignee: Adrian Schröter
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-25 20:59 UTC by Jean-Daniel Dodin
Modified: 2005-10-17 09:55 UTC (History)
1 user (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
conflict.txt (2.65 KB, text/plain)
2005-08-25 21:01 UTC, Jean-Daniel Dodin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Daniel Dodin 2005-08-25 20:59:55 UTC
I don't know if this is a bug, but...

I tried to update beta2 to beta3 by the way explained on opensuse, that is
selecting beta3 as ftp source, yast, packages, zzall, right clic, all the
packages newers...

this gave me the conflict list I give in attachement. of course I didn't the
update (I will see with the cds)
hpope this will help you.
Comment 1 Jean-Daniel Dodin 2005-08-25 21:01:08 UTC
Created attachment 47667 [details]
conflict.txt

the yast conflict windows as saved by yast (very good idea, this save option)
Comment 2 Michael Gross 2005-08-29 15:37:26 UTC
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 (...).
Comment 3 Jean-Daniel Dodin 2005-08-29 15:41:50 UTC
It was only an update, so only the files already in place had to be fetched.
Comment 4 Michael Gross 2005-08-30 12:36:24 UTC
Gnome-Maintainers: Please check this. We figure that these dependencies are
valid and were added in beta 3?
Comment 5 JP Rosevear 2005-08-30 13:18:31 UTC
Correct, but in the non OSS version, these conflicts didn't exist.
Comment 6 Rodrigo Moya 2005-08-30 13:39:59 UTC
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.
Comment 7 Jean-Daniel Dodin 2005-08-30 15:37:19 UTC
the update from cd iso's, dod not had any problem :-(
thanks
Comment 8 JP Rosevear 2005-08-31 13:02:29 UTC
What do you mean by "dod"?
Comment 9 Jean-Daniel Dodin 2005-08-31 13:04:26 UTC
sorry, typo :-( read "did". I had no problem at all making an update with the
cd's (nothing related with this page)
Comment 10 JP Rosevear 2005-08-31 13:07:49 UTC
Sounds like the YOU source was out of date, Adrian?
Comment 11 JP Rosevear 2005-08-31 13:59:06 UTC
*** Bug 113506 has been marked as a duplicate of this bug. ***
Comment 12 Adrian Schröter 2005-08-31 14:34:46 UTC
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 ? 
Comment 13 Jean-Daniel Dodin 2005-08-31 15:41:52 UTC
here, #2:

http://www.opensuse.org/index.php/Update_SUSE_to_next_version
Comment 14 Adrian Schröter 2005-10-17 09:55:41 UTC
okay, yast sources ...

it was a temporary build failure it seems. At least the dependencies are solvable on the final version.