|
Bugzilla – Full Text Bug Listing |
| Summary: | Zypper and YaST Online Update refuse to install updates (because of locked package) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Tristan Miller <psychonaut> |
| Component: | libzypp | Assignee: | Stefan Schubert <schubi> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | dmacvicar, meissner, mvidner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
A shell session showing zypper failing to update
/var/log/YaST2/zypper.log A shell session showing zypper failing to update /var/log/YaST2/zypper.log |
||
|
Description
Tristan Miller
2007-01-13 21:15:40 UTC
Created attachment 112882 [details]
A shell session showing zypper failing to update
This is a typescript of a shell session showing zypper (run in double verbose mode) claiming (but failing) to perform updates.
can you also attach /var/log/zypper.log ? one problem is that you do not use "w3m" from suse. I don't see why not using w3m from SuSE would cause this problem. Even if it is causing the rest of the packages not to be installed, there should be an error message to that effect. As it is, the installation reports success when in fact it should be reporting an error. I will attach zypper.log. Created attachment 112884 [details]
/var/log/YaST2/zypper.log
I wish to install the updates because some of them are security-related or fix major or extremely annoying bugs. Is there a workaround I can use to download and install these updates manually? The problem is that libzypp recognizes that you have a non-standard w3m installed and marks it as "locked". Then zypper cannot cope with this lock and fails to perform the update and even pretends success. Please split off a separate report for YOU, with logs (http://en.opensuse.org/Bugs/YaST). To work around it, install an updated w3m manually, using "yast2 -i" or "zypper in" instead of performing the whole update. Or download the updated w3m manually (you probably want the special version from http://ftp-1.gwdg.de/pub/linux/misc/suser-jengelh/SUSE-10.2/i586/ rather than http://ftp.gwdg.de/pub/suse/update/10.2/rpm/i586/ ) and install it with rpm. Please, split the report according to commen #6. Jano is taking over as the primary maintainer of zypper, I am a co-maintainer. Tristan, did you file a report for YOU? If yes, please mention its number here for cross-reference. I assume that you resolved the problem manually as Martin suggested above and have not encountered it since. Or have you found a workaround for similar cases? However, zypper needs at least to report such problem and/or skip the locked package during update. I have filed a YOU report as Bug 253059. Sorry for not doing this sooner, but I've been away from home. Until now I have been resolving the problem manually as suggested in Comment #6. I haven't found any other workaround. As this has been fixed on libzypp level (see bug 253059), zypper should now work, too. Closing this bug without testing, please reopen if needed. I've installed the latest released patch for libzypp (=2.14.2-1.1) and this problem is still occurring. Will attach logs. Created attachment 139562 [details]
A shell session showing zypper failing to update
Created attachment 139563 [details]
/var/log/YaST2/zypper.log
just checked with the following versions on 10.3 aplha1, the problem is fixed there. $ rpm -q zypper libzypp zypper-0.7.1-3 libzypp-3.2.0-3 Schubi, this is in fact a duplicate of bug 191810. Can you please check if the fix has been released through YOU for 10.2, or if libzypp containing the fix is instalable on 10.2 and check with Tristan whether he has the right version installed? Then please close this bug as duplicate of bug 191810. Thanx. Yes it is fixed there too *** This bug has been marked as a duplicate of bug 191810 *** |