Bug 483179

Summary: 'zypper up foo' does not allow noarch->anyarch nor anyarch->noarch updates, lu does
Product: [openSUSE] openSUSE 11.1 Reporter: Markus Elfring <Markus.Elfring>
Component: libzyppAssignee: Jan Kupec <jkupec>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P2 - High    
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 483910    
Attachments: solver test case
detailed log

Description Markus Elfring 2009-03-07 14:11:16 UTC 
Created attachment 277858 [details]
solver test case

I get the following informations from the command line interface.

Sonne:~ # zypper update -t package --debug-solver xml-commons-resolver xerces-j2 wxGTK-doc monsoon libpcap* liblzo2-2-32bit
Loading repository data...
Reading installed packages...
No update candidate for 'wxGTK-doc'.
No update candidate for 'monsoon'.
No update candidate for 'libpcap'.
Package 'liblzo2-2-32bit' is not installed.
Resolving package dependencies...
Generating solver test case...
Solver test case generated successfully at /var/log/zypper.solverTestCase.
Sonne:~ # zypper list-updates
Loading repository data...
Reading installed packages...
S | Repository                                   | Name                  | Version                  | Arch
--+----------------------------------------------+-----------------------+--------------------------+-------
v | Haupt-Repository (Open Source Software) 11.1 | bundle-lang-common-ar | 11.1-11.2                | noarch
v | Haupt-Repository (Open Source Software) 11.1 | bundle-lang-common-ca | 11.1-11.2                | noarch
v | KDE Rückportierungen 11.1                    | kdbus                 | 0.8.6_SVN_20070413-187.4 | x86_64
v | KDE 4-Kern                                   | kio_iso               | 1.99.2.beta2-4.11        | x86_64
v | KDE Rückportierungen 11.1                    | kradio                | 1.0beta3b_20060920-226.4 | x86_64
v | KDE 4-Kern                                   | krusader              | 1.99.2.beta2-4.11        | x86_64
v | Haupt-Repository (Open Source Software) 11.1 | libedit0              | 2.11.snap20080712-1.39   | x86_64
v | openSUSE BuildService - Spiele               | liblzma0              | 4.999.8beta-5.1          | x86_64
v | Haupt-Repository (Open Source Software) 11.1 | liblzo2-2-32bit       | 2.03-2.29                | x86_64
v | Haupt-Repository (Open Source Software) 11.1 | libpcap0              | 0.9.8-47.41              | x86_64
v | Richard Bos 11.1                             | libpcap1              | 1.0.0-4.1                | x86_64
v | GNOME-Gemeinschaft                           | monsoon               | 0.20-1.1                 | x86_64
v | Virtualisierung - Qemu 11.1                  | qemu                  | 0.9.2svn20081008-2.5     | x86_64
v | Haupt-Repository (Open Source Software) 11.1 | wxGTK-doc             | 2.8.8.1-1.6              | x86_64
v | openSUSE BuildService - Java                 | xerces-j2             | 2.8.1-239.10             | noarch
v | openSUSE BuildService - Java                 | xml-commons-resolver  | 1.1-238.10               | noarch
v | openSUSE BuildService - Spiele               | xz                    | 4.999.8beta-5.1          | x86_64
v | openSUSE BuildService - Spiele               | xz-devel              | 4.999.8beta-5.1          | x86_64

It seems that my observation fits to a recent comment by Lars Müller.
https://bugzilla.novell.com/show_bug.cgi?id=480303#c5

Should "spurious" update notifications be avoided?
Comment 1 Jan Kupec 2009-03-09 11:21:22 UTC 
Ouch, this is a bug in zypper. It should have found the 'wxGTK-doc' and the others.

BTW, '-t package' is no longer needed.
Comment 3 Jan Kupec 2009-03-09 13:39:21 UTC 
Could you please attach also zypper.log? Do

$ ZYPP_FULLLOG=1 ZYPP_LOGFILE=the.log zypper update xml-commons-resolver xerces-j2 wxGTK-doc monsoon libpcap* liblzo2-2-32bit

Reply 'n' in the 'Continue?' prompt, and attach the.log. Thanx!
Comment 4 Markus Elfring 2009-03-09 18:14:48 UTC 
Created attachment 278182 [details]
detailed log

Does this file show the error sources?
Comment 5 Jan Kupec 2009-03-10 13:52:29 UTC 
Yes, thanx! There are two problems:

1) According to the log, liblzo2-2-32bit is really not installed, so doUpate()
   should not pick it (that's why zypper shows it in 'zypper lu'). I'll clone this
   bug so that Schubi can look at it.

2) Zypper has chosen wrong wxGTK-doc (among others) to update. I'm still don't
   know why, i'll look further.
Comment 6 Jan Kupec 2009-03-10 14:55:57 UTC 
(In reply to comment #0)
> It seems that my observation fits to a recent comment by Lars Müller.
> https://bugzilla.novell.com/show_bug.cgi?id=480303#c5

JFYI, that's a different problem - the kernel _patch_ not rendered satisfied, while it should.
Comment 7 Jan Kupec 2009-03-10 15:10:09 UTC 
Got it, the installed wxGTK-doc is noarch, but the newer one is .x86_64. Zypper was looking for a noarch update.
Comment 8 Jan Kupec 2009-03-10 15:33:01 UTC 
Michael, are updates from noarch->specific-arch allowed? Which arch changes are allowed when in updatesystem=1 mode?
Comment 9 Michael Schröder 2009-03-10 16:08:25 UTC 
(This has nothing to do with updatesystem)

libsatsolver treats "noarch" as wildcard arch, so specific_arch->noarch or noarch -> specific_arch is both allowed.
Comment 10 Jan Kupec 2009-03-10 18:19:40 UTC 
OK, thanx. Fixed in git, to be in zypper 1.1.0 (newer release than the one in factory right now).
Comment 11 Jan Kupec 2009-03-10 18:59:45 UTC 
submitted