Bug#661471: NMU v2 (was: Re: Bug#661471: bug 661471 gnome-accessibility-themes)

[Theppitak Karoonboonyanan]

On Wed, Oct 31, 2012 at 5:34 PM, Theppitak Karoonboonyanan
<thep at debian.org> wrote:
> On Wed, Aug 29, 2012 at 10:35 PM, Theppitak Karoonboonyanan
> <thep at debian.org> wrote:
>> On Mon, Aug 13, 2012 at 3:01 PM, Theppitak Karoonboonyanan
>> <thep at debian.org> wrote:
>>> So, I agree with splitting the gnome-accessibility-themes binary.
>>
>> Any progress? If not, I'm proposing another NMU, which:
>> - Splits a11y themes into gnome-accessibility-themes binary
>> - Splits the shared translation files into gnome-themes-standard-common
>> - Makes both theme packages depend on -common
>> - Declares gnome-accessibility-themes and gnome-themes-standard-common
>>   as Replaces: the old gnome-themes-standard
>> - Drops Replaces: from gnome-themes-standard
>>
>> Debdiff is attached.
>>
>> However, some warnings are found during the upgrade test:
>>
>> ---8<---
>> Preparing to replace gnome-themes-standard 3.4.2-1 (using
>> gnome-themes-standard_3.4.2-1.1_amd64.deb) ...
>> Unpacking replacement gnome-themes-standard ...
>> dpkg: warning: unable to delete old directory
>> '/usr/share/icons/HighContrast': Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/usr/share/icons/LowContrast': Directory not empty
>> dpkg: warning: unable to delete old directory
>> '/usr/share/icons/HighContrastInverse': Directory not empty
>> ---8<---
>>
>> The remaining files in these directories are "icon-theme.cache".
>> Any suggestion on how to clear them properly?
>
> It seems this does not happen with clean installs. So, it may not be an issue.
> Could I do the NMU, then?

Uploaded to DELAYED/2.

Without response for a long time, I assume it's qualified NMU, despite the
intrusive change.

Regards,
--
Theppitak Karoonboonyanan
http://linux.thai.net/~thep/