Bug#382360: also got failed to remove messages on latest sid
jidanni@jidanni.org wrote:
> All I know is
> # apt-get dselect-upgrade
> The following packages will be upgraded:
> deborphan initramfs-tools libilmbase6 libxcomposite1 ucf x11-common
> x11-utils xbase-clients xorg xserver-xorg xserver-xorg-input-mouse xutils
> ...
> rmdir: failed to remove `/etc/X11/rstart/commands/x11r6/': Directory not empty
> rmdir: failed to remove `/etc/X11/rstart/commands/': Directory not empty
> rmdir: failed to remove `/etc/X11/rstart/contexts/': Directory not empty
> rmdir: failed to remove `/etc/X11/rstart/': Directory not empty
> # find /etc/X11/rstart
> /etc/X11/rstart
> /etc/X11/rstart/commands
> /etc/X11/rstart/commands/ListContexts
> /etc/X11/rstart/commands/ListGenericCommands
> /etc/X11/rstart/commands/@List
> /etc/X11/rstart/commands/x11r6
> /etc/X11/rstart/commands/x11r6/LoadMonitor
> /etc/X11/rstart/commands/x11r6/Terminal
> /etc/X11/rstart/commands/x11r6/@List
> /etc/X11/rstart/config
> /etc/X11/rstart/contexts
> /etc/X11/rstart/contexts/default
> /etc/X11/rstart/contexts/x11r6
> /etc/X11/rstart/contexts/@List
> # rm -r /etc/X11/rstart
> # grep ' status installed .*x' /var/log/dpkg.log|uniq|tail
> 2008-05-31 12:38:20 status installed x11-common 1:7.3+10
> 2008-05-31 12:38:21 status installed x11-common 1:7.3+10
> 2008-05-31 12:38:44 status installed x11-common 1:7.3+11
> 2008-05-31 12:39:01 status installed xserver-xorg-input-mouse 1:1.3.0-1
> 2008-05-31 12:39:04 status installed xserver-xorg 1:7.3+11
> 2008-05-31 12:39:05 status installed x11-utils 7.3+2
> 2008-05-31 12:39:07 status installed libxcomposite1 1:0.4.0-3
> 2008-05-31 12:39:09 status installed xbase-clients 1:7.3+11
> 2008-05-31 12:39:10 status installed xorg 1:7.3+11
> 2008-05-31 12:39:10 status installed xutils 1:7.3+11
>
It works fine here. I get "rmdir failure messages" when upgrading xutils
from sarge to testing, and the rstart files are still there. Then
upgrading xutils to unstable removes all rstart file without any error
message.
Unless you provide all details from your upgrade path (i.e. full log,
versions before upgrade, ...), we can't do anything.
Brice
Reply to: