Your message dated Thu, 28 Apr 2016 15:55:47 +0200
with message-id <20160428135547.gh21...@var.bordeaux.inria.fr>
and subject line Re: Fwd: Bug#822857: at-spi2-core: doesn't clean up legacy
directory properly
has caused the Debian Bug report #822857,
regarding at-spi2-core: doesn't clean up legacy directory properly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
822857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: at-spi2-core
Version: 2.20.1-1
Severity: normal
Hi.
Apparently /etc/at-spi2 is no longer part of the package.
The directory, though empty (at least after upgrade), isn't
cleaned up properly however:
Unpacking at-spi2-core (2.20.1-1) over (2.18.3-4) ...
dpkg: warning: unable to delete old directory '/etc/at-spi2': Directory not
empty
Could you please clean it up in a future version? :)
Cheers,
Chris.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.5.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages at-spi2-core depends on:
ii libatspi2.0-0 2.20.1-1
ii libc6 2.22-7
ii libdbus-1-3 1.10.8-1
ii libglib2.0-0 2.48.0-1
ii libx11-6 2:1.6.3-1
ii libxtst6 2:1.2.2-1+b1
at-spi2-core recommends no packages.
at-spi2-core suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Simon McVittie, on Thu 28 Apr 2016 14:51:59 +0100, wrote:
> If you haven't modified the conffile, the *next* upgrade of the package
> will clean up the empty directory.
Ok, that's what I was thinking, and was indeed considering just leaving
the issue since on the long run it'll auto-heal.
Samuel
--- End Message ---
