|
Bugzilla – Full Text Bug Listing |
| Summary: | zypp does not update installed/uninstalled after commit() | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Andreas Hanke <andreas.hanke> |
| Component: | libzypp | Assignee: | Duncan Mac-Vicar <dmacvicar> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | aj, lslezak, ma, suse-beta |
| Version: | Alpha 3 plus | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | YaST2 logfiles | ||
|
Description
Andreas Hanke
2006-08-27 04:50:10 UTC
Created attachment 97235 [details]
YaST2 logfiles
libzypp problem There is code in libzypp which re-generates the installed/uninstalled status after each transaction. So this looks more like a UI-ZYPP API bug. reassign to zypp bugzilla maintainer. Ladislav, either package-bindings or not re-initialization in the package workflow ? I think that the bug is in zypp, the pool is not refreshed after commit(). When I add this sequence into sw_single it works correctly: Pkg::TargetFinish(); Pkg::TargetInitialize(Installation::destdir); Pkg::TargetLoad(); But that's ugly, it should be fixed either in bindings or in zypp. Is it required to explicitly call the code mentioned in comment #3? (How?) *** Bug 206955 has been marked as a duplicate of this bug. *** *** Bug 201121 has been marked as a duplicate of this bug. *** JFY: I added the workaround from comment #5 to yast2-packager-2.13.151 Raising severity - the bug significantly affects package related actions done in yast *** This bug has been marked as a duplicate of bug 213777 *** |