Bug 156454 - After Update from 10.0 a few packages are not updated
Summary: After Update from 10.0 a few packages are not updated
Status: RESOLVED FIXED
: 162524 (view as bug list)
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Update Problems (show other bugs)
Version: Beta 7
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-09 13:50 UTC by Andreas Jaeger
Modified: 2006-04-07 18:08 UTC (History)
2 users (show)

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


Attachments
yast2 log files (1.52 MB, application/x-bzip2)
2006-03-09 13:53 UTC, Andreas Jaeger
Details
YaST2.tar.bz2 (594.53 KB, application/x-bzip2)
2006-04-07 16:10 UTC, Christoph Thiel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Jaeger 2006-03-09 13:50:48 UTC
rpm -qa  --qf='%{NAME} %{BUILDTIME:date}\n'  |grep 2005
gpg-pubkey Wed 09 Mar 2005 01:43:33 PM CET
gpg-pubkey Tue 09 Aug 2005 08:26:39 AM CEST
gnome-icon-theme Fri 09 Sep 2005 09:06:17 PM CEST
gpg-pubkey Wed 09 Mar 2005 01:43:34 PM CET
gecko-sharp Tue 13 Sep 2005 06:21:12 AM CEST
Comment 1 Andreas Jaeger 2006-03-09 13:53:48 UTC
Created attachment 71982 [details]
yast2 log files
Comment 2 Klaus Kämpf 2006-03-09 17:50:13 UTC
gpg-pubkey is filtered out and not considered for update or removal.
-> Michaels (both ;-) ), how to handle this ?
Comment 3 Klaus Kämpf 2006-03-09 18:08:42 UTC
Hmm,
DoProvideNameKind gnome-icon-theme -> Bad

Looks like this package cannot be found after starting 2nd stage of installation.

Same is true for gecko-sharp.

I probably have to login to the system in question.
Comment 5 Klaus Kämpf 2006-03-10 07:16:55 UTC
Hmm, ftp://10.10.0.100/install/SLP/SUSE-10.1-Beta7/x86_64/CD1 is disabled, factory and factory-e sources are enabled.
From where did you update ?
Adding Stano to CC
Comment 6 Andreas Jaeger 2006-03-10 07:38:19 UTC
I updated from 10.1 Beta7 and afterwards added factory, factory-e, disabled
10.1 - and installed some more packages.
Comment 7 Andreas Jaeger 2006-04-05 19:23:40 UTC
Christoph, can you check an update whether this is fixed?
Comment 8 Christoph Thiel 2006-04-05 20:46:06 UTC
Just checked the box that I updated from 10.0 to 10.1 build 905 today, and found one package that wasn't updated. Logs are attached to bug #163829.
Comment 9 Christoph Thiel 2006-04-05 20:47:22 UTC
$ rpm -qa --last
[...]
aaa_skel-2006.3.29-2                          Mi 05 Apr 2006 15:50:26 CEST
Crystalcursors-0.5-34                         Mi 05 Apr 2006 15:50:25 CEST
[^updated packages]
[not updated packages:]
gnome-mime-data-2.4.2-7                       Di 04 Apr 2006 18:03:30 CEST
manufacturer-PPDs-0.4-13                      Di 04 Apr 2006 18:01:59 CEST
gnome-icon-theme-2.12.0-3                     Di 04 Apr 2006 18:01:49 CEST
gpg-pubkey-9c800aca-40d8063e                  Di 04 Apr 2006 18:01:36 CEST
gpg-pubkey-3d25d3d9-36e12d04                  Di 04 Apr 2006 18:01:36 CEST
gpg-pubkey-15c17deb-3f9e80c9                  Di 04 Apr 2006 18:01:36 CEST
gpg-pubkey-0dfb3188-41ed929b                  Di 04 Apr 2006 18:01:36 CEST
$
Comment 10 Andreas Jaeger 2006-04-06 13:45:58 UTC
*** Bug 162524 has been marked as a duplicate of this bug. ***
Comment 12 Christoph Thiel 2006-04-07 10:31:48 UTC
Klaus, I just did a test update from 10.0 to 10.1 Build 906 and found all packages updated. Seems like you guys fixed the bug, when packages that changed the architecture from 10.0 to 10.1 (like gnome-icon-theme and the other packages in quetsion did) didn't get updated.
Comment 13 Christoph Thiel 2006-04-07 11:36:39 UTC
Sorry, we did a DVD installation instead of a CD one that should have triggered this bug.
Comment 14 Christoph Thiel 2006-04-07 16:09:38 UTC
Tested again with Build 907, CD update, and didn't run into this bug again. I'll attach YaST2 logs, but propose to close this bugs FIXED, until we hit it again.
Comment 15 Christoph Thiel 2006-04-07 16:10:41 UTC
Created attachment 77275 [details]
YaST2.tar.bz2
Comment 16 Klaus Kämpf 2006-04-07 18:08:20 UTC
Closing as fixed for now.

We had this error (DoProvideNameKind returning 'Bad') a couple of times in the past. Current yast2-pkg-bindings has extended debug in case it reappears again.