Bug#413513: marked as done (gtk+2.0: new .32 .64 suffixes break
backwards compatibility for custom configuration files)
Debian Bug Tracking System
owner at bugs.debian.org
Mon Mar 5 18:48:12 CET 2007
Your message dated Mon, 5 Mar 2007 18:46:57 +0100
with message-id <20070305174657.GA20777 at bee.dooz.org>
and subject line Bug#413513: gtk+2.0: new .32 .64 suffixes break backwards compatibility for custom configuration files
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
-------------- next part --------------
An embedded message was scrubbed...
From: braindead <braindead at fastwebnet.it>
Subject: gtk+2.0: new .32 .64 suffixes break backwards compatibility for custom
configuration files
Date: Mon, 05 Mar 2007 15:56:13 +0100
Size: 2412
Url: http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20070305/bc685e23/attachment.mht
-------------- next part --------------
An embedded message was scrubbed...
From: =?iso-8859-1?Q?Lo=EFc?= Minier <lool at dooz.org>
Subject: Re: Bug#413513: gtk+2.0: new .32 .64 suffixes break backwards
compatibility for custom configuration files
Date: Mon, 5 Mar 2007 18:46:57 +0100
Size: 1909
Url: http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20070305/bc685e23/attachment-0001.mht
More information about the Pkg-gnome-maintainers
mailing list