Project

General

Profile

Actions

Bug #3145

closed

directory '/opt' not empty so not removed.

Added by Francois BAYART almost 12 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Packaging
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I'm removing rudder-agent on some servers, and I get this message with "dpkg --purge rudder-agent":

 dpkg --purge rudder-agent
(Reading database ... 21158 files and directories currently installed.)
Removing rudder-agent ...
Purging configuration files for rudder-agent ...
dpkg: warning: while removing rudder-agent, directory '/opt/rudder/etc' not empty so not removed.
dpkg: warning: while removing rudder-agent, directory '/opt/rudder' not empty so not removed.
dpkg: warning: while removing rudder-agent, directory '/opt' not empty so not removed.
dpkg: warning: while removing rudder-agent, directory '/var/rudder/cfengine-community/bin' not empty so not removed.
dpkg: warning: while removing rudder-agent, directory '/var/rudder/cfengine-community/inputs' not empty so not removed.
dpkg: warning: while removing rudder-agent, directory '/var/rudder/cfengine-community' not empty so not removed.
dpkg: warning: while removing rudder-agent, directory '/var/rudder/tmp' not empty so not removed.
dpkg: warning: while removing rudder-agent, directory '/var/rudder' not empty so not removed.

I think "/opt" should not be removed by rudder, empty or not.


Related issues 2 (1 open1 closed)

Related to Rudder - User story #2732: Be able to remove and reinstall a serverNewActions
Related to Rudder - Bug #1645: after purge of rudder-agent package, some files not removed + new version of promises.cf not applied on package upgradeRejectedMatthieu CERDA2011-08-24Actions
Actions #1

Updated by Nicolas PERRON over 11 years ago

  • Target version set to 2.4.5
Actions #2

Updated by Jonathan CLARKE over 11 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions #3

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.5 to 2.4.6
Actions #4

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.6 to 2.4.7
Actions #5

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.7 to 2.4.8
Actions #6

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.8 to 2.4.9
Actions #7

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.9 to 2.4.10
Actions #8

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.10 to 2.4.11
Actions #9

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.11 to 2.4.12
Actions #10

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.12 to 2.4.13
Actions #11

Updated by Jonathan CLARKE almost 11 years ago

  • Status changed from New to Rejected

I just checked our Debian packages, and none of them claim to own /opt:

$ find . -name dirs -exec grep -Hn "opt$" {} \;
$

So closing this, as it is not our fault - I presume this is default behaviour for dpkg.

Actions #12

Updated by Benoît PECCATTE over 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions

Also available in: Atom PDF