Bug 228145 - YOU doesn't upgrade a previously downgraded package again
Summary: YOU doesn't upgrade a previously downgraded package again
Status: RESOLVED DUPLICATE of bug 191810
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: libzypp (show other bugs)
Version: Final
Hardware: x86 Linux
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Klaus Kämpf
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-13 05:14 UTC by Andreas Hanke
Modified: 2007-01-02 09:09 UTC (History)
0 users

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


Attachments
First part (60.52 KB, image/png)
2006-12-13 05:20 UTC, Andreas Hanke
Details
Second part (63.25 KB, image/png)
2006-12-13 05:22 UTC, Andreas Hanke
Details
y2logs.tar.bz2 (3.26 MB, application/x-bzip)
2006-12-13 05:45 UTC, Andreas Hanke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Hanke 2006-12-13 05:14:42 UTC
There was a security patch for evince that YOU installed successfully. Just for fun, I downgraded evince to the original GM version, and re-ran YOU.

YOU displays both the patch (in the left frame) and the package (in the right frame) with the "will be reinstalled" symbol, but the reinstallation never happens: YOU exists without effectively doing or updating anything.
Comment 1 Andreas Hanke 2006-12-13 05:20:43 UTC
Created attachment 109431 [details]
First part

The installed version is 0.6.1-22, but the available (and, for the patch, required) version is 0.6.1-22.2.

Therefore the patch is broken, and (until here) correctly marked as "will be reinstalled".
Comment 2 Andreas Hanke 2006-12-13 05:22:09 UTC
Created attachment 109432 [details]
Second part

Summary of what YOU then actually did: Pretty much nothing at all(?)
Comment 3 Andreas Hanke 2006-12-13 05:45:46 UTC
Created attachment 109436 [details]
y2logs.tar.bz2
Comment 4 Stefan Schubert 2007-01-02 09:09:59 UTC

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