Bug 151954 - YaST System Update tries to install x86_64 packages on i686
Summary: YaST System Update tries to install x86_64 packages on i686
Status: RESOLVED DUPLICATE of bug 151933
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 4
Hardware: i686 SuSE Linux 10.1
: P5 - None : Blocker (vote)
Target Milestone: ---
Assignee: Klaus Kämpf
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-17 20:58 UTC by Forgotten User OS1JNCFbCX
Modified: 2006-02-20 15:45 UTC (History)
1 user (show)

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

Attachments
The logs of a YaST System Update run until it uncovers that it intends to install x86_64 packages (444.48 KB, text/plain)
2006-02-18 12:51 UTC, Forgotten User OS1JNCFbCX 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User OS1JNCFbCX 2006-02-17 20:58:03 UTC 
When running YaST System Update on a i686 system with packages of current factory tree installed it complains that not all dependencies can be resolved automatically. If you then go to manual package selection and do dependency checking you find that it tries to install the x86_64 packages of some packages that are present on the system as i586 packages already.
Comment 1 Christian Boltz 2006-02-17 23:55:45 UTC 
could be related to bug #151933
Comment 2 Andreas Jaeger 2006-02-18 11:37:20 UTC 
Yes, this might be the same bug as 151933 but let's get the log files for this one first ;-).  But this is a "System Update" and not a new installation.

Robert, could you add log files, please?
Comment 3 Forgotten User OS1JNCFbCX 2006-02-18 12:51:37 UTC 
Created attachment 69181 [details]
The logs of a YaST System Update run until it uncovers that it intends to install x86_64 packages
Comment 4 Klaus Kämpf 2006-02-20 15:45:47 UTC 

*** This bug has been marked as a duplicate of 151933 ***