Modify

Ticket #692 (closed defect: wontfix)

Opened 12 years ago

Last modified 11 years ago

APT client tool not purging packages properly

Reported by: solj Owned by: dclark
Priority: minor Milestone: Bcfg2 1.2.0 Release
Component: bcfg2-client Version: 1.0
Keywords: Cc: solj@…

Description

I think this may be an issue with python-apt, but the Purging mechanism is not working properly. Configuration files are being left behind.

Attachments

Change History

comment:1 Changed 12 years ago by solj

  • Cc solj@… added

comment:2 Changed 12 years ago by solj

  • Status changed from new to accepted

comment:3 Changed 12 years ago by solj

  • Milestone changed from Bcfg2 1.0 Release to Bcfg2 1.0.1 Release

comment:4 Changed 12 years ago by solj

  • Milestone changed from Bcfg2 1.0.1 Release to Bcfg2 1.1.0 Release

comment:5 Changed 12 years ago by solj

  • Status changed from accepted to closed
  • Resolution set to worksforme

Indeed, this was a problem with python-apt. This appears to be working properly in Lucid.

comment:6 follow-up: ↓ 8 Changed 12 years ago by dclark

  • Status changed from closed to reopened
  • Resolution worksforme deleted

lucid has python-apt 0.7.13.4ubuntu1 - what version of ubuntu did this fail with? Perhaps we should make backported python-apt 0.7.13.4 packages available under debian and ubuntu.

comment:7 Changed 12 years ago by dclark

  • Owner changed from solj to dclark
  • Status changed from reopened to accepted

comment:8 in reply to: ↑ 6 Changed 12 years ago by solj

Replying to dclark:

lucid has python-apt 0.7.13.4ubuntu1 - what version of ubuntu did this fail with? Perhaps we should make backported python-apt 0.7.13.4 packages available under debian and ubuntu.

For sure it was not working in hardy. I'm not sure it is a huge deal to backport anything though. The packages are removed, they are just not purged.

comment:9 Changed 12 years ago by solj

  • Milestone changed from Bcfg2 1.1.0 Release to Bcfg2 1.2.0 Release

comment:10 Changed 11 years ago by solj

  • Status changed from accepted to closed
  • Resolution set to wontfix

Closing this as I'm not sure anyone has the time (or need) to backport this to hardy. It appears to be a non-issue now that the APT api is working properly.

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.