Bug#413513: gtk+2.0: new .32 .64 suffixes break backwards compatibility for custom configuration files

[braindead]

Package: gtk+2.0
Version: 2.8.20-6
Severity: normal


040_ia32-libs.patch and its new .32 and .64 suffixes can break backwards
compatibility with per-user ( ex. ~/.gtkrc-2.0 ) or global (
/etc/gtkrc-2.0/ ) custom configuration files.

See a little strace excerpt:
access("/etc/gtk-2.0/gtkrc.32", F_OK)   = -1 ENOENT (No such file or
directory)
access("/home/braindead/.gtkrc-2.0.32", F_OK) = -1 ENOENT (No such file
or directory)
lstat64("/etc/gtk-2.0/gtkrc.32", 0xbfeef77c) = -1 ENOENT (No such file
or directory)
lstat64("/home/braindead/.gtkrc-2.0.32", 0xbfeef77c) = -1 ENOENT (No
such file or directory)
access("/etc/gtk-2.0/gtk.immodules.32", F_OK) = -1 ENOENT (No such file
or directory)
access("/etc/gtk-2.0/gdk-pixbuf.loaders.32", F_OK) = -1 ENOENT (No such
file or directory)

I temporarily fixed it with a simple symbolic link:
ln -s ~/.gtkrc-2.0 ~/.gtkrc-2.0.32

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-11-debian
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)