Bug 154627 - FACTORY install tries to install suse/noarch/grub.src.rpm on i586
Summary: FACTORY install tries to install suse/noarch/grub.src.rpm on i586
Status: RESOLVED FIXED
: 154347 154651 (view as bug list)
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: libzypp (show other bugs)
Version: Beta 6
Hardware: Other Other
: P5 - None : Blocker (vote)
Target Milestone: ---
Assignee: Klaus Kämpf
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-02 08:08 UTC by Andreas Jaeger
Modified: 2006-03-02 14:25 UTC (History)
2 users (show)

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

Attachments
yast2 log files (2.50 MB, application/x-bzip2)
2006-03-02 08:09 UTC, Andreas Jaeger 		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 Andreas Jaeger 2006-03-02 08:08:48 UTC 
My installation from FACTORY of a few minutes ago failed since it tried to install
...noarch/grub.src.rpm - NOte: src.rpm instead of i586.rpm and noarch directory instead of i586!
Comment 1 Andreas Jaeger 2006-03-02 08:09:16 UTC 
Created attachment 70921 [details]
yast2 log files
Comment 2 Klaus Kämpf 2006-03-02 08:45:06 UTC 
Hmm, almost all i586 packages exist as .i586.rpm and as .noarch.rpm
Comment 3 Klaus Kämpf 2006-03-02 08:59:59 UTC 
Ah, the noarch packages are the .src.rpm packages, but they should not contribute to the zypp pool.

So its actually two bugs
- yast2-pkg-bindings doesn't choose the 'best' architecture
- zypp pool allows 'SrcPackage' kind of resolvables.
Comment 4 Klaus Kämpf 2006-03-02 09:08:26 UTC 
both fixed in SVN, preparing new packages for stable.
Comment 5 Klaus Kämpf 2006-03-02 11:04:42 UTC 
*** Bug 154347 has been marked as a duplicate of this bug. ***
Comment 6 Klaus Kämpf 2006-03-02 14:24:20 UTC 
submitted to stable.
Comment 7 Klaus Kämpf 2006-03-02 14:25:07 UTC 
*** Bug 154651 has been marked as a duplicate of this bug. ***