|
Bugzilla – Full Text Bug Listing |
| Summary: | zypper dup first installs package for wrong arch, then fixes arch in next zypper dup run | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | Christian Boltz <suse-beta> |
| Component: | libzypp | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | zypper.log.bz2 | ||
|
Description
Christian Boltz
2011-02-14 19:46:55 UTC
Created attachment 413923 [details]
zypper.log.bz2
The 1st dup probably just looks for a replacemant of the installed evolution-data-server-32bit, chosing the .i586 (-32bit!). Maybe the solver does not see that nothing actually requires a 32-bit package, and that's why the 2nd dup may perfrom the arch upgrade to x86_64. Michael? -- There's not much the 2nd dup does. BTW why has the factory-oss product:openSUSE no release number? Install summary: <install> U_Ts_(13885)product:openSUSE-11.4.x86_64(factory-oss) <install> U_Ts_(24143)evolution-data-server-2.32.1-2.4.x86_64(factory-oss) <install> U_Ts_(28042)openSUSE-release-11.4-1.38.x86_64(factory-oss) <uninstall> I_TsU(35637)evolution-data-server-2.32.1-2.4.i586(@System) <uninstall> I_TsU(37091)openSUSE-release-11.4-1.38.x86_64(@System) <uninstall> I_TsU(37853)product:openSUSE-11.4-1.38.x86_64(@System) Looks like the new "evolution-data-server-32bit" package is not installable. But some other package requires the 32bit library, so it proposes to install the i586 package instead (which contains the lib). Later on, the package requiring the lib seems to be gone, so it changes the arch to the better x86_64. To bad that you don't have a solver testcase. Regarding "zypper shouldn't propose...", that's exactly why it is asking for confirmation. . |