Bug 156901 - YaST does not detect unsatisfied dependencies
Summary: YaST does not detect unsatisfied dependencies
Status: RESOLVED DUPLICATE of bug 156439
: 157448 (view as bug list)
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 7
Hardware: i686 SuSE Linux 10.1
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Stefan Schubert
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-10 02:30 UTC by Forgotten User OS1JNCFbCX
Modified: 2006-03-14 14:10 UTC (History)
2 users (show)

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


Attachments
YaST logs (628.73 KB, application/x-compressed-tar)
2006-03-10 02:31 UTC, Forgotten User OS1JNCFbCX
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User OS1JNCFbCX 2006-03-10 02:30:00 UTC
When running YaST System Update with YaST packages from the latest factory tree, it did not detect that dependencies of some installed kmp packages could no longer be resolved when the kernel is updated. It did just force installation of the kernel resulting in:

# rpm -Va --nofiles
Unsatisfied dependencies for openafs-kmp-default-1.4.0_2.6.16_rc5_git2_2-9.i586: kernel(kernel) = 8366da779b4b1b1f, kernel(fs) = ebe97a168f879e76, kernel(vmlinux) = da1486218060ebca, kernel(mm) = a483339a74333448, kernel(net) = 848129716908355f, kernel(arch_i386_kernel) = 50708dd49c8f4551, kernel(fs_proc) = 300834be12a87133, kernel(security) = f2084e121bcfab7a, kernel(arch_i386_mm) = be92bd9e0060357e
Unsatisfied dependencies for madwifi-kmp-default-1451_2.6.16_rc5_git2_2-4.i586: kernel(kernel) = 8366da779b4b1b1f, kernel(drivers) = eea9a06738a66c70, kernel(drivers_pci) = b37d6a4ccbebdec1, kernel(net) = 848129716908355f, kernel(net_core) = c30bf0259f3f624a, kernel(vmlinux) = da1486218060ebca, kernel(mm) = a483339a74333448, kernel(fs) = ebe97a168f879e76, kernel(fs_proc) = 300834be12a87133, kernel(net_sched) = 45cf968d7d4f2ed2, kernel(arch_i386_kernel) = 50708dd49c8f4551, kernel(crypto) = 1c6e578c4ae3d7ec, kernel(net_ethernet) = 9f80304049f5c0e9, kernel(drivers_char) = 4f336e0c54d3a659, kernel(security) = f2084e121bcfab7a, kernel(arch_i386_mm) = be92bd9e0060357e
#
Comment 1 Forgotten User OS1JNCFbCX 2006-03-10 02:31:05 UTC
Created attachment 72137 [details]
YaST logs
Comment 2 Forgotten User OS1JNCFbCX 2006-03-12 10:59:46 UTC
This does happen for _any_ package that breaks dependencies due to an upgrade. All unsatisfied depdendencies that result from an upgrade are simply ignored. It seems that YaST does not take into account that some provides will vanish due to the upgrade of a package.
Comment 3 Michael Gross 2006-03-13 10:52:47 UTC
*** Bug 157448 has been marked as a duplicate of this bug. ***
Comment 4 Michael Gross 2006-03-13 10:53:17 UTC
This is a problem with the resolver I guess.
Comment 5 Stefan Schubert 2006-03-14 14:10:33 UTC
Should be the same.

*** This bug has been marked as a duplicate of 156439 ***