Bug#362885: x11-common: unable to upgrade, rmdir: /usr/X11R6/bin: Directory not empty
* Steve Langasek [Sun, Apr 16 2006, 01:19:35AM]:
> On Sun, Apr 16, 2006 at 09:47:29AM +0200, Eduard Bloch wrote:
> > I cannot upgrade the package on my system because it repeatedly fails
> > with:
> > rmdir: /usr/X11R6/bin: Directory not empty
> > x11-common postinst error: Could not remove /usr/X11R6/bin. Is not yet
> > empty
> > dpkg: error processing x11-common (--configure):
> > subprocess post-installation script returned error exit status 74
> > Errors were encountered while processing:
> > x11-common
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > Well, yes, there is one remaining file added manually by me, however the
> > postinst should not rely on that and fail otherwise.
> To expand on Daniel's closure message: X11R6 is dead, and this directory
> needs to be removed so it can be replaced with a compatibility symlink.
> Otherwise, the transition path gets much uglier as we try to track down
> one-by-one all the tools that reference /usr/X11R6/bin as an absolute path
> between now and etch's release.
> So if the file in /usr/X11R6/bin comes from an official package, please tell
> us the package so x11-common can conflict with it. If it's an unofficial
It was not from an official package. And it was a symlink, so dealing
with it is a bit more complicated. Anyhow, I wonder what exactly do we
win by trying to remove this directory. What is the problem with just
letting where it is and allow it to rot untill the last package having
files there is removed. This is the strategy used by dpkg since ages,
why should we try to nuke that directory, just for cosmetics reasons?