Modify ↓
Ticket #675 (closed defect: fixed)
APT.FindExtra() not properly updated after package removal
Reported by: | solj | Owned by: | solj |
---|---|---|---|
Priority: | major | Milestone: | Bcfg2 1.0.0 Release |
Component: | bcfg2-client | Version: | 1.0 |
Keywords: | Cc: |
Description
During a client run, after removing an unmanaged entry (with -r), the entry still shows as unmanaged at the end of the run despite the fact that FindExtra? is called after the package removal.
Attachments
Change History
comment:1 Changed 14 years ago by solj
- Owner changed from desai to solj
- Status changed from new to assigned
comment:2 in reply to: ↑ description Changed 14 years ago by anonymous
- Priority changed from minor to major
Replying to solj:
During a client run, after removing an unmanaged entry (with -r), the entry still shows as unmanaged at the end of the run despite the fact that FindExtra? is called after the package removal.
Scratch that. I think this is just one case of a larger overall problem. It appears that anything involving updates to the cache object is not working during a single client run (i.e. bcfg2 -k).
comment:3 Changed 14 years ago by desai
- Status changed from assigned to closed
- Resolution set to fixed
This is now fixed as of [8b76968c2b22e5df0fd7ed7c86379f32ac5d595d] (SVN r5278)
Note: See
TracTickets for help on using
tickets.