Bugzilla – Bug 174740
applying opera patch with zen-updater fails
Last modified: 2006-06-09 15:47:50 UTC
I tried to just apply the opera patch with zen-updater but got the following exception: Novell.Zenworks.Zmd.Public.ZenException: Failed to lookup resolvable with id '75716' Server stack trace: in <0x0019f> Novell.Zenworks.Zmd.Packaging.RedCarpetBackend+SqlTransaction:GetResult () in <0x000a3> Novell.Zenworks.Zmd.Packaging.RedCarpetBackend:ResolveDependencies (Novell.Zenworks.Zmd.Packaging.IResolvable[] installs, Novell.Zenworks.Zmd.Packaging.IResolvable[] upgrades, Novell.Zenworks.Zmd.Packaging.IResolvable[] removals) in <0x00042> Novell.Zenworks.Zmd.Packaging.PackageManager:Resolve (Novell.Zenworks.Zmd.Packaging.IResolvable[] installs, Novell.Zenworks.Zmd.Packaging.IResolvable[] upgrades, Novell.Zenworks.Zmd.Packaging.IResolvable[] removals) in <0x0005b> Novell.Zenworks.Zmd.Packaging.RemotePackageManager:ResolveDependencies (Novell.Zenworks.Zmd.Packaging.Public.ResolvableInfo[] installs, Novell.Zenworks.Zmd.Packaging.Public.ResolvableInfo[] upgrades, Novell.Zenworks.Zmd.Packaging.Public.ResolvableInfo[] removals) in <0x00000> <unknown method> in (wrapper managed-to-native) System.Runtime.Remoting.RemotingServices:InternalExecute (System.Reflection.MethodBase,object,object[],object[]&) in <0x00265> System.Runtime.Remoting.RemotingServices:InternalExecuteMessage (System.MarshalByRefObject target, IMethodCallMessage reqMsg) Exception rethrown at [0]: in <0x00a63> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception exc, System.Object[] out_args)
Created attachment 82918 [details] zmd-messages
Created attachment 82919 [details] zmd-backend.log
same problem with rug: root:/var/log # rug in -t patch opera Resolving Dependencies... ERROR: Failed to lookup resolvable with id '75716'
Where is this patch ?
/mounts/mirror/SuSE/ftp.suse.com/pub/suse/update/10.1/repodata/ patch-opera-1313.xml
I just installed this patch using "rug in -t patch opera" without problems.
The zmd-backend.log attached at comment #2 shows a successful solver run, selecting the upgraded opera x86_64 package.
After downgrading opera I am able to reproduce this bug
I get ERROR: Failed to lookup resolvable with id '57551' The resolvable in question is of kind "atom" and internally used inside zypp. select id,kind from resolvables where name='opera'; 57549|3 51101|0 57547|0 57550|0 57551|8 57549 is the patch, 51101 the installed package, 57547 the .i586 upgrade packages, 57550 the x86_64 upgrade package, and 57551 the atom (link between patch and package) The error message comes from zmd, I don't see it in zmd-backend.log
The exeception is coming from ZMD zmd/modules/linux/RedCarpetBackend.cs, line 1010 where it reads all transactions and calls GetResolvableById() for each id mentioned in the transactions table. However, GetResolvableById() does not look at the resolvables table (where all resolvables are listed) but (in turn) at packages, patch, nessage, and script. It does NOT look at patterns or products nor does it fall-back to the resolvables table.
*** Bug 174595 has been marked as a duplicate of this bug. ***
I'll add patterns and products to the GetResolvableById(), but I'm not sure what to do with atoms. As you say, atoms are only internal zypp objects, and there's no class zmd can create for them. Even if it could, what would it show in rug and zen-*? "unknown"? Who whould install an "unknown" thing to their machine?
Committed the pattern and product lookup (Committed revision 28224.).
*** Bug 173660 has been marked as a duplicate of this bug. ***
Re-assigning to Tambet and resolving as fixed.
Resolved. See Comment #14.
If the reading of transactions is for display purposes only, the atoms can be safely skipped.
Re-opening and asking Klaus whether this is fully resolved?
It's not fixed. About comment #18, zdm clears the transactions table before the actual transaction and adds required entries in. There are multiple reasons to do so, mostly because of concurrent user support.
What needs to be done is to create a dummy class implementing IResolvable which gets taken from the transactions table, passed to rug/zen-* (which ignores it for the output), and passes it back to zmd for the transaction. Assigning to Chris. (Thanks Naresh, Chris)
What is the status here? Is this a problem for SLE10, too?
This fixed in revision 28426. zmd, rug, and zen-* silently handle atoms.
*** Bug 177540 has been marked as a duplicate of this bug. ***
*** Bug 177589 has been marked as a duplicate of this bug. ***
*** Bug 177594 has been marked as a duplicate of this bug. ***
*** Bug 177634 has been marked as a duplicate of this bug. ***
*** Bug 177482 has been marked as a duplicate of this bug. ***
*** Bug 177875 has been marked as a duplicate of this bug. ***
*** Bug 178881 has been marked as a duplicate of this bug. ***
Where do we get a patch/fix/workaround ... anyone?
we have one in testing. temporarily add this update source: ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/ and insdtall the patches in there.
*** Bug 179414 has been marked as a duplicate of this bug. ***
I have added to YaST sources on my 10.1 x86_64: ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/ I see 3 updates (msttfonts, flash-player, Update of the update stack.) Selecting all or only zmd, YaST2 online_update silently quits. zen-updater applet shows 8 available updates, but zmd is not in the list of available updates (but it shows 10.1-packagemanagement-update-test in the configuration).
*** Bug 179744 has been marked as a duplicate of this bug. ***
After applying the patches, if I unselect some catalog in the Configure -> Catalogs tab, Zen seems not to save the setting because all catalogs are selected again after a logout or reboot.
*** Bug 180990 has been marked as a duplicate of this bug. ***
*** Bug 181086 has been marked as a duplicate of this bug. ***
*** Bug 181276 has been marked as a duplicate of this bug. ***
*** Bug 181890 has been marked as a duplicate of this bug. ***
Updates for this problem have been released today. Please install them with YaST Online Update, then restart zen-updater. afterwards zen-updater will work correctly.
*** Bug 183321 has been marked as a duplicate of this bug. ***